Suunto 2.50.26 – Q4 2025 Release Notes

thanasis

@Dimitrios-Kanellopoulos coming back to the battery drain issue.
This is the second full charge cycle I am running (so not yet a full 2 cycle calibration) .

It seems the drain is there in my case - although I shall wait for the second cycle iteration. Unless I have faulty device (which is something I need to assess btw), I get 5% drain on activity without GPS (Indoor Tennis for instance) with a HR belt connected and like 5% on a 1hour run with GPS and HR Belt . This is exceptionally high compared to where it was like 6 months ago (with previous firmwares) . Resetting the device after the activity seems to stabilize the drain percentage to another 5% for the rest of the day if worn on the wrist.

I will continue reporting on that

Dimitrios Kanellopoulos

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

although I shall wait for the second cycle iteration

why would you need to wait ?

Its I think very difficult to conduct the test you are doing with so close buckets. Meaning is its 5.2% to 4,4% ? etc.

Also I see you are trying to test battery life with so small activites that eventually have the overhead of ie connecting to sensors etc.

Not really sure why you have to bother so much to be honest and without being disrespectful but I have the strong feeling that:

Either your v1 is getting old ?
Either we are all ghosted by battery life issues.

I could say easily: Continue the tests , but on a personal note, I ll say just let it rest man and enjoy your trainings.

NOTE: we did have a battery “kinda” drain but that was on time mode it was minor and it was on first connect of the sensor. This is how the whole story began I think, or am I wrong?

Also if there is a really battery life issue we will kinda find out sooner or later.

thanasis

@Dimitrios-Kanellopoulos thanks . Indeed . I need to forget about it

btw: those are not the only the excercises I did ,or measured . I just wanted to indicate the indoor tennis (no gps) and outdoor running (gps + map etc) did drain a similar (as seen on the watch) battery percentage

duffman19

@Dimitrios-Kanellopoulos There will be significant battery drain if the backlight stays on after starting an activity, as has been reported by a number of us.

@thanasis Perhaps this is also the cause of your observed behavior?

Bigb0zz

Suunto Vertical 2 - System crash during workout . (Latest FW)

Dimitrios Kanellopoulos

@thanasis well not completely. Let’s let a little time pass. I’ll prepare Also some tools

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.