Software Update 2.43.8/.12 (2025 Q2)

sky-runner

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

When you press paused it tells you how long you have been paused on the screen.

I’d never pause my watch for the following 3 reasons:

It is way too easy to forget to unpause it in a race when running for hours and the brain becomes foggy - then all the stats become messed up.
I want the time to reflect the race time, not the time I am actually moving. I guess now it is possible to show the elapsed end-to-end time, but that wasn’t possible before. Still, if I pause my metrics would likely be messed up.
Third party apps get confused by having pauses in the activity FIT file. For example, Strava does change some of its algorithms when it sees pauses. Over 14 years of using various GPS watches I learned the hard way that it is the best to start an activity, preferably lock the watch, and not mess with it until I’ve finished. Otherwise, the risk of losing the data or messing it up is just too high.

Bogdan1921

I finalized my ruuning and I have this message. Nothing changed and still “saving”

Later edit: I’ve made a soft reset. The activity was saves and I have sent the logs in the Suunto app

Inge Nallsson

@Jordi-C said in Software Update 2.43.8/.12 (2025 Q2):

Started to work 30 minutes after the soft reset…

I use my Race S only for activities, so have it shut down in a closet the rest of the time. But I wanted to check the bug situation you reported and booted it up an hour ago. [Previously after installing 2.43.12 I synced with SA, shut the watch down completely, booted it up and synced again before shutting it down for the night <-- “Measure twice, cut once”]

Looking through the watch Widgets the HR graph was empty (since not having any history) and the kcal/h was dashed out --. OK, but when scrolling further down to the “Steps & Calories” widget my eyes bugged out at the values on display: 82479 Steps with 4641 kcal. Pictures:

I cleared the SA memory cache and resynced the watch several times but the numbers didn’t reduce - instead they went up a bit with body movements…

Then I saw @VoiGAS routine of doing a Soft Reset (holding the upper button pressed ca 15 seconds until the watch reboots). So I did that as well, thinking it might erase the Step/Kcal data. Well, it did erase the extra data points having accumulated, but booted up to what now seems to be a default on my watch of 82479 Steps with 4641 kcal. The “Total:” kcal had gone up a bit, seems to follow a ‘time of day’ increment.

I’m still waiting for the Heart Rate widget to show a graph since the Soft Reset, but the “Calorie consumption” at least has filled in the dashes to “70 kcal/h”.

Edit: Toggled the “24/7 wrist HR” button Off, then On again in the widget after about 1 hour post-reset. Then a “Minimum HR” value showed up there, but still no graph. It took 2.5 hours before the first vertical red line of a graph segment became visible. These compressed data views can really confuse an impatient person.

nseslija

@isazi What data can help?

isazi

@nseslija probably link to the activity, logs sent just after an activity when it happens, or steps to easily reproduce it. I’ll open a bug report with all of this.

far-blue

@isazi my Stryd is paired as a Foot Pod

atoponce

@isazi Finally in front of my computer. I have a lot of zero drops for 1 second in my FIT file that cannot be accounted for. This is reminiscent of my old Amib3 Peak and 9 Baro which had many zero drops in the recording, like the watch just didn’t record anything for that second. The unaccounted zero drops are at timestamps:

50:08
51:05
51:24
53:00
53:03
54:16
54:27
54:35
1:01:11
1:03:27
1:03:29
1:03:32
1:03:34
1:03:56
1:04:03

Everything else is accounted for.

The link to the activity is here: https://maps.suunto.com/move/aarontoponce/6853f8c79e9d8315b4d154d0

sky-runner

Has anyone noticed map rendering regression after this software update?

Previously I complained about trail visibility - that at 0.5 mile scale trails become very thin and at 1 mile scale trails completely disappear.

Suunto’s answer to that? Now it is way worse!

After the last update trails are visible only at the first 3 zoom levels - 100 feet, 200 feet, and 500 feet. At 500 feet scale trails become very thin and difficult to see and at 0.2 mile scale trails completely disappear. In fact, at 1 mile scale all local roads disappear too so that only major high speed roads are visible!

This doesn’t make any sense!
Has this even been tested by anyone who trail runs?

I should probably make a separate post about this because this seems to me like major regression in functionality!

Kaiphi

@Jordi-C Had the same problem on my vertical. Try to turn the button off and on again 24/7 at the bottom. Helped me

Inge Nallsson

@Inge-Nallsson The 80K+ Steps were gone from both watch and SA once a new day had ticked over, so can be considered ‘phantom’. A bit disturbing, but harmless in the grand scheme of things:

Heart Rate graph and other sleep registrations were all OK during the night…

GiPFELKiND

@sky-runner PLEASE GIVE THE OPTION FOR DOWNGRADE 2.37.48 thats the best Firmware.
Need it for Suunto Vertical Solar!!!

Egika

@Inge-Nallsson as the .12 hofix was addressing steps, resources and sleep representation, it is likely that this was solved now. Or did it happen already with the 12?

Inge Nallsson

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

did it happen already with the 12?

These phantom steps came with a bootup on 2.43.12 But I have no idea if such a resource-less (no data/history) watch start exhibited the same error on previous FW versions.

GiPFELKiND

@GiPFELKiND okay 2 likes for this @Dimitrios-Kanellopoulos @pavel.samokha Can someone share a link please with Firmware 2.37.48 or private Message have a great weekend

Pavlas

@sky-runner I don’t understand the change either. I’ve mentioned it before. I found the maps beautifully clear. But now zooming in 100, 50 and 25 meters is very ugly and opaque. Especially in the city. It’s not too bad on the amoled display, but I don’t like it at all on the Vertical

Tieutieu

@Pavlas I agree under 100m it’s a bit ugly, but at 100m zoom and above, I find it much easier for guiding.

MirkoP

@pavel.samokha
Not available in Italy