@GratefulDeadpan said: I have a hypothetical question since there seems to be a lot of se in here. IF (big IF) Suunto moves away from the old OS running in V1/V2/R1/R1S/R2 and instead Run future watches on the Run OS. What does that mean for the current line of watches? Can they be flushed with the new OS or are they relics (albeit working still, but still abandoned in a sense). Wondering if I should return my V2 and just wait this out as my Run is working just as well as the day I bought it. I have zero technical knowledge but I think it can be similar to what happens with garmin on their platform (fenix 7/965) vs (fenix 8/970) , the old gets bug fixes and some features but most features don’t come to it. I belive it is a bit like it as always be…ambits vs spartans vs suunto 5/9/9 peak vs 9 peak pro vertical 1 vs race/race s (anyone correct if wrong). There is the latest and greatest…and yeah slowly less features…

@Brad_Olwin said: @raven I agree with @sky-runner on Garmin Stamina. An hour or two into a 50k race my stamina is 0 but I was able to go another 4-5h at the same effort and finish the races within 6-7h. When I had a Garmin watch I replicated this several times. Yeah, seems long endurance efforts isn’t the strong point. For me that’s fine. I may do one 20km-22km effort a year, and most of the time I’m doing either 5km or 10km overall efforts. When possible, I like to get time on track and do interval work with 100m, 200m, 400m, and 800m targets, and recoveries in between. This is where ZoneSense might not even register at all for a shorter interval; I might do 200m at 3:30/km, then switch to a walk and see the entire time was “green” as the effort wasn’t long enough. That’s not a slam on ZoneSense; it’s not what it’s meant to do. I’m curious if situations like that might actually register with Garmin’s Stamina or not. Post-session, I can model workouts on intervals.icu and see W’bal effects when I go above my running FTP, but during session there’s no real tool for this I have at the moment. Here’s an example (4x 400m) with Suunto/ZoneSense on left, intervals.icu on right: [image: 1785886036662-5cbf3170-2bf9-4b6b-bd98-26254ab9c2dc-image.jpeg]

@2b2bff Yes, I’m aware. I would expect the watch to refuse executing a 3rd app, regardless if it’s an app or Guides workout, rather than hard crash and reboot.

22:17 cardiaque pour vous assurer d’obtenir les mesures les plus précises. Par défaut, la valeur FC repos est définie sur 60 bpm et la valeur FC max est définie en fonction de votre âge. Ces valeurs de FC peuvent être facilement modifiées dans les paramètres sous Général » Personnel. @ CONSEIL: Pour définir votre valeur FC repos, utilisez la mesure de fréquence cardiaque la plus basse mesurée pendant votre sommeil. Depuis le cadran de la montre, tournez la couronne ou balayez l’écran vers le haut pour faire défiler jusqu’au widget des ressources. 16 h 85% … Récupération suunto.com

@segi_pn when it will be considered ready for beta testing, it will be enabled in beta. Until then, it is not complete and not worth testing.

I’ve had my V2 since mid October and so far not a single crash. I always run 3 S+ non-third party apps. No other issues either.

@b_nino it was mentioned like million times already. This is comunity forum, it is not a Suunto support forum. Maybe people from Suunto read this, maybe they don’t. If you need support, contact the official channels.

@prakalejas worth the try, have you experienced this yourself? Are you sure adding the POD to the side of the computer arm is solving the dropouts of the computer? Did you analyze both situations?

@tomvanacker well known. I usually charge my watch shortly before going to sleep. The stress is somehow reset while sleep tracking, So, it doesn’t bother me much.

@sky-runner Yep, that’s exactly the same thing. I just upvoted your post.

@maszop said: @Kaiphi Link both accounts and they’ll sync automatically. it is what I do and works ok

I am in Scotland within a mile of the sea. I’m noticing a pattern with the tide widget. The last 2 weekends it has updated without me doing anything different and then will not update again for the rest of the week until the next weekend. I think it will update again this weekend if this pattern continues.

@phck9b It works in the simulator, but I don’t have a S9 Baro device to test. It may be crashing due to low memory, I refactored it once to make it fit in the Vertical 1’s runtime, so that’s likely. If you have VS Code, maybe you can share the watch’s log file.

A year and half since this issue has been reported. There are 27 upvotes. Are there any plans to fix this?

It’s a really good idea ! It can be at the same time the occasion to change the low/mid/high system for brightness by adding option ‘dimmed’ and ‘red’ or do a slider for more precision.

@Marcel-W hast du dazu einen Screenshot, was du meinst? Beide Werte sind doch da. HF sogar über die Zeit als Graph…

For the curious, while reverse engineering some features on the ambit, it is the POIs from the ambit that don’t contain altitude. Not linked to suunto app.

I have a Race S, and 2 weeks ago i did a factory reset because of something, i don’t recall what. But now the battery also goes down much faster than it used to, equivalent to what other people here are reporting: 7-10% per night. Bluetooth announce is off i now even put oxygen stuff disabled (for night monitoring) and DND for the night

I have been trying to build something like that but had not time too look in it further. https://forum.suunto.com/post/187238 It works in the simulator but not yet on the watch. Maybe I dive into it again after finishing my other projects.