# PebbleOS Update Not Triggering **URL:** \ **Category:** Get Pebble Help!\ **Created:** [June 30, 2026, 8:24am UTC](https://forum.repebble.com/t/pebbleos-update-not-triggering/1088 "2026-06-30T08:24:41Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![RF15](https://avatars.discourse-cdn.com/v4/letter/r/977dab/32.png) [@RF15](https://forum.repebble.com/u/RF15)\ **Post date:** [June 30, 2026, 8:24am UTC](https://forum.repebble.com/t/pebbleos-update-not-triggering/1088/1 "2026-06-30T08:24:41Z")
As per steve: > We paused 4.19 rollout Original post: I have a Pebble Time 2, connected to my Android phone. Yesterday I got a notification that the new PebbleOS Version 4.19.0 is available, but I swiped it away because it was inconvenient at the time. There was also a Pebble App update, which I installed. Now, the app tells me correctly that the watch is still on 4.17.0, but when I press on “Check for Updates”, nothing happens. No visual feedback that it is checking for an update, no feedback that a newer Version is available, or that there was a problem reaching the server, or that there was a problem talking to the watch. Visually nothing to work with, apart from the highlighting that the button was pressed and released. Did anybody else experience this? What’s a good solution for it before I just factory reset the watch and hope for the best? ---
**Author:** ![uaparit](https://yyz1.discourse-cdn.com/flex033/user_avatar/forum.repebble.com/uaparit/32/747_2.png) [@uaparit](https://forum.repebble.com/u/uaparit)\ **Post date:** [June 30, 2026, 9:08am UTC](https://forum.repebble.com/t/pebbleos-update-not-triggering/1088/2 "2026-06-30T09:08:52Z")
Yes, I’m experiencing the same issue with the app. If you don’t know how to trigger the update, there are ~~two~~ one ways to do it: - ~~There might still be a message on your phone telling you how to trigger the update (only if you allowed the Pebble app to send you messages).~~ - Otherwise, check the messages on your watch. Press the middle button (when the message is displayed) and select “Update now.” ---
**Author:** ![RF15](https://avatars.discourse-cdn.com/v4/letter/r/977dab/32.png) [@RF15](https://forum.repebble.com/u/RF15)\ **Post date:** [June 30, 2026, 9:32am UTC](https://forum.repebble.com/t/pebbleos-update-not-triggering/1088/3 "2026-06-30T09:32:28Z")
Update: Factory Reset also only gets the watch to 4.17.0. On the plus side, Factory reset is fairly painless and quick. (unless you have something stored for the apps I presume, which I don’t) ---
**Author:** ![uaparit](https://yyz1.discourse-cdn.com/flex033/user_avatar/forum.repebble.com/uaparit/32/747_2.png) [@uaparit](https://forum.repebble.com/u/uaparit)\ **Post date:** [June 30, 2026, 11:51am UTC](https://forum.repebble.com/t/pebbleos-update-not-triggering/1088/4 "2026-06-30T11:51:57Z")
I just tried to trigger the update (via the notification on the watch) and got the message “Failed.” I can’t upload any pictures yet, so here’s a link: [clock screenshot](https://upload.darkplanetego.de/f.php?h=0HziBByU&p=1) (But the link is only valid for one month) ---
**Author:** ![steve](https://yyz1.discourse-cdn.com/flex033/user_avatar/forum.repebble.com/steve/32/13_2.png) [@steve](https://forum.repebble.com/u/steve)\ **Post date:** [June 30, 2026, 2:30pm UTC](https://forum.repebble.com/t/pebbleos-update-not-triggering/1088/5 "2026-06-30T14:30:32Z")
We paused 4.19 rollout ---
**Author:** ![Flynn](https://yyz1.discourse-cdn.com/flex033/user_avatar/forum.repebble.com/flynn/32/73_2.png) [@Flynn](https://forum.repebble.com/u/Flynn)\ **Post date:** [July 2, 2026, 1:20am UTC](https://forum.repebble.com/t/pebbleos-update-not-triggering/1088/6 "2026-07-02T01:20:09Z")
How come?​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​ ---
**Author:** ![jhnc](https://yyz1.discourse-cdn.com/flex033/user_avatar/forum.repebble.com/jhnc/32/624_2.png) [@jhnc](https://forum.repebble.com/u/jhnc)\ **Post date:** [July 2, 2026, 1:30am UTC](https://forum.repebble.com/t/pebbleos-update-not-triggering/1088/7 "2026-07-02T01:30:16Z")
To fix a bug, judging by the comment on 4.19.1: > fixes an issue with text rendering on watchfaces