Related
Just a quick question for you guys. When I receive a phone call (full signal strength) and slide the slider accross to answer the phone there is a long pause of silence before the call actually connects. Has anyone else run into this situation?
Nexus One running stock Froyo (At&t)
yes I have this issue: I answer and cannot get an answer on the other end but I can hear them saying "hello". After a few seconds we connect and they say they never heard me say anything even though I was saying hello back.
I have two Nexus Ones: one answers calls perfectly and has great sound quality, while the other has this issue you describe, along with low call volume.
I think in my case it may be a hardware issue and I may need to send it in to be looked at. Both running on ATT although the good device is the tmobile version and the problem device is ATT 3G version.
Old MuckenMire said:
yes I have this issue: I answer and cannot get an answer on the other end but I can hear them saying "hello". After a few seconds we connect and they say they never heard me say anything even though I was saying hello back.
I have two Nexus Ones: one answers calls perfectly and has great sound quality, while the other has this issue you describe, along with low call volume.
I think in my case it may be a hardware issue and I may need to send it in to be looked at. Both running on ATT although the good device is the tmobile version and the problem device is ATT 3G version.
Click to expand...
Click to collapse
You think it is a hardware issue? I thought that it was like that across all N1s?
There was a thread here 1-2 weeks ago about the issue and pretty much EVERYBODY had this problem.
I can't find the thread anymore but it was about the delay between answering a call and the mic becoming active ... which takes 2-5 seconds.
I just noticed the other day that the delay seems to be less if I immediately put the call on speaker.
Never encountered that issue. The other side hears me immediately as I answer. I guess this is not "across all N1s", unless someone would think my N1 is special in some way (which it isn't, and so are all the other 7 N1s of my friends at work which also happen not to have this problem - and the call quality is great on at least 3 that I checked personally).
Instantly connects on my phone as well, so it's not on all devices at least. I have one of the first batches of T-Mobile N1's btw.
What carrier are you on?
this happens to me too.its so annoying. im on att
Can't find the thread but it was pretty long.
nexusdue said:
You think it is a hardware issue? I thought that it was like that across all N1s?
There was a thread here 1-2 weeks ago about the issue and pretty much EVERYBODY had this problem.
I can't find the thread anymore but it was about the delay between answering a call and the mic becoming active ... which takes 2-5 seconds.
I just noticed the other day that the delay seems to be less if I immediately put the call on speaker.
Click to expand...
Click to collapse
I'm not so sure anymore. I decided since my only choice was to send it in for repair, I might as well one click root and install CM6 and see what happens. So far, I have not had the issue. It's only been three days but that's the longest this device has ever gone without having the "no connect" issue. Also, my low call volume and speaker phone volume issues are now resolved. I now find myself turning the volume down rather than up. I'll update this thread with final verdict on whether this fixes my issue.
This sounds like an att problem not a nrsux one problem
I notice this problem as well. If I wait until the call timer appears on screen before I start to talk the other party doesn't seem to notice.
I'm on T MO and never had this issue. Try the one click root and flash a different ROM. If it doesn't work send it to HTC. I recently sent mine back on a Monday and it was back that Friday.
Sent from my Nexus One
Well my issue has been resolved by switching to CM6. It's been a week now and the issue has not occurred even one time. This was an issue that used to happen to me EVERY DAY, so I am very happy that in my case it turned out to be a software issue.
When I was running 2.1 I hoped 2.2 would fix it and when it didn't I thought for sure it must be hardware. It's so nice to KNOW I can answer the phone if it rings now. Sometimes I would get an important call and I was afraid to answer the damn phone!
Thank you Mr. Cyanogen, whoever you are.
I get this issue once in a while. I think its a software issue. Over time something gets hung up somewhere.
I had a thread like this as well..
http://forum.xda-developers.com/showthread.php?t=691399
For me it still happens randomly, stock 2.1 rom, stock 2.2 rom, Enom's ROM, etc...
Although I have a theory that I haven't tried to prove/disprove yet.. It seems like several times when this has happened I was holding my finger over the second mic on the back, which is naturually where my finger seems to lay when I hold the phone. Anyone else considered this? I'm thinking maybe it's throwing off the microphone trying to do noise cancellation?
khaytsus said:
I had a thread like this as well..
http://forum.xda-developers.com/showthread.php?t=691399
For me it still happens randomly, stock 2.1 rom, stock 2.2 rom, Enom's ROM, etc...
Although I have a theory that I haven't tried to prove/disprove yet.. It seems like several times when this has happened I was holding my finger over the second mic on the back, which is naturually where my finger seems to lay when I hold the phone. Anyone else considered this? I'm thinking maybe it's throwing off the microphone trying to do noise cancellation?
Click to expand...
Click to collapse
Definitely not the finger covering the mic. Just tried it with/without and same result.
There was another thread that was at least 3-4 pages of people complaining about it.
Sounds more like a network issue than a hardware issue, IMO
This issue has come up recently for me and it's really annoying. I'm not sure what triggered this problem...
Is anyone else experiencing this issue? Any ideas on how to resolve?
I've got the Rogers/AT&T N1.
I am a proud owner of Galaxy Note since a month ago, and I have problems with an echo on the call since than, althow I changed the firmware for many times. Now I use the XXKL7 version, and the problem persists. My mobile operator is Orange Romania, but I faced the same problem whith Vodafone.
Yes, I experience this problem as well - or rather, the people who call me have been complaining about echos.
I think this has something to do with the dual-microphone configuration.
My impressions:
The echo is experienced by the other party - not by the user of the Galaxy Note.
Echo is experienced only on normal cellular voice calls, not with other programs (e.g. Skype).
Phone cases aggravate the problem - the echo is very slightly audible when phone is used as is, but is terrible when a TPU case is attached to the back of the phone.
Echo is inaudible when phone is muted.
I use firmware, KK9.
This is obviously a problem that needs to be addressed by Samsung, but as a first aid I recommend you to remove your phone cover.
OK, looks like this is a well known problem, affecting both Galaxy Note and Galaxy S2.
Google it, you'll find a lot of discussions and various workarounds.
I still want to try the latest firmware KL7, see if issue is resolved.
I.m using the KL7 version, but the problem persists. Maybe the KL8 would solv my problem?? I.ve changed a lot of firmwares, I swiched all the Romanian SIMs operators, but the problem remained
I'll try to make this quick. When making phone calls with my Nexus 4, I'm experiencing two issues.
1) I sound choppy to the other person. For example, I'll be talking and I'll be going in and out. I've tested this with different callers and it's true for all of them. They all say I sound choppy.
or
2) Sometimes, neither of us will hear each other for a few seconds before sound returns. Like, I'll say something, and the other person will sound quiet, and I'll go "hello?" and they'll say "I said, oh okay." As if it didn't get the immediate response. The same thing happens vice versa, where I'll respond and they'll ask if I said anything cause they didn't get it.
Issue 2 happens a lot less. It's issue 1 that is driving me nuts.
Is anyone else experiencing this?
I'm on Tmobile and I've switched SIM cards twice, tested the network with my family's phone that are part of the same plan (perfect call quality, so I don't believe it's Tmobile), and I've had Google replace my phone. The RMA still has the same problem, so I'm reaching out to the forum to see if anyone else is experiencing this too, and more importantly, has a solution or at least know what's the culprit.
This only started happening with the Nexus 4. When I had my Galaxy Nexus on the same line and network, calls were fine.
I called Google a second time, and they could immediately hear what I was talking about. The choppiness was really bad, they said, and they insisted that it's hardware related (though I'm not convinced. Could I have gotten two defective Nexus 4's in a row? Possible, I suppose). They convinced me to give it one more go, and so I'm waiting for another RMA to arrive.
Any thoughts, help? I haven't been able to find much on the web about it.
Thanks.
If you got 2 defective Nexus 4s in a row it's either you are really unlucky or it's a signal related issue, like your signal could be weak causing choppiness, or maybe a problem with your carrier? I guess. You should probably try a 3rd time before looking for your carrier and asking them about the signal. Try moving your SIM card to another phone to see if it's the problem with the carrier. If it's ok on another phone, get it replaced a 3rd time I guess.
Good luck
So this is the second S5 I've had and same issue. First one, people could hear me if I called, but if they called me 90% of the time they couldn't hear me on the 1st call. If they called right back or I called them it was fine, usually. I've seen a lot of complaints about this on the S5 online. I even have a copy of the my youmail voicemail that I made on my S2 that was crystal clear and more louder/pronounced if that makes sense, and the voicemail I made on my S5 was all fuzzy and kinda garbled like I was talking 4 feet away from it. Replaced with another S5, and it started happening again except now I'm rooted so no more warranty and they can't/won't do anything. Stock or rom, it happens. So I know a few S5 owners, 3 of them have the same problem. All different networks so not specific to any provider (like if it were an at&t issue etc).
I tried clearing the pin hole at the bottom but didn't seem to make a difference. People think the S5 does this maybe b/c it's water resistant and theirs a membrane inside that hole for the mic that makes it garbled. Speaker phone it works fine. Just pissing me off, I love the phone otherwise, but this is my work phone as well and it's so nice and professional to keep playing phone tag with clients .
This doesn't make a lot of sense. You say that this is a well known, widespread problem that happens on various carriers. Which is hard to reconcile with the fact that I haven't heard of the issue and few people here or anywhere else are complaining of it? We have over 500 S5's deployed in my workplace and zero reports of this nature. XDA has 6 million members and we don't see a trickle, let along surge of reports here either.
This is highly unlikely to be a hardware issue or we would be hearing about it a lot. Likewise if the issue showed up with any frequency due to a specific firmware version. It's most likely user settings and you provided zero details about your configuration. Or I would have said a carrier issue, but you not only didn't tell us who your carrier was but you dismissed this out of hand saying that you see the problem all over, including three S5 owners that you know yourself using different carriers.
Making user settings, how you use the phone the most likely cause.
There isn't much to work with unless you provide detailed information about your configuration. How about some links to the frequent occurrences of this problem that you said you see all the time. Link us to a recording of a representative call where the problem occurs. And any information that might suggest or exclude patterns, e.g. what carrier you use, what carriers your other 3 friends use, what time of day does this happen. Does it happen only in fringe areas, only with strong signals, only with wifi calling, et cetera.
.
fffft said:
This doesn't make a lot of sense. You say that this is a well known, widespread problem that happens on various carriers. Which is hard to reconcile with the fact that I haven't heard of the issue and few people here or anywhere else are complaining of it? We have over 500 S5's deployed in my workplace and zero reports of this nature. XDA has 6 million members and we don't see a trickle, let along surge of reports here either.
This is highly unlikely to be a hardware issue or we would be hearing about it a lot. Likewise if the issue showed up with any frequency due to a specific firmware version. It's most likely user settings and you provided zero details about your configuration. Or I would have said a carrier issue, but you not only didn't tell us who your carrier was but you dismissed this out of hand saying that you see the problem all over, including three S5 owners that you know yourself using different carriers.
Making user settings, how you use the phone the most likely cause.
There isn't much to work with unless you provide detailed information about your configuration. How about some links to the frequent occurrences of this problem that you said you see all the time. Link us to a recording of a representative call where the problem occurs. And any information that might suggest or exclude patterns, e.g. what carrier you use, what carriers your other 3 friends use, what time of day does this happen. Does it happen only in fringe areas, only with strong signals, only with wifi calling, et cetera.
.
Click to expand...
Click to collapse
Pry exaggerated as a bit frustrated. Away for business and on phone right now. I just googled various call issues and saw same/similar on other phones, quite a few S4 reports (like googling S5 can't hear me, or can't hear calls, or android can't hear calls etc). Again not exactly the same but similar, found older Android phones people talking about the same. S5 people I saw post in various threads on different forums, not necessarily made a thread of theirs (like they found an issue like that and bumped thread even if it was a different phone). I'm on AT&T, 3 friends one is T-Mobile and others are Verizon. Though theirs isn't near as bad as mine, theirs happens infrequently on both ends which makes me think maybe carrier related, whereas mine is almost always the caller on my end not hearing me well on the first call. I have two employees with S5s as well and no issues with theirs like this.
I don't know what user config info you want? I've rooted and flashed android for years, I hardly ever touch anything volume/call mod related. I don't know what settings you'd be talking about, stock or rom is the same (didn't install viper, didn't do anything with volume controls on DK as their borked on this version etc). Changed background noise on/off but didn't do anything.Not sure how I use the phone would do anything, they call, I answer, I call, they answer? Happens anywhere no matter signal, whether full bars at house, or office, or lose a few bars when traveling, time of day doesn't matter happens anytime. I just had a conference call where I ended having to use speaker phone for them to hear better but they still said it wasn't clear. Wife just called me and she said through the phone or speaker it's like I'm talking through a towel (speaker not as bad). My AT&T store said they've had a few people come in with complaints of call issues on their S5 but in various ways, and sometimes a factory reset worked, sometimes not. Which didn't work for me, and I blew a canister of air and use a small pin like some said they did to see if anything was clogged in the Mic port but no difference.
I'll be back in a bit, but I could try to record a call with my wife. And I'll upload the files from youmail voicemail where you can hear how loud/pronounced and clear my message is from my S2, and the garbled message from both S5's.
Think I fixed it, let's hope. So I went into safestrap, tried a few things, fix permissions etc. No difference. Restored a few times, no difference, did 3 factory resets, no difference. Each time I either message someone to call me to test, or I logged into youmail to record a new greeting and heard it fuzzy/garbly. Did one more factory reset, msg'd wife to call again, she called and first thing she said was omg it's way louder and cleaner sounding like I'm not muffled. I logged into youmail, did a new greeting and yup it's 100% normal sounding. So no clue why this worked all of a sudden with all my other tries today and before. My first S5 they tested at the AT&T store and it luckily did the issue there so they could hear what I meant and note it. They gave me a loaner and it was sent in, and I guess luckily it was reproducing that same issue when it was checked as they did a replacement since the phone was only 2 months old. And now that I think about it I doubt the tech or whomever was checking it out sat there and did multiple restores/resets like I did, and I guess I was really lucky they didn't get it and test only to have it operate normal like the 10% of the time or whatever it did.
Being rooted now sending in was pointless, as knowing people over the years that have even if sent with stock rom, warranty was denied. F'd up thing is they have to prove rooting caused the issue, I don't have the time nor want to deal with that crap. Example I love cars/trucks and mod everything we have, and with the Magnuson-Moss Act they have to prove your "mod" directly affected the failed part/problem. In the phone world you end up just getting transferred around and dealing with crap trying to sort that out. I have one of my cars modded (ctsv) with pulley swap, full exhaust with lt headers etc, custom tune yada yada, one of my trucks has custom tune/intake/headers/no cats/custom exhaust etc and neither had problems with getting warranty work done, b/c doing a custom tune and pulley etc isn't going to make your radio or nav fail. In the phone world on the other hand they'll tell you to pound sand, root and mic fails, oh that'll be our diagnostic fee part replacement $ have a nice day. lol
i'll try to upload audio files from youmail showing the sound quality difference when I get a chance. I know one of my friends tried a factory reset and didn't work. Guess I'll tell him and the other two to keep doing resets over and over till it works lol, whether that means 5 or 10 times. Why it didn't work on the 1st or even 2nd try is beyond me
I have been having an issue with people having trouble hearing me or saying that I am breaking up while on a phone call. This issue started after the latest update which came out about 2 weeks ago. I think it was a security update.
When on a phone call where people are having trouble hearing me, I can either put a headset on or put it through the speaker then the person on the call can hear me normally. I have tried a factory reset, deleting the cache, removing the sim card and put it back in but nothing has fixed my issue.
I do not think that it is a signal problem because of what I said about having no issues if I am using a headset or the speaker phone. Also, I have ruled out a mic problem by taking a video and talking normally then playing the video back. When playing the video back, I can hear myself without a problem (this suggestion was made the Huawei itself).
Does anyone anyone know what is going on? Or is having similar issues? I really don't want to be without a phone if I have to RMA my phone. Huawei's customer service said that they would not send a replacement phone prior to them receiving the RMA (if there is an issue with the phone of course).
I am on the Verizon network. Any suggestions is welcomed. Thank you.
I too am on Verizon and seem to have call quality degraded in the past month. I have no idea why. I live in southern Md.
Same here. Thought it was my case as it started about the same time i got the case. I'm in Central Florida, in a good coverage area. Phone was fine until last update. Now having bluetooth issues and this call issue.
Maybe this is just the noise cancelling mic issue that so many reported when it first came out? I may try to root and turn off the mic as suggested to see if its better, unless one of you guys are rooted and have done that already?
Can I roll back to pre-may update somehow?
yes
I too am
I'm still having the muffled / echo voice issues - putting my finger over the noise cancelling mic seems to "fix" it for me but I'm desperate for a proper fix - otherwise I can see myself jacking in the 6P for another phone soon
Hepperz said:
I'm still having the muffled / echo voice issues - putting my finger over the noise cancelling mic seems to "fix" it for me but I'm desperate for a proper fix - otherwise I can see myself jacking in the 6P for another phone soon
Click to expand...
Click to collapse
Have you tried (or are you) root and disable the noise cancelling mic? Think I may go this route if it continues (which I expect it will)
Unfortunately I use my phone for work, and the software will disable if it detects the phone is rooted - so that's a no go for me.
I had some issues with mine on Verizon. Turning off Enhanced 4G LTE Mode in cellular networks fixed my problems.
shiftr182 said:
I had some issues with mine on Verizon. Turning off Enhanced 4G LTE Mode in cellular networks fixed my problems.
Click to expand...
Click to collapse
Same for me
Sent from my SM-T320 using Tapatalk
Turning on enhanced Lte fixed my call quality issue actually, I had the same breaking up issue with it off. I still have the noise cancellation issue where people can't hear me unless I'm talking right next to the mouth piece though. Did you try wiping your cache partition in the boot up menu?
Wow, no issues for me from the latest update at all. I am in a crappy reception area so needed to turn off enhanced 4g when I got the device about 4 months ago but it's been nothing but great with VZW despite crappy reception.
Hepperz said:
Unfortunately I use my phone for work, and the software will disable if it detects the phone is rooted - so that's a no go for me.
Click to expand...
Click to collapse
Using root cloak is an option.
Had issues again last night. Seems when there is any background noise is when the issue presents itself. I'd venture to say this isn't just with VZW. I was able to stop it by placing my finger over the noise cancelling mic on the back of the phone. Guess its time to root and disable it...ugh
See the 800 and counting posts on the Google Help forum. Search "Muffled Voice 6P" and you'll see what I'm talking about. Basically, a bunch of these phones don't work as phones, and Huawei either doesn't want to pay to fix all of them, or more likely, doesn't know how to fix them. The problem with Chinese companies is the same problem Mao had back during the Great Leap Forward. He demanded enough grain to beat Great Britain, the demand was unrealistic so all of his lieutenants made up fictitious yield reports, and they spent all of their budget on farm tools and farm labor, and not enough on train cars to take the grain into town, and a ton of people starved to death as a result! I'm sure something similar to this happened at Huawei: "Boss, the call quality on this 6p is absolutely stupendous". "Well done vice president, here's your bonus". Sales of Huawei 1-2 years later: not up but way, way down. Layoffs. People hungry again...