@matram said: @elbee You do not copy (typically). You maintain one repository. Top level features can be enabled / disabled when building the SW for different watches. Your architecture is layered with a UI layer, a service layer that has to be able to support all features (this is Suuntos current issue I think). Yes, I know. That’s how it should be. But if the same feature works slightly different on various watches and some bugs are fixed for 1 watch but not for the other, I can only conclude there is no 1 repository for all watches but a separate one for each individual watch.

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

@MartinPadiPro Yes, but let me guarantee you that you will encounter the same issue soon (if Suunto doesn’t fix the issue in an update). Between my first and second time I had 5 months diving without issues, between second and third, 1 month.

Just checked the “new” features in the video of the Ocean: They were all present in the latest update. So I guess we cannot expect a new firmware

Tide widget started working again today. Watch hasn’t left the house in the last 48 hours so I’m not sure what has changed. Perhaps Suunto has been working behind the scenes to fix it? Still not sure where they are getting their tide data from as it differs a bit from the tide tables of both my nearest ports. High and low tide times are out by between 10 and roughly 20 minutes on the widget. Still gives my location as Scotland, UK.

I still think it would be much easier – and therefore faster – to implement this in the SuuntoApp rather than in the watch software. You could achieve not only the same results but even more. Plus, you wouldn’t have all the limitations – sleep analysis, recovery, TSS, CTL, ATL, HRV, etc. You could also, for example, use different activities during a multi‑day trek – like swimming, climbing, or via ferrata – without having to deal with complicated activity session management or multisport mode. Additionally, full freedom of sensor management between different parts of a multi‑day activity. Reboot, update etc. between days etc. On top of that, it would be available to every user (like ZoneSense), not just those with the latest watches. And you wouldn’t have to pray that a crash doesn’t happen during such long and complex recorded activities. You could also relatively easily group and combine selected activities into one final one, and then – like with any regular activity – export it automatically to other services, just as it currently happens at the end of every activity. Especially since, in such a case, it’s really only about the total distance, elevation gain, duration, and a few less important stats like steps or calories. All the other statistics are far more useful on a daily (per session) basis for ongoing analysis.

@aiv4r Thanks, good advice! I am not blindly trusting AI. I have consulted a physiotherapist. Her advice and Claude had considerable overlap. Claude recommended a few more hamstring-related exercises and training one leg at a time to fix a left / right imbalance. Feels like good advice so far. My impression is that AI coaches (e.g. Garmin) are not good enough, they may actually be dangerous. An LLM trained on all the data out there and with access to your personal data may be more useful if you use it in the right way. Personally I hate subscriptions but I am willing to pay if they are truly useful. But my Claude Pro subscription is about 20 Euro and provides value apart from training. I would not be willing to pay a similar amount for an additional AI service that provides much less value.

Tiny fonts again - poor.

@freeheeler I sold my Ambit 3 watch when I bought my Vertical 1. Now I use a Vertical 2, but I haven’t sold my Vertical 1. I wear it occasionally. Legendary watches

@hhouter Great insights, thank you! I think the Mares locked during the dive - definitely something I don’t want. So I can stay with RBGM and if I want to switch the option is here to do it with similar behavior Edit: But in the Link you provided the screenshot shows a Locked screen while on 5m depth - could it be that it was just the 3 minute delay that allowed you to surface?

@VoiGAS said: The Run is the weight king (queen?) It should as it is one of its selling points…

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

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