@joaquin there’s definetely a bug here, and I found the explanation. I made another experiment. If inside Komoot I don’t check the roundtrip, it does not make any effect , since the route is roundtrip (or at least, I can see indications in both directions despite of that) But it is more. It’s Komoot what is making the bad turn-by-turn directions. Have a look at this photo: [image: 1777134752391-komoot_bad.png] A: Start point B: End point of the route What you see in the photos I posted in the other post is that Suunto is notifiying that 1 as the very first point, because of Komoot’s issue. That’s why there’s the 18 meters offset in the photos I posted for you. But is worse, second roundabout is not notified at all (all other brands do notify it (Garmin as roundabout, Amazfit- Coros as a left turn). So offset explained. Now, about the photos you uploaded. Photos 2,4,3,5. Suunto’s notifications seem to be wrong and that is a one-way track (no roundtrip). What I’m seeing (3 and 5) is that there are several turns close together. It’s like there is something bad at the algorythms, detecting 2 very close left turns as an U-turn. Perhaps this is Komoot related. What happens when turns are very close inside Komoot? In my opinion, it’s very clear Komoot’s workaround is more a problem, once we know others are not having these kind of issues.

I’ve got about 1 week left of my return window…I’ve already sent one back as I wondered whether it only affected certain units and hoped I might be lucky second time round. I was also banking on it being addressed in the update…to me the accuracy fix would’ve been better than all the new features that came along. Might be time to try a Vertical 2…

@OutdoorMan said in Minimal watchface (feedback): @dreamer_ I personally just need to have a date in time only mode, because I never remember what date it is. And that’s it Totally agree. Battery icon also means you’,ll never forget charging your device but that is my feeling. I consider the rest of the things totally useless

@Egika thank you too.

Very Nice!!!

@Nikolai-Simonov said in Live location S+ app: It’s not a bug but feature! you don’t need to re-connect it each time, just take a 5-15 sec to connect. Thanks for all the explanations. The Bluetooth connection to the watch is a bit unclear to me, but I understand the general principle. And I confirm your explanation: even if the app says “waiting for S+ application…”, it will turn green as soon as the activity starts. However, I tried the live tracking again this evening during a run, but unfortunately, it didn’t work very well - version 1.0.16-ext (102) First, I had trouble activating tracking: the watch said it was connected (I had the GPS coordinates on the dedicated screen) and the app indicated a connection with the watch. But I still wasn’t located on the app’s map, either at the start or after a short movement. I had to stop the activity, disconnect and reconnect the app and the watch, and start a new activity to finally be located on the map and see my movement. Several kilometers later, I checked and the watch was disconnected (“DISCONECTED state:99”). I’m not entirely sure, but I think the app still indicated a connection with the watch. I tried disabling the Suunto app on the watch and then re-enabling it, disconnecting from the app and re-enabling it, several times, in various orders, but still without success. I finally gave up on LiveTracking. Last weekend, I also had some issues with version 1.0.13-ext (77) where I experienced a disconnection for a few kilometers, but the connection was restored afterward and the tracking resumed (with a long straight line corresponding to the disconnection). As I work in software development myself, I imagine it can be very difficult to diagnose with just this text information, sorry

A similar issue has been reported on Reddit: https://www.reddit.com/r/Suunto/s/ON5V0wTTNr with more that one user saying they had this issue.

@MdzOtt yes, SA is the one not doing it ;). In my case with Karoo Gen 3 I see same avg power with zeros included (gold standard) like you get see with garmin/Strava

I am also someone who have been using GPS watches for a decade and half now, starting from Garmin Forerunner 110 in 2011 and having Vertical 2 as my latest watch. I run in Pacific Northwest on mountain trails that are often under a very dense tree cover, under tall coniferous trees such as Dogras Fir, Red Cedar, Western Hemlock, etc. This is an extremely difficult environment for GPS and historically most GPS watches were very inaccurate. For a long time I thought that Suunto Ambit 3 Peak with its massive GPS antenna was perhaps one of the most accurate watches, but the new generation of watches with dual-band GNSS that have been released in the last few years, starting with Garmin Fenix 7 are amazingly accurate in this environment compared to anything we had before. The last generation of Suunto watches with dual-band GPS - Vertical, Race, Race S, Race 2, Vertical 2 - are all very accurate and some of the best in class in terms of GPS accuracy. But in my opinion, still nothing beats the Airoha GNSS chipset that was used in Garming Fenix 7, Forerunner 255, 955, and few other watches a few years ago. I think more recent GPS watches are a bit less accurate even though they may offer better battery efficiency. Here is a comparison of Fenix 7X Sapphire vs. Suunto Race S - on a similar terrain with the same map zoom level. Both of these are are examples of running downhill on a narrow singletrack trail. Both of these show 6 laps on the same loop. You can see that the track produced by Airoha GNSS definitely looks tighter with tracks from laps closer on top of each other. [image: 1776988567192-screenshot-2026-04-23-at-4.55.25-pm.png] [image: 1776987438944-screenshot-2026-04-23-at-4.18.40-pm.png] To be fair, more recent Garmin watches (Fenix 8, Enduro 3) are definitely less accurate than both Suunto watches and earlier Garmin watches. Also, distance wise I think Suunto is a bit more accurate. Garmin had a tendency to shorten the distance by 1-1.5% compared to the distance of the GPS track.

@sky-runner right. Could reproduce. Reported it. Thx!

@Tami999 the official Czech reseller is suuntocz.cz Thanks for the tip! Finally I can make my choice

@Manuel-Extreme There are 3 things Should the the watch always record data even if it can determine the data is incorrect? No Should suunto look into crashes? Yes Am I less concerned with loosing some heart rate data than you? Yes. My original reply is about the first point. But since it is an important point for you I will no longer capture your topic. (Btw, I was not able to reproduce your steps on my race 2, so it could be model specific)

@Audaxjoe maybe… We should ditch the “I have it all” sports watch and take indoor and outdoor series apart

@Egika My bad, I have a 9 peak pro and I assumed it was the same for all Suunto Watches ^^

@sartoric Ive had this happen to me on nearly every single hike/walk that I use the map. Too often for me to share coordinates every time. Considering its been nearly 3 years since this was first reported, what is the main issue?

@Egika it coulde be average fuel consumtion number that could motivate you to ride more

said in Vibrations et tonalités fantômes: My current guess is that it may have something to do with the compass auto-calibration. I am almost certain this is this issue now. To check this, I performed the following: Open the compass widget (make sure it is already calibrated). Bring a magnet close to the watch (doesn’t have to be strong, a refrigerator magnet will work). This will reset the compass and bring up the “Calibrate Compass” notification. Without moving the watch, back out to the watch face. While on the watch face, perform the calibration movement (figure 8). The watch will eventually vibrate, signaling that the compass has been calibrated. Go back to the compass widget to verify it has been calibrated. I’ve performed this several times and every time I get the “phantom vibration.” My assumption is that some of us are perhaps in situations that cause the 9PP’s compass to reset often, and thus we get the phantom vibrations more often than others. I know for me, getting in and out of my car tends to mess with the compass calibration. Even a simple act like opening the refrigerator (with all those magnets on it) could reset the compass, triggering the background auto calibration and thus the phantom vibration. @isazi @egika Is there a chance this could be verified by Suunto? Would this qualify as a bug? Although a minor inconvenience, it seems like something that could be an easy fix as it seems to only affect the 9PP. Edit: You can perform an even easier verification. Simply bring a magnet close to the watch while on the watch face (locked or not). Then perform the figure 8 movement. You’ll get the phantom vibration once it calibrates, no need to check the compass widget. Checking the widget just verifies that the magnet reset the calibration.