@sky-runner said: @withManish said: too many features add unnecessary load on it, and it finally crashes. Let it be a modular software system; I download what I want rather than loading everything onto the watch. Features that are not immediately used don’t really add any load. I am a software engineer with 30+ years of experience and the above doesn’t make much sense to me. The reasons for the crash are likely way more nuanced and difficult to reproduce; otherwise they would have been fixed long time ago. My strong suspicion is that that the root cause is in fact due to an attempt to make the software more modular with parts of the software running as independent apps. The mechanism to make it modular uses a web app like execution environment with Javascript and garbage collection (Duktape Engine), which I imagine is hard to make work 100% reliably on a watch hardware with such limited resources - both CPU and memory. The reliability issues likely arise at where this engine is stitched to the rest of the operating system. I am also coming from the IT field; I understand what you are talking about, but the issue is I don’t see any intention to focus on core issues and give solutions, rather carry forward as it is with new system as well.

@Nandodiver I have the tank POD, i believe the transmitter only works with the older computers like Vyper and the D Range of dive watches. I bought the POD in the beginning of this year and i’m not aware that there is a new version available.

@GratefulDeadpan No, it’s not available on Android in the Beta version (in my opinion).

@VoiGAS said: @raven Did you try it with the same activity type for Warmup? So no Crosstraining - Running, but Running - Running? I heard this should work. Not happy with it as running activities also creates VO2MAX values. I more typically do a “walk” startup, then end and switch to “run,” but I’ve done “run” then “run” too and it didn’t make a difference. Admittedly it’s been a bit since I tried “run” then “run” so if an update changed things my info may be out of date but I don’t recall updated talking about improvements to ZoneSense on the Race S. Now it may be what is being referenced isn’t the ability to get ZoneSense “on” at start of session, but instead, a “run” then “run” might mean you can start the second run at race effort (i.e. no need to restrict yourself to only a warmup) in the first ten minutes, such that you still only see ZoneSense after the 10m mark but the fast start won’t mess up the calibration. That nuance I have not tested and I’d be uncertain how to verify. Yesterday I did a 2.2km in 18:07 walk with a little “pickups” here and there to make an average 8:08/km pace. ZoneSense measured my aerobic threshold lower than I’d expect, 134bpm compared to my normal 144bpm. Actual HR averaged 123bpm, max HR 146bpm so my pickups did elevate a bit. When I ended the walk I immediately did a run effort, which was 8m threshold, followed by 8m recovery, then 8m threshold again, for a total 5km in 26:50, average overall pace 5:22/km but “attack” efforts averaged 4:29/km and 4:36/km. Average HR 152bpm, max HR 168bpm. ZoneSense measured aerobic threshold as 160bpm, which is close to what I think of it at 162bpm. It did not make a recommendation for aerobic threshold. The second session did not “start” showing ZoneSense until after the first ten minutes. I did not rely on using ZoneSense for either session “live” as the first was too low effort to really care, while the second I was more focused on maintaining my attack pace for the work efforts, while the recovery I simply used standard HR and RPE to make sure I was down to zone2 but not allowing myself to get into zone1. So if the claim is “without that first session, the ZoneSense graph on the second session would be worse,” then perhaps. I’d need a second Suunto device to properly test that, using the first as normal, and the second not recording the walk effort at all and only starting it on the actual run, then compare results. But what I want is a “full” ZoneSense graph starting from session start to session end. [image: 1785847184995-d37e9f9d-e324-4f34-907a-166880ac1acb-image.jpeg]

@maszop can you give me some details about your disconnects with Vertical 2 and the new firmware? I will forward them to Suunto.

@matus69 I don’t even touch my phone. It is in standby. Then I tap update in the widget, and the watch seems to fetch data via SA in the background.

@Egika yep, I stiil have it in one of my drawers loved it so much!

@Colomers During the last 14 days, my watch has been restarting many times, both during active tracking and in normal daily use. I have already sent logs 3 times, but I have not received a meaningful response from Suunto yet. This is very frustrating.

@martintrail great to hear that tbh so if they have sufficient amount of developer bug fixing and other features can be done simultaneously priority based of course

@elbee you are funny. Often the car manufacturer will not even give an indication of the needed update We have a couple where we are negotiating for a buy back as they can’t solve a software issue. Life isn’t that hard with Suunto. I do have a wahoo and also have the issue. But I didn’t buy the V2 expecting to be able to broadcast to the bike computer so when I can it will be a bonus.

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

Crashed on me again, this time executing the following intervals.icu workout: Warmup - Easy 65-80% 20m Reps 10x - Run 96-99% 3m - Rest 30s Cooldown - Easy 65-80% 20m I was about 8-9 minutes in the warmup when I checked my watch and noticed that it was on the home watch face. Tried starting the workout again, it crashed, and powered off. I stopped and dug into the settings, when I noticed I had two S+ apps enabled. I guess starting a S+ Guides workout counts as a third S+ app and crashes the watch. I disabled both S+ apps, restarted the workout, and it behaved normally. I know the S+ app limit is 2 on the Race S, so it would be nice to have the watch inform me that I can’t execute the S+ Guides workout, because 2 S+ apps are already enabled. Hard crashing the watch is an unfortunate bug that should probably be addressed. Curiously, I pulled up the run activity, enabled 2 S+ apps, pressed “Start”, then while it was running, tried enabling a 3rd S+ app to see what would happen. Rather than failing gracefully, or just refusing to let me enable it altogether, the watch crashed.

@muellersjens Did you check again your previous activity in the app? HR is computed in the backend and sometimes it doesn’t appear good initially (if appearing at all). After this, what is saying your watch logbook for zones duration for this activity? Correct or same discrepancy?

@KSGravelJunkie Wahoo can’t choose between ANT+ and BT, whereas Karoo can, so it doesn’t have a problem with this … but I’m not sure if there isn’t also an identification error on Suunto’s part

@aiv4r is [image: 0UA9ixY] not a sign? Has been there since I dunno when. There are, from my understanding, already SuuntoPlus apps running natively on the Run, don’t ask me which as I’m not sure.

Well, scratches or cracks are permanent, even if the watch is well built. Since it’s a dive watch (close proximity to metal equipment / coral objects), I would rather change protective screen/case than the whole watch in case of an accident Anyways - print is couple of grams of filament and looks better in real life than in close up photo (could be even better if printed on smooth plate). Someone will definately find this useful.

@Squirrel thank you

I checked runs from Spring in this year. In April, with apparently the same setup, the R-R data recorded by the 9 Peak Pro looked normal. The recent recording contains repeated missing or corrupted R-R intervals and implausible HRV values. So it doesn’t look like a Firmware thing cause the major BT updates happend in Sept 25 and in January 26 April [image: 1785265928172-8e88a92f-036e-4a19-baf4-bdf31fd1923b-image.jpeg] Juli [image: 1785265951381-8f441eff-fefb-434d-ade5-fafcc40a355e-image.jpeg]

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