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

@2b2bff said: @dreamer_ said: Personally, I don’t see anything wrong with Suunto deciding to release watches every year if it helps the company improve its financial numbers. After all, Garmin has been doing this for a long time, and now Amazfit is doing it too. Perhaps the 2 year wait does not have any sense if you maintain the older devices. This is also common in other devices like smartphones. The key should also be to maintain support for older devices for a period of time. The faster pace you release new devices, the more devices you have to support… That is the problem about releasing devices in shorter intervals. Or perhaps the revenue is a lot more than the cost of maintaining an additional device. That is something that only Suunto will know…

@Mikenizm I was comparing some of the four Mandatory Gas Time Alarms from my dives and found a dive where indeed things are a bit more complex and result in strange readings like the dive below. This dive intreged me as I was actually reading TANK PRESSURE: - - (0) during this dive at 33 meters. I can share the json if needed. [image: 1785558073201-screenshot_20260731_150907_suunto.jpg] Claude: There are two gaps in collecting data of this dive. The alarm fired 10 minutes in the dive at 33.27m. something structurally different then the other ones which were more in the 1 to 2 minutes alarm range at shallower depths. Dive context: deeper dive (max 34.36 m), and this time the first alarm hits at 9:30 into the dive. No elevated consumption beforehand — this wasn’t a noisy-estimate problem like the other files. Time Depth Ventilation GasTime 400–470s 21.6→28 m steady 0.0003–0.0004 steady 1280–1630s Then a real, extended data gap: Time Depth Pressure Ventilation GasTime 480.62–490.62s 28.7→29.6 m None 0 0 500.62–560.62s 30.6→33.0 m present, declining normally None None 570.13s 33.27 m present None None ← Alarm fires here 570.62–590.62s 33.3→33.9 m None 0 0 594.13s 34.1 m present 0.000188 37s ← alarm clears 600.62s 34.1 m present 0.000186 1729s What this shows: There were actually two separate dropouts stitched together: a short one at 480–490s, then a long ~70-second stretch (500–570s) where the pressure signal was fine but the computer simply wasn’t producing a ventilation/gas-time estimate at all (None, not 0) — then another ~20-second full pressure dropout right as the alarm was active. The alarm fired at the very moment the ventilation calculation had been dark for over a minute — likely the computer’s watchdog flagging “I can’t tell you your gas time” rather than a genuine low-air event. When data finally resumed at 594.13s, it briefly computed a startling 37 seconds of gas time — before jumping to a much healthier 1729s just 6 seconds later. That 37s figure is a transient artifact of restarting the estimate on stale/limited data, the same pattern as the first file’s dip, just far more dramatic because the gap was longer and happened at depth…

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

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

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.

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

@Audaxjoe said: @André-Faria I work in car fleet management. We struggle to even get a car booked in for diagnostics in that time with Main Dealers. How would you feel if you contacted one of those dealers about a car and they would say, we fixed the issue. You would ask, when can I pick it up? And they would say, we have a release moment 4 times a year when all fixed cars can be picked up. Yours will be ready with the q4 release.

@sartoric No, no protector, suunto has the best saphire glass And always clean. Maybe it’s a hardware fault as @tieutieu and @isazi mentioned. Well, glad to know that it still working as before on some watches because the timing it changes on mine, sure looks like it was being deprecated. Thank you all for the clarification.

@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

Test run today with a Garmin. Race2 passed with flying colors. A huge thanks to the developers. Great job, guys. [image: IMG-20260718-123733.jpg]

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

@bubuche I would use Runalyze or another external platform for that. Now I‘ve been using the latest updates for a bit, I think we‘re there. I thought about using predicted wind from the weather app, but you end up losing accuracy as soon as buildings are involved. I will look at using the accelerometer perhaps, but felt it was overkill when I started with this app. It might solve the grade latency issue though. I‘ll play around with it at some point.

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

@Squirrel I can only tell what I observe. The gnss data is synced right when your watch is connected to the suunto app on the phone. At least, at some point the sync process is saying it is syncing gps data.

@dnctr I can also confirm it is the beta. I reinstalled what I thought was the July beta and it is now there. It is July Candidate 1, 3.13.0

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