Anyone else encountering this? I didn't check before I went to 5.0.1, but right now it is consistent. Rebooting helps for a time, but my phone is awake for the most part even if I'm not using it, and most of that time goes to RILJ, used by the phone app.
I saw some threads about using wakelock terminator, but this doesn't work well on Lollipop because Xposed does not work 100% stably.
NegativeOne said:
Anyone else encountering this? I didn't check before I went to 5.0.1, but right now it is consistent. Rebooting helps for a time, but my phone is awake for the most part even if I'm not using it, and most of that time goes to RILJ, used by the phone app.
I saw some threads about using wakelock terminator, but this doesn't work well on Lollipop because Xposed does not work 100% stably.
Click to expand...
Click to collapse
Yes, I'm seeing RILJ keeping my phone awake too since the 5.0.1 update
NegativeOne said:
Anyone else encountering this? I didn't check before I went to 5.0.1, but right now it is consistent. Rebooting helps for a time, but my phone is awake for the most part even if I'm not using it, and most of that time goes to RILJ, used by the phone app.
I saw some threads about using wakelock terminator, but this doesn't work well on Lollipop because Xposed does not work 100% stably.
Click to expand...
Click to collapse
lexluthor said:
Yes, I'm seeing RILJ keeping my phone awake too since the 5.0.1 update
Click to expand...
Click to collapse
I'm having this annoying wakelock too on 5.0.1 in Nexus 5. Have you found any solutions?
If you turn off location history (and may need to reboot), it goes away, but without location history, Google now isn't as fun.
RILJ seems to have a wakelock about 50% of the time. This is only since 5.0.1. At least it doesn't seem to really be killing battery life much.
I don't use Google Now and I have location services disabled all together most of the time (no GPS, no network location). I only use it when I open Google Maps. I also turned off location history but nothing changes. RILJ is always there. I think this is related to the phone app.
Adrianrff said:
I don't use Google Now and I have location services disabled all together most of the time (no GPS, no network location). I only use it when I open Google Maps. I also turned off location history but nothing changes. RILJ is always there. I think this is related to the phone app.
Click to expand...
Click to collapse
Do you have location history disabled too? I think rilj is the phone looking for location via the network as opposed to via GPS.
lexluthor said:
Do you have location history disabled too? I think rilj is the phone looking for location via the network as opposed to via GPS.
Click to expand...
Click to collapse
You mean this right (see screenshot)? Yes I disabled that hours ago and still have that wakelock (among other wakelocks with high counts like *alarm*, SyncLoopWakeLock and many others). RILJ is the worst one though. It doesn't happen on wifi, only on mobile data.
Adrianrff said:
You mean this right (see screenshot)? Yes I disabled that hours ago and still have that wakelock (among other wakelocks with high counts like *alarm*, SyncLoopWakeLock and many others). RILJ is the worst one though. It doesn't happen on wifi, only on mobile data.
Click to expand...
Click to collapse
Not sure that's the same place. I'm looking in settings->location->Google location history If I turn location history off there and reboot, rijl wakelocks stop.
lexluthor said:
Not sure that's the same place. I'm looking in settings->location->Google location history If I turn location history off there and reboot, rijl wakelocks stop.
Click to expand...
Click to collapse
Yeah, it's the same setting. That has been off since last night, along with Location services all together (I never use Google Now and rarely open Google Maps to see where something is or where I am). I don't think my problem has something to do with location. Thanks for your suggestion., though.
I may have found something here.
In Google Wallet->Settings->Notifications, I've turned off the nearby items option.
I've now only got 21 seconds of RILJ wakelock in the last 44 minutes.
I've had some other periods of time where RILJ stopped and when I turned the feature back on to test, RILJ didn't start up again, so I'm not sure I've found an answer, but, right now, it's looking ok.
Nope. Significant RILJ wakelock is back. Wonder why it wasn't there this morning.
This is definitely a strange one.
That is the same thing I've been seeing. You reboot and it goes away for a while, then comes back.
lexluthor said:
Nope. Significant RILJ wakelock is back. Wonder why it wasn't there this morning.
This is definitely a strange one.
Click to expand...
Click to collapse
I also noticed it's rather insoncistent, but most of the time it's there, going crazy. Nearly 100 instances in a matter of a few minutes. I'm not actually sure of this, but I think it's worse when I'm in a place with bad cell coverage (home and work, for example -FML-). And when I'm at work there's absolutely nothing I can do to stop the wakelocks, because if I connect to that crappy WIFI, the RILJ will go away, but I'll get A LOT of wlan_rx and wlan_wd wakelocks too. When connected to the WIFI at home the phones sleeps like a baby.
NegativeOne said:
That is the same thing I've been seeing. You reboot and it goes away for a while, then comes back.
Click to expand...
Click to collapse
In my case it doesn't. I've read that disabling background location helps (It's always disabled in my case) because it's the phone using cell towers to approximate your location. I don't use nor have Google Wallet. Wakelock detector shows it under "Phone (radio)".
All this ****ing wakelocks are drving me crazy, I'm having all sorts of them. A bunch of sync related wakelocks are always poping out, and I have autosync disabled most of the time. This came with the 5.1 update. I flashed Cynogenmod 12.1 this morning and I haven't seen any changes.
Been doing some more testing and this issue is just really strange. Turning off location history seemed like it was working for a bit, but rilj wakelocks are going just as strong now so that's not it.
Also, there are so few posts about this when i do a Google search that I'm wondering if this is just flat out a bug specific to the G3 that was introduced in 5.0.1.
RILJ is from the phone app. I had it in 4.4.2 too. As soon as I use the phone I get the wakelock.
lexluthor said:
Been doing some more testing and this issue is just really strange. Turning off location history seemed like it was working for a bit, but rilj wakelocks are going just as strong now so that's not it.
Also, there are so few posts about this when i do a Google search that I'm wondering if this is just flat out a bug specific to the G3 that was introduced in 5.0.1.
Click to expand...
Click to collapse
It's not exclusive of the G3, I have them too on the Nexus 5. It's definitely related to the radio (phone), I think it gets worse when you have bad coverage. I managed to stop a bunch of the wakelocks I was having by making a profile in Tasker to turn on autosync every 2 hours for 5 minutes and, more importantly, by denying permissions to Google Services, Calendar (and its sync service), Contacts (and its sync service) for location, wake up and keep awake, among other permissions. I still see the RILJ wakelock but it's not significant and has no impact on battery life. I'm not sure if the permissions thing helps with the RILJ wakelock, but I'm sure that was the only thing that help with battery life.
RILJ Wakelock on HTC Desire 816 after Lollipop Upgrade
I am facing the same issue after upgrading my HTC Desire 816 to Lollipop. RILJ is related to the Dialer.
Tried the following:
1. Clear Cache and Dalvik Cache
2. Force Stop Dialer
3. Restart Phone (Works for some time)
However, after Googling for a while I found out that a restart will help as long as you don't receive a call. As soon as you receive a call, the RILJ process again shoots up and keeps your phone awake.
A restart after every phone call is way too annoying.
Related
I have my phone running 99.6% of the time in spare parts and it shows android system as the culprit holding a partial wakelock.
so my question is, how do i fix this? i've tried a factory reset three times, am updated to 1.21 ota and have slowly started to reintegrate apps but it always starts again and always after a different app.
i'm getting pretty frustrated anyone got any ideas?
UPDATE In my case it was network time abusing wireless location service that was causing the problem and hence the reason a factory reset didnt solve it, i switched off network time and voila!
just to clarify, no live wallpapers, and phone is in airplane mode to avoid any data usage drainig the battery.
i have got beautiful widgets homescreen small clock and pure cal widget installed at the moment but even when i uninstall them it doesnt fix it, also im running launcher pro 0.4.2 but also had the problem when i reverted to sense.
and i have read every other thread here about battery life that i could find but no-one seems to have this problemo
anyone with any advice on why my phone wont sleep?
A long shot, but go in to Mobile Settings and untick Enable always-on mobile data.
Philosoma said:
A long shot, but go in to Mobile Settings and untick Enable always-on mobile data.
Click to expand...
Click to collapse
ok cool, giving that i try now but i had been leaving it in airplane mode to try and take the vagaries of data out of the equation.
this started about a week ago and i really noticed it when i was in a 6 hour long meeting and my battery basically draines 60% even though the phone was in airplane mode
ok tried that but with my phone just factory reset, airplane mode and no apps installed other than spare parts it's showing running 94.1 % of the time and all of it is android system.
that cant be right
i have restored data, maybe i shouldnt restore data either but that just seems plain crazy
Re: Android system - partial wake lock
What exact foreground and background processes/services do you have running when this is happening, any idea?
Apps like System Panel can show you them and some useful other details. That is certainly too high.
-------------------------------------
- Sent via my HTC Desire -
th3 said:
What exact foreground and background processes/services do you have running when this is happening, any idea?
Apps like System Panel can show you them and some useful other details. That is certainly too high.
-------------------------------------
- Sent via my HTC Desire -
Click to expand...
Click to collapse
ok right now there is
com.android.syncml.service
sense
market
messages
people
rss reader
syncml provider
sys panel
touch input
updater
and then a load of inactive cached applications
do you see anything unusual there?
ok so i downloaded system app and killed all apps except excluded and sytem apps and my running usage has gone down, now thats no suprise in and of itself but now i need to see if it stays down.
i've just checked again and the percentage is still going down, so it's either an inactive app which i didnt list ( is that even possible if its inactive) or one of the items i listed above.
has anyone got any thoughts.
What do the logs say upon going to standby? (Use aLogcat to watch/save system log).
I had same problem I tried the turning off network always on to off, didn't change anything. the thing that worked for me was turning off my flickr account!? For some reason it kept my calendar awake so keeping system from sleeping, don't ask me why as I can't figure it out, though since doing this I'm now getting up to 2 days of average use from the battery. Also I've done the usual of reducing the different accounts sync timings etc.
Have you typed *#*#4636#*#* into the phone key pad to look at what is happening? This can give valuable info on what's draining the battery.
Jazd71 said:
I had same problem I tried the turning off network always on to off, didn't change anything. the thing that worked for me was turning off my flickr account!? For some reason it kept my calendar awake so keeping system from sleeping, don't ask me why as I can't figure it out, though since doing this I'm now getting up to 2 days of average use from the battery. Also I've done the usual of reducing the different accounts sync timings etc.
Have you typed *#*#4636#*#* into the phone key pad to look at what is happening? This can give valuable info on what's draining the battery.
Click to expand...
Click to collapse
I have the same problem as OP since the latest update. The *#*#4636#*#* code is not helping in this case. The partial wake lock is displayed as Android System - which doesn't tell me anything.
I read something about the Calendar issues but I am unable to stop the calendar in running processes.
How did you solve your problem?
ferus said:
I have the same problem as OP since the latest update. The *#*#4636#*#* code is not helping in this case. The partial wake lock is displayed as Android System - which doesn't tell me anything.
I read something about the Calendar issues but I am unable to stop the calendar in running processes.
How did you solve your problem?
Click to expand...
Click to collapse
Ok i seem to have had some luck since last night though i'm not sure of the exact reason.
i did as th3 said and downloaded system monitor and then killed all background active and inactive tasks and that seems to have solved the problem. I have no idea why that would be the case though and i am watching it carefully to see if it stays fixed.
i dont have a flickr account setup
djet said:
What do the logs say upon going to standby? (Use aLogcat to watch/save system log).
Click to expand...
Click to collapse
Djet, I installed alogcat and have found all references to wakelock, rather than post the entire log
D/PowerManagerService( 77): wakelock: PARTIAL_WAKE_LOCK 'NetworkLocation Check Location' activated (minState=0)
D/PowerManagerService( 77): wakelock: PARTIAL_WAKE_LOCK 'NetworkLocation Check Location' activated (minState=0)
D/PowerManagerService( 77): wakelock: PARTIAL_WAKE_LOCK 'keyguardWakeAndHandOff' activated (minState=0)
D/PowerManagerService( 77): wakelock: FULL_WAKE_LOCK 'keyguard'ACQUIRE_CAUSES_WAKEUP activated (minState=3)
there are also some entries in red like this one
E/vold ( 53): Unable to lookup media '/devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0:0001'
and a load of errors to do with global search etc but this is all pretty much gobbledegook to me, what am i looking for?
thanks
ok so based on that log i have switched of the use wireless networks to find my location (not gps i hardly ever use that anyway) and now the running % is dropping fast.
i will keep you posted as to whether it keeps coming down or not.
it is going to be an enormous bummer if i cant use wireless location, thats one of a smartphones greatest powers, why would this suddenly start happening now ( started about a week before the ota update) and continues even when i factory reset.
kinkade said:
ok so based on that log i have switched of the use wireless networks to find my location (not gps i hardly ever use that anyway) and now the running % is dropping fast.
i will keep you posted as to whether it keeps coming down or not.
it is going to be an enormous bummer if i cant use wireless location, thats one of a smartphones greatest powers, why would this suddenly start happening now ( started about a week before the ota update) and continues even when i factory reset.
Click to expand...
Click to collapse
I suppose it's not the feature itself guilty but the applications using it. I had the same issue with battery running out because of Location service wake locks. It turned out one of the Locale app plugins was abusing this service. Having it uninstalled battery run became normal.
djet said:
I suppose it's not the feature itself guilty but the applications using it. I had the same issue with battery running out because of Location service wake locks. It turned out one of the Locale app plugins was abusing this service. Having it uninstalled battery run became normal.
Click to expand...
Click to collapse
Yes i know what you mean, how did you go about diagnosing that? also i have done several factory resets and it still happens
Re: Android system - partial wake lock
There are a many app settings that drain battery and the stock setup is nothing I am fond of. Location/locale was one of them for me, calendar, network time and widget/app syncs being the others. A non-stock app causing such problems was NetCounter.
Calendar was fixed by killing it and restarting it. It's a known bug for many.
If many widgets are running sync very often, then you can imagine battery draining fast.
-------------------------------------
- Sent via my HTC Desire -
th3 said:
There are a many app settings that drain battery and the stock setup is nothing I am fond of. Location/locale was one of them for me, calendar, network time and widget/app syncs being the others. A non-stock app causing such problems was NetCounter.
Calendar was fixed by killing it and restarting it. It's a known bug for many.
If many widgets are running sync very often, then you can imagine battery draining fast.
-------------------------------------
- Sent via my HTC Desire -
Click to expand...
Click to collapse
th3 you are legend, it was network time, i switched that off and all is now well in the world. cheers dude
Good find. I had the thing off anyway, but it is good to know.
I currently have a problem that "Google services -> event log service" is draining my battery a lot,
I was asking this in another thread about this problem but got told I should ask here in the specific forum for my phone.
I fully charged it during night and at 2:30am I rebooted the phone and unplugged the charger.
Now in the afternoon at 5pm I checked again (haven't used the phone since then) and battery was at 62 %
Wakelock detector is showing an activity of Google-services/Event log service with 1 hour 43 minutes.
Wlan off, 3G on, GPS off, bluetooth etc off.
I disabled all unessesary syncs including google backup/restore, not helping at all.
I checked developer settings for log recording etc.. but everything is off.
It's the international E975 model btw,
I have the same issue. I think i tweaked it too much lol.
Partial wakelocks in BBS indicates EventLogService has been on for 5h.. -_-
Have you done any tweaks to it? I.e: freeze anything from titanium, greenify, etc
This is a result of frozen apps.
jiexi said:
This is a result of frozen apps.
Click to expand...
Click to collapse
hi there
so if i check what apps are frozen and uninstall them, this will get rid of the problem basically, that simple??
It may just cause more problems. The reason the wakelock is even appearing as event log service is because the app is frozen, but causing wakelocks. But wait, didn't we freeze it?.. how can it still be causing wakelocks? Some other system level app is still capable of waking it, so it may or may not be something important.
jiexi said:
It may just cause more problems. The reason the wakelock is even appearing as event log service is because the app is frozen, but causing wakelocks. But wait, didn't we freeze it?.. how can it still be causing wakelocks? Some other system level app is still capable of waking it, so it may or may not be something important.
Click to expand...
Click to collapse
cheers, actually i have LOTS of wakelock time taken from these 2:
1) Alarm Manager - Android System. this one grows by 5 units every time i unlock the phone and check, NORMAL??
2) Event Log Service - Google Services, this one is a bit more quiet but still growing silently.
Things i have on:
usually sync, but those 2 above grow regardless of sync being on or off, then i have 2 alarms in the calendar, one active and one not and some calendar notifications.
are those responsible? right now my phone is doing around 2% battery use but i notice that it grows very easily, just now i lost 1% in only 25 minutes.
the "awake" graph under battery looks strange.. sometimes it matches screen off (so good), sometimes, it seems to be on, with screen OFF for no reason whatsoever.
any idea?
thanks
I have Samsung Galaxy S4 (TMO) running on rooted stock ROM 4.2.2.
Off late, I have been observing that the battery is draining much faster than it should be.
Earlier it typically used to consume ~12% of the battery during night time (when the phone is not used at all).
However, off late my battery is draining rapidly and is not standing for at least 8 hrs.
I checked the battery usage and got to see
Google Services (v4.3.11) is ranked higher at ~52% followed by
Screen
Android System
Android OS
etc.
I used Wakelock Detector to see what items are causing this drain.
I figured out that under Google Services the top ranking battery eaters are
NlpWakelock
NlpCollectorWakelock
So I tried couple of different things by disabling Google Sync. Even then, there is no change.
The following is what I did which fixed the battery drain:
1. I disabled/unchecked the Settings -> Location Services -> Location Sources -> Use wireless sources
After this, I checked the usage in the Wakelock Detector.
NlpWakelock : This one is now stopped and I don't see any activity with this wakelock
NlpCollectorWakelock : This continues to have wakelocks and is still ranking higher.
2. Now I set the Settings -> Location Services -> My places -> Home -> Selected Method -> None.
Earlier I had this option set to be identifying my home using my WiFi network. This is causing continuous In/Out data transfer (most probably polling to the network to check if the connection is alive) in the status bar observed by the WiFi icon. Once I set this to None, I don't see continuous In/Out data transfer in the status bar.
Apart from the above, I did power off the phone and removed the battery when it showed <5%. Left it like that for couple of hours. Then re-assembled and then it showed me 10% and recharged it after that. I did this on purpose to calibrate the battery (but not necessary) due to continuous discharge/recharge cycles happened for the last couple of days.
After recharging it to 100%, I left the phone without using it for 4 hrs to observe the wakelocks. Voila, the Google Services is at the bottom of the list. The above two wakelocks are no more seen under the Google Services. By the way, I did have the Google Sync on during this observation. I observed 1-2% battery drain for each one hr.
After this, the battery drain is not happening. For the past 9 1/2 hrs, accessing - Facebook, google search, The Weather Channel - couple of times resulted in 17% battery drain so far.
UPDATE: It's been almost 22 1/2 hours by now... the battery is now at 52% after a normal usage of accessing - Facebook, google search, The Weather Channel, CNN, TOI, Google+, phone calls and having Google sync on.
Hope this helps anybody else having a similar problem.
Greenify.
Yeah it's been well documented that Google Service locations(mainly the "Wi-Fi and cellular network" option) will drained the battery quick.
???
Thanks for this info. My phone started dying in the middle of the day when it didn't used to. I'm not sure if I updated something and it caused these settings to change but I will see if this helps.
This didn't help me. I have massive battery drain. I made a few wipes, changed different stock roms. Now I'm on Google edition ROM and It's the same. Nlpwakelock is a nightmare for me. Could it be a third party app problem?
Did you have Google now activated? In that case, check if you have location services activated for it. NlpWakelock is mainly associated with the location access. Using wakelock detector, you would be able to find which application is using the NlpWakelock. That would give you a clue about what other app(s) using this wakelock.
Sent from my SGH-M919 using xda app-developers app
uresh.kuruhuri said:
Did you have Google now activated? In that case, check if you have location services activated for it. NlpWakelock is mainly associated with the location access. Using wakelock detector, you would be able to find which application is using the NlpWakelock. That would give you a clue about what other app(s) using this wakelock.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
I'm using BetterBatteryStats. Disabling Google Now/Location Reporting/Location History doesn't make any difference.
radko93 said:
I'm using BetterBatteryStats. Disabling Google Now/Location Reporting/Location History doesn't make any difference.
Click to expand...
Click to collapse
Which app is showing to be using the NlpWakeLock?
radko93 said:
I'm using BetterBatteryStats. Disabling Google Now/Location Reporting/Location History doesn't make any difference.
Click to expand...
Click to collapse
One more thing, after doing any changes, in order to get fresh wake lock information, you need to restart the phone. That way, you would know if the NlpWakeLock is being used from the fresh restart. However, if you see the Battery stats from the phone Settings, it would still show the information from the last recharge.
uresh.kuruhuri said:
Which app is showing to be using the NlpWakeLock?
Click to expand...
Click to collapse
Google Play Services. I tried to restart the phone. More info about what I tried is here
Edit: I turned off Location Reporting and History, and it's much better. Google Now is making wakelocks now, but only few. Anyway Google ****ed up their own services.
Hi,
I tried to search the whole wide web for identification on this particular wakelock, but the search came out negative. I have rooted Nexus 7 (2013) with stock rom and this wakelock is getting over a thousand alarm wakelocks per discharging cycle. I know it has something to do with scheduled tasks, but have you guys had this same issue with your Nexus? Can't say how much this effects the batterylife, but it would be nice to know what causes this and is it avoidable
Here is a pic from my BetterBatteryStats so you can see the wakelock in question:
So it is called ALARM_WAKEUP_ACTIVITY_DETECTION.
Thanks!
Figured it out, at least i pinpointed the cause of this wakelock. It has something to do with Googles location services. I turned all the location services off and the wakelock disappeared. Why does Google want to wakeup my device every 3 minutes even though i have device management off, google now off, everything else that relates to location, off?
jezbez said:
Figured it out, at least i pinpointed the cause of this wakelock. It has something to do with Googles location services. I turned all the location services off and the wakelock disappeared. Why does Google want to wakeup my device every 3 minutes even though i have device management off, google now off, everything else that relates to location, off?
Click to expand...
Click to collapse
Turning Google Now off usually does it. Did you have location history and/or reporting on?
Simba501 said:
Turning Google Now off usually does it. Did you have location history and/or reporting on?
Click to expand...
Click to collapse
I had Google Now off as well for a few days without any effect. I also disabled the history and reporting and no effect. The only thing that ended those wakelocks was to permanently shut down location services. But it's not a burden to me, only a few clicks and i can have them on when i need them.
I'm no stranger to Android and troubleshooting problems, but right now I'm honestly at a loss as to what is causing my battery drain. I'm losing a little over 1% per hour while the device is in doze overnight, adding up to around 10-12% over 8 hours. Previously the max I would lose was close to 5%. I can't pinpoint exactly when something went rogue, but I want to say it was after the January update. I don't think I've added any new apps. I've obviously tried to clear data/cache in Google Play Services among some other apps too.
I've tried to use the battery historian, GSam, BBS, you name it. GSam is showing my device as constantly waking up overnight while in deep doze, but I can't attribute that to any wakelocks. BBS is basically clean as far as partial wakelocks go, and battery historian shows that 7% of the battery drain is unaccounted for. The one thing I have seen a few nights now is the Significant Motion that's in Google Play Services. I've also seen that under Phone and under Android System. I'm wondering if it's some kind of sensor, but I can't figure out what is causing it to stay on. I keep my phone on my nightstand overnight.
My next steps are going to be turning off always on display (AOD), turning on airplane mode overnight, and then doing a factory reset. I'll report back for anyone that comes across here, but I wanted to see if anyone has had similar issues.
I'm attaching a few screenshots, maybe someone can pick up something I'm missing.
https://imgur.com/a/rGxXQ
bosox284 said:
I'm no stranger to Android and troubleshooting problems, but right now I'm honestly at a loss as to what is causing my battery drain. I'm losing a little over 1% per hour while the device is in doze overnight, adding up to around 10-12% over 8 hours. Previously the max I would lose was close to 5%. I can't pinpoint exactly when something went rogue, but I want to say it was after the January update. I don't think I've added any new apps. I've obviously tried to clear data/cache in Google Play Services among some other apps too.
I've tried to use the battery historian, GSam, BBS, you name it. GSam is showing my device as constantly waking up overnight while in deep doze, but I can't attribute that to any wakelocks. BBS is basically clean as far as partial wakelocks go, and battery historian shows that 7% of the battery drain is unaccounted for. The one thing I have seen a few nights now is the Significant Motion that's in Google Play Services. I've also seen that under Phone and under Android System. I'm wondering if it's some kind of sensor, but I can't figure out what is causing it to stay on. I keep my phone on my nightstand overnight.
My next steps are going to be turning off always on display (AOD), turning on airplane mode overnight, and then doing a factory reset. I'll report back for anyone that comes across here, but I wanted to see if anyone has had similar issues.
I'm attaching a few screenshots, maybe someone can pick up something I'm missing.
https://imgur.com/a/rGxXQ
Click to expand...
Click to collapse
Are you rooted by chance? I've seen this mentioned in a couple other threads. Seems the culprit has something to do with GPS's, tethering in developer options, wifi and bluetooth scanning or a rouge app. Most all the cases I've seen have been since the 8.1 update.
Solutions I've seen...turn off everything in the pic.
Clear cache/data on play services(kinda risky)
Clean flash the January update with fastboot.
Turn off bluetooth and wifi scanning.
Check your router setup(some wifi setups like to keep waking the device. I get this in hotels at times)
Try turning wifi off at night.
How many apps are using location services?(I had a weather app that was keeping my device awake)
This can definitely be a bugger to identify. Sure hope you find it ?
Badger50 said:
Are you rooted by chance? I've seen this mentioned in a couple other threads. Seems the culprit has something to do with GPS's, tethering in developer options, wifi and bluetooth scanning or a rouge app. Most all the cases I've seen have been since the 8.1 update.
Solutions I've seen...turn off everything in the pic.
Clear cache/data on play services(kinda risky)
Clean flash the January update with fastboot.
Turn off bluetooth and wifi scanning.
Check your router setup(some wifi setups like to keep waking the device. I get this in hotels at times)
Try turning wifi off at night.
How many apps are using location services?(I had a weather app that was keeping my device awake)
This can definitely be a bugger to identify. Sure hope you find it
Click to expand...
Click to collapse
I am rooted. I've got WiFi/bluetooth scanning off, but I did just notice that Tethering hardware acceleration was on. I'm turning that off. I'll see how that goes tonight, if it's still draining then I'll try turning WiFi off and see what happens.
I've got GasBuddy, Google, Play Services, Maps, and WTForecast using location. None of those usually show up in any battery stats aside from Play Services.
bosox284 said:
I am rooted. I've got WiFi/bluetooth scanning off, but I did just notice that Tethering hardware acceleration was on. I'm turning that off. I'll see how that goes tonight, if it's still draining then I'll try turning WiFi off and see what happens.
I've got GasBuddy, Google, Play Services, Maps, and WTForecast using location. None of those usually show up in any battery stats aside from Play Services.
Click to expand...
Click to collapse
Wtf weather was the one giving me trouble at one time. I just turned a few things off on that one. Are you using the "enable doze for GSM" magisk module like in the pic. That really seems to keep google play services in check :good:
bosox284 said:
I am rooted. I've got WiFi/bluetooth scanning off, but I did just notice that Tethering hardware acceleration was on. I'm turning that off. I'll see how that goes tonight, if it's still draining then I'll try turning WiFi off and see what happens.
I've got GasBuddy, Google, Play Services, Maps, and WTForecast using location. None of those usually show up in any battery stats aside from Play Services.
Click to expand...
Click to collapse
I wouldn't worry about turning off AOD saving you a bunch, I turned mine off and didn't notice any diff at all in overnight batt drain, so set it to DIM, and still haven't noticed any additional batt drain from when it was off.
If you really want to be a miser without totally losing AOD,
"always on" OFF,
"Lift to check phone" ON,
(Settings>Display>Ambient display>)
set it to DIM (Settings>Display>Screen Saver>Current Screen Saver gear>Night mode checked)
which is how mine is set up
Badger50 said:
Wtf weather was the one giving me trouble at one time. I just turned a few things off on that one. Are you using the "enable doze for GSM" magisk module like in the pic. That really seems to keep google play services in check :good:
Click to expand...
Click to collapse
Where is that fix touch module?
Sent from my Google Pixel 2 XL using XDA Labs
Prattham said:
Where is that fix touch module?
Click to expand...
Click to collapse
Look in downloads in magisk manager.
Badger50 said:
Wtf weather was the one giving me trouble at one time. I just turned a few things off on that one. Are you using the "enable doze for GSM" magisk module like in the pic. That really seems to keep google play services in check :good:
Click to expand...
Click to collapse
I've been trying to avoid using that module just because I don't want to delay anything from GCM, but I'm going to look into it if I can't identify another culprit.
bosox284 said:
I've been trying to avoid using that module just because I don't want to delay anything from GCM, but I'm going to look into it if I can't identify another culprit.
Click to expand...
Click to collapse
Delay what? ?
Badger50 said:
Delay what? <span class="emoji-outer emoji-sizer"><span class="emoji-inner" style="background: url(chrome-extension://immhpnclomdloikkpcefncmfgjbkojmh/emoji-data/sheet_apple_32.png);background-position:73.97179788484137% 79.9647473560517%;background-size:5418.75% 5418.75%" data-codepoints="1f914"></span></span>
Click to expand...
Click to collapse
GCM = Google Cloud Messaging, it's integrated into apps for push notifications. My (perhaps incorrect) assumption is that by dozing Play Services, you could delay push notifications for other apps.
bosox284 said:
GCM = Google Cloud Messaging, it's integrated into apps for push notifications. My (perhaps incorrect) assumption is that by dozing Play Services, you could delay push notifications for other apps.
Click to expand...
Click to collapse
Haven't noticed any delay what so ever with any push notifications from any apps. Google or otherwise :good:
I lost 11% overnight (8 hours), I have Amplify, Enable Doze for Google Play Services Magisk module and ForceDoze, and still getting that drain.
Could it be these apps conflicting with one another?
I noticed this as well and it seems to have started after the January update. Although mine isn't quite as bad. Pre-January update I was losing about 2-3% in like 8 hours. I'm now losing that much in like 4-5 hours. There were 2 days in a row where I actually lost like 15-18% over like 7 hours.
rickysidhu_ said:
I lost 11% overnight (8 hours), I have Amplify, Enable Doze for Google Play Services Magisk module and ForceDoze, and still getting that drain.
Could it be these apps conflicting with one another?
Click to expand...
Click to collapse
Get rid of amplify and forcedoze. Then see what happens. You've got too many things trying to do the same thing!
The Jan update has been ****. I would get almost 7 hrs SOT with 20% left. Now all I get is ****ty 4 hrs and phone at 10%. Usage wise it's the same since day 1 nothing new as such. No rogue app on BBS. This is messed up.
Badger50 said:
Get rid of amplify and forcedoze. Then see what happens. You've got too many things trying to do the same thing!
Click to expand...
Click to collapse
Yeah I had a feeling that could be it. I'll give it a shot by removing them, thanks for the suggestion! :highfive:
Badger50 said:
Look in downloads in magisk manager.
Click to expand...
Click to collapse
It isn't there that's why i asked
Sent from my Google Pixel 2 XL using XDA Labs
bosox284 said:
I am rooted. I've got WiFi/bluetooth scanning off, but I did just notice that Tethering hardware acceleration was on. I'm turning that off. I'll see how that goes tonight, if it's still draining then I'll try turning WiFi off and see what happens.
I've got GasBuddy, Google, Play Services, Maps, and WTForecast using location. None of those usually show up in any battery stats aside from Play Services.
Click to expand...
Click to collapse
Try to run "su" and then "top" from terminal,
See what is your top process,
In one occassion, my magisk hide stucked up and using 30%++ of CPU all the time, even when idle, and that drain the battery in no time,
Am on 8.1 Jan, Kiriskura Kernel,
Tweak applied is Brevent, Amplify and my own EnableDoze for GMS.
Never lost more than 5% in 9 hours of sleep. Average is 2-3% with wifi on. Less than 2% when network is totally off
Prattham said:
It isn't there that's why i asked
Click to expand...
Click to collapse
You can try the one attached.
I cant find it in download section as well
Prattham said:
It isn't there that's why i asked
Click to expand...
Click to collapse
My bad. I forgot that it was a special build by another user. Install it from magisk manager. If it doesn't install, then flash it in twrp.
https://github.com/AndroPlus-org/ma...b/master/magisk-module-fix-touch-pixel2xl.zip