Suunto Vertical: Bug Collection
-
Cute little bug (or perhaps take this as suggestion for improvement):
When I use sunrise/sunset field on the “altitude-chart” watchface, it automatically switches to sunrise field after sunset. This is pretty cool. But it shows “today’s sunrise”, not “next sunrise”. Before midnight, you are looking at the outdated sunrise time which can be several minutes behind/ahead…
E.g.
Yesterday at 23:59, it showed sunrise 7:04 (= outdated one)
Two minutes later at 0:01, it showed 7:06.Could this be improved to always show the next sunrise? Nitpicking, I know
-
Style selection “dark” in map settings does not differ from “outdoor” in my Vertical. Maps are working fine and without problems though. Reboot or soft reset does not resolve it.
Just to report it, I didn’t read all the topics about offline maps …
-
@pilleus said in Suunto Vertical: Bug Collection:
Style selection “dark” in map settings does not differ from “outdoor” in my Vertical. Maps are working fine and without problems though. Reboot or soft reset does not resolve it.
Just to report it, I didn’t read all the topics about offline maps …
thank you!
actually the first time I hear this. Is it he same after a reboot of the watch (and finally after deleting and re-downloading the respective map? -
I may be assuming something wrong … the only difference between “dark” to “outdoor” is a light darker rendering of the colors. I can see it when I zoom out to 500 m. For me “dark” means “black with white streets and dark coloured areas”.
The downloaded tile is okay and a reboot does not change anything.
-
@pilleus
Do I understand that you do indeed see differences?the difference between Outdoor and Dark on Vertical indeed is not like inverted display. Streets are white in both modes.
Just other details rendered differently:- trails are dark in Outdoor and light in Dark
- Background is lighter in Outdoor and darker in Dark
- buildings are dark in Outdoor and light in Dark
- water bodies are darker in Dark
-
-
@LitchiMonster the intensity zone screen still does not work properly with latest firmware, as described in my previous post, if anyone was wondering
-
So I believe we can call it a bug.
Laps are not reachable on watch activity logs for activities before the last update (2.30.26).
-
@Michaël-POINTEAU this is not really a bug, as it is by design.
Activities completed before a firmware update are somehow compressed. This comes with laps being not available and also the graph in the summary screen does disappear in the log book in the watch. -
@Michaël-POINTEAU said in Suunto Vertical: Bug Collection:
So I believe we can call it a bug.
Laps are not reachable on watch activity logs for activities before the last update (2.30.26).
as @Egika wrote : it always has been like this : after a FW update, details of past activities in watch logbook are no more available.
but, another question comes to me :
@Egika , with the new change where activities are stored in emmc, will the situation still be the same ? (details remaining after FW update) -
@Mff73 weird. With my Ambit 3 peak I don’t remember this.
-
@Michaël-POINTEAU
When I mean “always”, I mean “since Spartan”
And when we say “no detail”, we mean “no graphs, no zones details, no lap”, but it remains ascent/descent and some others. -
@Mff73 currently graphs still cleared with a firmware update.
-
@Egika
Rodger ! -
The clock disappeared
The optical heart rate sensor does not turn off after training. -
@ciniak77
did you try the same 4 fields view? -
@ciniak77 just exchange the average heart fiel with the instant heart rate.
The “avg” mention where it’s placed avoid time display (screen resolution) when using 7 field display. -
@LitchiMonster What is the issue, your description is insufficient “not working” is not much to go on to try to help.
-
Weekly duration has some issues on the new watch face…sometimes appears, sometimes does not.
Backlight activation had no impact on values shown. I cycled through that complication a few times and noticed that the value reappeared a few minutes later
-
@stromdiddily noticed that too once. Not sure based on what it does that.
