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 4s 5.80 battery drain

Hello,

I know I am not the first one but it looks like all compaints from all users does not get heard about the battery drain.

So, is Garmin actually looking at it and soon have a fix, or nobody care and we'll just have to wait for a lucky fix in a future update?

  • The battery drain issues come up after every release, not only 5.80. It seems to be the process of rolling out a new software that triggers it, and it is not the same for all. That means the fix is also not the same for all. Some will need to modify settings, others will need various types of restarts. most of us have no issues.

  • Not sure to see the relation between an update and a battery drain other than a problem in the update. My phone doesn't lose 3/4 of its battery when there is an update, neither of my laptop or in my partner's fitbit or my old mp3 players at the time.

    And if the fix is some random manipulation and hoping for the best, it hightlights a real problem in garmin knowledge of their products and in what they release.

    If it is apparently a known problem with every update, maybe it should be aknowledged and allowed to be downgraded easily. 

    I understand some updates went wrong, that happens, but i don't understand there is no communication about it and potential fix.

  • You will see a pattern on the forum. After every release there is a bunch of random watch owners complaining that the watch was okay before, but that there now is a significant battery drain issue. Some of them get it sorted, and then it gets rather quiet until next release, when it happens again. Seems like some watches get into various failure states during the upgrade process. It does not seem to be related to the actual software content that is released.

  • Hi,

    My battery was also draining more quickly after the update to 5.8. I was needing to charge every day and I don't use the back-light or Pulse OX. I think I may have partially solved the issue though. I looked through all menus and found in the 'sensors' menu my Senseiser wireless headphones showing as a sensor. It looked like my V4 was constantly scanning for this 'sensor'. I removed the headphones from the sensors section and now in 48 hours the battery has gone from 77% to 20% which is more like what I had before. I will charge again soon and see how long a full charge will last.

  • I'm having the same problem after a system update toward the end of June. I'm currently running 5.80, tried the factory reset, turned off all notifications from my cell phone and I still go from 100% to 30% over the course of a work day when I used to never fall below 60% in a 24 hour period even with 1000 text alerts a day.

    I've tried searching every menu - sensors, music, etc. to turn off everything possible and no improvement. 

    HELP because this is a MAJOR problem - I loved everything about my 4S until 4 weeks ago and now I hate that I can't do anything with it I used to. 

  • I wonder if you are having the same issue I was. I couldn't use any custom watch face from the Connect IQ store. Stock faces were fine and my battery life returned to normal.

    I really liked my watch face so I rolled back the update to 5.7 which was the last working update for me. I have to occasionally go through and delete the update file though as there is no way to stop the update.

    I have notifications and pulse OX when I sleep on and I usually get about 5 days of battery life I got updated to 5.8 and I couldn't keep my watch alive for 24 hours. I did a lot of testing and found it connected to my watch face I downloaded draining the battery. I tried SO many watch faces and they all did the same only the stock ones returned it to its usual 5 days of life on update 5.8. I contacted Garmin about it and they told me it was watch specific and wanted me to send my device in and receive a refurbished one.

    I have taken very good care of my watch so I didn't want to trade a perfectly fine watch for a refurbished watch. I just rolled the update back. I do have the 5.7 file for Vivoactive 4 saved on my computer. I am going to be keeping the last working update backed up on my computer from now on knowing these issues can arise.

    I am sure I can find some way to get that download for you if you want to try it as Garmin's downloads don't go back that far anymore.

  • I am sure I can find some way to get that download for you if you want to try it as Garmin's downloads don't go back that far anymore.

    can you please tell the process how you downgrade the watch and are you able to retain the settings? I've files of Betas I've downloaded and was thinking about returning to 6.05 since I didn't have issues with frozen activity like on 6.10 but I was reluctant to try it out.

  • Right now they only have two files up. The beta 6.05 and the official release before 5.8. Once they start working on new updates these files will be gone.

    You go to the updates for vivoactive 4 on garmin website, download the zip file, and then put the gupdate file in your garmin folder on your watch when you connect to computer. (Instructions are on the page at the bottom) there is the file gupdate 580 in the zip and that is the last release before their beta version. If you want to go back to 5.80 then you would need to change the name of the file taking off the 580 so it reads gupdate and then following directions for the beta.

    Sadly going back resets settings on the watch like GPS, backlight and a few other things. I don't have my watch set up too different so it is an easy fix for me if I need to go back again.

    When an update happens and your watch tells you there is an update just say no and sometime before you go to sleep plug the watch in and delete the update file. That way you don't get surprised with it being updated when you wake up and the problems being back.

    Good luck.

  • Thanks for sharing this! I As I wasn't sure whenever those files are sufficient for the downgrade and if the process of downgrading is any different from the upgrading. Because I keep seeing people telling that they want to roll-back to older version of the firmware and I thought that possibly there are some caveats for that.

    I'll probably give it a try if I'll catch another freeze on the current firmware