Develop Bugs

The process com.android.phone has stopped unexpectedly

So I've seen other people that have this problem but the difference is usually they get the message when opening this or that, while I get the message constantly. As is, if I force close it, it pops right back up again leaving me no time to actually do anything on my phone.
Any help would be appreciated, I have CM7 installed and this just happened after a reboot.

Did you flash the latest gapps when you flashed CM7?

Yeah, and CM7 had been working great up till this point. Now it says I have no service and I can't do much of anything.

TheUnknowing said:
Yeah, and CM7 had been working great up till this point. Now it says I have no service and I can't do much of anything.
Click to expand...
Click to collapse
Did you flash anything without wiping data? if you did you might have to wipe data. Before you do that try to fix permissions in rom manager and clear the data for the phone app. If those things dont work wipe data. If a data wipe doesnt work you have a problem with the ROM you flashed. If its a nightly you should either flash a different nightly or flash the stable.
As for the service you can try to flash a new radio. If that doesnt work i recommend going back to a sense rom updating your profile, and then your PRL. I wouldnt imagine the radio is the problem, because ROM's shouldnt normally include radio files, but you might as well try to flash the newest radio anyways. Newest radio is 2.15.00.11.19.
flashing a new radio, updating your prl, and updating your profile are about the only things you can do to help your service. updating prl and profile can only be done on sense roms through settings, because those involve sprint code, which is not made public.

Update: I'm not sure how to do most of the things you mentioned but my radio is up to date. I discovered that this problem only occurs after I reboot the phone. It flashes fine, works normally, but once I reboot it the problem starts up.

[Q] 3g data issues

i have tried following the instructions on another thread i found here about trying to fix a 3g issue with the incredible and new roms, but i have not been able to get my 3g back. currently i am running a stock ruu. my system info reads s follows...
Android ver
2.2
baseband ver
2.15.00.07.28
Kernel ver
2.6.32.15-gb7b01d1
htc-kernel @and18-2 #1
build number
3.21.605.1 CL231334 release-keys
software number
3.21.05.1
ClockworkMod Recovery v2.5.1.2
i have rooted again since i ruu'd and have more or less just lived with it while trying to figure it out on my own. it seems to be random sometimes i will be able to look stuff up other times not so much. i know it isn't my service area as i have a work blackberry on verizon and that is fine. does anyone think this could be a software issue or does this sound like hardware. i am really hoping it is software as i have had my incredible since launch and really don't want to get it replaced, lol. i appreciate any help you guys can give me.
could it be the radio i have flashed? i dont know a whole lot about them so i havnt done a whole lot of troubleshooting there. can i go backwards with radio flashing? i just want to be sure before i try that as to not brick.

Does your 3g disappear or drop down to 1x often? You say you tried another thread, could you link me to it so I know what you did OR could you explain what steps you have done to alleviate this?
The typical solution is to flash a stock rom then boot into the rom itself and leave it running for a minute or two, even make a call and check 3g to make sure it's working. Then restore your backup rom and enjoy life. I'll provide you a stock rom link with steps to follow in a few minutes.

found it. i followed this thread and reverted back to stock. still hasn't helped my 3g woes. could having the wrong radio cause these problems?
http://forum.xda-developers.com/showthread.php?t=817487&highlight=3g+fix
***Edit i generally don't even have the 3G symbol in my notification bar or if it is there like now it just wont connect sometimes. in settings it says mobile network is connected as well

undeclared said:
found it. i followed this thread and reverted back to stock. still hasn't helped my 3g woes. could having the wrong radio cause these problems?
http://forum.xda-developers.com/showthread.php?t=817487&highlight=3g+fix
***Edit i generally don't even have the 3G symbol in my notification bar or if it is there like now it just wont connect sometimes. in settings it says mobile network is connected as well
Click to expand...
Click to collapse
Aight, the rom link in my instructions is this one from RMK40. His link has since gone down. It is the first leaked OTA from last May prior to the flood of gingersense roms.
1. Boot into recovery and perform a Nandroid
2. In recovery, do a Factory reset/Wipe Cache/Wipe Dalvik Cache
3. Flash this
4. Boot into the rom and make a test call. Also check your 3g connection and see if it works. You can run it for ten minutes or an hour if you want to see if the connection fails, although it shouldn't.
5. Reboot into recovery and do Nandroid restore
6. Enjoy.
Post back with your results.
Edit: Here is a reference thread from where I obtained my instructions. I believe you are in the same scenario.
http://forum.xda-developers.com/showthread.php?t=1229732

i did a back up, wiped and flashed the rom, twice, both times i got boot loops :-/
maybe it's my radio?

undeclared said:
i did a back up, wiped and flashed the rom, twice, both times i got boot loops :-/
maybe it's my radio?
Click to expand...
Click to collapse
I would flash the froyo ruu thru hboot and then reboot. Then go back to hboot and select factory data reset, or boot to the os and go to Menu Settings Sd & phone storage and select factory data reset. Let it do its thing and then reboot. Once it boots up do the ota programing and your 3g should be fixed. Then you can flash cwm recovery thru hboot, and the su binary thru recovery and you will be rooted and ready to flash roms again. I have had this happen several times when using sense 3/3.5 roms ported from sprint phones.
Also that radio is old, from froyo, but that shouldt be the issue. If a factory reset dosent fix it i guess it wouldnt hurt to try updating to the newest radio. Im 95% positive factory reseting the phone from hboot or the settingd menu will fix your 3g. You have to have the stock recovery for the reset to work, that is why you need to ruu again, unless you are already on the stock recovery.

thanks i think this is working i just got done with programming and now i have 3g! gonna stress test it till later tonight i think and then it is off to flashing a new rom! any rom either of you suggest that shouldn't give me these 3g issues?
again thanks so much for your help

undeclared said:
thanks i think this is working i just got done with programming and now i have 3g! gonna stress test it till later tonight i think and then it is off to flashing a new rom! any rom either of you suggest that shouldn't give me these 3g issues?
again thanks so much for your help
Click to expand...
Click to collapse
It usually happens to me on roms ported from sprint phones, mostly after doing a *228. I would highly advise not to do a *228 on a sprint rom. If you want to be extra cautious i wold just stay away from sprint ported roms all together.

[Solved] Urgent, LTE issue.

Solved! ODIN'd back to stock and LTE kicked in immediately. Back to flashing =) Thanks guys!
Original Post:
============================================================================
Hello everyone,
I need some immediate help please. I flashed GalaxyMod TouchWiz ROM (coming from Vanilla RootBox). I flashed because I was looking for a more stable ROM and started having the following issue:
After the flash I only get 3G for roughly 5-10 minutes. After about 5-10 minutes LTE finally activates. This persists through ROM flashes. This happens after every reboot and after toggling airplane mode.
I have since flashed Task650's AOKP and CM10.1 and the above issue is still present. I have checked my APN settings, which are on PTA. I also checked my preferred network and this is where I noticed an oddity. It is stuck on WCDMA preferred for the first 5-10 minutes and then finally changes by itself to LTE / GSM/WCDMA.
Steps I've taken so far:
1.) Flashed the LTE fix (while still on GalaxyMod ROM) which was provided in the GalaxyMod thread. This made no affect on the issue at all.
2.) Flashed new modems, no affect at all.
3.) Wiped Cache, Dalvik Cache, Factory Reset, System, Internal Memory and Data, reflashed a new ROM, no affect.
I never had any delay in connecting to LTE prior to flashing GalaxyMod, and now I get it on every ROM I flash thereafter.
What can be causing this? I am thinking the only thing I can do is Triangle Away, ODIN back to Stock and send it to Samsung.
If you have any suggestions at all, please let me know. I am desperate to get this working.
At the time of this post I'm running TWRP 2.4.1.0, CM10.1 and the packaged CM Kernel that comes with the ROM.

RPelham said:
Hello everyone,
I need some immediate help please. I flashed GalaxyMod TouchWiz ROM (coming from Vanilla RootBox). I flashed because I was looking for a more stable ROM and started having the following issue:
After the flash I only get 3G for roughly 5-10 minutes. After about 5-10 minutes LTE finally activates. This persists through ROM flashes. This happens after every reboot and after toggling airplane mode.
I have since flashed Task650's AOKP and CM10.1 and the above issue is still present. I have checked my APN settings, which are on PTA. I also checked my preferred network and this is where I noticed an oddity. It is stuck on WCDMA preferred for the first 5-10 minutes and then finally changes by itself to LTE / GSM/WCDMA.
Steps I've taken so far:
1.) Flashed the LTE fix (while still on GalaxyMod ROM) which was provided in the GalaxyMod thread. This made no affect on the issue at all.
2.) Flashed new modems, no affect at all.
3.) Wiped Cache, Dalvik Cache, Factory Reset, System, Internal Memory and Data, reflashed a new ROM, no affect.
I never had any delay in connecting to LTE prior to flashing GalaxyMod, and now I get it on every ROM I flash thereafter.
What can be causing this? I am thinking the only thing I can do is Triangle Away, ODIN back to Stock and send it to Samsung.
If you have any suggestions at all, please let me know. I am desperate to get this working.
At the time of this post I'm running TWRP 2.4.1.0, CM10.1 and the packaged CM Kernel that comes with the ROM.
Click to expand...
Click to collapse
Running galaxymod right now and in DFW area with great LTE coverage and never had the issues you had or any for that matter. Somehow in the flashing, I'm going to get real technical here right now , something got borked that isn't affected by flashing a new ROM. We could give to several things to try but honestly flashing back to factory out of the box and starting from there is the only fail safe way to do it. probably faster too. That's I would do

hednik said:
Running galaxymod right now and in DFW area with great LTE coverage and never had the issues you had or any for that matter. Somehow in the flashing, I'm going to get real technical here right now , something got borked that isn't affected by flashing a new ROM. We could give to several things to try but honestly flashing back to factory out of the box and starting from there is the only fail safe way to do it. probably faster too. That's I would do
Click to expand...
Click to collapse
Thanks for the reply. I just downloaded root-injected stock and am flashing as we speak. If this doesn't work, I'm going to flash back to bone-stock and see how that goes. I'll report back and let everyone know =)

RPelham said:
Hello everyone,
I need some immediate help please. I flashed GalaxyMod TouchWiz ROM (coming from Vanilla RootBox). I flashed because I was looking for a more stable ROM and started having the following issue:
After the flash I only get 3G for roughly 5-10 minutes. After about 5-10 minutes LTE finally activates. This persists through ROM flashes. This happens after every reboot and after toggling airplane mode.
I have since flashed Task650's AOKP and CM10.1 and the above issue is still present. I have checked my APN settings, which are on PTA. I also checked my preferred network and this is where I noticed an oddity. It is stuck on WCDMA preferred for the first 5-10 minutes and then finally changes by itself to LTE / GSM/WCDMA.
Steps I've taken so far:
1.) Flashed the LTE fix (while still on GalaxyMod ROM) which was provided in the GalaxyMod thread. This made no affect on the issue at all.
2.) Flashed new modems, no affect at all.
3.) Wiped Cache, Dalvik Cache, Factory Reset, System, Internal Memory and Data, reflashed a new ROM, no affect.
I never had any delay in connecting to LTE prior to flashing GalaxyMod, and now I get it on every ROM I flash thereafter.
What can be causing this? I am thinking the only thing I can do is Triangle Away, ODIN back to Stock and send it to Samsung.
If you have any suggestions at all, please let me know. I am desperate to get this working.
At the time of this post I'm running TWRP 2.4.1.0, CM10.1 and the packaged CM Kernel that comes with the ROM.
Click to expand...
Click to collapse
Did you check to see if your IMEI is missing?
I had the same issue on GalaxyMod. I had to do a clean install of the ROM, apply KT's kernel, and apply the LTE fix BEFORE I rebooted. I could not tell from your post if you did a clean install of GalaxyMod. Then I checked my IMEI and it was missing, so I performed the fix found here http://forum.xda-developers.com/showthread.php?t=1801997 and repeated the steps above. Worked for me as I get LTE speeds now on GalaxyMod.

peaster3 said:
Did you check to see if your IMEI is missing?
I had the same issue on GalaxyMod. I had to do a clean install of the ROM, apply KT's kernel, and apply the LTE fix BEFORE I rebooted. I could not tell from your post if you did a clean install of GalaxyMod. Then I checked my IMEI and it was missing, so I performed the fix found here http://forum.xda-developers.com/showthread.php?t=1801997 and repeated the steps above. Worked for me as I get LTE speeds now on GalaxyMod.
Click to expand...
Click to collapse
I'm getting LTE speeds, problem is after toggling airplane mode or rebooting the phone it takes up to 10 minutes for LTE to activate. I fresh installed GalaxyMod, wiped everything possible in the wipe menu of TWRP with the exception of external SD.
I also applied the LTE fix before I booted GalaxyMod, but I did not flash KT747. I prefer to not flash that kernel because it has the updated BT/WIFI drivers and had a warning that I would need to back those drivers up if I ever wished to revert. I don't really feel like going through all of that lol.

Solved. ODIN'd back to stock =) Thanks hednik!

RPelham said:
Solved. ODIN'd back to stock =) Thanks hednik!
Click to expand...
Click to collapse
Glad it worked.... these phones are almost fool proof as you can start with a clean slate if all else fails. Glad it worked
IMEI was still intact ?

hednik said:
Glad it worked.... these phones are almost fool proof as you can start with a clean slate if all else fails. Glad it worked
IMEI was still intact ?
Click to expand...
Click to collapse
Yupp I haven't yet lost my IMEI since I got the phone back in July. Guess I'm lucky so far, see posts all the time where people lose it, and I'm a flashaholic lol.
Sent from my SGH-I747 using xda app-developers app

[Q] mic doesn't work with calls

Calls worked until I installed cm10.1 nightly. Now I can't be heard unless i turn on speaker phone. Sound is still crap but at least I can make a call.
I have tried a few nightly's and now I'm on the people's rom 3.14. (Loving tpr by the way). I doubt it is a hardware issue based on other reports and the fact it was fine until the custom roms.
I still use my phone as a phone from time to time and need it to work or I have to go back to stock.
Thanks

Could have been a bad flash / download
Did you check the md5sum?

leftcranium said:
Calls worked until I installed cm10.1 nightly. Now I can't be heard unless i turn on speaker phone. Sound is still crap but at least I can make a call.
I have tried a few nightly's and now I'm on the people's rom 3.14. (Loving tpr by the way). I doubt it is a hardware issue based on other reports and the fact it was fine until the custom roms.
I still use my phone as a phone from time to time and need it to work or I have to go back to stock.
Thanks
Click to expand...
Click to collapse
Let me make sure I'm understanding you correctly:
Your mic was working fine until you flashed the CM10.1 nightly. Afterwards, the other person could only hear you when you were on speakerphone.
You switched to TPR 3.14. This switch did not fix the mic problem.
You're thinking that switching back to stock (presumably unrooted) will fix this issue.
Please correct me if any of the above is incorrect.
If he issue isn't hardware-related, I'd bet it has to do with the kernel. Let me ask you the following:
Which CM10.1 nightly did you install? Did you see any other issues in the CM10.1 thread which might indicate problems with the nightly you flashed?
What kernel did you use while on CM10.1? I know that the newer kernels (3.4.y verses the old 3.0.y) have had issues and are just recently getting stable.
As CNexus asked,did you check the md5sum for the TPR Rom you flashed?
When you flashed TPR, did you do a full system wipe, or only a Factory Reset (data) wipe? I believe since you were coming from a 4.2.2 Rom (CM 10.1) to a 4.1.2 Rom (TPR), you should do a full system wipe. Some remnants of the CM10.1 kernel/system files could still be there, messing up the mic.
I would think re-flashing TPR (after checking the md5sum) with a full system wipe would fix your issue, but answering these questions would help us diagnose the problem better.

topherk said:
Let me make sure I'm understanding you correctly:
Your mic was working fine until you flashed the CM10.1 nightly. Afterwards, the other person could only hear you when you were on speakerphone.
You switched to TPR 3.14. This switch did not fix the mic problem.
You're thinking that switching back to stock (presumably unrooted) will fix this issue.
Please correct me if any of the above is incorrect.
If he issue isn't hardware-related, I'd bet it has to do with the kernel. Let me ask you the following:
Which CM10.1 nightly did you install? Did you see any other issues in the CM10.1 thread which might indicate problems with the nightly you flashed?
What kernel did you use while on CM10.1? I know that the newer kernels (3.4.y verses the old 3.0.y) have had issues and are just recently getting stable.
As CNexus asked,did you check the md5sum for the TPR Rom you flashed?
When you flashed TPR, did you do a full system wipe, or only a Factory Reset (data) wipe? I believe since you were coming from a 4.2.2 Rom (CM 10.1) to a 4.1.2 Rom (TPR), you should do a full system wipe. Some remnants of the CM10.1 kernel/system files could still be there, messing up the mic.
I would think re-flashing TPR (after checking the md5sum) with a full system wipe would fix your issue, but answering these questions would help us diagnose the problem better.
Click to expand...
Click to collapse
I think you have the symptoms correct.
I did a data wipe but not a factory reset before each rom install.
I started with this rom
cm-10.1-20130303-NIGHTLY-d2spr.zip
I tried 3/13, 3/24 and 3/27 before trying TPR3.14.

leftcranium said:
I think you have the symptoms correct.
I did a data wipe but not a factory reset before each rom install.
I started with this rom
cm-10.1-20130303-NIGHTLY-d2spr.zip
I tried 3/13, 3/24 and 3/27 before trying TPR3.14.
Click to expand...
Click to collapse
Yeah, a full system wipe might be the ticket. Let us know if that works.

I'm Back Baby
I tried a system wipe and a rooted stock rom. This didn't work. I then tried the LJ7_Stock_with_count_reset16 rom and my sound was ok. I cleaned out the mic hole with a pin and bam sound was like normal. I'm now back on TPRGS3.14 and everything is good. I think I had 2 issues but possibly only 1. messed up mic from multiple flashes and crap in the mic hole. I guess checking for a physical problem even as small as a mic debris is an easy first step.
thanks for the suggestions

[Q] GAAPs seem to break WiFi in CM 10.1 RC2

[EDIT] I meant GAPPs. Damnit.
Hello,
I'm at a loss for what's happening and how to fix it. My GoogleFU is failing and nothing I try seems to work.
Basically, WiFi does not work for me in CM 10.1 RC2 and it's something to do with the GAAPs. Everything is initially fine on a fresh install [edit: I don't know if it matters, but when I flash the latest milestone of AOKP WiFi never works. At the initial set up it connects but fails to authenticate over and over] and it's all going swimmingly at first. When I open the Playstore in these first few moments, it's the last version. Eventually the Playstore updates itself and that's when WiFi stops working. Nothing can connect to anything. In the Playstore I just get a 'failed to connect' message and a 'retry' button that doesn't work. The browser doesn't pull anything up and I can't get any sort of connection until I turn WiFi off and go to data.
I'm really at a loss. If it helps, I'm on the Sasktel version, but it's still the I747 [i747m in the stock ROM] which is the same as Bell/AT&T, right? So that shouldn't matter. I'm flashing the 20130301 GAAPs and even tried the 4.1.2 ones (they didn't work at all). I'm using CWMR 6.0.1.2. I can't figure out what I'm doing wrong. Any advice at all would be greatly appreciated. I don't know why I'm having so much trouble with ROMs on my S3 when it was so much easier to root than my old One V (which is still running CM 10 like a champ with 0 errors - I gave that phone to my sister).
Sorry for the long post, but this has been melting my brain.

so what all are you wiping before these flashes? i would recommend data, cache, dalvik, format /system, format /data when changing ROMs and especially when changing android versions (4.1 to 4.2, etc). If you have a micro sd card, place your ROM, gapps and a backup on there and go through the above wipe procedures.
you should also consider updating your recovery. 6.0.3.1 is the latest. you can flash this in recovery, go to Advanced and reboot recovery for this to take effect.