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

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

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

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

@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

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

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.

I’ve been having the same problem. It happens while in activities (the activity still saves afterwards but always looses 9.1seconds off the end.) if I have a guide running it restarts about 3 out of 5 times at the end of guide/interval. I’ve tried disabling all suunto + guides, navigation etc it also happens when not inside an activity but while on the normal, day to day watch face also. I’m reverting back to the previous firmware now (April’s version) because I know it didn’t do that then, which is a shame as I was getting used to the map labels.