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?)
Related
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)
Greetings,
I have an HTC Desire running CM7 (Android 2.3.7). Earlier today I was toggling the Wi-Fi and deleting one entry from my remembered networks. At this time, the internal storage was apparently filled to the brim (~30KB left). I don't know if this is what caused it to go haywire but anyway, Wi-Fi is completely broken now. When I turn it on, it stalls for about 20 seconds (causing crashes in all applications that try to use Wi-Fi) and then it turns itself off again. The Wi-Fi icon never appears in the top bar, so it seems like it just cannot initialize it. My remembered networks list is also empty now.
My best guess would be that the full storage at the time caused corruption or inconsistency in the Wi-Fi configuration. So I'm looking for a way to reset the Wi-Fi (preferably nothing else) or just solve my problem in any way.
Oh yeah and the command line doesn't scare me.
Thank you for your time.
EDIT: Message to people from the future having the same problem:
I managed to solve my problem by removing the file /data/misc/wifi/wpa_supplicant.conf using the app Root Browser. If you are going to try this I highly suggest renaming the file, just in case.
Got my Zu a few weeks back. When in stock, this problem occurred randomly and extremely infrequently. Now, the phone is unlocked and rooted and currently in 757 (4.4.2). Now the frequency of the problem has increased many fold. Whats the problem? ... The device just switches off without any notification or alert!! Even when fully charged. I need to switch it back on (with the power button) when I realize it has switched off.
This switch off randomly happens at-least 3-4 times a day. I used the "catlog" app to see if any errors or failures are logged (which may cause the shutdown), but the log entries are so many and so many are generated that they just fly past for me to figure out anything. Is there any specific error that I may have to search for? Any ideas on how to approach the problem and maybe solve it? If it turns out to be a h/w issue, I can send it for service. But I need to ensure that it’s a h/w issue Any help will be greatly appreciated. Thanks!
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.