Software update 2.39.20 (2024 Q4)

SuperFlo75

After the update, my wife’s S9PP stopped the OHR this night, which causes a wrong sleep tracking… we did a soft reset… wait and see… it seems to be an issue with the S9PP? My SV is working as usual!

taziden

Same here. 1h47min of sleep according to S9PP, then no more HR after that.

Dimitrios Kanellopoulos

Hi @SuperFlo75 @taziden @Александр-Даниленко @Francesco-Pagano @Janne-Leppamaki @The_77

Please send logs via the app and send me a private message with your email address used in the app to check the issue with OHR stop working.

Could you help me out ?

fv4500

@Dimitrios-Kanellopoulos
Same issue observed here, 9PP shows no OHR at all. Sensor is off. Won’t work or get active in the context of an activity either (OHR on, sensor/belt HR off). HR widget shows “Heart rate - not measured”.

Soft reset restored OHR back.

Keeping an eye on how this develops!

cheetah694

@BrunoH I tried everything and my Control Panel was still broken. I gave up on it and went to work. Now it’s repaired by itself. Took literally no extra actions. Maybe just give it some time and it will be cured.

SLAUB1

S9PP here, and no sleep tracking for 2 days now. OHR needs a soft reset to start working again.

tmclr

@Dimitrios-Kanellopoulos

Seems this is an issue for all 9PP users. Also being reported on Reddit.

Mine is the same - heart rate readings too high when working, but frequently OHR sensor not working at all, and sleep tracking also broken.

minimark069

The same for me S9PP stopped OHR at midday yesterday until I did a reset and only recorded 1.12h sleep last night.
On a more positive note my suunto smart belt seem to be connecting to the watch again following connection issues with the previous FW.

pilleus

No problems with my S9PP. I had the issue with an earlier firmware, but since the last two updates it seems to be solved.

thanasis

so far the update is exceptional… leading me to also sell the AWU . it’s simply great an update

Francesco Pagano

On the positive side, this issue with OHR stopping is saving me quite a lot of battery charge

Audaxjoe

@cheetah694 mine was the same. Just started working.

gerasimos

@thanasis how about battery drain problems and offset, back to normal?
AWU what it is?

Janne Leppamaki

Logs sent. Hopefully those help

andry_ua

new update, but still without Ukrainian language… very sad…

Matúš

@pilleus said in Software update 2.39.20 (2024 Q4):

No problems with my S9PP. I had the issue with an earlier firmware, but since the last two updates it seems to be solved.

Same here! (At the moment…)

t-Dox

Hi guys, on 9pp, it seems there is a problem with the counting of watch faces installed on the watch, the default one is not considered and therefore when you get to 3/4, it does not install others. On the counting of sleep hours, it also seems to me that they are counted badly, battery life instead perhaps improved slightly (used 30% in two days with an hour of indoor activity without GPS) but I prefer to wait a few charge cycles to see if it has improved/resolved (I did both hard reset and restart, after the firmware update)

Александр Даниленко

@Dimitrios-Kanellopoulos said in Software update 2.39.20 (2024 Q4):

Hi @SuperFlo75 @taziden @Александр-Даниленко @Francesco-Pagano @Janne-Leppamaki @The_77

Please send logs via the app and send me a private message with your email address used in the app to check the issue with OHR stop working.

Could you help me out ?

I sent it just now

As additional information, here is the video showing that OHR doesn’t respond at all (even activity start or oxygen blood measurement):

https://youtu.be/lnAEC9PiR98?si=Ndj0l9qhMBsaDRyD

P.S. OHR stopped working 3rd time for the last 2 days.

sebchastang

@BrunoH said in Software update 2.39.20 (2024 Q4):

@kriskus no amount of soft resets or language changes can fix this on my Vertical.

Same issue on my Vertical
Still persists after several reboot/soft reset.
Any advice is welcome.

Александр Даниленко

@MirkoP said in Software update 2.39.20 (2024 Q4):

Otherwise I will forced to make a firmware downgrade, waiting for a fixing of this annoying bug.

How to make a firmware downgrade?