@André-Faria not really sure if it is a bug, it simply uses many more pixels, and complications that are updated per second (seconds indicator, compass), so it is more resource heavy than many other watchfaces

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

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

[image: 1787667921621-35aac4f6-43b9-4837-bdc8-a0f7bac8e812-image.jpeg] As an example of how I use intervals.icu here’s a recent running session. Let’s say at the end of this session I stopped and had lunch and then started again. That after-lunch effort is starting me from a very different state than I left off at the end of this session, and I don’t see a reason to connect them for analysis. My HR is fairly elevated at the end of this — in my mind, I’d need to first get my physiological state to “return” to this end-moment condition to justify “adding on” more time. Also note in the middle of this is a 33s walking effort and a second walking effort of 29s later, where I could have paused the session, but then it’d no longer be an accurate representation of how my body handled the overall effort. That time was important to see HR dropping.

I sent several logs and always emailed support@suunto.com as well. I never received a meaningful reply. A simple “we know about this and we are working on a fix” would have been enough. In the end, I took the watch to a Suunto service center. Today is the 8th day and I still have no update on the resolution.

Had a reply from divevolk : Thank you for your inquiry about the Divevolk SL50 underwater video light. Yes, our SL50 is equipped with electromagnetic compatibility (EMC) shielding. The housing is made from aviation-grade aluminum alloy with military-grade oxidation (Class III) treatment, which provides effective electromagnetic shielding. The product is CE certified for electromagnetic compatibility, ensuring compliance with international EMC standards. On the next dive i need to take my old dive lights to rule them out of interference.

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

@sky-runner I asked again

@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

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

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.

@HoBart we should have a proper Core 2 section in the forum soon.

Judging the long time of receiving updates i dearly hope some proper features or firmware overhaul is being prepared.

@Egika said: @Thorlap71 have you followed the recommendation of resetting your watch? It should definitely not reboot randomly. If this happens during exercise, maybe some S+ might be causing it. I have no idea if the next FW update will change something for you. Regarding mobile notifications: You can now select in the watch to be notified in watch mode and during exercise independently. Maybe re-check your settings for both cases. It works for me. Hello, For me it was reboot 3-4 times a day since the new firmware. During exercise as well as during “normal” watch usage. Right after the last reboot (during activity), I sent the log with the app. I tried soft reset, with no luck. I downgraded and no more reboot. Regards