Suunto Vertical: Bug Collection
-
@BrunoH thanks for your replay and I guess you are right. I’ll just have to wait for the successor of the vertical come. Thanks.
-
Hi, since the last update the HR sensor sometimes stop working when I am not wearing the watch (no data and the light are not blinking). In order to make it work again i have to perform a soft reset.
-
@Bouli35 that’s weird, it’s a problem I had months ago and it’s fixed now.
-
@BrunoH so i followed the resources a little bit more and as I can tell there are no tweaks made by Suunto that have changed it for me. It still goes up to 99 every morning no matter what I do. But since Suunto is not using their algorithm in their new watches after the vertical a suspect it will never change and it is what it is.
-
@Artus-Diver Hello Artus, for your information, since I added the 1km autolap when I swim with my Suunto Vertical I no longer have any problems with inconsistent durations in my swimming sessions. I also find that the stroke detection is slightly better. Is it better on your side?
-
Hey all,
When using other sports outdoor (sport non précisé outdoor), the elevation recorded by the watch is very unstable.
For example, from yesterday hike which was 3km with 250m d+, watch give me more than 800m of d+.This has been observed with other activities.
When using Hiking sport mode, elevation is spot on.
Why is the elevation not correct when using other sports outdoor ?
-
Just had the new firmware update and since then, I have a quick black screen of around 1 sec before showing activities when pressing the up button from the watch.
-
@darxmurf
It’s related to the watch face, when you are waking the watch up.
Some have this glitch.
https://forum.suunto.com/topic/14081/lag-black-screen-on-k14-marine-compass-wake-up-after-2.48.16-update/9I’m using the good’ol “classic analog” and it works normally
-
@sartoric thanks for the info. Waiting for a fix then
-
The last two updates were happening against my will. I have automatic updates turned off, and I always check because every subsequent update turns it back on. Has anyone else experienced a similar incident?
