Post your stats from BBS into the thread. Follow the suggested cycle from the OP, and make a post, people are very helpful there.@DB126 My battery life has taken a moderate toll recently. For context, it is a 5000 mAh device, runs Android 10 with LineageOS 17.1, does not have any Google services or applications yet it went from 2-3 days with heavy use, to 13-14 hours at best, and takes forever to charge.
I know this thread might be outdated and many recommendations do not apply anymore. Do you happen to know whether there's new tricks or threads that I can dive into? Got BetterBatteryStats installed and running thus far, but don't know where to go from here, given the newer Android version, different set-up, and it has been a few years since I last had to go through wakelocks or logs to narrow down what may be causing issues with my device's battery. Appreciate your input!
Sounds like you have an older device with a tired battery. Everything has a lifespan. Replace the battery, replace the device or tether to a portable power source.@DB126 My battery life has taken a moderate toll recently. For context, it is a 5000 mAh device, runs Android 10 with LineageOS 17.1, does not have any Google services or applications yet it went from 2-3 days with heavy use, to 13-14 hours at best, and takes forever to charge.
I know this thread might be outdated and many recommendations do not apply anymore. Do you happen to know whether there's new tricks or threads that I can dive into? Got BetterBatteryStats installed and running thus far, but don't know where to go from here, given the newer Android version, different set-up, and it has been a few years since I last had to go through wakelocks or logs to narrow down what may be causing issues with my device's battery. Appreciate your input!
I think that it has something to do withAny inputs on what is *gms_scheduler*:internal, does limiting it cause any problem? I couldn't find much information on it.
Also, old GMS use to have *net_scheduler* - are these the same, just a new name?
GcmNetworkManager
, which schedules network-oriented tasks, so that Google Play services is able to batch network operations across the system.Are you sure?I think that it has something to do withGcmNetworkManager
, which schedules network-oriented tasks, so that Google Play services is able to batch network operations across the system.
You were supposed to take my post with a grain of salt.Are you sure?
I was thinking of using Amplify and limiting its wakelock.. maybe somewhere 10800ms. I don't know what would break, so I thought I'll check with someone who must have tinkered with it.
I know but thanks for showing me the right door. Appreciate it.You were supposed to take my post with a grain of salt.
-- You can explore further from this write-up.
ALARM_WAKEUP[0-9]+
CONTEXT_MANAGER_ALARM_WAKEUP_[0-9]{3,}