SOFTWARE UPDATE 2.33.12 - Q1 2024
-
@Mff73 said in SOFTWARE UPDATE 2.33.12 - Q1 2024:
@Francesco-Pagano
it is just the way such sensors are working : light emission (LED) and a sensor which tries to see the reflected light from the support.
Light is on only when the sensor think that there is any reflected light to analyze : from skin (logic) but from any potential reflecting support (try with a banana
)it is even not the contact, but just near enough to see any reflection
-
Today, the touch screen was blocked again. Unable to use it. I switched off the vertical and restart to fix the problem. So not resolved with this FW update.
-
Iām having problems too! Today the touchscreen froze, I clicked on the data field many times and nothing happened, and then the field began to switch data on its own. I also couldnāt access widgets using the touchscreen.
-
@Sergei-Ladeishchikov said in SOFTWARE UPDATE 2.33.12 - Q1 2024:
the field began to switch data on its own
Iāve also experienced this several times. The touchscreen seems to experience repeated āphantom touches.ā I managed to grab a video of the behavior.
Not sure if this is related to the software update, but itās only happened while on 2.33.12.
Vertical Ti
-
@duffman19
yeah, I had this today too.
Never happened before. -
@duffman19
Iāll report this -
@duffman19
next time this happens, please send logs and pm me your account email, date, time and timezone logs sent.
thank you in advance
-
@freeheeler I remember another funny thing with the touchscreen. Right after updating to the latest firmware, in pre start mode of a trail running activity, I went into the navigation menu to select a route. I tried to swipe down but then the touchscreen went crazy. Without me doing anything, I was kicked out of the navigation menu, like I had swiped from left to the right of the screen (the back gesture). Immediately after that the watch went by itself back into the navigation menu. And back out. And back in. And back out, and back inā¦ Since the watch went crazy, I went crazy too and pressed buttons like a manic.
That helped and all of a sudden the watch stopped doing this. I started the activity and everything worked as expected. I never saw this behaviour again. Next time I will send logs (by the way, the watch was completely dry, no water drops on the screen). -
@wmichi
can confirm and saw this with clean and dry screen twice -
Could anyone explain is such battery usage is okay or not: -60% in 7 full days with only 5h15m of road running (5 runs - 2 with ohr, 3 with HR belt, including one structured run workout), 6 syncs in total and the watch was laying in the drawer between training sessions.
As I can see every training takes only 3-4% so I think 40-45% for being in standby mode is way too much. Highly likely it was much better before Decemberās update
1.5 year old 9pp with the latest updates.
upd: runs were done with perfomance GPS setting and raise to wake backlight
-
@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.
