@Steven-Hambleton Well, I guess a sync back to the watch after a trim could be implemented to keep the values in sync. But at the moment everything is better than having a run in your stats with a 30min car drive afterwards or whatever.

@withManish I get to about 4 days easily. With AOD and notifications enabled. And about an hour of GPS tracking per day…

@athinakap30 With every new software update, the battery gets worse; no matter what setting you use, the juice doesn’t last as long as they are claiming. The last battery issue was addressed in firmware version “2.48.16”, and later firmware versions have been pathetic for battery performance, and Suunto engineers have ignored it royally (busy developing more bugs ) I have been suffering from this issue for a very long time; resets, factory resets, and firmware rollbacks have not worked. Every time I do that, I spend more time reconfiguring whatch.

@isazi Yeah, let’s hope they implement it as soon as possible.

@Goatee Suunto reached out to me via email asking for more information (watch serial number, app version, etc.). I sent them the deets, so I’ll see where things go from there. Hopefully we can isolate the bug and get it fixed.

@Kowalski I’m waiting for a successor of the Race S as well, decided not to go with the Race 2. But it felt surprisingly small for its size…

@Kowalski I don’t know. I’m not a Reddit admin, so I don’t know the tools they have at their disposal to detect stuff like this. It may have been that there was malware hidden in the file hosted in the Google Drive file, and the Core 2 leak was the bait to get you to open it? Just speculating.

A year and half since this issue has been reported. There are 27 30 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’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?

@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 @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