Suunto Vertical: Bug Collection

runomatic

After all that negative feedback, i’ve got a positive one: Went out for a 25k run with just 7% battery left. Coming home with 4% after 2:40h. Call me Mr. Brave!

freeheeler

@runomatic
going out on 7% is living on the edge

seanvk

@Simon On the subject of the widgets. One item I would add to your mentioning of HR and spO2 is that I think they should entirely avoid putting the widgets in a pipeline so to speak. Not just because of the lag, but there is no quick way to get to the one you want. Instead, they should have the following flow:

middle button or side swipe -> list of widgets with some partial information.
top or bottom buttons, scroll up or down
middle button select for more detail

I just really dislike the side scroll for the widgets and coupled with the lag, it’s not a very good experience just to get to one widget you wanted to look at in more detail

A Former User

@seanvk Like Garmin you mean? Would make more sense imho.

BrunoH

@seanvk my solution was first to hide the ones I never use. Then I arranged the remaining ones so that the most used widgets are next to the watchface, left and right.

I don’t think Suunto will abandon their chosen UX and replace it with something copied from the rivals.

Having said that, I’d really like to see Suunto solve the lag…

A Former User

Btw. that 9pm thing about the Week Report was true. lol

Frederick Rochette

@runomatic On Saturday, I also had 7% left and after going out for a 2-hour run, I also had 4% left.
After completely discharging the watch on Saturday, I recharged it to 100% at around 11.30pm. When I woke up at around 8am on Sunday morning, the watch was at 98%. I went out for a 2-hour run and only 92% remained (6% for 2 hours…).
So battery consumption seems to be random… because one 2-hour run = 3% and another 2 hours = 6%.

surfboomerang

@Frederick-Rochette I don’t know if this is some kind of calibration. I noticed similar behaviour.

I charged the watch in the evening but it wouldn’t get over 99%. Next morning it was at 97%. I did a 1:30hr sunny run and it dropped to 95%.
That afternoon I had a 2:30hr car trip where sun hits the watch a lot, but never full bars. Suddenly the watch was at 100%.

Normally it took approximately 1hr of full bars to charge 1%

Next day I did a 2:30hr hike and the watch is down to 93%. I did noticed I left one S+ app active so I don’t know if that was the cause.

freeheeler

@Frederick-Rochette
always same settings?

isazi

@babychai no updates, it is not a firmware thing, I believe the maps do not have contour lines for Malaysia at the moment. It probably needs an update of the map. Before release most non European maps had not contour lines.

babychai

@isazi oh okay, thanks for the info~

Mff73

@Frederick-Rochette said in Suunto Vertical: Bug Collection:

So battery consumption seems to be random… because one 2-hour run = 3% and another 2 hours = 6%.

not random, but non linear.

Etienne Gardea

Hello, my map of Normandy during trail session sometimes appears and sometime not ? I have download the map on my watch. I don’t understand this bug. Somenone have the same ?

sartoric

@Etienne-Gardea
yep, just search this topic for “black map”

Tieutieu

@sartoric said in Suunto Vertical: Bug Collection:

@Etienne-Gardea
yep, just search this topic for “black map”

As @sartoric said, it’s been discussed for a while. The hotfix to come should fix it.
It’s most likely related to routes sync. Just go to parameters/general/stop the watch. Stop it. Start it. It should solve.

A Former User

This morning my watch rebooted during a walk. I was using a custom sports mode. Until recently I’ve used only stock sports modes, decided to customize it a bit. No custom modes for me, I guess

surfboomerang

@tomasbartko I doubt it’s the custom modes. That is the only mode I use for all my sport profiles and I never had a mid-activity crash on all my Suunto watches

EzioAuditore

Donwnloading 2.25.64.6205 now

Ivan De Rasis

@Hristijan-Petreski

A Former User

@surfboomerang I haven’t changed anything else. And it happened for the first time since I got them (16th of May).