@elbee These are different topics. Komoot generates turn-by-turn instructions because it has its own routing engine and is a platform fully dedicated to route planning. In fact, its core value proposition from the beginning has been precisely to create reliable turn indications, so all its development is optimized around that. In the case of sports watches, the approach is different. It’s not just about navigation, but a much broader ecosystem including performance metrics, battery optimization, sensors, etc. Replicating that level of accurate turn generation without a full routing engine behind is not trivial. Garmin, for example, does not rely on pre-generated turns embedded in the route file. The watch itself generates turn instructions in real time based on its onboard maps. That’s why you don’t see turns included in the route itself, as they are calculated directly on the device during navigation. Additionally, what you’re showing in the screenshot is exactly that behavior. The “turn notifications” toggle does not mean the turns are embedded in the file itself. It simply enables the device to generate turn alerts during navigation based on its internal maps and routing logic. In other words, the turns are not coming from the GPX/FIT file as predefined instructions. They are being calculated on the watch side, in real time, using the available cartography. This is fundamentally different from platforms like Komoot, where the turns are precomputed by a routing engine and exported as part of the route. With Suunto, when working with GPX files, you are limited to the track geometry, which does not contain reliable turn information. That’s why, to have accurate turn-by-turn guidance, the route needs to be created or edited directly in the Suunto App, where that navigation layer can be properly generated [image: 1776667935483-garmin-connect.png]

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

@Horizontal_2 In my opinion it should never be greyed out.

@dreamer_ Or this one, “Modern Analog” [image: 1776667873751-screenshot-2026-04-20-084842.png]

@snow said in Race S: Extremely high battery use rate: . Last fw fixed my 20% drain per day It might have fixed it for now just because the watch was restarted and the watch state was reset. It might reappear again. In the past I had this issue on and off. I suspect this issue is connected to external HR sensors but perhaps it is more complicated.

I can’t tell which is more accurate between Running Dynamic and Suunto Spark on the watch, so I’m not confident enough to speak about it.

@duffman19 Okay, thanks for that info. I guess there is not too much we can do about it? I understand they have stopped providing new updates for the S9PP. I have two watches and the one stopped doing it but the other one still does. Hopefully it just stops too!

@Nikolai-Simonov version 1.0.13-ext (77) And a strange is that I don’t have a save button even if I fill it with a phone number [image: 1776601447433-screenshot_20260419_142243.jpg] [image: 1776601488328-screenshot_20260419_142438.jpg] When I use the return button, sometimes it saves the number filled, and sometimes not. I also tried to select a contact instead of fill it manually.

@2b2bff said in Race 2 accuracy: It measures shorter than the other models. The question is is it more accurate, though? Nordic Walking on a measured loop of 2260 m: March 31 Loop Race S Garmin 955 1 2277 m 2259 m 2 2263 m 2263 m 3 2267 m 2262 m 4 2255 m 2267 m April 19 Loop Race 2 Garmin 955 1 2244 m 2261 m 2 2241 m 2263 m 3 2244 m 2267 m 4 2242 m 2272 m 5 2238 m 2265 m On measured straight paths, errors were smaller.

@sindavide yes, I also experience it on the Race 1. The last beep, which should be longer, gets interrupted, therefore sometimes shorter or not even audible. By the way, having 11 beeps is weird to me, I’d prefer 9 short and one long.

@DrSilverthorn Wait until you try to sync two or more watches with the app. Then as you switch between watches, the one that was inactive keeps bringing the routes back, so it becomes very difficult to get rid of them. You have to remove a route from every watch to truly remove it; otherwise it keeps coming back. There has to be a “master” copy - a source of truth - and I think it has to be in the app or more exactly in the user account on cloud because routes can also be added via the route planner on the web or sync with 3rd party services like Strava or Komoot. Also to make it even more complex there can be multiple Suunto apps on multiple devices. Even if only one device can still, routes can still be changed on every device. Personally I edit routes on 3 devices - a phone, a tablet, and MacBook laptop running iOS Suunto App. But only the phone does sync with the watches. Someone at Suunto needs to sit down and analyze this in details and fix it once and for all. A decade ago I fixed a similar mess of bookmark synchronization in Chrome browser, so I know it can be done.

Hello, I has the same problem, but without using navigatoin or map. Yesterday when I ran my watch restarted after about a kilometer. Today again during my run watch restarted twice!

@MiniForklift Thanks a lot! Yes, my wife proudly brought the medal home. At this point, she’s the ultrarunner in the family. Back to the maps: I think they’re very clear and easy to read. The latest update makes them more complete. For me, they’re much more readable than Garmin maps in terms of tracks, roads and trails, contour lines, and color contrast.

Today I did a run with a biceps band and the Vertical 2 titanium. Biceps, accurate readings. Maximum of 145bpm: [image: 1776639697484-biceps.jpg] Wrist sensor (Suunto Vertical 2). Today I used a nylon strap to ensure a better fit: [image: 1776639747016-v2.jpg] As you can see, the readings are completely wrong and stuck. The thing is I had this issue in the past with the Race 1. I’m a person with a trained heart and low bpm while resting. I have been using Garmin watches in many years and I don’t have this issue in Garmin. Coros is also working for me (but Amazfit not). Needless to say I know how to wear the watch. In my opinion, there’s something related to software since it’s very clear the watch is stuck from the very beginning. Considering the new sensor and the same issue I had in the past, I think algorythms are not clever enough when there’s noise because factors like sweat or the arm movement itself. I know the new sensor is working for many but I’m not the only one with exactly this issue, and in others everything just works (and as I posted before).

@Thibault-B. I didn’t say nothing… I tried again this morning and it works fine. The app update may not have synced to the watch yesterday. Can’t wait to test it during my next training