Develop Bugs

Android system - partial wake lock - one solution found

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.

Wakelock overflow 1013

This I'd always in does anybody know what this is?
Sent from my SPH-D710

Here is a pic I took earlier.

wiki in here -
http://forum.xda-developers.com/wiki/Wakelocks

kobridge said:
wiki in here -
http://forum.xda-developers.com/wiki/Wakelocks
Click to expand...
Click to collapse
thanks but still not sure what my specific wakelock is?

polska2180o said:
thanks but still not sure what my specific wakelock is?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=626210
long story to short - 1013 is a media server process.

I'm getting the same problem, how did you solve the problem?

I am having this same issue, different device, but this is the first thread I found with the issue.

Have you been listening to music?
sent from MY BAD A$$ ET4G

Had anyone figured out what this is? I have not been listening to music at all.

Tsudeily said:
I am having this same issue, different device, but this is the first thread I found with the issue.
Click to expand...
Click to collapse
Media is pretty unspecified, could be pictures, videos, not just music

I have it too on my Verizon s4, just installed Google experience launcher and new search on it today, hadn't seen it before... running bone stock otherwise. 4.3.
Edit, turned off ok Google listening... haven't seen it since, at least today.
Sent from my Nexus 7 using Tapatalk 4

1013 wakeup fix
sl33p3 said:
I have it too on my Verizon s4, just installed Google experience launcher and new search on it today, hadn't seen it before... running bone stock otherwise. 4.3.
Edit, turned off ok Google listening... haven't seen it since, at least today.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I erased the google music widget and fix the problem with 1013 wakeup, hope this helps

Daniel Ilie444 said:
I erased the google music widget and fix the problem with 1013 wakeup, hope this helps
Click to expand...
Click to collapse
We have got the same problem with Galaxy Note 3, stock rom, rooted. At some point in the night, this *overflow* starts to keep the phone awake and uses 40% of battery in less than 3 hours.
There is no widget on any homescreen.

vincentgdg said:
We have got the same problem with Galaxy Note 3, stock rom, rooted. At some point in the night, this *overflow* starts to keep the phone awake and uses 40% of battery in less than 3 hours.
There is no widget on any homescreen.
Click to expand...
Click to collapse
Better Battery Stats or Wakelock Detector will help you to figure out what app(s) are causing it.
My ROM: WICKED X

bilgerryan said:
Better Battery Stats or Wakelock Detector will help you to figure out what app(s) are causing it.
Click to expand...
Click to collapse
Unfortunately Wakelock Detector doesn't show anything uncommon. I deinstalled Spotify and Quizduell Premium, rebooted the phone again - and the problem seems to be gone.
This really is strange behaviour and Android should by now be able to find out those problems by itself. This reminds me of Windows, which after over a decade still struggles with problems and you have to install tools to solve them - or reinstall the whole system.

Hi, I know this is an older thread but I've been having the same problem recently and I tried to Google a solution to the problem and found this thread. I too have had high battery drain from Google Services. The phone is basically awake at all times. GSAM Battery Monitor lists *overflow* as the main culprit.
I have location services turned off and I turned off syncing of all accounts except for Gmail. I uninstalled all updates to Google Services and any apps associated with it. I have rebooted the phone multiple times. I'm pretty sure I've tried every battery saving tip I can possibly find and nothing seems to solve the problem. Every now and then I'll get a day of amazing battery life and think my problems are behind me; then it will go back to the same terrible battery life without me changing any settings or changing the way I use the phone.

crazydoglady said:
Hi, I know this is an older thread but I've been having the same problem recently and I tried to Google a solution to the problem and found this thread. I too have had high battery drain from Google Services. The phone is basically awake at all times. GSAM Battery Monitor lists *overflow* as the main culprit.
I have location services turned off and I turned off syncing of all accounts except for Gmail. I uninstalled all updates to Google Services and any apps associated with it. I have rebooted the phone multiple times. I'm pretty sure I've tried every battery saving tip I can possibly find and nothing seems to solve the problem. Every now and then I'll get a day of amazing battery life and think my problems are behind me; then it will go back to the same terrible battery life without me changing any settings or changing the way I use the phone.
Click to expand...
Click to collapse
Have you tried turning mobile data and/or Wi-Fi off when not in use?

[Q] Google Play Services draining battery

This is draining my battery. Kept phone awake for almost 100% on time. Anyone else noticing this? Not changed anything. Only thing that has changed is I now have Google Glass, but I dont have them with me today, so it wouldnt be using that.

droidkevlar said:
This is draining my battery. Kept phone awake for almost 100% on time. Anyone else noticing this? Not changed anything. Only thing that has changed is I now have Google Glass, but I dont have them with me today, so it wouldnt be using that.
Click to expand...
Click to collapse
I was having a similar problem with Play Services and Media Services. I installed App Cache Cleaner and set it to auto wipe every hour or so. That fixed the problem (or at least stopped it from draining the battery).
Hope that helps.

Techngro said:
I was having a similar problem with Play Services and Media Services. I installed App Cache Cleaner and set it to auto wipe every hour or so. That fixed the problem (or at least stopped it from draining the battery).
Hope that helps.
Click to expand...
Click to collapse
I have disabled use wireless networks in Location Services and all has gone back to normal. Maybe give that a shot and see if that fixes it for you.

Researched this a lot, found some solutions, bad and good fixes and after trying some different twists on it after two days this is what I found to be the best, and I decided since this is just as bad as 4.0/4.1 and the mediaserver battery drain I might as well try and help at least 1 person by mass posting this reply I wrote else where to other threads, so here you go:
"Hey- I don't know if you, or anyone else has found a working solution, but here is the way I found best:
Note- I am on galaxy s4 [sgh-i337] running a 4.4 KitKat rom. I have found the following work around to work best for me:
1 Google now & Hotword detection=OFF,
2 GPS = OFF and turned on only when needed, eg maps/checkin on facebook/whatever needs location.
3 Settings-> Manage Apps -> Google Play Services -> Manage Space -> Clear All Data.
**Optional:After this [root only] I go into KT tweaker and make sure my phone cpu is set to a max of 810 Mhz when screen off.**
This fix usually works until I reset the phone. I ALWAYS follow those 3 steps when rebooting. AND always check that after I've used GPS that Google Play Services isn't keeping my phone awake. [Eg, after 30 minutes I check if the phone ever went to sleep again when the screen was off.] IF it does act up, I repeat steps 1, 2 &3. I still get notifications and all, and this is the least feature disabling way I've found that works with the cost of a little micro-management of your phone.
With this fix I can idle for an estimated 5-6days. As I take off my phone from charge at 8am and at noon with minimal usage [maybe 4 or 5 texts] I am at 97%. With WiFi on & connected.
OTHER: I personally keep NFC&Android beam&Bluetooth OFF, and turn ON when I need it on. Other- WiFi is always ON, and "Scanning Always Available" & "WiFi Optimization" is checked ON for me. And for location mode when I do have it on, I keep it at EDIT: Device only. Using only gps to find my location.
All in all, I hope this gets fixed."
I can post screen shots and all if somebody wants them or if there is need for one
-icy

VS985 Lollipop stock RILJ wakelock

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.

Help with identifying wakelocks/battery drain

Hi everyone, for the past couple of weeks I have had more idle drain than usual on my rooted Nexus 5x. The problem has persisted across multiple roms. I recently returned to stock, and waited a day to restore my user apps with Titanium Backup, and in that day, the stock rom did NOT have the problem. Then, when I restored user apps, the problem returned. So it appears that one of MY apps, not the OS, is causing the wakeups. However, in both BetterBatteryStats and Wakelock Detector I cannot find any particular wakelock(s) that seem to be causing this issue.
The only concrete evidence I have is the Android built in battery details screen. In the screenshot of the graph and the awake/screen on bars, you can see constant wakeups starting around 2pm (when I restored user apps). Before that, the phone mostly slept while the screen was off, but after 2pm, it has been waking up constantly. I have also attached Wakelock Detector screenshots (Have not used BBS yet on this ROM). They show awake time that is much higher than the sum of the listed wakelocks. (Note: the 52 minute "Photos" app wakelock was a one time thing today, the problem has persisted without that.) If anyone can figure out what might my issue is, I would hugely appreciate it! Thanks!

Best way might be to restore one app per day to figure out which app it is

2x4 said:
Best way might be to restore one app per day to figure out which app it is
Click to expand...
Click to collapse
I was hoping to avoid that, in case anyone had any ideas. But I have a feeling I'll have to. Thanks!

brentoma589 said:
Hi everyone, for the past couple of weeks I have had more idle drain than usual on my rooted Nexus 5x. The problem has persisted across multiple roms. I recently returned to stock, and waited a day to restore my user apps with Titanium Backup, and in that day, the stock rom did NOT have the problem. Then, when I restored user apps, the problem returned. So it appears that one of MY apps, not the OS, is causing the wakeups. However, in both BetterBatteryStats and Wakelock Detector I cannot find any particular wakelock(s) that seem to be causing this issue.
The only concrete evidence I have is the Android built in battery details screen. In the screenshot of the graph and the awake/screen on bars, you can see constant wakeups starting around 2pm (when I restored user apps). Before that, the phone mostly slept while the screen was off, but after 2pm, it has been waking up constantly. I have also attached Wakelock Detector screenshots (Have not used BBS yet on this ROM). They show awake time that is much higher than the sum of the listed wakelocks. (Note: the 52 minute "Photos" app wakelock was a one time thing today, the problem has persisted without that.) If anyone can figure out what might my issue is, I would hugely appreciate it! Thanks!
Click to expand...
Click to collapse
I believe I suffered the same issue, and I have a solution. Not a fix but solution...
http://forum.xda-developers.com/nexus-5x/help/google-photos-device-awake-diff-roms-t3406571

Seeing the same issue ... have disabled the AutoSignInandSync service, waiting for the results and will update if that helped.