Suunto Vertical: Bug Collection
-
I have discovered a problem with structured workouts. When I select the “press lap button” option to complete a particular part of the workout, it does not work in practice and during the workout the watch does not move to the next scheduled workout part. I’m not sure if it’s the watch’s error or an app bug, but it worked fine on the S9PP.
-
@aroo7 I already described that behavior here:
-
@Mitch9 sorry I didn’t notice your post, thx
-
I found missing ‘track/terrain profile’ on custom trial run.
If I select track ,on the default trial sport , I can see additional screen with terrain profile.
If I do this same using my custom trial , I can’t see it. it is missing. Going to the options ,selecting again the track resolving the problem.Below link to recorded situation.
-
@greku
I can’t replicate that. tried with different trailrunning modes (default) and with custom trailrunning mode, also with different battery modes.
do you have something else setup or enabled? -
@greku
if you are motivated, try to delete your custom sport mode, and recreate it and check again.
I don’t have the issue neither today, but i had quite same phenomenon some weeks ago (before the recent updates) when selecting a route before launching the activity didn’t seem to really select the route (thus, no elevation graph). -
@freeheeler Mostly default …
@Mff73 I created new trial running mode , the problem is still here. Selecting track after starting activity resolving the problem (terrain profile) is at additional screen. -
@greku
did you update with latest firmware ?
is it doing the same with another route ? -
@Mff73 yeap. Im on 2.25.66
I checked other tracks and it is this same. Bleh
Edit. I found solution.
When Im starting my run I need to first choice my track, then change battery mode from ‘nonstandard’ to ‘performance’ … -
Ok, some odd behaviour here today. Not sure of it’s a big or a feature.
Did some windsurfing today. Not a normal session, but a day full of races. Normally I use the custom battery mode to turn off the screen after a few seconds but since this was race day, the sail race timer app could be used.
Because I didn’t want the screen to go off during a start, I selected Performance mode for the activity. I noticed this also enables wrist HR so I scrolled down to the wrist HR setting and turned it off. Then I started the activity and noticed that the screen went off after a few seconds.
Viewing the options during the activity learned that the battery mode switched back to Custom somehow. So I selected Performance mode and noticed that wrist HR was enabled again also. But this time I wasn’t able to turn it off mid-activity. The wrist HR option is missing at that moment and switching to Custom battery mode didn’t disable it also. I ended up measuring HR data the whole day because I couldn’t find a way to turn it off during the activity.To me it’s somewhat confusing if the wrist HR is controlled by both battery modes and separate switch in the options list.
Another finding has to do with the sail race timer (5min). I pressed the lap button on the 5 min mark. It counts down to 0 and then shows some other values. All fine.
(Side note: making the countdown time variable would be great. Now I only have an app for 5 or 10 min starts.)Today there were multiple starts in a row and that’s where I found out I was unable to reset the countdown timer for a second start. The workaround I found was to disable and enable the app and press the lap button on the 5 min mark again
Also the battery drain problem with S+ apps was clearly visible. 21% in 3:30 moving time (around 5hrs of total time with breaks)
Normally it is aroud -5% for 3-4hrs. -
S surfboomerang referenced this topic on
-
Not sure if this is a bug. Went for a hike for nearly 2 hours. The activity log says I burned >900 kcal but the activity widget, despite counting the steps has the kcal wrong - it’s showing a number under 900. Not sure how this is possible where one metric counts the activity and the other either doesn’t or does a calculation different to the activity, which also makes no sense.
-
Another bug that continues to plague is the sleep. I agree with DCR on why in todays world we still need to input a sleep window, but hey-ho. I have my sleep window set to 10pm to 7am. I had set the watch on the shelf around 20:30 and picked up again around 22:00. I had plenty of button presses as I set the alarm. However when I woke up the next morning, the watch measured sleep from 20:30. Not sure how that is possible when it isn’t even able to measure HR. Seems rather odd but I know this feature has been an issue for me for years.
-
My Vertical has been struggling lately to detect the start of sleep. I have sleep tracking window set from 9.00 to 7.00. I usually go to bed between 10 and 11 and have alarm set up at 6.00. I had RHR set up as 7 day avg. min. HR + 10 beats as some suggested as a rule of thumb in the forum. Today, I changed RHR to 7 day avg. min. HR (I think it is according to SV instructions) and I will see if it makes any difference. Is there anything else I could do about sleep tracking or it depends on the person characteristics? Are there any improvements planned on sleep tracking? I remember my S5 and S9P tracked sleep duration quite well. Thank you all for any tips.
-
Please, if you have bugs now that the hotfix is released, create a separate post. This topic has 516 (and counting) posts already, and it is impossible to follow.
-
R runomatic referenced this topic on
-
Major Bug
When training in the map view, the watch completely crashes. Then there is an automatic restart. Crashed twice in the last 4 days supported (4 training sessions)!!!
Please fix the problem quickly -
@steiner how is your sportmode configured? I use the map a lot and never had a crash. Also enabled any S+ app or guides?
-
B bubuche referenced this topic on
-
@steiner Next crash send logs to Suunto and record date and time logs sent. Then PM me with the above information and your Suunto app username. I will file a bug report.
-
Here are the 3 fit files. Du you need something else?
95% i do not use the maps.19.06
64a5595cf1dd6f55c1bea9f5.fit
04.07
64a410068494c46fa44255f3.fit
05.07
649000724c0b4b07d5ab21b6.fit
-
@steiner What we need are log files sent as soon as possible after a crash. Then PM me or @isazi or @freeheeler with your username for the Suunto app and the date and time that logs were sent to Suunto. The files may or may not help the developers.
-
🧐 bug??
img-2607.mp4
