Conclusions about the Suunto Vertical

[EzioAuditore]

@Tieutieu I did not have a crash on simple sessions such as: yoga, core, weight lifting and bike commuting. No external sensors on these sessions except twice while biking just to confirm that the OHR while biking is not accurate at all (very low same as the Baro).
Other than that I have not had a crash for 2/3 of the runs. These were when I have Endurance sessions or Recovery where the Training Peaks Guide (I always use this) do not have a lot of ‘interruptions’ laps. Whenever I have interval training and the guide should do an auto lap I either get a crash or the last interval gets stuck at 0m and it does not progress. This happened to me yesterday. After advancing the screen upon returning to the TP Guides the screen was blank and I thought that the watch crashed again but when I pressed the middle button to switch screen it went to the next S+ app (aerobic decoupling).
So I have narrowed the problem down to interval sessions with TP guide. The auto lap is only accurate in the first 2, 3 intervals and then it slowly starts to lack prompting you for the next 100 meters when in fact I’ve run 150 and so on.
When running I always use External HR (Polar Verity Sense or Garmin HRM Pro - connected to the Apple Watch simultaneously). Recently I paired and started using Stryd foot pod (but I had crashes without it as well).
The rest of the settings on the watch are not changed a lot:

• English language,
• Backlight same as yours,
• No alarm and sounds on button press,
• HR: 24 with sleep tracking and auto disturb on during sleep, SPO2 On,
• Widgets: All except of Media Controls,
• Apps: TP Guides (always) and once the 2 S+ app was enabled I switch between Fat burn and Aerobic decoupling (depending on the session).
• No custom modes used. Always default ones,
• Maps on,
• Unlocked always during activity,
• Depending of the activity I set either Power Zones or HR zones (mostly use HR). But during crashes I did not had HR zone since I was doing intervals.
• Occasionally when endurance or recovery I add as a target the distance I have to go.

Cheers.

[Egika]

@Hristijan-Petreski did you happen to send logs from the app within a few hours after a crash? If yes, please share the time when you sent it together with your SA user name with me or one of the admins in a private message.
This will definitely enable devs to take care of whatever causes the trouble here.

[EzioAuditore]

@Egika Before hot fix I always informed @isazi. With the hot fix I contacted support sending them logs (Time and User included) but they just ignored me saying if I do not provide them with the Log ID (long number) they cannot help. Once I persisted that there is no more Log ID (at least not from Android app) they said they will ask the responsible compartment and I will get an email informing me of the ticket and how to ‘correctly’ send logs: I never received ticket number nor any email.

[Egika]

@Hristijan-Petreski wew - anyway, as you know the procedure, it would be great if you could do as before. This way isazi or me could open a ticket with your information right away.

[trailcafe]

@Hristijan-Petreski
Have you tried to do a full reset (Settings - General - Reset settings)? Maybe it is worth a try…
I had to do it with a pre-release FW version and it solved some issues, maybe it can also fix the crashes for you.

[EzioAuditore]

@trailcafe I always did soft reset. Today I will do hard as well and see how it goes. @Egika will do thanks.

[EzioAuditore]

So after hard reset and one interval run things were rather normal (as it ought to be). I basically threw everything at the watch:

• TP guide for VO2Max session 16 km: 1km warmup (6 x (400m all out with 100m cool down) + 2km in zone 1) x 3 times
• Second S+: fat burn
• Navigation: Snap to route without turn by turn
• Target: 16km
• HR belt
• Foot pod (stryd)

All was good except my VO2 that tanked 3 units 51 to 48 so now it will take some time to get it up again (thats what she said)

I have spotted one unusuall suspect for making the guide start lagging by 10-20 meters:

Say you start the intervals 400 + 100 on the second time and as you hit the exact kilometer you get 2 notification: one the auto lap from the watch and the other the lap of the guide if you happen to reach the 50% thumps up then it is 3 notifications in a row. This makes the guide start lagging. I do not know if this is an issue or i should disable auto lap when doing guides?

@isazi & @freeheeler maybe something you can keep an eye for Thank you again both of you. I will report if this start deteriorating again.

Have a nice evening and rest of weekend.

[EzioAuditore]

One question related to the hard reset. After the reset the Suunto Coach 6 week average shows: no data. Isn’t this data supposed to come from the Backend? Or it comes from the watch? Thanks!

[EzioAuditore]

So the most ridiculous piece of tech I own at the moment (or ever) has crashed for the 6TH TIME!!! In 2 months 6 crashes. Let’s send logs again.
Crash happened 13:00 - 13:02 (In between this interval). Logs sent at 13:37 CET.

I apologize publicly for criticizing the bugs at Garmin. Apparently there are much worse bugs (if SW related). Cannot believe the company I sweared on from the most robust has delivered such a bad experience (I had crashes with the Baro too so I guess this has been long in the making).

Downvote my post as much as you like. I’ll be sending last letter to support after which I will look into alternative methods and preferences.
Have a nice day all.

[Łukasz Szmigiel]

@Hristijan-Petreski I don’t get it why you’re upset on being a beta tester of a premium watch

[EzioAuditore]

@Łukasz-Szmigiel I am the most upset at myself at the moment But hey we humans learn from our mistakes. This was an expensive mistake but I will learn something out of it.

[zhang965]

@Hristijan-Petreski said in Conclusions about the Suunto Vertical:

So the most ridiculous piece of tech I own at the moment (or ever) has crashed for the 6TH TIME!!! In 2 months 6 crashes. Let’s send logs again.
Crash happened 13:00 - 13:02 (I between this interval). Logs sent at 13:37 CET.

I apologize publicly for criticizing the bugs at Garmin. Apparently there are much worse bugs (if SW related). Cannot believe the company I sweared on from the most robust has delivered such a bad experience (I had crashes with the Baro too so I guess this has been long in the making.

Downvote my post as much as you like. I’ll be sending last letter to support after which I will look into alternative methods and preferences.
Have a nice day all.

Welcome to suunto community.

We only truth our great suunto testers:

[EzioAuditore]

@zhang965 This is not really helpful although I know what you aim at. At the beginning I was ignoring it but I cannot say you are not right.

[surfboomerang]

@Hristijan-Petreski I still can’t figure out why some of us have crashes all the time while other never have crashes. I owned a S9B, S9P en now the SV. None of them ever crashed.

Suunto…if it is something of a magical mix of settings, please let us know so people can disable/change the conflicting settings and enjoy the watch without crashes.

[Łukasz Szmigiel]

@Hristijan-Petreski just kidding of course. It’s a pity that you’re having poor experience with Vertical.

I think that there’s something worrying going on with recent Suunto approach to firmware. Especially when the new interface has surfaced with 9PP and now, with Vertical. Old bugs being ported to new devices, some bugs not getting fixed for months, strange ideas for critical functionality like the backlight being changed between versions.

Yes, new features are awesome but if I was to choose - I’d choose stable and polished software than the one having lots of bells and whistles.

[Łukasz Szmigiel]

@surfboomerang it’s a complex device with a complex firmware. It’s impossible to test throughly with a small group of field testers. Never before there were maps or an interface so heavily dependent on JS in a Suunto device. Also, plenty of S+ apps now with ability to switch them during the workout.

[A Former User]

@Łukasz-Szmigiel said in Conclusions about the Suunto Vertical:

I think that there’s something worrying going on with recent Suunto approach to firmware. Especially when the new interface has surfaced with 9PP and now, with Vertical. Old bugs being ported to new devices, some bugs not getting fixed for months, strange ideas for critical functionality like the backlight being changed between versions.

I completely agree here, the update for the 9PP made me to put in a drawer & for sale and switch to FR255. Also reading this forum, Facebook groups etc made me completely forget about getting a new Vertical in the future. I mean why would you take away such a useful feature like raise to wake during activity only? Who asked for this? They still have only 1 alarm option in 2023 and they’re “improving” the already good and working functionality? Who cares if they have the best battery on the market if the watch crashes after 30 minutes of activity? And why would they deploy to production a version with a lot of known and reported bugs? Also about the beta testers, we’re not really beta testers. Yes, some of us installed the FW manually and I’ve expected a few bugs, but I never expected that the exact same buggy version of that firmware will be published as production to all users after a few weeks. Especially since this watch(9PP) did not get an update since the end of November 2022.

Kudos to Suunto designers, the watches look and feel good, but IMHO that’s all about them.

[EzioAuditore]

@Łukasz-Szmigiel I don’t know mate…. If external apps (plugins or Suunto plus apps as we call ‘em) crash your core than the problem is in the core SW rather that the apps. As I said, first I thought it was the laps of the TP guide (intervals) but this was not the case twice, so it’s not. I would also appreciate if there was a statement: hey do not use 2 apps or something else so I would know how to set the watch. All they do is they ask a logs from me (support) and then tell me the logs are not good and so on… I had better support experience with literally every other company. First time I have to contact the company I loved and I face the harsh reality others have been pointing out and I was telling them: hay it cannot be that bad! (I am really sorry and ask for apologies from these people). Today I might’ ve sounded harsh and not as I usually do, but there was a lot of fun made out of me and my Suunto and I had no arguments to say anything. A pity really cause I invested quite a lot in the whole ecosystem (Karoo, straps and years of persuading others to get Suunto). Well I guess I’ll have to wait for a better looking AW Ultra or some Forerunner at the end ;(

[A Former User]

@Hristijan-Petreski said in Conclusions about the Suunto Vertical:

@Łukasz-Szmigiel I don’t know mate…. If external apps (plugins or Suunto plus apps as we call ‘em) crash your core than the problem is in the core SW rather that the apps. As I said, first I thought it was the laps of the TP guide (intervals) but this was not the case twice, so it’s not. I would also appreciate if there was a statement: hey do not use 2 apps or something else so I would know how to set the watch. All they do is they ask a logs from me (support) and then tell me the logs are not good and so on… I had better support experience with literally every other company. First time I have to contact the company I loved and I face the harsh reality others have been pointing out and I was telling them: hay it cannot be that bad! (I am really sorry and ask for apologies from these people). Today I might’ ve sounded harsh and not as I usually do, but there was a lot of fun made out of me and my Suunto and I had no arguments to say anything. A pity really cause I invested quite a lot in the whole ecosystem (Karoo, straps and years of persuading others to get Suunto). Well I guess I’ll have to wait for a better looking AW Ultra or some Forerunner at the end ;(

It won’t solve your problem, but if you think the watch is not up to standards send it back, get your money back and enjoy the rest of kit you have that will still work with either your previous watches or other brand. Life is to short to be annoyed with something you paid for.
Even with logs and stuff, any brand can’t solve this “from one day to the other”, specially because they need to test it to make sure it won’t happen again. (I am not trying to defend Suunto on this). Also companies are not perfect…

The rest is just your expectation vs reality. Enjoy outdoors.

[EzioAuditore]

@André-Faria I think that was the the first hot release aimed at. Since at some point I was not sending logs cause the hot release is around the corner solving the crashes. I did not complain at all the first 4 times and also defended Suunto when others experienced crashes. But how can I stay positive when I cannot rely on something that should be robust and do the thing it’s supposed to do and costs this much? Will you be cool if while you talk your mobile crashes 40% of the time so you lose maybe important calls or whatever?! ‘Get your money back’: can you please tell me how can I communicate this to Suunto’s support without involving lawyers and what not (cause I’ve tried believe me). I will continue using the Baro until it’s done and then bye, I have no problem to switch to other brand but word of mouth spreads quite a lot in the training communities (and nowadays social cycles) so at the end it will not be me who suffers most.