[image: 1786344212040-29362.jpg] [image: 1786344212067-29363.jpg]

@Elipsus Ultimately, it doesn’t really matter. According to Suunto’s specifications, the Core 1 watch could be used at depths of up to 10 meters. You can even use the buttons underwater. This has been tested many times without damaging the watch. Whereas, according to these specifications, the Core 2 can be used at depths of up to 2 meters only. So, it’s a hardware downgrade. This was confirmed in an email exchange with Suunto support.

@Adrian.S I’m having the same issue, no zoom at all. Route created via komoot and sent automatically to suunto app.

@metrodraft Try turning off and on the Bluetooth on your phone. I believe this happened to me before and that’s what fixed it.

I agree with the points above, the app is absolutely useless at this point. There should be a dedicated app for Suunto diving products.

During last 6 months my S9PP stopped HR moritoring / sleep tracking, so this is somehow related to last sw update as noticed already. Earlier this happened only once a month and always in the middle of the month, 17th-19th of the month. Now in August this was getting worst, 2 times in the beginning of the month and now again on last night (14.8)

let’s wait for the end of the hiking season and maybe the diving computers will move forward

Hi Same for me … I dive in salt water but I rinse the Nautic in fresh water after each dive

@Ze-Stuart thanks for the input. Due to your suggestion it has been a long 2 week low sleep work to built an ambit app with claude ahahh Lot’s of reverse engineering. Not easy. I am missing just some points that if someone can help (I believe from Suunto would be easier, @pavel.samokha @dimitrios-kanellopoulos @isazi ) How does the firmware decide a rule is a browsable WORKOUT (listed in the WORKOUT menu) vs a normal pinned display app? Is it purely that the rule is wired to the PID_RUNNER_GPS_TEMPLATE_GUIDANCE display template, or is there another marker (a rule flag, a CustomModes tag, an EXERCISE_MODES_RULE field beyond the 6 bytes [RuleIdx][UseRule][LogRule] we see, an Apps-entry field, …)? What bytecode/data does the guidance graph consume to draw a segment (segment count, per-segment duration/distance/lap end, upper/lower target, target metric)? i.e. what is the .Binary a Category:"guidance" rule compiled to — its structure, or the App-Zone/VM primitives it uses that a generic app does not? Is the guidance .Binary a different bytecode dialect than a normal App-Zone app, or the same VM with specific built-ins/opcodes for segments/targets? (If the latter, the live community compiler might be able to emit it with the right source.) Full claude recap here. These features that were lost in the movescount transition, and I am trying to get them back to the community.

Still working. Battery consumption was high, now usually as always approx. 4% per day. Upper button nearly unusable as it seems that no signal is sent to platina. A lot of power is needed to push button.

There is no feature I would love to see more on the Ocean than GF99 and Surface GF display as a switch view.

Hi, Is there any chance to get HR broadcast feature in a future firmware updates for Ocean?

@Ecki-D. I sync to Strava, crop there, export GPX, load it to Sport Tracker (after deleting the original). It works, but it is like trying to scratch your left ear with your right foot . Btw. This feature was asked for for at least 10 years