i use to use codename android build 3 and im currently using provision mod. i was wondering why does it randomly reboot on a certain time? is there a setting that i should be looking at?
Your phone shouldn't be randomly rebooting, at least on the "stable" ROMs out now. Try to catch a logcat of what is happening. The app aLogcat, I believe, will write to your microSD.
epyonhell said:
i was wondering why does it randomly reboot on a certain time?
Click to expand...
Click to collapse
Wait?? Are you saying that your phone reboots at the same time every day?? If so that is not random. lol Some clarification would be good.
how would i find this problem on the log?
is alot of words in the txt
should i just clear it and wait until it just restart?
Trying doing a factory reset in recovery and wipe data, cache, dalvik cache and format system. Then re flash the rom
Sent from my SGH-T959V using xda app-developers app
Install aLogcat, figure out how to have it dump the log to your microSD, then, when it crashes, upload the last hundred lines or so to one of the paste-this websites and link it here. I think there are a lot here that would take the time to look at it and give you any insights they might have.
here you go
heres the log
That looks pretty normal, perhaps just the "boot up" portion of the log? Was that the last that was captured when you had a crash? I may not have been clear -- we'd need to see what happened just before the crash. Basically start up aLogcat writing continuously to the microSD, then look at the "last" written when you come back after a crash.
AH! My mistake -- you need aLogrec to record to the microSD.
jeffsf said:
That looks pretty normal, perhaps just the "boot up" portion of the log? Was that the last that was captured when you had a crash? I may not have been clear -- we'd need to see what happened just before the crash. Basically start up aLogcat writing continuously to the microSD, then look at the "last" written when you come back after a crash.
AH! My mistake -- you need aLogrec to record to the microSD.
Click to expand...
Click to collapse
it crash when i was driving while i have the phone charge and listening to music (poweramp) with headjack connected
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.
Recently I've been noticing that the stock launcher always seems to restart when coming out of another app. For instance, I might go into Gmail for a few seconds, and when I press the home button, I get the white HTC screen then a loading screen for the launcher. So I have to wait like 15 seconds before actually seeing my home screen when I was just there seconds before!
Is anyone else having this issue?
I tried switching to Launcher Pro, but I got similar issues there, where all the icons would have to reload individually on the screen when pressing the home button. And it was a big laggy (more so than the stock launcher).
I had that same problem but that was because I accidently moved the sense launcher to my sd, after moving it back it stopped also look to see if any of the sense programs like people, browser etc we moved cause they can also cause Sense to restart if not stored on phone.
Sent from my HTC Sensation 4G using Tapatalk
Nope, they're all on my phone. Just double checked.
Having same problem but it's intermittent. I also asked a couple of other people and they are having the same problem.
It's really annoying. I don't always have quick access to apps because of this. And running another launcher doesn't help. Hopefully this is fixed in the OTA update, whenever that'll be.
bretac said:
Recently I've been noticing that the stock launcher always seems to restart when coming out of another app. For instance, I might go into Gmail for a few seconds, and when I press the home button, I get the white HTC screen then a loading screen for the launcher. So I have to wait like 15 seconds before actually seeing my home screen when I was just there seconds before!
Is anyone else having this issue?
I tried switching to Launcher Pro, but I got similar issues there, where all the icons would have to reload individually on the screen when pressing the home button. And it was a big laggy (more so than the stock launcher).
Click to expand...
Click to collapse
I have found that turning off the Fast Boot feature and restarting has pretty much eliminated this problem.
Thanks rorycs! That seems to have done the trick.
Any ideas why fast boot was causing the issue in the first place?
bretac said:
Thanks rorycs! That seems to have done the trick.
Any ideas why fast boot was causing the issue in the first place?
Click to expand...
Click to collapse
I have no idea... I can only guess that Fast Boot caches some data and that when the data is changed by a new app install/delete or some other saved data it has to rebuild the cached data each time before reloading .... Just a guess....
Sent from my HTC Sensation 4G using XDA Premium App
rorycs said:
I have no idea... I can only guess that Fast Boot caches some data and that when the data is changed by a new app install/delete or some other saved data it has to rebuild the cached data each time before reloading .... Just a guess....
Sent from my HTC Sensation 4G using XDA Premium App
Click to expand...
Click to collapse
I've tried and, yes, it helps a little but it still happens!
So, I wonder when HTC's going to fix it? (I don't feel like doing a hard reset!)
I tried reformatting my memory card and also I no longer use the htc task manager to "kill all" seems to be working for me so far.
ak29 said:
I tried reformatting my memory card and also I no longer use the htc task manager to "kill all" seems to be working for me so far.
Click to expand...
Click to collapse
Hi since this evening I have the same problem. The first few weeks I did not have any problem with my sensation. This afternoon I applied a display protector and now he is starting up again and again.
Coincidence probably.
Where can I find the fast reboot mode> I can't find it on my (dutch, vodafone branded) phone.
Thanks
Usually the sense UI closes itself when the phone runs out of RAM, that's why it happens when you exit an app. Seems like also the fast boot option uses a bit more RAM so it makes the sense restart more often. Hope I helped.
Yeah mine has started restarting recently also.
I stopped fastboot but still does it. This is extremely annoying as it usually happens when I want to make a call or send a message and have to wait while it restarts.
Sent from my HTC Sensation Z710e using XDA App
I took off my screen protector hoping that that was the cause of all problems but it wasn't. Too bad, also formatted my sd card again. Hoping that that suggestion I found here on XDA works... so far so good...
Edit; so far still good it only rebooted once while it was in my pocket... working trick?
snah65 said:
I took off my screen protector hoping that that was the cause of all problems but it wasn't. Too bad, also formatted my sd card again. Hoping that that suggestion I found here on XDA works... so far so good...
Edit; so far still good it only rebooted once while it was in my pocket... working trick?
Click to expand...
Click to collapse
Pffft; I thought it was solved but today all misery started again, reboot after reboot, when i use my video cam it stops working and I have to wait till its working again. That costs me today a lot of footage from my kids at the carnival.
I hate it when things don't work.
So far i tried:
Taking of screen protector
disable fast boot
wipe and format my SD card.
Someone any suggestions? Will a factory reset work?
Thanks
snah65 said:
Pffft; I thought it was solved but today all misery started again, reboot after reboot, when i use my video cam it stops working and I have to wait till its working again. That costs me today a lot of footage from my kids at the carnival.
I hate it when things don't work.
So far i tried:
Taking of screen protector
disable fast boot
wipe and format my SD card.
Someone any suggestions? Will a factory reset work?
Thanks
Click to expand...
Click to collapse
Too bad! Brought my sensation to the shop and they did an system update with new software, phone was working for one day and now the **** started all over again, it just stops working randomly.
When i take a picture it stops, when its in my pocket it stops... I hate this!
I will bring it back to the shop again now for a hardware check, probably that will cost me two weeks.... I just have my phone one month......
I came to this thread lookling for a permanent fix to the loading screen but unfortunately i did not find that. I can offer a temporary fix, which certainly is not what we want but something is better than nothing.
Go to manage apps, all then to htc sense and delete data. That will correct the problem for a while. Unfortunately u will look te wallpaper and apps on the screen and u will have to put them back.
Guys, come on you have to search a little better for the answer.... but here you go anyway:
There are 2 options I have found that will work. I have been using the first option for months now with no issue or problem. Sense keeps restarting when it gets low on memory so the system swaps it out. You can choose your fix from the 2 options below. The first one apparently changes the way the system handles the Sense launcher and keeps it loaded much better - it is the option I use (I have found that when you exceed about 420MB used for your apps then the next option will work better). The second option simply stops the system from swapping the Sense launcher out of memory completely. Both of these require you to be rooted and to modify "build.prop" which is found in the /system folder.
If you are not comfortable with this edit make a Nandroid Backup first!!! (If you screw it up your phone may not boot)
1. Make a backup copy of "build.prop" (I simply copied it and renamed the original to "build.prop.old" and left it in the /system folder)
2. Edit "build.prop" with a text editor (you can use Astro or ES File Manager)
3. Scroll all the way to the END and add one of the following lines as the LAST LINE in "build.prop"
Choose ONE of the following lines and add it exactly as typed here:
ro.HOME_APP_ADJ=0
ro.HOME_APP_ADJ=1
4. Save your edited "build.prop" and reboot.
That's it. Enjoy!
*NOTE: I am not responsible for any damage you may do to your phone by attempting this mod or for any errors that may occur as the result of editing system files.
PLEASE hit THANKS if I helped you!
Mine only happen when im using widget sense friend stream. Not sure why it happen only during scroll the widget friend stream others app did not trigger the restart htc launcher..
Sent from my HTC Sensation Z710e using XDA App
try ARHD with No sense. Won't have such annoying problem happen again.
although the widget in Sense is nice, but with GO launcher and its widget in custom skin, feel satisfactory. at least it save ram and stop restarting which really annoy me.
Just flashed cleardroid and keep getting this message about every 2 seconds. Any ideas? Phone will not let me do anything, keep getting this popup over and over.
You check the md5 or the ROM package? And full wipe before install? Wipe and Reflash to see if happens again? I'm sure you probably thought of that, just covering all bases before anyone goes all out on an obscure solution.
Sent from my Inspire 4G using XDA App
This may be 100% off base. But a sweep of the Google-verse has pointed mostly in one direction.
It seems most people point the finger at a Google contacts sync issue.
1. Had you gotten through the setup wizard on the first boot?
2. Would you have Google contacts it would be syncing with your phone?
3. If yes and yes then humor me for a sec and try this.
Reflash CD doing a full wipe in the process. Start the phone for the first boot, and *DO NOT* set up your Google account. See if the problem is gone. Then set you account in the settings menu. Let it sync up. See if problem comes back.
I had this issue and saw a couple of others, in posts saying they "could not post shots as their phone would not take them"
I. Get "screenshot HD". This let's you take screen photo's. If you are getting the warning in the pic you know with the normal camera they are blank.
2 Quickpick. The pics won't show in the builtin gallery. You can freeze or remove it and use QUOTE. QP. I tried making it the system one but had issues so it's just in with the apps. I made screen shot HD a system app, you don't have to, but it needs root access to work .
The picture below is proof. I tried a phone save and the message appeared, you can see. I took and posted with the above.
I've gone from rom to rom to try and get rid of this but no luck. Thats why I'm sure it's a bug. I'm going to reboot and do a logcat .
Hope it helps someone.
zerosum0 said:
I had this issue and saw a couple of others, in posts saying they "could not post shots as their phone would not take them"
I. Get "screenshot HD". This let's you take screen photo's. If you are getting the warning in the pic you know with the normal camera they are blank.
2 Quickpick. The pics won't show in the builtin gallery. You can freeze or remove it and use QUOTE. QP. I tried making it the system one but had issues so it's just in with the apps. I made screen shot HD a system app, you don't have to, but it needs root access to work .
The picture below is proof. I tried a phone save and the message appeared, you can see. I took and posted with the above.
I've gone from rom to rom to try and get rid of this but no luck. Thats why I'm sure it's a bug. I'm going to reboot and do a logcat .
Hope it helps someone.
Click to expand...
Click to collapse
Get a file manager with root access like es file explorer.
Go to /data/media/0/Pictures/ folder
Back up your pictures if there are any
Go to /data/media/0 folder and delete Pictures folder.
Did that . Still got the message
zerosum0 said:
Did that . Still got the message
Click to expand...
Click to collapse
Wipe cache or do these commands in terminal emulator:
su
restorecon -FR /data/media/0
Did that twice when I read SU's piece on SD card problems. Did a full factory reset and changed roms. The changing rom solved it for a few days then it started again.
As for cache wiping im allways doing it. I moved some system updates to the rom, yesterday and did full cache wipe
There you go
I appriciate you sticking with this. Id love to solve it,or rather you to, as I CANT!
Oops typo!
you entered command wrong - must be restorecon
Redone
zerosum0 said:
Redone
Click to expand...
Click to collapse
There is a space between -FR and /data...
Ok
No luck. Im happy with it as is anyway. I can take screen shots and now video. Nothing else has ever been affected. I can see and access my memory as it is. I tried all the things on SU's piece when it was posted. I dont and never have thought that it's the same thing as ive none of the problems he lists. The phone still takes screenshots the old way, but they are grey squares. Gtg gf wants me
I'm having the same problem. Can't take screenshots with the same error message.
Cuttooth said:
I'm having the same problem. Can't take screenshots with the same error message.
Click to expand...
Click to collapse
I solved it with a complete wipe, Inc data, apps. Lot of messing around but phones back to normal.
Sent from my Nexus 5
My phone learned a new trick last week: launch an app, and the screen turns dead black after the app's splash loading screen.
It doesn't happen with every app or every time certain apps are launched, but if it is going to happen, it is always just after an app loading screen and before the app itself would be displayed. It never happens on a system or preference screen, or in an app without a splash animation.
Button back-lighting, volume control, and haptic seem to remain active and respond as normal, but the app seems to be locked into the foreground with a black screen, and can't seem to do anything to stop it but reboot the phone via power button hold.
I'm running CM 12.1 nightlies on a Verizon S3. I've been updating the CM nightlies, well, nightly since last week in hopes a fix would be included in one of them, but I'm not sure this is a ROM issue. I've also wiped Dalvik/Cache several times, with and without a ROM update. I saw black screens on some phones were caused by theme window animations, so I've disabled these in CM, but hasn't made a difference.
Just a guess on my part, but if the nightlies do not fix this you may end up needing to do a clean flash. Hopefully you do not have to go as far as formatting /system.
dawgdoc said:
Just a guess on my part, but if the nightlies do not fix this you may end up needing to do a clean flash. Hopefully you do not have to go as far as formatting /system.
Click to expand...
Click to collapse
Thanks, but wouldn't a "clean flash" require wiping `system`?
I'm wondering whether this is possibly a hardware problem too: this phone's been pretty beaten up, not sure how to determine that though.
deesto-xda said:
Thanks, but wouldn't a "clean flash" require wiping `system`?
I'm wondering whether this is possibly a hardware problem too: this phone's been pretty beaten up, not sure how to determine that though.
Click to expand...
Click to collapse
I'd wipe everything, including system and your internal SD card, then you'll know for sure if it's hardware related or not.
deesto-xda said:
Thanks, but wouldn't a "clean flash" require wiping `system`?
I'm wondering whether this is possibly a hardware problem too: this phone's been pretty beaten up, not sure how to determine that though.
Click to expand...
Click to collapse
Yeah, I was thinking internal sdcard, like @BadUsername said.