Originally Posted by dizzy21

Is anyone else having issues with wifi calling dropping out and causing force closes? Is there a fix? This is the only ics rom that I can actually turn it on with.... Lol

Sent from my LG-P999 using XDA

so your getting fc on the wifi calling app? or which app? and no I dont use wifi calling any more, but when I did it was working last I tried it... I cant test it for you now as im on hfp beta... sorry

Originally Posted by da-pharoah

so your getting fc on the wifi calling app? or which app? and no I dont use wifi calling any more, but when I did it was working last I tried it... I cant test it for you now as im on hfp beta... sorry

I get the com.android.phone error when it becomes active. phone becomes pretty much useless until i turn off the wifi-calling.


Thanks for testing it on new build...

Originally Posted by netsecdude

Yeah, I've been getting the same thing. If I connect to wifi, I'm fine. If I'm away from that wifi spot, data doesn't pick up and I have to restart the phone. Noticed to that text messages work fine on wifi, but picture messages don't. I have to me connected to t-mobile data to send a picture. It's weird. GetRIL doesn't fix this issue

Added note: I'm not using wifi calling..

Originally Posted by netsecdude

Added note: I'm not using wifi calling..

dang data issues with CM9.. Its above my pay grade to fix.. maybe one day ill learn to build android like Hell... maybe... I got lots of things going on right now and I dont have time to learn to build.

Originally Posted by dizzy21

I get the com.android.phone error when it becomes active. phone becomes pretty much useless until i turn off the wifi-calling.


Thanks for testing it on new build...

I am getting this as well, can't use a rom without wifi calling :(

Sent from my LG-P999 using Tapatalk 2

kinda weird but now the only time i get data drops is when i have GPS turned on. works perfect until i turn on GPS, then the data drops begin...

Originally Posted by Milton515

I'm having a issue with my Gmail force closing... I have fixed the permissions thru Rom Manager and thru recovery mode that didn't fix it.. I also have updated the ril... I am running the dirty version of 1.7 and the issue started Saturday... If anyone has a fix or is having the same issue please let me know... Thanks in advance

Sent from my Hell Bound Thumbs

I had a somewhat similar issue with my gapps where they were working and then randomly started getting screwed up. My question for you is this: after you re-flashed the ROM, did you do a "Restore apps with system data" or just an app restore?

I found that I had reinstalled the probem by restoring the system data, but when I did a fresh install of apps without data, my problems were solved. You may want to do another flash (make sure to use the scrubber in the OP) and then slowly restore your apps in batches (say 5 at a time) in order to focus your search for what might be causing your FC issues. I did it this way and found that I had a couple of apps that were causing problems so I just deleted them and then re-installed them from the market sans additional problems so far.

Give that a try and let us know what happens.

---------- Post added at 01:59 PM ---------- Previous post was at 01:17 PM ----------

On another note...

I've noticed that when I use my power button to reboot into recovery, it always reverts back to an older version of clockworkmod, but if I use the reboot utility inside of ROManager it goes to the newer one just fine.

Any thoughts on why this might be, as well as how I can remove the old recovery image to permanently replace it with the new one?

Sounds like you need to update your recovery with nvflash. Flashing through rom manager is a kind of fake flash, which is why it does the two versions depending on how you get into recovery.

Tapatalked from my A100 - Flex Reaper RF1.

Originally Posted by samstheman42

[/COLOR] On another note...

I've noticed that when I use my power button to reboot into recovery, it always reverts back to an older version of clockworkmod, but if I use the reboot utility inside of ROManager it goes to the newer one just fine.

Any thoughts on why this might be, as well as how I can remove the old recovery image to permanently replace it with the new one?

i used this thread to flash the touch recovery (5.8.1.3) over the older one (5.0.2.0) and have never had an issue

Originally Posted by pio_masaki

Sounds like you need to update your recovery with nvflash. Flashing through rom manager is a kind of fake flash, which is why it does the two versions depending on how you get into recovery.

Tapatalked from my A100 - Flex Reaper RF1.

+1 to this. and if your going to nvflash it I would recommend to use the G2X Cleanup Batch but it comes with a WARNING ** WILL FORMAT INTERNAL SD so be prepared for that... but its a great tool!