High wakelock count causing battery drain
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
I used BetteryBatteryStats and found that com.google.android.gms is waking the device a lot
To Reproduce
Flashed Havoc OS (A11) on Redmi Note 10 Pro
Flashed microg 0.2.24.214816 as system app through TWRP (system-MinMicroG-standard-2.11.1.zip)
All microg self-check on
No accounts added
Cloud messaging on
Safety net on
Apple wifi location backend enabled
Install betterbatterystats to check battery drain
Expected behavior
Under alarms section in Betterbatterystats, shows com.google.android.gms having 18.7 wakelocks per hour. Mostly being org.microg.gms.mcs.RECONNECT and org.microg.gms.mcs.HEARTBEAT
System
Android Version: 11
Custom ROM: Havoc 4.16
Screenshots
logcat-2022-06-11_114022922.txt
BetterBatteryStats-2022-06-11_121451177.txt
Even clean flashed it again and did the same setup but still it persists.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached logcat and BetterBatteryStats reports, focusing on the org.microg.gms.mcs.RECONNECT and org.microg.gms.mcs.HEARTBEAT wakelocks. Compare the reported alarm frequency with the documented Android 11, Havoc OS, and microG setup; done means identifying the cause of the repeated wakelocks and confirming that the excess battery drain is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- mobile-dev, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100