I turn 50 next year and have noticed a decline in my eyesight over the last couple of years. Nothing too bad, mainly just with focusing and needing to read things at a further distance away so it’s not blurred. I’m still on my V1 which I’ve had for 3 years, still no issues at all with legibility and I don’t struggle to read anything whilst I’m running on road or trails. I do a lot of running in the dark and I find the display with the backlight fantastic; I don’t have a V2 to use as a reference point, but one of my training partners has an AMOLED (Garmin). It is simply way too bright for me, so maybe there’s a degree of personal preference with AMOLED versus MIP

Explanation of one of the “Out of the route” . It seems an issue generated by Komoot: Track inside Komoot: [image: 1777216884054-komoot_issue_4.png] Track inside Garmin Connect: [image: 1777216986875-track_garmin_connect.png] I have never finished that route where Komoot is saying, I allways finish at the top (as you can see in Garmin Connect’s track). It does also explain the last bad climb guidance notification. The watch triggered a downhill pop-up, but I was going up (the track was not finished yet). It means the Komoot workaround does not only affect to the turn-by-turn notifications, but ALSO to Climb Guidance. Needless to say that, despite I had tested this track in Coros and Amazfit, I have re-uploaded the same track to Coros and Amazfit to be sure. This issue is only in Kommot. Coros: [image: 1777236515149-coros.png] Amazfit: [image: 1777236601148-amazfit.png] Another thing: The shot with the track I uploaded yesterday here: https://forum.suunto.com/topic/15071/several-navigation-issues-feedback/39 In the first fork (of those 2), I noticed I have reversed Climb Guidance notifications (uphill when it should be downhill and downhill when it should be uphill). Those 2 small forks, are basically 2 slopes with a final U-turn. I understand it is very likely this issue is (again) caused by Komoot, since it’s Komoot who is creating all the logic that Suunto uses for the turn-by-turn directions and Climb Guidance. [image: 1777238543838-climb_guidance.png] What I don’t understand how is it possible I’m finding these kind of issues. If Komoot is not accurate, will Suunto have the Komoot approach forever?

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…

@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

The issue with the incorrect zoomed in individual climb guidance. In a short period of time I have already experienced it twice. Here you can see that I have transitioned from a descent to a climb as visible at two different zoom levels: [image: 1777224787857-f1b77f1a-e047-41cc-b259-92e28034ec4b-1_all_9057.jpg] [image: 1777224818028-f1b77f1a-e047-41cc-b259-92e28034ec4b-1_all_9056.jpg] But if I zoom all the way in, it shows me at a descent, and that seems to be the previous descent that I’ve just finished: [image: 1777224970549-f1b77f1a-e047-41cc-b259-92e28034ec4b-1_all_9058.jpg] I hope it doesn’t require another year for this to get fixed! Also, as mentioned above, fix the layout so that it actually shows how much climb or descent is remaining and increase the font size for the remaining distance because it is quite difficult to see.

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.

@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

@suzzlo said in Downloading map takes a very long time: @muurain said in Downloading map takes a very long time: Suunto’s cloud service that throttles the downloads but… you can download maps for the mobile phone that are much faster… so… if we think, same server is delivering them… this should not be the problem… Anyway, I can live with it You’re right! I didn’t even realize that, even though I did download mobile maps too And yeah this does seem like an understandable constraint of small smart devices. I too am happy to have the convenience of WiFi downloads, even if they are pretty slow compared to bigger devices. My old Garmin Fenix maps downloaded way faster, but it was via USB cable and a PC. But given the analysis here, the original post does now sound like a WiFi issue or a bug. Maybe try downloading maps on some other place or WiFi…? If the download speed is considerably less than 1GB / hour (or ~2Mbps), it should work faster and there are not many broadbands this slow.

@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

@gkaempfer Same here

@Egika Yes, different colours make no difference unfortunately

@Highlands These are great! Thanks

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?

@thibault-b. Good job !!! I test the last version today. It seems perfect all information I need size … thanks !

@maszop Thanks. And weirdly it has now synced correctly some 20+ hours after finishing the activity. That’s what usually happens an hour or two after I’ve grumbled about it on here. I’m inclined to suspect some sort of Bluetooth issue but whether it’s the phone or the watch I can’t say. It’s annoying.

@Egika thank you too.

Very Nice!!!

Hi. I also think the Vertical is still a good sports watch. I hope that in the next v1 update they’ll be able to include the altitude in the elevation contours in the maps at zoom resolutions that the MIP screen can display. Having them is useful in some conditions.