Software Update 2.48.16 (2025 November Rain release)
-
Battery drain can generally be caused by certain systems not properly switching off after use.
One is external BT sensors.
Another one could be the GPS chip (and possibly navigation calculation) staying alive after cancelling an activity, etc.
I know that the devs are aware that there are still issues in certain cases and that they will of course be fixed. -
@Bartek-W that is what I said all the way. I did a hard reset and after that all BT connections were killed. Now I have 53 % left after 7 days with some hours of GPS activity. Before the battery drained within a week
-
I definitely agree that there is a problem with the Bluetooth on the watches (especially the Vertical 1, in my case). I changed the battery in my Suunto belt a month ago, and it’s already at 50% battery life. That’s completely abnormal.
However, in my case, the reduced battery life only affects the Vertical 1: the Race 2 has excellent battery life. Furthermore, another indication that there is an issue with the Vertical 1 is that at night it consumes 3-4% of its battery, compared to the Race 2, which consumes 1%, with the same settings.
-
@Stefan-Kersting This finally annoyed me enough that I did a factory reset last night and it worked. I now only have my Polar H10 and Stryd food pod in the paired devices list. No more ghost devices.
-
@atoponce said in Software Update 2.48.16 (2025 November Rain release):
@Stefan-Kersting This finally annoyed me enough that I did a factory reset last night and it worked. I now only have my Polar H10 and Stryd food pod in the paired devices list. No more ghost devices.
I did a factory reset as well with this latest firmware (Race). Unfortunately, my H10 (again) after some time all of a sudden turned into a ghost sensor.
So, the underlying bug is still there on the latest firmware and a hard reset only seems to fix the issue with ghost sensors (and battery drain) for a short time. At least that is my experience.
-
@duffman19 I too have the same problem with using already paired sensors of the same type (Polar Verity Sense and H10). Thanks for posting the work around, because I’d resorted to pairing and unpairing HR sensors, as we had to do originally before the ability to use multiple sensors of the same type was added (albeit imperfectly, as we have found).
It would be great if this could be fixed.
-
@Brad_Olwin Why in the name of god aren’t custom sports modes able to save to the app?
Seems like a huge own goal to have people set them all up again should a watch issue come up.
These along with custom zones, alarms, and general watch settings should all be backed up so a full restore can be done without having to set these things up every time.
-
I am now totally convinced that this update hasn’t fixed the battery drain issue for me, it maybe even made it worse, and that the cause lies in the connection to my heart rate belt.
After the last full charge and soft reset, I always unpaired the sensor after using it. The discharge after a running activity (typically in the morning) until bed time was around 3%. Today I forgot to do it, I finished my run this morning with 75% battery and it’s 67% at night. Phantom vibrations are occurring every time I “wake up” the hr belt by moving it. These were never present before the update. -
I have done 2 x separate hard resets on my vertical 1 . The battery drain seemed to improve only for a short while. As soon as the watch is being used in normal training again etc the battery drain resumes
-
same here, vertical 1
i see .5% burn per hr in smartwatch mode.i don’t use any connected sensors…
with 3 to 5 gps activities, i’m charging every 5 or 6 days. super frustrating.
