Software update 2.39.20 (2024 Q4)
-
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.
-
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. -
No problems with my S9PP. I had the issue with an earlier firmware, but since the last two updates it seems to be solved.
-
so far the update is exceptional… leading me to also sell the AWU . it’s simply great an update
-
On the positive side, this issue with OHR stopping is saving me quite a lot of battery charge
-
@cheetah694 mine was the same. Just started working.
-
@thanasis how about battery drain problems and offset, back to normal?
AWU what it is? -
Logs sent. Hopefully those help
-
new update, but still without Ukrainian language… very sad…
-
@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…
) -
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.
-
@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?
-
@sebchastang Update: “control panel” works as expected now after powering off the watch, let it rest on the table for 15 minutes and restart it
-
@sebchastang The control panel had fixed itself over night. I powered off twice back then and it didn’t help, the contol panel remained broken. But one good night sleep and it was ok in the morning.
It’s hard to figure out what’s happening. My common sense says that data can be processed with a delay, but how on earth can a faulty UI functionality change after a delay… That’s a mystery to me.
-
@Александр-Даниленко I thought I could, instead I discovered that I can’t: so annoying
-
@BrunoH I also had the same - initially after updating it looked as many here did, but a couple of hours later, it was fine. Hey ho.
-
@BrunoH It is broken again after a power off/on
Can you please confirm it is not broken anymore even after restarting the watch? Thanks for your help. -
@pavel-samokha …installed it this morning, got the Christmas watchface… And it immediately crashed already two times on that watch face.
I couldn’t see it, but two times today already, the watchface switched back to the default watch face… And: when you enter watch faces in the store, it locks and says it’s syncing… Every single time I go to a watch face.
I restarted the device, it happened again.
Seems the quality is not where it should be.
