So I recently was asked to try troubleshooting a phone that was randomly rebooting (specially when receiving calls) and I tried to the best of my knowledge (which is pretty much non-existent) identify what was triggering the behavior, but it really seems random since it happens when answering calls, using apps or simply navigating through the launcher. The said phone ended up been a china-phone (and a really cheap one) which lead me to think that it was some sort of hardware issue, but I'm not sure how I could find it out.
Anyway, I tried getting the logcat using ADB so maybe I could get an idea of the reason of the rebooting, but I really have no idea on how to interpret the results I got. So if anyone could help me I'd really appreciate.
Here's the log: http://notepad.cc/share/i68PoHioTf
These restarts are likely to be because of insufficient Ram or Storage.
Check your ram manager and storage availability. Uninstall some big apps and check the results.
Related
Ok, so I have a rooted Vibrant on stock firmware and I've been having a problem with my screen becoming unresponsive. It originally happened on a smaller level when the phone was newer and unrooted, however the problem has gotten much worse. I've done a factory reset of the phone along with a nandroid backup of it before the problem was severe, yet it comes back just as strong.
I already went through the problems with the no wake from setcpu, even thought it was my lock screen becoming unresponsive until I disabled it with NoLock. Also, I have the Logcat live wallpaper, and usually when you tap the screen, you can see the system processing the information, however when the problem occurs there is no response on the logcat live wallpaper. The phone doesn't freeze at all though. All the soft keys still work perfect as do the volume and power buttons.
Any ideas, tips, suggestions that might help me narrow down this problem? Could it be from a bad version of busybox? Autokiller maybe? I have it set to strict(was previously on aggressive) but no change. Maybe Autostarts is causing something to freeze up. Thanks for any help. Seams like these phones have alot of wake up issues.
I would reflash back to stock with Odin and see what happens when you don't have task killer, set CPU, etc. Also, be careful with autostarts
So I removed Autostarts and rebooted, same deal. I did a factory reset and still the same. I just unrooted a few minutes ago and the problem seams to have gone away. I'm gonna leave it like this for a bit without installing any apps and see what happens. Is it possoble I have a bad root.zip file or bad version of busybox? Doesn't make sense to happen when I have root, then go away when I don't. Any reason it could cause this? I'm really close to sending the phone back, but don't want to waste my time if it's just a bad root file or user error.
Well I don't know for a fact, hopefully someone more knowledgeable can chime in. Maybe when you are unrooted, changes made by autostarts no longer have the permissions to affect anything. Personally I would use Odin (have done it twice already) and start from scratch. But then you risk accidentally screwing up the phone if something goes wrong.
I removed Autostarts and rebooted just to make sure the changes took effect though. Even did a factory reset. Those removed all apps that required root access and the problem was still so bad it took me an hour to get the screen responsive again. Once I did get into my phone I booted into recover and unrooted. Restared the phone and now the issue seams to have gone away. Touch screen is very responsive now which leads me to believe it was something that had to do with the root file i'm flashing, or possibly busybox. Very very strange.
Hopefully someone much smarter than me could give some insight as to what could potentially cause the touch screens to just stop recieving signal. It's just bizarre that the phone continues to run fine, just not the screen.
I'm getting tired of this annoying problem. Four times it had happened to me and each time I reinstalled the phone software with the pc companion. It doesn't matter whether I'm not rooted (the first two times) or rooted. It kept on occurring. SMSes don't come in while others seem to be working fine, phone, internet, etc. I've tried restoring the sms related things using titanium back up but yet it seemed that the only remedy is reinstalling. Thought this time, I got an idea of may cause this. Each time it happened, I seem to be coming out from plane mode for the second time since the software installation. Going to try that now. But in the mean time, any ideas what may be wrong or if any of you experience the same problem?
Hi, i've had the same pb, it seems coming from lack of memory, if you got the little hard drive icon with the red exclamation dot, it means you don't have enough space free, and sms aren't received. So the solution, after all, is to desinstall some of your apps to get rid of that icon and finally a little test is to, when you've done that, send a sms to yourself and see if it works again.
hope it helps.
Well that's a huge possibility as each time it happens, that warning has pop out. But I'm sure each time the warning of low storage come on, it still has at least 10 mb. How can 10 mb not enough for texts?
Well i don't really know maybe some configuration, but i can assure you that it is one of the cause: i did a simple test, on the edge of 10mb i installed an app from the market, then the icon showed up and no sms could be received. after desinstall that same app, icon disappear, and sms was received.
I just noticed it so i try to always have this 10mb amount of memory... i just do with it, maybe someone who understands better how it works could help more than me
i have different problem. after root i cat receive nor send MMS.. working like charm without root. x10mini, 2.1 firmware.
i have no clue why
Thank you for reading. I feel really stuck and though I've tried cannot solve this on my own.
The Problem:
When my phone crashes, the logcat apps that are happily recording the events get force closed along with it, and the buffer is lost forever. I seemingly have no way of recording the actual crash event so that I can research the problem.
Possible Solutions, Unfounded:
So I guess what I need is a logcat app that writes the events to file as it's reading (none seem to offer this, only saves manually) or a way to read the internal log after the crash occurs.
Crash Description:
When it crashes, I get a few short successive vibrations, then a lot of lag between a few seconds to a minute, then (if I'm lucky) the screen goes black for a few seconds and then a sort of an instant reboot occurs where I am at the home screen and all the widgets/icons are loading again and all the programs running a moment ago are not open, and any programs normally loading on a startup will start. It always will say the Sim Card has been removed and I must reboot. I lose contacts but not network. Sometimes the phone just freezes without going black and the fast reboot occurs after some minutes or not at all.
Background on what causes the Crash:
As you know, the GPS on the Fascinate and other Galaxy S models have serious issues with accuracy. I have tweaked the internal settings (*#*#3214789650#*#*) myself, without modifying system files (I dont think I ended up going that far) in order to produce better results. I did this months ago and havent changed it since.
The tweaks did not perfect it, so for some apps where accuracy is crucial I temporarily use an app called FakeGPS, which allows me to manually set my location while the app is running. It worked fine. After I updated about 12 apps at once, FakeGPS included, now whenever I run that application the phone crashes as described above.
At first I thought it was just the new version of the App, so I tried a different one that did the same thing. But it also crashes in the same way. I reinstalled both, still crashes.
I am using firmware 2.2. My phone is rooted. I'd be happy to answer any questions.
Really appreciate even just a point in the right direction.. I wouldnt be afraid to poke around the filesystem if need be.
Thank you!
Sent from my SGH-T959D using XDA App
so i'm guessing this is a result of me freezing something via TB or disabling something via app manager but i've been getting occasional (like every 3rd call or so) crashing of com.android.phone.
it's more of an annoyance than anything as it just makes the screen go blank sometimes so i can't engage the phone during a call (usually when the call has ended and i'm trying to hang up) until the process reboots itself.
anyway, before i spend a ton of time trying to figure out which process, exactly, i froze that is causing this problem i thought i'd ask in case someone else already knew.
i didn't get crazy with the freezing either... just the obvious bloat stuff.
any help much appreciated. thanks!
(i'm on vzw, rooted w/ clockwork btw. stock rom though)
E/ApplicationContext( 320): Couldn't create directory for SharedPreferences file /data/data/com.google.android.gsf/shared_prefs/CheckinService.xml
Is what logcat shows me as a main issue. (Along with other related java stuff errors that seem to be with the google checkin service stuff?)
Now I dont know if this is the cause for m G1 rebooting constantly now. It only happens if I have Wifi or 3G on. Now if I am in airplane mode, things seem smooth and no reboots. Moment it has internet. Logcat starts scrolling and the checkin one pops up way too much. So figured I would ask people where who may be more skilled at knowing this issue and how to solve it. Thanks. =)
(Also its possible its rebooting due to low memory after it keeps trying and trying to do all this stuff?)