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

@MatthiasKlug said in getting too much ascent / descent on flat routes: @Dimitrios-Kanellopoulos … (edit: my first thought was that this behaviour is somehow temperature related (the bigger the temperature drop the higher the ascent) i just wanted to mention this, we will see if the outer temps get warmer and closer to the changing room, so there is less temperature drop) From my experience with the altimeter, it actually is not 100% temperature compensated. I found this when climbing indoor without GPS. I did 3 consecutive climbs in the second half of the recording. I might have gotten warm and the altitude is shifting downwards: [image: 1769164260259-db9acb8d-d9fb-4dbb-bcb9-684c6825ed4f-image.png]

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

@Liviu-Nastasa Sorry, you shared your “official” distance and GNSS (RAW data) measured distance: 14,44km vs 14,65km. That’s the exact behaviour I’ve been watching. In previous watches (RaceS, Vertical), the official distance (recorded in the FIT file and showed in watch) is always close to the GNSS distance. In Race is always between 0.5%-2% less distance than its own GNSS distance so it seems a lot more conservative than SV/SRS in terms of distance calculation, filtering/cutting distance from the “viewed” GNSS raw data. If Suunto has been always recognized as top accuracy GNSS reception watches (dual band, very clean tracks, etc), the calculated distance would be closer to the GNSS distance, unless poor recepction or data is received and discarded for whatever reason. Then, why Race 2 is more conservative? It has a problem in its algorithm and understimate distances? Is it more accurate and then SV and SRS were overestimating distances? Who knows, it seems clear that the algorithm (and final distances, paces, etc) are calculated in a different way and are different. To be honest, I think that SV it’s been a bit generous and overestimating distances a bit, while Race 2 is a bit conservative. May be the “real” distance will be in the middle.

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

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

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

I have a Race S, and I tried everything you mentioned here, but it still isn’t working for me. In my case, it started on the 1st day of the year… I hope there will be a fix soon. I liked the sleep summary in the morning.

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

@Dimitrios-Kanellopoulos All right It’s not what i’m expecting but it’s ok we can close this subject Thank you for your answers

I have a similar problem with my Race and Polar H10, where it gets stuck at 70-80bpm sometimes. [image: 1769498454420-screenshot_20260124-173404.png]

@tikgnd Спасибо тебе большое добрый человек, я потратил 3 дня на это, как я рад, что нашел твой комментарий

@louispar Works with no issues for me as well on Race S

@vinc14 …

that’s why I was asking for the temperature In general I suggest Suunto tinkers with OHR only during spring or summer time - then the feedback will be better

@el.Fakir Gôôd luck.