Software Update 2.43.8/.12 (2025 Q2)

pomah86

Any info on why the 9PP is not getting the update?

thanasis

Coming back to the altitude measurements issue

leaving the watch idle , it should NOT change either altitude nor the barometric pressure … at the moment a storm (which should have triggered the alarm ) changed both the altitude measurement and the barometric pressure , but that way both indicators were somehow wrong

VoiGAS

@danct As far as I read it there are only fields for the time in the different zones - but not the zone you are currently in itself. But didn’t try it

far-blue

@isazi FYI I had the same power display dropouts on my long run yesterday. This appears to be pretty consistent new behaviour I’m getting every run.

maszop

@thanasis This is the Suunto automation that replaced the manual Altimeter/Barometer mode switch found in older watches. Which, despite what people associated with Suunto have written here many times, works poorly.

isazi

@far-blue okay send me the activity, I’m collecting some examples

atoponce

@isazi Here’s a run where I saw consistent power drops on my Race S despite only stopping twice at intersections. This was an easy run.

https://maps.suunto.com/move/aarontoponce/685548cd0767c11a0a1196a9

I dare say half the time I’m looking at my watch while in full run, the power from my Stryd foot pod either reads 0 or just coming up from 0. Because I use 30s avg for my data field, it takes a bit to climb back up.

Bogdan1921

Voice feedback it’s not working. Two running exercises and no voice in my case.

atoponce

@far-blue I decided to downgrade. I’ve got the Chicago Marathon coming up and I train by power. I don’t want to be second-guessing my power reading or babysitting the watch during my workouts.

Settings > General > About > scroll to bottom > hold bottom button a few seconds > secret menu appears > Select OTA pkg.

I had a few installed, and selected the .8 release.

nseslija

@far-blue Same thing, on every cycling activity with power…

nseslija

@isazi https://maps.suunto.com/move/nseslija/6857cc0801be5718e3eb669a

Stefano M64

I met a problem with the maps (Lofoten, Norway), by zooming out some details disappear…

Brad_Olwin

@sky-runner Agree with you here, need to see trails and roads at low zoom levels ideally up to 5 km.

far-blue

@isazi I had another longer run today and tried to pay some attention to the dropouts. I think they may be related to where GPS might struggle a little more - under tree cover or underpasses etc.

Also, I suspect it’s actually all bluetooth because I’ve noticed random single RR values in Runalyze that are also very far out from the usually very clean datasets I get.

GiPFELKiND

@Stefano-M64 downgrade to 2.37.48 its since many updates the BEST Firmware and stable without Crash. With every new Update Problems like yours comes to the watch. Why upgrade when the system is running without Problems.

Pavlas

Has anything changed for Open Water Swimming? I noticed that the measurements are very inaccurate. Last year the watch read very well. My brother has an Ocean and it still reads well. So any change in one of this year’s firmware? Has anyone had a similar experience?
I still swim the same way - I try to keep my watch above the water a lot

Egika

@Pavlas no change here.
I have quite some recent activities with very good results. Same my partner:
https://forum.suunto.com/topic/13173/tracking-open-water-swim-with-race-s/2?_=1750662933845
It comes down to the same questions: Have you updated AGPS and given the watch some minutes in the pre-start screen to establish a good set of active satellites? A regular amateur freestyle swimming style should be sufficient.

Pavlas

@Egika Thank you. I’ll try to wait longer. But my process is still the same. I’ll wait for the GPS signal and get in the water. I know it’s better to wait a while. But I didn’t have any problems last year. I swim breaststroke.

Egika

@Pavlas then you have had exceptionally good luck in the past.

Technically the following is happening with GNSS reception:

The satellites continuously send out their position data and time stamps. The watch (with an incredibly small antenna to actually receive signals from space) tries to lock on those transmissions. It uses assumptions, where the satellites should be and which satellites to look for (from the AGPS data updates daily). Still those assumptions are just the starting point, and subsequently one after the other satellite is taken into the equation to calculate the current position. The data rate is pretty slow and the receiver needs to read the time stamps, the satellites are sending.
Position fix is possible, when a connection to 4 or 5 satellites is established. This is, when the arrow in the watch becomes green. Still, if the connection to one or more satellites is broken, the position fix will be dropped. This can easily happen if the satellite is just above the horizon, or if you move the watch antenna away facing a different direction. Thus it is crucial, that the watch is able to follow the transmissions of as many satellites as possible.
For outdoor activities usually the watch can still lock on more data streams while the activity has already started.

In the water, there is no GPS reception, as the satellite signals don’t penetrate water. This means, that the watch only has fractions of a second, to read data from the (badly positioned) antenna that has super weak signals to acquire from satellites far away in space, before it is submerged again.

You can help the process by waiting after the green arrow comes on. Green arrow means, the watch uses at least 4 satellites. Waiting longer ensures, that more satellites are added into the equation. If some are lost later, others can be used. 2-3 minutes is a good starting point.

Plus you need to bring the watch above the water level periodically for it to continue calculation your position. Breast stroke is not really suitable for this.

Conclusion: If you had good results in the past with not much waiting and swimming breaststroke, it is almost a miracle.