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.
So I have done some serious work to fix my overnight and sleep battery drain and have fixed the problem. I had the 4%/hour drain with zero use on TnT Lite/Vegan and CM7 and finally found two things to help.
First is the well know WIFI always on trick that also helps the sleep of death problem. Go to Wireless & Network>Wifi Settings> tap menu and hit Advanced>Change Wifi Sleep Policy to Never. This trick has been documented to work for some and not for others. What was new to me was the second step.
Install Root Explorer and navigate to /System/App...press R/W to mod files and rename the following apps by adding .old to the filename in this order:
Voicedialer.apk (e.g. Voicedialer.apk.old, etc.)
Telephonyprovider.apk
MMS.apk
Phone.apk (do this last as a FC loop may ensue right away)
hard reset and your done. Some of the new ROM's have removed these apps, some have not but regardless they are not needed on a tablet with no radio.
Since doing this I have gone 11 hours unplugged with 2 hours of heavy use and have 66% battery remaining. I would have typically been at 30% before making these changes.
Hope this helps someone.
I just did
I just tried doing your fix. I ll tell you how that goes
Djapatos said:
I just tried doing your fix. I ll tell you how that goes
Click to expand...
Click to collapse
Interested to know your result...
so far so good
jason1332 said:
Interested to know your result...
Click to expand...
Click to collapse
So far so good
I only lost 1% of battery in 1 hour idle no use.
And no sleep of death
Seems to be working
As I follow your methods, disable MMS is OK, but Phone, it give me FC, and I can not escape that windows.
Does I need to follow renaming in order?
Edit: A restart has fixed it.
Yup same here
HTung said:
As I follow your methods, disable MMS is OK, but Phone, it give me FC, and I can not escape that windows.
Does I need to follow renaming in order?
Edit: A restart has fixed it.
Click to expand...
Click to collapse
As first i was like wtf... then i rebooted and no issues afterwards.
Overall, i lose 1% every hour of idle, which is not bad
I just set this up. I will let you know how it works after 6 hours of sleep.
I would make sure people do the phone rename last. It gives a bunch of force close errors, but I held the power button down reset the tablet and double checked to make sure the changes stuck, which they did.
Way ahead of you. I used system app remover and removed all those plus bunch of other things.
I'm assuming the removal of these apk's would prevent you from sending texts and making calls via Google Voice and a SIP client, right?
clankfu said:
I'm assuming the removal of these apk's would prevent you from sending texts and making calls via Google Voice and a SIP client, right?
Click to expand...
Click to collapse
These won't affect Google Voice on your tablet. On your phone however this would do really bad things.
goodintentions said:
Way ahead of you. I used system app remover and removed all those plus bunch of other things.
Click to expand...
Click to collapse
Can you give a list of everything you removed? Thanks
I am using VeganTab 5.1 ROM, but I don't see the apk files that you have mentioned in the \system\app directory.
HTung said:
As I follow your methods, disable MMS is OK, but Phone, it give me FC, and I can not escape that windows.
Does I need to follow renaming in order?
Edit: A restart has fixed it.
Click to expand...
Click to collapse
Added the fc loop and reboot to instructions. Thanks...forgot about that.
shadowhawk2020 said:
I just set this up. I will let you know how it works after 6 hours of sleep.
I would make sure people do the phone rename last. It gives a bunch of force close errors, but I held the power button down reset the tablet and double checked to make sure the changes stuck, which they did.
Click to expand...
Click to collapse
Added to OP, thanks!
Another overnight result
Went to sleep at 55%, woke up G tab 9 hours later with 48% battery...woot!
I had 75% six hours later I am at 70%. Very happy so far with this fix. Thanks OP
Went to system/app and none of those files are present. Am I missing something?
weaselman said:
Went to system/app and none of those files are present. Am I missing something?
Click to expand...
Click to collapse
Hit R/W again to get back to read only...hit menu and save the changes. Force close loop when you return to homescreen...hard reset and your done. Some of the new ROM's have removed these apps, some have not but regardless they are not needed on a tablet with no radio.
antsig30 said:
I am using VeganTab 5.1 ROM, but I don't see the apk files that you have mentioned in the \system\app directory.
Click to expand...
Click to collapse
Running same ROM. I don't have the tablet with me so I can't check. Anyone know if the latest Vegan ROM has this removed already?
Thanks.
mtnbkr said:
Running same ROM. I don't have the tablet with me so I can't check. Anyone know if the latest Vegan ROM has this removed already?
Thanks.
Click to expand...
Click to collapse
Most likely yes...
Since upgrading to ICS ROMs, on several occasions I notice that mediaserver keeps the phone from sleeping FOREVER, takes over 80% of my battery. Contrary to several other reports of mediaserver wakelock, I do not have a corrupted media file on the SD card. The wakelock does seem to happen after using Gallery, however.
The only way to stop that, is to do a “clear data” on the Media Storage package. However this also clears my notification tone and ringtone settings in *all* apps, which is not acceptable.
Does anyone else have the problem, or know a workaround?
jcolinzheng said:
Since upgrading to ICS ROMs, on several occasions I notice that mediaserver keeps the phone from sleeping FOREVER, takes over 80% of my battery. Contrary to several other reports of mediaserver wakelock, I do not have a corrupted media file on the SD card. The wakelock does seem to happen after using Gallery, however.
The only way to stop that, is to do a “clear data” on the Media Storage package. However this also clears my notification tone and ringtone settings in *all* apps, which is not acceptable.
Does anyone else have the problem, or know a workaround?
Click to expand...
Click to collapse
turn off google photo sync in the accounts and sync settings, google?
simms22 said:
turn off google photo sync in the accounts and sync settings, google?
Click to expand...
Click to collapse
Thanks, will try.
jcolinzheng said:
Thanks, will try.
Click to expand...
Click to collapse
Any update on this? I'm having similar issues with mediaserver consuming the battery.
aoberhoferiv said:
Any update on this? I'm having similar issues with mediaserver consuming the battery.
Click to expand...
Click to collapse
Issue seems gone after following the suggestion. But I'd like to test more to confirm.
EDIT: Issue still exists. Even after freezing Gallery and disabling Picasa sync.
So I had another one yesterday, even with Picasa sync turned off. I'm switching off Music sync, hoping that could be the cause...
any new info on this one? my galaxy nexus has the same problem! Running 4.0.4
spinkick said:
any new info on this one? my galaxy nexus has the same problem! Running 4.0.4
Click to expand...
Click to collapse
Still having the problem. Even after I disable music sync...a reboot fixes it but the issue comes back at random times later.
An experiment to try is temporarily poping out your sdcard and rebooting your phone. Maybe something on your sdcard is causing problems. Another experiment is to put your phone in a place you won't touch for a few hours, and reboot it. See if it happens during an overnight test run.
Hello everyone,
Has anyone experienced the bug in 4.4.3 where screen on time is not being logged anymore and the screen does not show up in the integrated battery stats? If yes, is there a fix and if not, will this be fixed?
I want to avoid factory resetting my phone though, so if there is no solution I think I'll just live with it.
Thank you
Spiritreader
Spiritreader said:
Hello everyone,
Has anyone experienced the bug in 4.4.3 where screen on time is not being logged anymore and the screen does not show up in the integrated battery stats? If yes, is there a fix and if not, will this be fixed?
I want to avoid factory resetting my phone though, so if there is no solution I think I'll just live with it.
Thank you
Spiritreader
Click to expand...
Click to collapse
have you tried rebooting? and, do you have root? if so, using a root file explorer, delete /data/system/batterystats.bin and reboot.
Hi,
If you just recently updated your phone, it's possible that the battery stats have been reset, and usually just media server and all those things appear as the biggest battery consumers. If you fully charge your phone it should show the correct usage again.
Hope this works.
Hello,
Thanks for your answers
Unfortunately I haven't rooted yet, but I think I might invest time to do that if it can fix the issue. Rebooting hasn't helped nor fully charging it. It just seems like the OS doesn't even log the display stats anymore, although the bar in the battery monitor for screen on is still there
Hi all!
My Verizon Galaxy S4 (SCH-I545, rooted) hangs for several seconds after completing a full charge. The screen stays black with only the green light indicating the charge is complete lit up in the upper left corner. No reaction to any buttons for about 20 seconds or so. Then if I keep pressing the Back menu button the lock screen appears. This never occurred in the past until I installed Battery Doctor... I know, I know. Now, that is. Battery Doctor was uninstalled a few weeks ago after I read a number of posts/articles about its developer. However while it was installed there were always delays like this when charging. I thought that would stop after removing Battery Doctor, but it hasn’t.
I wondered if Battery Doctor left any unpleasant remnants behind, so I searched the file system with ES File Explorer and I did find a folder with Batter Doctor's apk file along with a number of other files in the same folder. I deleted them all but I still see the same delay/hanging after a charge completes - similar to what used to occur when Battery Doctor was installed.
Does anyone know if this is likely caused by something else Battery Doctor left behind? If so, any info on how to find and remove it? And if not, any other suggestions as to what could be causing this?
Thanks!
Jim
Hi, thank you for using XDA Assist. I don't know if Battery Doctor caused the problem or not. You could ask in your device's specific forum here, http://forum.xda-developers.com/galaxy-s4-verizon if others have experienced the same issue. It may or may not be caused by Battery Doctor. If it continues you could always return the device to stock with odin and start over.
OK. Thanks jd.
Jim
Thread closed.