"Raise to Wake" not working properly during activities
-
Hi all
In my last activities I’ve discovered that ‘Raise to wake’ doesn’t work properly in my Race 2.During activities if I raise the arm screen turns on, no problem. But, a lot of times, when arm goes down screen remains on and doesn’t turn off. Sometimes screen remains on several minutes. Today I was wearing also Race S in same arm and ‘Raise and wake’ has worked pwrfectlly during all activity. In Race 2, 8 out of 10 attempts fail, and screen remains on several minutes when bracing.
Yesterday, same behavior in an Indoor Cycling activity (training in the rollers).Have you seen this behavior?
Suunto T3D, Suunto Spartan Trainer, Suunto Spartan Ultra (retired), Suunto 9 Baro (retired), Suunto 9 Peak (retired), Suunto Vertical Titanium Solar, Suunto Race S, Suunto Race 2 Ti.
-
@jjpaz Yes, some of us have reported similar odd behavior related to the backlight across multiple watch models on the 2.50.26 thread (here, here, and here). The trigger seems to be entering the activity start screen. And you are correct that it doesn’t seem to happen every time, but maybe 50-80% of the time the backlight function changes without warning.
The only solution we’ve found is to reset your backlight settings in the watch’s main menu (turn them on and then off again).
The bug has not been confirmed by Suunto yet, but it appears to affect quite a few of us, and maybe more that haven’t noticed it yet. I would imagine this will require a hotfix as it will cause severe battery drain for those who do not notice that the backlight (MIP) or screen remains active when it should not.
-
I had that same issue with my Race and Race 2 several times (and that is also the reason why I returned to MIP Suunto Vertical).
-
@jjpaz I experienced this with my Race 2 for the first time today. I was about 14km into a trail run when it started happening - after a raise to wake the display would remain on for about 2 minutes after my arm going down. This sequence occurred 3 or 4 times, until I briefly manually paused and then resumed the activity - in my case that resulted in return to normal display behaviour once again.
