@isazi Thank you very much, I appreciate it. It’s a fairly easy implementation, I think this was purely missed with the last update, which is a pity, and hopefully they will include it now, since it’s not in the current test firmware as on your watch. I hope the next firmware update is around the corner. Also thank to @sergiob for pointing out where this should be in the menu. I can only hope to see it in the Ocean soon.

@isazi Yes, that is what is worrying me as in the Q1 and Q2 videos, features that was promised to be coming, never made it to the Ocean version 2.51.28 The links of the official Suunto videos said these will come to Ocean, but we are still waiting 6 more than 6 months later from when it was mentioned on the videos: Q1:https://www.youtube.com/watch?v=Jh0gD05DngU&t=2363s Q2:https://www.youtube.com/watch?v=t2QCoDLY5kQ&t=41s

@nikola giving this post a bump as well just to affirm i too am seeing this issue still.

@isazi Thanks, hope it will be available soon 🥴

My vertical 2 has not had any tide updates for several weeks after a few weeks of updating every 5-6 days for a few weeks. I am in Scotland within metres of the sea.

yes, I got this too. Claude research on this: This is a long-standing, recurring issue with Suunto devices, not exclusive to the Ocean. The typical pattern involves a green progress screen repeating multiple times, followed by “Error 1403” (sometimes 1405 or 1301) and the message “the device recovered from an error,” after which the cycle repeats. Charging is a known trigger—there is an entire forum thread dedicated to resets occurring during charging, showing this exact behavior. Error 1403 is interpreted as a memory or flash error; some units recover, while others require service. The consensus on the forum is that 1403 is a memory error—possibly a bad flash sector. Recovery doesn’t mean the problem is solved: there are reports of watches returning to normal operation for a while, only to crash during the first workout with the same 1403 error. The culprit appears to be Wi-Fi, not the charging process itself. The watch doesn’t remain idle while charging; once plugged in, it activates its wireless connection for background tasks. Firmware version 2.51.28 introduced automatic nightly GNSS optimization via wireless networks, in addition to map downloads. In a forum thread discussing this exact scenario—crashing during charging, a “restored to a safe state” message, and Error 1403—a Suunto engineer analyzed the logs. Unable to pinpoint the exact cause, they asked users to do two things: disable Wi-Fi on the watch (via Settings → Connectivity) and send the logs immediately if the issue recurs. One specific case supports this hypothesis: the crash occurred in an office where no Wi-Fi network had even been configured on the watch, suggesting a bug triggered by the attempt to connect when the charger was plugged in. What to do: Turn off the watch’s Wi-Fi (Settings → Connectivity). You will lose Wi-Fi map downloads, but Bluetooth syncing will continue to work normally. Send the logs now, while the event is still recent. In the app, the option is located at the bottom of the Settings menu or within the watch menu, depending on the version. Suunto Community Switch to charging during the day. There are two reasons for this: you can monitor whether the issue recurs, and a night spent charging doesn’t mean a lost night in your sleep tracking streak. Decision criteria If it freezes again with Wi-Fi turned off, the software hypothesis is ruled out, leaving hardware as the likely culprit—in which case, it’s a matter for technical support rather than a settings adjustment. In this scenario, the records you’ve already gathered (photo, date, “only while charging”) are what support your support ticket.

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?

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

@matteobucc said: ​Hi everyone and Suunto Team, ​I am an advanced freediver (diving to 50m+ and competing) using the Suunto Ocean. ​The hardware, display, and GPS tracking are absolute 10/10. However, for deep freediving and spearfishing, the software currently lacks essential features found in older dedicated computers or competitor models. ​To make it a complete tool, please consider adding the following in upcoming firmware updates. ​First, a single surface screen summary between dives that displays surface time, dive time, minimum temperature, and ascent and descent speed (m/s). ​Second, separate descent and ascent alarms, with the option to configure depth and time alerts separately for the descent phase and the ascent phase. ​Third, a dedicated spearfishing profile that silences audio and vibration alarms by default. ​Fourth, a dedicated pool freediving profile designed specifically for dynamic and static training without triggering depth sensor alarms. ​Fifth, advanced app graphs with clearer depth and speed details in the logbook for post-dive analysis. ​The hardware is top-tier; now it just needs the software it deserves. Thanks! I completely agree that the Suunto Ocean has some serious shortcomings when it comes to freediving and spearfishing. It is truly unbelievable that the watch cannot display the two most essential pieces of information for freediving and spearfishing on the screen at the same time: the data from the last dive (depth and duration) and the surface time. This simply makes no sense and is one of the biggest shortcomings of an otherwise excellent watch. I also believe the watch should have a dedicated Spearfishing mode. For a device called Ocean, it is quite disappointing that, despite offering numerous sport profiles, there is no option specifically designed for spearfishing. Another major frustration is the automatic activation of Scuba mode every time I dive. As soon as I go deeper than one meter while swimming or simply enjoying the water, the watch automatically switches to Scuba mode. As a result, it records false dive activities throughout the day and negatively affects recovery and activity statistics. I would genuinely like to understand the logic behind this software design. Officially, the Suunto Ocean is not recommended for professional scuba diving, yet Scuba mode is enabled by default, cannot be disabled, and its behavior cannot be customized. That simply doesn’t make any sense.

Well, scratches or cracks are permanent, even if the watch is well built. Since it’s a dive watch (close proximity to metal equipment / coral objects), I would rather change protective screen/case than the whole watch in case of an accident Anyways - print is couple of grams of filament and looks better in real life than in close up photo (could be even better if printed on smooth plate). Someone will definately find this useful.

@mikeller Bonsoir, Je voulais également remercier ceux qui ont travailler sur la possibilité d’un export des fichiers .fit de ma Suunto Nautic avec l’application Suunto afin de les importer dans la dernière version (PC) de Subsurface ou j’ai déjà toutes mes plongées. Encore merci !

@trianst Seems like General » Tones 》All off: no events trigger alerts NOTE: These tone and vibration settings do not affect scuba and freediving activities. See Dive alarms for dive alarm settings.

@GS-111 What i have is not the point. The point is that I’m not able/allowed to choose the size i might have… I can’t have 3 or 6 or 7,5 or other “not standardised” tanks of my need. A simple X,XX liters custom would not be that difficult it might even allow for less predefined sizes

@leorus have you set the depth for automatic start to the maximum?

The Nautic S now seems to have Trimix. About the Ocean I’m not sure. Does the Oceans Altimeter automatically adapt the dive algorithm for Mountain Lake diving? The Nautic S not if I got the manual right

In addition, it would be cool if I could add friends I follow as dive partners and they would also be found automatically with the name