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

I'm getting a bunch of force close messages on Boot

I flashed cyanogen 5.0beta. It was working great.....then i went to compress cache in one of the new apps(can't remember the name) the phone reset itself about 3 times so I wiped it and restored it. Now it completely boots, but then I get a "force close" message that won't go away. If someone could help I would appreciate it.

When you wiped, did you reflash the google stuff and the cyan rom?

I tried wiping it and the re-flashing cyan but I still get the same messages. Thts the only rom I flashed

I mean after you wiped did you also flash the Google Add on supplied in Cyanogen's thread (http://www.mediafire.com/file/jmmzywtlnjd/gapps-passion-ERE27-2-signed.zip) along with the ROM after you wiped?
Also, what is force closing? Is it specific apps? If so, are they system apps are market/3rd party apps? Is it processes that are force closing?

I just wiped and reflashed cyan and then downloaded and flashed the google addon and the I rebooted just fine. now i want to see if i can restore. Plus the force close message was google startup wizard

I think I gotta start from scratch if my titanium backup failed me

Damn. Well at least it's fixed. Thanks for the help. I don't know why the google add on helped but it did.

[Q] Android is upgrading after every boot

OK guys I have a problem and I'm hoping that you could help me.
I rooted my S4 and installed stuff that I wanted, phone was in a great shape until I came across this post that was guiding a way to remove the custom sign when you turn on the phone once you have rooted the phone, so the procedure was to install SuperSU and install the new su binary coming with it, uninstalling previous SU and rebooting. the post was claiming that the sign would be gone and the regular "Samsung galaxy S4" would be shown instead. So I did all those and on the way coming up on the first time the message "android is upgrading" popped up, it's the first time so it's fine, but then it became annoying when it started showing up every single time after that, I took some procedures to fix it as follows:
I,
1. removed application "supersu".
2. went back to the previous SU.
3. wiped delvik and cache. (something amazing about this is that after the manual wiping the number of apps being upgraded is 193, while in its every time boot it only upgrades 120 of them (which is good I think don't have to wait for all 193 every time), but it goes back to 120 after the initial boot after wiping delvik).
4. uninstalled TB.
5. executed fixing permission.
6 reinstalled TB and restored all the apps.
7. re-rooted the phone with motochopper.
8. looked for odex files in /data/ app. (there were none).
couldn't think of anything else and that's where I stopped. I know that this message pops up everytime delvik cache is wiped but I can't figure what is causing it every time.
one more thing, I noticed is that the USB debugging option turns off after every restart, not sure if this is something normal or what, just thought this may be helpful in the diagnosing process. one more thing the post was correct about the old sign coming back though.

There might be an app clearing cache everytime like an optimization app or something. Mine used to when I set rom toolbox to do so
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Please read forum rules before posting
Questions and help issues go in Q&A and Help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

egolabbakhsh said:
3. wiped delvik and cache. (something amazing about this is that after the manual wiping the number of apps being upgraded is 193, while in its every time boot it only upgrades 120 of them (which is good I think don't have to wait for all 193 every time), but it goes back to 120 after the initial boot after wiping delvik).
Click to expand...
Click to collapse
This exact same thing is happening to me, as of today. All I did was clear cache and dalvik, and all of a sudden this is now happening. Gone through all the steps to figure out why as you did, and nothing has worked.
Strange part...mine is also getting stuck with the 120 at each boot. When I do it manually, it's 236.

I ended up restoring my phone, I think that's your last resort as well. I hope you have a backup, otherwise you're in trouble!

1.install lucky patcher
2.go to toolbox tab
3.remove all odex files

No great change
majid.gh said:
1.install lucky patcher
2.go to toolbox tab
3.remove all odex files
Click to expand...
Click to collapse
My phone still does the Updating, just now instead of starting at 27 and going to 57, it starts at 1 and goes to 30

majid.gh said:
1.install lucky patcher
2.go to toolbox tab
3.remove all odex files
Click to expand...
Click to collapse
Simple as that! Just had to boot a couple of times. Excellent!

svendsvin said:
Simple as that! Just had to boot a couple of times. Excellent!
Click to expand...
Click to collapse
+1
On my rooted 4.3 Sony Xperia SP:
I did the lucky patcher thingy twice (it reboots each time, first time the nag happened). Booted up nicely after that.

It will do this if dalvik cache is wiped...one of your apps may be doing this automatically
Sent from my SGH-I337 using Tapatalk 2

Hey there this problem is happening with my. Samsung Galaxy S duos 2 also
- I rooted it.
- Then after 2 days Format it.
- Now there is "Android is upgrading" Toast is appearing after every single reboot.
SO WHAT TO DO GUYS....

Can't open apps I've downloaded. "unfortunately XXX has stopped"

I recently did the root from: http://forum.xda-developers.com/showthread.php?t=2291827
and the hot spot mod from: http://forum.xda-developers.com/showthread.php?t=2256950
I've reverted the hotspot mod and still the same result.
All my old apps work fine, nothing new that I download can be opened.

try clearing the data/cache on the apps then force close them and try to relaunch.....i had that issue with slim for a bit but it seems that whatever changes in build 6 were implimented fixed the issues.

xxaddictedxx said:
try clearing the data/cache on the apps then force close them and try to relaunch.....i had that issue with slim for a bit but it seems that whatever changes in build 6 were implimented fixed the issues.
Click to expand...
Click to collapse
Tried clearing data/cache with no improvement. Thanks for the suggestion tho.

what rom u running?

xxaddictedxx said:
what rom u running?
Click to expand...
Click to collapse
stock rom.
Just tried a factory reset and now everything is crashing before I can even get into the setup process.
all services/apps that try to load crash.

I'm also unable to wipe cache from stock recovery, it says error.
is there a way to do it from odin? I'm waiting on stock firmware download, hoping that will make my phone useable again.

would installing TWRP and flashing an aftermarket rom potentially fix it? stock firmware is taking forever to download.

Stock firmware fixed the issue, scared to reroot the phone now tho....

if your having issues booting after a wipe try moving to to differant rom. if you like the TW UI there are still plenty of options for you in the way of custom roms. also if your going to be formatting your phone (i.e. wiping cache and dalvik and system components) i would recommend you load a custom recovery. you dont have to have one but it is advised.

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.