FENIX 6X Pro battery Drain - Firmware 27.00

Hi,

 I've a Fenix 6X Pro since june 2021 with no problems ...

 Last week my battery start to drain very fast, my watch stop in less than 8 hours !

 So i start a little investigation:

  • Changed my Fenix 6X battery: Done and it'is not better Disappointed
  • Search for an overheating component with thermal camera: Done, i found a hot point near a screw at 30°c ???
  • Do a full hard-reset back and start/stop button at power-up
  • Rolled back from 27.00 Firmware to 26.00, and then updated to 26.79: That's not better Disappointed

 Now i'm very angry against GARMIN, a premium watch at 700€ for only 3 years !!! O_o

My conclusion I think it's time to buy COROS :(

  • Update:

     I've done that tips from user named :

    • The battery gauge is decalibrated. Fully charge the watch and leave it plugged in for an hour more, after it shows 100%. Then disconnect, sync, and perform the reset (hold the Light button for up to 30s till the watch shuts down, keep holding the button through the emergency notification if any comes). No worry - no data, and no settings get lost, at the reset (unlike at the master reset to factory defaults)! When powered down, wait ~10s, and restart. Use the watch until it fully discharges and shuts down. This process should recalibrate the battery gauge. In some cases you may need to repeat the full charge and full discharge cycle twice, in order to reestablish the calibration.

    What's going on now:

    1. After Reset-Full charge the watch stop from about 1h30 in running mode...
    2. Now the watch won't charge battery and charge data have no sense when i unplug/replug the usb cable... It's a mess !!!!
    3. I've opened the watch and touched the component during charge. The PMIC MAX20303 seems anormaly hot. Inductors are not hot.
    4. My very last try will be the MAX20303 replacement (I work in an electronic lab so i've the tools)
  • Awesome that you work in an electronics lab. I suspect the Max20303 failed in my Fenix 5 Plus, it had gotten awfully hot while charging and never started up again. I also found a capacitor that had turned to something looking like powder. So watch out for things like that too, but I suppose you'll check all the components visually anyway.

  • Update 2:

    • I've finally replaced the PMIC: MAX20303B. Unsoldering/Soldering the MAX20303B wasn't to hard, but there was a resistor or capacitor that i can't view with my eyes tha has mooved with the hot air flow. I only see that component under a binocular (magnifying glass). I've finaly all resolded at their own places... And tadaaa my watch reboot !! Slight smile
    • BUT the battery drain continue....
    • And finally i found the guilty component with a thermal camera.... It was .... my pressure sensor. The contact with the pressure sensor is done with 2 PCB in contact and i don't know how but there was copper oxide between this two pcb's... And copper oxide is conductive... So i've cleaned the PCB's

    What's going on now:

    • PRO:
      • Battery drain seems to be an old nightmare Slight smile
    • CON:
      • My pressure sensor is out of order Disappointed

    MEA CULPA:

    •  I was wrong when i suspected the latest Garmin firmware. It was just coincidence ...
  • First you are a fair guy. You also write about things where you were wrong.

    On the other hand having seen how you solved your puzzle, you would obviously have figured out  what exactly the problem of my Enduro was

    a) if it was not firmware related

    b) there was a strange fluctuation of altitude

    c) but the extent of its unreal volatility was too small (just 15-30 m on both sides)  to declare a completely dead pressure sensor (barometer) an/or internal thermometer

    d) none of the cleaning processes helped.

    I wrote the whole thing in conditional, because in the meantime my Enduro became stone dead, but the problem itself is still interesting for me. What the *** could modify the measurement of the barometer, but always in a range of only 2-4 mbar

  • Thank you for the update, this is very interesting and good to know for everyone.

  • Tried the hard reset, fixed my problem.

  • Tried the hard reset and it completely fixed my problem in 2025.