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

"android is upgrading" on every boot.

Hey Guys, anyoen have any clues on this?
All I did was swap out my boot animations.
On every boot the "Android is upgrading - Starting apps" popup
Boot time has not changed as my startup manager shows a consistant 34-40sec boot,
I even extracted the original image and reinstalled all the original boot anims.
Uninstalled xposed framework, Wanam,
uninstall titanium,
cleared cache via recovery..
Any ideas? Its annoying.
Thanks!

deathshead said:
Hey Guys, anyoen have any clues on this?
cleared cache via recovery..
Click to expand...
Click to collapse
You're getting that message because its rebuilding your cache on boot.. when you clear it in recovery, that's normal behavior.
Getting it every single boot, now, that sounds like there is a problem.. I would check for something clearing the cache besides you doing it manually (unless you are doing this every time you get that message on boot), worst case scenario flashing the stock odin file in General should clear it up

Did you fix permissions and ownership on the new boot ani? Use Jrummys root browser and check both of those.
Sent from my SM-N900V using Tapatalk

Finally figured it out!
What a pita. Reflashed via Odin and started
Installing all my stuff.
The app that caused this out of all the system app mods I have running was the transparent accuweather widget nodded apk. I forgot to Delete the corresponding odex when i installed it. DUH!! all Self inflicted.
All good to go now.
Thanks guys.

deathshead said:
Finally figured it out!
What a pita. Reflashed via Odin and started
Installing all my stuff.
The app that caused this out of all the system app mods I have running was the transparent accuweather widget nodded apk. I forgot to Delete the corresponding odex when i installed it. DUH!! all Self inflicted.
All good to go now.
Thanks guys.
Click to expand...
Click to collapse
Thank you very much. I was having the same problem ever since I installed LG G2 keyboard on my G Pro F240L running G2V5. It was just a 3 second message at start but still bugged me.
I deleted the odex files now for the keyboard and its theme files. Rebooted about 5 times to check. Keyboard still works, startup upgrade message is gone. Didn't have to reflash ROM or clear any cache. Great solution.

NeoMagus said:
You're getting that message because its rebuilding your cache on boot.. when you clear it in recovery, that's normal behavior.
Getting it every single boot, now, that sounds like there is a problem.. I would check for something clearing the cache besides you doing it manually (unless you are doing this every time you get that message on boot), worst case scenario flashing the stock odin file in General should clear it up
Click to expand...
Click to collapse
Hyperdrive It does that it is normal but does not actually go through the apks.

wipe cashe and dalvik

Hi all,
I think I might have a problem, after I flashed xposed framework on my nexus 6p and got the modules that I wanted up and running no problem, during 4 or 5 days all worked fine but had constant reboots,
I decided to go back before I flashed xposed with twrp and restored a full backup, it failed to restore all selected at the same time, so did one a time and restored but phone would just not boot, so
Having data partition restored and then dirty flash stock without wipe data I was able to get my phone back and running, and re-root fine and flashed twrp no problems
Went to twrp to wipe cashe and dalvik but it just takes like 2 seconds optimizing apps and boots to desktop right up, now my question is
Shouldn't it take a very long time to optimize all my apps after the wipe????
all seems to be working fine but kind of bothers me that I might have something in not working right that might develop into something worst in the future

It is at this point I usually full-wipe and reflash. =) Setting things up again can suck, but it's better than wondering what unknown thing is broken and will rear it's ugly head later.

Elnrik said:
It is at this point I usually full-wipe and reflash. =) Setting things up again can suck, but it's better than wondering what unknown thing is broken and will rear it's ugly head later.
Click to expand...
Click to collapse
full wipe and reflash, want to avoid that, any other commands perhaps?

OK so I did a full re flash, back to stock, re root, installed my apps, used for a while, log in on all, went to twrp to test wipe cache and dalvik, same thing, optimizing apps at first boot took like one second and boot to desktop, is this normal or should take longer to optimize all apps?? Anyone??

is my understanding that only apps that havent already been optimized will upon boot... (new installs from like a zip)

chaco81 said:
is my understanding that only apps that havent already been optimized will upon boot... (new installs from like a zip)
Click to expand...
Click to collapse
thats what i am thinking too now that you mention it, like when I installed xposed initially and did whipe cache/dalvik thing after it took long time to boot because was on something like optimizing app 3 out 78, same thing I have seen on my old nexus 5 when dirty flash a new firmware, but not sure if I have something broken or is normal

Layers won't uninstall even after factory reset/full wipe

So I got a Nexus 6p yesterday, and after messing around I wanted to mess with layers a bit to make certain things more AMOLED friendly like the settings, messenger, etc. So I tried using Dark Material layer only selecting a few of the overlays I wanted. Anyway after applying and a reboot my Settings would FC anytime I tried to access...okay fine, happened on my Nexus 5 also. No big deal I would just restore the backup I made PRIOR to messing with layers at all. After doing a factory reset in TWRP and restoring my backup, settings still FC, and my layers are STILL applied! The messenger one still opens and is fine, but settings FC. In TWRP I did the factory reset wipe and a manual wipe of System, Data, Cache...only thing I didn't wipe is internal storage. What is going on and how can I fix this??

perhaps layers is stored in internal storage?

Layers is stored in the vendor partition. There's a flashable zip for the latest vendors in the PureNexus ROM thread, flash that with TWRP and it'll clear your vendor partition.
PS. This has been asked a few times, a quick search probably would have turned up the answer you needed.
Sent from my Nexus 6P

Heisenberg said:
Layers is stored in the vendor partition. There's a flashable zip for the latest vendors in the PureNexus ROM thread, flash that with TWRP and it'll clear your vendor partition.
PS. This has been asked a few times, a quick search probably would have turned up the answer you needed.
Sent from my Nexus 6P
Click to expand...
Click to collapse
I did search for layers not uninstalling...and I did see the vendor solution however I figured since I was wiping system during my wipes I thought that wasn't the issue(I should have checked the actual folder, my misake). I also even did a full wipe and clean install, and still my settings and layers were installed. I couldn't understand why. After reading your suggestion I finally checked the vendors folder and seen they were still there...I removed them and after a clean install all was right with the world.
However I'm having a problem now with my password not working. I restored my backup I made prior to applying any layers and now my phone is saying my password is incorrect....ahhhh I'm getting so frustrated. Anyway thanks for your help!

Jonnyredcorn said:
I did search for layers not uninstalling...and I did see the vendor solution however I figured since I was wiping system during my wipes I thought that wasn't the issue(I should have checked the actual folder, my misake). I also even did a full wipe and clean install, and still my settings and layers were installed. I couldn't understand why. After reading your suggestion I finally checked the vendors folder and seen they were still there...I removed them and after a clean install all was right with the world.
However I'm having a problem now with my password not working. I restored my backup I made prior to applying any layers and now my phone is saying my password is incorrect....ahhhh I'm getting so frustrated. Anyway thanks for your help!
Click to expand...
Click to collapse
The password problem is fixable...within twrp you need to delete the password file. See this thread for details: http://forum.xda-developers.com/showthread.php?t=3245070

Jonnyredcorn said:
I did search for layers not uninstalling...and I did see the vendor solution however I figured since I was wiping system during my wipes I thought that wasn't the issue(I should have checked the actual folder, my misake). I also even did a full wipe and clean install, and still my settings and layers were installed. I couldn't understand why. After reading your suggestion I finally checked the vendors folder and seen they were still there...I removed them and after a clean install all was right with the world.
However I'm having a problem now with my password not working. I restored my backup I made prior to applying any layers and now my phone is saying my password is incorrect....ahhhh I'm getting so frustrated. Anyway thanks for your help!
Click to expand...
Click to collapse
Vendor is independent of system now, so wiping system doesn't affect it. There's a sticky thread in the general section detailing the problem with security and backups, very easy to find.

tfly212 said:
The password problem is fixable...within twrp you need to delete the password file. See this thread for details: http://forum.xda-developers.com/showthread.php?t=3245070
Click to expand...
Click to collapse
Ended up just doing a clean install after everything was straightened out.
Heisenberg said:
Vendor is independent of system now, so wiping system doesn't affect it. There's a sticky thread in the general section detailing the problem with security and backups, very easy to find.
Click to expand...
Click to collapse
I didn't know about the overlays being stored in vendor at the time so the sticky thread wouldn't have stood out as being helpful [emoji14]
I never messed with layers on my Nexus 5 as I like the stock MM theme, but now on my Nexus 6p with it having an AMOLED screen I wanted something dark for battery savings and such. Also kinda wanted to switch things up being a new phone and all.
If my settings keeps FC when I apply dark material layer, what could be the culprit? Someone mentioned needing to installing busy box since I'm on Cataclysm... Well I have the app installed, but I'm not quite sure how to install it further... There is smart install and the other option. Not even sure what busy box does lol.
Sent from my Nexus 6P running Cataclysm & ElementalX.

Fixing permissions in twrp fixed my FC's when I first installed layers.