Software Update 2.40.38 (2025 Q1)

Jordi C

My watch, for the first time, restarted itself this evening without doing anything.

Damian Tylczyński

Since update:

sleep tracking stopped to work completely.
if I stop the workout in the first minute or two, then heartrate stops to be detected later when new workout is started. Turning off and on again help.

thanasis

@far-blue @Brad_Olwin thank you both

thailon

My Vertical went to power saving mode without any interaction from my side, even batter was 45%.

Antoine

During an activity, the GPX route I was following disappeared. I tried to select it again, but it had disappeared from my list of routes on the watch, along with others. I redownloaded the GPX route into the app, and it was resynced with the watch. I was able to select it again, and I was finally able to follow the GPX route. This is the first time I’ve observed this behavior.

Artus Diver

@Devis said in Software Update 2.40.38 (2025 Q1):

Hello,
yesteday I swam in the pool (25m) for about 60 lengths and the Race S estimated a total distance of 1500 m .

I pushed the down button to mark a lap at the end of every length (but I did it only for the first 50 lengths).
From the first, up to the 10th lap, I swam freestyle (a length) and then return in backstroke (a length), five times.

Here what the Race S tracked. I underlined what I think it is not correct.

Thanks for any comment.

I have a Suunto Vertical and swimming in the pool after the latest updates is a nightmare!
It counts the distance incorrectly, LAP after 100m shows 75m and confuses swimming styles (…) It divides 100m sections into 2x50m (…)

The new algorithm has extended the time of laps approval from 4 seconds to 10 seconds. For recreational swimming it does not matter but if someone trains, the algorithm gets lost in fast and intensive intervals!
I do not know why such changes?

I am forced to go back to swimming with Suunto 9 Baro and I have no problems, everything works perfectly!!! Why can’t stick with the old algorithm?

Dimitrios Kanellopoulos

@Artus-Diver I see the post

Dimitrios Kanellopoulos

@Devis What is the problem with the 50m red circles ?

Alastair Polden

I can no longer connect my vertical watch to WiFi. It was previously working. Steps I have taken to rectify:
Disabled 5ghz WiFi
Restarted router
Restarted watch
Restarted phone

The last step to try is a hard reset of the watch but if I’m unable to reconnect to WiFi, I will have lost the downloaded maps i currently have on the watch.

Software 2.40.38
Model 0w222
Hardware 3211e2
PPG 0.4.65
Wlan v000052

runomatic

Bug or feature (to save battery)? The widgets of the Vertcial’s standard watchface (in my case “Ressources” and “Solar”) no longer update automatically. Only when I press the middle button does the value adjust.

Jan Suchánek

@timecode Thanks! I was thinking about that. So it only shows the zone. In this case, it could be smaller, just show color and left space for another complication… But I can live with that for sure :-).

fedequei

@Jan-Suchánek I have the same problem

Matthias Jäggli

@pavel-samokha And everytime something updates. it resets the watch face and it’s colors and complications. PLEASE leave this alone, it’s so annoying

pilleus

Air pressure complication doesn’t change the horizontal arrow despite of increasing air pressure (1014 to 1024 hPa within 12 hours).

On Vertical and 9PP with the choosen watchface.

sartoric

@pilleus
baro trend shows 2 X 3 hours timeframes and there should be a threshold I don’t remember at the moment.

It works ok on my Vertical

runomatic

@pilleus That is the same bug as mine, i suppose. (2 posts above yours)

pilleus

@sartoric said in Software Update 2.40.38 (2025 Q1):

@pilleus
baro trend shows 2 X 3 hours timeframes and there should be a threshold I don’t remember at the moment.

It works ok on my Vertical

No change since the update. Always the ️ arrow despite the steady increase from 1014 to 1024 hPa within 12 hours. There should be a arrow showing ️

Inge Nallsson

@Dimitrios-Kanellopoulos said in Software Update 2.40.38 (2025 Q1):

@Devis What is the problem with the 50m red circles

I believe the confusion comes from an issue I layed out in the posting https://forum.suunto.com/post/164067 (Several swim issues and questions). Whether being, as @Artus-Diver calls it, a ‘recreational’ swimmer or doing more of a ‘training’ session we users expect that pressing the supposed ‘Lap’ button will mark the distance since a previous button press AND give the exact timing between the presses.

But, as I showed in the linked posting, the ‘Lap’ button does (probably) not effect the timing at all and is just a means of summarising the automatic “Interval” counting the watch does by itself. It is thus very likely that a ‘recreational’ swimmer (pushing the ‘Lap’ button for every length *) will experience 0 metres lengths or, as in this case, 50 metres while expecting 25 because the the automatic counting easily is disturbed by slowing down or faffing with the watch or less than stellar push-offs. Remember, a ‘Lap’ button press is in no way decoupled from the automatic “Interval” counting.

Many ‘recreational’ swimmers count lengths instead of metres and therefore rely on the ‘Lap’ button doing the logical thing, i.e. in a 25m pool mark 1 length and that being 25 metres. The concept of automatic “Interval” counting (of varying lengths) is for them profoundly alien.

pilleus

@pilleus said in Software Update 2.40.38 (2025 Q1):

@sartoric said in Software Update 2.40.38 (2025 Q1):

@pilleus
baro trend shows 2 X 3 hours timeframes and there should be a threshold I don’t remember at the moment.

It works ok on my Vertical

No change since the update. Always the ️ arrow despite the steady increase from 1014 to 1024 hPa within 12 hours. There should be a arrow showing ️

Now the air pressure is falling, the value in the complication is correct, the little arrow above is still ️.

I tried different watchfaces, no difference. Both watches, Vertical and 9PP have been resetted to factory settings after the update.

Artus Diver

@Inge-Nallsson said in Software Update 2.40.38 (2025 Q1):

@Dimitrios-Kanellopoulos said in Software Update 2.40.38 (2025 Q1):

@Devis What is the problem with the 50m red circles

I believe the confusion comes from an issue I layed out in the posting https://forum.suunto.com/post/164067 (Several swim issues and questions). Whether being, as @Artus-Diver calls it, a ‘recreational’ swimmer or doing more of a ‘training’ session we users expect that pressing the supposed ‘Lap’ button will mark the distance since a previous button press AND give the exact timing between the presses.

But, as I showed in the linked posting, the ‘Lap’ button does (probably) not effect the timing at all and is just a means of summarising the automatic “Interval” counting the watch does by itself. It is thus very likely that a ‘recreational’ swimmer (pushing the ‘Lap’ button for every length *) will experience 0 metres lengths or, as in this case, 50 metres while expecting 25 because the the automatic counting easily is disturbed by slowing down or faffing with the watch or less than stellar push-offs. Remember, a ‘Lap’ button press is in no way decoupled from the automatic “Interval” counting.

Many ‘recreational’ swimmers count lengths instead of metres and therefore rely on the ‘Lap’ button doing the logical thing, i.e. in a 25m pool mark 1 length and that being 25 metres. The concept of automatic “Interval” counting (of varying lengths) is for them profoundly alien.

Good morning,
I hope I haven’t offended anyone with the term “recreational swimming”, if so that was not my intention, I apologize.
Of course I practice sports swimming but I often use other swimming techniques and the LAP button to mark laps, e.g. for exercises without hands.

By the way.

@Dimitrios-Kanellopoulos even when LAP works it still doesn’t give the length and it was already implemented in the Suunto AMBIT 3 PEAK model!!!

I don’t understand what the problem is to restore such functionality?

@Dimitrios-Kanellopoulos I’ve been using your products since 2001 (I swim, dive) and I don’t remember such a mess with the swimming algorithm!

(SA3PEAK, S9B, SV until update 2.39.20 later it’s despair).

Yesterday I sent the SV to the service because maybe it’s a watch defect? I’m curious about the service opinion.

Back to the topic.
I proposed dividing it into two disciplines only because the current algorithm does not satisfy either competitive or recreational swimmers.