Another random crash on my Vertical2 during a run today. Latest FW, no ZS, no S+, no sensors. Seriously, when are we getting a stable build? It’s getting hard to trust this watch for training.

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 elevation contours in the maps at zoom resolutions that the MIP screen can display. Having them is useful in some conditions.

@Egika My bad, I have a 9 peak pro and I assumed it was the same for all Suunto Watches ^^

@Egika it coulde be average fuel consumtion number that could motivate you to ride more

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 …

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.

@freeheeler nope I mean climb guidance

@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

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

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

@PhilBee said in new Vertical 2 - auto vs manual laps: yes i guess it must mean that coros record auto 1km laps since the previous auto or manual lap - but what’s wrong with that? to me that makes far more sense Nothing wrong. With that. With Suunto’s approach you can have an automatic lap on each km and an manual lap/interval whatever you wanna call it (in German they are called “Runden”) that are connected with some meaning. Especially if you follow a guide you might have something like 5 Minutes warmup 20 Minutes easy pace 1.6km as fast as you can 10km easy open end - run back home Each of these will become an individual “Runde”. This approach makes sense as well, doesn’t it?

@Nelson-Diogo ohhh, at least this makes sense also for Suunto … let’s see if they implement in there Race and improve in the Run

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

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