• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Virgin Mobile] Unfortunately, process com.android.phone has force closed

D

droiddekka

Well-Known Member
Over and over again. Usually while I'm on a phone call. The signal bars disappear and then it happens six or seven more times while LTE comes back.

This happens on AOKP 4.2.2 and 4.3 but not slim bean 4.3


I am Knox free and just Odin'd the mk3 4.3 stock rom



What's the damn deal?
 
for me when this happens the only fix was to ensure a full wipe before flashing the rom.

let it settle the go back for mod flashing
 
no this does not happen on the stock rom.

when i bought the phone it had 4.1 on it...then i rooted and flashed a 4.3 aokp (the cnexus sprint version) and this issue started happening.

at first it was immediately upon booting and then it would stop.

now...whenever i'm on a phone call it crashes after a minute or 2.

i can make and receive calls fine, just always crashing during the call. and the call is dropped.

is my phone.apk or telephony provider.apk the problem?


i tried pushing a phone.apk from the slim bean 4.3 rom to my aokp rom and immediately it rebooted and the com.android.phone service just started crashing like crazy. i had to restore my backup.



i always do a full wipe between flashes, and i'm using the latest philz CWM recovery.



i've flashed a few phones in my day but this has me stumped. aokp is the only rom i run on my phone.


should i be using different firmware? i'm on MK3 currently but have also tried md4 and md7 and have had the same problem.



:confused::confused::confused::confused::confused:
 
I'm pretty sure that this happens when the APNs are messed up. Try flashing the MopedRyder APN patch. Sometimes #3 does not work on new roms and you have to flash #2. I flashed the 3rd patch on several roms and had this problem. I started flashing #2 on the roms and the problem was resolved. Best of luck!
 
mablake184 said:
I'm pretty sure that this happens when the APNs are messed up. Try flashing the MopedRyder APN patch. Sometimes #3 does not work on new roms and you have to flash #2. I flashed the 3rd patch on several roms and had this problem. I started flashing #2 on the roms and the problem was resolved. Best of luck!
Click to expand...

Looking with no luck. Can someone post a link to #2?
TIA

Update - Never mind; just located it.
 
Did it fix the problem? Sometime you have to flash the rom and then flash the APN fix before reboot for it to be effective.
 
mablake184 said:
Did it fix the problem? Sometime you have to flash the rom and then flash the APN fix before reboot for it to be effective.
Click to expand...

I had this basic issue on 4.3.x ROM's, where I would get that message after any reboot, two times back to back, but then never again until the next reboot. I have yet to see it on 4.4.x however. My current sequence for flashing a new ROM is to flash the ROM and the APN fix in the same session, after a clean wipe, and then boot into system, let things settle, boot back to recovery and flash GApps, boot back to system, let things settle again for a few minutes, then get set up. Then one more time back to recovery for tweaks and mods like the Dalvik patch or custom kernel. The exception to this is Carbon, their website states that ROM and GApps need to be flashed together before first boot into system; based on the initial setup I can see why, since part of that setup is to get your Google account signed in and running.
 
struckn said:
I had this basic issue on 4.3.x ROM's, where I would get that message after any reboot, two times back to back, but then never again until the next reboot. I have yet to see it on 4.4.x however. My current sequence for flashing a new ROM is to flash the ROM and the APN fix in the same session, after a clean wipe, and then boot into system, let things settle, boot back to recovery and flash GApps, boot back to system, let things settle again for a few minutes, then get set up. Then one more time back to recovery for tweaks and mods like the Dalvik patch or custom kernel. The exception to this is Carbon, their website states that ROM and GApps need to be flashed together before first boot into system; based on the initial setup I can see why, since part of that setup is to get your Google account signed in and running.
Click to expand...

I'm running the 02/05/2014 Carbon ROM and get exactly what you referred to Stuckn - 2 back to back messages every time I reboot.

I think I'll try a clean wipe followed with flashing the ROM, APN fix and Gapps this weekend and see what happens (or should I boot after ROM and Gapps and then go back and flash the APN fix later?).
 
cmichael258 said:
I'm running the 02/05/2014 Carbon ROM and get exactly what you referred to Stuckn - 2 back to back messages every time I reboot.

I think I'll try a clean wipe followed with flashing the ROM, APN fix and Gapps this weekend and see what happens (or should I boot after ROM and Gapps and then go back and flash the APN fix later?).
Click to expand...

For Carbon, do this sequence: after clean wipe (do it 2x just to be sure), flash ROM, APN fix of your choice, and GApps of your choice (P.A. 0-Day GApps most recent version is my recommendation) all in the same session, then boot into system. Make sure you backup (Nandroid) your current version of things first though, just in case.
 
struckn said:
For Carbon, do this sequence: after clean wipe (do it 2x just to be sure), flash ROM, APN fix of your choice, and GApps of your choice (P.A. 0-Day GApps most recent version is my recommendation) all in the same session, then boot into system. Make sure you backup (Nandroid) your current version of things first though, just in case.
Click to expand...

Thanks; I'll try it tonight.

Update: The clean wipe seems to have done the trick
 
You must log in or register to reply here.
Back
Top Bottom