@2b2bff Yes, I’m aware. I would expect the watch to refuse executing a 3rd app, regardless if it’s an app or Guides workout, rather than hard crash and reboot.

A year and half since this issue has been reported. There are 27 upvotes. Are there any plans to fix this?

@tomvanacker well known. I usually charge my watch shortly before going to sleep. The stress is somehow reset while sleep tracking, So, it doesn’t bother me much.

@Marcel-W hast du dazu einen Screenshot, was du meinst? Beide Werte sind doch da. HF sogar über die Zeit als Graph…

I have a Race S, and 2 weeks ago i did a factory reset because of something, i don’t recall what. But now the battery also goes down much faster than it used to, equivalent to what other people here are reporting: 7-10% per night. Bluetooth announce is off i now even put oxygen stuff disabled (for night monitoring) and DND for the night

I’ve been having this problem on and off for a couple of year, first with Suunto Race and now with the Race 2. Tried everything but seems factory reset is the only “reliable” solution. But randomly it stops syncing and restarts again. Since this is affecting many users and have been a problem for years it would be nice to get Supports view on this. Anyone gotten a reliable fix/workaround?

@muellersjens Did you check again your previous activity in the app? HR is computed in the backend and sometimes it doesn’t appear good initially (if appearing at all). After this, what is saying your watch logbook for zones duration for this activity? Correct or same discrepancy?

@aiv4r is [image: 0UA9ixY] not a sign? Has been there since I dunno when. There are, from my understanding, already SuuntoPlus apps running natively on the Run, don’t ask me which as I’m not sure.

@Egika said: @elbee I have checked. This is going to be fixed. At least it is in the current test version. Thanks for checking! It’s appreciated.

@Sunday really? This is available on Suunto Run. Really starting to feel like the Run has the superior amount of qol compared to every other Suunto watch.

@André-Faria then this defect must have been developed over the last two weeks… But yeah, not impossible. I have this watch for about 18 months and it did already restart three times over that period. Something that is almost acceptable, although it has been once in the middle of a race…

@Gunnar Tried everything in this direction. Nothing works. Funny thing is that when wrist is in water and not swimming, HR value is plausible, but when i start swimming then it goes up to over 170/180 plus. I think it’s a combination of bad sensor design and possibly software

@Egika I noticed it -> too sad if the Verical 2 and Race 2 are still too big for your wrist ot buy a new watch

@Egika @maszop I can only share my experiences. I sometimes get the notification when my speed is clearly under 5.4km/h and quite often I don’t get a notification when I walk faster than 5.4km/h. I live in the Netherlands, not a really challenging gnss surrounding. Current pase with gps isn’t the most accurate, but I sometimes continue to hike for over 500 meter and then gps should have a fairly accurate pace.

@isazi I only have a recent (as in today) reaction from Suunto stating they haven’t got a clue what causes the problem, let alone how to fix it. But please do report it, with logs, when it happens again. That would be very helpful.

@Ars-Vitae Any update? Did the warranty replacement or repair actually fix the issue? I’m having the exact same problem with my Suunto Race S.

@lydum, known and fixed in next firmware.

You’re not alone https://forum.suunto.com/post/193526

Same here with the 9PP after the last firmware update. Since then it happens regularly and as it isn’t reliable anymore I stopped using it regularly. Anyone tried to go back to another earlier FW?

Still nothing done about this, huh.