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

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

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

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

ah here https://www.suunto.com/en-gr/sports/News-Articles-container-page/suunto-core-2-vs-core-1-whats-new-and-why-it-matters/

Tiny fonts again - poor.

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

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

@VoiGAS for the EON, thats correct as they hold both tables. You can switch over or set Buhlmann as default where locks do not occur. But this does not downplay the fact that the ceiling was not followed and decompression was not finalized. This will have impact on further calculations as Buhllman uses its nitrogen buildup for further calculations. So better not to have these sitiations and allways follow the indicators on the computer to the letter. Suunto does make the difference between voluntary or mandatory decompression stops. The RGBM lock only applies to the latter. The screen showed in the link indicates a mandatory situation which is explained by Suunto… you get a warning to go to the ceiling of 6,5 meter. You need to do that within 3 minutes and sit out the deco as long as indicated by the EON, in this case 75 minutes which is far from beeing recreational… If you fail - after warnings like the red ceiling indication and audible signal - to comply within 3 minutes, the computer locks for 48 hours. So you might say it indeed locks during the end of the dive.

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

@babychai No no, never used screen protector. Suunto saphire glass is very good, no need to protect it with a weaker layer IMO. But I think it’s a hardware issue, watch is not in warranty anymore, but I can live with it, until Suunto Vertical 3 release :). Cheers.

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

@Egika @maszop I can only share my experiences. I sometimes get the notification when my speed is clearly under 5.4km/h and quite often I don’t get a notification when I walk faster than 5.4km/h. I live in the Netherlands, not a really challenging gnss surrounding. Current pase with gps isn’t the most accurate, but I sometimes continue to hike for over 500 meter and then gps should have a fairly accurate pace.

@elbee Thanks for your input but I wasn’t buying it so did some further testing. Fired up my old 9Peak & connected the HR sensor to that, exactly the same outcome with constant connect/disconnect so it’s the sensor that’s faulty rather than my Race. I’ve sent it back to Suunto via online service request & as it’s only 8 months old I’m hoping for a warranty exchange

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

@Squirrel don’t know. This is iOS beta 3.13

@bbx100 Thanks for sharing your insight, much appreciated. My race2 is only 10 months old, so I have another 14 to go before it is out of warranty. So far, everything is still working again as expected after doing about 10 ‘moves’ and daily use. Let’s see how it goes with the next firmware update and onwards. If this happens again, I’ll definitly report to Suunto support.

I don’t see this too much on trails but 100% on roads. I think they over corrected a bit with this last update. I constantly get “off route” notifications simply being on the other side of the street running in the correct direction.

@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