@Kelley-Lim https://forum.suunto.com/topic/15621/suunto-app-stats-difference

@Kowalski I don’t know. I’m not a Reddit admin, so I don’t know the tools they have at their disposal to detect stuff like this. It may have been that there was malware hidden in the file hosted in the Google Drive file, and the Core 2 leak was the bait to get you to open it? Just speculating.

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

@tomvanacker well known. I usually charge my watch shortly before going to sleep. The stress is somehow reset while sleep tracking, So, it doesn’t bother me much.

@Marcel-W hast du dazu einen Screenshot, was du meinst? Beide Werte sind doch da. HF sogar über die Zeit als Graph…

@maszop said: @Kaiphi Link both accounts and they’ll sync automatically. it is what I do and works ok

Hi @Egika, Are there any news about this topic? Today I experienced another strange multiple lines on the track. It was here somewhere around here: 49.00919°N 17.04928°E And this is how it looks like: [image: 1787691940085-5463.jpg] [image: 1787691940286-5464.jpg]

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.

I may have found a related issue with my Suunto Vertical + Stryd setup. My setup: Suunto Vertical, firmware 2.50.28 Stryd paired as Foot POD GPS OFF Foot POD auto-calibration OFF I performed a controlled test on the same measured section of approximately 208–210 m. At easy pace, Suunto recorded: 206 m 211 m At faster pace, on exactly the same section: 348 m 289 m 281 m 290 m Stryd was also recording independently in its internal memory. The Stryd Offline Sync data looks normal and does not show the same distance inflation. I sent both the Stryd Offline FIT and the Suunto FIT to Stryd Support. After reviewing the activity, Stryd Support told me that Suunto was receiving Stryd data such as power/cadence, but was not using Stryd as the source for pace/distance. Since GPS was disabled, Stryd Support said that wrist movement was the source of pace/distance in the Suunto activity. I have already tried a soft reset and re-pairing Stryd, with no change. Suunto Support also has the logs, both FIT files and screenshots and is investigating the issue. This seems quite similar to the pairing/data-source behaviour discussed earlier in this thread. Has anyone with a Vertical + Stryd setup tested whether pace/distance really comes from Stryd when GPS is OFF? I would be very interested to know whether this is reproducible on other Vertical watches or specific to my setup.

I haven’t check if gas display is working below 30Bar But recently couple minutes after end the of the dive, i start to change tank for the second dive and the Suunto gave me brief alert of 3 bar remaining when i took off the regulator.

Upvote, are there any other traditional windsurfers

I come back to this topic, 2.53.42, seems like watch never gets my sleeping time and wake up time correct. I am off on my schedule, but I am moving, changing menus etc, kinda don’t understand how can the watch say I am sleeping. Is there any “manual” of good practices to not be like that or it will be corrected? In the previous firmware ª(on which also my sleep routing matched more the watch schedule routine) it worked ok for me.