@halajos no photo, it’s at bottom of screen, it’s small. I use the watch 24/7, and train 6-7 days per week

@Olaf-Gottschalk It might be software it might be hardware, that impacts software crash, but I think what this forum trying to tell you, that having crashes like that so often is not really normal and nobody else gets that. So you should contact Suunto and get it replaced or fixed. (Of course if you already tried that and was denied, I understand your frustration)

@Squirrel thank you, issue resolved.

Mistake on my part tss of tp was misconfigured indeed 1-2 difference thank you good evening

@halajos my bad. You are 100% right, I think it’s so similar to LCD bleed that I didn’t even think about it.

@mabe2k sorry, I‘ve just seen, that in the settings on the watch was a connection to the app. After removing it button was active. Solved now

@mabe2k great, thanks!

I am not sure if this is the same or a similar problem. Today I took the bike to get to work and recorded this as an activity. But the kcals are not shown in the active calories as you can see in the screenshot. The activity was between 06:30 and 07:45 with 85 kcal [image: 1760001924220-img_2371.jpeg]

My only tip is to slowly lower the watch down to the charger and let the magnets align themselves and “jump” to the watch. And then don’t touch. I have never had an issue with the watch not charging using that method.

@Brad_Olwin said in Map zooming with the rotating crown is inconsistent (unreliable): @sky-runner Suunto is aware of this issue and I believe working on changing it. MIP displays do better than the AMOLED. @Brad_Olwin, blast from the past! Back in May 2025 I complained that trails were barely visible at 0.5mi zoom level and disappeared at 1mi zoom level. You said that Suunto was aware and working on that. Apparently the solution was to make trails disappear at 0.2mi zoom. Do you know if Suunto is still considering improving this? Also I’ve heard that this works differently in some other regions, for example Denmark.

@Bjuanito nothing changed in that respect, unfortunately. I do not know the BLE standard for speed/cadence so I do not know if there is a way to determine if a sensor is speed or cadence (or both) and act accordingly

@isazi OK, got it. I read the manual and it is indeed mentionned that DND should deactivate in case of any alarm, thus sunrise as well. 🫣. I was not considering this as an “alarm” but more as a “notification”, I was wrong

@nseslija Thanks for the tip. Sadly, it looks like this problem has been around for at least 6 months. It’s been a long time since my watch was last rebooted or soft rest, so I’ll try that.