Experiencing exactly the same issue

I have this problem with the Suunto HR belt since November 2025… I reported this several times here, and I contacted the support… they told me to send logs… it’s a problem with SV1… it’s a problem with SV2… with two different HR belts… and that’s why I don’t think that this is a problem of a belt or a watch… this is a Suunto problem, but it seems that they don’t care about this…

@2b2bff No idea what you mean by “intervals.icu”…I’m referring to making an “interval workout” through the Suunto App that is then sent to the watch. The watch will vibrate when you enter or exit the target zone (whether that is HR, Power, pace etc), and also once per second starting at 4 seconds before each interval starts in order to get you ready for what’s coming. This thread isn’t related to any of those vibrations (which make perfect sense)…it’s the random ones where there’s no apparent reason that we’re trying to figure out…or get resolved if it is actually a bug.

I’ve got the Race S on the current software & same issue the other night, I was 1km into a fell race & the watch randomly restarted Raced the next night no issues with the watch Annoying, but at the same time it’s only done it the once in a years worth of use Sent the logs to Suunto & messaged as per the forum guidance, hope it helps for future

I usually always check if the altitude shown by the watch is correct, if not it can be set manually or auto adjusted. Apart of that, the data look very scattered, I agree with Egika about strong wind or dirty sensor. Did you get the same behavior also other times? in this case the pressure sensor could be defective.

Welp. Here we go again. I’m investigating zapps being unloaded when Constantin 2.0+ is being used with ZoneSense. It seems that the S+ app can be either custom designed or have custom features but not both

I still think it needs to be better. When map is configured to high level of details, Garmin maps allow trails to still be visible at 1.2-2 km from the current point without panning the map. In part, that is achieved by offsetting the current point towards the bottom on the map screen, so that you can “see” further in front of you on the map. At the same time, usually there isn’t much point at looking behind you on the map. On Suunto, trails disappear after 500 m when the watch is configured in metric units. It is even worse when the watch is configured in imperial units, in which case trails disappear after the 0.2mi level (320 meters).

I am experiencing exactly the same issue on my Suunto 9

GPS accuracy may be severely degraded by the rock face blocking the ‘view’ of half of the sky, therefore incline calculation may give random results.

@sky-runner Interesting that your crashes (if I read it correctly) happen before you even start the activity? I would like to ask this group how much of their watch memory is filled up with maps? I recently downloaded a lot of map areas and then the crashes began to happen a few days later….thoughts?

@Matúš My hypothesis is that there are some extra features that do not really work well together. Test 1: new battery installed because watch could not last for more than two days which is somewhat below specs. Before battery switch the sleep tracking was unstable, after the change it never came back. Test 2: turned of heart-rate measurement completely since it is no use … Surprise it is still trying to ignite the measurement LEDs ??? Restarted it several times, being more than a week since I received it back. Multiple trainings done, they worked out OK and battery time seems to have improved since I can use the watch more than two days on a charge now. However it is entirely unlike the other Spartan Sport WHR I own which can be worn a week and still has 80% of battery power. Both have new battery but remarkably different performance, sleep recording broke something in the 9PP as far as I can deduce.

@soryp I confirm I did it twice following your instructions… That’s why it is so strange !

@Maxime-Bouvier io ho lo stesso problema e ho già postato un’uscita con Garmin coros e Suunto. Secondo me è un problema firmware perché per il primo anno è andato benissimo. Ora da circa due mesi ha problemi.

Fixed - it should all display correctly now. You can use this thread for issues or ideas. Happy riding!

I don’t know how it works on an ocean, but on my race s the direction is auto detected. If the route has tbt alerts, those are applied either way the direction I walk/run/bike the route. If I have reached the destination, the route is still available. No need to go into menu’s the choose a direction, just start. On my 2 previous garmins, this worked different. I had to choose in advance which way to go (and on a round trip it wasn’t easy to see on the map which way to start) If you followed a route the other way around without setting it in the settings you had a course error warning on your screen, all the time. When you selected the route to be followed in opposite direction you would loose tbt alerts. And if you reached destination, the route disappeared from your screen. Way to many times when I wanted to follow a round trip, the stupid watch concluded I reached my destination before I even stared and the watch ended navigation. So you have to go into settings and select the route again. I understand your wish to follow a route in opposite direction, but don’t envy garmin users. Envy suunto users with a running sport watch.

@surfboomerang looks similar

@VoiGAS yeah, that is a thing of the past, sadly. You could see this tag there a year or so ago…

@Dimitrios-Kanellopoulos Android