Suunto 2.50.28 hot-fix Q4

Ecki D.

@misu763 It helps me to have the passcode function enabled.

So everytime the hr sensor fails, the watch thinks it is not on the wrist anymore and locks itself.
So as soon as I have to dial in the passcode I know something is wrong.

misu763

@Ecki-D.
Clever strategy! Thank you for the suggestion!

The_77

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.

Ádám Patkós

@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.

duffman19

@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.

The_77

@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!

Ecki D.

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%/h

HW seems fine → likely FW idle/deep sleep regression.

I think I’ll roll back FW.

OutdoorMan

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?

2b2bff

@OutdoorMan no need to open a new thread. It is already known to Suunto, it seems… https://forum.suunto.com/post/185192

OutdoorMan

@2b2bff I see, thanks. Let’s wait then…

Ecki D.

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.

JuanPh

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?

HonzaS

Just found small bug. The next alarm time in morning report is not right, because it does not reflect alarms set for workdays. I think it only counts with general time.
If I have set alarms for 6:00 and 10:00 on workdays and morning report shows up on saturday at 8:00, it shows next alarm at 10:00 but next alarm will be on monday at 6:00.

Ecki D.

S9PP – Idle drain investigation (final update)

I initially observed ~1%/h drain in smartwatch mode after the latest FW.

Testing over the last 24h:
• Flight mode → ~0.25–0.4%/h (normal)
• BT on (watch) + BT off (phone) → normal
• Background App Refresh OFF → normal overnight drain
• Activities (no GPS / short GPS) → within spec
• With Background App Refresh ON → slightly higher idle, but not consistently reproducible 1%/h anymore

Conclusion so far:
• HW is fine (training battery life fully in spec)
• Deep sleep works
• High drain seems related to iOS app communication state
• Not a permanent FW idle regression

For now I’ll keep Background App Refresh disabled and continue monitoring.

thanasis

regarding the drain/battery management or whatever is related to the indication the watch provides … I am a bit disappointed… after letting the watch deplete and recharged it , I used and for 2 days it consumed like 2% per day - which gave me some smiles… (with oHR and notifications off though) … then I went for a run , using Suunto HR Belt, enabled the notifications and it lost 10% over 1 hour…

it is what it is , but it’s definitely not great

Ecki D.

@thanasis if you like you can check battery usage during workout in https://smlanal.szmigiel.design from @łukasz-szmigiel
Export the json form the workout in suunto app and upload it there.

I haven’t checked yet but I guess the permanent sync with the HR Belt or other sensor is using much more battery. I did a MTB Ride this morning only with the OHR and best GPS and it uses about 2,8% / Hour.

Edit:
Uploaded a 10k run from December with Suunto HR Belt, it says 4,04%h. Still have to re-check with latest FW and App version.

The_77

Interesting bugs today, probably easy repeatable if someone wants to check.

Imported a Suunto guide from intervals.icu and set up a run with a route. Firstly, I previously had media on, and it wasn’t possible to turn off from the menu when running (long press bottom right).

Secondly, every time a new section started of the training, the watch would tell me it was off route, before confirming I was back on route about 10s later. Which if you combine with the vibration from getting into the correct zone, vibration to start the interval and so on, is a lot of buzzing on the wrist, especially if you have a short (100m or so) interval.

I’ll try and replicate it whenever I do a quality session next, probably earliest the weekend or next week I guess.

gagbo

@Benjamin-0 when I RMA’d mine I just got a “your battery’s fine, here’s your watch back”, so lucky you

The_77

Just to add, had the same issue yesterday with the route dropping temporarily when in conjunction with a guided so every new interval caused a “route lost”/“back on route” combo.

Also, the watch hung on a zonesense screen, with nothing happening when buttons were pressed. Happily before I soft reset I tried the long press bottom button to escape to a menu, and then exited out, all was fine. Avoided the zonesense screen the rest of the run, but if someone else has that they may resort to soft resetting.

Appreciate it’s a bit late in the cycle of watch updates to report, but any idea if these have been fixed in new SW update or are unreported? @egika @dimitrios-kanellopoulos

tmclr

Just replied to a post in the 9PP forum specific to this issue, but probably more appropriate to mention here…

After the last firmware update I started getting frequent phantom alerts/vibrations - several per day with no message on the screen or apparent reason.

In my case, this behaviour it disappeared after a few days without me taking any action, however over the last few days it has spontaneously started again - frequent phantom alerts/vibrations.

Not sure if this was acknowledged as a bug in the latest s/w and we can expect a fix in the imminent release?