Software update 2.39.20 (2024 Q4)
-
@sebchastang said in Software update 2.39.20 (2024 Q4):
@BrunoH I have also observed that sometimes even after self-repair the control panel fails again to display correctly.
I still don’t know what causes this broken display.When I have the control panel bug I solved it repeatedly with this pattern :
- control panel with long press bottom button shortcut => BUG
- back to watchface
- press middle button shortcut (for me it’s chrono)
- back to watchface
- control panel with long pressbottom button shortcut => OK, bug is gone
-
@Kramble thanks but I’d say this workaround is irrelevant since other showstopper bugs emerged. My Vertical lost wifi connectivity and thus couldn’t load new maps. I had to downgrade.
-
@Kramble Thanks for this new workaround!
Since I switched “control panel” access from bottom button shortcut to pinned widget (middle button short press), I have not seen the broken display anymore. Nevertheless I expect a fix in next firmware update. -
-
I just got a new Race S for Christmas, and now I registered to add another case where the OHR stops working from time to time.
It installed the 2.39.20 update on Christmas Eve, and since then, I had to restart my watch once or twice a day every day, because the sensor stops working.Unfortunately I can’t roll back to 2.37.48, because it was shipped with 2.35.36, and I don’t know how to go to an intermediate version.
-
I am also seeing the issue with not being able to add new map downloads with the new firmware. Existing maps seem fine but stuck in terminal “waiting to download” for any new map request.
-
@larrybbaker said in Software update 2.39.20 (2024 Q4):
I am also seeing the issue with not being able to add new map downloads with the new firmware. Existing maps seem fine but stuck in terminal “waiting to download” for any new map request.
This is something to do with your network or downloads. I downloaded three new maps for SV Solar last night with no issues.Perform a soft reset first, if that does not work then delete and reconnect your network and then try deleting or adding maps.
-
@larrybbaker said in Software update 2.39.20 (2024 Q4):
I am also seeing the issue with not being able to add new map downloads with the new firmware. Existing maps seem fine but stuck in terminal “waiting to download” for any new map request.
i have no issues on that front… strange
-
@Brad_Olwin Thanks @Brad_Olwin I did the soft reset with no change - I did not try deleting the networks and re-adding them (did not see your suggestion). I downgraded the firmware - added the new map with no issues and then upgraded the FW again.
-
@larrybbaker I replicated it by the following :
Added a second WiFi
Connected the watch to charger
Added a map to be downloaded
The watch says the WiFi cannot be reached
Deleted the WiFi
Adding the WiFi fails -
@thanasis confirmed thank you - I deleted my wifi settings and now cannot add them back - multiple tries soft reset of watch and killing/relaunching the app. IOS latest Beta. Watch on latest FW.
-
@larrybbaker unfortunately you are right … it’s now impossible to add a WiFi
-
@Brad_Olwin I just submitted logs for this issue - if needed.
-
@larrybbaker Can you PM me the email you use for SA and the time/date logs sent. I will attempt to replicate, which seems likely and file a bug report. Please include time zone!
-
@larrybbaker Same for me with vertical. I did try everything. Restarting watch, restarting phone, killing app, 3 different wifi(even restarted all 3 wifi routers also), nothing works. Seems like the only way to make it work would be to downgrade like you and @BrunoH did. Hope for hotfix soon!
-
@burningwipf I’m in the same boat. Contemplating returning this brick. If HR stops every few days, what’s the point of wearing it? And it sounds like this is an old bug that has re-emerged. I’m reverting back to the shipping software in hopes that at least HR is better.
-
Just as an addition: when starting an activity this morning, while searching for GPS signal, the Race S did a soft reset and then another one and after that went to the:“the device is being restored into a safe state“ - looped a few times and after 5 minutes or so ended up with an error - hard reseting the watch.
That’s a bit frightening if I imagine this happens right before or in a longer activity. Other than that watch runs fine.
-
I am coming back to the GPS
Comparing the GPS of the vertical after the Upgrade with that of the AMBIT 3 Peak is still a hit or miss… I am still not convinced that the multi GNSS on the vertical is any better of that of the AMBIT 3 peak.I took the A3P for a run and I was impressed! The altitude measurement, the track and so on are really exceptional and maybe a bit better than that of the Vertical (which after the upgrade is better than before).
It’s crazy -
There is no difference between my Vertical and my Spartan Ultra. In the woods the track of the Spartan often is more precise.
-
@pilleus said in Software update 2.39.20 (2024 Q4):
There is no difference between my Vertical and my Spartan Ultra. In the woods the track of the Spartan often is more precise.
That’s quite sad in my view
-
@thanasis said in Software update 2.39.20 (2024 Q4):
I am still not convinced that the multi GNSS on the vertical is any better of that of the AMBIT 3 peak.
I’d love to see some traces from the Ambit3 Peak, if you are willing to share (understand if you aren’t). My first Suunto was the 9 Peak, and its accuracy was definitely nowhere near the Vertical. Obviously the antenna design on the Ambit series is the big plus when it comes to accuracy. A larger, upward facing antenna is probably just as good, if not better, than a multiband one crammed into a small watch body.
But this is just for the GNSS traces. Activity distances always seemed pretty accurate with the 9P and 9PP I previously owned.
I’m still pleasantly surprised with the new GNSS updates. The removal of the “Suunto wiggle” seems to have resolved the issue I had with the watch often measuring (what felt like) just a bit long in some cases. I’ve noticed my regular routes are coming in about 0.5-1.0% shorter than previously. This seems about right to me. And the fact that Suunto doesn’t seem to use any additional metrics to calculate distance (GNSS distance = activity distance) gives me confidence in those totals.
A good test for GNSS accuracy are laps or hill repeats. Below is an example using my Vertical from a hill repeat session early this week with 5 laps (so 5 up and 5 down). The traces overlap pretty darn well, but not perfect. Still, one of the best performances I’ve seen from a watch.