Develop Bugs

Popping, clicking noise on phone calls

I was wondering if anyone else has this issue:
I notice that my phone sometimes makes loud pop noises when phone connects during phone calls.
It does not happen when dialing sprint voicemail , *2 or google voice mail .
It appears to happen when dialing certain landline numbers and certain verizon cell phone numbers.
I have read that some people who have the original epic 4g had experienced clicking and popping noises on phone calls.
However, I have not read anything of anyone who has the epic 4g touch having these issues.
Your input is Greatly Appreciated.
Sent from my SPH-D710 using XDA App

Fyi ...here is a link to this issue on the original epic 4g ..
http://forum.ppcgeeks.com/sprint-epic-4g/140584-epic-4g-weird-popping-noise.html
Sent from my SPH-D710 using XDA App

I have this problem too.
I mostly dial Verizon cellphones and I do believe that is when I have this problem most often.
I'll start to take more notice of the types of calls I am placing when this happens to me.
Not sure if its a phone problem, or a Sprint problem?
Could it be the default voice encoder? Default is EVRC. I just changed mine to 13K and I'll see if it makes a difference in the next few days. Then I'll try 4GV as well. (unless someone wants to let me know this is a waste of time testing?)
EDIT: the popping noise we had on the Epic 4G was the actual speaker. It physically made popping/clicking noises. I had that as well. But here, I am having popping/line cracking in the audio of the telephone while dialing/call connecting. Which problem are you having with Epic Touch?

Im hearing a popping , clicking noise coming from earpiece speaker upon connecting on some phone calls that I initiate . It doesn't happen on all phone calls though. It has happened when calling Verizon Wireless phones and some Landline phone numbers.
It has been happening in different locations ( about a 60 mile radius) throughout Chicago ,Illinois metropolitan area. I guess I can rule out a bad tower being the cause.
My phone is stock and not rooted.
Thank You very much for your input. I really appreciate it.
I am glad someone else has experienced this issue. I hope that the cause can be pinpointed and that a fix can be made for it.
Sent from my SPH-D710 using XDA App

Having this issue right now as I talk to my fiance on her VZN cell phone. Never really noticed it till this time.

Thank you very much for your input!
That now makes 3 of us having this issue. I wonder if it is only happening to a few of us or if it is more of a widespread issue.
I wish we could identify the cause of the popping noise. I never had a phone that did that. It is strange.
I would really like to fix this if at all possible.
Sent from my SPH-D710 using XDA App

Had the same exact issue with my Epic touch that i purchased on launch day, took it over to sprint and the representative also heard it. he did a reset apparently thinking it would fix it. the first couple of calls after the reset did make the popping noise go away so i left the store satisfied. getting into the car i made a call and the noise was back. went back in talk to the sales person again and he exchanged the phone for a new one (this is a week after having the phone). with the new one i havent ran into any noise what so ever so im guessing it was just a defect in that unit. just telling my experience.

Mu5ic92 said:
Had the same exact issue with my Epic touch that i purchased on launch day, took it over to sprint and the representative also heard it. he did a reset apparently thinking it would fix it. the first couple of calls after the reset did make the popping noise go away so i left the store satisfied. getting into the car i made a call and the noise was back. went back in talk to the sales person again and he exchanged the phone for a new one (this is a week after having the phone). with the new one i havent ran into any noise what so ever so im guessing it was just a defect in that unit. just telling my experience.
Click to expand...
Click to collapse
Thanks for sharing your experience. I too bought mine on launch day.
I hope mine isn't a defective unit.
I will have the phone checked out at Service Center to see if it is defective or not.

OK, I have not been having these problems for the past 2 days.
First, I did a "Data Reset": http://forum.xda-developers.com/showthread.php?t=1289475
Second: Changed my default Encoder to "13K" under the Advanced menu for "##3282#"
SO, my signal, data speeds, all seem better. I haven't noticed a difference in audio call quality, but I havent noticed any problems. Disclaimer: I do not know if it actually fixed anything. I will try going back to the system default of "EVRC" encoder to see if my problems reappear.
Does anyone know if "Data Reset" can actually fix these types of problems?

OK So I got a call from the finace today while I was at school. She was on her last break at work and I was just out of class for the day (and we just got off the phone she went out for dinner with family) and this problem did not come up on either of the 2 calls (there were more in between that also did not have them)
While she is on VZN I'm kinda wondering so far today not once have I heard the issue and it's loud enough and weird enough that I would notice it on any call but as I said not once today has it happened. BTW this is a none rooted device and I've done NO tweaks at all to it everything is flat out stock on this phone right now. so *shrug*

Thanks for all your help Chip! , Mu5ic92 and Cidica !! I Appreciate it!
I have noticed that the popping noise is intermittent. It has only happened 1 time out of 5 phone calls I made throughout the day.
I am going to try the data reset and also changing to the 13k voice to see if it helps.
Sent from my SPH-D710 using xda premium

Microphone cutting out mid call

Edit: please see this Google issue tracker post and star it to get Google's attention!
http://code.google.com/p/android/issues/detail?id=24019
I've had it happen 3 times now that I'll be on a call for a number of minutes and all of a sudden the person I'm talking to won't hear me any more. To be fair, I've been talking to the same person, and each time it's been an extended call (5+ minutes). It happened on Saturday, twice. Since then, I have wiped data/cache and flashed a custom rom. It happened again this evening, right around 10 minutes into the call.
The microphone doesn't come back. I tried turning on speaker phone and muting/unmuting my mic, but it won't bring the microphone back. Like I said, this is the same person I've spoken to each time, however, I've been speaking with them often (with their current phone) on my previous phone and never had this issue, so I'm not sure if it's their phone's problem. I spoke with someone else for 30+ minutes on Sunday and didn't have this happen.
To remedy the situation, I just hang up and call back and it works fine, until it happens again.
I'm confused. Is my phone problematic or is it a software bug or is it the other person's phone? Is anyone else experiencing this?
EDIT: Just thought I'd mention I'm on VZW LTE/CDMA.

Thought I was the only one with this problem. Had the exact same thing happen to me talking with my girlfriend the past two nights. Think I'm going to blow away everything and go back to stock 4.0.2. I think it's an app that's misbehaving.

Please report back with your findings.

I've had the same thing happen to me. It has happened the most often when talking to my gf who has an iphone 4 on ATT, but it also happened when I was trying to make dinner reservations at a restaurant that was using a landline.
I am running stock 4.0.2.
If anyone has any suggestions, I'm all ears.

This was a common problem on the Samsung Droid Charge, which uses the same questionable Via baseband modem for voice calls. The earlier Charge Froyo firmware had all kinds of voice issues: 1) outgoing voice drop. 2) systematic cut in/out. 3) garbled robot voice quality. 4) loud ear hurting static. Since the latest Charge firmware EP4 (gingerbread), all issues except occasional robot voice are fixed. The phone is now usable where it was laughable before. The loud static may have been linked to certain phones / hardware rather than firmware.
Hopefully Samsung can incorporate the Charge fixes into the Nexus.
Hopefully Samsung stops using 3rd rate Via chips.

Thanks for the input. Nice to have an idea of what's going on.
Sent from my Galaxy Nexus using Tapatalk

Hey I have this happen about once a day sometimes more and doesnt matter who im talking to it can happen to anyone at anytime. This is very annoying seems like the smarter and more advance these phones get the crappier the actual phone call part of it gets. I think they forget cell phones primarily are for phone calls

Ironically 2 of my calls today complained i was dropping out. But i had full signal. My phone is brand new so these are the only calls ive really made so far.

Reply I had the same thing happening to mine. I was actually on the phone with VZW Level 2 Tech support when the mic went dead. It happened twice while talking to the same agent. She said it sounded like a clicking noise on her end. She then told me to take the phone back to the store.
I went in and got it swapped for a new one and had to return that one the same day because the ear piece sounded blown. Now on my 3rd Galaxy Nexus. The mic issue hasn't happened yet but I just got this one yesterday.... I'll report back if it happens again.
Sent from my Galaxy Nexus using xda premium

I don't think this is a hardware problem. I've had this happen on all three GNs I've had. This last time I was talking on my jawbone headset. I tried switching to the phone mike and speaker phone it did not make a difference. I also tried muting and unmuting. How do we get Samsung to acknowledge this problem?

This happened to me a couple of times also, stock 4.0.2

I have the same problem on stock 4.0.2 and on RevolutionHD 2.1.2. I spent an hour or so with level 2 tech support. I was told that I was the only person to report this issue. They suggested that I change it out or switch to a different phone. My Son-in-Law has the Nexus as well and also has the same issue. I guess I have till 1/15/2012 to make up my mind.

I am having the exact same issues. I will say it lasts about 3-5mins in the call then no one can hear me, and I have to call the people back. I love my Nexus!! I am so glad that I am not the only one having this issue. Edit: I have gone on the VZW Tech Forums and informed them of my problem, and pointed to this thread. I am hoping I hear something from VZW. Maybe if we can get more people to post on the thread over there, VZW and Samsung will see there is a problem. Heres the link h t t p ://community.vzw.com/t5/4G-Discussion/No-One-Can-Hear-Me-After-3-5mins/td-p/762556 (sorry had to space the http part since I am new.

I've had this issue too. Sounds like a resonably easy thing to fix with software.
Sent from my Xoom using xda premium

Has anybody had this happen on 4.0.3? How about on the GSM GNex? Just trying to narrow it down.

Exact same problem here. I called Verizon and they sent out a new one. But after a few calls longer than 5 minutes the microphone went out and I had to call back. I reused the same SIM card. Could that be a potential solution?
Sent from my Galaxy Nexus using Tapatalk

I made tons of test calls today and not a single issue on my GSM version. I only experienced this cut out issue the first day so guess I'm good for now...

I've had this happen on me twice running a 4.03 Custom Rom. Happened about 15 minutes into each call

I believe it to be hardware.

Why do you think its hardware?
Sent from my Galaxy Nexus using Tapatalk

4th nexus same issue

As of now I'm on my 4th Gnexus and once again I'm being plagued with the same issue I have since my first one back on launch day. Loss of voice during a call, high pitch noises, (think scratching on a chalk board) loss of sound on all key press as well as numbers when dialing.
I have called about this issue. First time around Verizon said take it back get a new one. So I did that and so on happened 2 more times same issue same results. Now on my 4th one its starting again. So verizon said it was Samsung and Samsung said Verizon.
So I was hoping for some input on what direction I should go now.
Sent from my Galaxy Nexus using XDA

After so many replacements, I can only imagine that this is happening because of your location?
Sent from my GT-P7510 using xda premium

My wife has the same phone and she has not had any of these issues. On the other had she doesn't use her phone as much as I do! I'm pretty much on mine all day and she maybe looks at it once a day.
Sent from my Galaxy Nexus using XDA

srh21 said:
My wife has the same phone and she has not had any of these issues. On the other had she doesn't use her phone as much as I do! I'm pretty much on mine all day and she maybe looks at it once a day.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
This is an obvious case of user-error. The odds of getting a defunct phone that many times in a row is about like winning the lottery, literally.

srh21 said:
As of now I'm on my 4th Gnexus and once again I'm being plagued with the same issue I have since my first one back on launch day. Loss of voice during a call, high pitch noises, (think scratching on a chalk board) loss of sound on all key press as well as numbers when dialing.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
when you said high pitch noises, do you mean that during a call you can hear a buzzing sort of noise when people speak? I get that on my nexus too, it's slightly irritating but I'll live with it, better than spending time to unroot it, go back to stock and then waste a whole week in the service centre.

akira02rex said:
This is an obvious case of user-error. The odds of getting a defunct phone that many times in a row is about like winning the lottery, literally.
Click to expand...
Click to collapse
It's obviously not user error.. If you read a bit you'd see there is a very lengthy thread about this very issue.. It's called microphone cutting out during call or something like that.. You can replace your phone as much as you want, it's not going to change it. the cause is unknown but I believe they have at least determined it not to be hardware..
Sent from my Galaxy Nexus using XDA App

Powell730 said:
It's obviously not user error.. If you read a bit you'd see there is a very lengthy thread about this very issue.. It's called microphone cutting out during call or something like that.. You can replace your phone as much as you want, it's not going to change it. the cause is unknown but I believe they have at least determined it not to be hardware..
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
That is correct. Audio outbound gets garbled and then lost completely. This is the worst bug of this phone. I can't count how many phone calls where I'd have to hang up and redial because the other person couldn't hear me anymore.
Sent from my Galaxy Nexus using Tapatalk

I'd blame the carrier, as i'm on Orange UK, and I use T-Mobile UK as well, and call quality both ends, is excellent

Your wife may not have the issue but are y'all talking on the same tower when the issue arises? I'm on Verizon as well and never had this problem. That said, I don't talk a lot, maybe 400 minutes a month - mostly to my boss that has an iPhone so half the time I can't hear crap anyway due to that fact.
I will say, as a recent T-Mobile transplant that has used Verizon off and on for several years with work phones, Verizon doesn't seem to have the same call quality in general terms. Maybe it's just my ear, but even back in the day I owned some Motorola claim shells that sounded pretty muddy.
Have you tried to replicate the problem on a completely stock phone with no 3rd party apps? I wonder if there's a conflict somewhere.

akira02rex said:
This is an obvious case of user-error. The odds of getting a defunct phone that many times in a row is about like winning the lottery, literally.
Click to expand...
Click to collapse
Not sure how it could be user error as well. This isn't my first phone.

srh21 said:
Not sure how it could be user error as well. This isn't my first phone.
Click to expand...
Click to collapse
KWKSLVR said:
Your wife may not have the issue but are y'all talking on the same tower when the issue arises? I'm on Verizon as well and never had this problem. That said, I don't talk a lot, maybe 400 minutes a month - mostly to my boss that has an iPhone so half the time I can't hear crap anyway due to that fact.
I will say, as a recent T-Mobile transplant that has used Verizon off and on for several years with work phones, Verizon doesn't seem to have the same call quality in general terms. Maybe it's just my ear, but even back in the day I owned some Motorola claim shells that sounded pretty muddy.
Have you tried to replicate the problem on a completely stock phone with no 3rd party apps? I wonder if there's a conflict somewhere.
Click to expand...
Click to collapse
I pretty much tried everything. New sim cards, using it with nothing installed (stock) I'm super bummed I been waiting on a nexus device to hit Verizon for a while now. I'm not sure how much longer I'm going to put up with this.

What about rolling back onto 3G? Are you on the fringe of LTE connectivity at all?
I know a lot of people talk about call quality. Frankly, I haven't experienced any issues and no one has told me that it sounds like crap (and believe me, I have friends that would mention it, we're a HARSH bunch). I don't doubt they exist, and you certainly don't sound like 3/4ths of XDA that are overly dramatic whiners. Out of curiosity, roughly how many minutes a month do you talk? Any chance that it's just an issue where, well you know, the more you do something the more opportunity to experience something that goes wrong? I used to talk a ton for work, like 3000+ minutes a month. I had a lot more dropped calls then than now, know what I mean?
You know what I'd do, which Verizon would HATE but, hey, you are the customer. I'd take you and your wife's phone into Verizon, and have them flip the numbers around. Keep EVERYTHING else about the phones the same. Her apps stay, your apps stay, just swap the numbers around and try her phone with your regular use for maybe 3 or 4 days. If you can replicate the problem while she doesn't experience the issue at all on your phone, then you can probably narrow it down to either the tower your on, or maybe the phone really is just buggy after you've been on it for a while.
Every so often I'll have a long conversation and a call gets dropped, but I've never not been able to hear someone or them not be able to hear me. Like, they're the typical issues that you could assign to either being a tower pass off problem or the nature of LTE long before the phone (on either my end or the other person's end). But, like I said, that's a rare occurrence for me.

What version of ICS are you running? I had this same problem, specifically and most frequently the one where the audio cuts out of a call, sometimes it'd do it and force me to re-call my girlfriend as many as 3 or 4 times in an hour.
What fixed it was flashing ICS 4.0.4 released from Google themselves (if I waited for Verizon to do it I'd probably be single by now). This fixed it for me immediately right out of the gate. I've had the other issues you spoke of every so often but the audio cut out was constant. This fixed everything. Been running for a while without problems (month or so maybe?).

Eh...you didn't flash it straight from Google. At best, you flashed it straight from the Verizon/Google ota server the test ota is on

I stand corrected, this is what I get when trying to post while on hold at work. Not straight from Google, leaked 4.0.4. Originally found it elsewhere linked to a google domain site, but it's best served up here.
http://forum.xda-developers.com/showthread.php?t=1481044
Give that a shot for now, fixed my woes anyway.

lblacklol said:
I stand corrected, this is what I get when trying to post while on hold at work. Not straight from Google, leaked 4.0.4. Originally found it elsewhere linked to a google domain site, but it's best served up here.
http://forum.xda-developers.com/showthread.php?t=1481044
Give that a shot for now, fixed my woes anyway.
Click to expand...
Click to collapse
From here?
http://android.clients.google.com/p....signed-mysid-IMM30B-from-ICL53F.659e0a8f.zip

try a different SIM/Network. you'd be suprised

IINexusII said:
try a different SIM/Network. you'd be suprised
Click to expand...
Click to collapse
What network do you suppose he would try?

Sounds like the phone is doing you a favor. If I had to talk to my girlfriend for an hour a day I'd want my phone to kill itself.

lblacklol said:
I stand corrected, this is what I get when trying to post while on hold at work. Not straight from Google, leaked 4.0.4. Originally found it elsewhere linked to a google domain site, but it's best served up here.
http://forum.xda-developers.com/showthread.php?t=1481044
Give that a shot for now, fixed my woes anyway.
Click to expand...
Click to collapse
Did not fix the microphone going out issue for me :-( I just flashed the 4.0.4 leak on Tuesday hoping it would alleviate this problem, but I had the mic go out about 15 mins into a call last night. Same story as with stock, had to hang up and re-dial to continue the conversation.

Permanent Call Echo Fix (T-989, ICS + GB Roms)

So I have had the call echo issue for some time. Specifically once I started flashing ICS leaks left and right, but come to find out our issue is HARDWARE related rather than software related. To be clear this is a fix for the caller echo issue where the person you are talking to on the phone hears their own voice echoing back to them.
This thread pretty much sums up the whole thing.
http://forum.xda-developers.com/showthread.php?t=1441510
Cliff notes: There is a speaker that has come loose in your phone either from some suspect glue, or perhaps even a rough tumble if you've dropped your phone once or twice. Once this happens, the nearby NC (noise cancellation) microphone picks it up and the call echo follows.
The fix here is very simple, you just need to unscrew the 6 tiny screws (careful not to strip them, and remove and reinstall them in the same order) and then pop off the casing that protects your T-989's innards. While the thread (and pics) above are for the international Galaxy SII, the important part at the top that needs to be covered (the speaker) is the same.
I tried the fix without really doing anything except removing the casing, cutting a small sliver of an old business card to put on top of the speaker, and closing and screwing the case back on. Didn't mess with anything else, and the fix works great. I called a couple people before I reinstalled the screws and I encourage everyone to make a test call to make sure the echo is gone before putting everything back together.
This is a really simple/easy fix to get rid of the call echo, and it explains while some people have the echo with/without a case and to varying degrees. But I'm now enjoying Racing's UCLD ICS Rom with no call echo and all is right in the world.
If anyone needs anymore help just let me know, and those of you that have the echo and try this please report back.

Interesting..... tho I do not have the dreaded call echo, this makes sense because I never dropped my phone. . I know what to do now if I have the problem tho!

Thanks forbthe saceifice my question is tjis: if itsbhardware, then why is it that i dont get the same issue when running non-ics roms. It seems to me that running a non sgh-t989 ics ported rom is the issue. While some of us have been lucky, its happened to me with every ics ported rom but never with gb or aosp roms(eugene cm7 kang). ??? On a side note, if thats what it takes ro fix it, im more than willing to wait for ics for our phone than possibly break something and void my warranty. Also, ive used a case and also havent and have dropped my phone a few times. I would like to see other confirmed reports of people trying this.
Sent from my SGH-T989 using XDA

This is a software issue not a hardware issue since in gb I get no echo
Sent from my SAMSUNG-SGH-I727 using xda premium

defconoi said:
This is a software issue not a hardware issue since in gb I get no echo
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Yea I second that! Hardware issue
Makes no since.it works great on gb Roms. Nice thought through. But I gotta say Epic Fail!!
Sent from my SGH-T989 using Tapatalk

Make sense why some users never experience it and others do no matter what they flash.
I am thinking Samsung obviously must have adjusted the noise cancellation mic sensitivity or settings with ICS. It could also be the ICS framework with the way it handles it or maybe the RIL (radio interface layer) of the ICS roms.
Either way it makes a lot of sense especially if so many dont experience the issue on any rom while others it is every ICS rom.

darkside79 said:
Yea I second that! Hardware issue
Makes no since.it works great on gb Roms. Nice thought through. But I gotta say Epic Fail!!
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Not an epic fail if he beat the call echo issue. Its quite a macguyver type fix but it did the trick. I would rather wait for it to be fixed on the software side myself, however.
Sent from my SGH-T989 using Tapatalk 2

defconoi said:
This is a software issue not a hardware issue since in gb I get no echo
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
+1 I think this thread should be for pple who has dropped they're phone some physical damage or something like that because it can just be a software issue

goldfingerfif said:
Make sense why some users never experience it and others do no matter what they flash.
I am thinking Samsung obviously must have adjusted the noise cancellation mic sensitivity or settings with ICS. It could also be the ICS framework with the way it handles it or maybe the RIL (radio interface layer) of the ICS roms.
Either way it makes a lot of sense especially if so many dont experience the issue on any rom while others it is every ICS rom.
Click to expand...
Click to collapse
Thats true or it could be that we don't have a official ics modem +Ics rom it could be interfering some how

Call echo only happens with volume up all the way. If u put in call volume to medium-low it isn't noticeable. Call ur cell from a landline and blow into the mic on landline phone, if it repeats back lower volume and repeat until u don't hear it. What's happening is the headset speaker is too loud and the other mic is picking it up at the top
Sent from my SAMSUNG-SGH-I727 using xda premium

defconoi said:
Call echo only happens with volume up all the way. If u put in call volume to medium-low it isn't noticeable. Call ur cell from a landline and blow into the mic on landline phone, if it repeats back lower volume and repeat until u don't hear it. What's happening is the headset speaker is too loud and the other mic is picking it up at the top
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
That may not be best for pple in the city with low call volume i know they would want to be able to actually hear the person outside you know

im a little scared to pull my phone apart too. I think i'll wait for a software fix

well i never dropped my phone but i do have that issue with ICS and GB!!! when im on ICS my friends says that there is an echo when im on GB they say they can hear me wierd, and when i take the case off they say its a little bit better. so i do think its a hardware issue!!
in the other hand my friend that works at tmobile says that he had heard this issue with all of tmobile phones not just this one

Thanks for the replies guys, good discussion on this topic so far.
I agree this is definitely a "macguyver" type fix, but hey if it works it works. I've been daily driving Racing's various ICS ports since the initial leak in SPITE of the caller echo issue (I just talked to everyone on speakerphone lol) so this is really welcome news to me.
As far as damaging your phone, IMHO hacking the phone and installing Rom's is just as potentially dangerous (if not more so) than taking out 6 tiny screws out and inserting a small piece of paper underneath the casing, but its everyones decision if they want to try or not.
I have verified with 4 different callers and tested myself that the fix works for me WITHOUT a case. When I put the D30 case back on my phone there is still echo. Not as bad as before, but its definitely there.
So rolling with no case is kinda annoying but I was thinking of getting an extended battery anyways so this just makes it easier

FWIW I tried this fix and still get call echo... Slightly reduced maybe but definitely still there.
Sent from my SGH-T989 using xda premium

c130pilot said:
FWIW I tried this fix and still get call echo... Slightly reduced maybe but definitely still there.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Interesting do you have a case on your T989? Are you on a GB rom or an ICS leak?
Did you use a business card or just a thin piece of paper? Sorry about all the questions just trying to get as much info as possible from people experiencing this issue.
I also ONLY had the call echo issue when I flashed an ICS rom (and I had the call echo on all 3 of them), however when I went back to STOCK Gingerbread it went away. So maybe this issue is part software/part hardware?
The ICS leaks were the first roms I ever flashed, so I'm interested to know if ANYONE has the call echo on STOCK Gingerbread? I'm thinking that something in ICS increases the gain or does something to either the NC microphone or the speaker somehow?

Happened only on ICS Roms with and without case. GB Roms are ok. Used a business card.
Sent from my SGH-T989 using xda premium

c130pilot said:
Happened only on ICS Roms with and without case. GB Roms are ok. Used a business card.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Bummer man sorry to hear
If it is a "little" bit better with the business card in there you could try to maybe fold it over and make it a bit thicker? If it helps even a little bit maybe there is some potential there to fix it?

where are the noise cancellation files in the ics leak?

my experience from today... i went back to 100% stuck and still had echo.. not as bad with an ics rom.. but my girlfriend had told me that she was hearing it so i took off the cover and she says that it was better. so i kept talking to her and then she said the she hears an echo again so i started to talk more into the mic.. and it was gone. so i do believe its a hardware issue and its when my mouth is not close enough to the mic is when others hear an echo.. ok then again i rooted the phone and flash ics megamix on it so i gave my phone to my girlfriend to see if i can hear an echo.. so when she was holding the phone correctly i didnt heard it but when she put the phone in her shoulder and to hold it there while she talks i hear the echo.. so tell me if this a software or hardware issue.. i think it have something to do with the surrounding and how laud you talk to the person

[Q] People Can’t hear owner when in a call

I purchased a Samsung Galaxy Note 3 about a month ago. Last week I began having a problem with the phone. When a call comes in, whether I make it or if its incoming, I can hear the person on the other end fine but they can’t hear me. I turned the volume all the way up and that hasn’t worked. It is not the area I’m in, because it has happened in different areas.
Do you have any solutions to this?

Wifi calling? Are you rooted and non stock?
Sent from my SM-N900T using Tapatalk

I had the same issue. I was never able to fixed or the tmobile store. We change the mic several times and nothing. So I got an ear blue tooth and forgot about it. If you put it on Speaker works perfectly.
Sent from my SM-N900T using Tapatalk

I had an issue that was similar, but not the same. When I was at home on wifi and answered calls, I could hear the caller but they couldn't hear me (said there was weird squeaking noise or something). Answering calls when not on wifi gave me no issues, but my apartment is a total dead-zone so I really need wifi calling.
I just fixed it today actually by doing two things: turning OFF power saving mode, and turning off the voice control that deals with answering calls and such. I'm not sure if just one or both of those steps were necessary, but wow, F power saving mode! I thought my phone was pretty fast before, but w/ power saving mode off it just absolutely blazes. I've had pretty awesome battery life on 4.3 Tweaked ROM w/ Saber kernel, so I don't think I'll mind a battery hit in exchange for the ridiculous performance I'm seeing.
Back to your problem, I've heard of people solving issues by cleaning the microphone with a toothpick or something. Are you able to use the mic for voice recording or voice commands or anything? If you're having a hardware problem with the mic, an exchange might be necessary.

jeaniturrizaga said:
I had the same issue. I was never able to fixed or the tmobile store. We change the mic several times and nothing. So I got an ear blue tooth and forgot about it. If you put it on Speaker works perfectly.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Thanks for your Info but I don't like using ear bluetooth all time. I want to another solution if you have. Thanks

Compusmurf said:
Wifi calling? Are you rooted and non stock?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Its happend all kind of calling. Yes I am rooted

If it's a hardware defect, you could get a replacement for that.

Lorettaa said:
If it's a hardware defect, you could get a replacement for that.
Click to expand...
Click to collapse
I think so. It should replace. Thanks