Anyone Notice Battery Saver Turns On After Leaving the Activity Menu?

Thank you for everyone's patience. Please include the following info in your bug report going forward so we can continue to investigate the root cause:

- When reporting this issue, please confirm your Battery saver during sleep setting.
- What the hours of your sleep window is on the watch (Menu > User Profile > Bed and Wake Time).
- Also, tell us what the time is when you see the issue and what you were doing that led up to discovering battery saver mode was enabled.
- Is it actually in battery saver mode or is it just showing the watch-face?
- Do you have a CIQ watch-face active?

Thank you to those who have contributed to this bug report and assisting us in our investigation. 

Happened again about 90 minutes ago, so I photographed the relevant points.  I was actually viewing the app and backed out of activities due to GPS lock problems again.

1. Outside of sleep hours

2. Screenshot of Connect shows the watch isn't connected.  The pulse field is no longer active for at least 90-120 seconds and was the displayed value when last connected.  

3.  I had to go to the controls menu to turn battery saver off and then shortly after, Connect confirmed the watch was reconnected and then the pulse began updating again.

Great, thanks for the info. Can you tell me what your PulseOx settings are as well as every setting outlined in Menu > Power Manager > Battery Saver?

Also I have sleep PulseOx enabled, but have it turned off during the day 

I can confirm again everything I wrote above.  The glitch appeared twice yesterday.  Unfortunately, with 8.10, Ive gone from a couple to a few times a month to several times a week or a couple times a day now.

I can confirm it happens on Instinct Solar 1, too. I was on a multi day bike ride, so I was concerned with the battery charge and decided to use the battery saver for the first time. This is how I noticed something wrong.

I will try to describe my way of reproducing it even though some steps may be unnecessary.

Initial settings:

• PulseOx: off
• Batery Saver: always off
• Sleep Time: 23:00 -> 8:00
• Watch bluetooth is on, Phone is off.
• When battery saver is on, watch bluetooth is off.

Steps to reproduce:

• Turn on the Battery Saver (keep "during sleep" off)
• Go through the sleep time in the evening (this and the next 3 steps are probably unnecessary, but it was part of what I did)
• Turn it off.
• Sync with the phone
• Turn it on again.
• Also, turn on Battery Saver during sleep
• Sleep again

After the sleep hours end, the watch switches to the regular watchface. This may or may not be considered correct, depending on how we expect the manual Battery Saver option to work: whether it is a permanent or a one-time setting.

I synched with the phone. I usually do so in the morning. Most likely it is unrelated to the bug.

The scenario continues:

• Start an activity
• Save it

At this point, the battery saving watchface appears. Starting another activity no longer triggers the bug, no matter if I enable the Battery Saver manually again. All works fine until I go through the sleep hours again.

In my opinion, the last part of the scenario causes confusion. However, I am unsure what is the intended way the Battery Saver is supposed to work. It could be either:

1. Have a single setting, that works only during the day and turns off after the sleep hours end. For example, turn it on, sleep, then it switches off automatically.
2. Have two separate settings, so that you can turn it on manually, but sleep hours would not change it. For example, turn it on manually and it stays on until one toggles it, no matter the sleep hours. When it is off, only the sleep hours setting applies.

It is a quite long post, but I hope I made everything clear.

I am still running firmware v16.00, btw, but from what I read here, the bug is still present in all watches, so it doesn't matter.

This is AMAZING, thank you so much! Following your steps, I was finally able to reproduce.

I've given this info to our engineers where they can narrow the focus to a specific area in the code and start digging.

Wowowow