@gonzosurfer what happened finally??? Did you fix it?

@MiniForklift And there’s SunMaxxi Pacer - what does everyone use these days?

For those that are still rocking a Kailash but fetched Android support, or even desktop support, you can check my app. Feedback accepted. Being happy owner of two of these beauties, it was tested on real hardware.

and please synch with Withings the weight, muscle etc

The new indoor climbing app looks awesome!

@Iggge Yes it works with Vertical. I just started to use Engo 2 photocromatic. Easy to check compatibility. In case you can install ActiveLook sport app to your watch in MySuuntoPlus Engo 2 will connect. [image: 1787986017789-b0377319-4a2e-4c04-a3c3-76bf8d397101-image.jpeg]

@joey-kimton Hi - I guess you are talking about the Sun & Moon widget, which does have limited information. However, there are two Sports Apps (called Sun & Moon…) which give a lot more information such as dusk/dawn time, moon rise/set. Obviously you can only use these during an activity but it may help you out.

@Brad_Olwin The new map colours are a clear step backwards in terms of readability. Trails, terrain and contour lines now use very similar shades, making them difficult to distinguish at a glance. This is not an aesthetic issue — it directly affects navigation, especially when using the map quickly while running or hiking. The previous colour scheme had much better contrast and was significantly easier to read. Please consider reverting to the previous colours or, at the very least, adding a high-contrast map style as an option. Good-looking maps are useless if you cannot clearly see the trails and terrain.

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.

Hi All Does anyone know when Suunto Ocean will get the drill function? Kind Regards Reino

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.