Related
Recently callers have been complaining that they hear their voice echo when talking to me...its only on their end...everything sounds fine on my end. It also only seems to happen when receiving calls from other cell phones. Is this happening to you? Also please state what rom you are using so we can try to determine if this is rom-related or a sprint service problem.
First back to the question... I don't recall. But so far I haven't heard it on my phone.
Using my HTC Evo phone which I'm using Xda app to post
I take it your running MIUI? The last couple of builds have had this issue. It will get worked out.
im not having the issue, but i would like to know, which rom are you on and did you ever fix it?
The only time this has come up is when people use the MIUI ROM. This is a known problem in that ROM
Try turning your speaker volume down as low as you can still hear it. Echo is caused by the combination of lag and the sound from the earpiece getting picked up by the mic.
Yes I'm using MIUI. Someone just complained about it for the 1st time the other day. I read it was common in MIUI rom but wanted to see if others had the same problem. It doesn't appear to happen when talking to someone on a land line...nor does it happen when talking to my fiancée who has tmobile. I thought about switching roms by i like MIUI too much. I don't talk on the phone much/for very long...so the people i talk to can suck it up for a few mins lol
Did you upgrade to the new MIUI from 1/23? They said it's fixed in that.
I've seen several threads about the problem of the call issues, When first the call echo now the bad quality sound on CM and MIUI..
Devs I love your roms. they are amazing and I know that you all probably had tried to solve the call issue once it for all. Even though you make magic to the call issues, it still not gone completely.
There might be other users like me that love roms. special if we want to run JB or MIUI or any other than Stock TW. but the call issues are taking us from using these amazing roms..
I personal am so jealous because I love to use miui on my phone or JB but everytime I do my wife calls me and boom I have to flash back to stock TW because of these issues. I think you all know that people you are talking to is the ones who cant hear you or have an echo...
Now some say the that problem is hardware some say its drivers I dont know what it is and I'm sure you ''DEVS'' know what it is causing it.
My question here is wether we are gonna get rid of this issue once it for all or are we close to it or there is nothing to do.
I know Eugene have done wonderful on getting it fix but although in my end the issue still comes...
P.S some say that problem is on one of the mics ''top one to be exactly'' is there a way to just shut it off,
Then again Im not trying to flame anybody this is something that just gets on my nerves. Now if you have some sarcasm to say keep it to your self Xda for me is like a family. and we all try to help each other
If someone knew how to fix it, don't you think it'd be fixed?
Sent from my SGH-T989 using xda premium
born2gethard said:
If someone knew how to fix it, don't you think it'd be fixed?
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
That's what I was thinking
just like any variant in the Galaxy S Line. There is no sure fire fix, because these roms are built off the SGSII and ported (officially/unofficially) to our's and other variants. the T-Mobile SGS 1 had the same microphone issues. These are driver related and won't be properly fixed without Device source information related the OS in question.
the easiest "temp" fix is to mute/unmute after recieving a phone call. This will generally fix the issue for the duration of that phone call.
for future reference though if your gonna go samsung, and plan on being a rom flasher, I would suggest you invest in an International Device as they recieve updates quicker, and tend to have there sources available (which means smoother more stable roms)
even the SGSIII is going to run into issues due to the chipset variation from the world version (dual core vs quad core)
on that note though, now that 4.0.4 has been officially released for the Hercules, we should see Small issues like this addressed in the aosp 4.0.4 for our device.
I see you showed interest in Jellybean, i'll be frank on this. Unless we get JB officially from samsung for our SGSII there will never be a "perfect" fix to the microphone issue. (maybe a possibility if the skyrocket were to get JB or even the Sprint Variant) but the 4'3 inch SGSII is seperate hardware therefore drivers aren't compatible.
If you are referring to ICS, the call quality issues were resolved long ago.
If you are using JB AOKP / CM, make sure you have enabled noise suppression within your call settings. Go to your dialer, hit the menu button and scroll down to noise suppression.
With that being said, I have no problems with call quality using the latest AOKP JB ROMs though YRMV.
Rod3 said:
If you are referring to ICS, the call quality issues were resolved long ago.
If you are using JB AOKP / CM, make sure you have enabled noise suppression within your call settings. Go to your dialer, hit the menu button and scroll down to noise suppression.
With that being said, I have no problems with call quality using the latest AOKP JB ROMs though YRMV.
Click to expand...
Click to collapse
ICS hasnt been fixed all the way.. The issue are still on Miui and CM9 although it is better but not gone completely.
I even been having problems where I have to speak louder so the other person can hear me on stock rom, also I noticed that every now and then this issue comes on ICS Miui. sometimes I have to hung up and call back.
Greetings,
First post here, I hope this is the appropriate section for it. I have google'd and forum searched extensively and have yet to find a thread dedicated soley to this issue. Many people have reported it within various ROM threads only to have the next poster state he doesn't have the issue and the problem get buried in a 500 page thread.
Having gotten my feet wet with the stock ICS ROM that came with my Galaxy S3, I was happy to enter the world of custom ROM's and flashed CM 10 M2 as my first custom ROM. I was very much enjoying CM 10 when I received my first phone call after switching. Being an exclusive speakerphone user, I answered the call and enabled the speakerphone as usual. The caller stated they couldn't understand me as there was an echo on the line. I turned speakerphone off and they stated the problem was fixed. After finishing the call, I called my cell phone from my landline and enabled the speakerphone on my S3, then walked to the other side of the house to minimize any close vicinity interference. When I spoke into my landline I could hear myself echo making a conversation almost impossible. I disabled the speakerphone on my S3 and the problem went away.
I restored my stock ICS ROM and was unable to duplicate the problem. I assumed the bug was specific to CM 10 and tried AOKP JB milestone 1 and had the same issue. Today I tried Task and Ktoonsez's latest AOKP JB 4.12 ROM and The Collective's AOCP ROM with the same results. All the problem ROM's were JB builds so perhaps it's a JB related issue. I will be trying a touchwiz based JB ROM next to see if I still have the issue.
I think alot of people assume when they read this bug report they blow it off as they can't actually hear the echo unless the person on the other line reports it. Maybe alot of people don't use speakerphone? I don't think it's a universal problem or more people would be reporting this but it's not intermittent either. I can reproduce it 100 percent of the time and it goes away when I recover to stock. I also removed my case when testing this and it had no effect. If there is a workaround or fix for this I would be very thankful to learn of it as I very much enjoyed the custom ROM's but I just can't give up speakerphone. Thanks in advance! :fingers-crossed:
I'm having the same issue...
+1
Follow up
kenrothman said:
I'm having the same issue...
+1
Click to expand...
Click to collapse
So today I tried newest builds of Parandoid Android, and Liquid Smooth with the same result. Pretty much all the popular ROM's in the "AT&T Galaxy S III Original Android Development" contain this bug, I'm assuming because they share alot of code. Seems like they base alot of work off of Cyanogen Mod so perhaps that's where it lies, I don't know.
What I do know is I installed DrewGaren's Jellybean 747 Milestone 7 ROM which is Touchwiz based and the speakerphone echo went away. So my stock ICS ROM and this one do not contain the issue but every other JB based ROM I have tried does. I don't have the knowledge to troubleshoot this issue I just wanted to share what I've found and hopefully someone with the knowledge can help track it down.
I do prefer the CM 10 style ROM's over the stock experience but I can't live without speakerphone so hopefully this issue gets resolved, thanks for listening!
I have the problem too. I bought my S3 3 weeks ago and within a few days rooted it and installed the latest CM10 nightly. The first time I used the speakerphone I became aware of the echo problem with the it. So I switched back to the stock rom and the problem was gone, so I knew it wasn't a hardware problem with my phone. I've tried every nightly CM10 rom including the recently released stable build. I also tried the latest official AOKP as well as Task and Koonsez's latest build and they all produce the echo.
My buddy suggested I try the black jelly rom, and that's the only one I've been able to use that doesn't have any echo, but it's a touchwiz/Samsung based build. It's not bad, but it doesn't support wifi tethering and it's not as smooth as CM or AOKP. I really want to run CM but can't live without speakerphone.
On a side note, I rooted and rom'd my wife's and friends S3 the exact same way as mine and neither of theirs have the speakerphone echo problem. I suspect there are some hardware differences with Samsung phones. Maybe different parts suppliers that aren't playing properly with the drivers in the CM10 build.
From my tests this bug sounds like the mic is turned up max when speakerphone is on so it's super sensitive. Also, the volume level doesn't have any effect on the speakerphone volume whether you raise or lower it.
Really hope the dev's can fix this so I can run CM or AOKP once and for all.
On a final note, my phone is blue, while both my wife's and my buddy's are white. I don't want to conclude that the white phones don't have the speakerphone echo problem with CM roms. Hope it's just a coincidence.
for cm10 there is an official bug ticket for it here : https://code.google.com/p/cyanogenm...on Model Network Owner Summary Stars Priority
Randomacts said:
for cm10 there is an official bug ticket for it here : https://code.google.com/p/cyanogenm...on Model Network Owner Summary Stars Priority
Click to expand...
Click to collapse
thanks for pointing that out. looks like it's not really a popular issue, or popular enough to get them focussed on fixing it
anyone have any thoughts as to why identical phones don't behave the same, ie some S3's have the echo and some don't? I have 3 days left (30 day purchase return policy) to exchange my phone, and am contemplating getting it swapped to see if I get lucky with another unit which won't have an echo problem running CM10 or AOKP.
gots54 said:
thanks for pointing that out. looks like it's not really a popular issue, or popular enough to get them focussed on fixing it
anyone have any thoughts as to why identical phones don't behave the same, ie some S3's have the echo and some don't? I have 3 days left (30 day purchase return policy) to exchange my phone, and am contemplating getting it swapped to see if I get lucky with another unit which won't have an echo problem running CM10 or AOKP.
Click to expand...
Click to collapse
Hi, just wondering if anyone has found a fix for this or any other AOSP JB Roms that has the speakerphone echo fixed?
ladd76 said:
Greetings,
First post here, I hope this is the appropriate section for it. I have google'd and forum searched extensively and have yet to find a thread dedicated soley to this issue. Many people have reported it within various ROM threads only to have the next poster state he doesn't have the issue and the problem get buried in a 500 page thread.
Having gotten my feet wet with the stock ICS ROM that came with my Galaxy S3, I was happy to enter the world of custom ROM's and flashed CM 10 M2 as my first custom ROM. I was very much enjoying CM 10 when I received my first phone call after switching. Being an exclusive speakerphone user, I answered the call and enabled the speakerphone as usual. The caller stated they couldn't understand me as there was an echo on the line. I turned speakerphone off and they stated the problem was fixed. After finishing the call, I called my cell phone from my landline and enabled the speakerphone on my S3, then walked to the other side of the house to minimize any close vicinity interference. When I spoke into my landline I could hear myself echo making a conversation almost impossible. I disabled the speakerphone on my S3 and the problem went away.
I restored my stock ICS ROM and was unable to duplicate the problem. I assumed the bug was specific to CM 10 and tried AOKP JB milestone 1 and had the same issue. Today I tried Task and Ktoonsez's latest AOKP JB 4.12 ROM and The Collective's AOCP ROM with the same results. All the problem ROM's were JB builds so perhaps it's a JB related issue. I will be trying a touchwiz based JB ROM next to see if I still have the issue.
I think alot of people assume when they read this bug report they blow it off as they can't actually hear the echo unless the person on the other line reports it. Maybe alot of people don't use speakerphone? I don't think it's a universal problem or more people would be reporting this but it's not intermittent either. I can reproduce it 100 percent of the time and it goes away when I recover to stock. I also removed my case when testing this and it had no effect. If there is a workaround or fix for this I would be very thankful to learn of it as I very much enjoyed the custom ROM's but I just can't give up speakerphone. Thanks in advance! :fingers-crossed:
Click to expand...
Click to collapse
+1
speakerphone echo
I also have this problem. using baked 8. with kt747 and its awesome!! They seem to be aware and working on it. tried a different kernel but no dice. Ive been in every setting cant seem to get rid of it. my phone is white so its not that. hope someone can figure this out soon. tw roms dont have this problem and I like the aosp feel.It would be nice to know if anyone even an idea of the cause, maybe the users could check files and find something.
I confirm that I LOVE these ROMs, but absolutely need a working speakerphone too.
Some other thread said something about changing the radio to ULVA3 or something like that... not sure if anyone had any luck with that.
Anyways, thought I'd break my lurked tendencies and post for my 1st time here.
Love my GS3!
So I've been very happily using the Samsung-based ROM called Devils Reject since Dec 2012, and have been on V7 since it came out a few months ago and have been really happy with it. It's pretty smooth and stable, has great battery life, has tethering, custom toggles, various battery icons, AOKP lockscreen, power button menus, plus a bunch of other stuff I can't remember, and of course, there are no speakerphone problems.
But I've always been curious about giving CM another chance with CM10.1 and especially with the latest RC2 out.
Does anyone know if the speakerphone bug still exists with it?
speakerphone echo bug in CM10.1 RC2 for quincyatt
gots54 said:
So I've been very happily using the Samsung-based ROM called Devils Reject since Dec 2012, and have been on V7 since it came out a few months ago and have been really happy with it. It's pretty smooth and stable, has great battery life, has tethering, custom toggles, various battery icons, AOKP lockscreen, power button menus, plus a bunch of other stuff I can't remember, and of course, there are no speakerphone problems.
But I've always been curious about giving CM another chance with CM10.1 and especially with the latest RC2 out.
Does anyone know if the speakerphone bug still exists with it?
Click to expand...
Click to collapse
I have the speakerphone echo bug on my Samsung Galaxy Note with CM10.1 RC2. This has happening on earlier versions as well, but I thought a reset/wipe fresh install would fix it. Would like to stay on CM10.1 but I really depend on my speakerphone.
Is anyone else experiencing this? I went from stock, to rooting with the tool kit. I have twrp recovery. First I flashed frosty jelly bean, then I tried domination because I thought it was the ROM. Whats happening is, when I make a call the first ring sounds like a choppy ring like it is not a good connection, then that little tune that plays(the connection sound I guess) is delayed until after the first ring. Normally I would hear that little tune first, then it would start ringing. When the other person picks up on the other end, they can barely hear me. They have said I sound far away or I sound like darth vator lol. They keep saying "what, what", everytime I say something. This does not happen every call though. I immediately thought it was frosty jelly bean, so I flashed Denomination instead, but same call issue. Another problem im having with Denomination is: I read on the forum a little bit that some people when switching from 4.2. to 4.1. their gps wasnt working. I guess thats besides the point since I didnt flash any 4.2 Roms yet, but with my gps problem, its a little different. When I turn on google maps, originally without gps enabled it was able to pick up my location using mobile networks or wifi (yes they are turned on). It does in fact locate when gps is on. What do you guys think about these 2 problems?
Have you tried changing the Kernel? I have had the odd call sound issues on certain combinations of kernels and roms.
jcbofkc said:
Have you tried changing the Kernel? I have had the odd call sound issues on certain combinations of kernels and roms.
Click to expand...
Click to collapse
No. Whatever Kernel that it comes with I guess. Are you talking about in the aroma installer, it asks you if you want aggressive, optimal, extreme RAM free, etc? Are those the different kernels? If not, what are those options?
Hello and thank you in advance to all. I have a t989,
I run AOKP Galaxysbean V_12
KKO Kernel Governor is Smartass V2 and I/O is deadline
UVLI4 Radio
Problem: I know for a fact this is not a hardware problem, because I have went through 3 phone replacements because of stupidity and learning how to root phone, flash roms, yada, yada, etc. And with each of these phones this persistent problem occurs where all of the sudden at any given time, I will go to make a call and nothing. I can't hear the ring of another person's number, my voicemail, etc. The person does get the call, and when they answer, I still cannot hear them, and they cannot hear me.
Resolution: Ways I have fixed this before are with the first and second phone I flashed over a new radio, (previously UVLE1, UVLH1, 4G Blaze) and it fixed the calling upon reboot. Also I had flashed custom roms, or restored previous Nandroid backups and it worked again. (Little annoying doing this every 3 or 4 days. Though today, this happened with my newest phone, and flashing a radio did not work nor did restoring a Nandroid. This time I had to flash a new custom rom, then it worked. Then I flashed back over the Nandroid and it still works as of now.
Question: Could this be because of the kernel? Or the rom?
deleted
same here
Me and my wife have the same issues. We both have GS2s but hers is stock unrooted and mine is running CM10.1. Been dealing with Tmobile for months without success, swapping out cut down on how often its happening but did not fix it. Tmobile is stumped, very annoyed by this issue.
Not sure what's causing the problem but it seems jellybean 4.2 has fixed this issue. Try flashing AOKP 4.2 and make sure noise suppression is enabled and call this number 9143388802. The third option is an echo test and fourth option let's you record a playback to listen to how you sound. If you sound normal and people are still complaining then its their phone.
Sent from my SGH-T989 using xda app-developers app
I've come to the conclusion that its a rom problem because for me it happens with only certain roms. Ive tried all the rom kernel combinations and different radios but the only fix I've found is to retire that particular rom, no matter how good it is. Smoothness aint gonna get the cops or the fireman to your house. The only roms that have worked for me as far as call quality are, for some reason all of TheLastSidekick's Kangs, Darkside evolution 3, Sky Jellybean, Rushing's Bulletproof,and both of the 10.1 variants we have. The strange thing is I can't recall any call quality issue's when flashing roms from the Skyrocket thread. For instance I get the worst call quality ever using Jedi Jelly, but I'm crystal clear using Embryo from the Skyrockets thread, so much so I wont even try our version of the same rom.
I blame T-Mobile network. This would happen to me all the way back to my old flip phones. Every other call or so would do this. I've always put up with it cuz I like T-Mobile customer service.
Sent from my SGH-T989 using xda app-developers app
bonetweeter122 said:
I blame T-Mobile network. This would happen to me all the way back to my old flip phones. Every other call or so would do this. I've always put up with it cuz I like T-Mobile customer service.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I wouldn't go that far because I never had a problem on the Sensation no matter what rom I was using. I blame sammy
You know.. Now that I think about it.. My old flip phones were Samsung! Lil..
Sent from my SGH-T989 using xda app-developers app
I actually just realized this problem persisted when I would turn on the phone and try to make a phone call to quickly. After becoming aware of this. I turned the phone off and allowed it to fully boot back up, and it worked again.
deleted
WatchGintama said:
I can confirm that this is the problem. I rebooted my phone, called someone right away, and couldn't hear anything. Next I let it load for 40 seconds after boot, and I can hear fine.
Now we have to tell t-mobile this.
Click to expand...
Click to collapse
This is not the issue, it also happens to phones that have been on for minutes/hours/days.
Is there any updates on this issue? My wife is having this problem on her phone, and it seem like it's been getting worse...
gwuhua1984 said:
Is there any updates on this issue? My wife is having this problem on her phone, and it seem like it's been getting worse...
Click to expand...
Click to collapse
I found out with my problem. It was when I tried to make a call to soon. It would do this. As long as I have let the phone load for a minute or two after boot, I haven't had any more problems. My problem may be different from yours tho. Hope this helps.
I'm having this issue, and its not from calling too quick after a boot.
It came on out of the blue the evening of March 6 ...
I have the Tmob phone but it's unlocked and I'm using a Straight Talk AT&T SIM, connected to the AT&T network in Sierra Vista, AZ.
Ok... I need help. I am such a novice at this stuff but I find myself so very interested in the world of root, and the freedom that it brings. Basically my entire knowledge of computers..... Is Android, and worse than that, I'm self taught... Please don't run!! I'm a super quick study. Ok now to my problem, I started off rooting my T 989 surprisingly enough with absolutely no issues at all, or at least that I could tell. Ran beautiful and super smooth, then I went app hoarding and installed A fonts package installer, opened it, it installed about 85 prcnt. done and crashed. Never made it back. The novice, and the dumbass in me, FREAKED! and did an uneducated, no experience attempt to make recovery....... 4 times needless to say that I COMPLETELY wiped the entire phone. I had a friend bless me and show me a thing or two and I successfully managed to flash one of your Roms to it and I must tell you that I supremely thankful to all who n these projects.... MAD RESPECT to all of you. So the one issue I am clearly having is everyone I speak to says I sound like I'm on speaker or just can't generally hear me. Been through the settings a couple of times and I am pretty sure that I have them correct, and I have not touched anything that I wasn't sure about, and I definitely have completely refrained from pimpin my kernel. I really just need someone who can spend a little time setting me straight on some unfamiliars. Also just have a few stupid questions that won't be the least bit stupid after I get them answered. Any time any one can lend would be greatly appreciated and someone's good deed for the day. Thanks for allowing me to vent guy's
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
---------- Post added at 05:03 AM ---------- Previous post was at 04:54 AM ----------
And no, issue definitely is not exclusive to happening on reboot, mine has been that way ever since flashing, and on every call. But I can hear the other end perfectly......
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
neilc300 said:
Ok... I need help. I am such a novice at this stuff but I find myself so very interested in the world of root, and the freedom that it brings. Basically my entire knowledge of computers..... Is Android, and worse than that, I'm self taught... Please don't run!! I'm a super quick study. Ok now to my problem, I started off rooting my T 989 surprisingly enough with absolutely no issues at all, or at least that I could tell. Ran beautiful and super smooth, then I went app hoarding and installed A fonts package installer, opened it, it installed about 85 prcnt. done and crashed. Never made it back. The novice, and the dumbass in me, FREAKED! and did an uneducated, no experience attempt to make recovery....... 4 times needless to say that I COMPLETELY wiped the entire phone. I had a friend bless me and show me a thing or two and I successfully managed to flash one of your Roms to it and I must tell you that I supremely thankful to all who n these projects.... MAD RESPECT to all of you. So the one issue I am clearly having is everyone I speak to says I sound like I'm on speaker or just can't generally hear me. Been through the settings a couple of times and I am pretty sure that I have them correct, and I have not touched anything that I wasn't sure about, and I definitely have completely refrained from pimpin my kernel. I really just need someone who can spend a little time setting me straight on some unfamiliars. Also just have a few stupid questions that won't be the least bit stupid after I get them answered. Any time any one can lend would be greatly appreciated and someone's good deed for the day. Thanks for allowing me to vent guy's
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
---------- Post added at 05:03 AM ---------- Previous post was at 04:54 AM ----------
And no, issue definitely is not exclusive to happening on reboot, mine has been that way ever since flashing, and on every call. But I can hear the other end perfectly......
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Just leave me some thanks. Under your phone settings, there should be a noise surrpression box. Make sure it is check marked. Every time I do that people have said I sound better. What do you want to do? Change it back to custom rom? P.S. ALWAYS MAKE A NANDROID BEFORE YOU DO ANYTHING.. ALWAYS ALWAYS ALWAYS!.. Google will solve many questions too. If nothing helps or you need to be walked through some processes, message me.
Enable noise suppression in phone settings. Fixed my problem.
[ NEXUS⁴ / VANILLA ROOTBOX / APEX PRO / TAPATALK ]
dEris said:
Enable noise suppression in phone settings. Fixed my problem.
[ NEXUS⁴ / VANILLA ROOTBOX / APEX PRO / TAPATALK ]
Click to expand...
Click to collapse
I'm running cm10.1 nightlys as and I cannot find that setting.
Trbobuick said:
I'm running cm10.1 nightlys as and I cannot find that setting.
Click to expand...
Click to collapse
Open phone dialer, menu settings, and it's in there.