SOFTWARE UPDATE 2.33.12 - Q1 2024
-
@false what are your backlight settings, turn to raise ? Have you notifications enabled or off ?…
-
@Tieutieu Everything is turned off (literally). Backlight is raise to wake
-
@false OK I’ll check battery consumption on my wife’s S9pp, she has same settings ; I’ll let you know. But it’s seems hight. Usually she had less than 5% a day consumption with HR tracking on, notifications off, main backlight off, backlight to low, raise to wake to low (on my SV it’s around 4% a day max)
-
@false definitely not normal for mine, neither before nor after the update
Do you have 24/7 HR activated? I found that to drain the battery, if enabled while there actually is no HR/wrist etc nearby. Already before the recent update though -
@wurzlsepp No, nothing is active and never have been
-
@false ok that’s weird then. Supposing you’ve done a hard reset after the update (was necessary with my S9PP!), i also don’t know what could be the issue
You could power off the watch between your workouts and see if the battery still drains. If yes, its a hardware issue (warranty repair?). If no, software problem and thus there might be a fix (reinstall update, bug fix with next update, etc)
-
as an update - when my watch is switched off there is no battery drain
-
Has anyone noticed that the ascent calculation is a little more conservative after this update? I have some regular routes that I run and I’m consistently seeing about 5-10% lower ascent numbers compared to runs before the update.
The graphs look pretty great and comparable to other devices worn at the same time. Perhaps there’s a new algorithm with more aggressive rounding?
Most of my trails have lots of small rollers, small ascents of 10-20 feet at a time. I know there’s some sort of cutoff before it gives credit for ascent, which seems to be around 10 feet. Even so, it generally seems as though my activity ascent numbers are a little low lately.
-
@duffman19 this is old firmware. I would post on current firmware.
-
@Brad_Olwin Yes, I know, but the issue started with this update. And 2.33.14 was a hotfix addressing other issues. Just curious if anyone noticed a change starting with 2.33.12.
-
Remark on map ruller:
I have tried the “map ruller” during a trail.
First it works good. But after a moment it became uncontrollable and changed position on its own.
Even if after recentering the map (tap on screen).
To stop it i had to desactivate it.
Then, when back to home i have done a soft restart.
I have had this problem just one time.
Rk: no water on touch screen.Watch: Suunto vertical solar
-
@Antoine maybe unrelated, but on very rare occasions I noticed the touchscreen went crazy even without waterdrops. It prevents the watch from locking and the only way to resolve this was to thoroughly clean the screen and perform a soft reboot.
-
@surfboomerang it seems ot was specific to map ruller because the watch behaviour was good if i changed to another screen or if i desactivated ruller.
-
@Antoine update: i noticed an over consumption of battery with this problem
-
@Dimitrios-Kanellopoulos Since 2023 there have been posts in the forum regarding the flight mode, which, when activated, still maintains the Bluetooth connection. Why is the bug still not fixed in the latest update? From a developer’s point of view, this is a no-brainer. Why don’t you fix it? It’s usually the little things that make a big difference.
-
S surfboomerang referenced this topic on
-
@mr-quality https://forum.suunto.com/post/143310
-
Still persisting the problem of self deleting portion of the red route. the more you go ahead the more it deletes the beginning part of the red track… this is literally ridicouls honeslty… You cant understand where you started from…
-
@giuliosq that bug was not related to this hotfix (fixing connection issues). I am checking with Suunto if it will be fixed with next update.
Edit: oh this was the Q1 release post, not the hotfix. I’m checking in with Suunto anyway.
-
@isazi
Thanks a lot. Yes it’s related to the incomplete recording matter. Once saved it shows the whole route but if you want while recording to check where you started it deletes the first bits. Quite harsh once on glaciers where you need to follow the exact route back and it does not appear. But I guess you got what the issue is related to. Thanks a lot -
I isazi unpinned this topic on
