@wakarimasen said in Race 2: GPS, cadence and distance accuracy vs previous Suunto models: I think we may be ‘agreeing violently.’ Agreed! Nevertheless, I would be very surprised to learn that ‘official’ mapping is carried out by someone wearing a Suunto, Garmin, Polar or Corus device, and declaring the data ‘accurate.’ Only for OpenStreetMap I made an interesting observation a few years ago when testing the SV1’s different GNSS presets (Performance vs. Endurance vs. Ultra). It seems that, as the GNSS accuracy/signal/capabilities (whatever you want to call it) increases, the measured distance decreases. Makes sense as fewer errors mean straighter lines and less distance. So it could stand to reason that the newer watches have even more accuracy, therefore measure slightly less distance. However, I think this goes against all the work and analysis that @jjpaz has provided us here. It clearly looks like new watches have a different algo. My money would be on it having something to do with battery savings for those big, bright screens.

@GiPFELKiND You know I am a field tester…When I get home I’ll send a photo on V1, I think it is on there.

@Sportsfreund try this https://testflight.apple.com/join/DJyDC5SU?fbclid=IwAR3jTWlAkPOE4uL_3ehgsHHRV4SGRXAM9NCWEFH34_aMtwfu_Ac6WYzQOJ0

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

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

@Egika I see what you mean. The imported GPX is treated more like a static overlay rather than a natively planned route. For TbT to work, the Route Planner would need to ‘snap’ the GPX to the map and recalculate the path based on the map data upon saving. This is the only way the system can generate the necessary turn instructions.

@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

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

@giuliosq Wrist heart rate is highly individual. What works for you does not work for others and vice versa in all conditions. A car is designed to drive around a corner. Yet it does not what it is designed for if you try it on an icy surface.

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.

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

@Audaxjoe I’m afraid that the times are stuck for me.

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

@el.Fakir Gôôd luck.