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

Garbled/Poor audio Phone Calls

In the last 2 days my wife and I have both noticed very poor audio on our calls. It sounds like a garbled voice on the other end, like a robot talking. I am on a custom ROM and she is stock. It is not every call either.
Nothing has changed on our end, and it doesn't matter if it is by Bluetooth or not.
It does not affect how the other person hears us, but only how we hear them. I am thinking it is a T-Mobile issue. We are located in Orlando.
Anyone having similar problems?
Any thoughts on a fix?
Thanks!

Markdental said:
In the last 2 days my wife and I have both noticed very poor audio on our calls. It sounds like a garbled voice on the other end, like a robot talking. I am on a custom ROM and she is stock. It is not every call either.
Nothing has changed on our end, and it doesn't matter if it is by Bluetooth or not.
It does not affect how the other person hears us, but only how we hear them. I am thinking it is a T-Mobile issue. We are located in Orlando.
Anyone having similar problems?
Any thoughts on a fix?
Thanks!
Click to expand...
Click to collapse
Could be your rom or kernel. Do a factory reset.

I thought it could be my ROM, but it's happening to my wife, and she is stock.
So, that's why it's so weird.

If it's happening to you both it's almost certainly an issue on T-Mobile's end. Much more likely than you both having the exact same problem that no one else ever seems to have.
Sent from my SGH-T999 using Tapatalk

[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

[Q]Earpiece Sound During Voice Calls

During a voice call on cellular or wifi calling doesn't matter which I am on I hear this odd noise that can overpower the conversation at times. Best way to explain it that it sounds like an electrical current in the background and it comes and goes. I have asked several of my friends/colleagues to see if they hear it and so far no one else does. I do have really good hearing so perhaps it's only me and the phone is fine and I just have to deal with it? Perhaps I'm hearing a certain frequency that others cannot hear? Anyways, if anyone has a similar experience please let me know. If it is a hardware defect I'll submit contact Google and get a RMA. If it's my own personal defect I'll just have to deal with it :silly:. Thanks for your responses in advanced!

zetsumeikuro said:
During a voice call on cellular or wifi calling doesn't matter which I am on I hear this odd noise that can overpower the conversation at times. Best way to explain it that it sounds like an electrical current in the background and it comes and goes. I have asked several of my friends/colleagues to see if they hear it and so far no one else does. I do have really good hearing so perhaps it's only me and the phone is fine and I just have to deal with it? Perhaps I'm hearing a certain frequency that others cannot hear? Anyways, if anyone has a similar experience please let me know. If it is a hardware defect I'll submit contact Google and get a RMA. If it's my own personal defect I'll just have to deal with it :silly:. Thanks for your responses in advanced!
Click to expand...
Click to collapse
Google phones usually have this issue... If this is the only problem do not change it, as whatever they are going to send it's going to have the same issue... Google phones have it since Nexus one

NICEGYPT said:
Google phones usually have this issue... If this is the only problem do not change it, as whatever they are going to send it's going to have the same issue... Google phones have it since Nexus one
Click to expand...
Click to collapse
Hmm I see thanks for the info. On my 2 XL there was the distortion/rattle at higher volumes for certain frequencies but was mostly fixed by repositioning the speakers grill but that's a different issue. I don't remember experiencing this on my 6 or 6p and OG Pixel .

I have this issue as well. I didn't have this issue when I used my Pixel 2 XL. I DID RMA mine. I also have a display distortion as well from the notch up.

Is this in general use, or is this while charging?

wtharp2 said:
Is this in general use, or is this while charging?
Click to expand...
Click to collapse
General usage regardless if it's on or off the charger. Nothing downloading in the background etc.

MLIGN said:
I have this issue as well. I didn't have this issue when I used my Pixel 2 XL. I DID RMA mine. I also have a display distortion as well from the notch up.
Click to expand...
Click to collapse
Hopefully it's just a few devices that have this problem. Please update when you get your RMA and let me know if the issues persists. Thanks!

I am getting the same thing. Its like a high frequency ticking - phone earpiece only. Bluetooth is clear and the Pixel buds are clear. I call it objectionable. Coming from OG Pixel XL with no sounds like this.
---------- Post added at 12:33 AM ---------- Previous post was at 12:24 AM ----------
bobbyricha said:
I am getting the same thing. Its like a high frequency ticking - phone earpiece only. Bluetooth is clear and the Pixel buds are clear. I call it objectionable. Coming from OG Pixel XL with no sounds like this.
Click to expand...
Click to collapse
I just noticed - by accident.
I placed another call to test, forgot bluetooth still connected. Put the phone to my ear to check. The ticking sound was at the earpiece on the phone and the audio was at the bluetooth earpiece on the desk. They were separate.
The call was clear on the bluetooth earpiece, but the sound on the phone earpiece was there, alone. It sounds like data noise on the phone earpiece during the call.
---------- Post added at 01:14 AM ---------- Previous post was at 12:33 AM ----------
MLIGN said:
I have this issue as well. I didn't have this issue when I used my Pixel 2 XL. I DID RMA mine. I also have a display distortion as well from the notch up.
Click to expand...
Click to collapse
What is a good path for RMA?

bobbyricha said:
I am getting the same thing. Its like a high frequency ticking - phone earpiece only. Bluetooth is clear and the Pixel buds are clear. I call it objectionable. Coming from OG Pixel XL with no sounds like this.
---------- Post added at 12:33 AM ---------- Previous post was at 12:24 AM ----------
I just noticed - by accident.
I placed another call to test, forgot bluetooth still connected. Put the phone to my ear to check. The ticking sound was at the earpiece on the phone and the audio was at the bluetooth earpiece on the desk. They were separate.
The call was clear on the bluetooth earpiece, but the sound on the phone earpiece was there, alone. It sounds like data noise on the phone earpiece during the call.
---------- Post added at 01:14 AM ---------- Previous post was at 12:33 AM ----------
What is a good path for RMA?
Click to expand...
Click to collapse
If it is indeed data noise then it could be a shielding issue and I'm not sure if that could be fixed with a software update. Did you buy your device from Google? If so I'm positive they will RMA for this issue.

zetsumeikuro said:
If it is indeed data noise then it could be a shielding issue and I'm not sure if that could be fixed with a software update. Did you buy your device from Google? If so I'm positive they will RMA for this issue.
Click to expand...
Click to collapse
It was from Google.

bobbyricha said:
It was from Google.
Click to expand...
Click to collapse
They will definitely RMA for the issue. Give them a call and report the issue.

Just wanted to chime in that I had the same issue on my brand new pixel 3. I would recommend that if this bothers you, you not RMA the phone but rather return it for a refund. I do not believe this is a defect isolated to a select few units but rather an electromagnetic interference issue inherent in the design. I had the same issue on my Nexus 4 and it was never fixed. My pixel one does not do this, so I will be keeping it until at least the next model refresh. Still, who knows; please post if an RMA fixes the problem. Also, many people may never notice it. But at this price point, I'm not going to deal with waiting it out. I'm too busy to be a beta tester for a multi-billion-dollar company.

I've only had three calls so far, but I have not had any issues. All three were clear, and there was no background noise at all. I was only using the mobile network, so I don't know if Wi-Fi calling has anything to do with it, but I noticed in settings right after setting the phone up Wi-Fi calling was enabled by default. I turned it off. Maybe check that setting, and change it to see if it makes any difference?

bobbyphoenix said:
I've only had three calls so far, but I have not had any issues. All three were clear, and there was no background noise at all. I was only using the mobile network, so I don't know if Wi-Fi calling has anything to do with it, but I noticed in settings right after setting the phone up Wi-Fi calling was enabled by default. I turned it off. Maybe check that setting, and change it to see if it makes any difference?
Click to expand...
Click to collapse
The issue we are describing happens via WiFi and mobile. It may be related to certain cellular bands or the wifi radio causing interference (I had a Nexus S that exhibited a similar issue on GSM 1900, but not AWS HSPA). I personally tested 2.4 and 5 GHz wifi calling, an AT&T sim, and a T-Mobile SIM using band 4 volte calling and band 2 hspa. All exhibited the noise. More likely, you simply are not noticing the noise, but it is present. If it doesn't bother you, or you can't notice it, enjoy the phone!
Again, if it does bother you, it is unlikely to ever be fixed. Return the phone for a refund while you can.

In preparation for contacting Google for RMA I reset the phone. I did not restore from backup. It was much better, if not gone. I reset again, this time restoring from the earlier Pixel 3 XL backup. Made 2 calls. Its like 10% of what it was last night.
So for me it is varying. Before the resets, the clicking was there and hard to miss. My wife answered my phone and mentioned it, and she doesn't notice those things. Now, with a reset and restored phone, it doesn't seem to be an issue. Makes no sense to me but I'll take it. I love the phone otherwise.
Time to get back on the search for any screen protector that does not suck!

Add me to the list. Getting faint electrical static noises once a call connects. Over cell modem and with wifi calling apps like Signal.

theslug said:
The issue we are describing happens via WiFi and mobile. It may be related to certain cellular bands or the wifi radio causing interference (I had a Nexus S that exhibited a similar issue on GSM 1900, but not AWS HSPA). I personally tested 2.4 and 5 GHz wifi calling, an AT&T sim, and a T-Mobile SIM using band 4 volte calling and band 2 hspa. All exhibited the noise. More likely, you simply are not noticing the noise, but it is present. If it doesn't bother you, or you can't notice it, enjoy the phone!
Again, if it does bother you, it is unlikely to ever be fixed. Return the phone for a refund while you can.
Click to expand...
Click to collapse
Yeah, sadly I don't think it will be fixed or addressed even on this premium flagship. Since with the XL 2 they never did anything to alleviate the speaker buzzing/rattling. The only fix for that was to preposition the grills yourself to reduce it. They granted a RMA for the problem so if the next unit has it and the screen etc is fine I guess it will just be a have to live with it deal.

Another one for the list. I am having the same issue. Mine is a Pixel 3 XL from Google. I think I may RMA it because it definitely is apparent and bothers me. I'm not a hardware engineer but why is this a continuing issue for these devices?

zetsumeikuro said:
During a voice call on cellular or wifi calling doesn't matter which I am on I hear this odd noise that can overpower the conversation at times. Best way to explain it that it sounds like an electrical current in the background and it comes and goes. I have asked several of my friends/colleagues to see if they hear it and so far no one else does. I do have really good hearing so perhaps it's only me and the phone is fine and I just have to deal with it? Perhaps I'm hearing a certain frequency that others cannot hear? Anyways, if anyone has a similar experience please let me know. If it is a hardware defect I'll submit contact Google and get a RMA. If it's my own personal defect I'll just have to deal with it :silly:. Thanks for your responses in advanced!
Click to expand...
Click to collapse
On Pixel 3 here, and it's the same behavior. It's hard to believe Google is having this problem 2 years in a row. Last year they were able to mitigate it somewhat with a patch... I doubt RMA will do anything because all seem to be the same.

For those who RMA'd let us know if the replacement is any better.