Suunto 2.50.28 hot-fix Q4
-
@Ecki-D.
Clever strategy! Thank you for the suggestion! -
I have nothing exciting to note other than my alarms both went off 50 minutes later than planned today, on 9PP. I suppose it’s possible I snoozed them both 5 times or slept through them but I have doubts.
-
@Ecki-D. The OHR sensor doesn’t work for me either, the latest firmware. I restored it to 2.50.26 and it’s been perfect ever since.
-
@The_77 Any chance the watch face could have been touching your skin when the alarm was supposed to go off? The touch screen activates a moment before the vibration or sound does when an alarm goes off, making it possible to snooze or dismiss it without even knowing. It’s possible this could have happened 5 times if you didn’t move.
Old software required a button push to turn off or snooze the alarm. This is the way it should be. Not sure why it changed.
-
@duffman19 I mean, I was wearing long sleeves, so theoretically they could have been touching the surface, if that’s the case then it’s plausible.
I guess if it happens again I’ll find out!
-
After latest FW: ~1%/h drain in smartwatch mode (~4d total) 9PP.
• No activities
• GPS perf OK (~37–40h)
• Static WF
• Soft reset → no change
• Flight mode → still ~1%/hHW seems fine → likely FW idle/deep sleep regression.
I think I’ll roll back FW.
-
Race S, no issues until the latest hotfix. Now issues with sleep detection. There is also no data on the watch. Should I open a separate thread?



-
@OutdoorMan no need to open a new thread. It is already known to Suunto, it seems… https://forum.suunto.com/post/185192
-
@2b2bff I see, thanks. Let’s wait then…
-
Update – S9PP idle drain
Observed ~1%/h drain in normal mode.
In flight mode: ~0.25–0.5%/h (normal).
BT on (watch) + BT off (phone): normal drain.
Fully connected to iPhone: ~1%/h again.So it seems related to active BT/App communication, not hardware or general FW idle.
Now testing with background app refresh disabled.
Will report back.
-
Hi everybody,
Does the North-up option work? I think I tried just after release of version 2.50.26 and it worked, but now on 2.50.28, it doesn’t work, even after a soft reset, any clue?