Charge Hot Rebooting - Verizon Droid Charge

Hello,
Today is my 14th day with the device and this device seems to be hot rebooting itself. Its not a complete reboot but a hot reboot that take 1/3rd the time to start up. Attached is the Alogcat. Anyone have any ideas? Should I swap the device out?
There is no reason for a reboot. I am not running any applications at time of reboot. And it happens randomly.

I didn't see anything in the logcat showing what the problem was. It looked like alogcat didn't pull everything, or maybe something got lost when it hot booted. Could you try to get a logcat via adb if it happens again?
Code:
adb logcat > logcat.txt
Run the above and wait a little bit (10-15 sec) and then press ctrl+c to stop as it will just keep outputting the log to the file.

now i notice that only 3 apps are showing in my downloads in the market and i have around 20 downloaded applications. what can cause this?

do you use any app2sd+ technique (script, application, ...) ?
this happened to me in one ROM it was app2sd+, specially when i install/uninstall any app
or if i mount the sdcard as drive.

i do not all apps are installed on the phone internal memory.

after installing a new app all my apps showed back up in the market.

Its your setcpu. No profiles
Sent from my SCH-I510 using XDA Premium App

papi92 said:
Its your setcpu. No profiles
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
i dont have setcpu installed on this device. have not done that yet

Related

[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.

Freezing

My nexus s keeps freezing. I have factory reset from a recovery boot, formatted cache and SD. I'm at 2.3.3 and have not rooted.
It will not freeze when it is plugged in so adb debug session doesn't tell me anything.
I have tried alogcat with it set to 15 mins but it usually won't save anything before the phone freezes.
I am not using a custom launcher but it did freeze when I was using launcher pro.
When it freezes the clock stops and I can wake the device up but the screen is non responsive and I cannot unlock it. After the screen is turned off I cannot wake it up again.
Sometimes there is a error triangle but I am unable to see what the error is.
Ideas?
-- Lance
Sent from my Nexus S using XDA App
Sounds like there is something seriously wrong it get it replaces.
Sent from my MattedBlues CM7 Nexus S from the XDA Premium app.

can you freeze your wi-fi calling?

I tried to freeze wi-fi calling in Titanium Backup. But after that I still see this app when I check it in setting-->application-->managing-->running. And just as before, you cannot kill it from running application. Is this normal?
I used bloat freezer to freeze it and my battery life has been 10000000xs better ever since.
Sent from my LG-P999 using XDA Premium App
not normal. i froze it on mine, and my husband froze it on his, both using titanium and i havent seen it running since. perhaps you need a reboot? the app isnt in your drawer anymore, is it?
jayohwhy said:
not normal. i froze it on mine, and my husband froze it on his, both using titanium and i havent seen it running since. perhaps you need a reboot? the app isnt in your drawer anymore, is it?
Click to expand...
Click to collapse
I just took couple of screen shots. This is my first time to link files from dropbox. Hopefully it will work.
here it shows the wi-fi calling has been frozen
https://dl.dropbox.com/u/27291692/g2x/2011-04-28 09.23.55.png
and here is shows the wi-fi calling is stll in running app list
https://dl.dropbox.com/u/27291692/g2x/2011-04-28 09.22.59.png
I cannot see the wi-fi calling app in the application screen. --if that's what you mean in my "drawer"(?)
When you say reboot, do you mean press hold the power button to turn the phone and and back on again? I think I did that last night but apparently it didn't resolve the problem.
p.s. the same thing happens to one of "my account" app as well (the one cannot be killed by manage application in setting)
same case as OP. Froze wifi calling and MyAccount with TitaniumBackup, but both apps still run. (yes they disappeared from the menu, but they are still constantly running)
c19932 said:
same case as OP. Froze wifi calling and MyAccount with TitaniumBackup, but both apps still run. (yes they disappeared from the menu, but they are still constantly running)
Click to expand...
Click to collapse
You should have to reset it... cause i had the same problem i froze My Device and it sent me into this weird force close loop but after i reset the phone it didn't show up in the processes again.
spencersir2 said:
You should have to reset it... cause i had the same problem i froze My Device and it sent me into this weird force close loop but after i reset the phone it didn't show up in the processes again.
Click to expand...
Click to collapse
factor reset? again? well, if that's the only easy option...
btw, I think someone mentioned there is thread that gives a complete of bloatware that could be frozen. But maybe I not good enough at searching, can anyone point it out? Thanks.
tangyoulei said:
factor reset? again? well, if that's the only easy option...
btw, I think someone mentioned there is thread that gives a complete of bloatware that could be frozen. But maybe I not good enough at searching, can anyone point it out? Thanks.
Click to expand...
Click to collapse
No no no i mean like battery pull or turn the power off and on not Factory Reset! and ALL bloatware can be frozen and/or removed if you want! But the only reason you get this weird force close loop is cause you freeze/remove the program, but the process is still running leading to the phone not knowing what to do. Than after you reset it(Not Factory Reset) it wont start up because you have removed the app.
spencersir2 said:
No no no i mean like battery pull or turn the power off and on not Factory Reset! and ALL bloatware can be frozen and/or removed if you want! But the only reason you get this weird force close loop is cause you freeze/remove the program, but the process is still running leading to the phone not knowing what to do. Than after you reset it(Not Factory Reset) it wont start up because you have removed the app.
Click to expand...
Click to collapse
I do not have any FC problem. My problem is simply that, when I freeze the bloats with titanium backup, these bloats would be removed from the app drawer BUT still be running in the background. (this scenario applies to WIFI calling and Myaccount)
I have restarted the phone, factory reset, and tried this on 2 phones already. So I really doubt that would fix the problem.
1 question: what do you freeze them with? Maybe bloat freezer can do a better job than titanium?
just kidding! I went to the menu you are referring to and saw the apps under running processes for me too! This scares me, however since the program is present but frozen, aka can't be actively run, I am ambivalent as to whether it has an adverse effect on battery life. (maybe since it's frozen it is present on the list but won't drain battery?) Also, maybe it's presence there insures that it won't get in the way of an otA
Sent from my LG-P999 using XDA Premium App
Maybe you should try bloat freezer and reply back.
Sent from my LG-P999 using XDA Premium App
jayohwhy said:
Maybe you should try bloat freezer and reply back.
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Or you can use AntTek App Manager(It is free and does the same thing that Bloat Freezer does)
whats the name of the apk in for wifi calling and my account in system/app? im guessing its kineto for wifi calling since it has the same icon but I just wanna make sure
superevo89 said:
whats the name of the apk in for wifi calling and my account in system/app? im guessing its kineto for wifi calling since it has the same icon but I just wanna make sure
Click to expand...
Click to collapse
What program you using? Cause I am using anttek and it shows up as wifi calling for me.
Sent from my LG-P999 using XDA App
I been using root explorer to move apk's outta of the folder and store them on my external sd and save them on my desktop.
I used bloat freezer and it worked like a charm.
Sent from my LG-P999 using XDA App
so just to double check-- these apps dont show up in your running processes anymore?
jsauce75 said:
I used bloat freezer and it worked like a charm.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
please confirm that they don't run anymore
I completely uninstalled it from my phone. If it 'breaks' OTA updates, I'm sure there will be a ROM dump within hours anyway on here, if I'm not running CM7 by then that is.
yea the thing is that, I sometimes want to unfreeze Myaccount or WIFI calling to actually use them. Uninstalling/reinstalling is quite tedious every time

question about rom restarting

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

[Q] Apps launching slow

I am on CleanRom 3.0 right now, fresh install. Now, for the problem. Today while sitting in class I took my phone out to see it was booted into safe mode. So I rebooted it back, and noticed a lot of my downloaded apps were launching 10-25 seconds after I clicked to open them. So, I rebooted again. That didn't work. I cleared cache and dalvik cache. That didn't work. So, I dirty flashed CleanRom 3.0, which still didn't work. After driving and listening to spotify in my car, the apps launched completely fine, and still are. Does anyone know why this is happening? By the way, this happened on my rooted stock rom, that's why I switched roms. I don't know if this could cause any issues, but I do use Directory Bind.
Have you checked if power saver is on?
Another possibility could be a lot of applications running the background and just slowing your phone down.
Check your task manager by holding the home button for about 2-3 seconds.
Yea, power saving is off. And there isn't any apps running in the background when it's ran slow. Most stock apps will launch fast (settings, phone, clock), but downloaded ones won't (I funny, handcent sms). I seriously can't figure out what the issue is. I've even tried messing around with set cpu, but that didn't help.
Sent from my SCH-I535 using xda app-developers app
Try cache mate.
Sent from my SCH-I535 using xda app-developers app

Categories

Resources