Software update 2.39.20 (2024 Q4)
-
@wakarimasen said in Software update 2.39.20 (2024 Q4):
@t-Dox said in Software update 2.39.20 (2024 Q4):
@wakarimasen said in Software update 2.39.20 (2024 Q4):
@Dimitrios-Kanellopoulos No worries - these things happen. Mistakes in surgery (for example) and issues with new firmware affecting the HRM on a watch that is used for non-professional sports activities, are quite clearly different things
I don’t quite understand the connection with surgical errors… but as a software developer, I can only agree that errors in our industry can happen and that it’s not always the developers’ fault. Often what’s missing is testing and review work that should be done after development but that, either to cut costs or to stay on schedule, isn’t done.
Some mistakes are more important than others
that for sure, but in surgery the same procedures have been practiced for years, it is a much more repetitive job, there are always more people (and eyes) involved in the same operation (anesthetist, surgeon, nurses…) and it is much more difficult to make a mistake. For this reason it seems to me a bit of a risky comparison. In software there is a constant evolution, new libraries and frameworks every year and usually the developer works alone, so it is much easier to make mistakes
-
Hi there. Since there doesn’t seem to be a timetable of when the official return to the last Software Version will take place, is there a guide how to manually “downgrade” to 2.37.48?
-
@t-Dox said in Software update 2.39.20 (2024 Q4):
@wakarimasen said in Software update 2.39.20 (2024 Q4):
@t-Dox said in Software update 2.39.20 (2024 Q4):
@wakarimasen said in Software update 2.39.20 (2024 Q4):
@Dimitrios-Kanellopoulos No worries - these things happen. Mistakes in surgery (for example) and issues with new firmware affecting the HRM on a watch that is used for non-professional sports activities, are quite clearly different things
I don’t quite understand the connection with surgical errors… but as a software developer, I can only agree that errors in our industry can happen and that it’s not always the developers’ fault. Often what’s missing is testing and review work that should be done after development but that, either to cut costs or to stay on schedule, isn’t done.
Some mistakes are more important than others
that for sure, but in surgery the same procedures have been practiced for years, it is a much more repetitive job, there are always more people (and eyes) involved in the same operation (anesthetist, surgeon, nurses…) and it is much more difficult to make a mistake. For this reason it seems to me a bit of a risky comparison. In software there is a constant evolution, new libraries and frameworks every year and usually the developer works alone, so it is much easier to make mistakes
For sure - pick whichever analogy which suits you, that essentially sends the message that:
- worse things happen at sea
- there is no sense crying over spilt milk
Happy Christmas everyone
-
B Brad_Olwin referenced this topic on
-
@RoSko Yes, I found this :
https://forum.suunto.com/post/159082 -
BTW, apart from the bug with OHR, the S9PP has other bug or weird behaviour, which comes from old firmwares.
One of them - why does the watch turning of the screen even during the charging?
Also graphical bug with “Resources”.
And resources still doesn’t update automatically on many watchfaces. Some watchfaces are bugged. For example the “Race” one shows empty calories scale (not always, but most of the time). Same watch face cannot fit the word “Resources”, instead writting something like “Resour…”. Other watchfaces are also problematic. You cannot see HR on them (if you chose it from complications), once watch are locked.And my favourite - bug in swimming, I wrote too many times about:
https://forum.suunto.com/topic/9533/swimming-problems-s9pp?_=1735054260795 -
@pavel-samokha @Dimitrios-Kanellopoulos @Egika
Just to make sure:
The problems with the new release does not only happen the S9PP.Race S (at least mine) are also impacted:
- OHR stops working every few hours and needs a soft reset to restart.
- Sleep tracking stopped working on the first night
- And the settings of my Bluetooth devices (HRM + PWR) were changed
Bad/Inconsistent data being worse than no data, I downgraded to the previous software release until a fix is available. Everything has been working like a charm since then.
Looking forward the fix.
PS: Like others, I love Suunto for its design, deliberate simplicity, and reliability. Don’t change that.
-
Charging the watch after this update is a real problem. When I plug the watch in nothing happens, this morning I had to do 4 or 5 soft resets and a couple of power on/off and it finally started charging. Usually nothing happens when you connect the charging cable, occasionally it shows the charging screen on the watch but the battery percentage doesn’t increase
It’s a real PITA is I’m honest, don’t know if this is a noted issue or just me
-
@Dimitrios-Kanellopoulos
I hear a lot of talk about the problems with the PP, but not so much about the race.
I’m having similar issues with my Race, my main issue is irregular sleep tracking, and in the last two nights I have no sleep tracking whatsoever!
I really don’t know what to do about it, it is really frustrating. I send the logs but would like a suggestion how to overcome the problem.Been with a Suunto on my wrist since Ambit2
Currently alternating between Race titanium & Vertical titanium solar.
Would love a Vertical with amoled display. -
@peegee I have a similar issue on my Race S. Any suggestions are welcome!
-
@Jan-Van-de-Velde Strange, no issues with my Race S. Daily Heartrate, Sleep Tracking and battery lifetime like before
-
@Triumph114 Thanks! That worked just fine!
-
@Jan-Van-de-Velde said in Software update 2.39.20 (2024 Q4):
@peegee I have a similar issue on my Race S. Any suggestions are welcome!
Same here, my Race S does not register sleep tracking neither HR since firmware update. Hotfix will include update for Race S?
Regards
-
@peegee With the Race, sleep tracking also stopped from one day to the next. Deactivating and reactivating sleep tracking solved the problem for me.
-
Hi and happy holidays,
Do we have any ETA for the rollback?
I got stuck without the old build on my watch. Can’t rollback manually
-
Sleeptracking stopped again tonight after 4:46h sleep. So did oxymeter. Only reboot fixed it.
But now system menu is gone too. I use the bottom button as a shortcut like other do.
At least I have a Christmas Tree
️ as a watchface.To be honest, Suunto, please make it possible to BETA TEST your software before scheduling a release.
I’m in the gov IT business and know how it feels when the head of a ministry suddenly comes out of the
. It took some time but we managed to not role out such obvious bugs for years now just by getting really hard nut software testers 
-
@Ecki-D Suunto does extensively beta test, if you read a few posts down you will find this issue was caused bt something else.
-
Hello.
I have a Vertical ti.
The sleep registered by the watch is correct, but the one mentionned in the Suunto app is not correct. It’s like the app only registered the sleep after my first wakeup (bathroom ;))
Is there a log I could send to someone ?
Regards,
T -
@Dimitrios-Kanellopoulos said in Software update 2.39.20 (2024 Q4):
@false proper qa tests where done extensively. There was another issue that caused this.
These two statements contradict each other.
-
@Nicola-Fontana Not sure what would cause your training data to get lost. So far it hasn’t been the case at all. Switching to a different brand because of a firmware glitch seems like a knee-jerk reaction to me. When a competitor has a bad release you’ll have to switch again. That’s just bad strategy. I could resolve all issues by downgrading the firmware and turning off automatic firmware updates. No data was lost on the way.
-
After the last update 2.39.20 my Peak Pro heart rate monitor stops working when I turn on sleep tracking. It starts working again if I turn the watch off and on again while sleep tracking is disabled. Looks like a bug.
