This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Firmware 9.17 — Battery Drain

New Firmware, Old Problem

My watch was working normally for a month and a half then without warning or changes to settings it started draining at about 4% an hour.

I added the beta firmware (9.14) and did a full factory reset and it was ok again—for two weeks. Starting 10 May it was again draining faster than normal (though slower than before, at about 2% hr). ***BTW, both drain amounts (the 4% and 2%) were notwithstanding if I was using GPS or Ox or not. It's just a standard 4 or 2%.

Last night, I was about to do another reset when I noticed that there was a new firmware ready (9.17) so I installed that and did a power cycle. Over night I tested to see if that solved the problem. It did not.

So this morning I did a full factory reset as that worked last time. But no. Still 2% drain per hour.

Top Replies

All Replies

0 9033313 over 1 year ago in reply to Garmin-Kevin

I have the same issue.

1. Yes

2. Yes

3. Malaysia

4. I am on 8.15, try updating but the watch says no update available

5. No

0 3740688 over 1 year ago in reply to 6961267

I recommend you use a face watch that only shows time and date. This is how it normalized The drain battery

0 Ryan's Tech over 1 year ago

For those having this problem, if before this update you weren't using any other device with the Physio TrueUp enabled, on your watch go to the system settings and make sure the Physio TrueUp is disabled. After the update my Physio TrueUp was enabled and I disabled it and it fixed the issue for me and hopefully it'll help you too. Also if you don't use the pulse oximetry normally, then go turn it on and off again just in case.

0 Garmin-Kevin over 1 year ago in reply to 9033313

9033313 due to your location, you will need to reach out to your local Garmin Malaysia Support:

https://support.garmin.com/en-MY/?productID=730659&tab=topics&topicTag=region_batterytips

Product Support

Toll Free 1-800-81-6357

Tacx Support

Monday-Friday 9 a.m.-5 p.m. Closed on weekends and national holidays.

0 Bas_W over 1 year ago

Garmin-Kevin

Hello Kevin,

Is there already something known about the source of this problem and how to prevent it?

I tried the suggestions mentioned here, but they did not help. Something I noticed was that when I charge it with my laptop, it sometimes does function normally for a few hours until it doesn't anymore. then the watch gets slower and drains the battery quickly.

I would like to get this problem under control, so if a solution is known I would like to be informed. Otherwise, I wish to downgrade to the previous software version.
next to the inconvenience of not being able to rely on my watch, I also don't think its good to have a battery that's designed to be charged once a week to be charged once or twice a day.

With kind regards,

Bas Woudstra

0 af-toronto over 1 year ago

Garmin-Kevin

The problem is back.

The watch has been good since 13 May.

During a three week trip to Spain where I used the GPS almost daily for 6-8 hours it was fine as well.

I got back last Friday, charged in Toronto for the first time on Monday, and since then it's been on high drain again.

Has a solution been found?!?!

0 MirceaForce over 1 year ago in reply to af-toronto

I found a solution go to Bluetooth settings on your phone (mine is android) venu 2 plus (name may differ) and uncheck calling feature

0 af-toronto over 1 year ago in reply to MirceaForce

Thanks for this. I don't know exactly how to do what you suggest, but in trying I realized that my watch (while present in the list of bluetooth items) wasn't pairing. So I unpaired, and reconnected. Fingers crossed that will work.

I think this may be it, as I used a diff sim card while in spain and only reconnected my Toronto line on Monday (the same day my batt started to drain again)... I'll update if it works or not.

0 MirceaForce over 1 year ago in reply to af-toronto

for me it worked

0 af-toronto over 1 year ago in reply to MirceaForce

Disconnecting and reconnecting to bluetooth seems to have done it. Thanks for the tip.