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

Huge battery drain with v2.27

Something has happened that is causing heavy battery drain, especially overnight.  For the last few days, I have changed the configuration, charged the watch during the day, and by the next morning have been down to about 60% battery, having used 40% in less than a day.

A few things I've discovered:

If you enable incident detection, that seems to turn on the GPS and seems to cause battery drain.  I noticed I was getting GPS tracks in my activities without having turned on GPS for the activity. 

If you connect an external sensor, like a chest strap, it seems to be active all the time, not just during activities.  I noticed it was constantly 'searching' for the chest strap.  Is this a feature or a bug?  Is there a configuration setting for this somewhere?  My Vivoactive 3 only looks for the sensor when you start an activity.  This behavior seems sensible and should at least be an option.

Occasionally I swipe left to right, and instead of "Waiting for GPS", I get an instant position, indicating that the GPS was already on.  Am I swiping in my sleep?  Can this swipe for GPS feature be turned off?  I noticed this same behavior when Incident Detection was enabled. What else could be turning the GPS on?

At first, each of these changes seemed to have significantly reduced the battery drain, yet I had the same result this morning, 59% remaining. Something had sucked up more than 20% overnight.

  • Update:

    I hadn't realized that the swipe left to the right thing is the "Shortcut", so setting that to anything but "Save Location" avoids accidentally turning on GPS.

    I did a user settings factory reset roughly mid-day, and that didn't seem to have much of an effect. The battery was down to below 30% by evening.

    Before bed, I charged it back to 100%, changed the watch face (to Quatro from Glance), and rebooted the device.

    This morning, I woke up with the watch at 97% and it's still at 97% a couple of hours later, so for now, problem solved, and we know this isn't an inherent problem with the device.

    The two significant changes were the watch face and reboot I suspect the rebooting terminated a rogue process or something because there were certainly periods of good battery life with the other watch face.

    I'll validate if changing the watch face significantly affects the battery life, but if so, that would just be a defect with that watch face.

    In the future, when I see odd behavior, I'll remember to try rebooting the device.