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

Is there any solution to the bluetooth wakelocks caused by the Connect app?

I have a Vivosmart 4 and an Instinct connected to my Pixel 4xl (and 3xl before that) using Garmin's Connect app. I enjoy all the connected features and tracking, but as long as the app is installed and set up with a device it prevents my phone from sleeping properly which causes battery drain. I do not see similar drain when using other bluetooth wearables (Android Wear watches, mainly).

I know there are plenty of other mentions of users with similar issues in the past. Has anyone actually fixed it?

hal_bluetooth_lock kept the phone awake for 3+ hours when it could've been sleeping. The uart wakelock is related. The time difference between the 2 is the time that I'm in my car streaming music (when I'd expect the phone to be kept awake by bluetooth).

0 trux over 5 years ago

Just curious what power consumption does your Android show for the GC app? Mine shows 2.5%, which I found not too excessive, since I use it a lot during the day.

Did you try using the option "Put app to sleep" for GC in Android Device Care » Battery? Not sure whether your OS version has that option, though. Also, it could possibly disable sending the phone's notifications to the watch. You could also try disabling the notifications in the GC settings, to see whether it makes any difference, but I guess it is not the solution you are looking for.

0 icantremember over 5 years ago in reply to trux

Yeah, the actual Connect app usage was relatively low for that span. Something like 3%.