@kemetter said in Suunto Routeplanner: This should match Suunto app quite well, but some GPX files have quite odd content. I would need the original GPX file in question to be able to resolve this. Waypoints should load if GPX is exported from Suunto app, but from other sites it’s not a standard how they mark user named waypoints. Here is one example, which I think I created this in Strava: Issy Alps 50k.gpx When I load this in Suunto App it shows all waypoints and the distance is 50 km: [image: 1769826713292-screenshot-2026-01-30-at-6.31.23-pm.png] When I load the same GPX file in the routeplanner, no waypoints are shown and the distance is 42 km: [image: 1769826789058-screenshot-2026-01-30-at-6.32.48-pm.png] It may not be obvious by looking at the screenshots but the missing parts are from the start to the first waypoint and from the last waypoint to the finish. Basically, the route now starts at the top of the first mountain and ends at the top of the last mountain. I’ve had similar issues with a few more GPX routes. Also, I should mention that on-route waypoints can also be present in routes that are saved as FIT files. Those can be generated by some route planners such as PlotARoute and are natively supported by Garmin. It would be great if the route planner could load routes in the FIT format too. Also, routes in FIT format can embed turn directions, and some route editors (e.g. PlotARoute) can create those too. It would be awesome is Suunto followed the same standard.

@Brad_Olwin said in Suunto wristband: @Tami999 I managed to snag one of these a few years ago. A friend that works for Suunto gave it to me. Yay, Iam glad my memory is not that bad! Thanks for sharing.

@sky-runner I’m sorry, I didn’t mean the graph would look compressed, rather the complete UI would, as it would reduce the whitespace below the headline. If you look at the Android representation, you have a 100 line, but whitespace over the line. TBH I think it looks better with the 120 line and the whitespace. My problem is that the range is shifting around on iOS…

@jjpaz I actually love it, so I’m a little disappointed because the watch is really nice, but the thought that my workouts and the averages I’m trying so hard to maintain are somewhat distorted by an inaccurate clock reading is quite discouraging. I’ll do some more tests; this week I’ll try to see how it performs on intervals. This is the today comparison from Strava of the 2 results: [image: 1769980171190-efce7a11-3cf0-474c-b9f6-d284f1c959f4-image.png]

@Tieutieu yes agree looks great!

@giuliosq wrist heart rate is highly personal. Your experience will be different from others and depends on many factors. The use in the cold and walking with poles add to the complexity of the task the watch has. Good that the AW handles this well for you. And bad that the Vertical does not… In general I think you are correct in saying that the OHR sensor of the Vertical in inferior to the AW. That’s why it was changed with Vertical 2.

@flyinono this is a known regression in 2.50.26, it was reported and ack’ed by Suunto, you’re not alone, OHR stopping during the night which leads to no sleep and hrv data is a known issue.

@louispar I think OHR is very hard. Suunto works for me with consistent easy running, walking and sleeping as well as around the house. I run a lot technical trails and OHR is good but not great. For intervals I don’t bother with OHR from any brand. On my wrist neither Garmin (Epix2) or Apple Watch Ultra 2 or Suunto V2/R2 are good enough.

@ChanOJ I’m not absolutely sure to what extent, but displaying any information on an AMOLED screen shortens its lifespan, which is why the AOD modes are rather minimalistic.

@2b2bff

@Mff73 Haha, well, thanks for the tip. I´ll try it the next time

@2b2bff said in Adjustments to FR labels: But the things I mentioned months ago are still not worked in into the iOS App… That would be disappointing. An active and engaged community is a real asset and a win-win opportunity. Nautic is quite well designed from a hardware point of view. Most of the issues discussed here are minor software and UI refinements: low cost, but high impact on product quality and user experience.

@duffman19 said in Backlight Bug 2.50.26: There is a second issue where the backlight will remain ON after backing out of the activity start screen. Yup. I hit this issue simply by checking my list of Sports Modes and then activating the North-up map orientation: I didn’t get as far as an activity Start screen. Vertical 1, Data watchface.

It all depends on which weather service is being used. For me, in the Netherlands, my suunto race s does a good enough job. It also shows the location it used on the watch. As far as I noticed, this applies to most European countries. My previous 2 garmins did a lousy job. Garmin uses a service that only provides weather for main airports. People complained about it that the watch showed a different place then they were at the moment. Garmin “fixed” this by removing the location information from the watch, so you couldn’t judge the accuracy of the weather report anymore. So, people complained on garmins forum that the location information was removed. Garmin “fixed” the complaning by closing the topic on their forum. And yes, two weather services might provide a forecast that contradicts each other.

@Egika Yep, thats the one. I disagree on the redundancy personally (albeit probably from tradition of having that in so many watches, including Suuntos over the years lol). But yes, the mention of it, picture of it, and of my original mention of the “storm alarm indicator” show either the software needs to change to align with the manual and other watches, or the manual needs some updates to align with the current watch setup…

@Peer-Ole-Jacobsen You can use SyncMyTracks to sync data between apps on Android. It works great for Suunto and Garmin.

@Squirrel Thanks, I didn’t know that. I’ll try it.