SOFTWARE UPDATE 2.19.42 January 27, 2022

Richard Thygesen

@patrick-löffler and my watched might have had the same message I’m not sure becasue my eyesight is terrible and I just pressed ok on the message.

A Former User

@patrick-löffler same behavior with me, very strange

surfboomerang

@richard-thygesen Can’t confirm it. My S9P survived the night.
I don’t have sleep tracking enabled however

Patrick Löffler

@surfboomerang that’s interesting. Just to add more information. I have sleep tracking enabled and I also enabled the blood oxygen tracking.

Richard Thygesen

@patrick-löffler I also have all that activated.

HankWang

@patrick-löffler Same here. It rolled back to the previous FW and won’t be able to find the new version anymore.

surfboomerang

@richard-thygesen does the watch think it is up-to-date
If you go into settings->general->software update?

Richard Thygesen

@surfboomerang yes it does.

surfboomerang

@richard-thygesen then maybe start a new thread under the S9P section so it can be reported to Suunto.

@isazi said in SOFTWARE UPDATE 2.19.42 January 27, 2022:

If you happen to find a bug, please open a detailed post in the correct watch section of the forum, so it is easier to keep track to (and report).

HankWang

@surfboomerang I’ve done that

https://forum.suunto.com/topic/7556/issue-fw-rolled-back-to-2-18-18-and-won-t-find-the-new-fw-anymore

Bulkan

Sorry guys, looks like there is something with the update. Is rolling back and changed the time. We are reporting this.

Meanwhile you can send logs from Suunto app and we’ll need your user name in Suunto app. In that case you can DM your user name.

dulko79

Same for me, watch updated to fw 2.18.18 around 4 am cet, has wrong time and connection to phone.

HankWang

@patrick-löffler Hey bro, quick side question after seeing your signature: After putting on Garmin Epix2 on your wrist, why thinking about going back to 9Peak?
For me, I like cycling and Garmin ecosystem is very tempting to me. But I really do like the look of 9Peak…
Really wanna hear your opinion.

markytarky

24 hours with FW 2.19.42

daily battery consumption - ok no change
went for run 20k (+800m) trail - use S+ weather plus route navigation (route saved from a workout), the route was not showing the elevation screen nor the turns (I guess that is ok for route saved from a workout?), when changed to a different route, the watch crashed and restored by themselves - the workout was saved automatically and watch came to time mode. I started and new activity and watch frozen totally on the screen where they are looking for GPS, HR, etc. Soft reboot needed. Since then, all ok - I repeated all the steps above with no issue.
sleep mode - SPO reading ok, battery drain during the night with SPO on, no change compared to when SPO is not on. Great job. Morning summary ok.
resources ok
HR ok
baro, alti ok

surfboomerang

@markytarky said in SOFTWARE UPDATE 2.19.42 January 27, 2022:

battery drain during the night with SPO on, no change compared to when SPO is not on

The excessive battery drain was also fixed in this update. So does this mean that SpO2 is draining more than without, but the same as before the update?

markytarky

@surfboomerang I never had an issue with battery drain during the day or night. What I’m saying is that sleep tracking with SPO has the same consumption as sleep tracking without it. This is not the case for Garmin, where SPO night readings are on during the whole night and eating the battery dramatically.

A Former User

@patrick-löffler
same here

Me - S9B -
girlfriend - S9P - (old sw, no phone connection, watch time incorrect)

isazi

Using SpO2 at night consumes (slightly?) more battery than not doing it, just so you all know.

Patrick Löffler

@hankwang Two reasons. I have tried several different watches and the comfort in wearing the S9P is unmatched. It’s simply the most comfortable. And actually I like the Suunto app much more than the Garmin one.

halajos

@dimitrios-kanellopoulos said in SOFTWARE UPDATE 2.19.42 January 27, 2022:

@halajos fix is on the way backend wise. Issue was the HU lang for some corner case.

If you are too eager to use an s+ now you can change the phone lang to eng to bypass this issue but I think our backend guys within the hour(s) should have this fixed.

Do I need to do anything on my side after the fix is done? I know it may take more time to fix the backend, I’m just wondering if it’s already done and there’s something else wrong. The symptom is the same.