SOFTWARE UPDATE 2.33.12 - Q1 2024
-
@Fenr1r said in SOFTWARE UPDATE 2.33.12 - Q1 2024:
@wmichi My version of same:
Touchscreen unresponsive on first activity after update. Toggling relevant controls proved futile.
A soft reset fixed it. So far …
I had the same twice. I have the SV since 20th of February, that day I did install everything and so on, my first run was on the 21st, and I noticed that the touchscreen was unresponsive after the activity but after some minutes the touchscreen started to work normally again, but after the second activity it failed again. I did a softreset and everything started to work perfectly, initially I thought the issue was due all the installations in the new watch. But last week it failed again (with the new software) and I had to perform a softreset. Yesterday I had the feeling that the touchscreen was failing again dismissing an alarm but after one or two tries it worked fine.
If it happens again I will send logs.
Maybe son field tester can confirm if Suunto is aware of the issue.
-
@cosme-costa
I didn’t notice unresponsive touch with my private Vertical which runs the official released firmware 2.33.12 -
@Zdeněk-Hruška we can’t change what fields are shown on the autolap screens, neither manual laps.
I agree with you, I haven’t done cycling in a while but for running, when I use an external power meter (Stryd) the autolap screen shows me the lap avg power as in @Durri picture above.
When I use don’t the power meter , say I select foot pod instead, I get Lap. avg heart rate.In any case, if @Durri didn’t connect a power meter on his ride, sounds to me this could be a bug on his custom gravel cycling mode.
-
@herlas yes, I don’t have a power meter, and it should show the average speed. As I already wrote, I didn’t have to solve anything on the S9B when creating my own cycling profile, AVG Speed was displayed…
️Something is obviously wrong here
-
@Durri wouldn’t a custom sports mode with a lap summary where you can set the fields you need be a workaround for you?
-
@Łukasz-Szmigiel No, because if it worked before, it must work now
️ -
@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.
-
@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