I got this bug today(15 aug) for the first time on my FR. Red shift stays on after waking up. For context, I noticed an update installing probably couple or several days ago, not sure. Current SW version is 24.12.
I got this bug today(15 aug) for the first time on my FR. Red shift stays on after waking up. For context, I noticed an update installing probably couple or several days ago, not sure. Current SW version is 24.12.
I think I’ve figured out what’s causing this. I didn’t have it happen even once over the past few days, but last night I started an activity that ended after the time my red shift starts. So when the activity…
They are aware, and a fix is claimed to be in place in the latest beta:
Just had it again this morning too, hadn't happened for a while...
Have this bug now as well. Here is what I'm seeing-
(During the day, start with Sleep Mode: Off)
In Settings -> Display -> During Sleep -> Red Shift, change the Status to on. Red Shift then turns on, even though I am not currently in Sleep Mode.
Running v25.04.
---
These Garmin bugs are so frustrating.. after the recent blue triangle of death fiasco, I really felt fed up with Garmin's unreliability and thought about moving back to Apple Watch Ultra. These kinds of small bugs don't help Garmin's case. As a software engineer, we use automated tests to prevent these kinds of small bugs and for a device that some of us trust our lives with, I would expect Garmin to have an extensive test suite and do a far better job preventing these regressions from happening.
It is getting worse. My watch is stuck now every morning in the sleep mode with red shift on and touch-display off (I added the touch display off function in the sleep mode last week). I can not turn off the sleep mode manually with the sleep mode hot key. But urning off the red shift manually works. Turning on the touch dislay manually I have not yet checked. Bt I wonder if anything else is than still stucked in sleep mode. So in the moment I turn my watch off and on again after waking up. I'm looking forward for a bug fix...
They are aware, and a fix is claimed to be in place in the latest beta: