I cannot fix the root cause in the watch, but export to FIT files (and Strava) should gracefully handle the corrupted records. At least to the level when no intervals have abnormal duration. To fix broken workouts in Strava you need to delete it, export FIT file from Suunto App for the workout and upload it to Strava

@GiPFELKiND said: @johann.fuehrer thank you! I will try this ️ I always clean my Suunto watches like every week with normal soap, old hand brush. Daily just with water only after training. Looks like new

@André-Faria already soft & hard reset. This is the newer replacement watch as the last one was warrantied a couple of months ago after same issues

@Łukasz-Szmigiel ok @isazi for the follow up just in case

@Thorlap71 Personally, I haven’t tried it. Someone I spoke to did it and I still haven’t received an update from him on whether it had any effect.

@pavel.samokha said: @André-Faria Hey, you’re doing a nice effort, but it’s unlikely me or anyone else from current Suunto employees would help with that. I understand that it’s fun for you, but for wider audience of Suunto users I have more important issues to solve than providing you materials. It’s also questionable if I can provide them at all without legal checks. For sure, and I totally understand that. If I didn’t ask I would never know. And thanks for taking the time to answer me, it is already nice from you!

@brave_dave Are you sure? Try running in 35°C heat and see for yourself.

@Efejota said: My guess is that the watch at some point stops using GPS to save battery in critical conditions I don’t think this is it. He said he still had 18% left at the end of the activity. On older firmware, things used to shut down more aggressively, but that was some time ago. The first low battery warning does pop-up at 20%, but does not affect any settings. IIRC, things don’t start to shut down now until around the 5% range. Although, I suppose things could be different for such a large activity. Perhaps the 9PP was running out of memory at that stage? The fact that the activity distance is longer than the GPX distance does suggest that it shifted into Tour mode (GPS logged every 30 minutes) for the final 1.5km, logging one final GPS point at the end of the activity, but not connecting it to the GPX trace. I seem to recall some other folks having issue uploading extra long activities to SA, but can’t recall if it was watch model specific.

@Mff73 Thanks, I’ll test it again. With every long press I should come back a view. Understood! As with Maps Zoom . But in fact I always came back a level but never again to the initial overview of the complete altitude curve of the complete route.

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

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

Also seems that the Paragliding activity (I use it for Hike n fly) does not use the advanced running zones. There seems to be little response here on the forum, does anybody know where to report bugs?

@prakalejas My POD sits on the left side of my 1st stage. During my dives the Nautic Always sits on my left arm and the Suunto EON Core on the right. And two times I received dropouts on the Nautic while the EON Core was just fine. So my expectation is still something wrong in the Nautic firmware and not with the range and positioning of the POD vs Nautic…

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

Learn more about Gustin on: https://gustin.szmigiel.design/ Detailed changelog will be published there as I don’t want to pollute app’s description in Suunto App with detailed changelog.

@Sieunhan_Binh said: @2b2bff Do you have sleep tracking and 24/7 heart rate monitoring enabled? Indeed, I have The manufacturer claims that if you train with GPS for 5 hours a week and keep heart rate and sleep tracking enabled, the battery will last at least 5 days. Where have you read this?

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.