Crash reports collection Q1 2026

[sky-runner]

I wonder if the crash I mentioned in the previous post could have been caused by me unintentionally rebooting the watch by pressing on the start button.

I always felt that on Vertical 2 the start button dangerously sticks out which makes it too easy to press. Honestly, this seems like a bad design. During activity we almost never need to press this button.

At the time of the crash I was using poles and climbing up on steep terrain which means my wrists were bent the way that the button could be pressed. Furthermore I wore half gloves that Leki poles attach to.

I have just done an experiment - started an activity, switched to the map screen, then pressed and held the start button - shortly after the watch has rebooted!

I think this needs to be addressed - either the timeout for the reboot - how long we need to hold the button - should be increased or perhaps there should be another way to prevent this when using poles. But again, I don’t know if that is what has actually caused a reboot but I can see that accidentally rebooting Vertical 2 is quite possible when using poles.

Any thoughts about this? Should I start a separate thread to discuss this?

[Adrian.S]

@sky-runner This definitely requires a software update for all Suunto watches.

[sky-runner]

@Adrian.S I think, at the minimum, this requires changing the lock function so that the watch can be operated under the lock but without the risk of pausing, stopping, or rebooting it.

We should be be able to fully use the map and climb guidance under the lock.

But perhaps an alternative solution is to move the reboot function to another button that is less likely to be pressed (not sticking out like Start), or requiring a combination of two buttons. or extending the duration of how long it needs to be pressed to reboot.

[EzioAuditore]

@sky-runner button reboot aside I am 100% mine don’t reboot by upper button press. Seen it reboot while looking at it and no buttons were pressed or the middle button was used to advance and sudden crash or received notification for the guide and upon looking crash again.

[stromdiddily]

@sky-runner said:

@Adrian.S I think, at the minimum, this requires changing the lock function so that the watch can be operated under the lock but without the risk of pausing, stopping, or rebooting it.

We should be be able to fully use the map and climb guidance under the lock.

But perhaps an alternative solution is to move the reboot function to another button that is less likely to be pressed (not sticking out like Start), or requiring a combination of two buttons. or extending the duration of how long it needs to be pressed to reboot.

isn’t it just touch that’s disabled when you lock it? can still scroll thru the various screens

[sky-runner]

@stromdiddily said:

isn’t it just touch that’s disabled when you lock it? can still scroll thru the various screens

Zooming the map and climb guidance (elevation profile) are very important functions that I personally use very frequently even during a race. Perhaps I am even more likely to zoom during a race because normally I have waypoints for all aid stations and checkpoints. Furthermore, now with the configurable bottom field on the map and climb guidance screens, touch is also very useful on those two screens.

If I lock the watch, all these features become unavailable.

[stromdiddily]

@sky-runner got it, didn’t realize zoom was restricted during a lock

[2b2bff]

Yesterday my Race S suddenly restarted on my bike commute home. Just basic bicycle profile, no SuuntoPlus apps, no buttons pressed after I started the tracking. I already sent logs and a PM.

I’ve just seen something interesting as I looked at the activity. Two or three minutes before the watch restarted, it kept failing to record heart rate, GPS and speed for a couple of seconds. Not exactly at the same time for those parameters.
I’ve never seen something like this, yet.

It did recover until it finally restarted. Maybe this points to something in the code?

Also, I just recognized, 16:56:08 is completely missing.
Recording continued normal until just stopped 16:58:10.

[sky-runner]

@2b2bff You might be onto something. In my case I see that my Vertical 2 recorded GPS positions infrequently just before the crash:

Earlier in that run it recorded every 2-3 seconds and even earlier - every second. But that might also be a result of a steep terrain. Also it crashes right at a trail junction - perhaps I paused moving for a few seconds to navigate. Also, I see that the coordinates are recorded only when the distance advances, so perhaps there is that.

[OutdoorMan]

R2 booted up after I woke up and pressed a button. For some reason it stopped recording sleep at 2:30 in the night and turned itself off or crashed, I am not sure.