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?
This is easily reproducible -- running version 3.4.1.2.
I get a full day's worth of battery without Garmin Connect and need to plug in after 6h of use with Garmin Connect and Bluetooth enabled.
Still, when BT is enabled, the app is much too aggressive in how it keeps BT awake to the point of negatively affecting the phone's overall performance. Nexus 5X in my case.
I work out more than once a day. Obviously a fix would be welcome as this BT on/off dance is cumbersome.
Just got the update to 3.5 this morning and after 8 hours it is still looking good. Also devices seem to connect much quicker - like they did at the start of the year.
Just got the update to 3.5 this morning and after 8 hours it is still looking good. Also devices seem to connect much quicker - like they did at the start of the year.
Finger crossed!
Agreed. So far so good with 3.5.0.1, bluetooth doesn't show up in my battery stats.
Would be nice to see release notes for the Mobile app to confirm that this issue has been addressed.
Agreed. So far so good with 3.5.0.1, bluetooth doesn't show up in my battery stats.
Would be nice to see release notes for the Mobile app to confirm that this issue has been addressed.
After more than a day with the new version and both Connect and BT on the whole time, I am still at 41%, having started at less than 100% yesterday. Connect usage is 7% and BT 6%.
As far as I am concerned the problem is solved.
I posted the release notes for 3.5.0.1 in a separate thread for 3.5: they do not mention this fix. If you go the app page from Google Play you can see the "What's New" list yourself.
:D -- solved until there's a firmware update, then it'll drain again. We're working on changing the code to only send SW updates to Garmin devices when the Android phone/tablet is in charging mode.
:D -- solved until there's a firmware update, then it'll drain again. We're working on changing the code to only send SW updates to Garmin devices when the Android phone/tablet is in charging mode.
Hi Doug -- I'm confused by this message. I thought 3.5 addressed the issue but as soon as I uploaded my next activity from my Edge 510 device, the battery drain started showing up again on my Nexus5X device.
I know that my Edge 510 device is *not* running the latest FW (it's quite a few revisions behind, actually). Would this have something to do with the issue? Are there plans to have the Mobile App do the FW updates (if I'm reading "SW updates to Garmin devices" correctly) ?
@StayFrog, yes, it's possible the app is sending a SW update to the Edge. However, because the Edge 510 is bluetooth classic, not bluetooth low energy, the throughput over classic is MUCH faster, and I wouldn't expect a lot of battery drain. Please update the Edge with http://software.garmin.com/en-US/express.html tool.
Sad to say, but my phone's BT locked up again yesterday and ran through the battery at a rapid rate.
I had no firmware updates in the offing.
Furthermore I am still getting lockups that do not cause high battery drain, and for all these the only way I've found to recover is to power-cycle my phone.
Sadly the bluetooth bug is still present with the just-released version 3.5.1. Yesterday I was using my phone with bluetooth headphones and the transmission stopped. At that point I was unable to switch BT off. I rebooted my phone and the same thing happened 10 mins later. Rebooted again but this time went in and stopped all GC services before switching BT on. Problem did not reoccur, although it cerfainly will after I start GC again.:mad:
