Database Info

[Q] Is the init process supposed to be running 97% of my cpu?

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.

HTC Sensation General FAQ's. New to this device? Read here! UPDATED 8/3/11

**Added a few new things now that we have S-off. Check them out below.**
This thread was created simply for Noobs. Yes, if you don't know how to boot into the bootloader..than you should be reading this. We were all Noobs once. You can always check this more than once since i will be updating it with more issues and solutions fellow members post that i might have forgot to add.
If you dont have this recovery flashed already here is a Link to a WORKING CHARGING WHILE OFF RECOVERY PLEASE FLASH IT JUST TO BE SURE YOUR SAFE here. Will get removed when Rom Manager gives you the right recovery and not a broken one.
My Phone Died and i can't turn it back on!!! help!!
1. Download the recovery i have posted above. Once downloaded rename to remove the name of the recovery until its just named recovery.img.
2. Plug your device to a computer and run the command
adb reboot
or
adb reboot bootloader
if your device doesn't turn on, then simply pull the battery, put it back in, then redo the steps.
3. Once your phone does power on from one of those commands, reboot into android OS and put the recovery on the root of your sdcard.
4.Boot into bootloader while plugged into the computer and run the following command
fastboot flash recovery recovery.img
Then the problem is fixed! I'm very sorry for the inconvenience, but thats the fix.
7/28/11 We now have s-off.
follow this guide here for a better in depth on how to do it. : http://forum.xda-developers.com/showthread.php?t=1192300
How do i flash a ROM on my sensation?
1.place the rom on the ROOT of your sdcard.
2.boot into recovery using either the app rom manager and choosing boot to recovery, MORE THAN LIKELY your custom rom will have the advanced power menu so you can just hold the power key, go to restart, then choose recovery, or powering off and booting holding power+vol down, then scroll down to recovery, press power key.
3. WIPE your DATA/CACHE partitions, then scroll down to advanced and wipe your dalvik cache.
4. go to install zip from your SDCARD
5. Choose zip from sdcard.
6. Find the rom, press power button, and install it.
7. Reboot and enjoy!
Will i lose all my texts, apps,etc when i install a new rom?
Yes you will. You could make a titanium backup of everything though and restore it when your done flashing the roms so you can get everything back. Download titanium from the market.
What is the difference between a Nandroid Backup and using Titanium backup??
Well When you make a nandroid backup, your backing up the ENTIRE rom, not just things you want to restore onto your new rom. in other words, with a nandroid, if you want to go back to your previous rom if you don't like the new one, use a nandroid backup.
Nandroid sounds interesting and is something i would like to do!! How do i do it?!
You boot into recovery, go down to where it says backup and restore, and choose backup, name it, then go ahead and back it up. Thats obviously where you want to restore it as well. You *ALSO* can choose the app ROM Manager and do it from there.
My battery Life SUCKS after i flashed this New ROM!! IS MY BATTERY MESSED UP??
Nah its not don't worry about it. Your battery life usually is going to suck because your battery stats got wiped from android, and it has to recreate it. So let the battery die once probably, fully charge it, then let it die again. then Charge it then you should be ok. Give it a day or two you should see a change. If not, let the developer of the ROM know NICELY in his thread. If you see that someone already posted about the battery life, no need for you to post it as well.
How do i flash a kernel??
You flash it exactly how you do a ROM. No need to wipe anything just flash it and reboot.
How do i flash a RADIO?
That depends. if its in a format and the name starts with a P then has a bunch of different numbers after, then you do the following:
1. Place on the root of your sdcard.
2. Reboot into the bootloader.
3. Then it will find it, and ask you if you want to update.
4. Let it do the update. It will only replace the radio.
5. Reboot into recovery and wipe DALVIK cache.
6. Reboot and enjoy.
ALWAYS make sure you read the Original post of the person who is providing the radio to make sure he ripped everything out and its ready to flash.
My Phone is S-OFF and it fully died and now it won't turn back on and it doesn't look like its charging while its off WTF AM I BRICK?!?!
No its not. From what i learned its in "offline" charging mode since the battery is so low, and even though the light isn't showing, its still charging. To turn back on:
1. Either wait a few mins and let it charge for a little, then pull battery, put it back in and try to turn on.
2. Plug into computer, let it sit for a second, then use this command from terminal:
adb reboot
It will turn it on for you. i honestly don't know WHY its like this, but thats just how it is for right now. i personally had to use the second option. If i learn more about this, ill update you guys.
Does this Recovery update?! If so, how do i UPDATE IT?!
Since S-off and recovery JUST became available to us, its prolly not updated right now. But for future reference just download the App ROM Manager from the market. Once loaded, if there is ever an update or something for it, it will be in that app. then you can choose it from there and it will update it for you.
I hold the volume down+the power button but it doesn't boot into it!!!! help!!!
Pull the battery out before you do it. OR to make things ALOT easier, before turning your sensation off go into settings,power, and uncheck the Fastboot option. Now when you turn the device off, it will fully power down instead of just going into a "sleep" mode. Now do it.
My wifi is terrible! When i turn it sideways, i lose ALL MY BARS!! WTF?!?!
'Try moving your hand, you might be detuning the WiFi antenna'. If you know that the WiFi antenna is adjacent to the camera lens, you're more likely to be aware when you're covering it. But Your not alone either. i actually have this same problem as well. Yes i know it sucks. There are only three things you could do here though honestly since We haven't really brought it down to a conclusion of is it our hardware that's causing it or is it the software.
1.You could boot into bootloader and data wipe your sensation to see if it fixes it. BE WARNED IT WILL WIPE YOUR DEVICE, MEANING EVERYTHING WILL GET DELETED OFF IT! APPS, MESSAGES ETC.
2.If that doesn't fix it, go into Settings-Wifi & Networks-Wifi Settings. Once your in there press the menu button and go to the advanced option in the pop-up menu. Once in there choose Best Wifi Performance.
3. If that doesn't work, then you need to get a warranty replacement. we know it sucks, we promise.
My touchscreen stops being responsive! Whats going on!?
It seems to be happening to everyone after about a week of use, me as well. We think maybe an ota will fix it. But to do a quick fix of it just turn the screen off for a few seconds then turn it back on. it usually fixes it whenever it stops working.
My Data connection is horrible and extremely slow. Why?!
This also seems to have happened to everyone. To try to fix, call t-mobile and see if they have your phone in their database, and make sure on their database it has that you have a sensation and they have the right data package going for you. Also make sure your Sim card isn't old, which t-mobile can also fix for you. I Can personally say talking with t-mobile helps. i used to have poor connection. now i can use wifi hotspot for my laptop while being on the phone talking with someone still with full 4G bars.
You could also try this fix ( Thanks Mysterioustko):
-Go into the dialer and dial *#*#4636#*#*
-Select Phone Info
-Go to the "toggle cyphering" button and disable it
-For good measure turn off radio and then turn it back on
-Then reenable the "toggle cyphering" button
Just got my new sensation but its really hot!!! Is it defective?!
No it's not defective, its just hot. These batteries can heat up from time to time, ESPECIALLY on your first few charges, but it won't happen much anymore after. My battery was extremely hot from just charging it for the first time with the phone turned off, so i'm speaking from experience and from other users as well.
The voicemail notification won't leave the status bar even when i don't have a voicemail!!
Simple fix: Settings-Call-Clear Voicemail Notification.
Any more questions? Please Ask here. Ill try to answer them and add them to this post. Hope this helps people. Let's not keep asking the same questions over, and over, and over.. and over again.

you should add in some of the other known issues too, such as no sound issue & the voicemail icon clear, & try to get this as a sticky.

xnifex said:
you should add in some of the other known issues too, such as no sound issue & the voicemail icon clear, & try to get this as a sticky.
Click to expand...
Click to collapse
That Makes sense. Just i never came across that voicemail or no sound issue. Direct me to a link real quick so i can add them so i can see the problem and post the solution? Thanks alot for the input i appreciate it. ill keep looking for more Problems and what not. And i already asked a MOD to sticky it. I just doubt they'd Sticky it in the General AND Developement section, since i posted it there as well for the people who miss it here somehow (or just never come to this section of our forums) and vice versa.

I've read about people having touchscreen issues, where parts of the screen become randomly unresponsive. I have also noticed this on mine. Is the presiding school of thought that this can be fixed with their update?
I also have intermittent data stalls that require a cycle in and out of airplane mode to fix. Tmo has advised me that htc is going to fix this in their update and they are aware of it.
Sent from my HTC Sensation 4G using XDA App

TJBunch1228 said:
I've read about people having touchscreen issues, where parts of the screen become randomly unresponsive. I have also noticed this on mine. Is the presiding school of thought that this can be fixed with their update?
I also have intermittent data stalls that require a cycle in and out of airplane mode to fix. Tmo has advised me that htc is going to fix this in their update and they are aware of it.
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
Thanks for this. Couldn't hit the thanks button for this post. Apparently ive thanked too many people for one day
Added the Touchscreen issues and the data stalls. Let me know if i didn't put it in there right. And yeah i do think an OTA will fix it. Lets just hope for the best. I highly doubt its a hardware issue since everyone seems to be getting it after using the device for about a week.

Shaquiel Harris said:
That Makes sense. Just i never came across that voicemail or no sound issue. Direct me to a link real quick so i can add them so i can see the problem and post the solution? Thanks alot for the input i appreciate it. ill keep looking for more Problems and what not. And i already asked a MOD to sticky it. I just doubt they'd Sticky it in the General AND Developement section, since i posted it there as well for the people who miss it here somehow (or just never come to this section of our forums) and vice versa.
Click to expand...
Click to collapse
I'll get around to that soon

For the voicemail icon bug, I just called my phone and left myself a message and removed it. Worked well..

Temp stickied here as well. Please note that if/when we do a rollup that this may be un-stuck and added to the rollup thread.

a4ol said:
For the voicemail icon bug, I just called my phone and left myself a message and removed it. Worked well..
Click to expand...
Click to collapse
even faster: Settings>Call>Clear Voicemail Notification

ashasaur said:
Temp stickied here as well. Please note that if/when we do a rollup that this may be un-stuck and added to the rollup thread.
Click to expand...
Click to collapse
Thank you very Much!

xnifex said:
even faster: Settings>Call>Clear Voicemail Notification
Click to expand...
Click to collapse
Thanks. Op updated.

Not sure if this is the right place to ask this type of question but I didn't want to start another thread for something so simple.
Sometimes after I send a text message, the large word I typed magically reappears in the textbox. It happens randomly and I don't know how to reproduce it.

Hey
...wow... these forums are MASSIVE and I can't search noting? whats up with that?
Anyway that's off topic, so can I update the Hboot to 1.18, is the newly ship t-mobile phones at 1.18.

Issue #1: Downloaded Apps that was save on the SD card and showed on the homescreen, icons wont show or becomes like of the andriod market icon after a reboot.
Solution: Go to Settings>Applications>Manage Applications>Choose "All" tab> and look for the HTC Sense loader app. Tap it and choose "force stop" then press the home button. your homescreen will reload and the apps icons will now show.
Issue #2: HTC Sensation's default video player, sound goes away after 50-70secs of playing time.
Solution: i downloaded a different player since im getting pissed off with the default player and i cant seem to find a fix for it. i really hope this would get fixed with featured updates.

^Issue #1 worked great...cool! But, not sure how often it will need to be done....

well for me, everytime my device restarts, i do this.

Two main issues I've noted thus far, one minor, one moderate:
1. Sense performance seems choppy/sluggish when swiping from one screen to another. I believe this part of Sense is called "Rosie" but not sure. Sense performance is *definitely* slower than the EVO 3D which is weird because both phones have nearly identical hardware. Software glitch?
2. Battery use is *much* higher than I expected even after having a couple of weeks for the battery to settle in. I'm getting 150ma to 250ma usage when phone is just sitting there, screen off, not doing anything special. Yes, I have it set to push mail from Exchange, sync weather once per hour, sync with HTCSense.com, stocks, GMail, and Facebook. My HD2 did all this with about 20ma-40ma usage so can't understand why the Sensation sucks up so much more juice doing the same work. Turning on the screen and GPS (I use Google Nav) puts me in the 600+ma usage range. I currently can't get through even a half day of decent usage without draining the battery flat.
Item #1 is probably a software glitch because I've heard others complain about it. I'm hoping an OTA fix is on the way that will also unlock the bootloader.
Item #2 is more worrisome. I can't understand why the phone is using so much more power than my old HD2 (running Coredroid 1.6). 4G coverage near me is not all that good. I have a funny feeling the 4G radio is really sucking down the juice. Is there a way to force it back to 3G mode? I don't need 4G speed all the time and would prefer the better battery life.

prisoner881 said:
I have a funny feeling the 4G radio is really sucking down the juice. Is there a way to force it back to 3G mode? I don't need 4G speed all the time and would prefer the better battery life.
Click to expand...
Click to collapse
I was also wondering this too. I just got a Sensation yesterday and am wondering how to turn off the 4G to save juice when I don't need it

The WIFI sucks so much!!!! ugh.... i hate it!! if i change a new battery cover, is it gonna turn into normal? i just got my Sensation like an Hr ago...

Final Root Method
Where will this be posted once achieved? I'm dying for it! Thanks.

[Q] How to fix high media usage?

I saw people running scripts to kill directtalk or something like that?
any help? Im noticing this issue today.

ddurandSGS3 said:
I saw people running scripts to kill directtalk or something like that?
any help? Im noticing this issue today.
Click to expand...
Click to collapse
If it's directtrack just reboot your phone after using any media player. if it's media storage disable it charge your battery up then r enable it send to work. What ROM are you on?
Sent from my S3 running Eclipse 2.1

I've been having this problem on Codename ROM, Liquid Smooth ROM, and BlackBean ROM regardless of the method you posted any other advice?

Direct track you'll just have to do a reboot. If its media storage you can download rescan media root from the market and then disable media scanner and re-enable each time you reboot. Or you can download rom toolbox pro from the market, go to autostart manager, and then search "media" itll bring up mediastorage, long press on that and select "advanced freezer" then disable and re-enable the first option under "services"

So Its the Media Storage service giving me problems and downloading the Media Rescanner didn't seem to work by I tried out the ROM Toolbox pro process and hopefully it works out too early to tell. But regardless of if it does or not thank you so much for replying. You are the only person here who offered help so much appreciated

Okay so it seems neither of the methods you gave me worked

jesseag7 said:
So Its the Media Storage service giving me problems and downloading the Media Rescanner didn't seem to work by I tried out the ROM Toolbox pro process and hopefully it works out too early to tell. But regardless of if it does or not thank you so much for replying. You are the only person here who offered help so much appreciated
Click to expand...
Click to collapse
I may have spoken too soon. I did reboot this morning (51 minutes ago), and now my battery is draining fast adn MEDIIA is at 55%.

i am having the same problem too

Did you just load this Rom? If so, give it a couple days.to adjust
stripped apart rebuilt with Clean Rom&XdaTechnology!!!

Hulk0069 said:
Did you just load this Rom? If so, give it a couple days.to adjust
stripped apart rebuilt with Clean Rom&XdaTechnology!!!
Click to expand...
Click to collapse
i usually just force stop the media after rebooting the phone... seems to work of for me :good:

Event0 wakelocks

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

OnePlus 7 Pro Slowdown

It seems after about 48 hours of up time. The phone begins to lag extremely bad. Mostly when I first start typing it'll take 3 seconds or so for it to finally catch up to my typing. This happens Everytime I use the keyboard after those 48 hours or so. Apps seem to open very slowly as well after this time. A reboot seems to fix it and it runs fine after that until then. I've tried about 3 different kernels and face the problems with everyone. Not seeing any odd battery drain either. Just curious as to what would be causing this. Only module I have installed is google framework (for the dialer)

Doze.
This application who is show go in apk info and click dont optimize
Sent from my GM1910 using Tapatalk

Geto-Fraer said:
Doze.
This application who is show go in apk info and click dont optimize
Click to expand...
Click to collapse
Hmm really. I'll have to give that a shot ?
EDIT
I don't see Gboard even under the battery optimization. Doesn't give me an option to remove it from optimization. Pretty much all apps run slower around the 48 hour mark it's not just Gboard. But that's weird it's most annoying.

cgibbons51 said:
Hmm really. I'll have to give that a shot ?
EDIT
I don't see Gboard even under the battery optimization. Doesn't give me an option to remove it from optimization. Pretty much all apps run slower around the 48 hour mark it's not just Gboard. But that's weird it's most annoying.
Click to expand...
Click to collapse
Could be an app leaking memory (not properly returning it when it's no longer needed). Have you added any new apps recently? Try freezing them.
Or perhaps a bad app update?

davidk21770 said:
Could be an app leaking memory (not properly returning it when it's no longer needed). Have you added any new apps recently? Try freezing them.
Or perhaps a bad app update?
Click to expand...
Click to collapse
I'll have to check apps here and there cause I have a pretty long app list but nothing that would run in the background much. But nothing new that I'm aware of. Not seeing my memory usage maxed out or anything. I'll have to take another look after my phone's been on for 48 hours.

cgibbons51 said:
Hmm really. I'll have to give that a shot ?
EDIT
I don't see Gboard even under the battery optimization. Doesn't give me an option to remove it from optimization. Pretty much all apps run slower around the 48 hour mark it's not just Gboard. But that's weird it's most annoying.
Click to expand...
Click to collapse
Show system apps from menu
Also if you have Alot of apps installed you can try to turn off sync
This should take Alot of strain away from apps trying to update/check for updates
Stuff like snapchat, Facebook, and other apps with frequent updates.
If you have magisk/EdXposed installed it could be these as well since they are trying to force the system to change code.
It kinda depends on what you have done to your device, if it's stock then sync or doze could be the problem

ivoe said:
Show system apps from menu
Also if you have Alot of apps installed you can try to turn off sync
This should take Alot of strain away from apps trying to update/check for updates
Stuff like snapchat, Facebook, and other apps with frequent updates.
If you have magisk/EdXposed installed it could be these as well since they are trying to force the system to change code.
It kinda depends on what you have done to your device, if it's stock then sync or doze could be the problem
Click to expand...
Click to collapse
Sync isn't on for most apps I have. Everything is stock other than having magisk installed. Like I said oddly battery life and phone speed are great until 48h mark or so. I'll just have to work on narrowing it down from apps and stuff. Gboard isn't under any optimization settings. I can't remove it even with system apps enabled. Because if it's just cause the app is being dozed I would like to remove it.

cgibbons51 said:
Sync isn't on for most apps I have. Everything is stock other than having magisk installed. Like I said oddly battery life and phone speed are great until 48h mark or so. I'll just have to work on narrowing it down from apps and stuff. Gboard isn't under any optimization settings. I can't remove it even with system apps enabled. Because if it's just cause the app is being dozed I would like to remove it.
Click to expand...
Click to collapse
Sync is either on or off. I don't believe you can select certain apps, atleast I'm not aware of this as I just turn it off unless I need updates
Is the battery dead or is it being charged over the 48h.
If the apps being forced to sleep it has the tendency to lag and be unstable (stuff I noticed with my s5 before this phone)
Have you tried another keyboard? (I use SwiftKey and have had no lagging issues unless I messed with stand by apps via developer options)

ivoe said:
Sync is either on or off. I don't believe you can select certain apps, atleast I'm not aware of this as I just turn it off unless I need updates
Is the battery dead or is it being charged over the 48h.
If the apps being forced to sleep it has the tendency to lag and be unstable (stuff I noticed with my s5 before this phone)
Have you tried another keyboard? (I use SwiftKey and have had no lagging issues unless I messed with stand by apps via developer options)
Click to expand...
Click to collapse
Haven't tried another keyboard like I said it's not just the keyboard the apps also seem slow but the keyboard is also slow. The battery is fully charged at the time of the slowness. Sync I see for multiple apps overall.

davidk21770 said:
Could be an app leaking memory (not properly returning it when it's no longer needed). Have you added any new apps recently? Try freezing them.
Or perhaps a bad app update?
Click to expand...
Click to collapse
This is what I guess.
Some rouge app.
I'm running 10.3.0 and my phone is stable. No slowdowns and no reboots.
It will stay up for weeks if I let it.
Normally I reboot after a few days, just because.

tech_head said:
This is what I guess.
Some rouge app.
I'm running 10.3.0 and my phone is stable. No slowdowns and no reboots.
It will stay up for weeks if I let it.
Normally I reboot after a few days, just because.
Click to expand...
Click to collapse
Well that's good news we are on the same update. Do you have magisk? Or anything

tech_head said:
This is what I guess.
Some rouge app.
I'm running 10.3.0 and my phone is stable. No slowdowns and no reboots.
It will stay up for weeks if I let it.
Normally I reboot after a few days, just because.
Click to expand...
Click to collapse
Does clash of clans, cod mobile, or old school runescape run on your device? Or do you get blackscreen?
Seems it only happened on the new 10.3.0 / 10.0.3
It use to run fine on older 10.0.0
I think it could be the "backup" since it broke these apks into parts.
Its kinda annoying because I haven't been able to use these in over a month.
And OnePlus is in hiding due to the cornavirus.

It is the gboard sometimes and it usually starts to happen wit whatsapp and Instagram
It's the gboard it's hide arrow is sometimes visible even if you're not using now I don't know if this happens on your phone but using whatsapp or Instagram(nightly) whenever you go to Home screen from typing a message there's a small arrow that will appear at left bottom that collapses the keyboard. also there's a delay in status bar pull down sometimes whenever the problem latter mentioned starts to occur.

cgibbons51 said:
It seems after about 48 hours of up time. The phone begins to lag extremely bad. Mostly when I first start typing it'll take 3 seconds or so for it to finally catch up to my typing. This happens Everytime I use the keyboard after those 48 hours or so. Apps seem to open very slowly as well after this time. A reboot seems to fix it and it runs fine after that until then. I've tried about 3 different kernels and face the problems with everyone. Not seeing any odd battery drain either. Just curious as to what would be causing this. Only module I have installed is google framework (for the dialer)
Click to expand...
Click to collapse
This same issue happens with me after every 48 hours of up time ussualy my spotify lags and i have some.seconds of delay in unlocking my phone

cgibbons51 said:
It seems after about 48 hours of up time. The phone begins to lag extremely bad. Mostly when I first start typing it'll take 3 seconds or so for it to finally catch up to my typing. This happens Everytime I use the keyboard after those 48 hours or so. Apps seem to open very slowly as well after this time. A reboot seems to fix it and it runs fine after that until then. I've tried about 3 different kernels and face the problems with everyone. Not seeing any odd battery drain either. Just curious as to what would be causing this. Only module I have installed is google framework (for the dialer)
Click to expand...
Click to collapse
Just Remove that magisk module and tell the result ..