Suunto Vertical: Bug Collection

[BrunoH]

This morning I experienced my first bug: SV woke me up at 7:00, but the watch screen was frozen and showing clock face at 6:59. The alarm kept buzzing and buzzing and none of the buttons worked. It kept doing this about 20-30 seconds, then it rebooted and came back to life showing my sleep summary screen.

[Jonathan C]

@Egika according to this page, aren’t we supposed to “use the lowest heart rate reading measured during your sleep as your Rest HR”?

[jjpaz]

@Antoine-Lancrenon Same here today. I woke up and the touchscreen was not working.
Also my battery level was 18% and I received the advice to connect to charger so, I have connected the SV to the charger and (oh! surprise) watch has rebooted himself…

New bugs before the “no issues” software??

Many “little” and random bugs, will be corrected?

[Maryn]

@jjpaz today I had a 20% drop over night. New device.

[EzioAuditore]

@Marcin-Byrtek I think the first few charges the battery ‘calibrates’ and the 20% drop is not actually ‘true’.

[Brad_Olwin]

@jjpaz It is possible the battery was lower than indicated, the touch was turned off. When very low these types of batteries can deplete quickly. So this may not be a bug as your watch may have shut down once on the charger.

[jjpaz]

@Brad_Olwin It didn’t turn off, it restarted. I didn’t touch the watch. And battery level when charging started from the level it was before restarting, 18%.
So, it’s not a bug but watch didn’t show the correct battery level? Is that right? So, according to this, I can’t trust the battery level the watch shows. Perfect!
I think the answer is easier: there was some issue that cause the touchscreen not working and the reboot.

[Brad_Olwin]

@jjpaz Could be. I’m not sure. Was just a suggestion.

[mikekoski490]

Just thought I would pop this in here, as I know some people have said “Im thinking of switching to Polar!” Just to put the big ecosystem of all watches have issues in perspective. Taken from the Polar users FB page:

Users of Polar Vantage V & V2 and V3.
· 2h ·
3 times during training my new V3 crashed (needed to setup as new device afterwards) - App and watch on newest release. Anybody experienced similar issues?

[ChrisA]

@mikekoski490 Polar watches were quite basic, relating to features (even less watch faces, no loadable apps, only four data fields and limited data to display etc.) But (at least mine) were running extremely stable! Could be, that with more and more features added, chances raise, that more and more things could go wrong. I recall somebody with IT background here in the forum saying, that adding a little bit here and a little bit there might sound easy to do, but isn’t so easy in reality .

[jjpaz]

@Brad_Olwin Thank you for the suggestion.
I explained the issue just for help if anybody suffers same behaviour.
For me, in case of that, is just a small bug because it hasn’t happened during activity.
“During activity” crashed are the worst issues (only happened once in more than 5 months using SV)

[jjpaz]

@ChrisA Sure. New Suunto watches are becoming less stable since SuuntoApps inclusion and since maps inclusion. New features working together can cause random behaviours.
In that case the optimal way is to be able to detect and correct that issues and fast.
Let’s see if the promised software update is worth waiting for.

[inkognito]

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

[pilleus]

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 …

[Egika]

@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?

[pilleus]

@Egika

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.

[Egika]

@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

[pilleus]

@Egika

I can see differences if I know where these are …

1 and 2 in “outdoor”
3 and 4 in “dark”

[LitchiMonster]

@LitchiMonster the intensity zone screen still does not work properly with latest firmware, as described in my previous post, if anyone was wondering

[Michaël POINTEAU]

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).