@dreamer_ I think there might have been a small misunderstanding, so just to clarify my point. I was simply referring to the brands you mentioned as examples, not trying to say one approach is better or worse. Each brand has its own philosophy, and this is just ours. Of course, we are actively working towards improving things like GPX-based turn guidance or routing directly on the watch, but we want to do it in a way that we believe is robust and reliable for the user. That’s why, for example, offline maps in the app combined with routing to the watch is part of what I’d call the “Suunto way” of building a routable map experience. I really appreciate your feedback and the level of detail you’re bringing to the discussion. It’s genuinely valuable for us ️‍

@sky-runner I agree! I hope this will be fixed in the near future. It’s a very good function

@dreamer_ My watch face preferences haven’t changed much since I switched to the Vertical 2; I still prefer “Athlecis” when exercising, “Stride” or “Classic Analog” with a suit, and of course, a leather strap.

Phantoms vibrations reaturned, in my case. Not very often, but still… I will try to check if it is related to phone presence.

In my case, with the Vertical 1 Titanium Solar, I’m confident the issues started with version 2.43.12 released in June 2025. I had been monitoring battery consumption, which increased from about 3% per day during normal use to around 7%. It’s not a dramatic spike, but it reduces battery life from roughly 21–22 days down to no more than 14–15 days. Wouldn’t it be enough to check what changed between version 2.40.44 and 2.43.12?

@2b2bff I don’t think so…surely all the other devices can’t be wrong? Additionally, when I plot a route on footpath or the Suunto app, the Race 2 always returns a shorter distance than the plotted route too…my other watches don’t. This is mainly on canal towpaths so not a lot of cutting corners going on…but plenty of weaving round walkers etc. that could add a few meters. But it appears it’s not going to be looked at and I’m struggling to see why this would be.

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.

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

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

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

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

@Carlos-Villamar did you ever solve this issue. Suddenly i’m seeing the same. This headphone hardware is fine but the software is not that great.

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

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!