@Squirrel thank you!

@baaaa said: It’s disappointing that you’re aware of the issues but aren’t addressing them. This is not correct. Suunto devices and services, like any complex products, have many issues and areas for improvement, while resources are always limited. That’s why issues have to be prioritized and cannot all be addressed at once. Every user naturally feels that their own issues and requests are the most important, and that’s understandable. However, the bigger picture often looks different. @baaaa said: your company, but… Sadly, it’s not my company, only my employer. If it were my company, many things would probably be different. @baaaa said: it seems to me that your users who report bugs should be worth their weight in gold, and you should provide them with a simple and convenient tool for reporting bugs and suggesting new features. Instead, they have to go to some glitchy forum It sounds like you’re looking for official customer support channels. Those can be found at suunto.com. This is a community forum, not an official support or feedback channel. If someone is answering here they do it in their free time, not on duty. @baaaa said: search for relevant threads Yes, that’s the only practical way to keep the forum in a decent state. If everyone posted their own rant in arbitrary topics, the forum would quickly become a mess, making it even harder to find information and identify recurring issues. @baaaa said: wait for a moderator to approve their post… Unfortunately, that’s the only way to deal with spam. Users who have built up some reputation can post immediately, but newcomers need to wait for their messages to be approved.

@Gilles-D. said: But with almost 20 GB left on my Watch, it does not gives credit to your assumption You confuse storage and memory - these are two distinctly different things. The watch has 32 GiB of storage but only 32 MiB of memory plus a few more MiB on the SoC. But anyway, I don’t think this is a memory issue. This to me seems like a race condition - software developers will understand what I mean. A race condition is when two concurrent CPU threads race each other when one is trying to mutate or delete some resources in a conflicting way, which may lead to an unexpected result. This is more likely in a multi-core CPU. These issues are notoriously difficult to reproduce and debug. They may happen only one time out of thousand or one time out of million.

@SuperFlo75 Just got my new Polar H10. Paired with the Race 2 - works perfectly without any dropouts until now. Will be interesting whether the Suunto Smart Sensor will work as well (again) when returned from Suunto Repair…

Experiencing exactly the same issue

@Łukasz-Szmigiel said: How To Use Start your workout Hello i have a route I do my Trailrunning, i think it would better fit then the ghost runner. but, have it installed but can’t find in my watch. have a nice day vinc

@thailon same problem, daily it goes worse

@skifast12 sorry, I mixed you up with the topic creator. In the first post has been written an interval.icu SuuntoPlus Guide…

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.

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.

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

@vinc14 for OWS GNSS tracks, your hand has to leave the water: front crawl/freestyle or backstroke only. If you think of water as a mirror between you and the satellites, and your hand is behind the mirror…

@rémiP Thanks for this - but it seems the problem was somewhere else… “shift” does indeed work - but I now instead use it in an another way/method. It seems I was recreating an array without any need to do so - leading to memory issues. Hopefully now fixed.

@EzioAuditore and once again it must be remembered that the GPS data collection of the Race 2 is very good, the problem comes later with the software processing of the information to calculate the distance to be displayed.

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

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