Software Update 2.43.8/.12 (2025 Q2)

The_77

@Janne-Leppamaki I updated Thursday, no such issues present here. Mind you it was a varying timeframe before.

misu763

@Matúš
Yep! The report is back completed after the first day with missing data!

Egika

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

I noticed a mistake in the sport mode mountain bike downhill. When I start the activity, it shows me the duration, but not the depth meters and distance. These remain at 0. After exiting, however, everything is displayed. Does anyone else have that?

I had the same today on two out of 3 watches.
The third one showed all data correctly.
Reported it to Suunto
Thx!

kriskus

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

Did I read somewhere that there were going to be new watch faces coming out soon not attached to the update, but following soon after?

I also remember that there were two more watchfaces waiting to be released “in a few days”. I thought they would maybe come together with the S9PP firmware release, but that is not the case.

sracer

In the first post of this thread: “13. New watch faces available in the store this month”

Since last month just wrapped up, is there any update on the schedule?

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?

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.