Since last week I am seeing substantial battery drain on my Xperia M2 and the power management 'app' says that it is almost all (82%) due to bluetooth.It does not say what is requesting the bluetooth. I cannot yet identify the cause, so cannot say that GC is causing it but GC Mobile Android looks like it got updated last week and is my heaviest user of BlueTooth (to my Fenix 3 and VSHR) - is anyone else suffering from serious battery drain since about the end of January?
Just had bluetooth lock on / wakelock and at the same time it killed the watch overnight as well; the phone got hot enough from the lockup that it suppressed charging (!) and I woke up with it at 50% -- despite being on my Qi stand....
Current rev on Connect (3.3.2); not sure if the app or the watch was the root cause, but this has been reported by others on the Fenix 3 forum....
@tickerguy, Can you check your download queue on https://connect.garmin.com - are there any software updates in the queue? I'm attaching a screen shot for reference.
Thanks for the update. The reason I ask is because a wake-lock is held during syncing (upload and download). Software updates are included, and for the Fenix 3, those can be quite large in size. I've mentioned this thread to a colleague that works in the bluetooth layer of the app.
I rebooted the phone last night for unrelated reasons.
This morning, when it came off charge, it was behaving normally with a wakelock NOT being held (only awake when actually in use.) After breakfast I opened Connect so the phone would sync last night's sleep data.
From that point forward the wakelock was held and even force-closing the app did not clear it -- Connect immediately restarts when you do that.
Rebooting the phone clears the wakelock even though Connect auto-starts as expected (and re-connects to the Fenix 3) until you once again actually open the App. Then you're screwed once again and the wakelock is again held permanently, even if you back all the way out of the app, use the built-in manager to close it, or even go to the app in the settings and force-close it.
It appears that once Connect is actually opened for user interaction it never releases the wakelock it holds on the device. This is very bad as it at least triples idle power consumption from the Wakelock alone and in this case it's worse because it also locks Bluetooth open and thus I wind up with a very high standby battery drain attributable to Bluetooth as well. If I shut off Bluetooth on the phone then the wakelock and power consumption ceases, but as soon as it's re-enabled the wakelock comes back.
In short it appears that Connect is not releasing the Bluetooth channel when it is done with it (and thus the wakelock is held), even when it is force-closed, if it is started just ONCE to look at something or cause a sync to take place.
My device is a BlackBerry Priv running Android 5.1.1.
