[Q] process com.android.phone has stopped unexpectedly - EVO 4G Q&A, Help & Troubleshooting

Long time member - first time poster.
I have a bizarre problem. I have flashed and used at least a dozen ROMs, with various kernels, most recently Myn's RLS 2 as my daily driver.
Recently, I installed MIUI EVO v1.29, which worked fine. However, when I tried to flash back to Myn's, I got a "process com.android.phone has stopped unexpectedly" error at start-up. Same error anytime I use the phone or dialer functions for anything. Phone will not make calls or connect to Sprint, force-close when trying to view software properties in "About Phone," won't allow me to do a "restore" from ##DATA#. Same problems on Cyan, Frost and several others.
However, all functions in MIUI still work fine with no error messages as does the latest rooted stock. All other ROMs I've tried are basically non-functional.
I have tried wiping cache, dalvik cache and user data. I have tried updating to the latest radio and PRI (successfully). I have tried restoring from ##DATA# in the working stock ROM.
Any ideas on how I can fix my phone and continue to enjoy custom ROMs?
Thanks in advance.

I've only had this problem when installing any app that tries to interact with the phone - specifically call log widgets (sms& call log app).
Sent from my PC36100 using XDA App

Can you restore the process with titanium? Might help...just a shot in the dark really

Cy_n_ic said:
Can you restore the process with titanium? Might help...just a shot in the dark really
Click to expand...
Click to collapse
I'll give it a shot, but even if it works, it wouldn't explain the issue with a clean install.

Related

[Q] Problems after flashing rooted Gingerbread.

I rooted my EVO and flashed radio 'EVO_Radio_2.15.00.05.02_WiMAX_27243_PRI_2.15_003.zip'
Then I flashed a rooted stock gingerbread/sense ROM 'supersonic_4.22.651.2_deodexed-signed.zip'
Problem 1: I reinstalled a bunch of my apps using Titanium Backup, but none of these apps are showing up in the Market.
Problem 2: I cannot sync Facebook for HTC Sense. Whenever I try to sign in, I keep getting the error "The service is currently unavailable. Do you want to try again?"
I have tried all sorts of things like uninstalling all Facebook for Android updates and even a supposed fix I found in other forums in which you edit your work information on your facebook profile. Nothing seems to work.
Can anyone help?
slikazsilk13 said:
I rooted my EVO and flashed radio 'EVO_Radio_2.15.00.05.02_WiMAX_27243_PRI_2.15_003.zip'
Then I flashed a rooted stock gingerbread/sense ROM 'supersonic_4.22.651.2_deodexed-signed.zip'
Problem 1: I reinstalled a bunch of my apps using Titanium Backup, but none of these apps are showing up in the Market.
Problem 2: I cannot sync Facebook for HTC Sense. Whenever I try to sign in, I keep getting the error "The service is currently unavailable. Do you want to try again?"
I have tried all sorts of things like uninstalling all Facebook for Android updates and even a supposed fix I found in other forums in which you edit your work information on your facebook profile. Nothing seems to work.
Can anyone help?
Click to expand...
Click to collapse
For the apps not showing up in your market it takes time and a reboot or two. The facebook thing I'm not sure about though, it wouldn't work right for me from day one so I haven't tried to use it in awhile.
Why do people need their apps to show up in the market if they already have them reinstalled with TB??
HipKat said:
Why do people need their apps to show up in the market if they already have them reinstalled with TB??
Click to expand...
Click to collapse
I just find it helpful to see which apps need updating. It's definitely not essential.
For the apps download a free app from the market and they should show up they did for me.
Sent from my PC36100 using XDA App
Problem 1: I reinstalled a bunch of my apps using Titanium Backup, but none of these apps are showing up in the Market.
Click to expand...
Click to collapse
Normal when flashing a rom. Give it a few reboots and wait a day or so.
Problem 2: I cannot sync Facebook for HTC Sense. Whenever I try to sign in, I keep getting the error "The service is currently unavailable. Do you want to try again?"
Click to expand...
Click to collapse
Again, just wait a day or so.
sitlet said:
Normal when flashing a rom. Give it a few reboots and wait a day or so.
Again, just wait a day or so.
Click to expand...
Click to collapse
I'm sensing a pattern...
Thanks a lot guys. Today was my first experience with flashing. I can see why it's addicting.
I have a different problem after I flashed to the latest Gingerbread ROM, (on my eVO 4G btw). I flashed the latest ROM "gingerbread evo 1.2v", when that finished i flashed "EVO_Radio_2.15.00.05.02_WiMAX_27243_PRI_2.15_003" (was told it should fix any radio issues). then flashed "gapps 5-21-2011 with Voicemail.apk and Gtalk 1.3 with Voice and Video". My EVO restarted fine but now i cant make any calls or recieve any. In fact the status bar at the top isn't even there. When i press the phone icon i get a message saying "Application not installed on your phone". I must be missing a step or something. Any help would be great, thanks.
Doujouyaburi said:
I have a different problem after I flashed to the latest Gingerbread ROM, (on my eVO 4G btw). I flashed the latest ROM "gingerbread evo 1.2v", when that finished i flashed "EVO_Radio_2.15.00.05.02_WiMAX_27243_PRI_2.15_003" (was told it should fix any radio issues). then flashed "gapps 5-21-2011 with Voicemail.apk and Gtalk 1.3 with Voice and Video". My EVO restarted fine but now i cant make any calls or recieve any. In fact the status bar at the top isn't even there. When i press the phone icon i get a message saying "Application not installed on your phone". I must be missing a step or something. Any help would be great, thanks.
Click to expand...
Click to collapse
I read in another forum you sometimes need to re-flash the kernel after flashing new radios. You could try re-flashing the ROM now that you have the updated radios.
just tried flashing the rom after everything else and still same results. Any other suggestions?
Doujouyaburi said:
just tried flashing the rom after everything else and still same results. Any other suggestions?
Click to expand...
Click to collapse
I'm new to flashing ROMs personally, but I've also read people recommending to do a clean wipe 2 or 3 times and wipe the dalvik cache as many times before flashing again. I don't know what sort of issues they feel they are preventing by doing that so I don't know how plausible of a solution it is, but if you've got the time it wouldn't hurt to try.
Hopefully someone with more experience will chime in and you won't have to get your advice from a noob. Best of luck.

[Q] Messaging (and DRM content) processes stopping unexpectedly on boot?

Today I took a picture with my phone and my phone froze up shortly after viewing the picture for some odd reason. So I soft reset it with a battery pull. When I started my phone back up I received a few error messages. The first one was that the DRM Content process had stopped unexpectedly (I think this was happening before my phone froze up). The second one was that the Messaging process had stopped unexpectedly, and the third was Handcent stopping unexpectedly.
After this happened I tried opening up Handcent, to which it displays the same force close error for a split second and then automatically closes. I uninstalled Handcent and tried opening the regular Messaging application, to which it displays some sort of force close error for a split second and then closes.
I was running the SyndicateROM Frozen 1.1.0. I tried updating to the ACS SyndicateROM Frozen 1.1.1 to see if it would fix my problem. It didn't
Does anyone have any suggestions on how to troubleshoot this?
You had journaling off. You can't reboot the phone without powering off or you wind up with data corruption and force closes. You need to reflash your rom and then use the re eable journaling zip in the development section. Also it wouldn't hurt if you researched things before posting, there have to be > 50 posts about this.
NateTheGreatt said:
Today I took a picture with my phone and my phone froze up shortly after viewing the picture for some odd reason. So I soft reset it with a battery pull. When I started my phone back up I received a few error messages. The first one was that the DRM Content process had stopped unexpectedly (I think this was happening before my phone froze up). The second one was that the Messaging process had stopped unexpectedly, and the third was Handcent stopping unexpectedly.
After this happened I tried opening up Handcent, to which it displays the same force close error for a split second and then automatically closes. I uninstalled Handcent and tried opening the regular Messaging application, to which it displays some sort of force close error for a split second and then closes.
I was running the SyndicateROM Frozen 1.1.0. I tried updating to the ACS SyndicateROM Frozen 1.1.1 to see if it would fix my problem. It didn't
Does anyone have any suggestions on how to troubleshoot this?
Click to expand...
Click to collapse
Download enable journaling from here:
http://forum.xda-developers.com/showthread.php?t=1071723
Flash it after you reflash your rom.
I flashed the reenable journaling zip after reflashing my ROM. The DRM Content force close error still pops up when I boot up, and my Messaging is still crashing :/. What am I missing? Or could there be another problem?
NateTheGreatt said:
I flashed the reenable journaling zip after reflashing my ROM. The DRM Content force close error still pops up when I boot up, and my Messaging is still crashing :/. What am I missing? Or could there be another problem?
Click to expand...
Click to collapse
Have you tried a different kernel? Or something you are restoring from Titanium or Mybackup is causing.
I would start from scratch go back to stock, reroot with cwm 3.0.2.5, d/l ext4 conversion here http://forum.xda-developers.com/showthread.php?t=1109362, flash ext4 conversion, flash Frozen 1.1.1, flash journaling enable. Do not restore anything see if you still have the issue. If not then something you are restoring is causing your issue.
I don't have Titanium or Mybackup. The only backups I have are within CWM, made from flashing my ROM. I will try what you suggested, thanks.
Edit:
To go to stock, do I just wipe data/factor reset from CWM? Also is there any way to do what you said while still retaining all of my contacts/texts? I cannot lose my SMS history. There is valuable information within.
NateTheGreatt said:
I don't have Titanium or Mybackup. The only backups I have are within CWM, made from flashing my ROM. I will try what you suggested, thanks.
Edit:
To go to stock, do I just wipe data/factor reset from CWM? Also is there any way to do what you said while still retaining all of my contacts/texts? I cannot lose my SMS history. There is valuable information within.
Click to expand...
Click to collapse
Mybackup does txt and sms backups. Make sure you do a nan backup also just in case. You need to odin back to stock. Go here for step by step
http://forum.xda-developers.com/showthread.php?t=773032&highlight=odin+stock
Okay, I tried a bunch of SMS backup programs to no avail. Every one I tried would either crash or throw an error when it tried to back up my text messages.
I went back to stock, wiped my data/cache/system, and then flashed back Frozen 1.1.1 again. Everything worked fine until I tried recovering my data. The Messages process crashes again after recovering my data
Is my SMS history unrecoverable?
Is sms crashing or just the back up of the sms? What are you using to back up and recover your txt?
tazfanatic said:
Is sms crashing or just the back up of the sms? What are you using to back up and recover your txt?
Click to expand...
Click to collapse
The whole reason this started was because my SMS messages application started crashing. I am trying to recover my texts. I tried using 5 or 6 SMS backup utilities, but to no avail. I didn't try anymore because I figured none of them are going to work. Something in my SMS history is borked :/
Thinking the same thing sorry. Not sure if someone else has any ideas. Do you have a nan backup from before the issue started? Yeah you might lose some txt but not all.

[Q] Reboot on unlock after receiving texts.

Hi All,
I have a droid incredible that I was running CM7 on. At some point the phone started rebooting randomly when I pressed the unlock button. This happened a few times a day and I eventually realized that these reboots were only happening when I unlocked the phone after receiving a text.
This didn't happen on all texts, but maybe half or so. I've done the following to try to remedy the problem, but it is still occurring:
- wiped cache/dalvik cache.
- methodically removed app by app, cleared app data.
- removed all phone/rom backups.
- wiped data/factory reset of CM7.
- installed latest MIUI rom.
- wiped data/factory reset of MIUI.
I am currently running a wiped MIUI rom with only the apps that came preloaded on the rom. I feel like I've tried everything and can't figure this out!
Anyone have any thoughts on this? Thanks so much for your help!
It's still happening on MIUI or only on the CM7? Was it a Nightly?
Is messages cache full, or nearly so?
Sent from my ADR6300 using XDA Premium App
Bull_Moose, I have been using the latest CM7 RC1... never used a nightly. The ROM worked fine for a while and then a few months ago started rebooting after receiving texts. I switched over to MIUI, hoping it would solve my issues...but it didn't.
smtom, Is there a messages cache that can be cleared specifically? I've never seen it. I'm assuming, though, that since I've done several complete wipes of the phone that all caches would have been cleared anyways...
The sheer number of messages, over time, will yield the dreaded low on space notice. This is rendered moot by either backup of messages somewhere using something like SMS Backup +, or deleting threads, and storing your multimedia message attachments to sd or elsewhere. Couple questions : are you restoring messages across or between ROM's? What messaging application are you using?
Sent from my ADR6300 using XDA Premium App
Hi smtom,
Sorry for the delay. So, I do regularly use SMS Backup and Restore to archive my messages into separate files so that I can occasionally delete all message threads and clear up space.
When I have wiped or switched roms in the past I have always done clean installs, which should clear all message memory, right? I am currently just using whatever SMS app comes preinstalled on MIUI.
My problem with the phone restarting has continued despite all of this... but I wonder if using a 3rd party messaging app could make a difference. Hmmmm.
Ray
RayLJill, have you figured anything out since switching to a 3rd party app? My friend's incredible is getting the random reboots, new sms text messages or not. He is on most current CM7 Nightly after I did a complete wipe/factory reset/format all memory and clean install (he was having this issue on CM7 nighties before i did the clean install, still didn't help i guess)

Talk Authentication Error after restoring!

So I rooted my phone yesterday using Zedomax kernel v3 on a Mac using terminal. I then stupidly tried to wipe data and cache because of an error message I was receiving. After doing so couldn't get my phone to but up until I restored using Zedomax restore file posted in another thread. After restoring I then reinstalled the Zedomax kernel v3 using CWM and now I get an error message around Talk not being able to authenticate. I looked into some of the other threads and really only found the solution of rooting back to stock using the ACS kernel and couldn't get my phone to ever actually boot back up. I could only get the phone to boot up and stay on the vanilla android logo. So long story short what are my options to get this fixed?
Go to menu- settings- Applications - manage applications- running services- CLICK ALL TAB- scroll down and find Google service framework. Now clear the cache. Restart the phone and you should ever have this issue again. If you still have the issue, wipe phone and reinstall v3 or v4 and wipe Google framework and problem will definitely be fixed. And yes it could be restoring apps or ROM that's causing the issue.
Thanks, I did this and it seems to be working for now. We will see how long it lasts, hopefully it does.

Issue with TeamDIRT's REM-ICSux ROM

Hey guys. New to XDA, not new to flashing ROM's on my EVO.
I've been a longtime user of MikG, decided to try something different and flash an ICS rom, and this is the one I went with. Install went smooth, and everything booted, but i'm having a minor issue:
When attempting to access my contacts or use the phone to make a call, I constantly get an FC saying "Unfortunately, Contacts has Stopped."
Any ideas?
Try wiping ur caches, and fixing permissions in recovery
Sent from my PC36100 using Tapatalk 2
ottoman673 said:
Hey guys. New to XDA, not new to flashing ROM's on my EVO.
I've been a longtime user of MikG, decided to try something different and flash an ICS rom, and this is the one I went with. Install went smooth, and everything booted, but i'm having a minor issue:
When attempting to access my contacts or use the phone to make a call, I constantly get an FC saying "Unfortunately, Contacts has Stopped."
Any ideas?
Click to expand...
Click to collapse
Some times fixing permissions "may" correct that issue... You can boot to recovery and fix permissions there, or use one of the several apps that you can fix permissions thru [CWM/TE]
Formatted /cache successfully.
First time formatting Dalvik led to E:unknown volume for path [/sd-ext], but the second time was successful.
Fixed permissions.
Upon reboot, Android had to upgrade, and optimize 111 apps. Never seen that before? o.o
Issue seems to be fixed now, though. Thanks!
That a feature of ICS. I believe it's re-linking each app to the Dalvik Cache

Categories

Resources