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

25-50% of time phone awake

I use Sony Z3 compact Marshmallow 6.0.1 stock with root (debloated, but almost no other mods). VA3 and Vivoki are connected to Garmin mobile connect.
And I have quite high battery drain due that phone is 25-50% awake due to Android OS. Going deeper it shows bluetooth wakelocks (BTLowPower + msm_serial_hs_dma). If I remove garmin mobile all is back to normal. Sometimes phones does not go to deep sleep at all. After restart it goes back to 25-50% time with wakelock.
Tried to roll back to Kitekat, but than I had 50-75%% at least of same wakelock. Tried also Lolipop and too 50% wakelock. Marshmallow is best, but still too much of wakelocks.
The battery graph shows that Bluetooth is waking up the phone every ~30-60 seconds. Also strange that the Bluetooth is waking the phone, but connection with watch is missing. Sometimes for example I go far away from the phone - the watch disconnects from phone, I come back and stay few hours close by phone but watch does not connect back. But Bluetooth is still waking up the phone every 30-60 seconds...
Had a Microsoft band 2, so it would connect disconnect to watch without Bluetooth waking up the phone from deep sleep. And no additional wakelocks with band and app working in background.

Does everybody have same wakelocks? Was thinking may be to change phone to Sony XZ1 Compact with Oreo. may be Oreo has solved the issue? Anybody with Oreo, how are wakelocks?
  • Hi!

    I've the exact same issues with the exact same phone, with exact same stock android. See my findings here: https://forums.garmin.com/forum/into-sports/garmin-connect-mobile-application/garmin-connect-mobile-android/1276884-excessive-amount-ot-bluetooth-wakelocks

    Don't forget to submit a ticket on Garmin's support, I've already did and tell them what you're experiencing.

    What I also found out just yesterday is that if I revoke the Location permission from Garmin connect the wakelocks fall back to a much more bearable level. This is because Garmin developers are calling the BluetoothLeScanner.startScan() function which needs the Location permission from Marshmallow as explaned here:https://developer.android.com/about/versions/marshmallow/android-6.0-changes.html#behavior-hardware-id

    To me it seems the developers don't have a clue on what they're doing with bluetooth.
  • I have tried revoking location permissions, but all sync has broke. But on the other hand VA3 was syncing with location turned off. Vivoki was not syncing most of the time with location off. Though may be 1 or 2 times it could have synced with off location. But it might be that it already had established connection from before when location was on.
    Yesterday, just to test, I have removed Vivoki from garmin connect mobile. Now only VA3 is left connected and syncing. For at least 6 last hours the are no more bluetooth wakelocks.
    Will come back later after few days to report if wakelocks have returned or not.
  • So after few days removing Vivoki tracker from Garmin connect mobile there are no more wakelocks. It looks, for me it was a problem of Vivoki tracker and garmin connect mobile.. So now I had it connected to another phone, where I can turn of bluetooth not to have excess wakelocks.
    Could be nice if Garmin could solve issue with garmin connect and Vivoki tracker to be able to use both trackers on same phone...