Software update 2.39.20 (2024 Q4)

[shubri]

OHR stops for me also, Suunto 9PP - super annoying, although I had similar issue before, but maybe once a week. Now it cannot hold for 1h.

[jrun1200]

@sracer yes, it looked and worked so great as it was before, contributed to the straightforward clean look and feel of the watch. Now - even though a lot of people seem to like it - the carousel design just doesn’t work for me. it makes the screen far too messy with the different font sizes and loss of any alignment. I had thought it was a deliberate design choice by Suunto to keep things simple, not something that would need to „improve“.

I hope, future updates will bring an option to turn the carousel on or off.

[richardharnett]

@steffiwiegand
Hi, I have the same problem since the update. A power down and restart revive the HR etc. for a number of hours but it then shuts down again without warning.
I hope this fix comes soon (though not likely over Christmas) and I hope they test the next update more rigorously before release - the very thing this update was supposed to fix has introduced it onto my watch for the first time.

[Dimitrios Kanellopoulos]

Hi all it’s me again.

We will rollback the update for your s9pp due to the ohr issue until this is fixed.

You will be able to use the new watchfaces so not everything will be lost.

I hope it’s understandable and thank you so much for the feedback.

For people that don’t want the rollback they can disable the automatic updates via the app.

I’ll keep you posted once I know more.

For now, you need to know that the ohr jamming issue is a critical one, but due to holidays and time constraints , communications with the vendor etc we cannot move in some other direction. To be clear we did due to the needed to fix it but we don’t have certainty in the fix and we don’t want to ruin any more your previously fine experience.

[Łukasz Szmigiel]

@stromdiddily he did. On an unofficial channel, for a few people.

Take a look at reddit and Facebook groups, and also the people who created forum accounts just to post that their HR is no longer working.

For an international company this looks very miserable.

It looks as if @Dimitrios-Kanellopoulos was the only one working on this issue, on the weekend, as if it was his pet project

I believe it’s a communication issue. There should be a notice in Suunto App for all users with affected devices. There’s a problem, we’re sorry, we’re working on it.

[wakarimasen]

@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

[sebchastang]

@tuxella No problem for me to add new WiFi networks with latest firmware. Did you try to reboot your network/wifi equipments or select an other WiFi channel?

[t-Dox]

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

[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