Related
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
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
Having a very strange problem with my S3. I've noticed it at home more than anywhere else but basically what happens is that if someone calls me, the phone doesn't ring on my end but I do get a voicemail notification after they've left a message. Then when I talk to them, they tell me that on their end my phone rang once or twice and then went straight to voicemail. And my phone doesn't show any missed calls so obviously, my phone never detected that there was an incoming call.
BTW, it doesn't happen all the time. Sometimes the calls come in just fine.
I've checked my signal strength and it's always between 3 and 5 bars. I've missed more calls than I can count because of this. Some of them were important calls.
And I don't have any problem making outgoing calls or using the data connection for anything.
Any idea what's going on?
BonesHopkins said:
Having a very strange problem with my S3. I've noticed it at home more than anywhere else but basically what happens is that if someone calls me, the phone doesn't ring on my end but I do get a voicemail notification after they've left a message. Then when I talk to them, they tell me that on their end my phone rang once or twice and then went straight to voicemail. And my phone doesn't show any missed calls so obviously, my phone never detected that there was an incoming call.
BTW, it doesn't happen all the time. Sometimes the calls come in just fine.
I've checked my signal strength and it's always between 3 and 5 bars. I've missed more calls than I can count because of this. Some of them were important calls.
And I don't have any problem making outgoing calls or using the data connection for anything.
Any idea what's going on?
Click to expand...
Click to collapse
Is it just certain contacts? You may have them set to go directly to voicemail by accident. I can't find where the list is in the phone though ahah, I can see how to add them to reject list though.
EDIT: Found it go to dial-pad and hit menu and then call settings and you will see call rejection see if you have anyone in there.
Halmo said:
Is it just certain contacts? You may have them set to go directly to voicemail by accident. I can't find where the list is in the phone though ahah, I can see how to add them to reject list though.
EDIT: Found it go to dial-pad and hit menu and then call settings and you will see call rejection see if you have anyone in there.
Click to expand...
Click to collapse
Nope, has nothing to do with who's calling. Sometimes a call from the same person will come through but ten minutes earlier it didn't.
Ive had similar problems in the past. Turned out the phone signal was going up and down. When it was up, calls came through. And down, well duh. Either way, try a new radio. Maybe it'll hold a signal better. I've heard people complaining about H1, but cant say either way myself. Just a suggestion.
Ends said:
Ive had similar problems in the past. Turned out the phone signal was going up and down. When it was up, calls came through. And down, well duh. Either way, try a new radio. Maybe it'll hold a signal better. I've heard people complaining about H1, but cant say either way myself. Just a suggestion.
Click to expand...
Click to collapse
how can I try a new radio?
BonesHopkins said:
how can I try a new radio?
Click to expand...
Click to collapse
there's a thread in development. some people call em modems, but its the same thing. Choice of 3 i think.
Having the exact same issue is your phone always in lte while this happens?
Sent from my htc_jewel
Andrew149 said:
Having the exact same issue is your phone always in lte while this happens?
Sent from my htc_jewel
Click to expand...
Click to collapse
As far as I can tell.
stay away from LH1 modem it's trash....
BonesHopkins said:
As far as I can tell.
Click to expand...
Click to collapse
Same here
Sent from my htc_jewel
BNaughty said:
stay away from LH1 modem it's trash....
Click to expand...
Click to collapse
My baseband version is UCLG1.
btw, I never had this problem with my iphone 3GS which I had for almost 3 years.
I have to say that even though on paper the S3 blows the iphone out of the water, for pure functionality without problems, the iphone is definitely way ahead of the S3. I'm pretty much stuck with it for the next two years but I have a feeling that if things stay more or less the same in the cellphone market, I'll probably be switching back to iphones after my contract is up. The S3 is very cool but I've just had way too many problems with it that I never had with my iphone. My iphone just..........worked. With my S3 calls don't come through, I'm constantly having to force stop apps so my battery doesn't drain all the time (and even then, half the time the battery drains like crazy no matter what), the visual voicemail is sketchy as hell and doesn't work right half the time, the data connection even when it shows a strong LTE signal is often very slow and times out a lot, and a bunch of other misc. annoyances that I never had with the iphone. I wouldn't say I'm sorry that I bought the phone because I wanted to try out the latest and greatest but when my friends and coworkers have asked me about it, I've been telling them they'll be better of waiting for the iphone 5. Sorry to vent but overall, after having it for almost two months, I've concluded that I'm very disappointed with this phone. Sure, I can do things with it that I couldn't do with the iphone but f*ck me, at least with the iphone I could do basic sh!t like receive phone calls and check my email without the connection timing out all the time.
BonesHopkins said:
My baseband version is UCLG1.
btw, I never had this problem with my iphone 3GS which I had for almost 3 years.
I have to say that even though on paper the S3 blows the iphone out of the water, for pure functionality without problems, the iphone is definitely way ahead of the S3. I'm pretty much stuck with it for the next two years but I have a feeling that if things stay more or less the same in the cellphone market, I'll probably be switching back to iphones after my contract is up. The S3 is very cool but I've just had way too many problems with it that I never had with my iphone. My iphone just..........worked. With my S3 calls don't come through, I'm constantly having to force stop apps so my battery doesn't drain all the time (and even then, half the time the battery drains like crazy no matter what), the visual voicemail is sketchy as hell and doesn't work right half the time, the data connection even when it shows a strong LTE signal is often very slow and times out a lot, and a bunch of other misc. annoyances that I never had with the iphone. I wouldn't say I'm sorry that I bought the phone because I wanted to try out the latest and greatest but when my friends and coworkers have asked me about it, I've been telling them they'll be better of waiting for the iphone 5. Sorry to vent but overall, after having it for almost two months, I've concluded that I'm very disappointed with this phone. Sure, I can do things with it that I couldn't do with the iphone but f*ck me, at least with the iphone I could do basic sh!t like receive phone calls and check my email without the connection timing out all the time.
Click to expand...
Click to collapse
All of the issues you listed are not really S3 specific because I have had none of them and have had my phone since release. Apart from the video voicemail which I can't comment on because I have never used.
BonesHopkins said:
My baseband version is UCLG1.
btw, I never had this problem with my iphone 3GS which I had for almost 3 years.
.
Click to expand...
Click to collapse
I've had my I747 since release in June and not experienced any of these issues. Over the years with Blackberrys and the Galaxies I found most problems result from variances in the network. Signal strength, carrier software and even where the phone is in the house. I dislike much about the iPhone (I do have a 4th gen iPod) and much prefer the openness of the Android OS and NO iTunes. Hope things with S3 get better for you.
Still having the problem. It seems to happen most often when I have LTE enabled. I disabled it using the method mentioned in another thread where you remove the sim then enter a code which takes you to the menu where you can choose what to use.
When I had LTE disabled, it didn't seem to miss as many calls. But when LTE is on, I miss a crapload of calls. I'd leave LTE off but for some reason it keeps re-enabling itself every few days so it's turning into a massive pain in the ass.
Any suggestions?
I have the same issue as you, but I'm on Wind Mobile. This issue happens intermittently anywhere between 1 to 2 days, my phone will stop being able to receive calls. It's very frustrating and Samsung is really no help. After two attempts on trying to "repair" my phone, they have failed each time. The only thing they did was they ran a "RF Test" and everything passed, they said. So they re-flash my phone with the same ROM - again and again.. I told them, "This is my second time sending it in, and you guys are redo'ing the same steps as the first repair. You don't need to be a rocket scientist to know this, but wouldn't you think when you send me back the phone - the issue is still going to be there?!" ... And sure enough, when I got the phone back, I was still unable to receive calls..
So I took matters into my own hands - I flashed it with a older release stock rom and I tested it for 2 weeks, and it was able to receive calls. When I flashed with the earlier release, it also flashed the baseband. Either way, I should not be prevented from using the up to date software! This is a Samsung issue but if you ever tried dealing with them over the phone, it's painful. They said they would send me a REFURB replacement - (believe me, I tried fighting for a brand new phone, since I paid for a brand new phone and this issue came straight out of the box - it's not even my fault to begin with!) it's been 3 weeks and I still don't see any phone replacement nor did I receive any mails from Samsung.
Btw, Galaxy S3 is the phone I have.
If you discover a permanent fix for this issue, please let me know. I've been searching but no luck.
Thanks!
UPDATE: it's been over a month and I still don't see any phone replacement nor did I receive any mails from Samsung. So I called Samsung today after a month and 2 weeks. They said my replacement have been cancelled. First they said it's approved and requested me to send in my receipt for the phone. I had done the the very moment I hung up the phone from when they told me my replacement was approved (that was over a month ago). They want me to sent it in again to Samsung so they can "test". This is just ridiculous and getting out of hand. Does ANYONE have a fix for this????
Other forums are saying this is a wide spread issue...
are u missing imei, or just the problem you descibe... try flashing the latest modem... maybe yell at it while it flashes...
Nope, just having the issue I described... IMEI is exist and is valid.
aftershocks said:
Nope, just having the issue I described... IMEI is exist and is valid.
Click to expand...
Click to collapse
There's some newer modems out you could try but it still sounds like hardware...
Not sent from your phone...
Sorry for the late entry here but I'm also having the issue. aftershocks, and anyone else having this issue, open battery stats - what does your "mobile network signal" bar look like? Mine is mostly tan except for when I make calls, which then it goes green. I also have an HTC One X (AT&T model) and the bar's mostly green on the HOX.
I've flashed back to the original modem (UCLEM) to see if that helps and I'll move forward from there if not. UCDLK3 was the modem I was originally on when I noticed the missed calls. Here's the thread with radios: http://forum.xda-developers.com/showthread.php?t=1831898.
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
The only problem that I have with this phone is that callers keep complaining that they can't hear me. It seems like its only an issue when I receive calls and not when I make the calls. The weird part is that people will complain that they can't hear me at all or they will say I sound like I am really far away. they are like " hello, hello, HELLO!!!" so out of frustration I will move the phone away from my face and be like WTF! The screen will then turn back on and as soon as I talk again people hear me again just fine. So it definitely seems like an issue with the software. I went and replaced the phone at Verizon and since got a new one and the problem STILL exists. Anyone else have this issue at all? It's beyond frustrating!
Case
Sent from my SM-N910V using Tapatalk
---------- Post added at 04:28 AM ---------- Previous post was at 04:27 AM ----------
Verizon note 4 have the mics in different locations. I had to drill a hole for mine. Look at the bottom of the phone and your cas2
Sent from my SM-N910V using Tapatalk
I don't have a case for my phone
Sent from my SM-N910V using XDA Free mobile app
Don't have this issue at all.
If you don't have a case, maybe bluetooth is connecting to something?
I'd start troubleshooting it, try with speaker, see if some app is taking over your mics, obviously your mic works since its only on incoming calls and you've replaced your phone already.
Try booting into safe mode and testing.
Does it happen everywhere? Or only when you're in a certain area? Make sure you're not accidently muting it somehow?
Do all your testing in safe mode so you'll know if it's app taking your mic.
|> transmitted from deep inside a Verizon Note 4 <|
kerimh40 said:
The only problem that I have with this phone is that callers keep complaining that they can't hear me. It seems like its only an issue when I receive calls and not when I make the calls. The weird part is that people will complain that they can't hear me at all or they will say I sound like I am really far away. they are like " hello, hello, HELLO!!!" so out of frustration I will move the phone away from my face and be like WTF! The screen will then turn back on and as soon as I talk again people hear me again just fine. So it definitely seems like an issue with the software. I went and replaced the phone at Verizon and since got a new one and the problem STILL exists. Anyone else have this issue at all? It's beyond frustrating!
Click to expand...
Click to collapse
Does the other person hear static? Or nothing at all? For me I can hear then but they hear static.
I've called verizon about this for the past 4 weeks and now they have me doing something every time it happens. After it happens I have to hang up and dial ### and then after it tells me its a wrong number, hang up.
Apparently this is to mark the calls that were bad so they can further diagnose the issue.
I've been through 2 note 4s already and I am actually about to exchange this one today because I'm having other issues on top of the caller issues.
I'd recommend calling verizon and complain about call quality issues and ask them to put you on the monitoring service so they can further diagnose the issue.
-Wizzle
Same Issue on T-Mobile
I've had my phone a few days and it's constantly doing this. I first noticed it while using headphones. Then, I noticed it while on speakerphone. Most of the time, the people on the other end can't hear me. However, once today, I couldn't hear the other line but they could hear me. SO frustrating, because I use my phone for work!