Suunto Vertical: Bug Collection

isazi

@Jakub-Sliacan do you have autolaps enabled? If so, that field shows auto-laps and not manual ones.

localful

Hi, I am pretty sure this is a bug since I used to have this feature until the latest update. I can’t set my SV in “vibrate” mode only, meaning that for example mobile notifications would only vibrate. the tones setting in the general setting menu offer somewhat different combinations of setting the system sounds. I’ve complied a list of different setting combinations and what result they produce, none of them are what I was looking for…
If this does get answered, does anybody know the logic behind having a separate toggle switch for the “vibration” and then a couple of more options for the “alarm”? I am very confused with this logic and am unsure what controls what.

inkognito

@localful Have you set Tones to “All off”? If not, that’s why there’s sound on all the times…

markman8

Hello, its 3:50 in the morning and the Vertical just recovered from error 1401.1403 after entering Service mode (the 12s upper button thing).

I woke up in the middle of the night just to find out that the watch needed to enter Service mode glowing in the dark. I pressed the upper button for 12s and I thought that that was it reading in the mean time another section and thread in this forum about Verticals that never recovered from this mode. Fortunately and as I prepared a cup of tea I found that a new message came up on the screed saying that it recovered from error as mentioned above.

First of all could the team of programmers explain what this error is about? The version I am currently on is 2.30.26 and the watch enjoys the best of treatment as far as functionality and physical care is concerned. Yesterday before going for sleep I did sync it (I had 5 days that I did not synced it before that).

Suunto Cores (2 of them) have managed up to their expectations. Its a pity this titanium solar version does not. Not that I am disappointed completely (yet) but I am certain that for a real athlete and adventurer the Vertical would not be the ideal watch to be with.

Tieutieu

@markman8 said in Suunto Vertical: Bug Collection:

?The version I am currently on is 2.30.26

Never experimented any crash with SV. Why is your SV not updated to 2.40.38 fw ?

markman8

@Tieutieu said in Suunto Vertical: Bug Collection:

Why is your SV not updated to 2.40.38 fw ?

Really? There was no prompt from the watch to do so and as far as this forum is concerned the latest software version for Suunto Vertical is 2.30.26 the same as my watch is on right now.

isazi

@markman8 the latest firmware version for Vertical is 2.30.38

markman8

@isazi well as I mentioned the watch never prompt for upgrading to the latest one. Battery life is 83% and the following pictures reveal that I have set up automatic updates to on.

And yes the latest update is recognized by the app.

Watch still on .26

Please also note that the Software update in the General section is grayed out.

isazi

@markman8 send me a private message.

GiPFELKiND

@markman8 what is the Problem here? Why your watch isnt updated?

isazi

@GiPFELKiND I helped @markman8 fix the issue, now his watch is updated.

Mff73

@isazi
is this so a secret trick to fix by PM ?

Tieutieu

Small bug with suunto plus app selection :
when selected (climb for instance), the button remains “unpined” when i go out the app selection menu and come back in it.
To “unpin” the app =, I had to pin it again.

It works, but its strange. Have you also this behaviour ?

jjpaz

@Tieutieu said in Suunto Vertical: Bug Collection:

Small bug with suunto plus app selection :
when selected (climb for instance), the button remains “unpined” when i go out the app selection menu and come back in it.
To “unpin” the app =, I had to pin it again.

It works, but its strange. Have you also this behaviour ?

Yes, same behavior here

@Tieutieu same problem with the s9pp, ~~I had~~ (sorry) @taziden reported that a while ago… and I confirmed that!

stromdiddily

TSB on watch face switching values when display is activated vs not.

The -23 is the correct value but you can see it toggling between that and -15 which was from the day before.

https://photos.app.goo.gl/f9Vyxn6YapLuorJ46

Brad_Olwin

@stromdiddily I am not seeing this on production firmware. Mine is stable. However, in the morning it takes time for the new value to be reflected and does not always occur on the first sync. My TSB value is - 22 in SA, in the main widget and on the watch face mini widget.

stromdiddily

@Brad_Olwin said in Suunto Vertical: Bug Collection:

@stromdiddily I am not seeing this on production firmware. Mine is stable. However, in the morning it takes time for the new value to be reflected and does not always occur on the first sync. My TSB value is - 22 in SA, in the main widget and on the watch face mini widget.

Ok - do you want me to submit logs if it happens again? I too am on production firmware unfortunately

Brad_Olwin

@stromdiddily I think this is fixed in new firmware so probably not.

tkernen

I’ve been having on and off BLE connectivity issues for at least the last couple of months. I start an activity and none of my paired BLE devices connect to my SV (Polar H10, Stryd), even the Suunto App on my phone doesn’t sync.

The workaround is for me to put the SV into airplane mode, exit the menu, then back into the menu and disable airplane mode. It fixes the issue each time.

I still can’t figure out what does trigger this lack of BLE connection with paired devices.

I think, but I’m not sure that BLE devices connected via apps such as Core and Train.Red don’t see to suffer from this issue (TBC).

The current SW on my SV is 2.30.38, Bluetooth is 3.0.28

Anyone else has come across this issue?