Battery drain after update 2.44.46 (2025 Q3) on Vertical Watch

OutdoorMan

@MeazzaS9 ok, you stated it as fact so I was curious. I am not sure if I share your optimism though, but let’s see…

uvrays

Former long-time Garmin user – I switched to Suunto at the end of last year because Garmin put me off with a lot of messed up updates and among other things the resulting high battery consumption.
And now the same thing is happening with my Suunto Vertical Solar, which I switched to because of its high power efficiency…

As I’m new to the Suunto universe, can someone explain to me if and how I can roll back to the firmware without high battery consumption? Where can I get the firmware (I can only see the last two firmware versions in the watch – and the second to last one is already faulty) and how can I downgrade the firmware of the SV?
Thanks for advice!

Dimitrios Kanellopoulos

I’m reading through this issue, but I’m not entirely sure I agree with what’s being said here.

Since not everyone is experiencing battery drain, how can we say the drain is deliberate?

I’m raising this issue, but let’s keep things in perspective — it’s not that Suunto wants to drain the battery faster. The Vertical 1 is Suunto’s flagship model for MIPS.

Could you please check whether the battery drain remains the same if you unpair your sensors (under Connectivity)? This was one of the main low-level changes in the latest update, so it would help narrow things down.

Thank you for taking the time to write here and report your findings — it’s appreciated!

uvrays

@Dimitrios-Kanellopoulos Thanks for your reply.
I have just fully charged the SV and will now log the battery consumption again over the next few weeks with the current firmware. I can then compare these figures with the consumption logged at the beginning of this year (during the evaluation of the SV in comparison to the Fenix) – then I will have clear facts instead of vague feelings.
PS: I do of course not believe that these issues are deliberate! Watch software is apparently very sensitive to poor code or hidden bugs in terms of energy efficiency.

halajos

@Dimitrios-Kanellopoulos I’ve experienced random restarts with my Race v1 every few hours on 2.44.52, which were gone when I reverted to 2.44.46 (hard reset didn’t help on 2.44.52). May the restarts and increased battery drain related? I assume the watch draws more current during startup. Could someone who has battery drain issue check for an error code in the debug menu (mine showed an error code)?

kurtpenter

@Dimitrios-Kanellopoulos unfortunately yes, power drain is a thing even if I unpaired sensors and disabled Bluetooth visibility.

Something bad happened with the last 2 firmware updates on my SV1 (Finland): footpod does not work, battery drain, and dismissing notifications takes seconds. First time I complain about a FW update in years. First time I reach 4% battery.

I really hope a fix comes out soon and I’m starting to think to go back to previous FWs.

gone troppo

@Dimitrios-Kanellopoulos said in Battery drain after update 2.44.46 (2025 Q3) on Vertical Watch:

I’m reading through this issue, but I’m not entirely sure I agree with what’s being said here.

Since not everyone is experiencing battery drain, how can we say the drain is deliberate?

I’m raising this issue, but let’s keep things in perspective — it’s not that Suunto wants to drain the battery faster. The Vertical 1 is Suunto’s flagship model for MIPS.

Could you please check whether the battery drain remains the same if you unpair your sensors (under Connectivity)? This was one of the main low-level changes in the latest update, so it would help narrow things down.

Thank you for taking the time to write here and report your findings — it’s appreciated!

Hi

Yes I have tried this and it did not work, I literally tried every single “fix” that was suggested on these forums and various fb groups on mine none have worked. I’m not someone who just complains for no reason if you look at my historical posts I was singing praises for the suunto vertical more than anyone when it first come out on here when it worked properly. The solar stopped working which I can live with but the battery drain is a fundamental failure of this watch. I sent my watch to suunto repair cost me $50 who said there is nothing wrong with the battery or hardware and they claim it is only draining 4% per 24 hours!!! Yet I have approx 6 week worth of notes every morning I would record battery level when I wake up. I would get anywhere from 12-40% drain every 24 hours it gets worse as the battery gets lower below 50%. So either I’m lying or the suunto repair shop is lying???

To all the others this battery drain has been happening well before the last two firmware updates so rolling back to the last firmware won’t help you. This is something suunto must fix. Currently I’m using my old reliable ambit 3 peak which goes through maybe 2-3% battery a day and puts the vertical to shame how embarrassing. 2014 technology smashing the current stuff

OutdoorMan

@Dimitrios-Kanellopoulos I think we should keep in mind that this is also affecting other watches, not only V1. I have a new R2, went through multiple cycles already, tried everything and loosing around 10-20% per day without activities, just in watch mode. There are also many posts on other forums about it.

Elipsus

@gone-troppo Yup, same is happening on my 9PP, also roughly at 12% per day

Stefan Kersting

@Dimitrios-Kanellopoulos I have paired a stryd sensor that i can not unpair. As you see on the picture below I have paired the sensor several times and therefore you see the connections that actually do not show anyting.
Additionally the watch often does a beep sound without showing anything on the watch. Usually when activated an alarm you see that is sun rise or sun set, done that many steps and so on. But the watch just beeps and doesnt show anything. I can not see a pattern either.
Since the update I have to charge the watch once a week, usually on sundays and it seems that the training amount with GPS activities does not affect the this rythm. Skiing season has not starte yet but when training 20 hours a week I maybe have to charge more than once a week.

fedequei

@Dimitrios-Kanellopoulos
Thank you for your reply and for taking the time to look into this.
From what I understand, it seems that Suunto hasn’t yet identified the exact cause of the increased battery drain, and that’s a bit concerning.
As we can see, quite a few users are reporting the same issue, which appears to have started after the last two firmware updates.
In my case, I started noticing the faster battery drain since June, and I can confirm this with all my recorded charging cycles.
I also tried the suggested solutions, including unpairing all Bluetooth devices, but unfortunately it didn’t make any difference.
I really hope this can be investigated further and that a solution can be found as soon as possible.
Thanks again for your time and support.

Dimitrios Kanellopoulos

Alright. Time for logs

Press send logs via the Suunto app and send me a message here with the email used for the Suunto app account. Try to send the logs at a relevant time if this is applicable.

Kramble

@Dimitrios-Kanellopoulos said in Battery drain after update 2.44.46 (2025 Q3) on Vertical Watch:

Alright. Time for logs

Press send logs via the Suunto app and send me a message here with the email used for the Suunto app account. Try to send the logs at a relevant time if this is applicable.

Do you need some test without the mobile app connection?
Because I don’t use any Bluetooth gear but I do have battery drain and I just have my mobile connected with Bluetooth.

maszop

Suunto Vertical 1:
Yesterday morning battery level was at 10%. I plugged it in, and the charging message/symbol appeared. After about half an hour, I checked, and of course, that crappy charger had failed again. Still at 10%. I plugged it in again, and only managed to charge it to 20%.
This morning, the battery level is at 7%.

kurtpenter

@Stefan-Kersting I started this thread for footpod / Stryd issues https://forum.suunto.com/post/176560

maybe you can post your findings there too

I do not see the same issue you have but definitely something broke recently

Dimitrios Kanellopoulos

@Kramble can also be sure keep me posted