Suunto 2.50.26 – Q4 2025 Release Notes

atoponce

@Zdeněk-Hruška This has been a long-standing bug with Suunto watches. If GPS is locked, the watch will source pace and distance from GPS, not from Stryd. If GPS is not locked, such as running on the treadmill, then Suunto will use Stryd for pace and distance.

I’ve raised bug this with Suunto support a few times, so hopefully it gets fixed.

Dimitrios Kanellopoulos

@atoponce nope I don’t think it works like so.

atoponce

@Dimitrios-Kanellopoulos That’s what I’ve observed. Here is a recent outdoor 5K race with the Stryd Next Gen pod paired to my Race S. The paces differ:

Here is a treadmill workout. The paces perfectly agree:

This is reproducible on every run I do outdoors versus indoor. When GPS is locked, the paces with Stryd disagrees. When GPS is not locked, the paces are in agreement.

atoponce

This is a 5K race that alerted me to the problem. Suunto reported the distance as 5.19 km when the the course was actually short at 4.63 km, which Stryd correctly calculated. Note that Suunto’s pace is consistently higher than Stryd’s, and thus for the duration, resulted in a longer distance.

Dimitrios Kanellopoulos

@atoponce afaik you should turn off auto calibration but this was long time ago for me with stryd. I’ll ask internally

Zdeněk Hruška

@Dimitrios-Kanellopoulos that doesn’t work unfortunately. I have all Stryd data turned on and calibration turned off and if I am lucky I will get a power from the pod. But the pace is always from the watch (I tested with different settings and hand movements). Maybe I am wrong but it seems like that’s really the case and it shouldn’t be.

atoponce

@Dimitrios-Kanellopoulos Thanks for raising this internally. Auto-calibration is disabled, but auto-calibration is a new feature with the release of this firmware. I’ve checked several runs going back to January 2025 when I purchased the watch. This bug has been present since at least that point.

Mi bueri

Hello,

I had the following problem today (similar to 3 months ago):
31% battery in the morning
30% training start trail running: battery mode endurance
19% at training stop after 3:42 h (!6.30h)
Door unlocked, toilet, alarm 9% (16.35h)
1% 16.45h
Battery usage since the last full charge:

Jan 11: 100%, 12.30h
Jan 11: 95%, 3.25 h training (endurance mode) 16.30h
Jan 12: 92%, 10h
Jan 12: 86%, 3h training (endurance mode) 16.30h
Jan 13: 84% 10.15h
Jan 13: 77% 3.5 h training (endurance mode) 17.15h
Jan 14: 74% 11h (no training)
Jan 15: 68% 10h
Jan 15: 60% 3h training (endurance mode) 17h
Jan 16: 50% 10h
Jan 16: 40% 3.5 h training (endurance mode) 17h
Jan 17: 31% 10h
Jan 17: 19% 3.75 h training (endurance mode) 16.30h
Jan 17: 1% 16.45h

Until Jan 15 everything was great, then a 10% drop overnight is not good, and going from 19% to 1% in 15 minutes is unacceptable. I normally charge the watch once a week at about 20%, I bought it in October 2023. I had this jump from 19% or 18% to 1% about 3-4 weeks ago as well, but without any training beforehand.

What is going on? Ideas?

Dimitrios Kanellopoulos

@atoponce auto calibration was there before as well. Back when I was using stryd I vaguely remember this setting. I’ll get back to you guys about this.

Zdeněk Hruška

@Dimitrios-Kanellopoulos thank you very much. I think there are more threads regarding the Stryd not working properly with Suunto in this forum as well as on Reddit for example (especially about pace and distance not coming from the pod). I haven’t used Stryd for a few years. I remember that it worked flawlessly before. There are definitely some issues now. And it seems to be the case that on the treadmill it works as it should while on the gps profiles watch seems to prefer gps data. At least from my experience and testing.
Thanks for all the help!
Edit: Also there was a pairing issue with the new 5.0 Stryd but that one had been sorted out by the Stryd update.

herlas

@Dimitrios-Kanellopoulos toggle for auto calibration was there the whole time as you said, but it did dissappear at least for Stryd when we got the first firmware version that introduced ability to pair multiple sensors of same type.
Then we just got it back on latest 2.50.26 firmware

Squirrel

@Zdeněk-Hruška said in Suunto 2.50.26 – Q4 2025 Release Notes:

Also there was a pairing issue with the new 5.0 Stryd but that one had been sorted out by the Stryd update

Thanks for the info.

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

but it did dissappear at least for Stryd when we got the first firmware version that introduced ability to pair multiple sensors of same type

Right, disappeared due to Q3 2025 update bug.

pilleus

Fazua Evation power meter not connectable any more.

With the firmware before this one it was connected with CSCS protocol but without transferring data. And now there is only the name “Fazua Evation” and nothing else. No connection, just the result of the scan process.

On my Spartan Ultra everything is working, I can choose between speed/cadence (CSCS) and piwer/cadence (CPS).

With firmware 2.44.48 everything was fine with 9PP and Vertical. Afterwards no pleasure and just frustration. ️

It cannot be so difficult to implement the both protocols, because it was working before the change of Suunto’s bluetooth stack to several connectable ble devices.

Maybe the programmer from back then can help. 🧐

borgelkranz

@pilleus the same problem with the Fazua Ride 60. Very frustrating indeed.

maszop

Another software update without fix.
Suunto’s priorities are looking really bad.

https://forum.suunto.com/post/183759

Dimitrios Kanellopoulos

@Zdeněk-Hruška My understanding is when stryd is paired as a footpod via Settings - Connectivity, watch uses Stryd distance. And if the calibration is enabled, Stryd distance coefficient can be calibrated by watch GPS distance.

When stryd is not paired as a footpod, it can be connected via S+ Sports App Stryd, in this case, distance is from watch GPS.

Could you test ? Sorry to ask this like this but sold my stryd. And this is kinda the official info. If that doesn’t work, I’ll prio this, we also have a big issue with stryd 5 afaik so let’s batch those 2 if needed.

Good morning and have a great week.

vietpq

I’m using Suunto Race S with firmware 2.50.26 (Q4 2025) and I’m having serious doubts about sleep tracking accuracy.

Examples:

Night sleep:
I was in bed from 19:11, awake and actively using my phone until ~20:00, but the watch still detected sleep starting at 19:11.
Nap:
I napped from 12:41–13:05, then stayed in bed using my phone until 14:28.
The watch recorded continuous sleep from 12:41–14:28, even though I was clearly awake for over an hour.

It seems the algorithm relies too much on inactivity and lying position, and cannot distinguish between real sleep vs. lying still while awake (phone usage).

As someone who relies on sleep data for training and recovery, this makes the sleep metrics hard to trust.

safari

In my tests, I found that many issues have been fixed.
However, two things have gotten worse.

Sleep tracking: I wake up at 6 AM, walk 3 km in the campsite. The watch was active. Then I came to my tent. My alarm, which I set for 7 AM, went off. I stopped the alarm, and it said “Good morning.” It doesn’t realize I’m awake unless I physically touch the watch. Functions like step counting and location don’t contribute. 2. Increased battery consumption. I think, partly due to the added features, my battery life has dropped to 6 days with daily use.

These are my observations for now.

Zdeněk Hruška

@Dimitrios-Kanellopoulos thanks for the explanation. I understand the intended behavior and I have tested exactly this setup multiple times.

Unfortunately, my real-world experience is different:
• When using GPS activity profiles, the watch still seems to prefer GPS-derived pace and distance, even when Stryd is paired as a footpod and enabled (autocalibration off).
• This is very noticeable right after activity start:
I can clearly see pace reacting to wrist movement, even though Stryd is connected and active. That strongly suggests pace is coming from the watch, not from the pod.
• On the treadmill, everything works exactly as expected — pace, distance, and power all come from Stryd consistently.

I also regularly experience what looks like a silent connection degradation:
• Stryd appears connected and active
• But during the activity, power is not taken from Stryd
• Example from today:
In Suunto App I see avg power 202 W, while in Stryd PowerCenter (after offline sync) the same run shows 223 W
• The only workaround seems to be:
Forget Stryd → re-pair before the run
Even then, I get power only, while pace/distance still come from GPS.

Another odd thing:
• Autocalibration can only be enabled/disabled immediately after pairing.
• When I later go to Paired Devices, the option is no longer available — I can only see battery status, etc.
This doesn’t feel like intended behavior.

At the moment, the only reliable workaround seems to be using the SuuntoPlus Stryd app, but that comes with limitations (missing other native data fields).

So overall:
• Treadmill = works perfectly
• GPS activities = inconsistent data source selection + connection instability

I agree this probably deserves a deeper look. It is a little bit tricky to test so I may be wrong with some of those use cases. That comes only from my own testing. However I’ve seen very similar reports here on the forum and on Reddit, so I don’t think this is an isolated case or user error. But still might be

Happy to test further if needed and provide logs or comparisons.

Thanks for taking this seriously

Dimitrios Kanellopoulos

@Zdeněk-Hruška I got asked

Two simple tests? Alternatively, anyone with a Stryd can help verify this.
Test setup (outdoor activity, GNSS fixed, Stryd paired as footpod):
1… Watch on the ground, Stryd on the shoe
Start the activity and leave the watch stationary on the ground. Wear the Stryd on a shoe and run around the watch.
Expected result: distance should continue to increase.
2… Stryd on the ground, watch on the wrist
Start the activity and leave the Stryd stationary on the ground. Wear the watch and run around the Stryd.
Expected result: distance should not increase.