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
Related
Im using drhonks KG4 2.3.4 on my SGS4G and for some reason the tmobile wifi calling app volume is very low. Meaning, I cannot hear the other person, although they can hear me very well. Anyone else have this issue? I searched around xda but couldnt come up with anything conclusive.
I know that there were some that experienced issues with the Bali kernels wifi calling.
Sent from my SGH-T959V using xda premium
WTF, why do all "noobs" use kg4. Kg4 is very old. Use KH2. it gets rid of such issues.
airfluip1 said:
WTF, why do all "noobs" use kg4. Kg4 is very old. Use KH2. it gets rid of such issues.
Click to expand...
Click to collapse
Thanks but no thanks. KG4 is very stable and works best. I tried KH2 and KG6 as well among a myriad of others Including Bali which bricks my phone. KG4 provides the most stability and best benchmarks for me.
I dont know how using a stable kernel for my device makes me a noob but to each his own.
Also since you are going to call people noobs for using Kg4, you should change your sig file. It still says you use KG4. I wouldn't want you to be associated with the plebs.
EDIT: KH2 does not fix this problem. thought you should be aware of that as well.
lordxavier said:
Thanks but no thanks. KG4 is very stable and works best. I tried KH2 and KG6 as well among a myriad of others Including Bali which bricks my phone. KG4 provides the most stability and best benchmarks for me.
I dont know how using a stable kernel for my device makes me a noob but to each his own.
Also since you are going to call people noobs for using Kg4, you should change your sig file. It still says you use KG4. I wouldn't want you to be associated with the plebs.
Click to expand...
Click to collapse
Benchmarks should be about the same for all of them. For some reason, Samsung Adrenaline Shot v6 isn't giving us the proper scores for Quadrant on the KH2 kernel. The smoothness of the phone and the tests run Quadrant are very similar to the KG4 kernel. AnTuTu gives a similar, if not, better score.
Bali kernel would obviously soft-brick your phone. It's a kernel meant for Froyo, not GB.
As for your WiFi volume, that's normal on all GB ROMs. There has been no fix for that yet.
Honestly, using any build on this phone is fine, except for KF1 and KF2. You would be crazy to use those, lol.
bkoon1218 said:
Benchmarks should be about the same for all of them. For some reason, Samsung Adrenaline Shot v6 isn't giving us the proper scores for Quadrant on the KH2 kernel. The smoothness of the phone and the tests run Quadrant are very similar to the KG4 kernel. AnTuTu gives a similar, if not, better score.
Bali kernel would obviously soft-brick your phone. It's a kernel meant for Froyo, not GB.
As for your WiFi volume, that's normal on all GB ROMs. There has been no fix for that yet.
Honestly, using any build on this phone is fine, except for KF1 and KF2. You would be crazy to use those, lol.
Click to expand...
Click to collapse
Thanks. I didn't know there wasn't a fix. Yea I wouldn't downgrade that far. KH2 works fine, I just wasn't getting the scores I wanted to see and it was crashing in some odd places that I cant really put my finger on yet.
lordxavier said:
Thanks but no thanks. KG4 is very stable and works best. I tried KH2 and KG6 as well among a myriad of others Including Bali which bricks my phone. KG4 provides the most stability and best benchmarks for me.
I dont know how using a stable kernel for my device makes me a noob but to each his own.
Also since you are going to call people noobs for using Kg4, you should change your sig file. It still says you use KG4. I wouldn't want you to be associated with the plebs.
EDIT: KH2 does not fix this problem. thought you should be aware of that as well.
Click to expand...
Click to collapse
BTW, it says I use the kg4 kernel. The hacked voodoo one. NOT KG4. I use audiophile.
Considering that we all have the exact same phone, I find it *very* hard to believe you're getting better performance and stability out of KG4 than KH2. I just made the move to KH2, and I've noticed several subtle yet substantial improvements over KG4 -- including wifi calling volume. The *ONLY* instance where I have a problem with wifi calling is in a situation that will never arise for me in real life:
When wifi calling is on *and* you're paired to a BlueTooth headset or handsfree kit, the other party hears an echo of their own voice *when you call them*. Incoming calls don't suffer from this affliction, and calls in both directions are just fine if you're not paired to a BT audio device.
I guess it's also worth mentioning that I avoid "deodexed" roms/releases like the plague, and the KH2 I'm running is the raw leak that krylon360 got his hands on. I really don't know if that could or would make a difference in the wifi calling issue, but I know for certain that I've run into less problems and quirks on odexed roms and releases than I have on deodexed ones (not to mention there are GOOD reasons for odexing (that far outweigh the primary reason for deodexing, which is themes), but that's not for this thread).
As far as the condescending attitudes of some of the people here, I say just shrug it off. When someone's a **** to you, take a few minutes to look through their posts and topics, and often, you'll find they're a condescending **** to most people, not just you. I usually only read 4 or 5 words into airfluip1's posts, and often, that's 3 or 4 words too far.
Oh, and airfluip1: Why do 'noobs' insist on running kg4 kernels on their kh2 roms when drhonk released a kh2 kernel for it?
P.S. -- If you can recover from it, it's *not* bricked. Flashing a froyo kernel over a gb rom will definitely send you into a bootloop, but that's not a brick. A brick implies just that: your phone is now dead and useless, you may as well slap some mortar on it and use it to fill a hole somewhere in your house.
hello all,
i am also having the same odd issue on kh2 n im using audiophile ftw, i tried valhalla and it seemed to work fine... after messing around quite a while with kh2 i havent been able to find the issue, if anyone can point us in a proper direction id apreciate it
It just a 2.3.3 and up issue Im guessing their should be a fixing about it when ever Tmobile realese a stable a non problem gb...
Sent from my SGH-T959V using xda premium
mex911 said:
It just a 2.3.3 and up issue Im guessing their should be a fixing about it when ever Tmobile realese a stable a non problem gb...
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
s/Samsung/Tmobile
Samsung develops the ROMs, they just build them to meet T-Mobile specifications.
Jay Aristide said:
s/Samsung/Tmobile
Samsung develops the ROMs, they just build them to meet T-Mobile specifications.
Click to expand...
Click to collapse
dang im slow lolz .....
Sent from my SGH-T959V using xda premium
seen it work on 2.3.4
mex911 said:
It just a 2.3.3 and up issue Im guessing their should be a fixing about it when ever Tmobile realese a stable a non problem gb...
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
actually ive flashed valhalla 1.0 and wifi calling works just fine on that.. i havent tried replacing wifi calling from another rom, if i hav any success ill post a follow-up here
Wifi calling works flawlessly on Valhalla its just that wifi sucks on gb lol
sent from my real Gs move in silence like lasagna
ok, so im running the latest version of ICBINB rom on froyo i believe. i dont trust myself with the steps for GB on the galaxy s 4g yet, but also running the bali 3.3 kernel, why oh why does sound from in call come through both the earpiece AND the goddam speakerphone!?!?!? this is wracking my brains! google is useless, and has provided me with very little in terms of assistance.
i have factory data reset, reflashed the rom, wiped, wiped again, wiped some more, still wiped, even odined to kd1 stock, reflashed ICBINB and i still get this demon....
anyone have any help to offer?
Unfortunately I do not but if you know how to flash and restore data like that then getting onto GB is a breeze and the benefits are amazing. ICBINB KI3 is amazing. I have never had any issues with the sound on GB but I did on froyo
That is one of the problems with the kernel, there its no fix unless you go to GB.
Sent from my SGH-T959V using XDA App
Are you using wifi calling? I think that's the only time that it is an issue. If so, you should be able to use titanium backup to freeze or uninstall wifi calling. I think that would fix the issue.
Sent from my SGH-T959V using XDA App
Yes I use WiFi calling a lot but it doesn't happen on stock Rom. I have had some hesitation about switching it to GB being I've seen some nasty rumors floating around about GB destroying sd cards.
Coming from the vibrant to the fascinate to the sgs4g ( I also have a HTC sensation) I'm used to flashing, and subsequently bricking and unbricking my devices, but when my 32 gb class 8 sdcard is at risk. I get apprehensive. Plus some of these roms say check mounts, but they don't list Wtf the mounts need to be in the thread for the Rom.
I'm getting a replacement sgs4g tomorrow, issues not related to flashing, so I will try a GB approach off a fresh device.
Thx guys, you may have saved my sanity. Especially since I don't see any other kernels for ext4 besides Bali. On group anyways.
Sent from my HTC Sensation XE with Beats Audio using XDA App
With red CWM you should not have to change the mounts. Some people do just to be safe. Almost all GB roms I have used have been UMMU.
I could definitely understand your concern about sd card. There are always risks that come with flashing. However in my personal experience it is well worth the risk
Wifi calls rerouting through the speaker phone is common on all of the Froyo ROMs. There was never a fix for it.
You don't really need to check mounts anymore, although it's good practice. Having the red CWM (thanks to krylon360), we don't need to check mounts.
In the event you don't use drhonk's Bali kernels or GB kernels, you would have to set them to UMMU 99% of the time. Not using them would be crazy though. ;P
on all froyo roms huh....that sucks lol i did notice when i odined back to kd1 stock i no longer had that issue. thats good to know about the mounts though. saves me a headache lol.
i use wifi calling at my home since the tmobile signal where i live is relatively crap ( talking G signal) so wifi really saves my bacon.
however at work and at my school i get 4g and done have the issue., instead i get ringtones just go off randomly during phone calls. and they dont stop until you end call.
vut again, after using odin to go kd1 again, no issues at all yet.
thx guys!!!
back to playing with my sensation!
Looking through the known issues on all of the Infuse ROMs, "1st call after boot has no sound" appears to be pretty common.
Are there any AT&T Gingerbread ROMs out there without this bug?
Well actually theres no need to do a first " no sound call" at the first call just turn speaker on anf off that solves the " no sound bug"... and theres NO AT&T gingerbread rom at ALL yet, we only have Rogers GB rom and AT&T leaks.
Anyways just turn speaker on and off on first call and simple as that the "bug" is gone...
Hope i helped you
There is actually no official gingerbread roms. yet. but toggling the speaker will fix it. it seems to be more of a android thing really. the HD2 has this issue too.
Thanks... My Infuse is due to show up via UPS on Monday. I'll see how long I can wait until I give up on AT&T releasing the official GB update (if I'm lucky I'll make it a month). Then, I'll decide which of these ROMs to go with.
Since I use A2DP a lot, looks like CM7 & MIUI probably wouldn't be the best choices for me.
koriotto said:
Well actually theres no need to do a first " no sound call" at the first call just turn speaker on anf off that solves the " no sound bug"... and theres NO AT&T gingerbread rom at ALL yet, we only have Rogers GB rom and AT&T leaks.
Anyways just turn speaker on and off on first call and simple as that the "bug" is gone...
Hope i helped you
Click to expand...
Click to collapse
Hey!! nice it works!! THANKS
Just use infused... no bugs...
Sent from my SAMSUNG-SGH-I997 using XDA App
Perpetrator said:
Just use infused... no bugs...
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
+1
1.6 for Froyo
2.2.3 for Gingerbread
Both work flawless!
Optimus-Prime said:
There is actually no official gingerbread roms. yet. but toggling the speaker will fix it. it seems to be more of a android thing really. the HD2 has this issue too.
Click to expand...
Click to collapse
Thought "no sound on first call" was a Hellraiser issue.
Optimus-Prime said:
There is actually no official gingerbread roms. yet. but toggling the speaker will fix it. it seems to be more of a android thing really. the HD2 has this issue too.
Click to expand...
Click to collapse
I'm guessing you came from the HD2 android ports? Hah. Anyways the Tilt 2 had that bug sometimes on the old XDAndroid builds with certain kernels but strangely it didn't have that problem on the GB port. Weird
Sent from my nice little phone... or should I say huge gigantic beast
Agrees with bigfau ....it is a hellraiser issue...only the Rome ported with hellraise have the no call after boot...tested
Sent from my SGH-I997 using xda premium
Do you have to hit speaker on the first call for every boot or just the once?
neon_skunk said:
Do you have to hit speaker on the first call for every boot or just the once?
Click to expand...
Click to collapse
Everything boot. Just happens on ports. Ie it won't happen on Zeus or NumasX. Just toggle the speaker and done.
Sent from my SAMSUNG-SGH-I997 using Tapatalk
It will happen on all Hellraised ROMs. Should not happen on any ROMs derived directly from an AT&T leak.
I thought this was common knowledge, and been discussed a million times. There is really a thread on this.?? Lol
Sent from my SAMSUNG-SGH-I997 using xda premium
To a developer I'm sure it's common knowledge. Back when I posted this, I didn't know a Hellraiser ROM from my own elbow. Heck, even now, it's not always entirely clear to someone like me which ROMs are based on Hellraiser. Depends on how detailed the dev wants to be in the OP of their release thread.
PharmNerd said:
To a developer I'm sure it's common knowledge. Back when I posted this, I didn't know a Hellraiser ROM from my own elbow. Heck, even now, it's not always entirely clear to someone like me which ROMs are based on Hellraiser. Depends on how detailed the dev wants to be in the OP of their release thread.
Click to expand...
Click to collapse
all PORTED ROMs from i9000 are possible through LinuxBozo's hellraiser kernel.
http://forum.xda-developers.com/showthread.php?p=16905319#post16905319
http://forum.xda-developers.com/showthread.php?t=1231286
infuse base roms are caty, zeus, numas, bionix etc
Recently I went to an AT&T customer service store to finally have my bricked skyrocket replaced. Everything was working great on stock gingerbread (they even gave it to me with the 2.3.6 update included), but when I went to flash an ICS rom, in this case CM9 alpha 5, I lost my in-call audio. Now, I know that this can be a bug with CM9, especially if you change the lcd density of the screen (which I did not do), so I decided upon trying a different AOSPish ICS rom, in this case AOKP build 40. Boom, all of a sudden I had my in-call audio back. Unfortunately, after about a week of running AOKP, my in-call audio died again. Here's the crazy part. I flashed back to gb stock w/ odin, and my in-call audio was STILL gone. In fact, all of my audio was gone on gingerbread. I've tested numerous roms, and they all seem to have the same result; Gingerbread gives me no audio whatsoever, ICS gives me audio, but no in-call audio. My first though was it was a hardware issue, but given that regular audio still works on ICS, as well as VOIP calls on skype, I'm not sure how it could be.
In any case, I'm just posting this here to warn people about this, or maybe see if anyone else has had a similar experience.
Bob saget.
Here's my post from the other day. Welcome to hell...
Guys, I have a huge problem. I installed DPI Modder Pro the other day and set to 160. Everything was cool until I realized I could not make a call after installing 7/1. I see the time increasing and the other person I'm calling is getting the call but I can't hear anything, sometimes though its just stuck on "dialing" yet the other person's phone is ringing. I luckily backed up right after installing the 6/30 nightly but I can only use the phone after the first boot from a restore. If I reboot, calls are gone again. Can't make them, can't get them. I flashed back to stock via Odin and was able to repeatedly reboot and have phone access with rogers 2.3.5 stock. I did a clean CM9 install and like usual, the first boot ran the call no problem but after a reboot, nothing. I don't know what else to try. I've fixed permissions, wiped with CWR, you name it. I'm stuck on 6/30 and I can't power down or reboot or I have to restore to get calls back.
Please help. PLEASE.
BaconStep said:
Bob saget.
Click to expand...
Click to collapse
Glad to see you contributing to the thread.
Sent from my SAMSUNG-SGH-I727R using xda premium
Did you darkside?
Sent from my SAMSUNG-SGH-I727 using xda premium
orlandoxpolice said:
Did you darkside?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I believe the first time I flashed CM9 I did the darkside cache only wipe as per the instructions since I was on non-touch cwm at the time.
Guys, I have a huge problem. I installed DPI Modder Pro the other day and set to 160. Everything was cool until I realized I could not make a call after installing 7/1. I see the time increasing and the other person I'm calling is getting the call but I can't hear anything, sometimes though its just stuck on "dialing" yet the other person's phone is ringing. I luckily backed up right after installing the 6/30 nightly but I can only use the phone after the first boot from a restore. If I reboot, calls are gone again. Can't make them, can't get them. I flashed back to stock via Odin and was able to repeatedly reboot and have phone access with rogers 2.3.5 stock. I did a clean CM9 install and like usual, the first boot ran the call no problem but after a reboot, nothing. I don't know what else to try. I've fixed permissions, wiped with CWR, you name it. I'm stuck on 6/30 and I can't power down or reboot or I have to restore to get calls back.
Click to expand...
Click to collapse
Well, first off, I did not change my screen density, yet still lost my in-call audio. Secondly, when I flash back to stock GB, not only does my in-call audio not return, I actually lose ALL of my audio.
Never lost in call audio on any of the aosp roms. Come to think of it calling has never been an issue for me.
Sent from my SGH-I727 using xda premium
Odin usually fixes all which is why this is odd
Sent from my SAMSUNG-SGH-I727 using xda premium
Although I'm still not sure exactly what the cause of the problem was, R4ins 7/03 aokp nightly finally gave me back my in-call audio. I'll run it for about a week and see if the fix stays. Until then I'm still tentative to call this bug "fixed" as this is pretty much what happened the last time I lost my in-call audio.
Edit: As I was afraid of, my in-call audio has again ceased to exist. First call worked just fine, left the phone alone for a couple hours while I went out to the beach, and when I came back and tried to place a call all I could hear was a very, very faint buzzing coming from the ear speaker.
Several months ago when it was still alpha 1 or 2 i found that after changing dpi calls can be borked so i pushed a dpi modified phone.apk for cm9 that i found in the epic 4g touch forums it seemed to fix mine and others rom.... But on alpha 5 that problem should be fixed
What kernel were you using i heard that instigators 3.x kernel had some random bugs with call audio and camera I'm on 2.8 with no probs and I'm using the nightly 7/02 build
Also welcome back to skyrocket forums you were missed
CM9 Skyrocket
Maybe its a bootloader thing? Don't the ics leaks from design gears contain new bootloaders? Maybe I'm crazy. We need to find out if people that this happens to people who havent ever flashed the Odin ics leak prior to flashing any ics builds. I always have flashed the latest leak then went on to aosp and aokp just a **** I the dark I guess:thumbup:
Sent from my SGH-I727 using Tapatalk 2
droid512 said:
Several months ago when it was still alpha 1 or 2 i found that after changing dpi calls can be borked so i pushed a dpi modified phone.apk for cm9 that i found in the epic 4g touch forums it seemed to fix mine and others rom.... But on alpha 5 that problem should be fixed
What kernel were you using i heard that instigators 3.x kernel had some random bugs with call audio and camera I'm on 2.8 with no probs and I'm using the nightly 7/02 build
Also welcome back to skyrocket forums you were missed
CM9 Skyrocket
Click to expand...
Click to collapse
The first time it occurred I was using the stock cm9 kernel provided by teamchopsticks. Since then, I've used a variety of different kernels, but they've all given me the same result.
Thanks for welcoming me back, I missed you guys too.
cdshepherd said:
Maybe its a bootloader thing? Don't the ics leaks from design gears contain new bootloaders? Maybe I'm crazy. We need to find out if people that this happens to people who havent ever flashed the Odin ics leak prior to flashing any ics builds. I always have flashed the latest leak then went on to aosp and aokp just a **** I the dark I guess:thumbup:
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
There maybe some validity to this my phone had the odin leak then ics roms then cm9 but my friends just went from gb to smooth ice then to cm9 and he always has issues were on the same build and kernel and radio idk why mine always runs better
CM9 Skyrocket
Ok guys, I don't even know where to begin. I'm a noob to flashing roms and such. I have a G2X and I was so frustrated by the lag and glitchiness of the phone. So i rooted my phone through superoneclick and i flashed CM 7.2. I could receive texts and send texts no problem until i flashed an ICS rom. The first one i flashed was EB bld 5.5 and i noticed that people tried to text me but i couldnt receive any. I can send texts but i cant receive them. I went through tons and tons of forums and other sites but i couldnt find a solution. Does anyone know y i cant receive texts?
Reflash? If issue consists then try other ics roms
Sent from my LG-P999 using xda app-developers app
Check your APN settings. Sometimes when I flash a new ROM my SIM card will put most of the info in but may leave out the network password it something.
You can usually get your apn settings from your service providers website. Or somebody here will provide them? Who is your cellular company?
Remember to use G2X scrubber or Nullifier before flashing a new ROM. Then flash your Gapps and reboot. Then just leave your phone alone for 10 minutes or so. Also, try calling someone. If you can't hear the call audio, its probably a baseband issue. The G2X development forums have some very great guides.
Sent from my LG-P999 using xda premium
Running Hellfire Sandwich 1.9
Shoothy said:
Remember to use G2X scrubber or Nullifier before flashing a new ROM. Then flash your Gapps and reboot. Then just leave your phone alone for 10 minutes or so. Also, try calling someone. If you can't hear the call audio, its probably a baseband issue. The G2X development forums have some very great guides.
Sent from my LG-P999 using xda premium
Running Hellfire Sandwich 1.9
Click to expand...
Click to collapse
I have this exact same problem. For some reason I cannot receive sms on CM 7.2 based roms or any ICS roms. However it works when I use the MIUI 2.2.24 rom with the trinity ELP kernel by Morific. Very odd. Does anybody have any ideas I've been having this problem for a couple of months now and I'm running out of ideas. My baseband is the latest Mar 11 2012 one and i'm with Mobilicity (in Canada). Any help would be appreciated, thanks.
It's a problem with cm 7.2 based kernels. I submitted a catlog to the cm team but only a few phones are having this problem. The only thing I've found that works is flashing one of morifc's older kernels on top of cm 7 nothing I've tried works on ics roms. Also if you have wifi calling enabled it's strange but you should receive text messages.
Sent from my LG-P999 using xda premium
noodlev1 said:
It's a problem with cm 7.2 based kernels. I submitted a catlog to the cm team but only a few phones are having this problem. The only thing I've found that works is flashing one of morifc's older kernels on top of cm 7 nothing I've tried works on ics roms. Also if you have wifi calling enabled it's strange but you should receive text messages.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Yeah, I was getting sick of the MIUI rom (and it was being weird) so I followed your advice and flashed Cyanogenmod 7.2 with a trinity kernel and all is well now. It is a shame that it won't work with ICS, hopefully that O2X leak will fix this issue. Also, the tmobile wifi calling app doesn't work since i'm on a different provider (Mobilicity). I was wondering if there is another app that is equivalent or if I could use the wifi calling app with Mobilicity somehow?
I don't know of any other apps that work like wifi calling and I'm pretty sure the tmobile wifi calling app only works with a tmobile network. I was hoping the cm team would have looked into this by now I submitted the ticket awhile ago and it got labeled as an apn issue which it clearly isn't. It's something in the kernel disregarding the sms notification.
Sent from my LG-P999 using xda premium
Recently I installed Pixel Plus UI in my Redmi Note 9(Merlin) , everything is fine but i can't able to Recieve Calls and Text Messages. So what should i do.