I have the new Pebble Time 2 running PebbleOS v4.19.0 and connected to an Android phone (One Plus 11 5G, OxygenOS v16.0.5). For the most part the watch has been working great and I’m very happy with it. But in the past week it has locked up twice.
When I say locked up, I mean the screen is off and pressing the Back button or any button, does not turn it back on and my phone shows that it is disconnected. I have to hold the Back button on the watch for at least 15 seconds before it will turn back on.
The first time this happened was on 6/25/26 but I don’t know what version of PebbleOS I had at that time. I do however apply the firmware update as soon as I see it’s available through the official Android Pebble app on my phone.
The second time this happened was sometime between when I applied the PebbleOS v4.19.0 firmware update last night (6/29/26) and this morning. I actually woke up late today because my watch was locked up so the daily alarm I have did not work.
I never had this problem with my previous Pebble Time that I used over 8 years. I know there is active development going on for PebbleOS so I understand things like this can happen. I just want to find out if this is a hardware or software issue.
I have the same, exact problem. Happened twice during the night within the last few days. I assumed it is a bug in the OS. I also noticed that while it went blank, the watch went from about 50% battery down to 26% in just a few hours. I am on v4.19.0.
Thanks for the report. Could you please send it to us through the mobile app? Click Settings > Help > New Bug Report. Make sure your watch is connected to your phone before doing this, this sends us important log information that we will use to fix the issue.
I thought I was the only one with this problem, but it turns out it’s a software bug. My PT2 also shuts down during the night and I wake up to a black screen. My theory is that if Health (HR) is running overnight and the display is showing the heart rate, it causes the device to crash. Interestingly, it happens around 3 and 4 am.
The watch “locking up”, as you put it, just happened to me a few minutes ago. I’ve submitted a bug report. Both my watch and Android app are running latest versions of the software.
Well, last night I tried using my ‘The Royal’ watchface (which only uses the ‘Steps’ health feature), and lo and behold, the PT2 cut out again during the night. I’ve already sent my bug report to Claudio in Support. In my view, the watch freezes when using watchfaces with health functions (displays). My guess is that it’s related to sleep tracking.
Just following up on this, I have not experienced this issue since the last time I posted. There have been two firmware updates that I’ve applied as they get released so I’m now running v4.19.2. At this point it’s hard to say if one of those releases resolved the issue or this is just one of those more elusive bugs.