SOFTWARE UPDATE 2.33.12 - Q1 2024
-
I had a strange issue on my s9pp with the firmware, which leads to think that some bugs are still inside else where.
somehow a king of buffer overflow or something like that.
One day last week I trigger a training as aerobic, and 1st i activated the bleep test from suuntoplus. But delete it and and make a new one and deactivate the function (wasn’t needed obviously).
Then the next days i made the same training, and every time that i triggered it, appeared around 10 or 12 min some beep and vibrations from the watch at irregularly moments until the end of training sometimes 2 or 3 time spaced on few seconds, and was really hard for some session to concentrate me because of this.
The watch displayed nothing special different when it came.
And after a week I had a look on the app by each training, and by some of them, the bleep test data appears , by other not.
The only action that I found to stop it, was to deactivate (uninstall the suuntoplus bleep test) and restart the watch…
Had someone experiences a similar issue ?
I’m thinking about to create a separate topic of this eventual issue or bug… -
@Ecki-D, @Brad_Olwin
I would also like to get detailed information about this new functionality, but it is not in the documentation.
For me it sometimes works and sometimes it doesn’t.
To be precise, to force this new function to work, the speeds must be much higher than, for example, “autopause” and the reaction time is very long.
The guys from Suunto support suggested a factory reset, but I don’t need this function that much to lose the collected data on the watch.P.S. I checked several times on two SV copies and this function has difficulty working in non-standard modes.
Maybe it’s accidental?
I’m curious about other users’ comments. -
@artusdiver @Ecki-D @Brad_Olwin
Here’s some more detail about this warning:
There are two different reminders. A “resume reminder” and an “abnormal speed (stop) reminder”.
-
The abnormal speed is checked only in selected activities:
running, trail running, walking, trekking, hiking, golf, nordic walking, orienteering and open water swimming.
The warning is triggered when the speed is >36km/h for 10s or more than 20km. -
The resume reminder is always active.
It appears, when the activity is paused and the speed >5.4km/h for 5s
*When the reminder is dismissed, it will not pop up again with speed changes. Only after the exercise state is changed.
-
-
This post is deleted! -
@Egika said in SOFTWARE UPDATE 2.33.12 - Q1 2024:
The abnormal speed is checked only in selected activities:
running, trail running, walking, trekking, hiking, golf, nordic walking, orienteering and open water swimming.and windsurfing
-
Since the update to 2.33.12 the touchscreen of my Vertical becomes unresponsive sometimes (in normal use, not during training). Buttons still work in this situation. The only way to make it work again is to do a soft reset. It happens once a day, sometimes twice a day and at other times it keeps working for two or three days. I don’t see any pattern. Sometimes it happens after an activity and at other times I don’t do anything with the watch for hours, and then, when I try to swipe or select a widget, the touchscreen is unresponsive. I never had this issue before the latest update.
Second thing: I am not 100% sure and maybe my mind plays tricks on me, but I think something has changed how the backlight works during training. Before the latest update, I never had any problems in changing light conditions (sun/shadows) like in a forrest, when I run below a bridge or pass a short tunnel. The backlight always came on reliably when I raised my wrist. Now the backlight always stays off. I also tested it while sitting in the sun: Hold the watch in the sunlight, then cover the screen and do the raise to wake gesture. It takes 3 to 5 seconds until the backlight turns on. And sometimes it doesn’t turn on at all. Totally unreliable…
Third thing: Again the backlight, when I am in the activity options (long press middle button during training) and I activate the toggle “Backlight”, nothing changes. Again, I am not sure (oh god my brain), but I could swear on the last firmware, this simply turned on the backlight permanently. Now this toggle doesn’t make any difference.
Anybody else with these problems?
-
@wmichi I sometimes have problems with the screen touch, sometimes it’s after a workout on the summary page, sometimes it’s after the sleep summary, sometimes it’s just when checking the time and changing the data field on the watch face (by the way, there was one time I changed the data on the watch face by pressing my finger, but the data did not change, I tried pressing and pressing, and then the data began to scroll through on its own, without pressing. It looks like some kind of freeze.) All this happens rarely, sometimes I solve it by rebooting, sometimes I do nothing and leave the watch alone , later the touchscreen starts working.
-
@wmichi yes, I see the same issues. Touch screen for me became unresponsive twice so far, with at least a week in between when it worked. Also solved by soft-reset. It is somewhat annoying, but definitely does not happen every day like for you - that’s terrible!
-
those issues (sync, non-responsive) are really strange.
My SV works like a charm after update. It’s was already working fine before.
None of my friends using SV or SR have problems either.
Probably some settings combination in exercice that may cause that. -
I don’t have those serious sync issues but something similar. I still have my 9PP and use it once in a while. While I never have an issue to switch in SA from Vertical to the 9PP, the other way around doesn’t work flawlessly. I would say in 5 out of 10 times SA doesn’t find the Vertical. The only way to fix the issue is a soft reset. I also had a Race, which I have sold yesterday. On the Race the exact same problem. Switching Race to 9PP: no problem. 9PP to Race: in 50% of the cases soft reset to make it work.
-
@wmichi I have had similar, with old and new firmware where the touch screen becomes unresponsive. Three to date; once during charging once during use on old firmware, this morning after waking up and checking sleep summary on new firmware.
I cannot say there is a specific sequence that causes it or prove anything out to check/test but it always becomes responsive after a soft restart. the buttons always work but it seems like the digitizer hangs up for some reason.
-
@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 have created a new gravel cycling profile. I set up a notification of the distance traveled every 5 km. The watch won’t show me the average speed when notified. When I use the preset gravel mode it works. Does anyone have a similar experience?
-
@Durri I think the contents of such notification are different per sport. You can set a screen with laps and populate them with different info, whatever you need.
-
@Mff73 said in SOFTWARE UPDATE 2.33.12 - Q1 2024:
@Łukasz-Szmigiel
i was just questionning myself, no judgment.
It was an option, it was remembered, it is not anymore, it is not nice, it is a “bug”.
Then, it is just few clicks to remove it, and “remove it each time” is the definition of a nuisance
I got it Thanks for „spelling it out“. I think what you posted is a user story that would allow the Suunto devs to add it to a test suite or check list that a new FW needs to pass. I would love to know how advanced Suunto is on this aspect. I know myself that it is easy to break software but I am supported by a test suite so that my users are not my beta testers. (Things can still go wrong because the way humans use things varies, but I save my users a lot of grief with my test suite.)
-
@Mauerwegler
Suunto has field testers -
@Mauerwegler Suunto knows various stories and there were issues reported by the testers that didn’t get fixed prior to the release.
Apparently it goes beyond “they didn’t know” and certain issues may as well be flagged as of little importance or no importance. Or may be as well be a feature instead of a bug. For example - the nag I’ve reported in S5 in regards to being stationary and having no compass - it was badly implemented in my opinion, but might have been left in the firmware intentionally, as maybe most users didn’t understand that the direction won’t update when stationary (although I’d argue that if one owns such device, it’s not necessary to display the message every time). Or the buzzing in S9PP - I’ll be surprised if it ever gets addressed.
There are priorities and company priorities are different than mine or yours.
-
S sartoric referenced this topic on 14 Apr 2024, 16:02
-
@Łukasz-Szmigiel Lukasz hello, I think you are wrong. I had a Suunto 9 baro where I created my own cycling profiles and it was never a problem. Every time after driving 5 km, I received information about how long it took me to drive plus the average speed. In S.Race it only works in predefined profiles in the watch. When you create your own cycling profile, the average speed is missing.
-
@Durri Hi, maybe I am wrong but I think that the reason is that it works as a mode with a power input (or at least it’s expecting that you have an powermeter connected). That’t why you have an average power field in there. I am not sure how to change it, do you have a powermeter connected to the watch? Maybe it would need to be disabled before the activity starts… I will check it.
-
@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.