@elbee Thats a sign for a battery management problem. Full cycle charging helped in my case

Maybe, they could fix the firmware just to get live tracking app functional again.

@raven While I would never use “pause and resume later” (and in fact I almost never pause my watch at all), I do agree that there is a lot of value in recording non-performance fun activities, and I see how stitching multiple separate sessions together into a larger activity is appealing to a lot of people. For starters, there is a growing tendency to share such fun non-performance activities on Strava, posting with a bunch of photos. I kind of enjoy when others share that. For example, someone can go explore a city while traveling and take a lunch break in the middle. Sharing that as a single activity on Strava is much better than spamming everyone with multiple short activities. Personally I just keep the watch running, sometimes even when I go into a store, and then I let Strava automatically remove all non-moving parts. But I can see how pausing and resuming later would make more sense to many people.

Why Suunto, why… Today, a new bug with the watch face. You didn’t correct the previous bugs with the watch face either, and today a new bug appeared on the watch. And this morning I didn’t get the morning report again. I didn’t get the morning report yesterday either.

@johann.fuehrer Sorry to hear that. It’s really annoying when the record of an activity is not complete. I really hope as well, that Suunto will find a solution to this (soon).

@isazi Thanks for answer! But I had the restart with settings lost yesterday, so I can’t be faster :-(. So the right procedure is to send logs and sent email to support@suunto.com? For now it seems, that I have to wait for next release and hope it will be fixed.

@Nandodiver Did you check the interference of the magnetic fields of the compass function for both devices + tradional compass when putting them all so close to eachother?

@VoiGAS said: @André-Faria 76g weight can’t be true - thats too heavy Yeah there is no way they tack on an extra 40g from the Run 1. Misprint or different watch.

@Horizontal_2 So you’re a lucky man. I’ve had mine since October as well, and ever since the previous update I’ve been experiencing restarts. Yesterday, after a restart, all my sport profile settings (data fields, etc.) were wiped. If this isn’t fixed by the end of the year, I’m returning the watch and moving on. These exact kinds of issues are why I left Garmin and praised Suunto. Now it’s a disaster. At least Garmin had settings backup.

@brechtvb said: and charging on a power bank triggers bugs and boot loops (I have experienced) Me too. I guess it depends on the power bank, but that is a huge issue…

@tm3610 said: With iOS, Garmin allows you to block app notifications per app, and you select it on the watch. only with newer watches, though. Garmin isn’t utilizing the new iOS notification model, where you can change on watch notifications per app. Neither does Suunto…

@Tieutieu Battery drain: Same here

@sky-runner I asked again

@Migsey wrll, my dive this morning was with the new firmware and I noticed that after a minute the SAC value started high and graduately leveled around 12 / 13. But you have seen the tank pressure, so it simply cannot have anything to do with the POD as it only transmit. The Nautic picks up the signal and applies it’s magic with tank sizes and internal calculations. Did you check the tank size and dive mode like single multi gas in the settings? [image: 1787495145871-screenshot_20260823_125600_suunto.jpg]

@hhouter Compass takes up two data fields. Tank pressure definitely cannot be seen along side with compass.

@the_jav You also talked about this interaction with data, like zoom and selecting a display window. That is what a mean by too complex for a tiny screen. And I don’t think you can draw a conclusion how data is handled based on how different parts of the ui look. The data can be the same but the widgets might be programmed by different people over a longer period in time (older widgets might not have been rewritten to benefit from newer functions in the os)

@boxwex no, I only know that this is being tested

Hello, same issue here on my Suunto Race 2 (firmware 2.56.18]), three swim sessions in a row now where the saved distance ends up way lower than what I actually swam, plus garbled interval durations like others are seeing. One thing that might help, the corrupted “total_timer_time” values in my .fit export aren’t random, they’re always just above 2,147,483.648s ==> exactly 2^31 ms. Classic 32-bit overflow ? Subtract that and the durations line up perfectly with the good lengths, so the data’s still there, just wrapping wrong somewhere. Already emailed support with a sample file.