SOFTWARE UPDATE 2.19.42 January 27, 2022

[skydancer]

Could someone answer if the battery drain in idle mode after upgrading to 2.18 for S9 (non-baro) has been resolved in 2.19 and the drain is back to levels observed in 2.16?

[surfboomerang]

@skydancer Multiple people with different watches confirmed that battery drain is back to what it used to be.

[MiniForklift]

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

@skydancer Multiple people with different watches confirmed that battery drain is back to what it used to be.

I never had a battery drain issue before, however I do from this latest update

[DMytro]

Tried going for a little bit higher hills today, I think improvement is definitely there (S9 and S9B respectively):
Total ascent was 194m for S9 and 160 for S9B. Previously it would undercount by about 30% on small hills, now it overshoots but by a lesser amount. I actually think it gathers the excessive ascent whilst on the even terrain either than on the hill itself, so if one does hill repeats, results might be even better.

[Michal Rada]

@dimitrios-kanellopoulos Hi, I have S9B, has anyone also noticed the change in Media Control screen in 2.19.42 FW? Old FW: the Media Control screen keeps active until you change it by middle button. New 2.19.42 FW: the Media Control screen changes back to clock (default) screen automatically after 1 minute. This is really annoying… I liked previous behaviour to keep the Media screen active “forever”. This change is not listed in 2.19.42 realease notes, so I’m not sure if it’s a bug or intended change.
Thank you for reply!

[DMytro]

Just did a hike in the mountains yesterday and could test the new algo for S9, S9B:
S9
Ascent 1008
Decent 994

S9B

Ascent 1032
Decent 1031

The route was a closed loop, so the data matches very closely on both. According to map data, ascent should have been just about 1000m. So, both watches did really well, and meter-by-meter works wonders.

[freeheeler]

@dmytro
did you plan the route in SA and “map data” is from SA?
…I didn’t know you had access to an S9B, how come? or do you need to apply rule 1 and 2 now?

[DMytro]

@freeheeler I used komoot. And I would give a bit more detailed map ascent info, if we wouldn’t change our descend path a little bit.

If only haha, my gf bought an s9b almost a year ago.

[A Former User]

@dimitrios-kanellopoulos Thanks. Last question. FusedAlti is used in absolute altitude? Not in ascent / descent, or? That would be me understanding. And that’s why altitudes are staying almost nearly perfect, but weather changes are impacting ascent / descent? Ascent / descent is just the barometer change and can be affected on stormy days. Am I right? Or are there even in ascent / descent FusedAlti checks and corrections?

[freeheeler]

@mountainchris
FusedAlti changes absolut pressure and the change does not count to ascent / descend. it sets like a new “zero”.
when weather changes, e.g. pressure drops it would give (as you know) a higher altitude. with gps it compares if a drop is reasonable or not every now and then and if the algo decides the drop is because of weather and not due to ascending, it readjusts the altitude with the help of gps altitude.

I hope this answers your question

[A Former User]

@freeheeler Thanks, yes. I thought this is the way it is done, but I was curious. That’s why you see the weather pressure changes fully in ascent / descent. Absolut it is corrected. Theoretically watch knows which corrections were made and could correct ascent / descent (afterwards). But complex, failures could be made and we see only changes normally 0-2 hPa on a day. So effect in hm would be not much in mountains with significant ascents.

Running relatively flat on very stormy days can have a significant impact, but there are only some countable days. On a S5P you wouldn’t see this weather / storm in ascent.

[freeheeler]

@mountainchris
here’s one issue I can not explain…
I’ve started at my doorstep with clearly wrong altitude and observed how fusedalti had corrected altitude after the first “hill”.
the route should be 99.something% symmetrical but a alti drop happened 1/3rd way back and it remained wrongish. the graph itself does not look like the sensor was blocked. no up or down spikes.
but the last bit on the way home has a different shape than the start that was corrected by fusedalti.
it would be interesting how often fusedalti kicks in and if it also considers gps signal strength for accuracy? I think it does, because if gps height is several meters off, it would unnecessarily “correct” an almost correct value.