Related
Hi
I'm frustrated - my Galaxy Nexus just keeps on crashing, randomly. At first, I thought it had to do with non stable Roms like AOKP (build 23 or 25) or Codename Android (1.4.0). So I downgraded to Stock Rom 4.0.2 on my GSM system.
But it still keeps on crashing. With this, I mean that it reboots all of a sudden and I find myself back at the SIM PIN input screen.
With Codename Android and AOKP, it was so, that it hung "deeply". Ie. when I connected it to my Linux PC, nothing at all showed up in the syslog of the Linux system - normally, it shows that "something" got connected. Not even that happened. "Solution": remove battery…
Well… I know that this is a bit slim, but how/where might I start to debug the cause of the crashes?
I don't have any special hardware connected. Most often, it crashes, while I'm typing somewhere (Browsers (different ones: chrome, browser, dolphin), Google Mail, Google Talk, Google+). But it also happens, that it crashes in the middle of the night, when I'm certainly not typing.
How to debug?
About this phone:
My installed apps: on Google Docs or or pastehtml.com — I also tried trimming the list of installed apps down, but either I didn't trim enough, or it was in vain…
Well… As you might guess… I'm totally clueless…
Thanks,
Alexander
If you have the android development tools installed on ur computer, you could try just leaving the phone plugged in while the Logcat view is opened. Logcat displays a whole bunch of debug info which may help you out when the phone suddenly reboots itself.
Also when you downgraded the firmware to stock, did you also clear the cache partition? Have you tried doing a factory reset from the UI? Did you also downgrade your radio to stock? Things to keep in mind.
- chris
Hm.logcat. Most of the time, i am not near a computer, when it cradhes. Is there a way to continually store the logcat output on the device itself?
When i downgraded, i did a cache wipe. I also did cache wipes / factory resets, when i had the custom roms installed.
I also flashed the stock radio, yes. So that is not the reason, i would say.
It is also not related to the keyboard - i thought so first. So i switched from SlideIt to SwiftKeyX. No change. And it also crashes while i am not typing.
Alexander
If I were you, I'd go to complete stock. Stock rom, kernel, and radios. No extra apps and see if it's a hardware issue or not. But that's just me.
Well, loveubuntu, i see what youre saying, i really do, but this basically would mean, that i couldnt use the phone. And what good is a phone, that cannot be used?
I am already back to stock rom, stock kernel and stock radio.
Well if you're back to 100% stock, relocked and not rooted it could be one of two things. Hardware issue or an app.
Well, thanks, but it doesnt help much...
And, actually, it just occured to me, that it is.already known, that it mist be an app. Ive got the same crashes with custom rom/kernel and stock rom/kernel. This shows, that the crash isnt.related to rom/kernel.
But how to debug this? I cannot keep the smartphone connected to the pc to have logcat ru.ning all the time. When i am travelling, i just dont have a pc around...
Any ideas?
well ffs not 24 hours a day. They mean just plug it in and run a logcat while you're using it and try to force a crash. If you can capture a log of what happened when it crashed then you will know what's crashing it.
If you go back to 100% stock (as in, flash Google images) and it still crashes with no apps installed, its a hardware problem.
Uninstall your task killer while you're at at it...
I cannot force a crash - as I said, it happens randomly
As far as crash with no apps installed… Well… I guess it won't crash, because then I won't be using it. That advice really cannot be followed.
It's been suggested to relock and remove root. What would that do? Could that really have anything to do with it? Very hard to imagine.
Oh, why uninstall the Task Killer? Yes, it's installed, but not active (in the sense, that it does not kill any tasks automatically and I also don't usually kill tasks. System also crashed, when I didn't kill any tasks).
alexs77 said:
I cannot force a crash - as I said, it happens randomly
As far as crash with no apps installed… Well… I guess it won't crash, because then I won't be using it. That advice really cannot be followed.
It's been suggested to relock and remove root. What would that do? Could that really have anything to do with it? Very hard to imagine.
Oh, why uninstall the Task Killer? Yes, it's installed, but not active (in the sense, that it does not kill any tasks automatically and I also don't usually kill tasks. System also crashed, when I didn't kill any tasks).
Click to expand...
Click to collapse
re-locking and unrooting will help diagnose the problem as app related or hardware. You may have a lemon.
Also, if you know it's app related, then the solution is easy. Uninstall all the apps and start again. That's why I suggested a factory reset. You can factory reset being rooted and unlocked. You can backup with titanium backup first anything you may need or make a nandroid.
task killers cause these kinds of problems.
Had a very simler problem to this, on stock 4.0.2, tried rooting and installing custom rom to see if it fixed and didnt also lots of factory resets nothing helped! In the end i had to send it off to sammy, got it back same problem , off again they sent it back with the same problem , off AGAIN got it back on friday with ( oddly) a new screen and havent had a problem since.
My advice send it for repair, if its happening with different roms / stock or whatever its gotta be hardware
If you want a logcat that you dont need a pc for use " alogcat" free app from the market, helped me ( mine actually had hardware error on the logcat )
I updated to Jelly Bean 4.1.1 using Eftrant's method and did a complete wipe, re-installed and setup every application/game from the market but I've noticed that when I access places like Apps under Settings menu, using programs like Quick App Manager, the phone freezes or hangs. This problem was pretty bad in 4.1 but 4.1.1 seems to have improved it just a bit (not freezing/restarting as much). I thought that this was an application specific problem but doesn't look like it. Anybody having the same issue and have a solution/workaround?
Just to be clear, when I was running ICS the phone did not have a single instance of Freeze or Restart, I've been using this phone since January, so, it is not a problem with my phone either, just with the Jelly Bean update and the issue doesn't happen all the time only sometimes.
Have you tried doing a factory reset and running it without very many apps to see if it helps?
I have the same problem with Stock 4.1.1. Nothing helps (Full Wipe, No own Apps installed, Wipe cache, etc.). It randomly occurs in Settings/Apps. The Phone freezes and needs 1 Minute - Then "Settings isn't responding. Do you want to close it?"
To reproduce the problem: Slide in Settings/Apps from "DOWNLOADED" to "RUNNING" to "ALL" and back - a few times. Sometime the phone freezes.
Does it freeze at all with no apps installed? Can you pinpoint the freezes to a certain type of thing you're doing?
martonikaj said:
Does it freeze at all with no apps installed? Can you pinpoint the freezes to a certain type of thing you're doing?
Click to expand...
Click to collapse
No, unfortunately not. With absolutely no apps installed the problem occurs less times but it is not gone. I think there is a bug.
---------- Post added at 09:36 AM ---------- Previous post was at 09:28 AM ----------
Can anyone try to reproduce the issue? It seems to occur only after a full wipe and some apps installed.
Slide in Settings/Apps from "DOWNLOADED" to "RUNNING" to "ALL" and back - a few times. Sometime the phone freezes.
It also happens when you try to clear data/clear cache of a certain application like Browser, Gmail, Gallery, or any of the stock apps. A mentioned earlier the frequency of the phone freezing reduces if there are no applications installed. This definitely seems to be a bug that occurs when a lot of data about all the applications is being pulled at once. You can replicate the issue if you install an app like Quick App Manager which scans all apps when the app is started.
wessonster said:
It also happens when you try to clear data/clear cache of a certain application like Browser, Gmail, Gallery, or any of the stock apps. A mentioned earlier the frequency of the phone freezing reduces if there are no applications installed. This definitely seems to be a bug that occurs when a lot of data about all the applications is being pulled at once. You can replicate the issue if you install an app like Quick App Manager which scans all apps when the app is started.
Click to expand...
Click to collapse
Thank you for the Info!
It was happening on my GN too. But now it's fine.
I used to flash 4.0.4 factory image and OTA to 4.1.1 many times(more than 6). It was fine without any app installed from google play. After about 60 apps, freeze in setting-apps. Jump in an app detail, back, in another, freeze.
Now it' OK. But unfortunately, I don't know which setting fixed it. I try a lot.
Do you use flipboard? Or any large number of fragment files in sdcard/android/ ? Try to clean. Set flipboard to use internal storage.
If freeze again, er.....the last method. wipe cache, factory reset, flash 4.0.4, install apps and then OTA 4.1.1. Instead of OTA 4.1.1 and then install apps.
hope you can understand my English, and this can help you.
bynature said:
It was happening on my GN too. But now it's fine.
I used to flash 4.0.4 factory image and OTA to 4.1.1 many times(more than 6). It was fine without any app installed from google play. After about 60 apps, freeze in setting-apps. Jump in an app detail, back, in another, freeze.
Now it' OK. But unfortunately, I don't know which setting fixed it. I try a lot.
Do you use flipboard? Or any large number of fragment files in sdcard/android/ ? Try to clean. Set flipboard to use internal storage.
If freeze again, er.....the last method. wipe cache, factory reset, flash 4.0.4, install apps and then OTA 4.1.1. Instead of OTA 4.1.1 and then install apps.
hope you can understand my English, and this can help you.
Click to expand...
Click to collapse
"install apps and then OTA 4.1.1. Instead of OTA 4.1.1 and then install apps" fix the problem but i want to use a Custom ROM....
The Issue is listed on: code.google.com/p/android/issues/detail?id=35101
It's weird. Such an easy freeze and so few reports about it.
bynature said:
It's weird. Such an easy freeze and so few reports about it.
Click to expand...
Click to collapse
Well I have the same problem. It generally happens to me after I delete apps via settings...apps.
enough to make me quit cell phones
Happens on my nexus constantly. Verizon has sent me two replacements, which I sent back because they did the same thing, with or without any apps installed. All have had 4.1.1. This problem does not occur on 4.0.4, which I have flashed to the devices after upgrading to 4.1.1 just to run some tests. There is clearly a bug in the vzw 4.1.1 update. It is very, very frustrating and happens regardless of the apps we try to force close, clear cache, etc. They do not have to be google apps as someone has posted. I can easily duplicate the issue and it has been witnessed by two different corporate locations across four reps. I hope we can get a flashable 4.1.2 update soon, I've tried a 4.1.2 rom briefly and have not had the phone freeze at all.
Happens to me. I re flashed the rom and all went wrll
Swyped on my Galaxy Nexus running AOKP with Franco Kernel
Logcat/dmesg or it didnt happen.
Sent from my i9250
bk201doesntexist said:
Logcat/dmesg or it didnt happen.
Sent from my i9250
Click to expand...
Click to collapse
Funny.
Though it seems that logcat doesn't even log the problem, the phone is frozen solid for a couple minutes when it does freeze. I'll pull a logcat.
Sent from my Galaxy Nexus using XDA Premium via Verizon Wireless
del
And dmesg?
You people think its easy to troubleshoot these "freezes", and come in here without anything other than "i've tried a few roms and it still happens"
Sent from my i9250
del
This is quite annoying
Every time I turn on my phone, all of the apps that start when my phone boots force close. I'm not able to send a text or even use the dialer. I'm able to browse my home screen, but when I try to run an app, either it will run for a bit and then force close, or it will close as soon as I open it. The battery I have is bad, which results in my phone turning off randomly, I know it's a bad battery because I've had this issue before and replacing the battery solved it.
Today I tried to use soundhound and while it was "listening" the phone decided to turn off. No surprise. However, when I rebooted it, none of my apps were able to run. I get the "Unfortunately, x has stopped working..." and am forced to close the app. I'm not able to do anything on my phone. I can still receive texts, I'm unable to respond to them. I should be getting a new battery in the mail any day now, and I'm hoping it will solve the issue.
I'm running cm9 beta 1. I've cleared the cache and the d-cache.
Could the battery be the cause of this? Any suggestions?
I'm gonna try to temp boot to EL29. Mobile ODIN doesn't work, am I able to use ODIN 1.85 on my computer instead? I would install the direct boot v3 file under the PDA option right?
EDIT: The apps seemed to have worked when under a temp boot of EL29. I'm gonna do a fresh install to see if that does the trick
I doubt its the battery. Maybe a corrupted install. Download files to pc if possible then xfer to phone. Verify md5 before flashing. You can get software from sourceforge if needed.
The fresh install did the trick. Still not sure how this happened, but whateva. I don't need a new phone
That's good sometimes you just get a bad flash or flash a mod that just messes things up. I have flashed things that worked perfectly for others and my phone got jacked. Its all part of the game. I keep a recent one click on my laptop just in case.
It sounds like when you installed your rom you forgot to wipe data/factory rest or when you restored app backups you installed data with system apps from a TWiz rom. When restoring backed up apps you can usually restore data for system apps from TWiz > TWiz or AOSP/CM > AOSP/CM as long as they are on the same build ie ICS > ICS or JB>JB etc. You can restore data for user apps safely regardless of rom they were backed up on. But the FC issue comes from incompatible system data it screws up the system process and causes apps to FC when it tries to load the data
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
I'd been using FF18 for quite a while without incident, but after upgrading to FI27 (not OTA, via the one-click method), Google Play is hanging the system immediately after successfully downloading and installing any given app. It puts me on the usual page allowing me to open the app, I press open, and wham, the system freezes until it reboots automatically about a minute later. The app that I installed then runs fine.
(In testing this several times, I should mention that one time I actually was able to open an app I just installed, but it hung about 10 seconds in, and the system rebooted as usual. It ran fine after that.)
I've searched around a bit for this and see that I'm hardly the first to encounter this issue. Sometimes it occurs when no recent update has been performed at all. Unfortunately, I haven't really found a solution yet. The best I've seen is to delete the data for Google Play and Download manager, and rebooting, which I've done to no effect. I've also tried uninstalling Google Play, but I think in this case that just leaves me with the same version that I had, the one that came with FI27 (in any case, that didn't help either).
How does one go about troubleshooting this type of problem? I suppose wiping out the phone and starting over would fix it, but I was hoping for more of a surgical rather than nuclear approach. After all, on a PC, you don't reformat when you have a problem with a program.
Have you tried wiping the data for google services framework?
sent from MY BAD A$$ ET4G
patrao_n said:
Have you tried wiping the data for google services framework?
Click to expand...
Click to collapse
I hadn't, but I did just now (there was just over 4MB there), along with a reboot following, and unfortunately it didn't help. Maybe Google Play services too, or something else?
Try deleting data for anything that says google play.
sent from MY BAD A$$ ET4G
You stated you upgraded so I'm assuming you didn't do a fresh install. Even if you did do a fresh install, restoring data & apps from an older version could cause problems. You should try a fresh load and work your way back from there.
Edit: Saw you did the one-click. Still think you should try a full wipe and try it again with a fresh load to see how it goes.
patrao_n said:
Try deleting data for anything that says google play.
Click to expand...
Click to collapse
I've now done that (though one or two had no data), along with the framework one you mentioned earlier, followed by a reboot, but it still happens. Arghh!
tdunham said:
You stated you upgraded so I'm assuming you didn't do a fresh install. Even if you did do a fresh install, restoring data & apps from an older version could cause problems. You should try a fresh load and work your way back from there.
Edit: Saw you did the one-click. Still think you should try a full wipe and try it again with a fresh load to see how it goes.
Click to expand...
Click to collapse
Yes, I chose the nodata FI27, since it said that it was good for same-version or upgrades (in this case, ICS to ICS), but I will choose the nuke-from-space one if there's no way out of this, though wouldn't just resetting to factory defaults at this point do the same thing?
It's a little bit disturbing that an issue with one app, albeit an important (though not essential) one, can require wiping the phone. If this were to come up again for some reason, maybe just one day out of the blue and not related to putting on a new ROM, it would be nice to know a way out.
Perhaps I can grab a log from somewhere with ADB?
rseiler said:
I've now done that (though one or two had no data), along with the framework one you mentioned earlier, followed by a reboot, but it still happens. Arghh!
Yes, I chose the nodata FI27, since it said that it was good for same-version or upgrades (in this case, ICS to ICS), but I will choose the nuke-from-space one if there's no way out of this, though wouldn't just resetting to factory defaults at this point do the same thing?
It's a little bit disturbing that an issue with one app, albeit an important (though not essential) one, can require wiping the phone. If this were to come up again for some reason, maybe just one day out of the blue and not related to putting on a new ROM, it would be nice to know a way out.
Perhaps I can grab a log from somewhere with ADB?
Click to expand...
Click to collapse
If you have a custom kernel with recovery make a backup. Or get one and do it and then do a full wipe and fresh load. That is the only way you'll know for sure.
Yes, I will, but I thought I'd live with it a while to see what I could learn.
I've found that opening the newly-installed app is not the issue: simply installing a new app is. If I wait on the "Open" screen right after an install, and do nothing, within a minute the system will freeze and reboot.
Interestingly, updating apps does not trigger the problem, as numerous apps have updated this week, even one that Google Play wanted me to approve manually. Go figure.
Anyway, I have a logcat of an example in case anyone is interested. In this case, I initiated an install at 15:26, which is when the log begins. It ends shortly after the reboot.
http://tny.cz/0b86937c
I have a HTC Wildfire S, rooted, with an AOKP rom.
One day, my phone was running slow, so I rebooted into recovery and cleared dalvik cache and system cache. I rebooted the system and absolutely NOTHING is working. after I unlock the phone, a bunch of processes stop working. Pressing the home button makes Nova Launcher crash. I have since uninstalled it, and still nothing is working.
I can't even turn the phone off using the power button. The only way I can shut the screen off is by removing the battery manually.
EDIT: I tried a factory reset, and it's still the same as before. NOTHING is working. I can go into Settings, that's about it.
A list of apps that stop working:
Link2sd
facebook
outlook
yahoo weather
google.process.gapps
nova launcher
swiftkey
superuser
ETC..
I have attached pictures so you guys can have a sense of what my problem is. Sorry if the pictures are blurry, I had to use my Ipod touch to take them.
Sorry If i have made any errors in this thread. I am new here, I just created an account right now so I can find some help to solve my issue.
HughGRection said:
I have a HTC Wildfire S, rooted, with an AOKP rom.
One day, my phone was running slow, so I rebooted into recovery and cleared dalvik cache and system cache. I rebooted the system and absolutely NOTHING is working. after I unlock the phone, a bunch of processes stop working. Pressing the home button makes Nova Launcher crash. I have since uninstalled it, and still nothing is working.
I can't even turn the phone off using the power button. The only way I can shut the screen off is by removing the battery manually.
EDIT: I tried a factory reset, and it's still the same as before. NOTHING is working. I can go into Settings, that's about it.
A list of apps that stop working:
Link2sd
facebook
outlook
yahoo weather
google.process.gapps
nova launcher
swiftkey
superuser
ETC..
I have attached pictures so you guys can have a sense of what my problem is. Sorry if the pictures are blurry, I had to use my Ipod touch to take them.
Sorry If i have made any errors in this thread. I am new here, I just created an account right now so I can find some help to solve my issue.
Click to expand...
Click to collapse
just reflash the rom. boot into recovery wipe data and flash the rom
Reflash or flash another rom.
Sent from my Samsung Galaxy S4 using Tapatalk
Thanks @Guitarfreak12 and @aWFSuser
I did what you guys said, and I reflashed the same ROM and everything is working fine. The only downside, although, is that I have had to re-install all my apps again.
Also, would you guys know what caused the problem? I'd like to know so that I can ensure it doesn't happen again in the future.
HughGRection said:
Thanks @Guitarfreak12 and @aWFSuser
I did what you guys said, and I reflashed the same ROM and everything is working fine. The only downside, although, is that I have had to re-install all my apps again.
Also, would you guys know what caused the problem? I'd like to know so that I can ensure it doesn't happen again in the future.
Click to expand...
Click to collapse
Did you had a lot of applications installed and linked along with dalvik to sd-ext?
Then after clearing the cache on reboot the dalvik files will regenerate in the /data partition if there are a lot of apps and the /data overflows then your apps will stop working without the dex files. And clearing the dalvik cache usually doesn't help in increasing speed.........next time you should go into link2sd and use the "clean dalvik cache" option there.........
HughGRection said:
Thanks @Guitarfreak12 and @aWFSuser
I did what you guys said, and I reflashed the same ROM and everything is working fine. The only downside, although, is that I have had to re-install all my apps again.
Also, would you guys know what caused the problem? I'd like to know so that I can ensure it doesn't happen again in the future.
Click to expand...
Click to collapse
This actually happens because Link2SD can also link dalvik cache files as well, what the recovery must have deleted would be the symbolic links that the Link2SD script creates, so next time if you want to clear the dalvik cache, use the option found in the Link2sd app
Alright so it seems, instead of using the dalvik cache cleaner on recovery, I should just use the one located in Link2sd. I'll be sure to do that next time to ensure that no problems persist.
Thanks for all the help!