Related
has anyone else noticed that if you go to the battery usage on the S4G it shows the phone as always awake? check the graph. it's really strange!
perhaps this could be linked to some of our heat/battery issues? the phone is not sleeping correctly?
You have a rogue program that isn't shutting down. Now you need to figure out what it is.
When I had this it was VTOK since that program never shut off.
Go to Settings> Applications> Running Services and look at the times that everything has been running and try to figure out which one doesn't belong
HTC watch can be a culprit too
Sent from my HTC Sensation Z710e using XDA App
xnifex said:
You have a rogue program that isn't shutting down. Now you need to figure out what it is.
When I had this it was VTOK since that program never shut off.
Go to Settings> Applications> Running Services and look at the times that everything has been running and try to figure out which one doesn't belong
Click to expand...
Click to collapse
I practically uninstalled every application that had an associated service, disabled everything from startup that I could find and the issue persists.
The only way I can get it to not be always awake is if I disable data completely... not background data, or autosync, but all data. no 3G, no 4G, no Wifi, nothing.
As soon as wifi comes on, I get a "sync" circle in my status bar (despite the fact that all sync is disabled on my phone), and the problem returns. The only active connections are to Google IPs (as shown by a netstat from the terminal), looks like gtalk/market ports...
I'm stumped.
I'm going to update the market, see if that helps.
EDIT: it didn't.
Just an update:
Downloaded ATK from the market, there seems to be a lot running for a phone I just rebooted.
I killed everything one-by-one, none of them made the sync icon go away.
There was only one that I could not kill... Watch.
... it also has a service that will not die either....
but if it's watch, surely someone else out there has the same issue?
HTC watch was the issue with mine, it took some time until i figured it out
Utking said:
HTC watch was the issue with mine, it took some time until i figured it out
Click to expand...
Click to collapse
it was. I disabled the account and rebooted a few times.... I'm good now.
very strange. And for some reason, when someone said "watch" I thought of a clock.... ha. that wasn't any help.
No, the video application. turned out to be the culprit. ffs.
Mystik said:
it was. I disabled the account and rebooted a few times.... I'm good now.
very strange. And for some reason, when someone said "watch" I thought of a clock.... ha. that wasn't any help.
No, the video application. turned out to be the culprit. ffs.
Click to expand...
Click to collapse
great if else you could freeze it with titanium backup
Push notifications while phone is sleeping - are these commonly disabled by default in custom roms as a battery saving feature? I've tried Embryo 5.1, Majick-Wizz R3, and CM10 Alpha (all using the recommended kernels/radios, flashing using CWM Touch 6.0.1.2 v12.5), all seem to have the same "issue" where I don't get push notifications from things like Gmail or third party apps while the phone is sleeping. As soon as I wake the phone, the notifications come in.
I couldn't really find anyone on this forum or anywhere else on this issue, except for cases with the HTC Evo, which leads me to believe it's common knowledge whatever is causing this or how to fix it, but I'm new here and this is escaping me completely...
Thanks for any help!
I get push notifications for my email account all the time, and when I've tested other apps (Facebook, Twitter, news apps, etc.) they've always worked there as well. This is on several ROMs, including MW (all three releases), SkyICS 4.2F6 and CM9.
Are you restoring system data from Tibu, by chance? That's all I can think of from a practical perspective that would carry the problem across ROMs, but I'm not a dev and can't begin to guess at any potentially more difficult solutions.
I actually don't restore any data from anywhere except Google auto settings backup. These are all fresh installs.
Edit to add: the notifications seem to work until the screen has been off for 10+ minutes. Also they worked on stock rom.
Edit2: Looks like it may have to do with the WiFi. Made sure the WiFi policy was set to remain connected while sleeping, but that setting doesn't appear to be working. Disabled WiFi and let phone sleep for 10 mins and sent emails to test, and notifications worked.
Edit3: Tried disabling/enabling the WiFi sleep settings in various ways to see if a setting was stuck somewhere, to no avail... Flashed InstigatorX 6.3.4, no dice. It's definitely the WiFi going to sleep though. Confirmed that if WiFi is turned off, all works well. Also, upon waking the phone, it takes a few seconds for network connectivity to start working again (if WiFi is enabled). How do I get this setting to stick?!
Update: Ok, so I just reflashed with all of the Google backup stuff turned off, and tested, still not working.
I'm really running out of ideas here. It's not that I'm unwilling to try something, I just literally can't think of anything else to try...
EDIT: So I just downloaded an app for which the purpose is to keep WiFi awake at all times, and it happens that the app also checks your WiFi sleep policy setting for you. In my case, it told me that i had WiFi set to disable when the phone is sleeping (despite that not being the case). I suppose this fully confirms that the issue is the setting isn't sticking. I let the app change that setting for me then uninstalled the app, going to test throughout the day tomorrow. In the meantime, is there a relatively harmless way to manually check whatever configuration file holds this policy setting?
So I'm on Liquid pre-RC based on Cm10 now and it seems to be working intermittently. The only way I can get it working consistently so far is installing an app built for this purpose. Am I really the only one experiencing this issue with custom roms?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I don't really have an answer for you, but I can at least tell you that you're not crazy. I have definitely noticed this happen where I will wake up my phone and instantly be hit with email notifications. However, it didn't happen every time like that. And to be honest, I think my push Gmail worked fine; it was my pull email that would do it to me. That was on CM9. I don't think I've noticed it happen since I've been on MW.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Google search seems to be keeping my phone awake and destroying my battery.
Using the GEL, my phone was awake any time my launcher was active. Switching to Nova, it seems this issue is mitigated, however if I ever go to use the search app (or Now), it initiates the battery rape-fest.
Just wondering if anyone else has had this issue. I know lots of people here have their data and/or wifi enabled/connected 24/7, so it may not effect them.
I'm linking photos stored in my DB account showing some of these battery drains.
https://www.dropbox.com/s/jhw1f4prbneyg45/2013-12-26 06.19.30.png
https://www.dropbox.com/s/gfhr2vf1z5kf4tw/2013-12-26 06.19.24.png
https://www.dropbox.com/s/0f506skwf26q3se/2013-11-27 01.43.17.png
https://www.dropbox.com/s/ky7yjo2628p1ngl/2013-11-27 01.43.22.png
https://www.dropbox.com/s/dr0e2jjswt52mce/2013-11-27 01.43.26.png
The periods of no signal is when I'm at work - there's no service out here so I might as well have it on airplane mode.
Unfortunately, I really like the GEL, and was hoping that there'd be an easy fix to this. Switching run times doesn't help. I'm currently on ART.
Any advice is helpful.
Do you have hot word detection on? If so then it off that could be triggering it it solved the issue I had with it
Sent from my Nexus 5 using Tapatalk
Once or twice Search would keep my phone awake and drain the battery. Something to do with toggling some Location settings on or off.
Force stopping the application fixed the issue for me each time once I noticed it on my battery list.
bblzd said:
Once or twice Search would keep my phone awake and drain the battery. Something to do with toggling some Location settings on or off.
Force stopping the application fixed the issue for me each time once I noticed it on my battery list.
Click to expand...
Click to collapse
Hmm I also had this problem and also was tinkering with location settings the other night... interesting. If it starts acting up I'll force stop it.
I wanted to disable or uninstall Google Now and Google search and it wiped my homescreen
kevtrysmoddin said:
Do you have hot word detection on? If so then it off that could be triggering it it solved the issue I had with it
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This was the first thing i thought of. I turned it off, no change.
bblzd said:
Once or twice Search would keep my phone awake and drain the battery. Something to do with toggling some Location settings on or off.
Force stopping the application fixed the issue for me each time once I noticed it on my battery list.
Click to expand...
Click to collapse
My issue is that I shouldn't have to force stop it. Why is it running wild? This is a Google application, shouldn't this be near flawless?
Sent from my Nexus 5 using XDA Premium 4 mobile app
new ion? said:
This was the first thing i thought of. I turned it off, no change.
My issue is that I shouldn't have to force stop it. Why is it running wild? This is a Google application, shouldn't this be near flawless?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just know it's a pretty easy fix (force stop or reboot) so not a huge deal IMO.
If I had to guess Search is trying to look up some location information which it can't currently access. Instead of stopping it just keeps trying forever. I've yet to see the issue since disabling Locations completely and experienced the issue only with partial location services enabled.
My advice would be to leave Location services completely on or completely off. It may effect those with locations on, but either reporting or history (or both) off.
Sent from my Nexus 5 using Tapatalk
Oooo, apparently I had history on and reporting off. I'll try turning both off and letting search run for a bit tomorrow, I'll see what happens. If it comes down to it, I'll submit a bug report.
Sent from my Nexus 5 using Tapatalk
shouldn't be an issue
I have been having the same identical issue as you guys. I have found shockingly little in my searches, which I've been doing periodically for the last few months, really, since I've had the phone(12/5/13).
Now for the particulars :
I have a nexus 5. I'm running the stock ROM and kernel via OTA (4.4.2).
I am rooted (via wugfresh's toolkit) and I have the xposed framework installed along with only a couple of modules, (gravitybox, bootmanager).
Now all this means I am essentially bone stock which means since its a nexus 5 I have the GEL launcher by default and I love it and the setup in general, (my favorite setup so far of all my phones, nexi and other).
Now I've been fortunate and have never really needed to track down and eliminate software causing battery decimating "wakelocks" on any of my devices. And apparently the newer versions of KitKat make finding and solving wake lock issues difficult using apps developed for the purpose.
If I were to upload screenshots of my battery screen when the issue is presenting itself, Google search is up in the top five at least. And when I click it for details it shows similar readouts to what's been posted by OP in his screenshots.
I can't be the only one having serious issues with wakelocks cause by Google search on their nexus 5 and I'm baffled by the lack of discussion I've been able to find regarding this issue, (my google-fu is in my opinion at least up to par)
Whenever I notice my battery draining faster than normal without fail I go into my battery settings and discover that my phone is awake constantly regardless of screen-on time and the culprit is always exclusively Google search. Now its far from difficult to force stop the app and go about my business. And it usually doesn't cause me any issues for a time once that's been done. However, the unpredictability of the Google search app causing a crippling wake lock is for me the main issue as it means I cannot leave my phone unattended for more than a few hours without the possibility of coming back to my phone with my battery that's been molested. The battery in my opinion is more than acceptable and I quite like it. However the uncertainty is horrible.
I've read through the posts In this thread (regrettably few) and I have not been able to make a correlation between location services being on in any of the three modes and Google search wakelocking my ****. Also, I use Google Now all the time every day, and hotword detection is always on to call it up from the home screen by voice which i use even more so. So in my opinion while it is possible I'm sure that somewhere in all that there is a trigger for the issue, it is by no means predictable and in my experience never reproducible.
Now, for the "Google Search" app to cause a wake lock that will persist until the apps been manually force stopped, completely unpredictably represents a HUGE BUG that un-does all of the amazing work with our chipset and kernel and os that gives us such great battery life without having to sacrifice clock speed via custom min/max settings or governor controls.
I just don't get it. This is the first time I've ever encountered such a glaring problem/bug with so little complaint or even discussion.
I think we all should submit official bug- reports to Google about this issue and start being vocal in all of the android communities. I very very rarely comment or post as I am always able to make do by searching and reading diligently. But this blows my mind, the lack of posts and discussion would normally suggest this is a very limited problem affecting a very small minority. But I don't buy that. My set up is too stock, too close to the largest percentage of nexus 5 users to be so. Maybe people are just force stopping the app and forgetting about it, chalking it up to something they've personally done to their phone because "how could Google search be doing this to everyone else". I don't know. But this has to be more widespread of an issue than search results are indicating.
In summation: what OP said lol. But I don't think it has anything to do with what's been suggested by other posters on this thread. Their suggestions may work, and they may mitigate the issue. But if that is the case. Than this a very huge bug that threatens to undo all of the amazing work that's been done with aosp regarding battery efficiency and optimization.
- FerrousState
PS. Let's get some real discussion going in this community and all the others. Smarter people than us should be working on this - Top men guys, TOP MEN!
Hey guys I have this problem as well. I can't view the pics in OP but Google search is running at about 14%
Sent from my Nexus 5 using xda app-developers app
Brockg said:
Hey guys I have this problem as well. I can't view the pics in OP but Google search is running at about 14%
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Tap Google search in your battery and check how long it's kept your phone awake. Then back, and check again. If the seconds just got higher it's currently eating your battery and needs to be force stopped.
Any suggestions are just to mitigate the problem for now of course. Hopefully it's being worked on.
I've yet to see the issue again but I have Locations and Hot Word off, Google Now on. I strongly believe using either "device only" or turning off the 2 settings within Locations can act as a temporary fix however.
Is there a tool or way to test the Nexus 5 sdcard memory?
For the last six months I've had problems with my rooted Nexus 5 (stock kitkat) suddenly running very slow. After a lot of time trying to figure out why, I determined the following.
1. Slowdown happens when an app is writing something to the sdcard.
2. Is not a particular app. Can be any app.
3. When it happens all 4 CPU cores are running close to full blast.
4. Battery usage shows "android os" is 50% of the usage.
5. Task killers do not solve the problem.
6. Reboot restores things to normal for a while.
So I now wonder if there's something wrong with the built in memory but don't know how to test it.
Is there a way to test the Nexus 5 message? It is very frustrating to talk 2-3 pictures and then have the 4th one make everything grind to a stop. Right now, typing this is a pain because every letter takes its time to appear. I know rebooting will solve it but I should not have to.
sounds like you get a process(es) that get "stuck". also, when this happens, have you ever checked if your google stuff is syncing or " stuck"? sometimes badly written apps can cause this to happen as well.
simms22 said:
sounds like you get a process(es) that get "stuck". also, when this happens, have you ever checked if your google stuff is syncing or " stuck"? sometimes badly written apps can cause this to happen as well.
Click to expand...
Click to collapse
I think you are right but I don't know how to find the faulty process. I "think" I first noticed it after the google camera update, but I used settings /apps/ to uninstall the camera update without improvement. I think camera showed the problem because it has to save the image to memory sdcard.
I don't sync and have sync turned off everywhere and on all apps. Sometimes Google play shows up as the prominent battery user even though I don't have it update apps automatically. But it is primarily android os that is the bad guy.
One of the things I had tried when the problem first started was to restore an earlier nandroid backup, but the problem continued, so I restored the most recent nandroid I had done before the earlier restore.
Recent screenshot.
I was on the browser and Tapatalk for a while. But not on play store.
Not frozen now when taking this screenshot.
You need to get gsam, or BBS or wakelock detector and see what one of those says. The stock battery screen is pretty much useless to find a battery problem.
But I'm guessing all your issues are tired to one bad app as said above.
Get a battery app I suggested, run a full charge down with it running.... And comb thru all of it and see if anything pops out.
kj2112 said:
You need to get gsam, or BBS or wakelock detector and see what one of those says. The stock battery screen is pretty much useless to find a battery problem.
But I'm guessing all your issues are tired to one bad app as said above.
Get a battery app I suggested, run a full charge down with it running.... And comb thru all of it and see if anything pops out.
Click to expand...
Click to collapse
I already did that. I have gsam and wakelock detector installed but my knowledge of Android is very limited and they have not helped me so far except to confirm I have a problem. I wonder if there is a way to see the dates I installed various apps. That way I could uninstall in the order they were installed.
Here are various screenshots. The list of active processes goes down several pages.
My guess... It's an app that hadn't been updated since kit kat has been out, and it's spamming location services.
Just a guess.
Check in gsam for times waking device, held awake time and kernel wakelock. (You need gsam root companion from play store installed as well.). These are all found in gsam app screen by clicking the drop down at the top. See if anything looks bad on any of those.
---------- Post added at 05:18 PM ---------- Previous post was at 05:17 PM ----------
Oh, and obviously, whatever tick tick is, is killing your battery. If it accesses location.... that's my bet for the culprit.
Thank you all for the advice. Obviously I've tried various things. TickTick is a todo list app. Quite nice actually. Anyway I had suspected it might be a problem and have uninstalled it (several times) with no improvement.
Finally, I seem to be making some headway. Don't know which of these two did it (if the improvement lasts.....).
1. There were 3-4 apps I had avoided updating because I didn't like the updated versions (maps, Hangouts which I don't use, Firefox, etc). So I now gave up and clicked on "update all".
2. I disabled the module gravitybox and rebooted.
So far things have returned to normal. My CPU cores are back to low levels.
I'm keeping my fingers crossed. If things continue well after a while I will reactivate gravitybox. I'm holding my breath!
After a full 15 minutes of normal behavior (unbelievable!), I took my courage in hand, reactivated gravitybox. Used my usual apps without the previous freezing recurring (so far). If this continues - and it seems to - it might suggest you don't update GAPPS (I think it was Hangouts) only at your peril.
Such a difference having an uncrippled phone!
After a while the slowdowns returned. Any suggestions?
Hey guys, lately I've been having the eventx-xxxx wakelocks that *seem* to keep my phone awake and drain my battery. These wakelocks are usually event0 ones and followed by a four digit number which I believe to be the Process ID.
The current wake lock I am having is event0-2012 shown by BBS. It changes on every so the PIDs are rarely the same. It also happens that the 4 digit number happens to be the process ID of system_server. So there's something that's keeping it awake.
Lastly, the event0 is the synaptics touchscreen. So I'm guessing that this event0 wakelock keeps track of all the touches you make on the screen. This problem only appeared after the new touchscreen firmware updates so that may be the cause. Anyone have any thoughts on this matter?
Screenshots for proof below
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Alright guys I'm back to share what I have found after doing some research.
Right now I'm using ark kernel with liquid smooth 3.2 milestone
So back to these wakelocks, as it turns out, even though event0 was the most prevalent, most of the time it was on was while the screen was on, so basically you can ignore it.
However, there were two other events that I still had to investigate, event2 and event3. For me event2 is gpio_keys which are the button inputs. event3 is s2w_pwrkey.
First I deleted the event2 file under /dev/input. These files are restored on boot but I would still make a backup before trying this. After deleting this, my volume buttons stopped working, as expected. But my power button still worked. I used it for a couple hours but there was something that was keeping my phone awake still.
Then I rebooted and deleted event3. This is related to the sweep2wake that's implemented in alucard's kernel. I never use it anyway so I went ahead and deleted it. And what do you know, now my phone is sleeping like a baby and even the other events have gone down as well. But the problem is you have to delete the file on every boot. The solution? An init.d script with the following line. Where X is the number of the event you want to remove. You can also just add it to any existing scripts you might have in /system/etc/init.d
rm /dev/input/eventX
How to find out what's causing yours?
1.Download wake lock detector from the
play store and use it for a day
2.check under kernel wakelocks to see if
your phone is being kept awake by an
alarmingly high number of event
wakelocks, if so proceed.
3. Open terminal emulator and type the
following: "su" press enter after each
line
"ps | grep xxxx" where xxxx
is the number
following the event
wakelocks.
4. If system_server doesn't show up,
another app is causing it. Find it and
manage it. Otherwise, proceed.
5. Go back in terminal and type "su" enter
"getevent -c 1" this will give you all
of you events and and what they
are bound to.
6. Make a backup in recovery.
7. Delete one of the problem events and
see if your phone is kept awake, if it.
isn't then congrats! You found the
drain! Else keep testing.
8. Once your are certain which one it is.
Create an init.d or use an existing
one and add the line "rm /dev/input/
eventX" replace X with the event
you want to remove.
You're done.
If you have any problems or questions, I'll be happy to help.
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Thanks alot for this thread, very helpful. :good:
i don't have wakelocks (using @ak kernel and enabled only dt2w) but very useful thread
5 star rated :good:
ak said:
Thanks alot for this thread, very helpful. :good:
Click to expand...
Click to collapse
Cool that means alot coming from you
wizyy said:
i don't have wakelocks (using @ak kernel and enabled only dt2w) but very useful thread
5 star rated :good:
Click to expand...
Click to collapse
Thanks! I've never had a 5 star thread before
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
I am on cm11s and have these same wake locks but all are less than 10 on so far a days worth of battery time. I don't think it's much of a problem for me and probably more for cm12? Anyways thanks for the info now I know where to look if it ever becomes an issue
Cheers
i've been getting these crazy same wakelocks the last week as well, which is weird because i didn't get them the two weeks before that when i got my phone. And I've been flashing ROMs (Mahdi, SlimKat, Lollipop) and kernels (stock and AK) back and forth. Even after settling on Mahdi with a clean flash, they're still showing up. THanks for your investigation, I'm going to check things out when I get home tonight.
tracerit said:
i've been getting these crazy same wakelocks the last week as well, which is weird because i didn't get them the two weeks before that when i got my phone. And I've been flashing ROMs (Mahdi, SlimKat, Lollipop) and kernels (stock and AK) back and forth. Even after settling on Mahdi with a clean flash, they're still showing up. THanks for your investigation, I'm going to check things out when I get home tonight.
Click to expand...
Click to collapse
Agreed, it only started happening recently and I haven't installed any new apps, but newer Roms and kernels. So I really don't know whats causing it
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
tracerit said:
i've been getting these crazy same wakelocks the last week as well, which is weird because i didn't get them the two weeks before that when i got my phone. And I've been flashing ROMs (Mahdi, SlimKat, Lollipop) and kernels (stock and AK) back and forth. Even after settling on Mahdi with a clean flash, they're still showing up. THanks for your investigation, I'm going to check things out when I get home tonight.
Click to expand...
Click to collapse
Update: I flashed AK v30 kernel and the wakelocks seem to be gone now! Prior to this I was on Mahdi with stock kernel which had the wakelocks, and prior to that I was on Mahdi with AK v11 kernel which also had the wakelocks. This is only after an hour of "testing" though, so hopefully no apps I'm going to use will trigger them back :/
Edit: jk, wakelocks returned after a while. Screenshot attached. I rebooted the phone then left it alone for almost two hours.
Getting event0 1585 wakelocks, quite alot , more than 30k wakelocks in 3 hours.
It seems to be related to the synaptics driver, which to my knowledge is the touchscreen so i better not turn that off
Running AK 030 with Paranoid Saber Droid 4.4.4
mumaster20 said:
Getting event0 1585 wakelocks, quite alot , more than 30k wakelocks in 3 hours.
It seems to be related to the synaptics driver, which to my knowledge is the touchscreen so i better not turn that off
Running AK 030 with Paranoid Saber Droid 4.4.4
Click to expand...
Click to collapse
No just ignore that one. Most of the the 30k happens when the screen is on l
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
abhi08638 said:
No just ignore that one. Most of the the 30k happens when the screen is on l
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Click to expand...
Click to collapse
I am getting another quite massive wakelock, ipc0000007b_sensors.qcom, this one hits 143k wakelocks in 6 hours.
Tried searching for it on google but didnt really find any answerd or solutions. Do you know maybe what this wakelock is?
Most likely its a sensor, as seen in the name.
mumaster20 said:
I am getting another quite massive wakelock, ipc0000007b_sensors.qcom, this one hits 143k wakelocks in 6 hours.
Tried searching for it on google but didnt really find any answerd or solutions. Do you know maybe what this wakelock is?
Most likely its a sensor, as seen in the name.
Click to expand...
Click to collapse
I'll look into it
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Nice investigating and bug hunting OP.
mumaster20 said:
I am getting another quite massive wakelock, ipc0000007b_sensors.qcom, this one hits 143k wakelocks in 6 hours.
Tried searching for it on google but didnt really find any answerd or solutions. Do you know maybe what this wakelock is?
Most likely its a sensor, as seen in the name.
Click to expand...
Click to collapse
Alright, unfortunately I couldn't find any information about it. Are you running any auto brightness apps? Autorotation? Accelerator gaming? Magnetic case?
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Flashed the most recent boeffla kernel this morning (had ak 030 yesterday) and this whole day I haven't had any disruptive event wakelocks. Instead of minutes of those wakelocks, they're just St seconds now. Didn't change anything else.
tracerit said:
Flashed the most recent boeffla kernel this morning (had ak 030 yesterday) and this whole day I haven't had any disruptive event wakelocks. Instead of minutes of those wakelocks, they're just St seconds now. Didn't change anything else.
Click to expand...
Click to collapse
That's curious. It might be because of new commits that might have been reverted in the kernels. Right now I'm using Ark kernel
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
abhi08638 said:
Alright guys I'm back to share what I have found after doing some research.
Right now I'm using ark kernel with liquid smooth 3.2 milestone
So back to these wakelocks, as it turns out, even though event0 was the most prevalent, most of the time it was on was while the screen was on, so basically you can ignore it.
However, there were two other events that I still had to investigate, event2 and event3. For me event2 is gpio_keys which are the button inputs. event3 is s2w_pwrkey.
First I deleted the event2 file under /dev/input. These files are restored on boot but I would still make a backup before trying this. After deleting this, my volume buttons stopped working, as expected. But my power button still worked. I used it for a couple hours but there was something that was keeping my phone awake still.
Then I rebooted and deleted event3. This is related to the sweep2wake that's implemented in alucard's kernel. I never use it anyway so I went ahead and deleted it. And what do you know, now my phone is sleeping like a baby and even the other events have gone down as well. But the problem is you have to delete the file on every boot. The solution? An init.d script with the following line. Where X is the number of the event you want to remove. You can also just add it to any existing scripts you might have in /system/etc/init.d
rm /dev/input/eventX
How to find out what's causing yours?
1.Download wake lock detector from the
play store and use it for a day
2.check under kernel wakelocks to see if
your phone is being kept awake by an
alarmingly high number of event
wakelocks, if so proceed.
3. Open terminal emulator and type the
following: "su" press enter after each
line
"ps | grep xxxx" where xxxx
is the number
following the event
wakelocks.
4. If system_server doesn't show up,
another app is causing it. Find it and
manage it. Otherwise, proceed.
5. Go back in terminal and type "su" enter
"getevent -c 1" this will give you all
of you events and and what they
are bound to.
6. Make a backup in recovery.
7. Delete one of the problem events and
see if your phone is kept awake, if it.
isn't then congrats! You found the
drain! Else keep testing.
8. Once your are certain which one it is.
Create an init.d or use an existing
one and add the line "rm /dev/input/
eventX" replace X with the event
you want to remove.
You're done.
If you have any problems or questions, I'll be happy to help.
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Click to expand...
Click to collapse
Really a different way to deal with the problem than any other threads I have gone through. I am facing the same issue. Phone being awake when connected to WIFI only. The problem does not persist with Data connection and WIFI Off. Its very strange. I was working around for the solution but different things seemed liked working at different times.
Though I was having Event wakelocks and not wlan wakelocks I followed some solutions from this thread http://forum.xda-developers.com/galaxy-s2/help/puzzle-wlanrxwake-wakelock-sgsii-t2133176
Disabling netbios worked for me and again after an update the problem came back. Next time I tried changing frequency to 2.4Ghz and it worked. Now again after dalvik cache wipe the problem came back. No solution left to try.
I shall try the methodology u hav provided. Finger crossed. Really frustrated with this issue. Unable to keep the phone connected to WIFI.
But what can be the real issue. How can the volume keys or sweepwake issues persist only on WIFI and not on data connection. Should I ask for am exchange from OPO?
abhi08638 said:
Alright, unfortunately I couldn't find any information about it. Are you running any auto brightness apps? Autorotation? Accelerator gaming? Magnetic case?
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Click to expand...
Click to collapse
Non of that, next to the standard autorotation and auto brightness of android itself. I did see that all the screen off gestures were turned on in synapse so I turned that off but it didn't seem to help. Its not that big of a deal though, probably some necessary stuff happening in the background. Still getting rock solid battery life! 6+ hours sot over 2 days so you don't hear me complain thanks anyways for sharing your info!
Sent from my One using XDA Free mobile app
kandalamv said:
Really a different way to deal with the problem than any other threads I have gone through. I am facing the same issue. Phone being awake when connected to WIFI only. The problem does not persist with Data connection and WIFI Off. Its very strange. I was working around for the solution but different things seemed liked working at different times.
Though I was having Event wakelocks and not wlan wakelocks I followed some solutions from this thread http://forum.xda-developers.com/galaxy-s2/help/puzzle-wlanrxwake-wakelock-sgsii-t2133176
Disabling netbios worked for me and again after an update the problem came back. Next time I tried changing frequency to 2.4Ghz and it worked. Now again after dalvik cache wipe the problem came back. No solution left to try.
I shall try the methodology u hav provided. Finger crossed. Really frustrated with this issue. Unable to keep the phone connected to WIFI.
But what can be the real issue. How can the volume keys or sweepwake issues persist only on WIFI and not on data connection. Should I ask for am exchange from OPO?
Click to expand...
Click to collapse
Yeah I have noticed this wifi issue as well. Iight be related to the new drivers that were implemented but I haven't been keeping up with that so I don't know if it was reverted or not. I usually keep the wifi sleep policy to never. As I said before, I don't really know why they show up, but this "solution" is very dirty. The best way would be to find the cause of it.
I removes the s2w event because whatever triggered it actually uses power by keeping the capacitive keys on. So stopping that process ultimately saved me some battery.
Sent from my LG-P880 using XDA Free mobile app