Watch going in battery saver mode by itself

Battery saver mode is supposed to go on when I have three days of battery left . But the thing goes on by itself. The fastest way I found to get my regular watchface is to go in and out of my sleep mode.

Anybody seen thisQuestion

.

  • I'm about positive this is due to accidental presses of the top right button. That activates your default activity. From there after a few minutes it thinks you've only got X hours remaining, which then triggers the mode.

    I think disabling all "favorites" in the Activites, or setting the only "favorite" to Settings may get past it. I've been having this happen for quite a while now and just switched it to see if it'll make a difference.

  • I have the same issue on my Epix 2, and have had the issue for months.  Incredibly annoying. Would really appreciate a fix, especially since it has been over a year since this was posted...

  • I observed this bug, but only partially.

    Maybe the bug was fixed since your post, but the fix was mot perfect?

    This morning I woke up earlier than usual as the result of the “clock change day” ending Daylight Savings period. I manually ended Sleeping before the sleep window end time. It seemed that Battery Saver and DND properly switched off.

    But an hour later, which was after the end of my sleep window btw,  I wanted to modify ciq DF settings and realized my watch is not connected neither to ciq app, nor gc app. I switched BT settings on my phobe off and on, then I rebooted my phone, then I switched my watch off and on, then power cycled it. 

    Since my watch was still not connected to my phone, I tried a wifi sync which worked. Before a complete unpair and repair I checked Settings/Connectivity/Phone menu item and the status of my phone was off. I manually switched on and everything became perfect.

    So it seems that manual end of sleeping does NOT fully switch off all the elements of Battery Saver mode, namely the “Phone Connection disabled” is not restored.

    I am also wondering whether the whole thing was related to DST day, if so there is no way that I can proove there is a bug.

  • I experienced exactly the same, I'll file a bug report!