SOFTWARE UPDATE 2.19.42 January 27, 2022

wmichi

@dmytro Ok, thanks for this info. So I don’t need to worry

DMytro

@wmichi you’re on the current firmware, right? I’d suggest setting background brightness to low. But otherwise it seems somewhat consistent with my results.

wmichi

@dmytro Yes, right after turning the watch on for the first time, I updated to 2.19.42. After the update I got a really bad battery life, which got better after charging the device to 100%. I will play around with the backlight settings.

surfboomerang

@wmichi You have sleep- or 24/7 HR on?
20% per day looks a bit too much. For reference, my S9P loses about 3-4% per day after the latest firmware update.
I’m 9 days after the latest charge and some hours of training and the watch is down to 54% at the moment.

wmichi

@surfboomerang Yes, sleep and 24/7 hr active. I wanted to replace my S9P with this S9B, because the screen of the Peak is a bit too small for me. Also my S9P lasts longer, even with permanent standby light on (adaptive on). Maybe I need to drain the battery of the S9B to 0% and do a full charge.

cosme.costa

@wmichi If you have 24/7HR active I do not think that you will improve much. At least that is my experience, if you turn it off then you will have a massive improvement.

On the other hand you should wait two or three charging cycles before having any conclusion.

Despite Amazon’s fantastic customer service, people (Amazon customers) sometimes are the worst and Amazon workers, I can imagine they are really stressed. Once I bought a Nest Thermostat and I received a kitchen clock with the same shape instead, and the box was sealed too. I’ve read in the Amazon comments that there are people ordering roombas, changing the battery of the new one in the one that they already have at home and then returning it as they do not want it. So, probably you had bad luck with Amazon. The good thing is that with Amazon it is so easy to deal with this issues.

wmichi

@cosme-costa Yeah, could be just bad luck with Amazon. On the other hand: The boxes where sealed in plastic and the buttons on my second unit had a different color (grey instead of blue). So I guess in this case someone at Suunto had stress We are alle just humans…

So the battery life of my S9B seems to be in line with other S9B. And since the tech of this watch is basically 3.5 years old, it’s ok.

MdzOtt

@dmytro substantial improvement

S.Pichi

after updating to V 2.19.42 , my watch(S9peak) downgrade itself to 2.18.18. Right now it show watch is up to date . what i should do to update again ?
thanks for advance.

S.Pichi

@s-pichi it ok now , i do factory reset and can update now. Thanks.

MiniForklift

I was always the annoying one who had the S9B with no battery issues, used to be able to get a good couple of weeks before I needed to even think about charging

Noticed that my battery levels appeared to be dropping faster than usual so I charged it to full last night. Now, around 20hrs later it’s down to 90% and I haven’t used it at all today (no training). HR is disabled as is sleep and mobile notifications - nothing is active. 10% in less than a day without any training is definitely not right, something is off since I updated

Egika

@miniforklift as always with firmware updates: give your watch time for a full charge cycle (full to empty to fully charged), as the battery calibration needs to recalibrate itself. Then check again please.

Pavlas

I had a battery problem with the previous firmware 2.18.20
After the last update it’s good again.
But one thing happened to me on Tuesday. I went for a run. I wanted to use the Suunto Plus - Burner. As I selected the Burner, the watch froze and restarted.
After restarting, I tried again and it seems fine now (I tried it 3 times)

DMytro

@pavlas did you send logs?

Pavlas

@dmytro No. I forgot. I’m sorry.

isazi

@pavlas if it happens again (hope not), sync your watch with the app as soon as it recovers, send logs, and send me a PM with the description of what happened, the time you sent the logs, and your email. I will fill in a bug for Suunto.

A Former User

@dimitrios-kanellopoulos short questions about deeper understanding ascent / descent algo during sport modes:

Ascent / descent is only counted if a certain threshold of ascent speed is reached? That means if you would run 10km with constant very low ascent ( 1m per 10km), you won’t see 1m total ascent, only maybe in absolute altitude?

I suppose absolute altitude is something completely different than ascent. Question: fusedalti has only impact in absolute altitude, not ascent? Thats why you would see weather changes in ascent but not in absolute altitude.

Pavlas

@isazi Okay, thank you!

isazi

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

Ascent / descent is only counted if a certain threshold of ascent speed is reached? That means if you would run 10km with constant very low ascent ( 1m per 10km), you won’t see 1m total ascent, only maybe in absolute altitude?

Yes, if you do not climb 3 meters in a short time, it does not count.

Dimitrios Kanellopoulos

@mountainchris complicated question.

Complicated answer

Yes if you do 10km with 1m ascent in each 1km it wont show 10m ascent . Your hand moves 1m . Its more complicated. But first you need to pass that threshold, have some vertical speed (accelero) and then it will count every 1m.
So if you run 1km with 3m ascent at some point and then 1m increments will count. But not forever. So if during the 2nd km there is no ascent , the 3rd km onwards even if 1m ascent , it wont count. So that threshold is reset if it sees you stopped ascenting.
The fused alti does 2 things , not in order and not only 1 time

a) If the difference of GPS based altitude to barometric altitude is big it will try to “fix” this instantly. Ie you are at 1000m but the barometer says 1m , it will correct that and all past values.
So if you are at minute 5 , lets say with a flat altitude of 1m all the time before it will correct all prev values as well to 1000m.
b) if the difference is small, and the GPS error is not helping to determine accurately the altitude it will start to correct slowly and that might count towards ascent. for example you are at 120m and the baro says 100m. The GPS error is 20m. IT wont try to correct it as the GPS altitude might be 120, 140 or 100 or what ever in 20m error. It will listen to good moements of GPS altitude and pull a bit up that barometric altitude without correcting prev values. So slowly you will see 119 , 118 and those might count to descent if you are descenting but not if not due to the threshold not being passed.

I wont go to internals but it is not an easily subject to describe.

A+B can happen many times during your workout