Suunto Vertical: Bug Collection
-
@Ketoohs I also run a marathon on Sunday only comfortably, but I would still not like to see it happen at the competition.
-
Yesterday, first run with my new Vertical, I found another “surprise”: “The Schödinger’s Suunto+ Screen”.
I selected one Suunto+ App before start the activity, Training Peaks Rythm, and started the activity. I switched between screens and didn’t find the S+ screen.
In the middle of the run I accessed the Menu and verified that S+ App was selected. I went back to activity and from that moment the S+ screen was showed…
At the end of the activity all the S+ App was recorded from the beginning of the activity so it was working but without its own screen.
Also, my screen was in “white” mode and the “TP Rythm” screen was showed in “dark” mode, is thar normal? In S9P S+ screens are showed in the same mode (white or dark) that all the other screens, isn’t that? -
@Kurt68 What I am thinking is that I am going to use the basic running mode from Suunto (despite creating a custom mode), and not including any S+ apps.
Just so I minimize the chance of something happening.
-
@jjpaz this is also known
-
@Kurt68 I did 2 runs with everything enabled (GPS performance mode, 2 S+ apps, navigation etc) and everything went very smooth.
Oh, and I use a custom sport mode. Not the basic running profile.
-
Ieri ho provato il mio Vertical Lime/Black, funziona tutto in maniera egregia… L’unica cosa che non mi ha calcolato è il valore di V2O nonostante abbia corso per 40 minuti in zona aerobica/anaerobica
-
@surfboomerang for me it was the 3rd run. The first 2 worked perfectly. But I’ve already read here that I’m not the only one where the vertical crashed.
-
Maps: Downloaded one US state overnight - Nevada. Maps not visible. Powered on/off device. Maps not visible. Only black screen, no grid. Watch is trying to get fix.
After you download a map region, do you have to get a gps fix to see the map or can it use your last known location? I had a fix before last night so I thought it would use that.
Default HR Zones: set running HR zones first. Came back to Default HR Zones and only Max HR rate was set. Rest was — for HR and n/a for percentage. Powered on/off device. Default HR now filled in.
-
@seanvk to see maps you need a GPS fix
-
@isazi Worked! Thank you
-
Did couple of steady runs, 30min, HR135-140 all was good except in each of those runs there was couple of peaks where HR jumps to 170, stays there couple of seconds and comes back to 140
-
@vlado said in Suunto Vertical: Bug Collection:
Did couple of steady runs, 30min, HR135-140 all was good except in each of those runs there was couple of peaks where HR jumps to 170, stays there couple of seconds and comes back to 140
Can confirm, the same happened today to me (at one time it showed 210, which is not even my cadence, so it could not have locked to it). Also it seems that it has slower reactions to sudden spikes (e.g. uphill running).
-
@Dimitrios-Kanellopoulos said in Suunto Vertical: Bug Collection:
@jakubdr Do not reconnect if possible. just do a fake activity
Second time was the charm. Very slow to upload though.
-
The raise-to-wake feature is a little bit overreactive. Minimal movement enables the backlight. It also seems that the watch is ignoring the light sensor. Even with bright light the backlight is still enabled sometimes.
-
Just checked my HR zones:
I set them on initial setup 3 days ago, I wanted to tweak some values…
-
@vlado said in Suunto Vertical: Bug Collection:
Did couple of steady runs, 30min, HR135-140 all was good except in each of those runs there was couple of peaks where HR jumps to 170, stays there couple of seconds and comes back to 140
I get an opposite result, running above 170, hr back to 140.
-
@Likarnik
Did you reset the watch ? -
@sartoric yes, it worked like 3days ago when setting power zones (post earlier in this topic). Just posting info for devs, not sure if root cause is same for all zone types… I hope hotfix will get rid of all those bugs.
-
Excessive battery drain of approx 5% per hour when using S+ apps (Decoupling & Fat Burner). First noticed after a run that the battery percentage was suspiciously low(er) after a 1 hour run. Tested it again yesterday - during a bike ride - with both S+ apps selected the battery drain was 5% per hour.
Additionally neither of the apps functioned correctly as they were selected after the start of the exercise. Decoupling was waiting for the start of the activity and Fat Burner was not adding up any energy expenditure. As a side note - For the before-mentioned run both of these S+ apps were selected before the start of the exercise and seemingly functioned as intended - but the battery drain was also present.
@isazi, has this been noted or should I open a new thread?
-
@surfboomerang
you can set it from high to low and it will work as we are used to