Suunto Vertical: Bug Collection
-
@jakubdr was Strava already connected before the run ?
-
@Dimitrios-Kanellopoulos Yes, it was the first thing I did during the initial setup as well as the TrainingPeaks connection. Manual .fit export and import to Strava worked, it just did not sync automatically. I will try to reconnect it before the run tomorrow if I can replicate the issue or to see if it resolves it.
-
@jakubdr Do not reconnect if possible. just do a fake activity
-
Not really a bug but some minor improvements:
POIs do not appear on the map when map only is started.
POIs do appear on the map in an activity, but only as white icon which makes it very hard to see against the outdoor map style. Almost impossible actually. I would suggest a black outline around the icon like in the Suunto app. -
@Likarnik Same here. Tried to configure Power Zones and was not possible and watch get stuck in that menu.
Solved by soft reset. -
Today I also had a crash during an activity. After 1km run the clock restarted. Suunto needs to improve quickly.
-
@Kurt68 Uff something I don’t like hearing
, as I have a marathon on Saturday and Vertical is now my only watch… -
@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?Suunto T3D, Suunto Spartan Trainer, Suunto Spartan Ultra (retired), Suunto 9 Baro (retired), Suunto 9 Peak (retired), Suunto Vertical Titanium Solar, Suunto Race S.
-
@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.
Suunto Vertical Titanium Solar
OnePlus Nord 4 -
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
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@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
Suunto Ocean
Suunto Vertical Solar Canyon
Suunto Ambit 3 peak Sapphire -
@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.
