Software Update 2.48.16 (2025 November Rain release)
-
I have nothing quantified but here is my 2 cents analysis about battery drain.
Even after this update, I still observe a battery drain bigger than expected.
What I have found is that, after charging the device, if I turn off the watch and then reboot it, then the battery acts much more normally and without any suspicion of battery drain.
Does this make any sense ? Is it possible software or hardware wise that a shut down of the watch can somehow fix the battery drain issue ?
-
@v.sacre The reason is that, after first activity with BT sensors connected, increased battery drain can happen after finishing the activiy. My “workaround” is to soft reset the V1 after every activity… This bahavior keeps the battery drain in a “stable” drain.
I can test the “zombie BT process” powering on my Coospo HR armband, V1 vibrates as if it was connected to the sensor.
And this doesn’t seem to be happening in my Race S.
-
@runomatic I think there is something to what you just said. Coros shuts off, but others do not. I had to replace my Garmin HRM Pro + battery that had 85% before the update after the update. Left the HRM hanging in my bathroom. I think that it was connecting every time I was in range. I do not use the HRM enough to go from 85% to 5% in a couple weeks. When I approach the HRM pro + when it is dry it does not automatically connect. However any time I am in range of it while the belt is wet it will connect. Even just when I walk by and am in the connectivity settings.
-
@Александр-Даниленко I can confirm this, swimming algorithm is broken. I don’t really know if it is because of the latest firmware, or Race 2 (I have switched from Race), but last time I had swimming training watch missed distance by far. At the end of training I was paying more attention, it missed almost every second 25m distance, I counted more than 10 missed distances. My swimning style is exactly the same it was before, and usually it missed one or two distances in about 2.5km.
-
This are my notes of battery status with this firmware:
- 14.11. 19:20 100%
- 15.11. 20:19 94%
- 16.11. 21:14 87%
- 17.11. 18:27 81%
- 18.11. 20:12 71% (1h40m GPS)
- 19.11. 20:36 65%
- 20.11. 18:32 57%
- 23.11. 19:08 37% (20m non-gps)
- 24.11. 22:00 27% (20m non-gps
- 25.11. 17:53 20%
It looks like it would do around 13,5 day if i went from 100% to 0%. I run it with AOD off, low brightness and as you see i did almos no excercise. Since with 24/7 tracking it is advertised up to 18 days of battery life. This is not ideal but it is not worst too. I would expected at least 15-16 days with excercise i did.
-
@runomatic I use only the Suunto HR Belt which seems to make trouble
I wrote about this some days ago -
I have been recording battery drain for a good while however here is my data since this latest firmware update.
21/11 100% 5:20am
22/11 93%
23/11 81%
24/11 70%
25/11 55%
26/11 42%This is pretty typical of what i see from my vertical 1
-
@gone-troppo Which watch is this? If it is a SV1, it’s too high battery consumption, I think… how much training sessions do you have a day? For my usage, with about 3-4 hours of activity a week, the battery has to be charged every 4 weeks normally, and now, since the summer update about 3 weeks… it’s not bad, but it’s less than before!
But the issue with the chest strap is more annoying, because although the OHR is fine for normal running, it doesn’t work well when running with poles or cross-country skiing. -
@Stanislav-Damjanov Yes, I’ve noticed the same on my 9PP
-
@Stanislav-Damjanov said in Software Update 2.48.16 (2025 November Rain release):
it misseg almost every seconon 25m distance, I counted more than 10 missed distances. My swimning style is exactly the same it was before, and usually it missed one or two distances in about 2.5km.
Yes, the missed lengths have skyrocketed also for me over the almost exactly one year since I bought the Race S. Back then (December 2024) the algorithm categorized everything as "Free"style, but missed very few lengths. Then Suunto started to tinker with style identification…
What is now a fact, is that if the algorithm can’t identify the style, the whole length is discarded (instead of having a fallback to e.g. Freestyle). For me, as a competitive swimmer in the 1970s with Breaststroke as a specialty, this has a profound implication. Back then we were tought a very tight and quick arm pull, something crudely ascii-drawn like:
_( )_ \_ _/I am trying to illustrate a sort of < > pattern with the upper and lower arms. Using this style the algorithm discards about 80% to 100% of all my Breaststroke lengths. The watch starts to count lengths again if I use a more modern and wider competition arms style; again crude ascii:
_( )_ |_ _|It also count lengths quite consistently if I use the widest style of all, the slow recreational style tought by my father:
_( )_ / \Apart from having to relearn a swimming style (!), the problem with a modern wide arm pull is that it relies quite a bit on muscle strength. I am 65, so that style is very exhausting. And even as a youngster the idea of the tight arm pull was to quickly get them out of the way and use the legs as the main way of propulsion.
Anyway, these are my experiences… Since I do about 50% Freestyle and 50% Breaststroke the current situation is really disheartening. Last swimming session I left the watch at home - if it can’t count, there’s little use for it.
