[Q] pm8921_eoc Wakelock Problem - Nexus 4 Q&A, Help & Troubleshooting

Hello there,
Recently I've been seeing pm8921_eoc wakelock even above the msm_hsic_host wakelock.
I've been seeing unexpected drains in my battery life too!
I read this post: http://forum.xda-developers.com/showpost.php?p=36736462&postcount=7049
From what I understand, this wakelock shouldn't wake up the device when it is unplugged. However, when I unplug my device and check my phone after an hour or so WITHOUT usage, it is down by almost 10-15%. When I looked up the wakelocks PM8921_EOC topped the list.
QUESTIONS:
1> Why is this wakelock requested and what does it do?
2> Is there any solution to it?
3> Is it to do with the charging cable I use? (I use the stock cable - the one that came with the phone)
Waiting for a quick response.
Regards.

Related

[Q] Weird battery levels

Hey Guys,
this morning I woke up to a dead phone again. Which was odd, because i charged it to 100% a couple of hours before I went to sleep.
When I turned it on and plugged it into the charger I immediately went into the battery usage log and took these screenshots.
Now, I heard of problems with the N4, the battery not being the best and all, but is it normal for the phone to discharge in that time by just lying around?
Also, when I plugged it in, the displayed battery level climbed somewhat fast. It had 1% when I plugged it in and 10% a minute after that. While I write this, it's at 20% already.
Is this anything out of the ordinary or am I just imagining it?
danielms22 said:
Hey Guys,
this morning I woke up to a dead phone again. Which was odd, because i charged it to 100% a couple of hours before I went to sleep.
When I turned it on and plugged it into the charger I immediately went into the battery usage log and took these screenshots.
Now, I heard of problems with the N4, the battery not being the best and all, but is it normal for the phone to discharge in that time by just lying around?
Also, when I plugged it in, the displayed battery level climbed somewhat fast. It had 1% when I plugged it in and 10% a minute after that. While I write this, it's at 20% already.
Is this anything out of the ordinary or am I just imagining it?
Click to expand...
Click to collapse
Have you installed any new apps lately?
I'm betting you have a wakelock that is preventing your phone from entering deep sleep.
Download Better Battery Stats and see if it's wakelock causing it
http://forum.xda-developers.com/showthread.php?t=1179809
mrhiab said:
Have you installed any new apps lately?
I'm betting you have a wakelock that is preventing your phone from entering deep sleep.
Download Better Battery Stats and see if it's wakelock causing it
http://forum.xda-developers.com/showthread.php?t=1179809
Click to expand...
Click to collapse
Let's see... I installed UCCW (not used yet), Light Manager (changed LED settings slightly) and Fast Reboot.
Could the Light Manager be the problem? I'll go ahead and check those battery stats anyway...
EDIT: Oh, I also recently set up face unlock (stock feature) Should not be a problem though, since it's not an additional app, right?
So, after running on battery for a while I took these. Can you make any sense of it?
EDIT: Wanted to check the stats again after I had on battery for the night and it was dead again. Unfortunately the stats seem to be deleted when the phone restarts (or maybe when it's plugged in).

qpnp-smbcharger-ffffffc00ea20400 wakelock issue

Subject of this thread is listed as a major kernel wake lock at times for me. Anyone know exactly what that is?
Aridon said:
Subject of this thread is listed as a major kernel wake lock at times for me. Anyone know exactly what that is?
Click to expand...
Click to collapse
I just started seeing this wakelock also. I haven't changed anything lately and it just appeared. I hope someone has an answer.
Aridon said:
Subject of this thread is listed as a major kernel wake lock at times for me. Anyone know exactly what that is?
Click to expand...
Click to collapse
I just started getting it since updating to 6.0.1 PN. I switched to AK Synapse and it drastically reduced it, but it is still there. Only info I can find is much older phones. I am using an LED manager...wonder if that could be it. May freeze it this week and see.
murphyjasonc said:
I just started seeing this wakelock also. I haven't changed anything lately and it just appeared. I hope someone has an answer.
Click to expand...
Click to collapse
KennyG123 said:
I just started getting it since updating to 6.0.1 PN. I switched to AK Synapse and it drastically reduced it, but it is still there. Only info I can find is much older phones. I am using an LED manager...wonder if that could be it. May freeze it this week and see.
Click to expand...
Click to collapse
I believe that wakelock is from charging. I don't know why but the device doesn't seem to register as deep sleep with better battery stats when fully charged and then idle but still plugged in. Likely an issue with the program and not the phone.
However if you want to test this simply charge your phone over night. Once it hits 100% it will stop charging at some point and go into sleep mode. The device is still plugged in but won't charge anymore. Device will use power, mine is usually around 95 or 93% when I fire it up and use a little juice in the morning. During this time the device uses battery quickly until it drops to 89% or so then normal discharge rate. This is normal of most android devices I've had and most everyone here is aware of this:
http://phandroid.com/2010/12/25/you...is-lying-to-you-and-its-not-such-a-bad-thing/
Getting back to the wakelock issue, f you check better battery stats this wakelock shows up under the above condition. You'll notice the time on this wakelock is usually the sum of the device on but screen off time and your screen on usage or pretty close to it.
Now charge your device to full while waiting for it (as in not going to leave it for 4+ hours on the charger after it is full). Once it stops charging at 100% pull the device. Use as normally.
Now the device is fully charged. Really this time and not just the UI telling you it's full. When you use it throughout your day and then check better battery stats you'll notice the wakelock is no longer there or nearly so depending on how fast you got the device off the charger after it was full.
End result is this seems like a reporting issue with better battery stats or the device not fully going into deep sleep while being plugged in. I would tend to lean on a reporting issue as discharge time seems about normal at 1% or so per hour while idle and that tends to hold true to my regular doze discharge.
TLDR:
This seems more like a reporting issue than actual wakelock. Any significant battery drain when fully charged can be explained by the link above and testing as I have explained in the post.
Aridon said:
I believe that wakelock is from charging. I don't know why but the device doesn't seem to register as deep sleep with better battery stats when fully charged and then idle but still plugged in. Likely an issue with the program and not the phone.
However if you want to test this simply charge your phone over night. Once it hits 100% it will stop charging at some point and go into sleep mode. The device is still plugged in but won't charge anymore. Device will use power, mine is usually around 95 or 93% when I fire it up and use a little juice in the morning. During this time the device uses battery quickly until it drops to 89% or so then normal discharge rate. This is normal of most android devices I've had and most everyone here is aware of this:
http://phandroid.com/2010/12/25/you...is-lying-to-you-and-its-not-such-a-bad-thing/
Getting back to the wakelock issue, f you check better battery stats this wakelock shows up under the above condition. You'll notice the time on this wakelock is usually the sum of the device on but screen off time and your screen on usage or pretty close to it.
Now charge your device to full while waiting for it (as in not going to leave it for 4+ hours on the charger after it is full). Once it stops charging at 100% pull the device. Use as normally.
Now the device is fully charged. Really this time and not just the UI telling you it's full. When you use it throughout your day and then check better battery stats you'll notice the wakelock is no longer there or nearly so depending on how fast you got the device off the charger after it was full.
End result is this seems like a reporting issue with better battery stats or the device not fully going into deep sleep while being plugged in. I would tend to lean on a reporting issue as discharge time seems about normal at 1% or so per hour while idle and that tends to hold true to my regular doze discharge.
TLDR:
This seems more like a reporting issue than actual wakelock. Any significant battery drain when fully charged can be explained by the link above and testing as I have explained in the post.
Click to expand...
Click to collapse
The only thing is this wakelock doesn't start until after I unplug it and leave for work. It grows during the day..so is it faulty reporting? Something is using my phone when idle for about 2 hours a day with screen and sync off at 384 Mhz and that wakelock usually shows at about an hour and 10 minutes or so. I have also done as you said and after it dropped to 97% charged it back up and pulled it off immediately..same wakelock and similar time. Also this wakelock was not there with 6.0.0. So Google changed something with 6.0.1 that brought this to life for me. Also interestingly, this wakelock was at about 4-6 hours with stock kernel. I changed to AK kernel and that is what made it drop to about an hour and doubled my standby time.
OK, I froze Light Manager with TB and this wakelock went away. This was the only new thing I added to 6.0.1 to get the battery fully charged light to not change until 100%. Stock changes it at 90% for some stupid reason. So if anyone is using an LED manager, try removing it for a day and see if that makes this wakelock go away.
so here is the source. Are you guys all using the stock charger that came with the device? Only reason I ask is because I didn't start seeing this until I started using a samsung charger with a micro to c adapter.... I think
Reported at 93% it's my highest wakelock. Stock charger and no LED manager installed. Other causes or fixes?
I too have this at the top of my wakelocks. Did anyone else find a solution? I don't have any led managers
Same issue for Lenovo p2
Same issue with Lenovo p2. Anyone has any solution for this?
https://forums.lenovo.com/t5/P2-P2a...t-keep-awake-quot-after-charging/td-p/3861495
Exact same problem here... any luck guys?
HTC 10 (Stock Australian Variant - 7.0)
I contacted Lenovo support on email. As usual they told me to do FACTORY RESET. I did factory reset but eventually after couple of days issue started again.
there is some issue with SMB1351 chip on motherboard of Lenovo P2. but they are not able to figure it out. In battery stat, there is no issue with any of the apps which i installed on my phone.
any help on this is greatly appreciated.....

Battery drain ~15% per hour on standby

Hi,
I'm running CM 12.1 over S4 I9500 intl. and witnessing some battery issues - about 15% per hour with the phone doing nothing.
1) Deleted sucking apps, leaving only whatsapp.
2) Tried a different battery with same results.
3) Bluetooth/WIFI/GPS turned off, auto brightness is on

Here are some screenshots with some battery stats / wakelock detectors:
imgur.com/a/JUmLF

Can you find something abnormal?

Thanks a lot.
shayks21 said:
Hi,
I'm running CM 12.1 over S4 I9500 intl. and witnessing some battery issues - about 15% per hour with the phone doing nothing.
1) Deleted sucking apps, leaving only whatsapp.
2) Tried a different battery with same results.
3) Bluetooth/WIFI/GPS turned off, auto brightness is on

Here are some screenshots with some battery stats / wakelock detectors:
imgur.com/a/JUmLF

Can you find something abnormal?

Thanks a lot.
Click to expand...
Click to collapse
The screenshots are useless because you took them with your battery at 85%. Based on this screenshots I don't see any drain. You need to take them when the battery is almost empty.
Install BetterBatteryStats.
you have link to download this?
You could google it yourself, it's not like it's a secret app or something. But here: forum.xda-developers.com/showthread.php?t=1179809
shayks21 said:
Hi,
I'm running CM 12.1 over S4 I9500 intl. and witnessing some battery issues - about 15% per hour with the phone doing nothing.
1) Deleted sucking apps, leaving only whatsapp.
2) Tried a different battery with same results.
3) Bluetooth/WIFI/GPS turned off, auto brightness is on

Here are some screenshots with some battery stats / wakelock detectors:
imgur.com/a/JUmLF

Can you find something abnormal?

Thanks a lot.
Click to expand...
Click to collapse
Download wakelock detector and check for kernel wakelocks and other wakelocks.
Try focusing on them.
Plus download CPU SPY app and see if at all your phone us going on the deep sleep mode.
If not..download some battery saving app and force deep sleep it or download Kernel Tuner and underclock your cpu to 250-1200mhz and put cpu 2 and cpu 3 on the offline mode.
Then revert.
Hey guys thanks for the replies.
I posted all screenshots from BetterBatteryStats, Wakelock Detector. please check the initial post.
Thanks
I too had the same issue. In my case the phone application was sucking all the battery juice and the phone was turning very hot. I force ended it and the issue was solved.

Phone won't enter deep sleep....

Setup: running latest stock image (mhc19i). Rooted, xposed, ElementalX kernel with ghost pepper script, and I run naptime with aggressive Doze.
Issue: fell asleep with my phone around 50% battery remaining. Woke up seven hours later and it had 30 something. I typically don't see more than 1-2% idle drain over night so this got my attention. I checked better battery stats and I obviously have a wakelock issue. Not sure what it could be. Powermanagerservice was running at something ridiculously high, like 96%. Audiomix is the other wakelock running rampid. See screenshots below. Any input appreciated!
Pain-N-Panic said:
Setup: running latest stock image (mhc19i). Rooted, xposed, ElementalX kernel with ghost pepper script, and I run naptime with aggressive Doze.
Issue: fell asleep with my phone around 50% battery remaining. Woke up seven hours later and it had 30 something. I typically don't see more than 1-2% idle drain over night so this got my attention. I checked better battery stats and I obviously have a wakelock issue. Not sure what it could be. Powermanagerservice was running at something ridiculously high, like 96%. Audiomix is the other wakelock running rampid. See screenshots below. Any input appreciated!
Click to expand...
Click to collapse
Have you tried rebooting and then monitoring it to see if it happens again? It could just be a one-time bug, you'd need to reboot to confirm that though.
I was thinking that as well. I did recently reboot. I'm going to accumulate a good amount of up time and then check the stats again. As of now, battery drain seems to be normal.
Something is still keeping my phone awake while the screen is off...
Pain-N-Panic said:
Something is still keeping my phone awake while the screen is off...
Click to expand...
Click to collapse
I've seen this Audio Mix wakelock happen before on the OnePlus One, from memory I think it was kernel related, so switching kernels might be worth a try. You could also try using Wakelock Detector to see if it'll shed any more light on it, maybe it's an app rather than the kernel.
Hmm....think I solved my issue. I got audiomix wakelock to completely disappear. Simply going into settings and turning off all notification sounds did the trick. For me it's not an issue, however, for others who don't constantly keep their device on vibrate I could see this being a massive dilemma. I'm assuming "powermanagerservice" is a normal wakelock to observe?
Pain-N-Panic said:
Hmm....think I solved my issue. I got audiomix wakelock to completely disappear. Simply going into settings and turning off all notification sounds did the trick. For me it's not an issue, however, for others who don't constantly keep their device on vibrate I could see this being a massive dilemma. I'm assuming "powermanagerservice" is a normal wakelock to observe?
Click to expand...
Click to collapse
Yes, powermanagerservice is perfectly normal for when the phone is in use (or some background operation is running). You'll see it roughly correlates with your screen-on time.
I recently decided to check the huge battery drain during night and I found out that my phone would not go in deep sleep. Can anyone please help with that? Also, the 'jio' app I have been using was installed 50 days back and the battery drain similar before that too. Would be really great if I could find a solution for the deep sleep issue. I am trying to load the screenshots of betterbatterystats but not able to.
vikalp4jain said:
I recently decided to check the huge battery drain during night and I found out that my phone would not go in deep sleep. Can anyone please help with that? Also, the 'jio' app I have been using was installed 50 days back and the battery drain similar before that too. Would be really great if I could find a solution for the deep sleep issue. I am trying to load the screenshots of betterbatterystats but not able to.
Click to expand...
Click to collapse
Use gsam form the play store to find out what app is keeping your phone awake.
Uninstall said app.

workaround for 70000.ssusb wakelock power drain

I was having heavy power drain due to the 70000.ssusb kernel wakelock. I tried almost everything from flashing my ROM to replacing the battery to replacing the motherboard and nothing helped.
I've found a workaround to it though (a fellow user had posted it on some thread).
If you're facing power drain due to this wakelock, buy an otg adapter and connect it to your phone, without a pendrive. This fixed the issue.
I used have less than 3 hours of SoT but now it's 6 hours.
You can also root your phone and change some otg settings to fix it, but this is a safe workaround without root.
A lot of people are facing this issue, so thought I'd post this.
Screenshots for reference.
AkCullen said:
I was having heavy power drain due to the 70000.ssusb kernel wakelock. I tried almost everything from flashing my ROM to replacing the battery to replacing the motherboard and nothing helped.
I've found a workaround to it though (a fellow user had posted it on some thread).
If you're facing power drain due to this wakelock, buy an otg adapter and connect it to your phone, without a pendrive. This fixed the issue.
I used have less than 3 hours of SoT but now it's 6 hours.
You can also root your phone and change some otg settings to fix it, but this is a safe workaround without root.
A lot of people are facing this issue, so thought I'd post this.
Screenshots for reference.
Click to expand...
Click to collapse
Did you get your USB ports changed in the service center?
Nah they wouldn't get it changed saying they're perfectly fine.
I used to have it on 8.0, but during some updates and patches it disappeared.
I think the problem is in the port, I have reasons to believe mine has water damage.
Don't have a otg adapter but disabling USB host via software does the trick to stop this wakelock.
Echo Y /sys/module/dwc3_msm/parameters/disable_host_mode
Sent from my Mi A1 using Tapatalk
fburgos said:
I think the problem is in the port, I have reasons to believe mine has water damage.
Don't have a otg adapter but disabling USB host via software does the trick to stop this wakelock.
Echo Y /sys/module/dwc3_msm/parameters/disable_host_mode
Click to expand...
Click to collapse
Can you let me know how to do this? Does this require root
I have this wakelock too! BUT!
I flashed yesterday Mint kernel, left the phone for 8 hours from 100% charge, came back and battery was at 99%. Phone was in deep sleep 99% of the time. Still have this wakelock but I guess mint kernel does something to prevent battery drain. On stock kernel it was draining battery about 20% in a period of 8 hours
AkCullen said:
Can you let me know how to do this? Does this require root
Click to expand...
Click to collapse
Yes always root is required to modify system files.
Open terminal emulator execute su, then paste the command and execute
Sent from my Mi A1 using Tapatalk
After few days of researching and testing, this 7000000.ssusb wakelock has nothing to do with battery drain, at least in my case. And it does NOT prevent my phone to go into sleep. One time wakelock count was about 4000, and phone was Awake (Screen Off) only 1-2 minutes. Battery did not drain at all during the 8 hour test.
Airplane mode ON = No drain
Airplane mode OFF - Removed SIM cards - wifi ON = Drained ~15% overnight
Airplane mode ON - wifi enabled = Drain ~15% overnight
Airplane mode OFF - wifi disabled = Drain 1% overnight.
All this time 7000000.ssusb ''wakelock'' was present.
I suspect that wireless router is causing drain overnight or something related to wireless network.
I got this wakelock too. But in my case this wakelock occured after I flashed stock rom (july update) via MiFlashTool because my rom wont boot properly after installing custom rom (like wont boot after restarting, bootlooping). I've tried with flashed 8.1 stock rom and with any custom rom + kernel that I know have a good deep sleep (LR + Project K v16, this gave me 1% overnight drain with wifi and mobile data on earlier) but still it drains me like 20% over night. I'm googling here and there, someone posted that he can get rid of this problem by following restore imei guide but he said that we shouldn't following that guide if we are not messing with our imei or we are not losing our imei, so I'm afraid to do that. I'm still wondering why reflashing stock rom make a new wakelock problem that we really didn't want.
Hello guys, the only solution i found it´s using the metaphoenix kernel. Its the only kernel where my phone can go to deep sleep and not having wakelocks we are all suffering. i dont know what does the kernel do but with other kernel in idle/hour i had 3-4% and with metaphoenix i get 0.6-0.8% idle/hour. i hope this helps you out.
Greetings
I finally solved my drain issue and it was not 7000000.ssusb related, even if this ''wakelock'' is still present my phone goes into deep sleep well with only 0%-1% drain overnight (8 hour period). Also my SOT increased drastically, from 5 hours to almost 10 hours (Custom ROM and kernel, from 100% to 1%) Now i charge my phone every second day! :highfive:
I bought Xiaomi Mi Wifi 3C router. Drain from 15%-20% dropped to 0%-1%. Tried 2 routers before Xiaomi router and both caused battery drain during idle (routers were cheap and old - Netis and TP-Link).
So before assuming this wakelock is the cause for drain, please consider checking other things.
Turn OFF wifi during the night, if battery drain reduces drastically then consider replacing router (assuming you checked for other symptoms that can cause drain)
I also have NETLINK wakelock, but drain is still 0%-1% in the 8 hour period.
AkCullen said:
I was having heavy power drain due to the 70000.ssusb kernel wakelock. I tried almost everything from flashing my ROM to replacing the battery to replacing the motherboard and nothing helped.
I've found a workaround to it though (a fellow user had posted it on some thread).
If you're facing power drain due to this wakelock, buy an otg adapter and connect it to your phone, without a pendrive. This fixed the issue.
I used have less than 3 hours of SoT but now it's 6 hours.
You can also root your phone and change some otg settings to fix it, but this is a safe workaround without root.
A lot of people are facing this issue, so thought I'd post this.
Screenshots for reference.
Click to expand...
Click to collapse
That was me who got that work around. But there has to be a permanent fix. And i dropped my phone with otg attached and broke the otg. Lol. Now back to battery drain again.
fburgos said:
I think the problem is in the port, I have reasons to believe mine has water damage.
Don't have a otg adapter but disabling USB host via software does the trick to stop this wakelock.
Echo Y /sys/module/dwc3_msm/parameters/disable_host_mode
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
New problem arises now. The new LOS based on 4.9 kernel does not have this path. No such file can be found.

Categories

Resources