Software Update 2.44.52 (2025 Q3 - HOTFIX)

[GiPFELKiND]

@Jacobus said in Software Update 2.44.52 (2025 Q3 - HOTFIX):

When you press the i sign next to your heart rate, you see the zones and the measured threshold, this looks a bit strange after the hotfix.

Suunto, whyyyyyyy the Problem is all people who didnt know how to Software downgrade have to life with this until a next Update will solve this onee… Merry Christmas hope suunto will solve this in the next few hours! Make the following new watch release LATER and first SOLVE ALL PROBLEMS.

[santler]

@safari same here

[Dušan Ković]

Watch updated over night, although I disabled automatic updates…

[OutdoorMan]

I was wondering why there’s nothing for the Race 2 and noticed it is on 2.46.4, which is higher.

[pilleus]

@borgelkranz

For bike sensors which have two ble protocols the Vertical and now after the update of the 9PP both watches are useless. The Fazua bike sensor broadcasts CPS (power and cadence) AND CSCS (speed and cadence). Only CSCS is picked up by the watches and the sensor is paired as speed sensor, not as power sensor.

Because there is no possibility to choose the CPS protocol the power data are unavailable from now on.

It’s frustrating, very frustrating. ️

[fv4500]

@Dušan-Ković yes, very frustrating… it’s been several versions of firmware and software like this. No doubt that’s intentional.

[jakubdr]

On my SV the constant disconnects and reconnects of my HR Arm bands disappeared and it is working as expected.

What seems to be broken still is the activity tag in Suunto App. Before this hot fix everything was as VO2Max, now it still takes pace zones as a basis despite switching to TSS (hr) and marks my runs as anaerobic because of some made up pace zones. What I would like is to have a switch back to HR zones because my pace zones vary a lot (especially in trail running).

[Kenneth De Cocker]

@VoiGAS This! But then again for my training a few weeks ago in the Mullerthal area it didn’t crash and during my 100k is also didn’t crash, but it was still a worry of mine …

[pilleus]

How can I downgrade to a firmware I have stored as sof-file on my smartphone? Suunto app doesn’t open it because of the message that it is damaged or an unknown file type.

I want to downgrade two versions before the actual firmware, the pkg is not stored in the service menu of the Vertical.

[KingK0ng]

@OutdoorMan lol, here i am hoping for a fix for my race 2. Horrible sleep tracking, completly off, data disprecency (29% recovery watch , 91 on app), resource Never goes below 90%, sleep is also 79% score, deep sleep is 2-3 hours even with 4-5 hours sleep :D)

God im regretting not returning it.

[Jan Suchánek]

@brechtvb I have them, will try it and let you know.

[borgelkranz]

@pilleus I feel you. For me it is obvious that the possibility what to pair has to return. Until then I stay on the older version.

[safari]

@KingK0ng
I wake up to a notification while sleeping at night. It says “You’ve been sitting for two hours, get up.”

[enriqueescoms]

@fv4500 Please, for 9PP, can you check if has been fixed the touchscreen bug on the navigation screen. Because if it’s not fixed, it’s impossible to go back one screen at a time (with the touchscreen because of the bug, and with buttons because of the function layout).

[OutdoorMan]

@KingK0ng I still have a few days to return it, and I am going to do it. I rather stick with my almost dead 9 Baro. I wanted a modern watch, but the more it can do, the more issues you gonna have I guess.

[duffman19]

@enriqueescoms Nope, still not fixed. No changes to the 9PP navigation issues.

[enriqueescoms]

@duffman19 Bufff…incredible

[fv4500]

Hi @enriqueescoms, so tested it with a very standard hiking activity with one SA+ app enabled. Indeed, as @duffman19 says, you cannot long-press the middle button to go back one screen because this actually triggers the zoom in/out options. Only way out is to the right.
I also noticed that the touch screen was completely unresponsive (first time I notice that because I literally never touch the screen, just use the fantasic clicky buttons of the 9PP), but that was because of the battery profile set to “performance” which by default disables the touch screen.
I re-tested the hiking activity with a “custom” battery profile with touch enabled, and indeed the screen is totally unresponsive, but in the map view only – you have to use the middle button to get out of that screen. In the other screens, touch control works well.
While this does not affect me at all, indeed it seems that the touch control should be available in the maps screen if touch is enabled, isn’t it? For me, the behaviour with buttons seems “as per the design” because the long-press triggers the zoom controls, I don’t see what else designers can do here.

[Stefan Kersting]

@fondueaufromage have the same issue too

[brechtvb]

@GiPFELKiND last one shuts the light