How do I find out which Android process is force closing? It happens every time I restart my phone. It doesn't happen too often but it happens at least once every time I restart. The notification does not say which process, it only says Android process. Sometimes my default keyboard, swiftkey x, is replaced by swype after force closing the Android process. Thanks in advance.
Edit: it actually says the application Android system force closes
Sent from my SPH-D710 using XDA App
That actually means "Android System" is force closing. I know useful right? I don't remember where to get the information that might help figure out why but typically a full wipe and a reflash will take care of it.
s.lee1993 said:
How do I find out which Android process is force closing? It happens every time I restart my phone. It doesn't happen too often but it happens at least once every time I restart. The notification does not say which process, it only says Android process. Sometimes my default keyboard, swiftkey x, is replaced by swype after force closing the Android process. Thanks in advance.
Edit: it actually says the application Android system force closes
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
yea you may have deleted something thats acting up or maybe you installed something your phone is not happy with. I would try to do as the poster above said or run fix permissions in recovery or Rom Manager and see what happens
Are you on an EL13 build? What is your exact setup? If its EL, I may know why.
Sent from my SPH-D710 using Tapatalk
Yes I'm on calks 2.5, so I'm on el13. Also I don't mind reflashing and a wipe, but if there is an easier way, I would prefer to do that.
Sent from my SPH-D710 using XDA App
s.lee1993 said:
Yes I'm on calks 2.5, so I'm on el13. Also I don't mind reflashing and a wipe, but if there is an easier way, I would prefer to do that.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
I do know that undervolting was causing a lot of people to have reboots including myself. I reduced it from 75 to 50. Also did you use Titanium Backup to restore data to your apps. That also causes some issues
I have neither manually undervolted my phone nor backed it up using titanium, so i dont think its from that
Sent from my SPH-D710 using XDA App
s.lee1993 said:
I have neither manually undervolted my phone nor backed it up using titanium, so i dont think its from that
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
I was told that the Android System is calling a file that doesn't exist on EL13. Is it only when you power on phone? Strongsteve found it and fixed it on his ROM but I don't have the knowledge to locate it myself. Is 2.5 Calk's latest update? If he has a newer build, you may want to update. Maybe he found it and fixed it as well.
Sent from my Nexus S 4G using xda premium
Since installing Calkulin's 2.6 and EL13, Google Maps has been force closing on me after reboots. I'll be watching this in case it's a related issue.
Related
I am running Syndicate Rom Frozen 1.0.3 with Twilight Zone kernel. I was browsing Facebook when my phone froze and i had to pull the battery to reset it. After rebooting, every time i tried to open the default messaging app it kept FC'ing along with ChompSMS. I uninstalled chomp to try to fix it but nothing. I am wondering what the next step is. Do i Factory reset the phone? I am trying to avoid this cause I do not want to reroot, reconvert to ext4 etc...Thanks
It sounds like u got data corruption u might have to reflash the rom again
Sent from my SPH-D700 using XDA Premium App
Estewa_619 said:
It sounds like u got data corruption u might have to reflash the rom again
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
I am updating to Syndicate Rom 1.1.0 hopefully that will fix it. Thank you
So every time I flash I wipe data/cache/Dalvik/Battstats. I was using CWM2 for a while and when every ROM continued to slow down and lock up I tried upgrading to CWM3, narrowing my ROM choices but not solving the problem. Whenever I flash, my phone will return to it's snappy self for a varying amount of time before crapping out again. I've tried Sense, AOSP, Evo, and Z ROMs and all behave the same for no apparent reason. What am I doing wrong? My phone used to be lightning quick, I sampled many ROMs and kernels without incident, only experimented with OC briefly, and all of a sudden it's gotten painfully slow no matter what i do. Please help me make my Incredible, "incredible" again
Is it still slow on the Stock ROM? If you haven't tried that already, I would try that. It's possible something else may be wrong with the phone if you've tried many different ROMS and all do the same thing. Do you have all the same apps installed as well, or are they different for the most part?
try fixing permissions
Try wiping your SD card and when you sign in your gmail account don't let it restore all of your apps. Setcpu is also a good investment if you have not already purchased it
Sent from my Incredible using XDA Premium App
TheBr0ken said:
try fixing permissions
Click to expand...
Click to collapse
How do I do this?
In the advanced menu in recovery.
Sent from my ADR6300 using XDA App
k_nivesout said:
In the advanced menu in recovery.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
will i need to re-flash my ROM after doing this?
Nope, doesn't delete anything.
Sent from my ADR6300 using XDA App
This seems to have fixed the problem, thank you so much.
Sent from my ADR6300 using XDA App
Actually, on closer inspection, the permission fix only temporarily stopped the issue. I even switched to the nearly stock Nothing Special Peanut ROM and I still got a FC from Sense. Is my phone a dud?
Sent from my ADR6300 using XDA App
How are you restoring apps? I would wipe everything and flash a fresh ROM. does it freeze up now? If not, my $$ is on a rogue app that doesn't like playing with your phone.
patsfan1130 said:
How are you restoring apps? I would wipe everything and flash a fresh ROM. does it freeze up now? If not, my $$ is on a rogue app that doesn't like playing with your phone.
Click to expand...
Click to collapse
Hmm I just flashed OMFGB w/o restoring my apps. The only things I've installed are the Google Apps, Google Voice (which is my primary method of communication), XDA, and SetCPU. The fcs seem random, not tied to any particular action. They even happen when I'm not doing anything on the phone. Any ideas?
Thanks for the help everyone.
Sent from my Incredible using XDA App
update: I think the problem stemmed from using the SetCPU widget with the refresh rate set to 5 seconds. Not sure if changing the setting makes a difference, but removing the widget from my home screen has solved all the issues insofar. We'll see if it takes this time.
Sent from my Incredible using XDA App
setcpu is always a "use with caution" kind of app. you can get great results, but it's mostly educated trial and error with your rom/kernel combination.
Why do most roms OP state to "fix permissions" directly after flashing the rom, when that does nothing... it fixes them in .3 seconds? lol.... pretty sure it's best to do it after setting the phone up the way you want. Where it takes a couple minutes and actually gives you a log of what is fixed. Just curious if I'm wrong in thinking all this jazz.
Sent from my SGH-T999 using xda premium
I had no idea either. But this cleared it up for me.
http://wiki.cyanogenmod.org/wiki/Fix_permissions
Sent from my Galaxy Nexus using xda premium
Probably just because it can't hurt to do one, that and if an issue arises they can be certain that it was done.
Sent from my SGH-T999 using xda premium
Ive wondered it myself. Never do it though. To me its there for when you run into problems with FCs and such. I assume its the devs trying to be proactive for those who dirty flash.
Ive seen it screw things up to btw.
Sent from my SGH-T999 using xda app-developers app
I know what Fixing Permissions does, just why they tell their users to fix them before anything can be broken, is where my curiosity begins, if I remember right even after a dirty flash they don't wont be fixed til after a reboot...
my way of doing things
wipe data/system/cache
flash rom
boot up>let sit for 5 minutes>install through TB or recover data
boot into recovery and fix permissions, which takes a couple minutes, if I have errors.
Congratulations, no one cares.
psykhotic said:
Congratulations, no one cares.
Click to expand...
Click to collapse
True story, I'm a terrible person.
Sent from my SGH-T999 using xda premium
only fix permissions if you have issues of force closes or log cats are showing files as unreadable... basically if you are having issues of some sort.
also, good idea to fix permissions from terminal while booted into android if you are using a recovery that has not been updated in a long time
cobraboy85 said:
only fix permissions if you have issues of force closes or log cats are showing files as unreadable... basically if you are having issues of some sort.
also, good idea to fix permissions from terminal while booted into android if you are using a recovery that has not been updated in a long time
Click to expand...
Click to collapse
Oh, I know how to run and use fix permissions. I'm just curious as to why some rom cooks give instructions that are useless.
Sent from my SGH-T999 using xda premium
That's a valid question.
I think it's an instruction for crack flashers.
It levels everything out.
Especially, if you are trying to keep your data
Sent from my SGH-T999 using xda premium
********UPDATE*********
Thanks to hardcore,I found a fix in another thread
forum.xda-developers.com/showthread.php?t=1843837&page=4
Using a terminal emulator or adb shell,
su
cd /data/log
chmod 444 dumpstate_*
This sets those files to read-only permissions and that seems to fix it.
Ever since Jellybean instead of apps force closing as they normally would my phone becomes unresponsive and reboots after 2-3 minutes.It gets quite annoying and I wanted to know has anyone else has been getting this issue. I have wiped dalvic/cache also factory data reset,I am unable to do anything in anycut,the phone automatically goes through freeze process,any ideas on how to fix issue?
got the issue too. Only on tw based roms tho. why i only **** wit cm10/aokp. And anycut doesnt work completely with jb yet. You have to use the anycut widget instead
Thanks for the response I guess the only way to stop the problem is not to have a tw Rom,I guess I might just have to bit the bullet on that one,im not really into flashing roms I'm only rooted for hotspot and system settings to change certain things
Sent from my SPH-L710 using xda premium
Could always setup the dualboot to have stock and an aosp rom
Okay I might have to look into that, thanks for the quick responses I thought I was the only one, my friends have s3 to add well and was not experiencing issue,I can see now that's for top them not having stock Rom
Sent from my SPH-L710 using xda premium
You could also find out what process is causing the bad behavior, what's not playing nice, and remove or freeze that app. You could also try to do a fresh install of your rom.
I was getting the same issues, but I found out that Maps social pin-point (Latitude) was causing my issues and unchecked all of the options related to check-ins and location sharing. No problems since.
When you say fresh install do you mean hard reset?if that's what you are referring to I have done that and wipes in recovery. And how exactly did you find it was that specific app doing That to your phone?
Sent from my SPH-L710 using xda premium
brianhot1 said:
When you say fresh install do you mean hard reset?if that's what you are referring to I have done that and wipes in recovery. And how exactly did you find it was that specific app doing That to your phone?
Click to expand...
Click to collapse
For that specific problem, it was trial and error, but a logcat would help. At the time, I couldn't figure it out. I believe there's an app to help read logcats.
Okay thanks
Sent from my SPH-L710 using xda premium
I found one app that was freezing for me I cleared data and uninstall updates for play store, the issue still happens sometimes though
Sent from my SPH-L710 using xda premium
Download Fast Force Close it really helped with the extremely frustrating freezes.
https://play.google.com/store/apps/details?id=com.issess.fastforceclose
Sent from my SGS3!
Cool so how exactly would the app help me if you don't mind me asking I see that it produces the fc would that help in fixing the freezing issue? And if so then how
Sent from my SPH-L710 using xda premium
Any update? It still happens?
Sent from my SPH-L710 using xda premium
Did you use the app? It seems that the app triggers a force clse popup if (im guessing here) a certain amount of time has gone by (like the OS itself does, but maybe shorter) or whenever an app goes unresponsive (it comes up instantly)
So either way, its supposed to fix the force close dialog not showing up for you.
I have our installed but I guess im still working on how to use it, I'm going to try to run it in the background
Sent from my SPH-L710 using xda premium
Update!!!!! Thanks to http://forum.xda-developers.com/member.php?u=336619
Thanks for the tips guys. This was also irritating me to no end on several Samsung roms. I think it happens on the Note and S3 too. Maybe even the S2.
My solution was:
Using a terminal emulator or adb shell,
su
cd /data/log
chmod 444 dumpstate_*
This sets those files to read-only permissions and that seems to fix it.
Sent from my SPH-L710 using xda premium
Great tip. Had never heard of this before.
Sent from my SPH-L710 using xda app-developers app
Hi guys, I got this device today, rooted using Odin, and am currently using stock rom and kernel(4.1.2) my stock browser worked fine for the first few hours after I rooted and then seriously out of the blue it started giving me app not responding toast and closes. Any ideas what may have caused this? I deleted a few of the bloatware apps with TB but didnt delete anything having to do with the browser or data connectivity. I even left google talk alone and I always get rid of it. Any suggestions?
Sent from my SGH-T989 using xda app-developers app
Try wiping cache and davlik cache in recovery and fixing permissions. That's always the first place to start.
Also, its always best to just freeze bloat. And after a bit, if all is well, then uninstall.
Sent from my SGH-T989D using xda app-developers app
kj2112 said:
Try wiping cache and davlik cache in recovery and fixing permissions. That's always the first place to start.
Also, its always best to just freeze bloat. And after a bit, if all is well, then uninstall.
Sent from my SGH-T989D using xda app-developers app
Click to expand...
Click to collapse
I tried that after I posted, still no go. I think I may just nandroid back to before it started misbehaving and see if it happens again.
Edit: im a dumb a$$. I changed my screen density to 200. Thats why its crashing. I wonder if there is something I can do to edit the apk its self so it doesn't crash because of density.
Sent from my SGH-T989 using xda app-developers app
grantusmantus said:
I tried that after I posted, still no go. I think I may just nandroid back to before it started misbehaving and see if it happens again.
Edit: im a dumb a$$. I changed my screen density to 200. Thats why its crashing. I wonder if there is something I can do to edit the apk its self so it doesn't crash because of density.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Use xposed to put browser back to stock dpi. Tho I'm at 210 and everything works fine. Any browser.
Sent from my SGH-T989D using xda app-developers app