Software update 2.39.20 (2024 Q4)

[peegee]

@pavel-samokha said in Software update 2.39.20 (2024 Q4):

For Suunto 9 Peak Pro, Vertical, Race and Race S

• Improved outdoor distance accuracy
• New GNSS software: SONY v00.173
• Automatic compass calibration
• Save POIs or start bearing navigation by using ruler point markers in map
• SuuntoPlus Sports App displays device connection status
• New Christmas and New Year watch faces, along with a new green theme watch color*
• Added a button lock option in the control panel
• Enhanced UI visual effect (the zoom effect)
• Fixed battery consumption issues in certain scenarios
• Bug fixes and stability improvements

*new watchfaces for Christmas and New Year not yet released in SuuntoPlus Store, will be released soonish are published now in SuuntoPlus Store and should be installed from there

Any info when a fix will be coming out…?

[Łukasz Szmigiel]

What is 2.39.34? A fix or a previous version with bumped up version number?

[Sergey Balbir]

I have got 2.39.34.22544
Going to install it…

[Danny poleg]

@Sergey-Balbir Is this update for all watches???

[Sergey Balbir]

@Danny-poleg
I got it for S9PP

[peegee]

@Łukasz-Szmigiel
Good news now just need a fix for the race….

[Dareo]

Due to issues with 2.39.20 I rolled back to 2.37.48 and disabled automatic updates.

In the Suunto app it now tells me there is an update available and it gives the version number as 2.39.34.22544.

However, I don’t find any info related to this version on any of the Suunto pages (to include this forum). Is this a fix for all the issues being reported for 2.39.20, or is it just an alias for said version?

[Dareo]

Disregard. I just saw new posts indicating that it’s a new version.

[Un Ancien Utilisateur]

Updated the S9PP and the new carousel menu is gone, so I am assuming it’s a rollback? Took quite a bit…

[Arju Ambin]

@timecode Are there any green accent color for the watch faces?

[pilleus]

@Arju-Ambin No

[Un Ancien Utilisateur]

@Arju-Ambin just the mint green.

[Arju Ambin]

@timecode seems lika a rollback to previous firmware with an increase in number of the version untill they figure out what’s causing the issue. Guess we’ll have to wait for either Suunto or the testers to confirm what the new update is about.

[Egika]

2.39.34 is for S9PP only. Mainly to fix the OHR and sleep tracking issues.
Technically it is a downgrade to v2.37.48 for the moment as the OHR issues need more time.

[Arju Ambin]

@Egika thanks for confirming. Good call by Suunto on reverting. Hopefully it won’t take long until the devs get it figured out

[MKPotts]

@Egika
Most of the discussion on here was about the OHR/sleep issue - which my watch had with 2.39.20 - but my bigger problem was the very high battery drain during activity (6-7%/hr). Some other users also reported this, though it seemed not as many as the ohr.

Do you know if Suunto are aware of this and working to fix it at the same time?

[Elipsus]

@MKPotts Yo, I also got the problem, i noticed that my backlight was always on despite telling it to turn off, I solved it by doing a hard-reset, takes around half an hour to do, and you loose a little bit of data, but that was worth it IMO

[Egika]

@MKPotts I am no aware of any high battery drain during activity, sorry. And it would be quite unusual as well. Unless backlight is constantly on, as @Elipsus suggests.

[MKPotts]

@Elipsus
Thanks. I checked the backlight settings after the problem started and it was definitely off. I do most of my running in the dark, so would notice if it was switching on despite the settings.
Rolling back to 2.37.48 firmware has fixed the issue for me, back to usual battery burn in activity. But I won’t update to any later firmware releases until I know the battery drain issue is fixed.

[MKPotts]

@Egika
Thanks for the reply Egika.

It definitely wasn’t caused by the backlight in my case - see my last post - and other people have reported the same battery drain in this thread (@jussim for example) after installing 2.39.20.

It would be really helpful if any other product testers on here could comment about Suunto’s awareness of this problem. I’ll contact support if necessary but in my case it’s clearly related to the firmware (no problem before the update or after rolling back).