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

Vivoactive 3 battery drain s/w 6.60 problem

Former Member
Former Member

Hello,After the 6.60 software update my vivoactive 3 battery, discharged  quickly and the watch turned off for less than 12 hours.

Garmin how to corrige that ?

  • Are the people that are having trouble powering-down the watch some of the day?  There was an issue early-on with this watch where the battery would drain quickly when the watch was OFF.  This was addressed in a firmware update.  Perhaps this problem has come back.

  • I leave my watch on 24/7 with an occasional power reset to keep it fresh. 

  • I did what you have suggested. Reset the watch twice without setting it up or connect to phone to ensure it is starting afresh. However, firmware 6.60 still stay there, it never get revert back to older firmware. I also uninstall the Garmin Connect app on my phone, removed all watch faces, widget and data field app. Restart my phone and download the Garmin Connect app from App Store, setting up the watch as if it is a new watch. But despite all these, battery drain still remain the same. My watch is 1.5 years old, warranty already out. 

    It was perfectly alright before firmware 6.60 update. So this happened right after the update, am I wrong to blame Garmin for screwing this up???

  • Former Member
    0 Former Member over 5 years ago

    I alsos get this problem, write to garmin. 

  • my v3 is also that old, so you saying you unable to revert back to original firmware? The only other thing i can think of is to try downgrade and also my old trick, simply master reset the watch over and over, like 20 times and hope it will go away. I did that with my Fenix3hr before quite a few times and it eventually work. But hey if you tried everything and still no luck, i guess Garmin *** up. In that case you will have to wait for next update and hope it will fix it. 

  • i understand but you should realised that all these people reporting this issues are actually tiny minority. Read what i wrote as an answer regarding your options like downgrade, repeated master reset, etc. Or you can just wait and wing it till new firmware hopefully fix this.

  • Agreed.   My wife has a VA3 without any issues.  Same firmware, but her watch is 6 months newer than mine.   My guess is that my battery is shot and that it's not a firmware issue.   Backing up my hypothesis is the fact that every day for the past month, my watch battery lasts less and less.   It started going from 5 days to 3.  Then to 2.  Then last week down to 1.  Now I'm down to about 12 hours to go from 100% to 0%.   In my mind, there's no way that this is firmware related now.  Everything, at least in my case, points to the battery.

  • Yes, I have tried 3 times reset altogether but still unable to roll back to older firmware. In past few days, I tried troubleshooting the problem myself. First I let the watch battery completely drained and charged it back to 100% overnight. It didn't help. Then I turned off the auto backlight, didn't help too. I turned off bluetooth connection and cut off all notification, same battery drain problem. Then I went a step further turned off heart rate tracking, still same battery drain. Tonight after I fully charge it, I will turn off activity tracking so the watch is basically like a dumb watch, just showing time only. Will see if the battery still drain. 

    Good news is after i double check, my watch has 2 years warranty. So regardless of my trouble shooting outcome, I'm going to send it to warranty after this. I pray I can get a new watch or any refurbished one other than this watch!

  • Hallo zusammen, 

    Ich habe das gleiche Problem. Am Nachmittag den Garmin Service angerufen, 5 Minuten später hab ich eine Mail mit RMA Nummer erhalten. Die Vivoactiv wird ausgetauscht. Ist bereits bei der Post. Die Uhr ist von Mai 2018.

    Das war ein sehr nettes Gespräch, was will man mehr.

    Super Service 

  • Yep. That problem is still there on mine. 
    Had it about a year ago when I bought it new.
    Still have it on 6.60 today. Nothing fixed/changed