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 4 (all versions) SW 5.10

This update can be downloaded with Garmin Express or automatically with Garmin Connect Mobile. 

Change Log

  • Improved sync speed with Garmin Connect Mobile
  • Improved translations
  • Added access to detailed activity information from the Last Sport widgets
  • Various bug fixes for golf and club sensors
  • Increased maximum pool size
  • Improved CIQ Data Field power management and error handling
  • Fixed gesture handling for CIQ watch faces
  • Fixed handling of disabled cards in Garmin Pay
  • Improved NFC stability
  • Added a stopwatch reminder
  • Fixed rowing speed data field
  • Today in the morning (started with 62%) I did a factory reset, and installed 5.10 again. I didn't changed the watchface and 12 hours later I just lost 10%. So it's pretty much a normal battery consumption. I

    As I was thinking about your reply it occurred to me that many of us are saying the issue is "overnight" but that really the issue is "while asleep" - I think? Overnight is different for us because we are all over the world. I also recall seeing posts that say the watch can't detect sleep very well. So my latest question - could this be related to when we tell the watch we are sleeping in the settings? If we don't tell the watch we ever sleep will we never have the large drain?

  • Just got an email back from Garmin's servicedesk. They expect a software update within a month including a fix for this issue. Probably it's just a kind of a standard answer, but let's give them the benefit of the doubt.

  • Weirdly enough I also sent a support ticket (with the link)  to raise awareness and they also told me they're just replacing the watch. Found that response quite interesting. They said it's good for 30 days, so we will see what happens over the month of October?

  • On the one hand, getting issued a replacement isn't such a bad prospect for a frustrated customer... and perhaps it'll provide a better incentive for Garmin to improve software testing since it has a large financial impact. However, the more likely outcome is that these replacements are factored into the unit price already, and this over inflated unit price is a burden on every customer, and it seems like it could just be a perpetual cycle. 

  • 24 hours later the battery has 43% left, so 24 hours cost around 19%. So i don't have a battery draining issues during sleep so far. I have set the sleeping time between 1 AM and 7 AM.

    4 hours ago I have changed the watchface to another "default" garmin watchface and now it is still 43%. Let's wait for another 24 hours. By my estimate, it will be around 20% tomorrow morning.

  • Yesterday I had a drainage of 30% for the night. At around 10 in the morning I changed the watch face to the default and since then I have a drainage of 0,6% per hour with one running activity and in my opinion this is the root cause. I haven't done restarts or factory resets.

  • In the morning I still got 28% left, so this all looks good. I have added a battery widget and about 12 hours later I still have 21% over. I'm going to charge it back to 100%, change the watchface to non-default watchface and see what's going to happen. Probably the batterypercentage will go down fast.

  • This is the correct answer. I tried the same and with a default watch face I only lost 5% at night vs 30+ with one from ciq

  • Hmm it's now 14 hours ago since I have charged the watch and changed the watchface... 3 hours ago it was still 100% and now it's 95%....

  • I've only used Connect IQ watch faces and I have normal battery consumption. 

    It depends on the watch face, how the developer has coded it, and whether its been updated with the latest SDK or bug fixed for possible battery drain issues. 

    Perhaps if you named the watch faces you are having issues with, then you could potentially be helping others constructively by having them avoid it. Also, has anyone contacted the developers for said watch faces and reported the issues?

    The watch faces I use on 5.1 that are no different in battery consumption over 5.0...

    Racing - Anti-Aliasing
    Rails