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
Related
I have been trying to figure out why my cpu is always maxed out, so I downloaded OS monitor and noticed that the /init process is using a constant 90-98% cpu usage. Is this normal?
kevinpc said:
I have been trying to figure out why my cpu is always maxed out, so I downloaded OS monitor and noticed that the /init process is using a constant 90-98% cpu usage. Is this normal?
Click to expand...
Click to collapse
No, it is not.
/init for me right now is 0%
Are you running any mods like a custom rom, or setcpu, or anything like that?
I'm using stock, so nothing.
What is the init process for, maybe I can determine if an app is causing this.
I have also killed it and it comes right back on.
Update:
Okay I have simply done a reboot battery pull and it killed it. I am still wondering what triggered it to happen, but thanks for your reply.
kevinpc said:
I'm using stock, so nothing.
What is the init process for, maybe I can determine if an app is causing this.
I have also killed it and it comes right back on.
Click to expand...
Click to collapse
in a nutshell, init is supposed to be what starts all your services and anything that's been added to the init.rc script at boot up time for the phone.
Have you tried running a logcat to see if anything's revealed in the log (there's an app for that (alogcat on the Market) if you don't know how with adb or a terminal app on the phone itself).
I've read that for some other devices with this issue that enabling debugging (Menu/settings/applications/development/now turn on Usb debugging) solves the problem for them.
You might also look at settings/about/battery usage, and see if something there is chewing up the battery besides Android system.
Try system panel and see what that says. Or run the top command in terminal and see...
Issue is back!
RogerPodacter said:
Try system panel and see what that says. Or run the top command in terminal and see...
Click to expand...
Click to collapse
This issue has popped up a few more time now, I can resolve it by a battery pull, but it always seems to pop back up. I looked at System Panel and i don't see any particular apps using the cpu other than Panel, but still processes has /init at 95% load.
What log app should i use and how do i post it where it is not to long for the post max characters?
kevinpc said:
This issue has popped up a few more time now, I can resolve it by a batter pull, but it always seems to pop back up. I looked at System Panel and i don't see any particular apps using the cpu other than Panel, but still processes has /init at 95% load.
What log app should i use and how do i post it where it is not to long for the post max characters?
Click to expand...
Click to collapse
Grab aLogcat from the Market, or just hook up to the computer (if you have adb on it) and type in "adb logcat" from the terminal command line.
You can save it as a text file and attach it to a post here, or use pastebin website.
distortedloop said:
Grab aLogcat from the Market, or just hook up to the computer (if you have adb on it) and type in "adb logcat" from the terminal command line.
You can save it as a text file and attach it to a post here, or use pastebin website.
Click to expand...
Click to collapse
Hope this helps. I have performed a factory reset today, but i do have my apps backed up by google servers so everything that was on there before is back on again, and so the /init process has resumed its normal heavy load again. Here is the log from alogcat.
Going through the log i didn't see anything suspicious, but I have an untrained eye.
next time it happens, run the Top command which should show all cpu processes using your resources at that time. dont reboot first so you dont clear away the bug.
i think there is even an app on the market called "top" which will do the command for you so you dont have to deal with it in terminal.
i dont see anything particular in your logcat. did the issue happen during the time period of this log?
kevinpc said:
I have been trying to figure out why my cpu is always maxed out, so I downloaded OS monitor and noticed that the /init process is using a constant 90-98% cpu usage. Is this normal?
Click to expand...
Click to collapse
i occasionally get this on my htc legend with official unrooted 2.2. i just reboot to fix it because the phone is near unusable when this is occurring. it is a pain though. it never happened under 2.1 official
i just bought a nexus s and waiting for it to come in the mail so im not too fussed about the legend. i wonder if it has anything to do with some market app...
had the same issue on my samsung vibrant. to get rid of the issue i turn debugging on and rebooted the phone at least once a day (in the morning when i wake up).
RogerPodacter said:
next time it happens, run the Top command which should show all cpu processes using your resources at that time. dont reboot first so you dont clear away the bug.
i think there is even an app on the market called "top" which will do the command for you so you dont have to deal with it in terminal.
i dont see anything particular in your logcat. did the issue happen during the time period of this log?
Click to expand...
Click to collapse
Here is the log from TOP running from Terminal Emulator, I this report doesnt seem to breakdown what exactly is using or causing the high cpu usage just states that it is in use by usr and system. By the way this is stock 2.3 Nexus S.
I also didn't see anything stand out in your logcat. Not going to bother looking at the top, since it's easy enough to read and you've reported it.
Have you tried a factory reset of the device? Pain in the butt to re-setup the phone, but might resolve the situation.
If it were me, I'd factory reset, install minimal must-have apps only and test it for a day. If the problem doesn't resurface start adding back the nice-to-have apps and monitor performance.
If the problem does resurface after a fresh reset and minimal apps, I'd take the thing back and exchange it. Something's not right with the phone at that point.
distortedloop said:
If it were me, I'd factory reset, install minimal must-have apps only and test it for a day. If the problem doesn't resurface start adding back the nice-to-have apps and monitor performance.
If the problem does resurface after a fresh reset and minimal apps, I'd take the thing back and exchange it. Something's not right with the phone at that point.
Click to expand...
Click to collapse
Ok I have performed a factory reset also deleting all sd information. Will only use stock G, for a day or two without any installed apps or launchers, we will see if this is a stock bug, market bug, or hardware bug. Hopefully.
P.S. what is Best Buy return policy? j/k
deleted...wrong topic.
kevinpc said:
Here is the log from TOP running from Terminal Emulator, I this report doesnt seem to breakdown what exactly is using or causing the high cpu usage just states that it is in use by usr and system. By the way this is stock 2.3 Nexus S.
Click to expand...
Click to collapse
well crap on me, you're right, top doesnt necessarily break out the processes. i'm so used to system panel i guess i just forgot.
damn i dont know how else to track down your bug. you already posted a logcat when this bug happened. not sure what else to do.
RogerPodacter said:
well crap on me, you're right, top doesnt necessarily break out the processes. i'm so used to system panel i guess i just forgot.
damn i dont know how else to track down your bug. you already posted a logcat when this bug happened. not sure what else to do.
Click to expand...
Click to collapse
Well I have done everything possible to resolve this bug, and now it is back with a factory reset using almost zero applications. And we are 100% sure this isnt a normal process? Well if not I guess its back to best buy after work tomorrow. I hate being disappointed.
kevinpc said:
Well I have done everything possible to resolve this bug, and now it is back with a factory reset using almost zero applications. And we are 100% sure this isnt a normal process? Well if not I guess its back to best buy after work tomorrow. I hate being disappointed.
Click to expand...
Click to collapse
Yes, I am sure that it is not normal to have the init process stuck at 100%.
ryan562 said:
had the same issue on my samsung vibrant. to get rid of the issue i turn debugging on and rebooted the phone at least once a day (in the morning when i wake up).
Click to expand...
Click to collapse
Just to finish this thread up, this did actually fix the problem, i turned debugging on, went immediately to OS Monitor and watched the /init process go from 97% to 0%, but unfortunately I don't find this acceptable with an expensive phone such as this. So I will go exchange the Nexus S for a new one and cross my fingers, if it happens to happen on the next one, I will go back to my Nexus One that is sitting in my top drawer just for instances such as this.
Thanks for your replies.
kevinpc
kevinpc said:
Just to finish this thread up, this did actually fix the problem, i turned debugging on, went immediately to OS Monitor and watched the /init process go from 97% to 0%, but unfortunately I don't find this acceptable with an expensive phone such as this. So I will go exchange the Nexus S for a new one and cross my fingers, if it happens to happen on the next one, I will go back to my Nexus One that is sitting in my top drawer just for instances such as this.
Thanks for your replies.
kevinpc
Click to expand...
Click to collapse
It does appear to be an idiosyncrasy of your phone. I always run with debugging on anyways, since some root apps require it, but for testing purposes I just turned it off, checked init process (0%), rebooted to be sure, checked init process (still 0%).
This was an interesting one...before closing out the thread for good, please come back and let us know if the replacement unit behaves the same way for you or not.
Installed Beans 8 recently and Ive been having my phone be awake at precise intervals overnight. it seems like every 15 minutes. Ive checked my settings and cant find anything that I wouldve done to cause it. Ive neverhad this issue. btw, im running KT747 kernel
aynway, I bought and installed betterbattrystats after searching for help. Im at a loss at the moment. The readings are a little too advanced for me. I dont know the difference between a good wake up and a bad one. Are there common causes for this?
Is there a better way to narrow this down? I deleted the apps I dont use hoping that one was rogue and doing this, but I dont think thats it. The only thing I could think of off the top of my head was that I recently upgraded to nova prime and i am using the unread counter that Nova uses. could that be scanning for notifications constantly?
Any help appreciated. I love this ROM. its by far my favorite taht ive flashed so far, i dont want to flash somethign else. Im sure its something I did.
thanks in advance. If its neccesary ill post up my Betterbatterystats tomorrow after I run through a charge cycle during the day tomorrow.
bumping this up for screen shots. I put this down before i went to bed, and checked when i woke up. I set an alarm before going to sleep, thats all i did. i think my phone being awake has to do with the maps app. how can i control this? ive never had this happen before?
GPS has been off and googles location service is all that I keep on. it looks like its updating at regular intervals. is this google now? Its not a huge drain, but its enough that ive noticed it. any help appreciated.
in the meantime, i cleared data/cache, uninstalled and reinstalled maps.
That looks pretty normal. You may want to post the better battery stats info, it may help. Also for location waking your phone up, open maps, go to settings, location settings and disable report location from this device.
Sent from my VS920 4G using xda app-developers app
I am too lazy to type everything. Download gscript from the play store and create a script that mirrors the picture. Save and run it. Once it completes there will be a txt file on /sdcard so open it up and sift through the entries till you find a line that says Alarm Stats. After that line just see if any entries have a large number beside alarms
Sent from my SCH-I535 using xda app-developers app
I would post this in the Developer forum, in reply to a poster who has the same problem, but I just registered and therefore do not meet the requirements to post there.
I'm wondering if anyone else has observed this behavior. In short, I installed TriForceROM 3.0 (after performing a "Wipe User Data" operation in TWRP 2.6.0.0) and all was well for about 12 hours. During the ROM installation, I chose the "Standard" option, as I believe it's called. (I didn't elect to customize anything.)
After 12-18 hours of having the ROM installed, I noticed that my phone was simply powered-off. I hit the power button and nothing. Then I held-down the power button, which is how I normally power-on the device, and then realized that the device was, in fact, powered-off when I came back to it after a few hours of being in the other room.
After powering-on the device, the same thing happened a few hours later, and the issue seems to be occurring more and more frequently as time passes.
I have not changed any of the ROMs settings, and I haven't installed any type of third-party "tweaking" app.
Another individual has the same problem:
http://forum.xda-developers.com/showpost.php?p=43942167&postcount=1466
Could this be due to kernel, power, or CPU settings? I noticed that when I opened KTweaker for the first time, the application warned me:
"Your KThermal values do not match current, Apply values?"
and
"Your vibration Strength does not match current, Apply Vibration Strength value?" (this one seems unrelated)
The CPU temperature seems to hover around 45 degrees Celsius. (Is this a normal range?)
Another observation is that when I long-press the Home button (to bring-up the app-switcher), I see a little Android icon with the title "MIPErrorActivi...". If I click on it, I'm simply dumped to the Home Screen. I don't know if this is at all related.
Thoughts or suggestions, anyone?
My phone is model SPH-L720.
Thanks in advance!
I went into KTweaker and clicked "Load Defaults" and rebooted, and everything seems to be stable. No reboots in 18 hours or so.
Also, the ROM author has mentioned this issue, as well as an interim fix (related to the KT kernel), and says that he will release v 3.1 within a few days, which should fix the issue entirely.
Good stuff!
UPDATE:
Well, the phone rebooted itself, eventually, so setting KTweaker settings to defaults was not the solution.
However, I downloaded the kernel update that the ROM author suggested ( http://forum.xda-developers.com/showthread.php?t=2288309 ) and that does seem to have fixed the problem. No reboots in over two days. Yay!
An interesting aside is that with the new kernel and accompanying KTweaker app, the warnings that I was receiving with the old kernel when launching KTweaker disappeared. All is well!
DrRichardQuack said:
I went into KTweaker and clicked "Load Defaults" and rebooted, and everything seems to be stable. No reboots in 18 hours or so.
Also, the ROM author has mentioned this issue, as well as an interim fix (related to the KT kernel), and says that he will release v 3.1 within a few days, which should fix the issue entirely.
Good stuff!
UPDATE:
Well, the phone rebooted itself, eventually, so setting KTweaker settings to defaults was not the solution.
However, I downloaded the kernel update that the ROM author suggested ( http://forum.xda-developers.com/showthread.php?t=2288309 ) and that does seem to have fixed the problem. No reboots in over two days. Yay!
An interesting aside is that with the new kernel and accompanying KTweaker app, the warnings that I was receiving with the old kernel when launching KTweaker disappeared. All is well!
Click to expand...
Click to collapse
Thanks for noting this. I actually started my account for the same reason, but haven't had enough useful input to get the posts to leave feedback in the dev forums. I sure don't want to spam useless posts :angel:
Lsd-Pulsar said:
Thanks for noting this. I actually started my account for the same reason, but haven't had enough useful input to get the posts to leave feedback in the dev forums. I sure don't want to spam useless posts :angel:
Click to expand...
Click to collapse
Haha. Well, glad I could be of help and that we both garner a couple of "useful posts" out of it.
I'm pretty sure that the reboots continued for me (although, less frequently with the kernel patch in place), but upgrading to TriForceROM 3.1 seems to have fixed the issue altogether. It's worth noting that I chose a different kernel this time (I forget what it's called; the name is four letters, all capitals). No reboots in the first 24 hours.
I doubt it makes a difference, but I also upgraded to the MF9 firmware from Samsung. Happy to answer any questions in that regard, too.
DrRichardQuack said:
Haha. Well, glad I could be of help and that we both garner a couple of "useful posts" out of it.
I'm pretty sure that the reboots continued for me (although, less frequently with the kernel patch in place), but upgrading to TriForceROM 3.1 seems to have fixed the issue altogether. It's worth noting that I chose a different kernel this time (I forget what it's called; the name is four letters, all capitals). No reboots in the first 24 hours.
I doubt it makes a difference, but I also upgraded to the MF9 firmware from Samsung. Happy to answer any questions in that regard, too.
Click to expand...
Click to collapse
I would wager that you moved over to AGAT's. Several users reported lag with that kernel, so I stuck with KT.
After more reboots and a lot of tweaking, I've got my issue nailed down. Raising the voltages on the low end cpu frequencies (where a phone would normally be with screen off) has corrected the stability issues. I also had to up the voltages at the high side. That helped Antutu to run for a while, but now that's crashing back to desktop for me. When it does run, I usually hit around 25,000 with the Triforce 3.0 + Ktoons kernel with overclock enabled. I have not overclocked the GPU (yet). Running KTmod, but not crossbreeder.
I may back this all up tonight and reflash with Triforce 3.1. I've been fighting battery issues: Google Location Services and Android Widgets Pro seem to be behaving badly.
I feel like I'm very close to a fast, stable rom install with good battery life. Once I get there, I'll wait a couple months until the existing ROM's and kernels are polished a little more. And now I'm one post closer to being productive in the Dev forum.
That's the one; AGAT's kernel. I haven't noticed any sluggishness with the ROM's (and or kernel's) default settings. So, I'm happy!
No random power-downs or any other abnormal behavior since upgrading to 3.1 and switching to AGAT's three days ago.
I don't know if it was upgrading from 3.0 to 3.1 or switching kernels that fixed the random power-downs; I'm just glad I have a very fast and stable ROM at this point.
My battery life has been good. Moderate usage throughout an 8-10-hour work-day leaves me with about 70% battery when I get home.
My hat's off to the developer. I think I'll kick him a few bucks.
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?
I know I am not the first one to post about this issue. I have searched, not only on xda, but some other websites. I just cannot find a solution. I am running 5.1.1 non rooted Stock ROM. I have tried everything. Enabled and Disabled a lot of settings. Nothing seems to work. 20% for that Android System is just too much. It started a week ago. Today I have Installed "Quick System Info PRO" and it shows that some "System_Server" is eating battery due to a high usage of RAM and Proccesor. See attachments please.
I am thinkg about updating my OPO, but I am not sure if this will help.
Did you find a solution? Do you know how to fix this? Please share your knowledge with me.
I used to plug and charge my OPO once every day and a half. But now I have to live with my charger inside my pockets because I am charging my phone every 10 hours.
There are any other apps? Also, try with android 6.0, might fix something.
Hi @srsdani.
Thank you for your reply. No. There are not any other apps eating battery. Mostly because I am at work, I use Whatsapp.
I should also mention that the phone gets super hot for no reason, like when you are playing a game after a long time. (Due to the intesive CPU usage).
leokook said:
Hi @srsdani.
Thank you for your reply. No. There are not any other apps eating battery. Mostly because I am at work, I use Whatsapp.
I should also mention that the phone gets super hot for no reason, like when you are playing a game after a long time. (Due to the intesive CPU usage).
Click to expand...
Click to collapse
there can be couple of problem responsible causing this .if i would be you , i would deep wipe my every os related partition and flash a new maybe unofficial cm 12s /any non crazy rom properly and see the results
You use at work wifi or mobile data?
Off topic :
Privacy guard shows phone is awake while charging phone(location service) is waking up only while charging.. Anysolution?
1.i have disabled screen awake in dev options
2.i am using original charger
3.i am on latest cos13
4.while charging screen is completely off & no background apps running (greenifyd)
Even wakelock Detector also shows phone awake.. How to disable??
Wifi
srsdani said:
You use at work wifi or mobile data?
Click to expand...
Click to collapse
I use WiFi, mostly.
#sychrome# said:
there can be couple of problem responsible causing this .if i would be you , i would deep wipe my every os related partition and flash a new maybe unofficial cm 12s /any non crazy rom properly and see the results
Click to expand...
Click to collapse
I'm thinking is OS-related. But by doing some search you will find a lot of people with same issue. Even non-OPO users. I'm gonna give it a try anyway.! Thank you for your reply.
leokook said:
I'm thinking is OS-related. But by doing some search you will find a lot of people with same issue. Even non-OPO users. I'm gonna give it a try anyway.! Thank you for your reply.
Click to expand...
Click to collapse
try better battery stats and correct firmware and recovery , if possible do everything in fastboot inc flashing
So, yeah, I got the most expected update, installed and worked great... Until some issues showed up, like lockscreen freeze, and now the "you can't see you WiFi power consumption" issue. I'm mad, I know WiFi was taking a huge piece of my battery ( tried some suggestions) but now a bug report appeared, and this is what I face today
Before it was like this
What should I do now? A clean install ?
Sent from my A0001 using XDA-Developers mobile app
leokook said:
So, yeah, I got the most expected update, installed and worked great... Until some issues showed up, like lockscreen freeze, and now the "you can't see you WiFi power consumption" issue. I'm mad, I know WiFi was taking a huge piece of my battery ( tried some suggestions) but now a bug report appeared, and this is what I face today View attachment 3741929
Before it was like this View attachment 3741930
What should I do now? A clean install ?
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
Don t fast reboot
Shutdown your device and power on
Reboot enable system drain
Disable from security settings google administrator
Cyanogen device manager does the same
Also cyanogen statistic are not used any more to lollipop
Do not use greenify apps from version to version update has opposite results
If you want better battery use apps that will disable sensors and locationwhen device sleep