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

Fenix 5X Plus battery draining

My battery has been acting out of character after the ransomware attack. Noticeable battery draining rapidly from full charge to 10% in 2 days. Normally it takes 8 to 9 days with connection to phone and regular workout (running with GPS). I contacted Garmin support team and they said it was nothing to do with the ransomware which only affected online services. 

So I can only imagine it's pure coincidence that this is happening. I love my Fenix 5X plus. Had it for 2 years now with no battery issues until 3 weeks ago. 

After going through a full reset and removing apps from IQ, the draining continued. Garmin Support then quoted $140 to do a full exchange of the watch as it was outside of warranty. I am not ready to spend anymore money than I already had on this watch. Paid close to $1k for this watch and expected it to last longer than two years, so not ready to spend another $140 for what I think is a glitch from Garmin, which is no fault of mine. Is anyone facing the same issue and got it addressed?

I am almost regretting my choice when I was choosing between the Apple Watch and this. I had been with Garmin since 2008, so this does not happen all the time. 

  • Hello, I have the same problem with my Fenix 5 plus battery last two days, I been with Garmin since Fenix 3 but if this problem continue I will switch to Apple Watch

  • Former Member
    0 Former Member over 5 years ago

    I am having the same issue. I have had my 5 plus for 2 weeks now and I went from 100% to zero in 48 hours. I was trying to figure out what might cause it. Im stumped.

  • It's probably the bluetooth that stay connected either to your phone or headphone or external HR monitor. You need to figure out what it is first.

  • Yes it is, yesterday after my run I turn the watch off and then on I today I have 83% . Reading another post there is a workaround that is to downgrade BT to Ant BLE BT 504 this will be my next step

  • Have you guys done a forced power off? It seems many people post to do this after a firmware update or unexpected power events and it resolves their issues.

    Hold the power button for at least 10 second. The watch should switch off. Wait a few seconds then push the power button (it will take a couple of seconds to get the startup triangle). I would then do a standard power off and power on.

    A standard power off is really a standby. The cpu is still running to keep the clock going. When you do a forced power off, the clock stops at that point.

    One thing I have noticed after a forced power off is that the initial GPS lock takes a while. Also make sure to resync the time!

  • how do we downgrade software? the watch syncs once connected with garmin connect

  • yes i disconnected from phone still not helping.

  • Former Member
    0 Former Member over 5 years ago

    For me this occurred after the BLE 6.06 update. The release notes for FW 13.00 mention that the high power mode remains activated and that 13.00 corrects this bug. Seems to work on my 5X Plus

  • I'm using Android File transfer on Mac and follow this instructions:

    Installation Instructions

    1. Download and unzip fenix5PlusSeries_***Beta.zip.
    2. Place the gupdate.gcd file, found in the System_v*** folder, into the \GARMIN folder of the device.
    3. If there is a ANT_BLE_BT_v*** folder, place the gupXXXX.gcd file into the \GARMIN\REMOTESW folder of the device. Please note, not all Beta releases will include an update.
    4. Disconnect from your computer and proceed through the update.
    5. If you would like to revert to the last public release software, drop the gupdate.gcd file found in the System_Backdate_v12.10 folder in the \GARMIN directory.
    6. NOTE: If you revert to an older version of software, all of your settings will be reset to defaults.
  • I think that is not enough to disconnect from the phone since BT keeps on, for me the solution was to power off and then on