Conclusions about the Suunto Vertical

freeheeler

@Sascha-Domres
if I may chime in here… our forum friend @mikekoski490 also had issues with maps, far away from germany. my wild guess, it is coincidence and difficult to test. also difficult to verify before travelling.

please see the below link with a brief description what to do if restarting the watch doesn’t help. this is all we can do to support developers to improve maps
https://forum.suunto.com/post/123379

Mff73

@Sascha-Domres
Maybe it is not the map itself, but a sum of other circumstances which leads to map not displayed (and of course I really don’t know ).
I had once, no map with previous/initial FW: restart of watch solved it, and map is still the same.
My personal case, just that.

Brad_Olwin

@Sascha-Domres I have tested this in six different regions so far in the US and will test in Europe next week. So, I think somewhat isolated but clearly some regions or some type of watch usage is an issue.

Tieutieu

I also had few no map issues with first firmware. Soft reset didn’t solved, but stopping/restarting the watch did. Since then not a single black map. Have use it in different regions (different maps)

trailcafe

@Brad_Olwin where will you stay in Europe? Doing a race here?

gone troppo

My maps here in Australia whilst taking bout 10 hours to download worked great recently on an off trail hike and got us out of trouble many times including leading us out of the rainforest at night with headlights everyone in our group loved my watch by then end

EzioAuditore

Black maps only in the beginning but I’ve been gifted with 4 crashes mid activity. One with the latest hot fix

A Former User

I’ve shelved the Vertical for now, as I find it too unreliable. It also gives me the chance to let it drain completely for once.

fluca

@Brad_Olwin I agree 100% with you because what you say make sense for me. But it seems to me is not related to my post you are replying or am I missing something?

zhang965

@fluca said in Conclusions about the Suunto Vertical:

Brad_Olwin I agree 100% with you because what you say make sense for me. But it seems to me is not related to my post you are replying or am I missing something?

That’s normal, dude, it’s his style,

Welcome to Suunto community

A Former User

@Brad_Olwin said in Conclusions about the Suunto Vertical:

@Sascha-Domres I have tested this in six different regions so far in the US and will test in Europe next week. So, I think somewhat isolated but clearly some regions or some type of watch usage is an issue.

Or yours is the one that works hehe

Brad_Olwin

@fluca This was your statement about degradation in reliability and chasing Garmin by Suunto.

Brad_Olwin

@trailcafe No. here for work and a very short visit.

Brad_Olwin

@Ilya-Sul said in Conclusions about the Suunto Vertical:

I’ve shelved the Vertical for now, as I find it too unreliable. It also gives me the chance to let it drain completely for once.

This should not be happening. I did not have a single crash on your firmware version and that included a 34h race. Please send logs to Suunto immediately after a crash and PM me with Suunto app username and time/date logs were sent

Brad_Olwin

@André-Faria said in Conclusions about the Suunto Vertical:

@Brad_Olwin said in Conclusions about the Suunto Vertical:

@Sascha-Domres I have tested this in six different regions so far in the US and will test in Europe next week. So, I think somewhat isolated but clearly some regions or some type of watch usage is an issue.

Or yours is the one that works hehe

I have 2 Verticals. Neither have serious issues but one is older hardware and has some problems specifically related to the hardware. However, no crashing or map issues.

A Former User

@Brad_Olwin said in Conclusions about the Suunto Vertical:

one is older hardware

I’m sorry, just curious, what do you mean by “older hardware”?

Brad_Olwin

@Dan-Cantir Prior to release.

fluca

@Brad_Olwin I mean, I owns a S9PP which was seriously buggy (and it is yet), I’ve owned a SV form 1 month and it was buggy for some (not for me) at release. I have been with suunto since 2014. Since then, at release, suunto whatches just used work. Now we have a dedicated tread for bugs.
We also have a (kind of) beta program to see if the software is good enough to be released in production. This is all new for suunto and similar to what garmin does.
Something has shifted. I am not saying is necessarily bad. I am not saying it is suunto fault.
To stay in business, you have to play that business’ rules. In this business Garmin has 30% share, suunto in not listed. Garmin make rules, suunto follows.
This should not be taken as an offense. It is what it is.

Egika

@fluca to correct you:
I had a Suunto Spartan Copper back in 2015/1016 which resetted on me during a triathlon

The situation changes with more complexity. Like what car companies have gone through at the end of the last century. They dealt with it using HIL automated testing.

zhang965

@fluca said in Conclusions about the Suunto Vertical:

Brad_Olwin I mean, I owns a S9PP which was seriously buggy (and it is yet), I’ve owned a SV form 1 month and it was buggy for some (not for me) at release. I have been with suunto since 2014. Since then, at release, suunto whatches just used work. Now we have a dedicated tread for bugs.
We also have a (kind of) beta program to see if the software is good enough to be released in production. This is all new for suunto and similar to what garmin does.
Something has shifted. I am not saying is necessarily bad. I am not saying it is suunto fault.
To stay in business, you have to play that business’ rules. In this business Garmin has 30% share, suunto in not listed. Garmin make rules, suunto follows.
This should not be taken as an offense. It is what it is.

Come on dude, it’s just a watch, take easy.

I’m very happy with vertical now, I don’t use s+ app, don’t use map, don’t use OHR. It can perfectly run without any issue for a 10k run.