Race S: Extremely high battery use rate
-
Confirmed on my watch too. Before sleep was 15%, in the morning 9% - DND on, 24/7 HR, lastest software 2.50.28.
-
I just tried:
- Race 2 Watch face, with always on display
- 24h after charging, 1h20 of GPS activity (biking with a chest strap)
- 24/7 heart rate (but no SpO₂)
- wore the watch the whole time
I lost 29% battery (from 100 to 79)
So long and see you next software update for another try, I’ll go back to my forerunner 255
-
@snow so charged the watch 100% Sunday morning and got 75% after 5h activity with tracking and auto pause. Then no activity only kept the watch with me, now it is Wednesday 21:00pm and I’m at 10%. Seems still high consumption to me. I remember I could get 6/7 days of battery life without activity.
-
@Michele-Sella Yes, the battery use is easily twice as high as it used to be.
For example this morning during a 40 minute gym training without GPS it went down (according to the information stored in the FIT file) from 33% to 31%.
7 hours later the watch is already at 23%. That isn’t normal by any means! AOD is off.
-
@Michele-Sella I thought a factory reset would definitely fix the problem, but unfortunately, it’s gotten even worse now. I could be wrong, but as I said, it seems to depend on when I start using bluetooth. Now I restart the watch after every use of the chest strap and GPS just to see if anything changes. I hope Suunto starts looking into this regression
As @sky-runner says also for me AOD off and even 24/7 HR off to save battery now
-
@gagbo said in Race S: Extremely high battery use rate:
I lost 29% battery (from 100 to 79)
Thats 21% and expected as the watch with AOD will only get about 5 days - less if actually used…
Race S
-
@2b2bff my bad, it was to 71%, one too many 9
But I guess counting for 80min of GPS and 24h of AOD that would still be within spec (30h GPS is 3%/h and 5d AOD is 20%/d so 23 vs 29) I guess I misread the specs
-
@2b2bff I currently observe about 20% loss per day with display wake on wrist (no AOD) and all other settings being default. For example, my watch lost 22% (from 31% to 9%) in the time period since 9am yesterday to 11:30am today.
According to the website the expected battery life in smartwatch mode with these settings is 9 days, but the real battery life is about twice as short.
-
@sky-runner I have AOD enabled and get about 4 days, I guess. So, not extremely high, but mabye a bit more than it used to be…
Next update is around the corner, so let’s see what it gives us… -
A soft reset after using the chest strap seems to mitigate the issue…
Edit: yesterday at 6 pm I updated the watch (version 2.53.42); the battery was at 40%. I went for a 30-minute run wearing the chest strap and didn’t perform a soft reset afterwards. This morning at 6 am the battery was at 36% (sleep, hrv enabled). So far, so good, I’d say
Edit: after four days of heavy use, afaic the battery is holding up well so, barring any last-minute surprises, I’m happy with it now
Edit: the last one I promise. Today I went trail running for an hour and 40 minutes with the navigation screen on the whole time. The battery dropped from 86% to 79%
-
Feedback after updating my SRs Tuesday. Extra battery consumption seems to fixed to me and back to what is was on daily use. To be confirmed
-
I can confirm now : extra battery drain on daily use has been fixed
Suunto’s devices at home :
Vertical titanium solar
Suunto Race S
S9pp titanium sand
Suunto Wing & Spark
S9B titanium Ambassador edition, A3P, X6 -
@Tieutieu I am not so sure! I have a new Vertical 2. At first the battery usage was excellent. But once I connected and used Coros armband HR sensor for the first time, the battery consumption has increased to over 10% per day in smartwatch mode. The battery was at 55% yesterday. One day later, including a 1:30h run, the battery now is at 43%. A different watch but the same issue. That doesn’t seem normal!
Suunto: Ambit, Ambit 3 Peak, 9 Baro, Race S, Race Ti, Vertical 2 Ti
Garmin: Forerunner 210, Forerunner 610, Fenix 6X, Fenix 7X Ti -
@sky-runner said in Race S: Extremely high battery use rate:
@Tieutieu I am not so sure! I have a new Vertical 2. At first the battery usage was excellent. But once I connected and used Coros armband HR sensor for the first time, the battery consumption has increased to over 10% per day in smartwatch mode. The battery was at 55% yesterday. One day later, including a 1:30h run, the battery now is at 43%. A different watch but the same issue. That doesn’t seem normal!
Before this update, I had noticed a significant drop in battery life, and the only solution I had found to mitigate the issue was to perform a soft reset after using the chest strap. After the update, I also performed a factory reset, and now afaic the battery is working properly
-
@sky-runner this thread is in the Race S forum and has Race S in the title. I guess it is related to the Race S then?
Race S
-
@2b2bff said in Race S: Extremely high battery use rate:
@sky-runner this thread is in the Race S forum and has Race S in the title. I guess it is related to the Race S then?
Not necessaraly. There is a generic race s topic on this forum, but not a generic battery issues topic. It only means people with a race s complain, but doesn’t imply the problem is hardware, software, settings or user related.
-
@elbee I mean all the Race S people say: It is fixed. Then a guy with a Vertical 2 says: no it is not.
There are other Battery drain topics, but this one has been for the Race S.
-
@Tieutieu Not for me. I’m still seeing 20% drain per day.
-
@2b2bff said in Race S: Extremely high battery use rate:
@sky-runner this thread is in the Race S forum and has Race S in the title. I guess it is related to the Race S then?
I know this is a thread in Race S forum because it was me who started it.
I suspect this is a software issue so it is likely the same across all models. Anyway, I haven’t had a chance to verify this with Race S. Perhaps I’ll do that next week. Currently I am using Vertical 2 and Race S is unused. -
@sky-runner said in Race S: Extremely high battery use rate:
I suspect this is a software issue so it is likely the same across all models.
Indeed as software issue, but maybe connected with the changed HR sensor algorithm? In that case it is a solution solely for the Race S. But who knows…
Interested about your results…
