Software Update 2.40.38 (2025 Q1)

[The_77]

Just to report a bug that was in the last version too. Last Saturday I was following a long route with many waypoints. The behaviour I expected is that I would see the normal tooth in all but the navigation screen, except when within 50m. This worked for maybe the first two hours.

After two hours or so, the distance to waypoint then permanently took over the the bottom tooth on every screen, meaning obviously I lost a data field on every screen. Mildly frustrating.

A separate bug I encountered this week was as I stopped a run, a notification interrupted the ending screens, and made it impossible to click end (or any option). A short hold of the middle button to return to activity, followed by ending it again solved the issue.

[The_77]

Separate bug today, think it has been reported before.

When using autopause and following a route, when cycling I prefer having the 250m size, rather than 100m. Naturally when I stop at the lights, the autopause resets the zoom to 100m every single time. In the city, this is a proper pain.

[Łukasz Szmigiel]

@The_77 it’s with us since Suunto 5 I think I’ve reported it as well and @isazi filled a bug report last year I think

[The_77]

@Łukasz-Szmigiel I thought I’d seen you report it. How unfortunate.

[sky-runner]

@The_77 said in Software Update 2.40.38 (2025 Q1):

After two hours or so, the distance to waypoint then permanently took over the the bottom tooth on every screen, meaning obviously I lost a data field on every screen. Mildly frustrating.

This seems very similar to what I have experienced during my last race too. I did a separate post about that. I’ve noticed the notification at the bottom too but forgot to mention that in my post. I suspect that might have been triggered by going off the route temporarily and possibly by the route being temporary reversed.

[SuperFlo75]

After about a month with the current software, I realize that my SV is working without any problems that I can see. In particular, the battery consumption is as good as it was at the beginning. Good job, Suunto!

[Jordi C]

After about 15 days without issues, this morning my SR got “hung” again synchronizing the activities with the phone.

After restarting the watch and the phone, the problem has been solved.

[Миша Пономарев]

Расскажу о проблеме с которой столкнулся.
У меня Peak Pro 9 с последним обновлением 2.40.38.
Решил я покататься на горных лыжах, включил соответствующий режим, дождался сигнала о готовности GPS и поехал. После нескольких спусков, посмотрел на дисплей, а на он показывает по всем параметрам ноль, то есть как будто не было никакой активности. Проблема решалась только перезагрузкой часов.
Что интересно, после синхронизации с телефоном, тренировка в которой на часах были нули, отобразилась со всеми параметрами (расстояние, скорость, перепады).
Кто-нибудь сталкивался с подобным багом?

[Tieutieu]

@SuperFlo75 Same here…except the “wind effect on elevation calculation”…It’s still there, mostly experimented on my bike.
I don’t remember having had such obivous effects with previous FW.
As example : SV on my wrist this morning. 80m of elevation on the 10km final descent (and it’s pure descent).

[SuperFlo75]

@Tieutieu Ok, I never noticed this behavior… I did a trail run some days ago when we had heavy wind… and the elevation was similar to another run before when we had calm weather…

[larrybbaker]

Not sure if it’s just me… but since this last update my watch sets off the storm alert every morning @ 0700-0715 EST. With no indication of any weather in the area…

[duffman19]

I noticed that the touch screen activates when the alarm (alarm clock) goes off. This allows you to tap either “Snooze” or “Dismiss,” but also means you could accidentally press either of these while fumbling to turn it off. I use my watch as a morning alarm (set to vibrate). On several occasions I have accidentally dismissed the alarm due to an accidental touch. I believe I’ve read that several others have had issues with the alarm. Perhaps they are also dismissing them due to accidental touches.

Interestingly, once you dismiss an alarm, the touch screen is no longer activated. So the watch isn’t “unlocked” as it would be if you pressed a button. I think the expected and safer behavior would be to require a button push to dismiss an alarm.

[ScottBH7]

+1 to this request - for alarms making the top button ‘Snooze’ and the bottom bottom ‘Dismiss’ (kinda the same as a workout in that sense - Continue top and End bottom) should provide for a much better user experience and virtually eliminate false alarm dismissal.