Suunto Vertical: Bug Collection

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.

babychai

@Brad_Olwin
Hi, beside touch screen is auto scrolling now the touch screen are not responsive. Soft reset still not solve it.
Then I just downgraded the firmware back to 2.39.20, the auto scrolling at the moment didn’t happen but the touch screen still not responsive/working. Screen surface are clean.

Send another logs? or should i do factory reset?

darxmurf

Hi all,
My watch was stuck at 9:40AM today, I had to long press top button to reset it and now I just have a black screen. Sounds like the black screen of dead is back.

darxmurf

okay, there is no more suunto service point in Switzerland, the shop have to send the watch in Finland… one month without my watch then.

Tieutieu

@darxmurf why do you expect one month ? last year I send my SV to cz service center for a solar panel replacement. I send it on monday (DHL pickup),
arrived tuesday, repaired thursday, send back friday by repair center. I got i back at delivery point in vacation the next week. So 2 weeks max.

(but I must admit that i was expecting one month too…and it gave me a perfect excuse to buy my SRs… )

darxmurf

@Tieutieu well, I brought it back to the sport shop where I bought it, I should have contact the suunto support directly in fact

babychai

just for update.
so i sent my SV to the Service Center. they restart the software (not soft/factory reset) then problem solved. few days later same problem come back again. i bring back to the Service Center and they straightaway give me a new SV watch due to still under warranty without any question asked. repairer just said digital problem.

Brad_Olwin

@babychai Glad you have this fixed!

darxmurf

Watch is back from repair center \o/ update in progress

Tieutieu

@darxmurf Great : less than a month !

darxmurf

@Tieutieu yep ski tour tomorrow to test that

fedequei

Hello!
Since updating my Suunto Vertical to the latest version, I have noticed the following issues:

The Wi-Fi menu stays permanently set to “Off” (as shown in the photo).
On the new watch faces, especially the Athletics watch face, the data remains frozen and does not update throughout the day. For example, if I set the energy level complication in the bottom left corner, it stays at the same level. The only way to update it is to reset the watch or start an activity.

I have read that many others are experiencing the same issues. Is there a solution, or do I have to wait for the next update (in about three months)?