I have been having this issue ever since my phone booted up and all my apps sequentally had force close dialogs happen. I am running my apps from the SD and figured something went wrong with the boot up sequence. I tried doing a nandroid backup, reinstall fresh 1.1, but no luck.
I then used my backups to reinstall over all my apps, then went into Market to install them via that. Everything seemed to be just fine, but the phone app would still not dial anything and when I recieved a call, it gives the error "The process com.android.phone has stopped unexpectedly" and then proceeds to try to reset the phone connection. Most times I lose all data connection and need to reboot.
Recently, I tried installing the latest Modoco CDMA rom. No luck. I then did a Titanium backup and force reinstalled everything again. Still no luck.
Anyone have this issue and get it resolved? My Hero can do everything but make and accept calls. I really don't want to do a wipe as this problem can just happen again, so I would rather understand the process.
Thanks in advance.
Ceger
Simplest way to fix this should be clearing the dalvik/boot cache from fresh's kitchen. I really should write up a guide on how to do these simple tasks manually.
obelisk79 said:
Simplest way to fix this should be clearing the dalvik/boot cache from fresh's kitchen. I really should write up a guide on how to do these simple tasks manually.
Click to expand...
Click to collapse
Will that work on MCR 2.2 as well? I'll look into that. Is it something I can do from recovery?
Ceger
yes should work on mcr 2.2 and can be done manually from recovery, I know recovery does dalvik cache, not sure if it also kils the boot cache as well though. The older version only did dalvik.
obelisk79 said:
yes should work on mcr 2.2 and can be done manually from recovery, I know recovery does dalvik cache, not sure if it also kils the boot cache as well though. The older version only did dalvik.
Click to expand...
Click to collapse
Do you need to do both? Wiping the dalvik cache created lots of app fc issues, which would be fine if the phone actually worked. Still won't make or receieve calls.
And thank you for the assistance.
Ceger
Edit. Clearing the boot cashe got rid of the FC issues. However, still have same issue with the phone app. This is so annoying.
honestly the best bet to clear up the issues would be to do a full wipe from recovery. Wipe the phone clean then run the stock RUU and re-root and install your custom rom. Do a nandroid backup first just to prevent losing any of your info.
Unfortunately despite the many well written guides here on XDA there are always a few issues most likely a result of slight hardware quirks or unfortunate circumstances at the time of flashing.
Just for '****s and giggles' have you tried pulling your battery for 30 seconds, reinstalling it and booting the phone up?
Heck sometimes just a reflash of the rom right over top of itself. I've been tinkering with this phone since the day root came out and I still don't fully understand all of it's quirks.
Ceger said:
I have been having this issue ever since my phone booted up and all my apps sequentally had force close dialogs happen. I am running my apps from the SD and figured something went wrong with the boot up sequence. I tried doing a nandroid backup, reinstall fresh 1.1, but no luck.
I then used my backups to reinstall over all my apps, then went into Market to install them via that. Everything seemed to be just fine, but the phone app would still not dial anything and when I recieved a call, it gives the error "The process com.android.phone has stopped unexpectedly" and then proceeds to try to reset the phone connection. Most times I lose all data connection and need to reboot.
Recently, I tried installing the latest Modoco CDMA rom. No luck. I then did a Titanium backup and force reinstalled everything again. Still no luck.
Anyone have this issue and get it resolved? My Hero can do everything but make and accept calls. I really don't want to do a wipe as this problem can just happen again, so I would rather understand the process.
Thanks in advance.
Ceger
Click to expand...
Click to collapse
use these commands to clear cache
rm -r /data/boot-cache/
rm /data/dalvik-cache/
once you finish then reboot.everything should go away...
he's done that already.
then i suggest to extract the rom zip file, and get into command on your device and go under the system/lib or app and see what is listed in the folders. and compare it to the rom folder.
That's how i was able to fix the voice search on my device, one of the lib file was missing and got it to work after that.
obelisk79 said:
honestly the best bet to clear up the issues would be to do a full wipe from recovery. Wipe the phone clean then run the stock RUU and re-root and install your custom rom. Do a nandroid backup first just to prevent losing any of your info.
Unfortunately despite the many well written guides here on XDA there are always a few issues most likely a result of slight hardware quirks or unfortunate circumstances at the time of flashing.
Just for '****s and giggles' have you tried pulling your battery for 30 seconds, reinstalling it and booting the phone up?
Heck sometimes just a reflash of the rom right over top of itself. I've been tinkering with this phone since the day root came out and I still don't fully understand all of it's quirks.
Click to expand...
Click to collapse
Done and done and no difference.
reddick said:
then i suggest to extract the rom zip file, and get into command on your device and go under the system/lib or app and see what is listed in the folders. and compare it to the rom folder.
That's how i was able to fix the voice search on my device, one of the lib file was missing and got it to work after that.
Click to expand...
Click to collapse
Done, even manually moved some files in case they were corrupted at one point. Very bad move, nandroid backup was my friend there.
Guess a wipe will be the only option then. How annoying.
Thanks for all of your inputs.
Ceger
Another thought... would updating my phone with latest kernal compile possibly do the trick? Or how about a replacement process for google.com.phone?
Ceger
Interesting theory.... worth a try.
i had this issue once and it was because of somehow the uids for the apps got messed up. a wipe should fix this in most cases. but for me it went like ur issue. i almost event went back stock. then i looked into it and found that in my packages.xml file the the uids were all messed up. i had multiple uids and certs for the apps i was having issues with. so what i did was pulled the packages.xml from the device and erased the apps i was having issues with. then pushed it back and rebooted. that cleared the issue. so if i were u i would research that. do a google search on it. then if it doesnt work do the ruu and reroot. good luck man. i know how u must be feeling. i was there
toastcfh said:
i had this issue once and it was because of somehow the uids for the apps got messed up. a wipe should fix this in most cases. but for me it went like ur issue. i almost event went back stock. then i looked into it and found that in my packages.xml file the the uids were all messed up. i had multiple uids and certs for the apps i was having issues with. so what i did was pulled the packages.xml from the device and erased the apps i was having issues with. then pushed it back and rebooted. that cleared the issue. so if i were u i would research that. do a google search on it. then if it doesnt work do the ruu and reroot. good luck man. i know how u must be feeling. i was there
Click to expand...
Click to collapse
Actually, the fix was much simpler. I wiped the SD ext partition and just did a Recovery Wipe. It went back to stock modded rom that remained rooted. I then used Titanium to reinstall my apps with data and then MyBackup to get back some settings such as my scenes, etc. and all was good. Took all of 30 minutes to get my Hero back up and running in better condition than before.
Thanks all for the assists.
Ceger
com.android.phone
com.android.phone
i am facing this prob on cyanogen mod10....when ever i reboot my optimus 2x....i face this damn problem
help plzzzzzzzzzz.....!!!!!
Seems without adding anything to my A7, in the past day it is literally non stop FC'ing on the above process. I hit Force Close and it keeps coming back (not immediately, more like randomly without 10-25 seconds). Only thing I've did extra n the tablet lately is play Angry Birds. Should I try to clear it's DB even though I haven't loaded it today? Also would like to state that I have rebooted and even shut down the tablet, and it still does it.
what have you done to it? stock firmware update? DexterMod? Stock fresh out of the box?
netstat_EVO said:
what have you done to it? stock firmware update? DexterMod? Stock fresh out of the box?
Click to expand...
Click to collapse
Guess in my first version of this thread, before I edited it, I had that information (morning brain fart).
DexterMod v1.3 + BT Fix
Worked fine yesterday morning then it started FCing out of the blue. I've begun (even though none of the apps were installed immediately prior to the FCs) uninstalling widgets that I installed. Next is to start on programs (I did however uninstall Button Savior as I know it loads on startup so I was thinking that was causing it even though it had been on the device for a couple days running flawlessly).
Got tired of messing with it. Did a Cache Partition Wipe and Device Wipe and it's back to normal DexterMod v1.3. This seems to have resolved the issue so it must have been something with one of the databases on the applications that I had installed. Will see once I reload all my apps.
Is anybody else experiencing this issue. I try clearing cache but still does it. Is annoying as i have to go back and update every app manually. I'm on stock 4.4.2 no root.
wperez2 said:
Is anybody else experiencing this issue. I try clearing cache but still does it. Is annoying as i have to go back and update every app manually. I'm on stock 4.4.2 no root.
Click to expand...
Click to collapse
Clear Play Store and Google Services Framework data, and reboot. Is it fixed?
I'll try that and report back when i get more apps to update.
No that didn't fix it. I also tried uninstalling the play store updates. I'm currently using ART instead of Dalvik, although i did revert back to Dalvik once and still fail. I'm planning on rooting the phone so maybe when it gets restore back to factory it will get fix. Thanks for the tips anyway
I am on OA8 (Lollipop). Currently unrooted.
Issue is every 30 Minutes or so it tells me that "Contacts has stopped working."
does anyone else have this issue?
I have this problem too. On OA8 rooted. Did I full system wipe and it still remains.
banditsw said:
I have this problem too. On OA8 rooted. Did I full system wipe and it still remains.
Click to expand...
Click to collapse
Go into Settings -> Applications, choose Contacts and clear data. You may need to force stop first and restart afterward.
So far I've yet to get this new version to work with the fancy new backup and organization features that just came out. When I first installed it would just crash immediately when trying to boot. What I've now tried is Force Stopping and clearing cache and data. This gets me into the "intro" screen, but as soon as I hit 'get started' It just crashes. Any ideas what's going on? I just updated to 5.1.1, had issue on 5.1.0 a well. I am rooted.
:highfive:
Tried force stop and clearing data and cache for both the camera and photo's app. Then tried rebooting and opening camera (worked fine) then photo's (crashed as usual). Tried doing it again but opening photo's first, still crashed on the screen where it looks like you turn backup on or off. I think there is a backup issue. I had auto backup off for photo's previously by the way.
the same here
AAhrens said:
So far I've yet to get this new version to work with the fancy new backup and organization features that just came out. When I first installed it would just crash immediately when trying to boot. What I've now tried is Force Stopping and clearing cache and data. This gets me into the "intro" screen, but as soon as I hit 'get started' It just crashes. Any ideas what's going on? I just updated to 5.1.1, had issue on 5.1.0 a well. I am rooted.
Click to expand...
Click to collapse
I am experiencing the same issue since yesterday after flashing Google Play Edition 5.0.1 【JFLTE-GPE】ROM on Galaxy S4. Looking for the solution...