Software Update 2.44.52 (2025 Q3 - HOTFIX)

VoiGAS

I really hope the fixe helps to reduce or eliminate crashes. Fingers crossed

safari

I’ve updated it.
First impression: recovery values are still inconsistent.

Recovery between watch and app in sync

Danny poleg

@sartoric That’s true, but from personal experience it’s worth asking, maybe they took care of it and didn’t emphasize it.

Miroslava

@safari same here

grego

@safari Same here, two different values.

v.sacre

@safari Same value on my watch after a sync

Stefano M64

@v.sacre said in Software Update 2.44.52 (2025 Q3 - HOTFIX):

@safari Same value on my watch after a sync

on mine (Race) too

maszop

Values still different in watch and app.

safari

@Stefano-M64
live test video

https://streamable.com/20eiep

OutdoorMan

@safari did you try to force quit the app and sync again? Yesterday I had an issue where it synced very quickly and it didn’t show any watch faces and app in the phone app. Force quit did the trick. Just an idea.

aiv4r

@safari Same here. Just updated, restarted and synced and checked. Recovery widget the app 72% on the watch 36%. (Race S)
No biggie, since I do not use it, but clearly not fixed.

safari

@OutdoorMan
I tried it now, it didn’t change.

dulko79

Inconsistent for me too.

maszop

Without public testing, Suunto is constantly exposing itself to ridicule.

safari

@dulko79
Interestingly, the factor values are correct (TSS, HRV, etc.) but the recovery value is inconsistent.

Luka_Kemp

Recovery between watch and app in sync - Unfortunately they have not fixed this.
The watch and the app show different values.

Is it so difficult to get these parameters in sync?
They have managed with Resources…

brave_dave

For me, often the values inside the recovery widget in the app are just wrong and don’t align with the same values displayed in other widgets in the app and on the watch (Race s).

For example right now, in the recovery widget the displayed 7d average sleeping time value for me is different than in the sleep widget. Often also the body resource value in the recovery widget is different than in the resources widget and does not update.
Sometimes switching from today to yesterday in the app leads to an update and realignment of the value.

So it seems that the underlying values in the recovery widget are calculated by the app instead of just being synced from the watch or transferred from other widgets inside the app. This “recalculation” inside the app leads to different values.

Observed on Android, App Version 6.2.2

@smopi @safari @aiv4r @maszop @dulko79 please check the underlying values across the app if they are also inconsistent as for me

smopi

Vertical: 74%
App: 73%

Suunto Vertical Titanium Solar to jest mój pierwszy zegarek tej firmy i na pewno ostatni. Po ponad 2 latach pierdolenia się z takimi błędami mam serdecznie dosyć. Jak to jest możliwe, że w sprzecie za taką kasę nie działają poprawnie tak podstawowe rzeczy jak synchronizacja danych pomiędzy aplikacją i zegarkiem? Do tego cała masa błędów w aplikacjach S+, które zgłaszałem, ale oczywiście nic to daje i nie są naprawiane. Ręce opadają.

JonasLarsson

Interesting change: No vibration when Polar H10 “connects”.

borgelkranz

@pilleus that would interest me as well. I downgraded because of this.

Edit:
I gave it a shot and installed the hot fix. My Fazua Ride 60 still gets identified as a speed sensor. But there is now an option to set the wheel circumference.

What also is the same is, that all my zones again got reset. Ok, nobody said that this was fixed. But I find this sad.

So I decided to downgrade again to wait and see what future fixes or updates might bring.