Software Update 2.43.8/.12 (2025 Q2)

VoiGAS

@sryke Interesting comparsion, thank you! So it seems to be normal that Suunto Power is not as flattened as Stryd. I find it extremly wobbly, also during the run. Jumpung between 100 Watt and 200 Watt and back from one second to another.
I noticed it with the current firmware, but maybe it was also like this before

runsgrun

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

@sryke Interesting comparsion, that you! So it seems to be normal that Suunto Power is not as flattened as Stryd. I find it extremly wobbly, also during the run. Jumpung between 100 Watt and 200 Watt and back from one second to another.
I noticed it with the current firmware, but maybe it was also like this before

I did notice dropout of power data with the older firmware but those instances were very sharp dips and the numbers recovered almost instantly. I attribute such this to the Bluetooth connection with the Stryd pod being interrupted and these didn’t affect the overall readings much.

Antoine

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

I don’t know if i was already mention but i have 2 remarks and sur if is is the normal behavior:

• Raising your wrist : OFF
=> but during activities the backlight is activated when raising wrist (it seems it wasn’t the case some times ago)
• custom battery mode
=> it is always selected by default even if the configuration is exactly the same as perfo mode

Nobody had the same problem on custom battery mode ?
How to solve it ?
Thanks !

sryke

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

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

@sryke Interesting comparsion, that you! So it seems to be normal that Suunto Power is not as flattened as Stryd. I find it extremly wobbly, also during the run. Jumpung between 100 Watt and 200 Watt and back from one second to another.
I noticed it with the current firmware, but maybe it was also like this before

I did notice dropout of power data with the older firmware but those instances were very sharp dips and the numbers recovered almost instantly. I attribute such this to the Bluetooth connection with the Stryd pod being interrupted and these didn’t affect the overall readings much.

But these dropouts shown on the watch do not show up in the fit file. My Race S fit file and the Stryd pod fit file were the same for me (in the cases where there is no overall disagreement of the readings). I don’t see any dropouts in the fit file.

Pavlas

The dissatisfaction over the new maps has been mentioned several times already. Especially the disappearing paths when zooming out more.
I did a comparison of how the different zooms look in the city. Only the 200m zoom is the same. But the 100m and 50m zooms look the worst in my opinion. Only the 500 m zoom seems clearer to me.
It doesn’t look that bad in the open. But when the dashed roads turn to white background at 50m and 25m zoom, it looks like I’m walking on a big road.
Judge for yourself.
I probably don’t need to mention that the new maps are on the left watch.

Tieutieu

@Pavlas Thanks for comparison.
I mostly use 100m zoom (for trail running) and 200m (for cylcing).
at 100m expecially, I find the new layer easier to follow. Small tracks are more visible.

runsgrun

@sryke

This is the combined chart of power data from Stryd’s (magenta) vs Race-S’s (blue) fit files. About 5 dropouts over 66 minutes. Sometimes none, sometimes more. Other than these and the sight offset due to different start times, the data points matched nicely.

Pavlas

@Tieutieu Yes, the new maps are a bit better in the open. But there are also 2 kinds of paths. Short dashes and long dashes. My comparisons are just the paths that are marked with short commas, and those aren’t very nice. In the city, it makes it look very cluttered. It would be good to find a compromise.

maszop

@Pavlas Just to add: after removing the paths from the 500m view, the map in the mountains looks like this:
alt text
I wonder who at Suunto came up with such a brilliant idea.

Now, not only are there no contour lines, but there are also no paths or trails.
Thank you Suunto Team.

Pavlas

@maszop Yeah, that’s bad too.

Max maxilifeguard

Is there a way to reinstall the software on the Suunto vertical?

safari

@Max-maxilifeguard If you’re talking about installing an FW,

Go to Settings > General > About

Scroll down to the bottom.

Hold down the bottom button on your watch.

Debug mode will appear.

Here, you’ll see the FWs in the “Select OTA Packet” section.

Remember, your watch’s battery should be at least 50%.

Max maxilifeguard

@safari thanks, but the problem is the watch is lock, i can’t unlock to used. I wonder is its possible to do it from the app

Milan Šádek

@Max-maxilifeguard there is no other way to recover a bricked watch than sending it to the Repair center. Mine got flashed and sent back to me within 48 hours. Good luck with your device!

safari

@Max-maxilifeguard In this case, the repair center…

sky-runner

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

Now, not only are there no contour lines, but there are also no paths or trails.
Thank you Suunto Team.

And as I mentioned earlier in this thread it is even worse when using imperial units because everything disappears at 0.2 mile scale, which is just 320 meters.

And at 500 ft (150m) scale trails are so thin on Race and Race S that they are almost invisible to my aging eyes unless I stop and steady the watch. With this change, maps are no longer useful to me.

Can you see the trail going down from the center of the screen on the picture above? I usually can’t. And it is even worse on a smaller Race S screen.

GiPFELKiND

@sky-runner hey @sky-runner you can downgrade

Squirrel

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

The dissatisfaction over the new maps has been mentioned several times already. Especially the disappearing paths when zooming out more.

Consider creating a thread about these map rendering issues, since you have a good comparison pictures and apparently 2 watches as well.
This way, it would not get drowned down among other things in 2.43.8/.12 and will be useful for later firmware releases as well.