Database Users

The process com.android.phone has stopped unexpectedly

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.....!!!!!

[Q] [CM7] Problems with applications

Hi guys
I'm having problems I guess CM7 related, maybe you have experienced one ot them (or all like me):
- SNESdroid: It doesn't work, when I try to load ROM I get a black screen and I have to kill the app
- GoLauncherEx: It works fine but I can't change themes because it doesn't do anything. If I try to add an app to desktop by the menu of GoLauncher it try to load apps list but exit immediately, and get same behaviour if I try to go to preferences of GoLauncher
- Games: After 15 min aprox of playing some games (AngryBirds, TripleTown) the cellphone get locked and I have to press power button to unlock it and the game quits
When I installed CM7 I didn't did 'wipe dalvik cache' since in [1] says anything about that, I tried yestarday doing 'wip dalvik cache' from 2init but it doesn't change anything
I'd like to know if the bugs are app related, CM7 related (or I did a bad installation). SNESdroid is the most important for me, do you manage to got it working?
Thanks in advance
[1] wiki,cyanogenmod,com/wiki/Motorola_Defy:_Full_Update_Guide

this happened to me, once. Nothing really seemed to work except a fresh install of CM7, by the book, and note... you need to wipe Dalvik cache before you flash the rom, or it won't work right.

Fixed
mankymoo said:
this happened to me, once. Nothing really seemed to work except a fresh install of CM7, by the book, and note... you need to wipe Dalvik cache before you flash the rom, or it won't work right.
Click to expand...
Click to collapse
That was it, I have to reflash the build again. Currently I have CM 7.2 Nightly and it works pretty good. Thanks for your post mankymoo
PD: Can a mod mark this as solved please?

Update Just Pushed

Turned on my A500 just now and the Android Is Updating popup flashed... then the counting of updated processes... all the version numbers seem to be the same... anyone else get this or have an idea what they updated?

If it's any consolation, it isn't an update. I have no idea what the issue is. But my tablet does the same thing every so often. It's as if I cleared my cache or something...

...odd
The only time I've seen that was on a reboot after a major update. Oh well, no worries.

That occurs when the Dalvik Cache has been cleared. Before ICS you would just see the boot animation the whole time that was happening, in ICS they decided to show you the process. Don't know why your Dalvik is clearing when you power down though.

cruise350 said:
That occurs when the Dalvik Cache has been cleared. Before ICS you would just see the boot animation the whole time that was happening, in ICS they decided to show you the process. Don't know why your Dalvik is clearing when you power down though.
Click to expand...
Click to collapse
Perhaps the OP should format /cache and wipe the dalvik-cache using recovery? Perhaps the permissions are messed up or the partition has gone awry.

Some odd things happened yesterday- All media on the storage card acted like the card was first plugged in. Everything had to index all over again. Then other little things that pretty much confirms some cache was cleared somehow. No idea... I'm probably going to back things up and do a hard reset.

Transformer TF101 Home and lock not working

Hi,
Hopefully someone has a solution for me.
This morning I switched on my TF101 and when I tried to go home from Gmail the button lit up but did nothing. I was convinced it didn't work. So I treid a few reboots and still nothing. I tried some other launchers and still nothing.
On further inspection I realised that when turning on slide unlock that also didn't work. Changing to pin, pattern or password still shows no unlock.

Are you running stock or a custom ROM?
Are you running stock recovery or a custom one?
I'd try to wipe the cache and dalvik, it fixes lots of weird software issues.

Lethe6 said:
Are you running stock or a custom ROM?
Are you running stock recovery or a custom one?
I'd try to wipe the cache and dalvik, it fixes lots of weird software issues.
Click to expand...
Click to collapse
It's the stock ROM rooted with debugfs.
I know how to wipe the cache but how do I wipe the dalvik. I remember doing it once a couple of years ago on another device but for the life of me now can't remember.
I was going to try clearing the davlik with Terminal Emulator and typed "su" followed by "ls" and all it showed is "recovery". Does this mean it's somehow landed in recovery mode? If so, how do I get out of it?

I managed to clear dalvik through terminal emulator. Optimised apps and rebooted but the problem persists.
Sent from my Transformer TF101 using Tapatalk 2

Reaper1242 said:
It's the stock ROM rooted with debugfs.
I know how to wipe the cache but how do I wipe the dalvik. I remember doing it once a couple of years ago on another device but for the life of me now can't remember.
I was going to try clearing the davlik with Terminal Emulator and typed "su" followed by "ls" and all it showed is "recovery". Does this mean it's somehow landed in recovery mode? If so, how do I get out of it?
Click to expand...
Click to collapse
If you have CWM, go to advanced, wipe Davlik.

frederuco said:
If you have CWM, go to advanced, wipe Davlik.
Click to expand...
Click to collapse
Thanks, now I remember I used CWM.

I thought I'd report back on this in case the information might help someone else down the line.
I tried the cache/davlik clear method and that did nothing for me. I stuck with it for a few days and eventually resorted to button saviour. I also realised that not only was the home button and any lock screen not working, but when using the ASUS quick settings in notifications it didn't show all settings.
This lead me to believe something in the system itself had gotten warped.
Today I did a Titanium backup, factory reset and restored all apps, data and system data. Initially it was fixed but on restart the problem casme back. I knew I'd restored whatever had caused the issue. My next step was to do another factory reset. Since it takes minutes to manually get the system back I only restored apps and data.
This time, after restore the issue was gone. So clearly the issue was in a system setting.
So for anyone else having this issue. Backup with Titanium, factory reset and only restore apps+data.

Dalvik Cache Wipe triggers Starting apps dialog box every boot

I have got this issue since I wiped the dalvik cache on Android 4.2.2 to fix a Play Store issue which I should of deleted that dalvik cache file with Titanium Backup or use Lucky Patcher to remove that left over file in /data/app/ but also wiping the cache somehow broke the APN API not allowing me to add the wiped APNs and such.
Since then I had to reflash EVERYTHING using the Nexus Stock Image flasher from Google Developers, since then I had no issues until a recent Android 4.3 update which caused the dalvik cache issue to arise since it wiped the dalvik cache.
I also do not have root because of the update but the su binary and SuperSU is still there so I cannot fix the issues manually.
When I come back on holiday I will root the device to see if I can fix the issue
but if that does not help then I can use the root to backup ALL the user apps, backup ALL the internal SD contents and reflash also rooting it.
Because I paid for the TB licence I can just restore my stuff in a touch of a "button".
I have removed apps which I don't use and the ones which I suspect is causing the issue but that does not help.
It seems that wiping the cache partition now does not break anything.
The dialog box says in the title "Android is upgrading..." and it says below "Starting apps..." and then gets off in a second.
I have seen forums of people having this strange issue but there are no replies.
I am getting back from holiday on the 31/8/13.
I really want this haunting issue to stop so please help so others can fix this issue without going though annoyance caused by this issue.

andyabc said:
I have got this issue since I wiped the dalvik cache on Android 4.2.2 to fix a Play Store issue which I should of deleted that dalvik cache file with Titanium Backup or use Lucky Patcher to remove that left over file in /data/app/ but also wiping the cache somehow broke the APN API not allowing me to add the wiped APNs and such.
Since then I had to reflash EVERYTHING using the Nexus Stock Image flasher from Google Developers, since then I had no issues until a recent Android 4.3 update which caused the dalvik cache issue to arise since it wiped the dalvik cache.
I also do not have root because of the update but the su binary and SuperSU is still there so I cannot fix the issues manually.
When I come back on holiday I will root the device to see if I can fix the issue
but if that does not help then I can use the root to backup ALL the user apps, backup ALL the internal SD contents and reflash also rooting it.
Because I paid for the TB licence I can just restore my stuff in a touch of a "button".
I have removed apps which I don't use and the ones which I suspect is causing the issue but that does not help.
It seems that wiping the cache partition now does not break anything.
The dialog box says in the title "Android is upgrading..." and it says below "Starting apps..." and then gets off in a second.
I have seen forums of people having this strange issue but there are no replies.
I am getting back from holiday on the 31/8/13.
I really want this haunting issue to stop so please help so others can fix this issue without going though annoyance caused by this issue.
Click to expand...
Click to collapse
that android is upgrading dialog box is the dalvik getting rebuilt, it get rebuilt after you wipe it, it is SUPPOSED to happen when you wipe your dalvik. it isnt an issue. if not, you wouldnt have a bootable or usable phone. the real issue here is you using lucky patcher. we all know what it is used for, and is disrespectable to the developers that hang out on xda.

simms22 said:
that android is upgrading dialog box is the dalvik getting rebuilt, it get rebuilt after you wipe it, it is SUPPOSED to happen when you wipe your dalvik. it isnt an issue. if not, you wouldnt have a bootable or usable phone. the real issue here is you using lucky patcher. we all know what it is used for, and is disrespectable to the developers that hang out on xda.
Click to expand...
Click to collapse
I only use Lucky Patcher for important stuff and not really for what you think so that is NOT the issue what so ever and misleading to this thread and plus, other people use it.
I mean that in EVERY boot it says that it is starting apps, nothing to do with building at all.
Sent from my Nexus 4 using Tapatalk 4 Beta

andyabc said:
I only use Lucky Patcher for important stuff and not really for what you think so that is NOT the issue what so ever and misleading to this thread and plus, other people use it.
I mean that in EVERY boot it says that it is starting apps, nothing to do with building at all.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Late reply, but Lucky Patcher did this to my phone just now and I don't know what to do, other than reflash. Which sucks because I spent all night modding out my phone and was stupid enough to not to a nandoid backup.
Edit: The first boot it upgraded everything then everything force closed, 2nd boot everything upgraded, but seems to be working fine. Woo. Was scared for a moment.

evilpig said:
Late reply, but Lucky Patcher did this to my phone just now and I don't know what to do, other than reflash. Which sucks because I spent all night modding out my phone and was stupid enough to not to a nandoid backup.
Edit: The first boot it upgraded everything then everything force closed, 2nd boot everything upgraded, but seems to be working fine. Woo. Was scared for a moment.
Click to expand...
Click to collapse
Well you was LUCKY (pun alert!).
Anyway it seems that the stock rom was always the issue, even reflashing does not fix this issue when you wipe the dalvik cache.
I am on ParanoidAndroid 3.98 at the moment and I am not getting any issues just by wiping the dalvik cache and/or the cache partition.
Sent from my Nexus 4 using Tapatalk 4

I have found fix for this error, it is mainly due to odex files which are created by lucky patcher so deleting these files using lucky patcher itself will surely remove this error with 50 percent success rate. Here's the fix; open lucky patcher, there in lower left section you can see Toolbox, click that Toolbox then select 4th last option i.e Remove all odex files.Thats it android will reboot on itself and vola no android is upgrading. .
Check out attached image for help.
:good:Hits Thanks If I helped u:good:

Garu8 said:
I have found fix for this error, it is mainly due to odex files which are created by lucky patcher so deleting these files using lucky patcher itself will surely remove this error with 50 percent success rate. Here's the fix; open lucky patcher, there in lower left section you can see Toolbox, click that Toolbox then select 4th last option i.e Remove all odex files.Thats it android will reboot on itself and vola no android is upgrading. .
Check out attached image for help.
:good:Hits Thanks If I helped u:good:
Click to expand...
Click to collapse
I just removed the odex files and worked great. Thank you.