Sorry for posting another AlarmManager wakelock thread, but I have spent quite a lot of time reading through the other threads with no luck. The problem is, I am a complete newbie when it comes to smartphones and computers. I do not understand how to run adb, get alarmmanager dump files etc etc.
Main threads I tried:
http://forum.xda-developers.com/showthread.php?t=1179809 (Better Battery Stats)
http://forum.xda-developers.com/showthread.php?t=1684932
http://forum.xda-developers.com/showthread.php?t=1212671
And many many more. Please note I didn't know any of the steps below when I started trying to fix this, so there might be some steps I included which will seem ridiculously stupid and obvious for most of you reading this...
What I have done so far:
1. Downloaded BetterBatteryStats, left it running overnight, and got the results:
http://forum.xda-developers.com/attachment.php?attachmentid=1349107&stc=1&d=1348437812
2. Tried to run adb as per one of the threads here. It said run this code...
Code:
adb shell dumpsys alarm > AlarmManager.txt
3. Installed Android SDK as per this video http://www.youtube.com/watch?v=MVXX-YdhRU0
4. Ran adb on cmd, and when I type adb, a bunch of text appears (which Im guessing means it's installed properly)
5. I connected my phone to computer. Also made sure my device is connected by updating drivers, enabling usb debugging mode, etc as per this site http://stackoverflow.com/questions/9899584/enable-usb-debugging-on-android. Typed in "adb devices" on cmd, and it shows a long string of numbers and charactes, followed by the word "device". (I am guessing this means my phone is connected)
6. Ran the code on step 2. Nothing happens. The cmd window just goes to next line. No error message or anything, but there is no alarmdump.txt file on my /sdcard drive.
7. Tried running the corresponding code on GScript Lite as per one of the threads here.
- If I disable "needs su", it autocloses after 20 secs and says "permission denial: can't dump alarmmanager..."
- If I enable "needs su", it just stays there without closing for a long time. Nothing happens
At this point, I have spent about 5 hours looking at threads from everywhere with no results. I would appreciate any help at all with this issue
PS: My phone is unrooted. I wouldn't even know how to begin rooting...
PSS: In the BBS dump file, it also says wifi was turned on for 2h. (I woke up and it was turned on). But I am definitely sure I turned it off when I slept. Maybe AlarmManager is not actually the problem? Rather some app that turns on wifi?
nothing seems unusual on your dump except go locker maybe...when the screenturns on whats on it?some msg?or just lights up then goes dim again?
skivnit said:
nothing seems unusual on your dump except go locker maybe...when the screenturns on whats on it?some msg?or just lights up then goes dim again?
Click to expand...
Click to collapse
Thank you for your reply
Yes, it just lights up and goes dim. There's no message or notification or anything.
Is AlarmManager not unusual? The count says 1423, which I am guessing means it woke the screen up 1423 times overnight?
If its not AlarmManager that is the problem, maybe I will change the thread title then.
Another fact that I forgot to add in is wifi seems to have been turned on for 2h overnight. But I was sleeping the whole time :S So I am not sure how that happened. I will add this in the original post also...
I will also create another bbs dump to see if anything changes
noobguy1234 said:
Thank you for your reply
Yes, it just lights up and goes dim. There's no message or notification or anything.
Is AlarmManager not unusual? The count says 1423, which I am guessing means it woke the screen up 1423 times overnight?
If its not AlarmManager that is the problem, maybe I will change the thread title then.
Another fact that I forgot to add in is wifi seems to have been turned on for 2h overnight. But I was sleeping the whole time :S So I am not sure how that happened. I will add this in the original post also...
I will also create another bbs dump to see if anything changes
Click to expand...
Click to collapse
AlarmManager does not mean the screen woke up 1423 lol, that would be crazy. What it does mean is things are running in the background. For example, Beautiful Widgets will set off an alarm to refresh the weather every 3 hours in my case. Android will set off its own alarm to turn on the led each time you get a message or whatsapp etc. Almost every app has an alarm tied to it so Alarm Manager will always be pretty high. Your screen turning on randomly......I have no idea. I would do a full data wipe and see if it keeps happening. Must be an app causing it to happen
Try un installing go locker see if that still happens
Sent from my GT-I9300
Related
Hi everyone,
I've done very much try and erroring to find out which app is draining my battery and if it's really neccessary.
As you can see on the attachment, it looks really nice already. The only thing which drives me crazy are those long and often "Aktiv" (Awake) parts. I couldn't find any information on the SDK pages.
My Phone seems to be very often Awake while in standby. I can't understand why it has to wake up that often. Am I right, that this "Awake" means, that the cpu is running (not in sleep mode)?
Is there any way to log which software is waking the device up?
Greetings
Chris
Yep, "awake" means that cpu is running. Try Badass Battery Monitor, it has a list called AppSucker, that lists the apps by battery consumption
Thanks. That is exacly what I was looking for.
Now I'm still sure, that there is somethink wrong with the battery consumtion. As you can see on the attachment, "Android-System" takes 2 hours(!) for some stupid things.
These are the datas for one night (it was a short one ) The phone wasn't used at all. Is that normal? I mean, thats nearly 30% of the time. Okay, the total capacity loss seems okey, but the phone hast absolutly nothing to do. Except for some interrupts of from the baseband and some cronjobs maybe. But that doesn't need 2 hours.
Any suggestions what courses these long awake times? Or another way to debug this?
Thanks
Chris
Android-system, huh? Seems like you have a wrong config, or a service is keeping awake the CPU...
Sorry, I dunno other way to debug it, but you already tried to calibrate your battery? (let that your battery runs out, charge it fully and, without unplug the charger, go to Recovery >Advanced >wipe battery stats. Unplug and reboot).
Yep, that was the first ding I did.
I'm running IceColdSandwich - 7.4 - AOKP STRIPPER EDITION. Maybe this is some kind of bug.
Maybe someone have another idea how I can debug this. Nevertheless thanks for helping.
You should check to see if Sync is turned on. This will cause the phone to wake up to contact any accounts you have set up to sync... I would suggest setting sync to off unless wifi is available.
On my rom (Gingerbread base) the wifi is turned of when the screen is off, which will make sure that google will never try to sync while the phone is idle.. The downside you will have to wake the phone in order to receive emails and stuff via wifi, and if not on wifi you will have to check your email manually.
I think I found it. Badass Battery Monitor showed that "Google Backup Transport" is part of Android-System, so I removed it. I didn't use it anyway.
My phone is not crashing, I still runs smoothly. The keep-awake time shrinked to 30m during 7h (including short uses). That seems totally legit for me.
Thanks for helping
Chris
Hello to all and thanks for your time.
First of all i did search about such a thread and could not find any which seemed to help including the stickies.
My problem is something on my room is misbehaving and chews trough the battery like hell.i need help identifying it.
To id my system :I'm on 9100xxlpw stock rooted no additional battery managers.
to describe the problem. I charged the phone to 100% and 5 hours later it was 50%.(i was sleeping so they're was no usage)
CPU spy reports 30 min of deep sleep rest 200mghz.
I'll add battery stats later.but basically Android system is chewing the batt. System appears to sleep but doesn't go deep sleep
Sent from my GT-I9100 using XDA
Install BetterBatteryStats. That should give you some clues as to what's causing the drain.
MistahBungle said:
Install BetterBatteryStats. That should give you some clues as to what's causing the drain.
Click to expand...
Click to collapse
Added Screen shots, please ignore media player and usb. I took screen shots as soon as I notice strange stuff but somehow system showed the screen shots duplicated so I deleted duplicates. Later I noticed I deleted the originals (most probably there was one c to begin with but gallery showed me duplicates, which is strange ).
New ones are taken after apprx. 1 hour of XDA browsing & listening to music.
emk2z said:
Added Screen shots, please ignore media player and usb. I took screen shots as soon as I notice strange stuff but somehow system showed the screen shots duplicated so I deleted duplicates. Later I noticed I deleted the originals (most probably there was one c to begin with but gallery showed me duplicates, which is strange ).
New ones are taken after apprx. 1 hour of XDA browsing & listening to music.
Click to expand...
Click to collapse
open BBS app then press soft menu key ones then select more and in that press Dump to file
then u see the log file in ur internal sdcard, post the same so that it can be checked to determine the wakelocks causing batt drain
Sun90 said:
open BBS app then press soft menu key ones then select more and in that press Dump to file
then u see the log file in ur internal sdcard, post the same so that it can be checked to determine the wakelocks causing batt drain
Click to expand...
Click to collapse
Gladly....
I think I have a possible culprit while searching for suspend_backoff
I found this http://forum.xda-developers.com/showthread.php?t=1697899 the phone model is different but I decided to turn wifi off to test and my battery consumption is almost like flat line when I'm not using the phone now (Data & synch is still enabled ). I do not know what causes this but I am not trough yet. I'd appreciate anyone to ID the source of the problem and how to overcome it (other than keeping wifi off) or should I switch to another rom
I have the same problem as you, but I think it is related to the (known and not yet solved) problem of the "dirty WiFi network", as it happens only with my office WiFi and not with my home one...
However in my case the problem is intermittent, while I always have the same high drain under the office WiFi, the major source of drainage changes, sometimes is suspend_backoff, other times it's deleted_wake_locks...
The_Flatline said:
I have the same problem as you, but I think it is related to the (known and not yet solved) problem of the "dirty WiFi network", as it happens only with my office WiFi and not with my home one...
However in my case the problem is intermittent, while I always have the same high drain under the office WiFi, the major source of drainage changes, sometimes is suspend_backoff, other times it's deleted_wake_locks...
Click to expand...
Click to collapse
I also had a feeling it might be wifi. I'm not sure what you mean by dirty wifi but. My home network seems to be suffering from dns problems. Also when I go to work one of my customers has a proxy while other has a unprotected wifi with web login. in both cases phone is able to connect to wifi but not to internet.
I also considered this might create some drain but it is too severe. I even thought my phone battery to be dead.
as the title says im having trouble with battery drain due to AudioOut_2 wakelocks but im not sure if this is really whats causing my drain. il upload my logs from betterbatterystats since im not an expert on really understanding the logs it generates. hope somebody can give me a clear explanation on my problem. because im getting paranoid over this. lol
skylinerr34j said:
as the title says im having trouble with battery drain due to AudioOut_2 wakelocks but im not sure if this is really whats causing my drain. il upload my logs from betterbatterystats since im not an expert on really understanding the logs it generates. hope somebody can give me a clear explanation on my problem. because im getting paranoid over this. lol
Click to expand...
Click to collapse
Do you have touch sounds enabled? I noticed when I have them enabled I get more of an audioout wake lock. I also get it while I play music on my phone.
graffixnyc said:
Do you have touch sounds enabled? I noticed when I have them enabled I get more of an audioout wake lock. I also get it while I play music on my phone.
Click to expand...
Click to collapse
Yes i have it enabled. in fact all the sound settings i have under settings-sound-system are all enabled. il try disabling them all. its just so weird why its having sound wakelocks even if the phone is not being used or the screen off. thanks for your reply.
have same problem too...
Sent from my checkrom jellybean powered sgs 3
Same problem here, and I don't have the sound enabled.
Sent from my GT-I9300 using xda premium
Ausboy 2011 said:
have same problem too...
Sent from my checkrom jellybean powered sgs 3
Click to expand...
Click to collapse
Im aware your using checkrom from your signature but its on jb..i am running omega 27.1 JB..on the nexus 7 forums some guys are having the same problem too..is it because we are all running JB?
Sent from my GT-I9300 using Tapatalk 2
same problem here using omega 27 with all system sounds off
Anyone track down a solution to this yet?
seems to be a jb thing and I spent a bit of time trying to pin down what caused it, but each time I drew a blank, but I got rid of it.....and I have kept my eyes open but I remember GM starting in his kernel thread that even he couldn't pin down what it was.
Apologies for not having a solution, but you can get rid of it
slaphead20 said:
seems to be a jb thing and I spent a bit of time trying to pin down what caused it, but each time I drew a blank, but I got rid of it.....and I have kept my eyes open but I remember GM starting in his kernel thread that even he couldn't pin down what it was.
Apologies for not having a solution, but you can get rid of it
Click to expand...
Click to collapse
Might I inquire as to how you ended up getting rid of it in the end? :fingers-crossed:
NewAussiefromCanada said:
Might I inquire as to how you ended up getting rid of it in the end? :fingers-crossed:
Click to expand...
Click to collapse
that's the thing.....I'm really not sure at all, something in my set up, something I froze with titanium, some sound setting, I really don't know,, I don't use haptic or touch sounds, so that might be linked, but beating in mind if I had tried one thing at a time, then used bbs and let it idle for two hours each time I tried something,I would be at it forever,
I'm dual booting slim and wanamlite, so even more complicated
Sorry to be so vague but I really can't pin it down!
skylinerr34j said:
as the title says im having trouble with battery drain due to AudioOut_2 wakelocks but im not sure if this is really whats causing my drain. il upload my logs from betterbatterystats since im not an expert on really understanding the logs it generates. hope somebody can give me a clear explanation on my problem. because im getting paranoid over this. lol
Click to expand...
Click to collapse
From my testing with my stock rom and communicating with the Dev from Better Battery Stats a month ago or so, I don't believe the statistic AudioOut_1 or AudioOut_2 is the cause for any battery drain. (at least not for me) You see them listed under Partial Wakelocks but the "count" increases every time certain UI sounds are triggered even with the screen ON! So it's a bit misleading...because the OS implies that the counts are increasing during standby.....hence the term Partial Wakelock.
And YES...by disabling Keytones and Touch Sounds etc., the statistic is eliminated and BBS will not show an increase. So basically...I IGNORE THIS STATISTIC...and keep my sounds turned ON!
As a test, I suggest you to disable this feature of the phone (go to Settings - Manage Applications and disavle apps Google Text to Speech and Samsung TTS).
puredesire said:
As a test, I suggest you to disable this feature of the phone (go to Settings - Manage Applications and disavle apps Google Text to Speech and Samsung TTS).
Click to expand...
Click to collapse
Did this work for anyone?
themadproducer said:
From my testing with my stock rom and communicating with the Dev from Better Battery Stats a month ago or so, I don't believe the statistic AudioOut_1 or AudioOut_2 is the cause for any battery drain. (at least not for me) You see them listed under Partial Wakelocks but the "count" increases every time certain UI sounds are triggered even with the screen ON! So it's a bit misleading...because the OS implies that the counts are increasing during standby.....hence the term Partial Wakelock.
And YES...by disabling Keytones and Touch Sounds etc., the statistic is eliminated and BBS will not show an increase. So basically...I IGNORE THIS STATISTIC...and keep my sounds turned ON!
Click to expand...
Click to collapse
See I would agree with you but when you turn and disable everything you have to your phone should be allowed to enter deep sleep. under the partial wakelock the audioOut_2 is the only thing not allowing it to enter thus if you look at all the all the apps you have running and some apps run like the sound is on even with the screen off. My problem was puzzle and dragons would run the sound and drain my battery and when i exit it the audio problem stops. So to answer your question tony just empty your running apps when you get ready to turn your screen off and see if that helps.
Metalshadowx2 said:
See I would agree with you but when you turn and disable everything you have to your phone should be allowed to enter deep sleep. under the partial wakelock the audioOut_2 is the only thing not allowing it to enter thus if you look at all the all the apps you have running and some apps run like the sound is on even with the screen off. My problem was puzzle and dragons would run the sound and drain my battery and when i exit it the audio problem stops. So to answer your question tony just empty your running apps when you get ready to turn your screen off and see if that helps.
Click to expand...
Click to collapse
Same for me. Normally my tablet eats 1 percent of battery max for a screen off hour. Today, I restarted, done a backup, booted the system and then I turned the screen off and went about my bussiness. Now, according to BBS, I have 3,5 percent down per hour. And the only "huge" wakelock is Audioout_2.
michalurban said:
Same for me. Normally my tablet eats 1 percent of battery max for a screen off hour. Today, I restarted, done a backup, booted the system and then I turned the screen off and went about my bussiness. Now, according to BBS, I have 3,5 percent down per hour. And the only "huge" wakelock is Audioout_2.
Click to expand...
Click to collapse
Same problem here on my note 2... last night before sleep time i killed all apps by holding down the home button.BBS clearly showed audio_out2 as the one which has the partial wakelocks... sigh... no solution yet?
on a side note in sound settings im not using sound and vibration. just keyones. screen lock sound and haptic fb.
Same problem here
All touchsounds disabled and AudioOut_2 did not stop to drain my battery. Maybe it's time to switch to BlackBerry Z10.
for those who are having problems with phone not going to sleep, just go to settings - manage apps - and disable the Samsung TTS app (or freeze it with Titanium Backup). At least this fixed the problem here.
cya
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.
Hi all,
I experience problems with kernel wakelock, named "s5p-ehci". In random moment it's getting seized my phone and the phone stops sleeping. It looks like:
all other kernel wakelocks and partial wakelocks take less than 1 min of activity, whereas s5p-ehci is active during hours. So, for instance, if s5p-ehci is active at night - I am loosing about 4% of charge per hour (phone deep sleep time is 0%).
Temporary solution is to reboot the device: so s5p-ehci's activity time is between seconds and minute, later it gets crazy again and is active constantly. I did not succeed to find some relation between it and applications or system processes.
I am not an Android developer, but since there is no other kernel for my device (Meizu MX2) I'm eager to TURN OFF this damned s5p-ehci... Please, tell me, how to do it:
either via build.prop or via linux command or changing some configs.
I have tried to use other firmware, wiped my phone and tried to work without my apps, but all in vain: so I still don't know, WHY this s5p-ehci is on Earth getting so active so long all of the sudden. It has nothing to do with USB, because my phone is not plugged with cable when it happens
Nafiganado said:
Hi all,
I experience problems with kernel wakelock, named "s5p-ehci". In random moment it's getting seized my phone and the phone stops sleeping. It looks like:
all other kernel wakelocks and partial wakelocks take less than 1 min of activity, whereas s5p-ehci is active during hours. So, for instance, if s5p-ehci is active at night - I am loosing about 4% of charge per hour (phone deep sleep time is 0%).
Temporary solution is to reboot the device: so s5p-ehci's activity time is between seconds and minute, later it gets crazy again and is active constantly. I did not succeed to find some relation between it and applications or system processes.
I am not an Android developer, but since there is no other kernel for my device (Meizu MX2) I'm eager to TURN OFF this damned s5p-ehci... Please, tell me, how to do it:
either via build.prop or via linux command or changing some configs.
I have tried to use other firmware, wiped my phone and tried to work without my apps, but all in vain: so I still don't know, WHY this s5p-ehci is on Earth getting so active so long all of the sudden. It has nothing to do with USB, because my phone is not plugged with cable when it happens
Click to expand...
Click to collapse
Since it persistent across different versions of the software, I'm wondering if it is not hardware related, like the USB is shorting out or messed up (yes, I read that it wasn't plugged in during the main issue, but doesn't mean it is not the root cause). Have you tried using https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector to see if maybe it can narrow down the source of your issues?
es0tericcha0s said:
Since it persistent across different versions of the software, I'm wondering if it is not hardware related, like the USB is shorting out or messed up (yes, I read that it wasn't plugged in during the main issue, but doesn't mean it is not the root cause). Have you tried using https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector to see if maybe it can narrow down the source of your issues?
Click to expand...
Click to collapse
Hi,
yes, i've used Wakelock detector app as well as its advanced colleague - BetterBatteryStats. So that's how I've found out about "s5p-ehci" wakelock. And I can see there is no other reason of phone insomnia, besides s5p-ehci.
All other apps and processes consume CPU moderately. When s5p-ehci activity is moderate - phone sleeps well. When it gets berserk and is active during several hours - phone does not sleep at all during whole this time (deep sleep is 0%), instead works on minimal frequency (300MHz), however, it's about 40% of battery draining per night.
If it's a hardware issue - I wonder who can help me with that investigation. Services do not deal with such cases, since there is no permanent problem signs. In my case the process can behave properly during a day. Then, all of a sudden, it's getting active and some its activity lasts hours! Then it's getting back to normal again. I've looked at kernel log and system log. There is a lot of various events happening there: something is going on, then device sent to sleep, then again something is going on, then wakeup, in various cases wakeup reasons are different, I was unable to find some relevant info... I would send this log to anyone who could help me to find source of the problem.
I've rolled back to Android 4.1 firmware and installed custom kernel.
Here situation is better, but what I have discovered:
phone seems not to detect when it's being plugged off from charger - no matter, USB cable from computer or wall socket wire. s5p-ehci does not go away and sucks off my battery. What only helps is manually resetting EHCI power: setting 0 in ehci_power file. As a result, something is reset, ehci power is on again, but this sucker goes away and after that everything is fine until next charge. But I need to find a root of the problem!
Going on investigation - too view info in Internet...