@egika unfortunately, yes. however, as a workaround, the latest version (still in appstore review) adds a restore session feature. so briefly you will be able to turn off live.τ for a minute, sync with the suunto app (to update a route or something), and then turn live.τ back on, the app will let you continue your session without interruption. it’s kinda hacky and not ux friendly solution, but it could works for non frequent things like an route update.

@halajos Yeah, fine. I have a feeling I’ve read and heard enough of it. My next buy will be a lactate meter.

I know it’s a topic for R2 here, but nevertheless the question about V2… for me, it seems that the calculation is also a bit shorter on V2 in comparison to V1

@EzioAuditore said in "Raise to Wake" not working properly during activities: @jjpaz you’re right when toggling it before starting the activity it works as intended. After the activity has been started it doesn’t. Thanks mate. Is this known and reported? I’ve sent ‘Comments’ from Suunto App, but I haven’t received any feedback, so I don’t know if Suunto officialy knows…

@tom_vertical you are a robot and nobody told you, maybe

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

@cheetah694 Yep, that sounds like better UX for 90% of the activities. An “End without partner sync” button in the watch that marks the activity to not be automatically synced. A new crop screen in the app. A manual “Sync to partner services” button in these activities. This sounds like the simplest/cleanest solution technically, I’m interested what Suunto devs think. Btw I also saw that Garmin Connect’s mobile trim feature only has a time select which would be more than enough for resolving the issue. [image: 1769003810445-19d2da956cfe66703079c2b9fcbe32aea86843647c74ef5cd41b7ffec1cb610c.png]

It worked, but I had to delete the app on three devices (including my iPad). The workouts I was looking for weren’t displayed correctly on any of them, which I hadn’t expected. Thanks a lot @2b2bff for the help , things always go really well here in the forum. Thanks @pavel.samokha and sorry for the panic

@jjpaz Small oscillations in altitude aren’t necessary added to the ascent and descent. There is a threshold. The best way to observe that on the watch is to have a custom data screen with the altitude field side by side with ascent and descent fields. These fields don’t change at the same time.

Under 2.50.26, I notice that my overnight, off-wrist battery consumption approximately doubles (vs 2.46…) My only change for the new FW was to enable North-up mapping. 2.50… did add the wifi weather updates (which do not work for me … could there be repetitive attempts by the watch to connect to wifi and the App that drain power?)

@jmolenaar2 said in My Vertical 2 Wishlist for Next Update in 2026: During the activity swipe to this screen and there would be a button to turn the flashlight on or off. Even some gesture to brightness could be there. Tap to turn on and off. Swipe up or down for brightness. Cannot rely on touch. That is no go for an outdoor watch. That would be useless in a rain or even when wearing a long sleeve shirt when the sleeve covers the watch. When I wear a long sleeve shirt I pretty much cannot leave my watch on the map screen because my shirt sleeve starts panning the map all the time. The best solution I can think of is double tap on the lap button. Implementation of the double tap can be a bit tricky because the first tap would have to be ignored and not trigger a lap, but it could be done. Another possible solution is combination of two buttons where the second button is pressed before the first button is released. Garmin does actually have that for some of the button shortcuts and that works reasonably well, but buttons should be on the opposing sides of the case for that to be usable.

@2b2bff said in Survey time: @Dimitrios-Kanellopoulos is it just me? I get an internal SSL error while opening the website in a browser… I get the SSL error on my phone with Android. It works from PC.

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

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

@vinc14 …

I had the same issue yesterday and today the heart monitor stopped working. After a hard reset, the HM came back and it is not working