Suunto 2.50.26 – Q4 2025 Release Notes
-
@Matúš Sorry I didn’t see your discussion above. Indeed this seems to be the same bug. I’m quite certain the trigger is starting an activity. Are you able to reproduce it?
@Dimitrios-Kanellopoulos @pavel.samokha Any news whether Suunto is aware of this?
I saw a few complaints of rapid battery drain on other forums, up to 70% over 24 hours, mainly 9PP users. I’d be willing to bet this is due to an inadvertently activated backlight.
-
Another wird behaviour since update, observed with both my SV and SRs : in watch mode, I notice while driving my car in moutains/hill terrain, with quick elevation changes, the altimeter is not immediatly responding and altitude is often “stuck” to the value of start of the climb for instance (first I thought that it may have been related to watchface, but I use different ones on each watch, and while going in to the barometer wigdet, the behaviour was the same). It takes few second/minutes so altitude starts updating and it is obviously less reactive than before.
Have you noticed the same ? -
@Tieutieu said in Suunto 2.50.26 – Q4 2025 Release Notes:
Another wird behaviour since update, observed with both my SV and SRs : in watch mode, I notice while driving my car in moutains/hill terrain, with quick elevation changes, the altimeter is not immediatly responding and altitude is often “stuck” to the value of start of the climb for instance (first I thought that it may have been related to watchface, but I use different ones on each watch, and while going in to the barometer wigdet, the behaviour was the same). It takes few second/minutes so altitude starts updating and it is obviously less reactive than before.
Have you noticed the same ?Yes, I have noticed this. It is also happening in a plane that is climbing from takeoff to cruising altitude. It is an effect during daily mode, not in activity recording.
It is known to Suunto and checked again.During activity, the altitude change filter is adaptive: für alpine skiing with quick elevation changes, the altitude is updated instantly. During hiking there is a filter in place that only allows slower altitude changes.
-
@duffman19, I confirm you that the trigger is the activity starting, actually, the activity starting screen (where are listed the activity settings). Triggered the bug by scrolling the settings, the raise to wake starts to “work”; later, by leaving that page, the back light stays on no matter what until a setting related to the screen in manually triggered.
I reproduced the bug two days straight: the triggering behaviour and the consequences were always the same.
-
After the update the sleep tracking continues to work well but the morning report disappeared. How do I bring it back?
-
@Highlands, try throubleshooting as described in this thread (read all the messages, not just the short three point guide).
https://forum.suunto.com/topic/14406/sleep-widget-not-working-properly-on-vertical-2
-
With previous firmwares I had a problem of altitude drifting in watch mode. Altitude would slowly go up during a day by 30-80 m. In activity, altitude was spot on. But after updating my Race 1 with this FW, the altitude is now drifting down in watch mode. I guess they did something with the fusedalti algorithm, but it needs some more fine-tuning.
-
During the hike I had the past Sunday there was a LOT of wind, nevertheless my Race recorded no odd altitude spikes, giving correct total ascent/descent values, in line with the ones I got with the app (Oruxmaps) on my smartphone. So it seems the new “SMART” barometric algorithm is actually doing what it is supposed to do
-
@Stefano-M64 Thanks for the info. Great news. I still haven’t had a good chance to test it out
-
Serious bug not being able to see manual laps in the app from activities after the last update. Still able to see them in my race s after the sessions but not in the app. Hope they solve this quick since it’s a very important function.
-
@elis001 it’s a bug in Suunto App. it’s fixed in version 3.7.1 (at least on iOS)
