Develop Bugs

Major battery drain from kernel wakelock

Hi,
I'm getting a major battery drain from a kernel Wakelock, and I cannot figure out how to fix it. I've tried reinstalling the ROM, to no avail. Using Eclipse.
Screenshot from BBS attached.
Sent from my Galaxy Nexus using XDA

I have the exact same 7 causing all kinds wakelocks over the last week. I've tried everything to try and figure out what the hell is causing it to no avail. If you figure it out, please let me know! I'm begining to think it was an update to an app that started causing this to happen (even though no apps are shown)

try disabling autosync and see if it works,non gsm version?

Nothing set to sync

Power manager service is a combination of all wakelocks in userland, meaning it combines all wakelocks caused by you (music, phone calls...etc), the others (minus alarm rtc which I'm not sure of) are all related to having the phone USB mounted which I'm assuming you have.

my gnex dosnt get deep sleep, someone know fix it?

zerocool79346 said:
Power manager service is a combination of all wakelocks in userland, meaning it combines all wakelocks caused by you (music, phone calls...etc), the others (minus alarm rtc which I'm not sure of) are all related to having the phone USB mounted which I'm assuming you have.
Click to expand...
Click to collapse
Nope, not USB mounting at all for me.
Sent from my Galaxy Nexus using XDA

i have deep sleep in CPU Spy but in betterbatterystats no

zerocool79346 said:
Power manager service is a combination of all wakelocks in userland, meaning it combines all wakelocks caused by you (music, phone calls...etc), the others (minus alarm rtc which I'm not sure of) are all related to having the phone USB mounted which I'm assuming you have.
Click to expand...
Click to collapse
I don't know what USB mount means, but why would there be a wakelock for usb when the phone is not connected to a usb cord?
Also, I've tried turning off sync, and the phone still has severe drain. It randomly fluctuates between losing less than 1%/hr to 6%/hr+, even when the phone is idle and sitting in the same place. I've noticed that there are quite a few times when the phone is awake, even though my screen is off and I'm not using it.
If this is an app causing the problem, how do I diagnose the issue? Shouldn't it be showing up in "battery" under settings or as a specific wakelock in Better Battery Stats. I used to easily get 2 hrs of screen time on CDMA LTE, but now I'm lucky if I can get 80 minutes.
I thought it might be the battery itself, so I went out and bought a new one. That was a waste - same issue.
Any insights?

Still can't figure this out. Anyone?

Change kernels.
Sent from my Galaxy Nexus using Tapatalk 2

Already did that. Didn't make a difference. There must be a reason this is happening.
Sent from my Galaxy Nexus using XDA

Stockmoose16 said:
Already did that. Didn't make a difference. There must be a reason this is happening.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I think I finally fixed my issue. I don't know exactly what it was but it had something to due with the following: Open Latitude and sign out (apparently I was logged back in after the last maps update), kill facebook everytime I close it (keeps way too many services open even though I don't have it to sync), enabled and disabled sync, bt, gps, 4g, uninstalled voodoo mods, re-disabled maps from autostarting, made sure I was logged out of talk, and also logged out of google +, some combination of the above fixed it for me.
I'm willing to bet it was a combination of maps, talk, latitude, and facebook since I tried most of the other things prior to the above. I updated maps and facebook the same day so it could be either of those.

None of those are the issue for me. I completely switched out my ROM and went down to a barebones number of apps. Still having a major issue with the exact same kernel wakelocks. I literally did not touch my phone overnight, and it still lost quite a bit of battery.
How come nobody seems to know what the wakelocks mean from my screenshot posting? This is impossible to diagnose.
Sent from my Galaxy Nexus using XDA

having the same issue. My battery life would be nearly ideal without this wakelock and the "modem_usb_gpio_wake" problem using up the battery. Using AOKP build 35 with lean kernel

Is this not the correct forum to post in? This question has been asked numerous times with the Galaxy Nexus, but nobody had given a solution.
My phone drain is terrible with these kernel wakelocks, but nothing fixes it. I've tried numerous other kernels with the same result. I've killed all my apps. I'm stumped.
What could possibly be causing this out of the blue?
Sent from my Galaxy Nexus using XDA

Stockmoose16 said:
Is this not the correct forum to post in? This question has been asked numerous times with the Galaxy Nexus, but nobody had given a solution.
My phone drain is terrible with these kernel wakelocks, but nothing fixes it. I've tried numerous other kernels with the same result. I've killed all my apps. I'm stumped.
What could possibly be causing this out of the blue?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Your best bet is to post a dump of your BBS results in the BBS thread, Chamonix and others in that thread know their stuff.

What program do I use to make a dump file?
Sent from my Galaxy Nexus using XDA

Stockmoose16 said:
What program do I use to make a dump file?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
BBS. Menu>More>Dump to File.

CMNein said:
Your best bet is to post a dump of your BBS results in the BBS thread, Chamonix and others in that thread know their stuff.
Click to expand...
Click to collapse
I'm pretty sure if people just searched how to do it, they would find betterbattery stats thread here in xda. Still, thanks man.
Sent from my i9250

No Wifi Deep Sleep with CM9

I've been going back and forth and trying to figure out what the issue is, but I'm wondering if anyone else is having Deep Sleep issues when using CM9 on the GSM Galaxy Nexus? I can restore my Nandroid of stock 4.0.4 with the UGLC1 modem and according to CPU Spy I have no problem going into Deep Sleep and having a high deep sleep percentage. I'm using the 20120518 CM9 nightly and I just can't seem to manage deep sleep. I went into CWM formatted /system, /data, and /cache. I then ran the jBroid kernel cleaning script and installed CM9. Did a factory data wipe and then booted it up. I didn't install gapps and used ADB to install CPU spy. So no google account or anything. I turned on WiFi, reset the timers in CPU Spy and left the phone alone for at least an hour. After an hour I had a sleep time of 3%. Any thoughts or solutions?

Is it staying fully connected. It might be disconnecting and reconnecting not allowing the phone to sleep.
Sent From My Sprint Galaxy Nexus via XDA Premium

Is there a way I can check this? This could be possible, but it seems like it should be causing stock 4.0.4 to never deep sleep and not just CM9. I might have to try CM9 with some different kernels and see.

duowing said:
Is there a way I can check this? This could be possible, but it seems like it should be causing stock 4.0.4 to never deep sleep and not just CM9. I might have to try CM9 with some different kernels and see.
Click to expand...
Click to collapse
It could be a bad flash. Redownload it and reflash wiping clean... data dalvik and formatting the /system. Then see what happens. If that doesn't work try the samurai kernel .
Sent From My Sprint Galaxy Nexus via XDA Premium

deep sleep cpu spy
I was having the same issue with CM9. I was showing 45% 350mhz 45% deep sleep on CM9 but when on stock I was deep sleep 80%+. I reset the cpu spy timers and now after 18 hours cpu spy time I'm back at 80% deep sleep.
Jeff

lockup during sleep

My phone locks up 2-3 times a day when sleeping. When it locks up, the "SAMSUNG" splash screen briefly flashes, and the phone vibrates. If left alone, it gets warm. I have to hold the power button or pull the battery to restart it. I have been unable to adb into the phone to get logcat or dmesg after it locks up. Also, this never occurs while the phone is plugged in. I have tried Darkside v8 with both Venom and Faux 008 kernels, as well as Jedi Mind Trick 8/18 with Faux 009. With Darkside, I tried changing the screen-off governor with System Tuner to ondemand as mentioned at http://forum.xda-developers.com/showpost.php?p=29559002&postcount=8633, but it didn't help. Is there anything I may have done wrong, or any way to fix this? Thanks!

What happens if you don't touch the governor?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

elesbb said:
What happens if you don't touch the governor?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
With conservative governor and screen-off set to no governor change, it crashed this morning. Running Mind Trick 8/18 with Faux 009.

MadMax3947 said:
With conservative governor and screen-off set to no governor change, it crashed this morning. Running Mind Trick 8/18 with Faux 009.
Click to expand...
Click to collapse
Try on demand .
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

elesbb said:
Try on demand .
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I set the governor to ondemand and rebooted. Phone locked up within 10 minutes. Also, if it helps, I had Venom clocked at 384/1512 and Faux at 384/1728 (since I can't lower the max because of DVFS). Darkside v8 ran fine for about a week before the crashes began.

MadMax3947 said:
I set the governor to ondemand and rebooted. Phone locked up within 10 minutes. Also, if it helps, I had Venom clocked at 384/1512 and Faux at 384/1728 (since I can't lower the max because of DVFS). Darkside v8 ran fine for about a week before the crashes began.
Click to expand...
Click to collapse
When you say lock up you're talking about sleep of death correct? Have you logcat afterwards?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

elesbb said:
When you say lock up you're talking about sleep of death correct? Have you logcat afterwards?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
It only locks up when the screen is off, and never when plugged in. I tried Streamline kernel a while ago and got sleep of death basically every time the screen turned off (and I went back to stock immediately), but this seems different (in that it doesn't just not wake up like Streamline, the phone vibrates and displays the SAMSUNG splash before it won't wake up). I tried to get a logcat with adb when it last crashed, but the phone didn't even show on my computer's USB bus. I restarted it and took a logcat and dmesg until it booted, which I can send you if you wish.

I tried flashing Gideon's stock OC/UV script (http://forum.xda-developers.com/showpost.php?p=20946429&postcount=574), thinking that my phone may just be unable to handle the default UV with Venom and Faux, but this caused it to SOD (without the SAMSUNG splash) almost immediately. I went back to my Nandroid of Darkside v8 (since Mind Trick didn't help things), and flashed Faux 009 with the undervolt set with System Tuner to -12.5mv below stock for all stock frequencies. If this doesn't help, is there a possibility that my phone is faulty? I have had it since December. Also, could this be related to the GPU or L2 overclocks in Venom and Faux (but if so, why wouldn't it crash when the phone is awake)? Thank you for your time.
If it still crashes, I have a flashable zip of the stock ICS kernel and its modules that I can try, or if extremely necessary I can ODIN back to stock.
EDIT: manual Faux UV did not help, just flashed stock.
EDIT2: It just crashed with stock kernel as well (still using Darkside v8 ROM). Since it doesn't seem to be ROM or kernel related, I'm worried it may be the phone (perhaps whatever passes for a PSU in a smartphone? It'd explain why it doesn't crash on battery power). I'll probably try flashing AOKP ICS next in case it's a TouchWiz problem. Is there anything I'm missing here, or should I ask for a warranty exchange if AOKP or stock ODIN still crashes?
EDIT3: Uninstalled System Tuner to be completely sure nothing's affecting the governor/voltage/clock/etc. (still Darkside v8 ROM, stock UVLE1 kernel), crashed within 15 minutes of restart.

MadMax3947 said:
It only locks up when the screen is off, and never when plugged in. I tried Streamline kernel a while ago and got sleep of death basically every time the screen turned off (and I went back to stock immediately), but this seems different (in that it doesn't just not wake up like Streamline, the phone vibrates and displays the SAMSUNG splash before it won't wake up). I tried to get a logcat with adb when it last crashed, but the phone didn't even show on my computer's USB bus. I restarted it and took a logcat and dmesg until it booted, which I can send you if you wish.
Click to expand...
Click to collapse
I would put stock ROM back on it take it to a t mobile store and show them what's happening. If you have warranty they should replace it. Your CPU is shot. It won't go into deep sleep. And when running stock, it's not a software issue. It's hardware.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

elesbb said:
I would put stock ROM back on it take it to a t mobile store and show them what's happening. If you have warranty they should replace it. Your CPU is shot. It won't go into deep sleep. And when running stock, it's not a software issue. It's hardware.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I was worried about this. I will ODIN back to stock tonight, but I won't be able to take it to a t-mobile store for a couple of days. Thank you for your help.
EDIT: I have been running stock UVLE1 (kernel and ROM) without root for almost a day now, and it has not locked up. According to CPU spy, the phone is able to enter deep sleep. Could there be something in the custom boot scripts used by Darkside and Mind Trick that my phone doesn't like? It's about the only thing I could think of that would not be fixed by the stock kernel. I might try re-rooting and/or flashing AOKP ICS in a few days if my phone holds up.

No deep sleep jb-4.1.2

Hello. I have compiled my own build from source 4.1.2_r1 using the binaries from JR003R. My phone will not deep sleep with stock or custom kernels. Curious if anyone has had any issues with this? Thanks

flyinj54 said:
Hello. I have compiled my own build from source 4.1.2_r1 using the binaries from JR003R. My phone will not deep sleep with stock or custom kernels. Curious if anyone has had any issues with this? Thanks
Click to expand...
Click to collapse
What does battery stats list as draining battery?
Swype'ed on my CM10 Galaxy Nexus

Using Gsam battery monitor. Shows 25% drain is kernel but also shows held awake @ 9%. Showing phone @ 4% with number of wake locks 389. Seems excessive. I'm not sure if held awake is when you are using the phone or what exactly that means.
Using LeanKernal as of right now 230mhz. Cpu spy shows 230mhz for almost all usuage with phone screen off and no deep sleep at all.
Edit: It has to be in my build. Flashed another users build and deep sleep works fine. Going to give another repo sync and fresh compile and give it another shot. Thanks

i'm running my own build as well and i dont have deep sleep issues, but naturally more testing is needed. bbs shows nothing to note and cpuspy also seems normal.
also, i'm not running straight stock kernel. sched sio/gov interactive.
used gcc 4.7. new kernel srcs havent been uploaded yet, afaik.
same apps that on JRO03R, just formatted /system and flashed.
sent from my i9250

My phone is working on 384 MHz instead of Deep Sleep

Yesterday i installed CM 10.1.3 from official cyanogenmod site. First few hours i had big battery drain and i saw that the phone isn't going into DEEP SLEEP but only at 384 MHz. I thought that some app is staying on even with locked screen so i downloaded Clean Master and set it to kill apps when screen is off and also i clicked on "don't keep activities" from dev.options menu.
I discovered one bug on this rom - the NFC cannot shut down, is it possible to stay at 384 MHz just because my NFC is always on? If not, give me some suggestion please

qtoo941 said:
Yesterday i installed CM 10.1.3 from official cyanogenmod site. First few hours i had big battery drain and i saw that the phone isn't going into DEEP SLEEP but only at 384 MHz. I thought that some app is staying on even with locked screen so i downloaded Clean Master and set it to kill apps when screen is off and also i clicked on "don't keep activities" from dev.options menu.
I discovered one bug on this rom - the NFC cannot shut down, is it possible to stay at 384 MHz just because my NFC is always on? If not, give me some suggestion please
Click to expand...
Click to collapse
Get rid of clean master. Get gsam and cpuspy from playstore. Sounds like you have cpuspy or something similar.....but gsam can tell you what is keeping your device awake. Then you can deal with it....or search on the app keeping device awake and find fix.
Sent from my Nexus 7 using xda app-developers app

I don't know if NFC would prevent deep sleep, or if clean master would help ( I'd uninstall it ), but I've spent a lot of time researching battery life fixes, so here's some tips:
1. Get the Better Battery Stats app - it's essential. You're most likely going to look under the Partial Wakelocks section from the dropdown. That'll help you narrow down which apps are keeping the device awake. Kernel Wakelocks are important too, but require some research into what stuff means. Select your reference point ( Boot, Unplugged, etc. ), then try to avoid using your phone for a couple of hours from that event at least before checking this app to get better results of what's causing issues.
2. After finding which apps are problematic, you can uninstall them, freeze them, or do the following if you prefer to keep using them without hurting your battery as much:
Install Greenify and hibernate the problematic apps. Hibernating an app prevents it from running unless you start it.
For extra measure, also get ROM Toolbox ( not sure if you need the pro version ), go to "Auto Start Manager", and uncheck certain things for apps ( like Facebook auto starting on location change, for example ) to lessen app wakelocks. You can also use the paid AutoStarts app in the market with the red car icon if you prefer something simpler.
**Note: disabling certain autostarts can break a function of an app, or the whole app, until you enable it again, so be wary of that**.
3. I don't believe this is even an issue anymore, but some roms had issues going into deep sleep on multi-core devices. Eugene373's CPU Sleeper should fix that. I haven't looked into this much though, so not sure whether it works or not.
4. I found this thread on the Skyrocket forums really useful when my phone was losing battery while charging: http://forum.xda-developers.com/showthread.php?t=1759541 .
Also, to save more battery, keep your screen at dimmest system brightness when you can, and turn off sync, data, & WiFi if you don't need it. GPS *should* be okay on all the time, because from what others say, GPS only wastes battery if an app is using it, so if you deal with the app, the GPS is fine.
tl:dr;
Not sure if NFC prevents sleep or if clean master helps. Use Better Battery Stats to find wakelocks. Use Greenify to hibernate problem apps. Use ROM Toolbox's "Auto Start Manager" or AutoStarts to stop problem apps from auto starting.

Oh....another long time habit I have is to reboot after you unplug from charger....every time! This used to be a common fix.....and I still do it.
Sent from my Nexus 7 using xda app-developers app

kj2112 said:
Oh....another long time habit I have is to reboot after you unplug from charger....every time! This used to be a common fix.....and I still do it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I tried your trick but it didn't work
Anyway, i downloaded GSAM Battery Monitor and also Greenify. I stayed like 1 hour and after that i opened GSAM and there was information that my battery drain is caused of Media Service. "Downloads" system app is working in background and it is preventing my phone to get into Deep Sleep. I tried to add downloads system app into Greenify but for this thing i need to get paid version .. anyway, i will not pay it
What to do now, at least now i know why i cannot enter in deep sleep - because of downloads system app ^_^

qtoo941 said:
I tried your trick but it didn't work
Anyway, i downloaded GSAM Battery Monitor and also Greenify. I stayed like 1 hour and after that i opened GSAM and there was information that my battery drain is caused of Media Service. "Downloads" system app is working in background and it is preventing my phone to get into Deep Sleep. I tried to add downloads system app into Greenify but for this thing i need to get paid version .. anyway, i will not pay it
What to do now, at least now i know why i cannot enter in deep sleep - because of downloads system app ^_^
Click to expand...
Click to collapse
Titanium backup can convert any system app to a user app. Then greenify will see them. The catch 22 may be that it only works on titanium backup pro version. LOL
But check and see!
Sent from my cellular telephone

My note3 also had a deep sleep lack this week. The culprit was Clean Master itself. Probably they messed up something with the last update. Beware.