said in Vibrations et tonalités fantômes: My current guess is that it may have something to do with the compass auto-calibration. I am almost certain this is this issue now. To check this, I performed the following: Open the compass widget (make sure it is already calibrated). Bring a magnet close to the watch (doesn’t have to be strong, a refrigerator magnet will work). This will reset the compass and bring up the “Calibrate Compass” notification. Without moving the watch, back out to the watch face. While on the watch face, perform the calibration movement (figure 8). The watch will eventually vibrate, signaling that the compass has been calibrated. Go back to the compass widget to verify it has been calibrated. I’ve performed this several times and every time I get the “phantom vibration.” My assumption is that some of us are perhaps in situations that cause the 9PP’s compass to reset often, and thus we get the phantom vibrations more often than others. I know for me, getting in and out of my car tends to mess with the compass calibration. Even a simple act like opening the refrigerator (with all those magnets on it) could reset the compass, triggering the background auto calibration and thus the phantom vibration. @isazi @egika Is there a chance this could be verified by Suunto? Would this qualify as a bug? Although a minor inconvenience, it seems like something that could be an easy fix as it seems to only affect the 9PP. Edit: You can perform an even easier verification. Simply bring a magnet close to the watch while on the watch face (locked or not). Then perform the figure 8 movement. You’ll get the phantom vibration once it calibrates, no need to check the compass widget. Checking the widget just verifies that the magnet reset the calibration.

Seems like this is quite a common issue. I had same experience where watch rebooted total 3 times in my run… did some troubleshooting with support team and they got me to return my device for repair …

In my case, with the Vertical 1 Titanium Solar, I’m confident the issues started with version 2.43.12 released in June 2025. I had been monitoring battery consumption, which increased from about 3% per day during normal use to around 7%. It’s not a dramatic spike, but it reduces battery life from roughly 21–22 days down to no more than 14–15 days. Wouldn’t it be enough to check what changed between version 2.40.44 and 2.43.12?

@johann.fuehrer said in Weather Sync Bug: @Matthew-0 Maybe a dumb question, but have you already been out and let the watch aquire some satellite link to get your position? The app on the phone retrieves the weather data and it uses the (global) position of the phone, not that of the watch. The behavior as described by the OP I see when the suunto app is closed on my iPhone. If it is still running in the background all is fine and weather data can be synchronized to the watch.

@isazi Thanks for reporting swiftly

@zanxion I’m just here to say any change in functionality is preferable configurable, When I bought my watch, on the map screen the datafield showed the distance to next turn. For me that was logical and usable. With a next firmware update this was changed to distance to end. For me, that doesn’t make sense. I know when I arrive at my destination but don’t know the turns. I asked Suunto why they made the change. Support said someone suggested it, so they changed it. With the last update they finally made it user configurable, so everyone can be happy. And yes, the detect activity while on pause really doesn’t work well.

Thank you very much, I guess I’ll have to solve it that way as well. It would be great if Suunto could pull dive sites from PADI, SSI, or DAN so that you could get suggestions about where the dive took place.

@Nikolai-Simonov sorry, I missed that one. I have checked your code and it is extensive like for simple watchface. I thought it is easier to code such a things. I am struggling with google ai with my watchface. Can I send you my code for some help?

Hi. I also think the Vertical is still a good sports watch. I hope that in the next v1 update they’ll be able to include the altitude in the elevation contours in the maps at zoom resolutions that the MIP screen can display. Having them is useful in some conditions.

@halajos said in FW 2.53.2 Countdown timer vibration: @sindavide yes, I also experience it on the Race 1. The last beep, which should be longer, gets interrupted, therefore sometimes shorter or not even audible. By the way, having 11 beeps is weird to me, I’d prefer 9 short and one long. Yes, same here. Plus alarm in the morning interrupts without pressing button and no snooze.

@Nandodiver this is also my first view (default).

@Gunnar thanks thats good to know it looks like the watch is maybe doing some calibration for HR before you start but clearly mis reads and includes the faulty data.

I’ve had the same issue, I posted about it in another thread. Really looking forward to this being fixed as it’s my favourite watchface by far, unfortunately unreadable right now. For me it was fine until last week [image: 1776328672991-after.jpg] Not a biggie but I do agree it would be great if in time the top two fields (temperature & battery) became customisable in the future

@larrybbaker that is verry strange. I have had the watch since release and what I can remember it has never worked. But I could be wrong. And yes I have tried everything.

@sazzas i asked for this feature to be improved and take inti account our cycle phases such as pain atc…

On my vertical 2 this is not an issue. Even when I get coffee and chill in bed for an hour or some thing, it counts as sleep

I started using armband sensor because my Race S measurements failed, rapid drops, false highs. Last time I forget the armband used only the watch and it was fine. My theory is in the winter cold the OHR isn’t reliable for me.