Suunto 2.50.26 – Q4 2025 Release Notes

[sky-runner]

@Dimitrios-Kanellopoulos said in Suunto 2.50.26 – Q4 2025 Release Notes:

@sky-runner we made nice changes for you I think I need a seperate post from you

I need to try to repeat some of the previous runs on rolling terrain to see what difference in ascent / descent it makes. I haven’t had a chance yet.

@Dimitrios-Kanellopoulos, so I far I have tried repeating one previous run on a rolling terrain - compared to the previous firmware version both distance and total ascent ended up being exactly the same. But at least I didn’t have to raise my arm at the top of each small climb, so perhaps that is an improvement!

However I wanted to use this chance to remind about two other bugs / issues:

[1] The estimated ascent given by Suunto app for the route is pathetically wrong. Strava calculated 441 ft elevation gain when I created a route from a previous run. In Suunto app the same route’s ascent shows as 280 ft. The actual elevation gain after running it is 535 ft, so almost 2x difference.

I looked at climb guidance during the run and every single climb showed up with less ascent than actual. For example, in one case climb guidance showed a 33 ft ascent. By the end, when the ascent was replaced by a flat section in the climb guidance, I had already climbed 72 ft and in fact there was still probably another 10 ft of climbing in front of me, but the watch had already switched to a flat section. And that is what I see consistently when running on rolling terrain. All moderate ascents and descents are almost always inaccurate and fairly short of the actual elevation changes.

[2] Navigation improvements such as larger arrows are claimed at the top of the thread. I am not sure what that is supposed to mean, but one annoying bug that I’ve reported over a year ago is still present:

As you can see the light blue navigation errors are rendered behind the red breadcrumbs tracks, and in some situations that is disorienting. I’ve seen multiple cases where I am at a junction that I’ve already gone through a couple of times with two or more possible ways in the navigation route and it is nearly impossible to tell which way to go because the light blue arrow is behind and nearly invisible. I can probably find some sceenshots of this issue that I’ve made earlier.

Is the development team aware of this issue and why such an obvious issue isn’t being addressed? It would be quite reasonable to always render the light blue arrows on top.

[DrSilverthorn]

@sky-runner I too have noticed that the SA ascent numbers are very wrong. They appear to be too low.

[GiPFELKiND]

@DrSilverthorn here the ascent numbers are to high. Walking at sealevel and suunto says 222m positive Elevation, i never had this before

[Dimitrios Kanellopoulos]

@GiPFELKiND I need this file please. Did you record with the app or watch ?

[borgelkranz]

@VoiGAS Same Here

[GiPFELKiND]

@Dimitrios-Kanellopoulos with my Vertical2

[duffman19]

@DrSilverthorn said in Suunto 2.50.26 – Q4 2025 Release Notes:

@sky-runner I too have noticed that the SA ascent numbers are very wrong. They appear to be too low.

It seems that the digital elevation model Suunto is using is better in some places than others. It looks like it’s pretty accurate for users in Europe, but less so for those of us in North America. Most of the routes I’ve planned in SA have very jagged elevation profiles suggesting that there are very few elevation reference points in my area. Not exactly sure which service Suunto is using (I’m assuming they are paying a third party for the data), but it makes sense they would prioritize Europe first. Although I’m also not sure why they can’t get a globally accurate model.

[Dimitrios Kanellopoulos]

@GiPFELKiND are the stats on strava ok ?
if not there, then you got a dirty sesnor

[surfboomerang]

@Dimitrios-Kanellopoulos for reference…
I did an almost similar round of running before and after the firmware update of my SV1.
The route is totally flat except for one tunnel. This explains the small dips in the altitude graph.

Before the firmware update: ascent 0m, descent 0m

After the firmware update: ascent: 4m, descent 19m

I live 1m below sea level which was nicely recorded before the firmware update. After the firmware I ended the run with -18m

[GiPFELKiND]

@Dimitrios-Kanellopoulos same here

[jussim]

Great to see that it is now possible to select ZoneSense for indoor rowing.

And even better that now the multiple heart rate monitors (optical and traditional belts) are handled smoothly.

Not to forget that an older model such as 9PP would even receive and upgrade. Good job, Suunto.

[Dimitrios Kanellopoulos]

for any person getting too much ascent / descent on flat routes please open a new thread and post there are relevant info and files

[GiPFELKiND]

@Dimitrios-Kanellopoulos @Dimitrios-Kanellopoulos i opened a separate Post now for this.

[Sportsfreund]

@jussim Zone Sense was able to work for a long time before the last update.

[tuxbuster]

@Dimitrios-Kanellopoulos said in Suunto 2.50.26 – Q4 2025 Release Notes:

Per-sport mode persistent configuration
Each sport mode stores its own user configuration:

Intensity zones
Map color
Connected sensors
Data screens
Autolap
Custom settings such as autopause, voice feedback, etc.

I’m still missing the option to enable tones specifically for workouts. I have all system tones muted on my watch, but I’d like to have them active during training only. Unfortunately, even with the new update, this feature is still not available. That being said, I really like the new options Suunto has already brought us with this update.

[ChrisA]

I also see extremely high recovery time after the update.

Resources used to work good for me on the Race I

[Bartek W]

I was very impressed with the scope of this FW update, but less so when I discovered nothing much changed in a way my external HR sensors are handled. I tried 3 different ones (Polar H10, polar Verity Sense, Garmin HRM Pro+) and each of them fails to record any HR data points after 8-15 minutes into the exercise. I also had occasional dropouts of Stryd connection. Sometimes my Race S can re-establish it in a few seconds, but sometimes just drops it for good. I did not do hard reset, but I removed all my sensors and paired them from scratch.

On the other hand, navigation screen makes more sense now. North up setting is a useful feature. Also finally direction arrows are legible. I wouldn’t mind them being even bigger, but it is significant improvement anyway. I can see which direction I am guided at a turn without having to use a microscope. Now it’s time to do something about the font displayed between workout steps (the screen with light grey background which tells you what to do in the next step)…

It’s been only a couple of days, but sleep tracking seems to be more precise. It does not seem to have the same tendency to log sitting still on a chair as a nap.

Keep up the good work Suunto Devs!

[brechtvb]

Does anyone know or tested if the Garmin wheel and crank sensor now work?

[VoiGAS]

@brechtvb Misuro B still doesn’t deliver Speed, so I guess it will be a problem with all sensors. Still

[DrSilverthorn]

I’m having continued issues with multiple bluetooth sensors as reported by other users (e.g. @Bartek-W and myself), where the heart rate sensor is detected (Verity Sense and H10), and connected, but there is no heart rate data. I discovered another issue, which may be related and the cause of other people having bluetooth HR issues. When using either the Zonesense or Live t (live tracking app), and either the H10 or the Verity Sense, the heart rate data gets stuck at a low number (in my case 87), and does not change. Disabling the S+ app while in the activity does not solve the problem, you need to start a new activity with those apps disabled to get heart rate data. I have not checked other S+ apps. I think these two are fairly resource intensive and the bluetooth sensor thread or process is probably not getting serviced enough (speculation).

I am using a Race 1.