Suunto Vertical: Bug Collection

isazi

@stromdiddily Suunto does not often provide a date in advance, I can say that we are currently at version 2.39.40 in testing, I think the OHR bug was more hard to fix then people realize (without reverting OHR to the 2.37 branch as for the S9PP).
I would guess it is a matter of a couple of weeks.

sebchastang

@isazi no problem. I will wait and see

ggrego

rhc@isazi bonjour j’aurais juste une question pourquoi dans le récapitulatif de l’activité le tracé gps donne ceci ! et quand je veux partager une activité mon traceur apparaît avec les zones de vitesse ? Bug?

thanasis

Today I went for a run with my Suunto Vertical paired with an H10 belt. I enabled the Bleep Test and Zonesense Suunto Plus apps before starting. After about 10 minutes, I had to pause to tie my shoelaces. At that moment, the watch started beeping excessively—about every 1-2 seconds—and vibrating constantly, which was very distracting. I had to pause the activity and then resume it.

When I resumed, the Bleep Test screen showed some random numbers, and my VO2max was indicated as 27.6, which seemed off. I decided to go into the control panel, disable the Bleep Test app, and continue running. After running for another 4-5 minutes, I thought I’d re-enable the Bleep Test from the control panel.

As soon as I did that, the watch began beeping and vibrating continuously again, and the VO2max reading jumped to 59-60—an obviously unrealistic figure for me. I then deactivated the Suunto Plus app and continued my activity without it.

Later, when I synced the data with the app, the numbers were inconsistent. The watch indicated a VO2max of 44.6, but the Bleep Test app still showed a VO2max of 60, with various other stats not matching up.

Has anyone else experienced similar issues with the Suunto Vertical, Bleep Test, or Suunto Plus apps? I’m trying to figure out if there’s a known bug or if I’m missing a setting. Any advice or troubleshooting tips would be greatly appreciated!

Inge Nallsson

@thanasis A “Bleep” test is very strictly applied protocol with exact metres and seconds to finish the back and forth laps before going to the next level with a shorter time span, etc, etc. You pausing the test seems to have completely thrown it off track… In programming terms I would say that the app has no “error handling”. Furthermore, it did not even revert to a ‘zero’/‘start’ position when you re-enabled it after the different pauses. Nothing you can do except not pausing

But if you are looking for a VO2Max test, I would recommend the “Cooper test” instead. Just run a steady max pace (controlled; which you can finish) for 12 minutes.

thanasis

@Inge-Nallsson said in Suunto Vertical: Bug Collection:

@thanasis A “Bleep” test is very strictly applied protocol with exact metres and seconds to finish the back and forth laps before going to the next level with a shorter time span, etc, etc. You pausing the test seems to have completely thrown it off track… In programming terms I would say that the app has no “error handling”. Furthermore, it did not even revert to a ‘zero’/‘start’ position when you re-enabled it after the different pauses. Nothing you can do except not pausing

But if you are looking for a VO2Max test, I would recommend the “Cooper test” instead. Just run a steady max pace (controlled; which you can finish) for 12 minutes.

Thanks for replying . However the constant beeping and vibrating was impossible to cope with . I think it needs to be somehow reviewed . Not pausing was almost impossible since it was constantly beeping !!!

Inge Nallsson

@thanasis Of course. Should be fixed. Goes without saying! Though, who wrote the app in the beginning? Do the resources exist to add error handling? I think we would have to wait a long, long time for a fix.

darxmurf

Salut @ggrego tu auras plus de chance d’avoir une réponse en pausant ta question en anglais. On est qu’une petite poignée de francophones sur ce forum.

(just saying he should ask things in English as we are not much french speakers around)

Dimitrios Kanellopoulos

@thanasis asking. Thanks for the logs.

Mitch9

@Mitch9 said in Suunto Vertical: Bug Collection:

@Jugger My SV also stopped recording heart rate two days ago. It happens during night so sleep tracking stopped also.

A soft reset solved the problem so far.

Heart rate recording stopped again during night.

Jugger

@Mitch9 Mine HR measure stopped again last wednesday morning. Soft reset fixed it again.

danielgilbey

Hi all and great to see the same bugs I’m having already reported here

Could someone from Suunto chime in with a timeline as to when they expect a hotfix/update to be available to resolve these ?

As much as I like my Vertical, I’m getting more and more tempted to revert back to my Suunto 9…

Artus Diver

Swimming in the pool.

New patch and problems with this update.

The first problem that appeared was the lack of information about 100-meter laps (markers) despite them being enabled and set.

A friend had a similar situation with information about climbing, which stopped appearing after the update despite them being enabled. The day before, everything worked for her on the old software.

Another problem is the recognition of swimming styles has completely fallen apart.

The first activity today was a 1000m freestyle warm-up. SHOCK, the watch detected everything as “BACKWARD”. No kidding! I’ve been swimming for many years with SAmbit3Peak, S9B, SV and I haven’t noticed any problems with recognizing swimming styles, it worked perfectly until today. Of course, the information about 100 meters didn’t work.

The next exercise is 20x100mx20s intervals in the medley style. What the hell, what was going on here?

In short: there were 20 intervals planned, the watch showed 38. Simple math gives a distance of 2000m, but in fact it gave 1500m. A mistake of 500m.

The algorithm got totally confused when changing styles and of course it incorrectly interpreted the type of style with the lengths that were supposed to be corrected.

The next exercise is 500m backstroke. It recognized the style because I think backstroke is the priority here, but out of the planned 500m it came out to 425m.
The last exercise is 500m freestyle in rows and pullboy. Six lengths out of 20 were freestyle, the remaining 14 lengths were backstroke! 6. There were still plans for the classic, but my irritation got the better of me (…)

I will emphasize it again. I have been sailing for years with SA3PEAK, S9B, SV and until today there was no problem. After the update, total disappointment. Of course, I am already going back to the previous version of the software because unfortunately it is impossible to train with it.

Yes, I did a soft reset.

dzembronja

@isazi Hello, after the last update 2.39.44, the pace and altitude graphs in the log disappeared, I don’t know if it’s just me, but I have this problem

sartoric

@dzembronja
are you taking about new activities or old ones?

because after fw update only data summary are kept on the watch for old activities, not full dataset (so graph)

babychai

Hi,

i aware this screen problem discussed here before but i not able to search it in this forum.

Few days ago my touch screen become auto scrolling and auto simply select the setting. How to fix this? i already soft reset multiple times but still cannot solve it. Please refer to my YouTube link below.

i using software 2.39.44

https://youtube.com/shorts/Bvy-wg2n6UQ?feature=share

Brad_Olwin

@babychai I know a tester is also having screen touch problems. I am not but when this happens you can send logs to Suunto. Then PM me with the time, date and time zone logs were sent and include your SA email address. The devs can then see the logs and identify them.

babychai

@Brad_Olwin Log sent and already PM you, thanks.

Okay, at least i know not only me have this issue.

DasEd86

Hello,

My watch is crashing when altering a route on the app during an activity. For instance: I just returned from a run and tried a new route. I wanted to make some changes to the route during the activity (e.g. change the route to avoid a path looked sketchy, mark a POI (e.g. shelter)). During sync the watch is crashing and I have to start a new activity. This happened the last three times I tried this (routes ranging from 15 to 35km). I found this a really nice feature and I am pretty sure it worked in the past. Anyone else having this issue?

kriskus

@DasEd86 Not really. I did this a couple of days ago with the most current firmware and it worked fine.