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

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.

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

@isazi said in [Race S - 2.50.28] Nap detected during recorded sleep: so report it again if it happens with the new firmware And there I am: Nap accounted to yesterday: [image: 1777121428413-059d473a-6019-4348-bf94-fa20ad027bb8-image.png] And tonights sleep: [image: 1777121473999-6f04e699-6aba-4c5e-bbc2-09d3a18430a6-image.png] Fair enough, I did wakeup because of some noise around 23:55 - as seen by the rising HR. But the sleep tracking didn’t even registered it as wakeup… I think, somebody should look at that code on a higher level as there seems to be something broken in the overall logic…

Thank you very much, I guess I’ll have to solve it that way as well. It would be great if Suunto could pull dive sites from PADI, SSI, or DAN so that you could get suggestions about where the dive took place.

Your watchface looks nice. It is simple and easy to read. Can you modify it to have 3 bottom data fields, same as top row? Could you please share your code?

@ashic Hi I am having exactly the same issue! Even Suunto chat could not help me. Waiting for an answer from their tech department. I also did a reset and lost my dive profiles…will try the D5 option…

@Egika thank you too.

said in Offline Maps and Routing in Suunto App: Im having problems with downloading the offline maps to the phone. It works for my watch but the with my phone Im stuck with “Waiting to download…” msg. I have cleared cache and data on app (not reinstalled as of yet) and also tried two different Wifis so far. Anyone else not being able to download the offline maps to the phone (again it works for my watch)? Thanks I have now tried to reinstall the app but also a third Wifi (hot spot this time) with no success? Its wierd that the Suunto Watch can download the maps but the Mobile phone cannot isnt? It would be nice if they were availble online so one can download them to the pc and transfer them onto the phone when problems like this occur. Just a tip!

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…

Very Nice!!!

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.

@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

@Nikolai-Simonov sorry, I missed that one. I have checked your code and it is extensive like for simple watchface. I thought it is easier to code such a things. I am struggling with google ai with my watchface. Can I send you my code for some help?