Update: we solved it! In Whatsapp notifications setting > lock screen appearance, the “show preview” should NOT be set to “never”. This fixes the issue! (We thought to have tried also this initially, but we were wrong)

@cheetah694 ZoneSense isn’t aware of your speed, effort you put in, not even your current heart rate. It applies statistical calculations on a series of your individual beat-to-beat intervals (time between subsequent beats of your heart). If the statistics show a certain pattern, ZS will show you the respective zone. So its accuracy depends on, in addition to the applied algorithm, the quality of the data received from the HR belt, and your individual physiology.

@Nandodiver had to lough hard when the “soonish” was transcripted into “Suunto-ish” [image: 1769503821565-9013d03f-c96b-4e71-bb1b-8fc5e0e1fb43-image.png]

@Matúš said in Wrong HR during skitouring: @giuliosq, I know about avalanche transceivers but, since I’m not a skimo guy, I don’t know what’s the interaction between these devices. There are here some users that practice skimo so, maybe, they will share their experience! I am a mountain and ski touring guide, and maybe can shed some light on this: Yes, avalanche transceivers could interfere with other wireless devices. It is advised to keep them apart. The international MountainSafety.info (MSi) board has shared information on proper wearing of avalanche transceivers. Basically there are two ways: using the supplied harness, or in a zippered pocket. When the harness is used, this has a couple of disadvantages: There must always be a layer of clothing above the transceiver. This is difficult in spring conditions when you just wear a shirt. Plus it is more difficult to reach the device if you need to take it out from under your clothes in emergency. This is why me and most other mountain guides wear the transceiver in a zip pocket (zip must be closed). This way it is also far enough away from the BLE chest strap.

@JebClydeNC you mean this? [image: 1769500552430-385bbb39-05bc-4252-9c5a-9388a38cd530-image.png] Right, I don’t have it in the watch as well. Just - you have the fully pressure trendline. So this one would be redundant. The manual should be changed. As a selection for complications, I don’t find it in the manual, that it should be available…

I have a similar problem with my Race and Polar H10, where it gets stuck at 70-80bpm sometimes. [image: 1769498454420-screenshot_20260124-173404.png]

@duffman19 said in Backlight Bug 2.50.26: I’ve discovered an additional behavior of this bug. It seems that, even if you start an activity and the backlight/AOD is behaving normally, at some point during the activity the raise-to-wake feature will activate on its own. My initial impressions suggested that the bug was only activated randomly when entering an activity start screen. Now, I’ve noticed that even after starting an activity with the backlight behaving normally (no raise-to-wake, backlight off), after some unspecified time period, raise-to-wake will suddenly be on. I can’t confirm how long into an activity this occurs since I usually do not even look at my watch after starting, but it is always there by the end. So the bug is not the result of some sort of user input, but happens on its own. @dimitrios-kanellopoulos @pavel.samokha Is there a reason why Suunto has yet to acknowledge this issue? In my case (Race 2), the behavior is exactly the opposite: I have AOD disabled and “Raise and Wake” enabled. During the activity, the screen stays on as if AOD were active. If I pause the activity, R&W works correctly again. During the activity, when I skip Autolaps, sometimes the screen turns off again after 8 seconds. Outside of the activity, everything works correctly, so I’m sure it’s a software issue and only happens during activity. This hasn’t happened with Vertical or Race S.

@salusi I have the same issue, my current solution is to use an old Polar H10 I have lying around. There are other threads where people seem to have the same issue.

Please, create a search feature in the forum to let users find that an idea is already existing and, at least, help them post in the correct threads subjects.

@el.Fakir Gôôd luck.

@Divingpassion I am indeed disappointed if the answer from Suunto is that. I can understand that new dive computers do take a bit of time to get up to speed to the real needs of some divers. Maybe if other divers ask for a 13 litre tank, they might change there minds ?

@bivio thank you! this has already been proposed quite a few times. I am sure it is on Suunto’s roadmap

Haha, good catch @el.Fakir ! Maybe the next firmware with provide teleportation feature. Beam me up to the surface!

Teleportation bug: User @el.fakir caught a good bug in the dive plan: Suunto Nautic does not consider ascent rate in its calculations. Following screenshot red highlights that Nautic assumes instant teleport from 36m to 9m. [image: 1769418288877-c7da9e3b-ca88-4c13-b2df-c19ff83d1ebe-image.png] Link to original post: https://forum.suunto.com/post/184204

@Liviu-Nastasa Sorry, you shared your “official” distance and GNSS (RAW data) measured distance: 14,44km vs 14,65km. That’s the exact behaviour I’ve been watching. In previous watches (RaceS, Vertical), the official distance (recorded in the FIT file and showed in watch) is always close to the GNSS distance. In Race is always between 0.5%-2% less distance than its own GNSS distance so it seems a lot more conservative than SV/SRS in terms of distance calculation, filtering/cutting distance from the “viewed” GNSS raw data. If Suunto has been always recognized as top accuracy GNSS reception watches (dual band, very clean tracks, etc), the calculated distance would be closer to the GNSS distance, unless poor recepction or data is received and discarded for whatever reason. Then, why Race 2 is more conservative? It has a problem in its algorithm and understimate distances? Is it more accurate and then SV and SRS were overestimating distances? Who knows, it seems clear that the algorithm (and final distances, paces, etc) are calculated in a different way and are different. To be honest, I think that SV it’s been a bit generous and overestimating distances a bit, while Race 2 is a bit conservative. May be the “real” distance will be in the middle.

@MarkG normally there is no issue with activities that long. Hopefully a one off.