Software Update 2.43.8/.12 (2025 Q2)

Matúš

@Janne-Leppamaki said in Software Update 2.43.8/.12 (2025 Q2):

I updated my S9PP 3 days ago. 2 nights went ok, but last night heartrate measurement has stopped at 0:36 and doesn’t blink anymore. HRM came back with disabling and enabling it from settings.

So, the old problem is back with this FW version. I just sent the logs also.

@Matúš said in Software Update 2.43.8/.12 (2025 Q2):

@Janne-Leppamaki, don’t say it…

Well, here we are again (and again)! I’ve updated the watch to this firmware last Saturday and last night, guess what?, the heartrate measurement has stopped.

I’ve bought the watch two years ago and the two main problems have always been the battery consumption and the heartrate measurement stopping: with the last updates, the first issue (for me) was (more o less) solved, but the second one, from time to time, comes around… Come on! How is it possible that a firmware update related to an outdoor track running mode and lots of data fields is able to retrigger the heartrate measurement stop?

IMHO, it’s a shame. As some like to write on this forum, these watches are outdoor watches, not smartwatches, ok, but the OHR measurement is an original feature of the watch, not a secondary feature added later on (some like to write on this forum that you have to buy the watch as it is, not as it could be in the future with possible updates): so, how is it possible that after three years of watch release, the OHR measurement software can be still influenced so easily with every update?

Frustration aside, I’ve downgraded the watch to 2.40.44.

Milan Šádek

@Matúš You are far more lucky than me if FW downgrade works for you. My SV got bricked first days of my holidays. It only keeps turning the backlight on and off, there is no response to a long press of the upper or upper + middle buttons. When the middle button is pressed, there usually is the service mode 12 sec screen, however it doesnt work at all. I had to send the watch to a service center. My next holiday is coming in the following week so this time it is me who has pulled the shortest straw…

herlas

@atoponce besides power drops on the watch showing 0s, since last couple is updates, are you seeing differences between avg watts SA vs Stryd app for both total & lap avgs ? Like a huge difference say up to 4 or 8 watts? I’ve sold my Stryd begging this year but I’ve heard folks in the telegram group report this and Stryd is saying not their issue. Just wondering thanks.

Ecki D.

Uuhh not again that 9pp bug I just started creating sport modes with zone sense display to get space for ohter s+ apps.
Up to now my 9PP still works as usuall updated it asap after it came out.
Had to restart twice to get GPS working an had to re-change a loads of sport modes where autostop and laps where set back to default.

So this sounds to me like it is not yet clear what the HR-Sensor problem is caused by and the last fix was just some kind of rollback in some parts.
And maybe there is no such thing as regression until now.

Anyway, is there some kind of “current zonesens zone” Value? Like the bar in the S+ Zonesense App? Or do I have to figure out which of the 3 Zone Timers is currently counting up?

Stefano M64

@pavel.samokha said in Software Update 2.43.8/.12 (2025 Q2):

GNSS optimization happens over wireless network automatically every night

do we know the time when this occurs? midnight?

isazi

@Stefano-M64 around midnight, yes (as far as I know)

isazi

@herlas power drops should be fixed in testing already, thanks everyone for reporting it

herlas

@isazi thanks, do you mean these power drops are more than a visualization issue on the watch and do contribute to lower avg wattage in laps and overall activity when comparing to Stryd app side?

isazi

@herlas I do not know, only heard there is a fix for that in latest testing firmware. Maybe it is just a visual bug

atoponce

@herlas Yes. Just this morning actually. I ran 3×9:15 at near-CP. Due to the frequent 0 drops on my watch, the lap table watch display on my Race S while in the run showed that I averaged 309, 309, and 308 W for those intervals. However, the data recorded in the FIT file shows the actual averages are 316, 316, and 315 W.

atoponce

@isazi If you need a beta tester, let me know.

Antoine

@isazi said in Software Update 2.43.8/.12 (2025 Q2):

@herlas I do not know, only heard there is a fix for that in latest testing firmware. Maybe it is just a visual bug

So a hotfix is coming ?

herlas

@atoponce what about Stryd side, what values ddi you get for those?

sryke

Another data point for issues with Stryd: Race S and Stryd since about the last software update (.12)

Stryd is connected as foot pod
Power field clearly underreports wattage
frequent power drop outs/zeros during a run
power in Stryd’s app looks very different (and in line with how values were before the update)

I did a mountain run yesterday, avg power for the ~40min uphill section: Stryd power 255 W, Race S reported power 214W. Can’t say this is due to the power drops, they don’t occur that often. Race S simply shows/logs a lower wattage throughout. As said before, this started at around the .12 software rollout.

atoponce

@herlas Screenshot from Stryd’s PowerCenter. 316, 316, 315 W.

atoponce

@herlas Also, I’ve tested my Stryd Duo with my old Suunto 9 Baro to eliminate variables and did not have any power drops on the display. The power reading on the watched remained 100% reliable during the run.

I haven’t yet tested my old Stryd wind foot pod with my Race S, again to eliminate variables, but knowing that there is a fix in beta, I don’t think I’ll bother. It seems like Suunto has identified the issue. Hopefully it comes out as a hotfix rather than the next quarterly update.

guy.s

I’m getting a problem with wayponts. Instead of showing up with the waypont name the watch is just displaying “Waypoint”. Changing the type of the waypont results in the watch showing the changed type as he waypont name , like “Parking”. The name is ok in the app, but the watch doesn’t show it.

Has anyone else seen this?

I don’t know whether it’s an app or watch problem.
Race 2.43.12, android app 5.3.7

Guy

babychai

@guy.s Yeah, i got this problem too on my SV.

Fenr1r

@guy.s Yup: noted here.

Hard to get custom names to “stick”. Entered, saved, synced … checked … repeated. Works worse with imported routes but still get reversions to default type names on SA-created routes. Usually midway through a multi-hour activity.

If there’s a guaranteed-success process/ritual known to Suunto, sharing would be appreciated.

isazi

@sracer few more released today