Database Info

WIFI Calling routing to speaker

This issue, that while using WIFI calling my audio during calls is routed to the external speaker, rather than the earpiece, has plagued my phone for weeks.
It seems to have started on the first BALI kernel, though as per Honk, it shouldn't be his kernel causing the issue. Though some are not reliant on WIFI calling as I am, I know there are others plagued with this issue..
That being said I started this thread to see if we can figure out what the issue is and not clog up the Bali thread
here's some info I found on a CM7 forum albeit for a different device, ZTE Blade, though with a very similar issue with all VoIP calling being routed to speaker.
It seems they were having alot of trouble figuring it out as well, and i'm not sure I understand some of the fixes they were trying to implement. maybe it can help though..
http://code.google.com/p/cyanogenmod/issues/detail?id=2858

I guess I'm the only one w the issue.. back to the Bali thread lol
sent from my real Gs move in silence like lasagna

You're not the only one with the issue...just the only one that it's really bothering. I don't use wifi calling being in NYC so the coverage is fine.
But I described that issue in the bali thread along with others, and also noted some issues possibly related to it.... voice dialing doesn't work, bluetooth voice commands don't work.
I'm using a stock deodexed Whitehawk KD1. The ONLY thing I flashed was Bali, and the issue has ALWAYS existed in each of the Bali kernels. It HAS to be Bali.

Yeah it is definitely the bali kernel it wasnt there before i flashed thus kernel i usw it sometime but it really not that important always 4g whereever i am going in my city
Sent from my SGH-T959V using XDA Premium App

I wouldnt blame the kernel, still running stock and have the same issue. I think it's the free wifi apk. I never experienced it before I called t mob and asked for the "upgrade". now on incoming calls I get speaker connection and on out going calls the recieving end always complains about echo.
On the moon our weekend are so advanced they encompass the entire week

I've been having the same problem for the past few weeks. For me, it started when I switched from the stock rom to teamwhiskey's rom. Its very annoying.

Yeah the echo is a problem too but I attributed it to Bali as well.. when the phone was stock there was always a low volume issue.. maybe tmobile will upgrade the app
sent from my real Gs move in silence like lasagna

i tried it on a stock rom umm it does the same thing its not the rom its the app

No one said it was a rom.. its the kernel
sent from my real Gs move in silence like lasagna

Stock rom with stock kernel does same thing
Sent from my SGH-i9100 using XDA Premium App

RaverX3X said:
Stock rom with stock kernel does same thing
Sent from my SGH-i9100 using XDA Premium App
Click to expand...
Click to collapse
Its the kernel. Wifi calling works fine with stock kernel. this is a known issue with Bali kernels.

I'm running bali 3.1 uv never knew it was a issue... I actually didn't try it until I seen that it was a issue for some.
Sent from my SGH-T959V using XDA Premium App

I have the same issue....
Project-V w/ Bullet 1.42 v2.2

T-mobile SGS4G running Bali 3.3 kernel with no custom ROM.
When I flashed this kernel I also wiped dalvik, data, etc. for a nice clean flash. At first calls routed to the speaker phone, but after letting the phone sit and rebuild for 20 minutes or so, the problem went away.

(smint) said:
T-mobile SGS4G running Bali 3.3 kernel with no custom ROM.
When I flashed this kernel I also wiped dalvik, data, etc. for a nice clean flash. At first calls routed to the speaker phone, but after letting the phone sit and rebuild for 20 minutes or so, the problem went away.
Click to expand...
Click to collapse
Do you have the echo issue?

The echo issue is horrible.. all people do is complain that they can't hear a thing but their voices. Its hard when its an important phonecall
Shermer321 said:
Do you have the echo issue?
Click to expand...
Click to collapse
sent from my real Gs move in silence like lasagna

I can confirm this as well... routing to speaker on occasion and echoing
I live quite a ways out of town and so wifi calling is the only option for me. My service out here without wifi is absolute ****. Given that I work from home and I'm always on conference calls, this is a real problem. I flashed the 3.3 Bali today and can confirm that it's still happening. Are there any updates to this at all?

I think were SOL at this point.. hopefully when GB comes out with a new custom kernel it'll work properly
sent from my real Gs move in silence like lasagna

RaverX3X said:
Stock rom with stock kernel does same thing
Sent from my SGH-i9100 using XDA Premium App
Click to expand...
Click to collapse
Stock ROM, stock kernel does *not* do the same thing. I've flashed stock to bali to stock to bali to stock again, and *EVERY* time I flash Bali, the problem starts. EVERY time I replace bali with the stock kernel, the problem goes away. I get nearly no signal in my room, and I rely heavily on wifi calling. Without a fix for this problem, the bali kernel is basically useless to me. Whenever I turn on wifi, all my calls route through the speaker and the other end complains about a terrible echo.
This is clearly an issue between the kernel and the wifi calling app, and since the stock kernel works fine whereas the bali kernel doesn't, my thinking is someone should setup some kind of data gathering layer BETWEEN the kernel and the wifi calling app to figure out how/why the two kernels are handling the wifi calling app differently.
Either way, this is not happening on the stock-from-t-mobile rom+kernel.

If you are not getting a signal from your room, try switching modems.I never got signal in my apartment and I flashed to kf1 and I started getting full bars and 4g. The stock wifi app seems to be giving a lot of users problems. I'll look into an alternative app
Sent from my SGH-T959V using XDA Premium App

G2X Discussion Thread (CM Nightly issues, ICS updates, etc.)

Well everyone, since my KANG thread in the development section has become a discussion thread since official CM nightlies started again, I've decided to redirect the discussion to here. I'm going to ask the thread in the development section to be closed, so it can stop taking up space there...instead we'll take up space here! Lol. But anyways I want this to basically be a continuation of the old thread...you can talk about your G2X questions, comments, problems, etc. here. This will be especially geared toward CM-related problems, but all G2X-related topics are welcome here I hope that everyone will continue to help each other out, and of course I'll monitor the thread to help as much as I can and research things if necessary. Enjoy!

This isn't necessarily CM-related but I guess it is in a way. I have been trying out EB's build 1 of ICS and honestly for the most part it works great already. The only big glaring issue (that actually made me revert back to Gingerbread today) was the incoming call problem I've seen reported elsewhere that when you try to answer a call, your ringtone restarts and it doesn't appear to actually pick up.
As for the G2X in general, I'm a firm believer that most common issues have been strictly software-based, which makes the resources we have here on XDA something like miracle workers if you think about it.

Kalm_Traveler said:
This isn't necessarily CM-related but I guess it is in a way. I have been trying out EB's build 1 of ICS and honestly for the most part it works great already. The only big glaring issue (that actually made me revert back to Gingerbread today) was the incoming call problem I've seen reported elsewhere that when you try to answer a call, your ringtone restarts and it doesn't appear to actually pick up.
As for the G2X in general, I'm a firm believer that most common issues have been strictly software-based, which makes the resources we have here on XDA something like miracle workers if you think about it.
Click to expand...
Click to collapse
Ya I couldn't stand that answer my phone wait for it to ring after I select answer was surely a big annoying thing that and wifi calling issues but other then that VERY usable can't wait for newer builds and development on 4.0.3..
I'm on his GB CM7 build and love it great great battery life only at 90% with descent use today.
Sent from my LG-P999 using xda premium

Quick question, if I am already running Arcee's ICS ROM would I need to do a full wipe and loose the way I have my phone configured or can I just wipe cache/dalvik cache and flash on top of Arcee's??

j.d.r said:
Quick question, if I am already running Arcee's ICS ROM would I need to do a full wipe and loose the way I have my phone configured or can I just wipe cache/dalvik cache and flash on top of Arcee's??
Click to expand...
Click to collapse
As it is always said, it is best to do a full wipe. You never know what issues may stick behind or get caused by not doing a full wipe, but give it a shot and report back and hopefully you don't have issues.
Sent from my LG-P999 using xda premium

Ok, so after reading the last comments in the CM thread, arcees rom is not been updated in awhile. What have people found the most stable, working ics ROM is atm? I'm using sk3, but will upgrade if there is better.
(btw, People get jealous of my now ICS powered phone )
Thanks!
Sent from my LG-P999 using Tapatalk

I believe Hellfire sandwich is the most updated and closest to everything working build. But there's lots coming down the pipeline thanks to our AMAZING DEVS!!!
Sent from my LG-P999 using xda premium

What's the best source for finding out the status of official Cyanogen 9 work on the G2X? I am not interested in kangs or spin-offs.

joeyxl said:
Ok, so after reading the last comments in the CM thread, arcees rom is not been updated in awhile. What have people found the most stable, working ics ROM is atm? I'm using sk3, but will upgrade if there is better.
(btw, People get jealous of my now ICS powered phone )
Thanks!
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
I haven't tried any of the other ICS roms, but been using HFS since the initial release. Obviously it's not perfect, but I've been running it everyday and don't have any major complaints

CM Nightly 226/Unnamed & Kernels
Recently transitioned back to CM from MIUI. Anyone try out the newest 226 (unnamed) Nightly yet? I'm still rocking the CM7.1.0.1 Stable, but for kernel flashing purposes, I'm trying to decide on a nightly.
I've used Faux123's UV/OC kernels, but seem to have lost my copy of his v0.4.3 (long term CM7.1.0.1 support). So, the newest v0.4.8 and T15 or ELF Trinity's won't work with mine. I know chip's vary, but mine seems to not like even the ELF Trinity kernel (which has worked for a few peeps running CM7.1.0.1).
Anyway, the breakdown of my ramblings are:
1. Anyone try CM Nightly 226/Unnamed?
2. Anyone happen to have a copy of Faux123's v0.4.3 kernel (CM Battery Version, not the DS driver) lying around? Or a compatible Trinity (preferred, actually)?
Eh, I know #2 is more wishful thinking. I'm mostly interested in anyone's experience with Nightly 226/Unnamed.
Ah, good to be back on XDA and CM, at that. I rolled on MIUI for way too long. Nice GUI & the customization was awesome, but man is that sucker a memory hog! Not to mention the random reboots and screen freezes... I should have never left my good ol' CM. Hindsight and all...

The only issue that I ran into with cm7/cm9 is the low microphone. I know this has been brought up in the past, but has been ignored as well. Some users claimed that it only happen to certain phone, but I'm almost certain that the issue lies within the rom. I do hope someone can shed some lights on this, cause i do miss using CM7.

long story short, i have a wiped g2x. power button is a ***** to turn on to the point that my finger tips are sore from trying to get it to boot into recovery since last night. i can only seem to get 2 different screens trying to do this:
a) the lg boot animation which promtly freezes as the phone has been wiped & i probably haven't held the volume down button
b) the s/w screen used for flashing a recovery, etc
the phone is not mine but trying to help someone out. is there a timing to releasing the buttons? seems that when it goes to the s/w screen, lg appears for only about a second and then straight to that one. any help would be appreciated.
edit: posted it here only because i'd been following the old thread which led me to this one. i was trying to update to the latest while this happened. i started a similar thread in q&a so if it doesn't belong i''ll remove it, thanks

I've been in a loop like this before. Make sure you have done a battery pull. I think the key is not to hold the volume down button so long, and then be patient for recovery to load, it takes longer than expected in this situation.
Good luck.

Nightly #225
my_former_self said:
Recently transitioned back to CM from MIUI. Anyone try out the newest 226 (unnamed) Nightly yet? I'm still rocking the CM7.1.0.1 Stable, but for kernel flashing purposes, I'm trying to decide on a nightly.
Click to expand...
Click to collapse
Ah, you want to talk to me! I just went from CM7.1.0.1 Stable to #225. More stable, much faster than CM7 Stable, #225 really should be CM7.2 Stable.
#226 seems to have a bug with the lockscreen PIN. Go get #225 and don't look back.

azyan said:
The only issue that I ran into with cm7/cm9 is the low microphone. I know this has been brought up in the past, but has been ignored as well. Some users claimed that it only happen to certain phone, but I'm almost certain that the issue lies within the rom. I do hope someone can shed some lights on this, cause i do miss using CM7.
Click to expand...
Click to collapse
I've seen in other threads that the app getril fixes the low mic problem. This app matches the radio layer to the baseband.

dmwOtis said:
I've seen in other threads that the app getril fixes the low mic problem. This app matches the radio layer to the baseband.
Click to expand...
Click to collapse
Lots have stated the same thing doesn't work for most some say it did. Worth a try if you haven't yet, no go for me
Sent from my LG-P999 using xda premium

Where is this getril app?
Sent from my LG-P999 using XDA

azyan said:
The only issue that I ran into with cm7/cm9 is the low microphone. I know this has been brought up in the past, but has been ignored as well. Some users claimed that it only happen to certain phone, but I'm almost certain that the issue lies within the rom. I do hope someone can shed some lights on this, cause i do miss using CM7.
Click to expand...
Click to collapse
I agree, this is by far the most annoying bug and the only "show stopper" I can think of on CM7. I do not think it's a 'phone-by-phone' thing, because if I flash to stock or Weapon G2X, my mic volume is fine. It's only on CM/CM-based ROMs, such as MIUI. I can't count the number of times where people have told me to "speak up" until I'm practically yelling into my phone. I think there's a bug with noise cancellation that causes it to be quieter than it should be.

Learn somethg new everyday just downloaded it... I had v21c when it expected v21e any idea why i didn't have the latest?
Sent from my LG-P999 using XDA

imoumni said:
Learn somethg new everyday just downloaded it... I had v21c when it expected v21e any idea why i didn't have the latest?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
GetRIL went the other way for my phone (Wind Canada P999), recommending v11h. Any notes re: the different builds?

Verizon CM10 Nightlies

Installed the most recent nightly Jellybean for Verizon. Seems stable but I notice what seems to be degraded sound quality on phone calls. Anyone else having that issue?
Can someone more experienced recommend a better (or preferred build)?
Thanks,

Stormer1981 said:
Installed the most recent nightly Jellybean for Verizon. Seems stable but I notice what seems to be degraded sound quality on phone calls. Anyone else having that issue?
Can someone more experienced recommend a better (or preferred build)?
Thanks,
Click to expand...
Click to collapse
You can't expect nightly builds to be stable- they will and do have issues with various things.
The vast majority, if not every single AOSP ROM for the SGS3 uses all of (or a good chunk) of CyanogenMod's code, which is why you see so many of the same bugs between builds that are rarely fixed until someone submits to CyanogenMod's Gerrit.
I can't comment on your specific issue, just posting some food for thought.

A lot of people have posted about echoes or low volume on the CM10 builds. I don't make many phone calls so I don't know if this affects every phone running CM10. But I'm sure it does to various extents. They will work it out in the coming weeks as they work toward a stable build.
Sent from my SCH-I535 using Tapatalk 2

the echo seems to be gone in the 8/31 build
use this thread to ask questions about it
http://forum.xda-developers.com/showthread.php?t=1840414&page=140

Preferred Build
Is there a stable build other than the nightlies? If so where would I find it?

Stormer1981 said:
Is there a stable build other than the nightlies? If so where would I find it?
Click to expand...
Click to collapse
I'd check the development forum or the nightly thread.
Sent from my Galaxy S III

ripken204 said:
the echo seems to be gone in the 8/31 build
use this thread to ask questions about it
http://forum.xda-developers.com/showthread.php?t=1840414&page=140
Click to expand...
Click to collapse
Agreed
Sent from my SCH-I535 using Tapatalk 2

No echo here. I just flashed to the 9/1/2012 nightly from stock.
Did you try playing with the call settings? I have noise suppression enabled and voice privacy disabled.

I actually have a similar problem (can't post on official thread yet).
I have trouble with my headset volume.
If i plug it in DURING a call, I cant hear anything and can't do anything to adjust the volume.
If i plug it in BEFORE a call, it's fine.
Any clues as to whats going on or any suggestions on how to fix it?

Paranoid android Sept 2nd build seems to work nice, i think it works better than the CM10 builds even though its based off it. You can also mess around with tablet mode!

Let's get the echo fixed and the roaming issue fixed and the forum will flock to these roms. Till then I would beware.
Sent from my SCH-I535 using xda premium

I just flashed CM10 09/04 nightly and I am still getting the 3 second In call delay, I am still getting echo on speaker phone and I am still getting my voice navigation only say " in a half mile" Nothing else, No one seems to even mention this in the official CM10 forms. and No its not a half mile from my house to the end of my street , its like less than 1000 ft. Everything else seems to work good but the delay and the echo are very annoying so I am going back to the build that worked best for me cm10 08/22

Defragger51 said:
I just flashed CM10 09/04 nightly and I am still getting the 3 second In call delay, I am still getting echo on speaker phone and I am still getting my voice navigation only say " in a half mile" Nothing else, No one seems to even mention this in the official CM10 forms. and No its not a half mile from my house to the end of my street , its like less than 1000 ft. Everything else seems to work good but the delay and the echo are very annoying so I am going back to the build that worked best for me cm10 08/22
Click to expand...
Click to collapse
Same results here for 904. The other forum mentions that an unofficial build has the incoming call delay fixed, though, so I'm hoping the fix shows up when the official 905 ROM comes out.

Headphones with mic not working
I'm running the 9/2 build and when I plug the stock headphones with mic into the phone I cannot talk or hear phone calls through it. No issue with music. Screen flickers when using keyboard (Swiftkey). Volume control in call doesn't seem to work. There is also a 5 second delay when I answer a call to when I can hear the other person or they can hear me. Same delay with speaker phone.
At least the damn echo is gone though :good:

Can anyone confirm whether or not the dock audio is working on recent CM10 builds? I've tried searching the thread and have done everything short of just flashing it to see.
Thanks for your replies!

The dock audio was still not working for me on the CM10 from 9/5.

landtuna said:
The dock audio was still not working for me on the CM10 from 9/5.
Click to expand...
Click to collapse
You are correct. Just tried it myself. This is the main thing holding me back from CM10. I'm going to attempt to add it in myself. We'll see what happens.

9/5 build seems to be very solid. No data issues or call issues. Cannot comment o no the dock audio though. Make sure you aren't doing dirty flashes, there have been tons of issues with dirty flashing.
Sent from my SCH-I535 using xda app-developers app

This is why I switched to ParanoidAndroid. It is Jellybean and far more stable than the current CM10. If you want Jellybean right now~ I highly recommend PA. If you really like CM, still, try PA~ it will help you wait for the official CM10 release. I actually don't see a need to go CM10 tbh. PA is wonderful.

Krystalmyth said:
This is why I switched to ParanoidAndroid. It is Jellybean and far more stable than the current CM10. If you want Jellybean right now~ I highly recommend PA. If you really like CM, still, try PA~ it will help you wait for the official CM10 release. I actually don't see a need to go CM10 tbh. PA is wonderful.
Click to expand...
Click to collapse
I'm going to give PA a try... I am still having serious issues with CM10, hope they will be fixed with PA

Phone Dials but no Sound

I have an occasional issue where my phone is dialing a number but I cannot hear the ringing, and once it connects there is no sound either way.
Sometimes if I reboot the phone will work again - but other times I need to reboot several times before it seems to start working again.
Obviously this is a huge problem as I use this phone for business...any suggestions on how I can diagnose this?

lirong said:
I have an occasional issue where my phone is dialing a number but I cannot hear the ringing, and once it connects there is no sound either way.
Sometimes if I reboot the phone will work again - but other times I need to reboot several times before it seems to start working again.
Obviously this is a huge problem as I use this phone for business...any suggestions on how I can diagnose this?
Click to expand...
Click to collapse
Which version of which build are you using? There was a well-documented (and very annoying) bug in CM for a while that affected in-call audio. This has been addressed in more recent builds and seems to have been eliminated. A little more information will make it easier to help you.

mrfeuss said:
Which version of which build are you using? There was a well-documented (and very annoying) bug in CM for a while that affected in-call audio. This has been addressed in more recent builds and seems to have been eliminated. A little more information will make it easier to help you.
Click to expand...
Click to collapse
Thanks...sorry for that ommission.
I am using vincom's Superlite CM10.

lirong said:
Thanks...sorry for that ommission.
I am using vincom's Superlite CM10.
Click to expand...
Click to collapse
I've had this problem with all kinds of roms (stock, custom, aosp, etc). Sometimes it happened more often sometimes less. I've even had this happen to me on three different phones (SE x8, i9100 and i727r). Most often it happens with CM7, CM9 and CM10. But it did and does also happen with official roms. I'm on the Rogers JB now and it still happens, but relatively rare. This has been discussed before and with no result. Apparantly this is a common android issue..
Same issue talked about here:
http://forum.xda-developers.com/showthread.php?t=2164921
http://forum.xda-developers.com/showthread.php?t=2168656

I had such problem too and hadn't found the reason.
Anyway, after I flashed UXUMA7 radio, I haven't experienced it any more.

I just had this issue today. I've been running cm 10.1 m snapshot since Friday using the phone no problems. Last hour of work my wife calls no audio during call. I then wiped the cache partition and devik cache nothing. Came home did a full wipe and now its fine. I don't know don't know what happened. I think I may find a different ROM if this happens again
Sent from my Nexus 7 using xda app-developers app

livefree79 said:
I just had this issue today. I've been running cm 10.1 m snapshot since Friday using the phone no problems. Last hour of work my wife calls no audio during call. I then wiped the cache partition and devik cache nothing. Came home did a full wipe and now its fine. I don't know don't know what happened. I think I may find a different ROM if this happens again
Click to expand...
Click to collapse
The last m release that I know of (I haven't been on straight CM for a few weeks) was released before a commit that fixed the no in-call audio bug. I'd read through the thread and look to see which nightly has been the most stable, if I were you. If you do decide to switch to another ROM I can personally vouch for Sons of Android or Slim Bean (onlychevys has an unofficial build out).

I have since switched to Embryo and, so far (hope I didnt just jinx myself) I have not experienced this issue.

lirong said:
I have since switched to Embryo and, so far (hope I didnt just jinx myself) I have not experienced this issue.
Click to expand...
Click to collapse
Embryo is tw, doesn't have the issue
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

[Q] PA 3.60 Phone Calls Not Working

I downloaded the new PA 3.60 6/11 build from notta yesterday with KT747 Kernel and RErick universal setup. After using for a while, without attempting to call, I was more than happy. At work today I called my girlfriend and in the middle of our conversation the call dropped. Ever since then whenever I try to make a call I get a "com.android.phone has stopped" message or it will connect, close phone screen but keep call in status bar, show that same message, then drop the call. Sometimes it says "Mobile network not found" after trying to call then will reload my bars after. Can't receive calls either but my network shows I have bars and every IMEI & numbers alike are there. Restored nandroid and calls worked.
Thought it might be kernel combo so tried to wipe everything and reinstall but problem persisted. Any ideas on how to fix?
Thanks in advance!

Try the latest paranoid android gapps, i had that problem a few times but after i flashed those the problem stopped. And what's Rerick setup?
Sent from my SCH-I535 using xda premium

andrewk7750 said:
Try the latest paranoid android gapps, i had that problem a few times but after i flashed those the problem stopped. And what's Rerick setup?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I've flashed the 6/10 gapps both times I flashed the ROM, unfortunately. Maybe bad download? I don't know at this point.
Its RErick's from Team Kernelizers setup for the KT747 kernel. Can find him on the TK Mod thread. Great battery life supposedly but didn't get to try it for too long since calls didn't work.

I was running the latest pa with their gapps and calling was fine for about a day then I got the phone crashing every time I tried to make a call and couldn't receive any.
Did nothing different. I didn't try to fix it or anything, I just restored my tw backup.
Unfortunately, I've been running tw mostly these past few months. Occasionally I try out aosp, be it cm or another iteration, but go back due to the annoying deal breaking glitches. I've pretty much given up on running anything other than bone stock on this phone. Not sure if it's just my phone or what, but anything else always has obnoxious bugs that never seem to get squashed.
Shame, too. The developers do great work. Probably just my particular phone as plenty of others seem to run with zero problems.
Stock bloated tw with nova for me. Even the debloated roms run wonky on my phone after a couple days. Always full, clean wipe.

antiseen said:
I was running the latest pa with their gapps and calling was fine for about a day then I got the phone crashing every time I tried to make a call and couldn't receive any.
Did nothing different. I didn't try to fix it or anything, I just restored my tw backup.
Unfortunately, I've been running tw mostly these past few months. Occasionally I try out aosp, be it cm or another iteration, but go back due to the annoying deal breaking glitches. I've pretty much given up on running anything other than bone stock on this phone. Not sure if it's just my phone or what, but anything else always has obnoxious bugs that never seem to get squashed.
Shame, too. The developers do great work. Probably just my particular phone as plenty of others seem to run with zero problems.
Stock bloated tw with nova for me. Even the debloated roms run wonky on my phone after a couple days. Always full, clean wipe.
Click to expand...
Click to collapse
The same things HaS been happening to me with alot of asop ROMs. Only way to fix is not use custom kernel and the roam setting have something to do with it. It sucks cause I like the asop ROMs . Its been doing to me for two weeks just wonder if they have changed anything with these ROMs cause it don't matter if its cm PA AOKP or unofficial versions of these I just can run them anymore
Sent from my SCH-I535 using xda app-developers app

kenbrownstone said:
The same things HaS been happening to me with alot of asop ROMs. Only way to fix is not use custom kernel and the roam setting have something to do with it. It sucks cause I like the asop ROMs . Its been doing to me for two weeks just wonder if they have changed anything with these ROMs cause it don't matter if its cm PA AOKP or unofficial versions of these I just can run them anymore
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Since I've been having so much trouble with any rom I haven't used a custom kernel since my thunderbolt days. I run whatever kernel the rom comes packaged with.
But like I said, it's probably my phone. It has defective bluetooth that I didn't figure out until well after I purchased the phone. It's got constant loud crackling and popping on stock (ironically, non existent on aosp roms). I doubt that's related but just illustrates the weird differences between phones.

Had the same problem less than an hour ago when i really needed to make a phonecall. Had to restore to my backup i made before flashing PA. Hell of a time for it to stop working.
Sent from my SCH-I535 using xda app-developers app

Well after first believing it was just my phone, after reading these comments as well as the PA thread I've come to the assumption that its something with the ROM and how it behaves with the phone app. Hopefully the details will get resolved soon cause I was really enjoying the new PA. Until then, sticking with hyperdrive.
Thanks guys.

had this problem since upgrading to the 6/11 build.
i could make calls out as long as i didnt press the ok button to dismiss the process stopped message.
i could not receive calls hwoever. it does ring like it should, but it does not allow me to answer.
using latest gapps package.

I've had this problem on both 6/12 and 6/14, using the 6/10 gapps.
Any chance anyone has come up with some way to resolve this?

for ppl with this problem, i moved to pacman to get all my newest PA features setup with pie, expanded desktop and halo.
not having htis problem on there.

ddurandSGS3 said:
for ppl with this problem, i moved to pacman to get all my newest PA features setup with pie, expanded desktop and halo.
not having htis problem on there.
Click to expand...
Click to collapse
Good suggestion. Really liked PACman for a while, but eventually my call got dropped and I ran into the exact same issue from that point on. At this point I've just decided to go with a TW based rom. With hyperdrive you can still have pie and download Floating Notifications app that is practically the same thing as halo but also has themes available too.
Until that bug can be fixed, going to stick with Hyperdrive. Sweet rom anyway.