Database Info

[Q]Please Help! Microphone not working on incoming calls..

Hello, i need some serious help over here
What's the problem:
I own a galaxy 3 since June, a week ago i started noticing the internal mic wasn't working on some incoming calls.
Details:
First of all the problem began for no apparent reason (the phone works fine otherwise and no major updates / new apps were installed)
This started happening on the official froyo ROM which was an excuse for me to flash the Kyrillos 9.4 ROM (wiped all data / formatted sd card in the process). The problem still occurs on Kyrillos 9.4 ROM suggesting that this is not a ROM issue
I thought it was a hardware issue but the caller can hear me perfectly if i connect the headset or use the speaker Also the internal mic works fine on some incoming calls and ALL outgoing ones!
Upon further investigation i came upon 2 threads on other forums (unfortunately i can't post the urls as i am a new user, if needed pm me or search google for "Microphone not working on incoming calls") which point out that the same problem incurs on HTCs and XPERIAs. Also it happens on replacement phones (original unit shipped back after this problem), on different providers, on official and custom ROMs, on clean phones (only the stock apps installed).
This seems to happen when the phone is idle for a set period of time (unconfirmed). Fast Reboot app / manual reboot / removing battery don't fix this, however making an outgoing call seems to enable the internal mic temporarily (even if the outgoing call never connects)
When this happens apart from the mic not working on incoming calls it becomes also unresponsive for other apps (Tape-a-Talk, Skype, Soundhound etc.)
Conclusion:
It seems to me that there is bug in froyo that keeps the incoming call code from activating the microphone or perhaps there is a conflict of sorts that keeps the microphone blocked. It is highly unprobable i think that the microphone would randomly start to fail on different android phones in the exact same way, so this shouldn't be a hardware issue.
Question:
Does anyone know/guess or can produce a possible solution for this? If not, could you please suggest further testing steps to help reproduce 100% this problem in an attempt to solve it?
Any help would be greatly appreciated as this is a pain in the neck for me (and others i guess?!)
PS: Excuse the thread form, i 'm really bored of writing / reading long posts
PS 2: This is my first post, hello xda community!

samsung vibrant
I have the same problem. I flashed the phone from android 2.1 TO cyanogen 2.3 and from it TO ice cream. I had this problem even to cyanogen and only in incoming call,never in other situation.
Googling I found same information but no solution. Anyone here knows something?

Anyway I found a stupid solution....try switching to 2g( I know that it's not a solution but...). It works for me!

that's ridiculous! how can network state have anything to do with the microphone of the device? can this be related to service providers maybe a more techish member could tell us.
anyway i am on 2g already as i don't have a usim card and this happens even if data network mode is deactivated. glad you found a way out but is it really a solution? i mean you have to ditch 3g for the phone to be actually a phone...
Since we seem to be the only ones among so many to be having this problem i am seriously thinking of taking back the phone for a replacement and hope for the best...

just an update, i lost functionallity of the microphone completely earlier today. That is with outgoing / incoming calls and any app i can think of, so i thought i 'd try changing the network data setting to 3g only since i was already on 2g...
WOW!!! that had an instant effect,it works seamlessly now,didn't even have to reboot.fingers crossed it will last.
that is one nasty and very strange bug. Please any of the developers could you take a closer look at this?
much appreciated
Sent from my GT-I5800 using XDA App

[Q] [NS4G] Bluetooth outgoing call issue

This happens only on outgoing calls on bluetooth (car audio): I can hear the person on other side talking, but that person cannot hear me. I switchover to handset or speakerphone and switch back to bluetooth, and the problem goes away. Both parties can hear each other and call proceeds without a problem.
This problem does not occur on incoming calls at all. I pick up using the button on car audio and the conversation happens without an issue.
The exact same issue occurs on all the builds I have tried: CM10.1 (both stable and nightly), Slimrom 4.2, Slimrom 4.3 nightly, Aditya's CM11 (tried at least 3 builds, currently running his build 12).
I did not see any mention of this by anybody else. Am I alone in facing this issue?
I have used both an android phone and a windows phone earlier on this car audio and this issue did not show up on those.
Thanks, folks. I would really love to fix this and continue to use this wonderful phone for a few more years!

It gets crazier
I just got my hands on a Sprint Galaxy Nexus (toroplus):
Weird: This exact issue (bluetooth outgoing call does not grab my side of the conversation until I switch the call to speaker/handset and back to bluetooth) happens on all the builds of CM10.2, CM11 and Slimkat.
Weirder: This DOES NOT happen on 4.3 stock rom (JWR67B) version of the software. I am unable to try and load stock rom to NS4G, so haven't tried this trick with that.
Weirdest: Now that I have isolated the problem to the CM (or its derivates in slim version), how is it even POSSIBLE that I am the only one experiencing this? I cannot find any mention of this issue anywhere in the net. Unfortunately, both my bluetooth receivers are the exact same model: pioneer DEH-4500BT. However, the fact that Galaxy nexus stock rom (and earlier phones, like Samsung Prevail or Lumia 521) work flawlessly deflects any suspicition on the DEH-4500BT's part.

[Q] Headset issue with Sebastian Kernel's ROM

Hi everyone,
this is my problem. I use almost always a very good quality headphones set (but without mic): obviously if I need to answer/make a call I have to talk into the phone's mic. Well, very often I'm not able to send my speech...I'm receiving very well, but the listener on the other side is not able to hear me, or at least he listen a very-very-very low sound. I did myself a test, calling me from an other mobile phone, and obviously I tried more than one headset.
I wrote "very often": actually, at the beginning after a reboot, this is not happening. It starts happening after a while, usually one hour after reboot: if you have a call, you are able to talk for 5 maybe 10 seconds, then there is the issue.
I thought it was a ROM bug (I was using Viper 3.1.4), then I tried Viper 5, then Elegancia, then Revelation...same problem... so I think it could be a kernel related bug ( @SebastianFM Kernel). Actually, no AOSP ROM has the same issue (Albinoman, Sultan, bilal, etc.).
Please, someone with these ROM can check if it is true?

Sorry for bumping it up. Anyone has experienced same issue? @SebastianFM, could it be ROM related issue, or I must search in a different place? Take in account that it happens only in ROM powered with your kernel...
pdbc said:
Hi everyone,
this is my problem. I use almost always a very good quality headphones set (but without mic): obviously if I need to answer/make a call I have to talk into the phone's mic. Well, very often I'm not able to send my speech...I'm receiving very well, but the listener on the other side is not able to hear me, or at least he listen a very-very-very low sound. I did myself a test, calling me from an other mobile phone, and obviously I tried more than one headset.
I wrote "very often": actually, at the beginning after a reboot, this is not happening. It starts happening after a while, usually one hour after reboot: if you have a call, you are able to talk for 5 maybe 10 seconds, then there is the issue.
I thought it was a ROM bug (I was using Viper 3.1.4), then I tried Viper 5, then Elegancia, then Revelation...same problem... so I think it could be a kernel related bug ( @SebastianFM Kernel). Actually, no AOSP ROM has the same issue (Albinoman, Sultan, bilal, etc.).
Please, someone with these ROM can check if it is true?
Click to expand...
Click to collapse

Problems with outgoing call quality

Recently I've been having a lot of intermittent issues with the quality of the calls on my oneplus one. People keep telling me they can't hear me well or they hear me voice all chopped up.
I hear people on the other side of the line flawlessly.
This seems to happen at no particular location. Even though at work my reception is really bad it also seems to happen while I'm driving.
For what it's worth, I can't recall one time that def told me one time when wifi but I wouldn't bet on this.
Currently running CM 12.1 nightly 20150504. Stock Kernel
Had anybody experienced this and had been able to solve it? Is pretty frustrating.

I am also facing same problem if any has solution
kindly help

Yes same problem for me. After reboot everything goes well for some time
Envoyé de mon A0001 en utilisant Tapatalk

I agree with all u. Even I am facing same issue. But Try ColorOS, MIUI, CM11. These ROMs gave me good network.
Problem is those are KK OS and most of the cases I am facing Google Services Keep Awake.
In LL, try Exodus, AICP. These 2 was good but not like the OS I have mentioned at top.

have you guys checked audio effects. See what have you checked off because I read that may be an issue. I also had a friend with the same problem and that solved it for him. He was on stock

I had the same problem following replacing a broken screen. Thought it was something I had done replacing the screen. The phone upgraded to 12.1-YOG4PAS1NO when I turned it on. Phone calls to some people were garbled at there end, call reception was good at my end. OK google worked, using the audio recorder App worked perfectly. I went to mobile network setting and changed preferred network type to LTE (recommend) and clear call quality has returned for three numbers that I tested it on. Not sure why that network type had changed. Not sure if this is just a coincidence. Will test further during the weekend.

I found somewhere that suggested it was something wrong with the noise cancelation and of you put your finger over the microphone on the back by the camera it should help. Haven't tried covering the mic yet, but noticed that if I'm somewhere a little louder then I don't have issues and when I am somewhere quiet I tend to get complaints, which leads me to believe it is something to do with the noise cancelation
---------- Post added at 05:10 AM ---------- Previous post was at 04:58 AM ----------
Also just found where it suggests disabling "OK Google" from any screen feature. Just disabled it and waiting for someone to call me

I, I desactivated OK google on every screen; after that the sound was perfect on all my outgoing calls

"Ok Google" deactivation from every screen solved the problem for me. Check this out - http://forums.androidcentral.com/lg-g3/504150-call-quality-has-suddenly-tanked-2.html this is where I got the clue to do this.

I had the same problem and indeed this seem to have solved it! So far so good...

I used this fix and according to a few people they have no issues hearing me anymore. And I also still have Google Now on all screens, so that's nice.

Other side in calls can barely hear me in most calls

Hey guys,
since amazon is out of stock - and therefore, getting a replacement device is kind of difficult - and I'm still waiting for oneplus to respond, I'd like to hear from you if you encountered similar issues with your OP6:
During calls, I can hear the other side just fine, but the person on the other side can not hear me most of the time. Sometimes, it seems some shreds of voice are being transmitted. It happened on about 90% of calls. There are calls that are perfectly fine, but most of the time, the phone is unusable.
What I could test so far:
- it happens in handset mode, speakerphone and with a bluetooth headset
- it happens on both SIMs, swapping them does not change anything
- it happens on 2G as well as 3G (no VoLTE available yet)
- the microphone works fine if I use the audio recorder (outside of calls)
- calls made via VoIP-software seem not to be affected, though audio quality on the other side isn't that great either (but that might be unrelated)
- sometimes, it seems to happen mid-call
Both SIMs did obviously work fine in my previous device (OP3), signal strength in calls is about -70dBm, both SIMs are on T-Mobile (Germany).
I'm on an A6003 with OOS 5.1.5, Baseband is MPSS.AT.4.0.c2.10-00012-SDM845_GEN_PACK-1.147963.5, bootloader is unlocked and rooted with Magisk.
I did find a thread describing similiar issues on the oneplus-forums (https://forums.oneplus.com/threads/dual-sim-issues.838595/#post-18474985), but I'm currently unable to login to their forums, for whatever reason.
Can any of you guys give me a hint on what to test to narrow down if it's a hardware or a software issue or maybe even suggest a workaround?
I'm happy to provide more details where necessary.
I'll probably have to switch back to my OP3 anyway, so I could give the Android P beta a shot and see if it happens there as well.
Best Regards.

So, it turns out (*after* factory resetting and flashing Android P of course ><) that the echo test number I've been using is equally broken on otherwise working phones, so most of my test results are null and void. I'll give it some more testing...

Just a heads-up for users who may stumble upon this thread in the future: call quality problems are mostly gone after updating to 5.1.6 (and replacing SIM-cards).

I've bought a OP6 just three days ago and I've updated it immediately to OS 5.1.8 (I've also rooted it) and the phone calls problems (call drops and other person can't hear my voice sometimes) are present.
I hope OnePlus will fix the issues not so later...

Unfortunately, I can't rule out that replacing the SIM-cards actually fixed the issue - it might be worth a shot. I haven't had any issues since my last post.