Software Update 2.48.16 (2025 November Rain release)

dani_degi

no problems with Battery Race 2

9-10 tage 10% a Day… 6-7 hours gps and 1 2 hrs indoor cycl and 1h swim…

easy

Kramble

@runomatic said in Software Update 2.48.16 (2025 November Rain release):

@Brad_Olwin I can confirm that. I have a V2 here for testing right now. After almost a week of intensive use, I still have 64% battery life. I don’t have any BT problems either.

By the way, I didn’t have any problems with my V1 either.

Could tell me the daily consumption of your V1 without activities but with OHR24/sleep tracking?
Historically it’s between 3 and 4 % (I’ve got my V1 since the release) but since the last updates it’s between 6 and 7% for me and some others.

runomatic

@Kramble said in Software Update 2.48.16 (2025 November Rain release):

Could tell me the daily consumption of your V1 without activities but with OHR24/sleep tracking?
Historically it’s between 3 and 4 % (I’ve got my V1 since the release) but since the last updates it’s between 6 and 7% for me and some others.

I would love to, but shortly after the last update, I received the Vertical 2 to test and have been using only that watch ever since.

duffman19

@Brad_Olwin said in Software Update 2.48.16 (2025 November Rain release):

Those of you having battery issues, it is not everyone.

Like most people posting here, I don’t assume my issues apply to every watch and every user. However, this doesn’t negate the fact that many of us are still experiencing one of the problems this update was intended to solve.

I think we’re all in agreement that the battery drain issues are somehow related to overactive BT connections. Personally, I suspect it has to do with the implementation of multiple BT sensor connections as this function has never worked properly for me since it was introduced. Perhaps the issue is only affecting those of us with multiple BT HR sensors? Or maybe it is only specific external HR monitors?

My experience
I have two external HR monitors paired to the watch: a Suunto Smart HR Belt and a Polar Verity Sense. If I use one of them for an activity (let’s say the Suunto Smart for a trail run), and the next time I choose that same activity I want to use the other sensor (so another trail run, but with the Polar VS), it is guaranteed that the watch will not connect to that BT HR sensor even though it shows as one of my available paired devices.

Even if I go into the activity settings (Exercise options > Sensor data) and select the correct “new” HR and then back out to the activity home screen, it will not stay connected. Currently, the only way to connect the new HR is to select a different activity profile altogether (so, let’s say walking), go into that activity’s settings, select the correct HR, back out of that activity (still doesn’t show the HR sensor is connected, btw), go to the original activity I wanted to start (trail running in this instance), and now the correct HR belt will usually show as properly connected.

I’m guessing this wasn’t Suunto’s intended behavior for having multiple BT connections. And since there are so many issues connecting to different BT sensors when attempting to start an activity, it stands to reason that there are also BT issues outside of activity mode that are causing severe battery draw. For me, I still have phantom vibrations outside of activities suggesting that the watch continues to attempt to connect to my external sensors.

Further, the increased battery drain only occurs sometimes. It is not a constant for me. So some sort of action or behavior is causing it, perhaps related to the dance I have to do to get my external HR sensors to connect.

I obviously don’t know the answer, but that’s why I’m posting my observations here in the hope that it will help lead to a solution.

jjpaz

@duffman19 That’s exactly the behavior I’m experiencing.

I alternate between a Polar H10 chest strap and a Coospo armband. Every time I switch sensors, I have to select and connect it in the pre-activity menu, exit the activity, and then re-enter.
And, afterward, especially with the Coospo, the battery drains rapidly, and I get phantom vibrations if I turn the sensor back on.

How do I mitigate the high battery consumption? By restarting the watch or putting it in battery-saving mode after completing activities (it’s a bit absurd having to restart the watch 5 or 6 times a week…).

What I’ve also noticed is that the problem seems much more severe on the Vertical than on my Race S; on the Race S, I barely notice this problem or the phantom vibrations…

duffman19

@jjpaz Interesting that you see it more on the Vertical and not the Race S. I have a V1 and 9PP and have observed high drain on both. Perhaps it’s model specific since the V1 and 9PP are more closely related than the Race family?

2b2bff

Today I have to join the “my watch didn’t track my sleep” club. Interestingly it stopped recording HR and resources shortly after I set DND mode yesterday evening and resumed recording after I took it off for a shower in the morning. No sleep tracking, no resources, no heart rate. Very strange this.
About an hour ago I looked at the watch from the side and saw green and red light coming from the HR sensor. But it should only record ox during night?

gone troppo

My watch only has one sensor connected and has only ever had one sensor Connected which is polar h10. I don’t know what is causing the battery drain but it started a long while back. Interestingly when I do a soft reset and then select an activity my heart rate sensor is still there paired I never have to re pair it ? I thought this was a bit suspicious. I have had the vertical since it was released my settings are always the same since the beginning very conservative.

No notification
No pulse ox
24 hour heart rate tracking on
Sleep tracking on
Backlight to lowest setting
No raise to wake or anything like that
I try to keep all settings as conservative as possible.

When I bought the watch it would go almost 4 weeks from 80% to 20% with around 12 hours activity a week both indoor and outdoor.

Kraisun Tunta

As a concrete case, last night I charged the watch to “100%” at 21:00 and wore it during sleep as usual. By morning, the battery had dropped to 95%, representing a 5% overnight drain. Under identical conditions, the normal overnight consumption is typically around 1%.

This deviation strongly suggests that the battery was not truly at a full state of charge when the system reported 100%. A more realistic estimation is that the actual battery voltage was likely closer to 96%, while the software prematurely capped and displayed it as 100%.

This reinforces the hypothesis that the current SOC algorithm is overestimating charge level due to calibration thresholds or coulomb counter drift, resulting in a misleading full-charge indication and an abnormal discharge pattern immediately after.

In practical terms, the system is reporting “logical 100%”
but the battery is operating at “electrical 96%”.

This mismatch is not a matter of user perception, but a measurable inconsistency between displayed SOC and real battery behavior.

Pavlas

My last day with sleep tracking, notifications, and no activity—3% battery gone. I’m satisfied.

Horizontal_2

@Kraisun-Tunta I really would like to do some electronical engineering with this device.

So all the problems could be related to wrong measurements?

Would it be usefull to charge the watch for a few hours instead of take it off at 100%?

Kraisun Tunta

@Horizontal_2 Keeping a lithium-ion battery at 100% for extended periods increases float voltage stress and high SOC dwell time, which accelerates calendar aging and long-term capacity fade.

Potential benefit of short post-100% charging
Better voltage stabilisation
Improved SOC calibration
Reduced initial phantom drop

Downsides of prolonged charging
Increased electrochemical stress
Faster degradation over time
Reduced overall battery lifespan

Reality check:This is an engineering trade-off, not a defect.

And honestly? Don’t overthink the battery.
All AMOLED-based smartwatches across brands operate within very similar battery degradation envelopes. The differences are marginal, not life-changing.

Obsessing over 1–5% variance is chasing noise, not performance.

Use the watch. Train. Sleep. Enjoy.
Let physics do its job.

Horizontal_2

@Kraisun-Tunta Thanks! This is helpful!

I guess I’m a little bit obsessed with the battery right now. I still think the drain is too high at some points. First I thought it was a hardware defect. Now I think it’s a software defect. Maybe less running with HR-belt will help

Next cycle I’m going to throw the battery status off the watch. Do’nt wanna know till I’m at 20%

GuillaumeA

Since Tuesday, 18/11/2025, I have switched back to Race 2 with the latest software.

In terms of activities, I did: 5 hours of outdoor sports in performance mode (without AOD and with external HR) + 45 minutes indoors without GPS. Starting from a 100% charge.

I am currently at 75% battery (i.e. just under 8% battery/day consumed with these activities). This is better than the Vertical 1, without a doubt. I find the battery life on the Race 2 quite impressive. And for me, it is very close to the specs.

In terms of daily settings: no notifications, 24/7 HR, sleep tracking + VFC, low brightness, turn to wake up.

Fun fact: at night, the Race 2 consumes 1% of battery. The Vertical consumes 3/4%. While the settings are strictly the same, there is one slight difference: the AMOLED is always off when the MIP works once a minute to update the time.

sorinus

@GuillaumeA said in Software Update 2.48.16 (2025 November Rain release):

Fun fact: at night, the Race 2 consumes 1% of battery. The Vertical consumes 3/4%. While the settings are strictly the same, there is one slight difference: the AMOLED is always off when the MIP works once a minute to update the time.

if there is no movemement (at night), the MIP is going quickly in power save mode (black).

Kraisun Tunta

@Horizontal_2 I might say Suunto’s battery calculation and power management could use some… “character development” —
but I enjoy my current unblocked lifestyle

Let’s just put it this way:
If battery management were an Olympic sport, Suunto wouldn’t be last…
but it definitely wouldn’t be giving the gold medal speech either.

duffman19

@Kraisun-Tunta said in Software Update 2.48.16 (2025 November Rain release):

Obsessing over 1–5% variance is chasing noise, not performance.

Use the watch. Train. Sleep. Enjoy.

I appreciate the above discussion on battery tech and completely agree with @Kraisun-Tunta that obsessing over small fluctuations in percentages is meaningless. However, some of us are still experiencing significant battery draws that cannot be explaining by small variations in battery algorithms.

Last night, my 9PP went from 72% to 59% over the course of ~8 hours of sleep. Typically I’ll see a drain of 2-3% overnight. This was not the result of a “false 100%” reading after a charge, but more likely caused by unwarranted background activity.

If bad battery calculations were the cause, then wouldn’t we also see periods of surprising battery stability or non-draining events? I have yet to observe this.