Battery Saver Control crashes watch

Working fine for me on 5.07

interesting. thanks for letting me know. wonder if a semi-hard reset (holding power for several seconds)  is in order. i can't remember if that wipes things like HR record or body battery though...

hmmff... did a soft reset and still crashes. anyone else out there have this problem? i'm hoping i don't need to attempt a full factory reset. seems i'm going through a lot of trouble to circumvent a missing published feature (sleep setting for Battery Saver) to get more battery life (ie, way below spec)

Yes, happens on my watch on 5.07 as well when perfomed exactly as you describe:
1. Add battery saver to the controls menu
2. Turn battery saver on - works
3. Turn battery saver off - watch restarts.

This doesn't happen if done through the settings menu, not through the controls menu.

Going to submit this one to Garmin as well with a reference to this thread.

thanks for confirming. misery loves company :p 

my thought is that with a couple button pushes before going to sleep i can save myself 1-2% battery consumption overnight

Garmin asked me to send a video (i did) and also a report via Garmin Express (i did this too). they also asked if this happened when go via the Power Management menu and i was surprised to see it happened there too. i don't think that happened with 4.16. so this may in fact be worse in 5.07 than 4.16.

I had to repeat the steps several times before it would happen. The behaviour is not reproduceable 100% of the time.

interesting... my update:

1. i have found that i cannot reproduce the problem using a Garmin provided (built in) watch face. it only happens with Connect IQ watch faces (Glance, for example). for me, with a Connect IQ watch face, the problem happens probably 80-90% of the time.

2. Garmin support is asking that i send my unit in which i am strongly against doing. my buttons are nearly perfect with my watch and as annoying as this problem is, i am not sure i want to play Russian Roulette with the Forerunner Button issues. based on enough of you seeing this problem, i think it has to be a software issue. i would think that Engineering could easily reproduce this problem. while i appreciate them wanting to get to the bottom of this, it seems their default method is to ask to give you a new watch and inspect the unit even though this is occurring for many users.

Would be happy to send my watch back, provided they send me a replacement out first, so I'm not stuck for 2 weeks waiting for a turnaround. Mine is exhibiting your issue and others that they aren't able to reproduce. I suspect that they wouldn't accept it, since it's not technically sold where I live and I imported it from Germany.