Software update 2.39.20 (2024 Q4)

[The_77]

One more thing to note on the update nav wise - went out for another run today and now when you’re off-route the “tooth” switches between the off-route message and the usual info, when not in TBT nav.

Which is lovely, but makes me wonder if the same could be applied to the new logic in TBT nav taking over the tooth. Is there any chance the nav changes can be expanded on in the change log notes? Just behaviour wise would be nice to know how it has definitely changed.

Else I concur with it being useful as a SA notification about the issue for 9PP users, might help/have helped in the interim before something is pushed. I find the nav changes almost worth a daily soft reset though for trail running in unfamiliar terrain but there we go.

[marwin]

@Dimitrios-Kanellopoulos Thank you for the update! I just registered on to forum to +1 the HR measuring bug. It’s nice to know that I’m late and you are working on it.

BTW: when can we expect the rollback?

[wakarimasen]

@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

[BrunoH]

More information regarding Vertical’s broken control panel. I used to be able to reproduce it with soft reset or by powering off, but I just found out that it had broken again “all by itself” without either of these boot actions. So apparently the symptom can surface even after being ok for a couple of days. I wish I knew what triggered it this time. Annoying, but not as serious as OHR problems.

[sebchastang]

@BrunoH I have also observed that sometimes even after self-repair the control panel fails again to display correctly.
I still don’t know what causes this broken display.

I agree with you @BrunoH, this is not as critical as the OHR issue, but I would still appreciate a fix.

I decided to switch access to control panel from bottom or up button to middle button (pinned widget). No display issue so far.

Maybe rendering a widget via bottom or upper buttons differs from rendering a widget via the middle button (pinned widget).
Buttons shortcuts can be configured to access a functionality (flashlight, alarm clock, do not disturb, …) or a widget. Middle button can be configured to access a pinned widget only (not a functionality).

Maybe I am wrong. I don’t know. But I share my experience if it can help Suunto to identify the cause of the issue.

[BrunoH]

@sebchastang thanks for the tip, this workaround works!

Maybe I am imagining things but it is like there’s a delay before the carousel appears.

[pilleus]

8 days ago I updated my S9PP and SV. S9PP I use for sleep tracking and as daily watch. Until today in the morning without the problems caused by the update.

In the morning I stood up at 04:54 h and went back to bed at 04:57 h. The heart rate in Suunto app shows a short peak and at the moment it goes down the measuring stopped. No heart rate, no sleep tracking for the sleep until 07:45 h.

I reinstalled the last working firmware stored in the watch to be sure things will work as expected.

[sebchastang]

@BrunoH This is not your imagination
I also noticed a “2-step” loading of the control panel widget. Top of the widget is loaded first (battery %, date), then the bottom part (menu) is loaded after a short delay.
I have also noticed this delay while loading the logbook display that I used to set as pinned widget. The weekday vertical bars were loaded, then came the filling of these bars (according to your training) after a short delay.

[t-Dox]

@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

[RoSko]

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?

[wakarimasen]

@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

[Triumph114]

@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

[SuuntoZec]

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

1. OHR stops working every few hours and needs a soft reset to restart.
2. Sleep tracking stopped working on the first night
3. 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.

[MiniForklift]

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

[peegee]

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

[Jan Van de Velde]

@peegee I have a similar issue on my Race S. Any suggestions are welcome!

[VoiGAS]

@Jan-Van-de-Velde Strange, no issues with my Race S. Daily Heartrate, Sleep Tracking and battery lifetime like before

[RoSko]

@Triumph114 Thanks! That worked just fine!

[RudelarisSR]

@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