Device: Galaxy S3 i9300. Cyanogenmod 10.2. Googy Max kernel 1.8.0.
Suddenly that wakelock appears in BBS, and Wakelock detector. CPU keeps in 200 MHz, never go to deep sleep.
Didn't change anything this last couple of days, apps nor configuration nor any.
Google it and the info is confused to me, many technical stuff and weird code things.
In one old XDA thread someone fixed this very problem changing the SIM card for a new one. Didn't work for me.
Sometimes rebooting the phone solves everything, but then after a while thÃs battery eater wakelock pops up and brings devastation with it.
Please, some help with this will be appreciate
Related
Hello
I've been reading about the event log service wakelock but i still can't find an answer for that, some people are freezing apps that i don't have. My phone is currently running under the stock rom + faux kernel and i have like 3 apps, that's all, i only use it as a music player, all the time is in airplane mode.
Do you know something related to the issue?
Another problem is, when using wifi, the processors stucks at 256 MHz and that drains battery as hel l, i can't find an answer for that D:
In the screenshot the problem seemed to be not as bad, but sometimes that wakelock is the number 1 partial wake and runs for hours
Greetings,
I had been using my Xperia Neo V with Cyanogenmod 10 (10-20130519-NIGHTLY-haida) for the last 2 months. It was all ponies and rainbows for me for the first 6-7 weeks.
Issue:
Now I'm facing with a random and ridiculous overnight battery drain issue since a week ago. Ridiculousness here is being referred to the amount of the drain (almost 60% overnight) and to the fact that there's no particular change of use of the phone by me,comparing with the days before. As you can see in the screenshots, the main actor here is "Operating System". I don't really know what this drain is related to, so I was not able to do comparisons of use.
Facts:
-Mobile Data was active but only at 2G
-Location services were off
-Bluetooth and all other possible signals were off
-No active apps, all were hibernated with Greenify
What might be the reason of this problem and what would you advice me to try?
Thanks in advance.
what kernel are you using? overclocked?
maybe you can try re-flash the rom
60% overnight is way high battery drain
You should try to see a pattern. Does it happen after specific usage "ritual" or just purely random?
It may be kernel bug/core system bug. Try dumping dmesg and logcat when it happen next.
I would start by trying to flash other kernel.
Install BetterBatteryStats (ther's an SDA thread); It will give you better info of what is draining your battery. In addition to that, you can post your logs in the thread (BBS thread) and they will provide better help.
Good luck
Edit: here's the link http://forum.xda-developers.com/showthread.php?t=1179809
Install wakelock detector app uninstall those... Try greenify too
Firstly we have to know what kernel are you using...
2.6.32.9 or 3.x.x version?
Hi there all, thank you for replies, and here are some extra info;
Fresh facts:
- Kernel: 2.6.32.9-FXP [email protected] #1
- Not overclocked
New observations:
So far I don't see any pattern as to what could possibly be the reason for this issue.
The last time I faced with this, the phone was fully charged and on 2G mode I left it on my desk (my wi-fi router was located next to it, keep it in mind so that it might be a clue coinciding with the BetterBattery logs I will reveal next) and after 3 hours, when I went to check if there were any calls, nearly 30% was drained. Comparing with the initial drain issue (which is a 60'ish% drain overnight) I can say it's the same issue within a proportionate period.
Well takin' a quick look at the BetterBatteryStatus report, drain was mainly caused by some wake thingy called "rx_wake". I don't really know much about all these wake calls in Android system but I googled it and reached to a brief conclusion that it's somehow related with Wi-fi connection. So I'm suspicious that maybe my Android system is perpetually sending wake calls related to a Wi-fi signal even when the Wi-fi mode is off on my phone (only relation I could make here is that I left the phone next to my wi-fi router)
I attach the screenshot and BetterBatteryStatus logs to this post, thanks in advance for your further comments.
Further comments, anyone?
Post the logs in BBS thread. There people has more knowledge and they can help you.
Issue Solved on Galaxy S - Will fit all I assume
Hi
I face the same issue from the day I install the ROM (CM 10.1.2)
I browse the Internet and found the issue
The issue is Wi-Fi and mobile network location
When it is on in this version it turn on the Wi-Fi not only on GPS request and No GPS status
You need to shout it down and issue solved
To change this setting:
System Settings -> Location access and disable the "Wi-Fi mobile network location"
Nachum
Greetings all!
I have done a lot of searches about this, and all the forum post either run dead or get solutions that does not work for me. I finally decided to see if anyone can help me here. I have the Galaxy S2 GT-I9100.
My problem is wakelocks called suspend_backoff and mmc1_detect (and some other, but those two have been persistent).
I have tried a LOT of options.
-Change rom: Used to have the stock rom 4.1.2, now I have the NeatRom Lite, both giving me the same problem.
-I have done a factory reset.
-I have taken out the battery, waited a bit and put the battery back.
-I do not have chrome on my phone (just the stock internet browser, and it does not have the tilt option)
-I have installed Rescan Media Root for in-case it is that.
-Set my phone on static IP.
-Set wifi to "Never" when sleep.
-Someone suggested that the network constantly sends data to the phone or ping it. So far I have not find anything like that (one reason being that all the computers are off at night) and in the router settings I can't find anything that would be causing this.
.....
[Will add more as I remember what else I have tried]
My phone is currently at 60% battery... it will probably be at 20% in the morning, if I am lucky.
Do anyone know anything else I can try? Maybe something with the network? I am running out of options and really getting annoyed with this problem... my phone has basically become a paper weight currently.
Please let me know if there is more info I should post.
Attached is an image of wakelocks I got with GSam Battery Monitor... Wakelock Detector shows the same.
Still no luck
Well I still not having any luck. Have had my phone off for a day now as there has been no use putting it on just for it to die soon again.... or keep it on charge all the time. :crying:
Anyone has any idea what else I can try. Seems like a lot of people is affected by these wake locks, but no solution has helped me so far.
Install BetterBatteryStats (search for it on here/Google Play), let the phone run for a couple of hours, then find the BetterBatteryStats thread on here & post to it/post your logs. People who hang around that thread should be able to help you.
Ok, this has gone past creepy
I got myself I9300, did all the necessary:
Root, ODIN > Philz, wipe, install rom
I installed PA for i9300, which was nice but battery drain was immediate problem so I just thought it was a bad/unfinished ROM. I then installed Resurrection remix which seemed like really neat and complete ROM only to experience the SAME problem - standby battery drain.
I then started searching for the problem cause. BetterBatteryStats says:
partial wakelocks -
SystemUpdateService on par with Awake. it is ALWAYS on
googled it, here is the problem:
People reporting it on 4.3, making constant wakelock, disallowing the phone to go in deep sleep once it is locked. And it was actually fixed in 4.4 CM and CM based roms (resurrection is one of them) but mine is running still.
I then started searching for the solutions, even though my OS version shouldnt do that. One of them says -
You should disable the service via apps "service diasble" or "Autorun Manager" from Play store in order to stop it. So I download both and the service is actually unticked. Shouldnt run at all. but it is still there destroying my battery. Next thing I found on CM forums says:
"wakelock is disabled by devs so that users wont experience constant OTA updates, and while it is disabled, it still runs (nice logic over here) and enabling it stops the wakelocks"
I then tick it to "enable" via those mentioned apps, but the wakelocks are STILL there, phone wont go to Deep Sleep
Extremely annoyed, I went to Settings>Apps>All and disabled the whole "Google services framework" which containts "SystemUpdateService" and there you go -
it still runs, wakelock on par with awake time ....
Is this God-mode service, is this some magic ? What the F is going on, and why do I even experience this when the problem was solved in 4.4 .. ? Please help me.
Hello,
I have a new BQ aquaris M10, which is flashed to latest android firmware with official tools from the ubuntu version (it's not usable for me yet)...
The problem that I have is MASSIVE lag when wake from deep sleep... at least I guess that's the problem. If tab has been inactive for more than say 30 min it takes about a 1 to 1.5 minutes to wake the screen after pressing the power button. After that it works perfectly.
No idea where to go from here... there' doesn't seem to be any relevant battery drain or such. GSAM battery monitor shows some 30% bat used by apps rest by hardware with screen on top. I have something like 1,8% per hour usage while mostly in standby.
Any help is appreciated.
Just a little update.. After installing the wakelock app and putting it in the partial wakelock mode the problem disappeared entirely.
I've seen some posts with nexus users reporting similar freeze when entering deep sleep after update to Android 5.1
Anyone has any experience or advice?
I flashed mine to bq's Android ROM but ultimately decided I'd rather go back to experimenting with Ubuntu Touch than use an outdated, Google-saturated version of Android. If only there were a Google-free, up-to-date, 3rd party ROM for this thing.