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

Sleep problem

Hello,
I have one problem with my Sensation, and it exist on all ROM but I'm currently at this ROM. Sometimes, when my phone is at sleep, if someone is calling me, after answer I dont hear anything (caller hear me or not) and after few seconds it writes me on display that I have missed call from that person. After that everything works perfect. I can receive calls or dial without any problem. Everytime, when problem occurs, phone was at sleep ad call wake him up.
I use laster firmware. Is there any solution for this? Is this known problem for sensations? I bought it 2 years ago, maybe it his time to go drawer
I like my phone but this is so annoying. I use ARHD, DarkForest and this ROM and it happen on every. But it's maybe relevant with last firmware upgrade.

panda1986 said:
Hello,
I have one problem with my Sensation, and it exist on all ROM but I'm currently at this ROM. Sometimes, when my phone is at sleep, if someone is calling me, after answer I dont hear anything (caller hear me or not) and after few seconds it writes me on display that I have missed call from that person. After that everything works perfect. I can receive calls or dial without any problem. Everytime, when problem occurs, phone was at sleep ad call wake him up.
I use laster firmware. Is there any solution for this? Is this known problem for sensations? I bought it 2 years ago, maybe it his time to go drawer
I like my phone but this is so annoying. I use ARHD, DarkForest and this ROM and it happen on every. But it's maybe relevant with last firmware upgrade.
Click to expand...
Click to collapse
What do you mean by "This ROM"? You didn't specify which one is it.
Anyway, did you change the phone's maximum screen off CPU frequency? You can try changing it in System Tuner to 384Mhz, it might help (or maybe even a bit higher).

astar26 said:
What do you mean by "This ROM"? You didn't specify which one is it.
Anyway, did you change the phone's maximum screen off CPU frequency? You can try changing it in System Tuner to 384Mhz, it might help (or maybe even a bit higher).
Click to expand...
Click to collapse
Sry, I write this in ROM topic too and copied Is try every rom and everything was the same.
I will try with changing frequency

[Q] Bluetooth handsfree problem

I have a Sony bluetooth head unit in my car which supports handfree and audio streaming profiles. I can play my music through the head unit just fine via bluetooth. I can also make and receive calls without problem when I am listening to the radio (ie when I am not listening to my own music). However, when I am playing my own tunes and I either make or receive a call, the head unit indicates I am on a call, it mutes the music but I just get silence through the speakers.
I used to have a Galaxy S Advance and it all worked just fine without too much configuration on the phone or head unit; basically just pair them up, make sure the right boxes are ticked in the bluetooth options and thats it.
Any idea what the problem could be? I've tried an upgrade to 4.2.2 but it didn't help...

Hi,
I have a similar problem. I can pair my s2 plus with cm11 from this thread to my car kit (Parrot MKi 9200). Playing music via phone on the car speakers works fine but when I place a call the receiving phone just gets loud static (and my voice very very silent).
I wanted to ask the developer of the cm11 I am using if he sees a way to exchange the bluetooth module (or what androis equivalent is) to the one of e.g. Android 4.1.2 because I know that one works perfectly. I am posting here because I havent reached 10 posts yet.
Of course I am open to other workarounds and ideas.
Thanks,
Kiesel

Bluetooth
Same issue here,
everything (music etc.) is okay, but the phone connection.
I'm connecting to my Ford Sync.
I can connect, but then the quality of the voice is very very bad, I can hardly understand anything...
I thing there's a configuration file in the etc/ folder, maybe that need some upgrade?!?
Hope someone can help, because I really like to keep CM11 on my phone...
Dan

This is a known problem wich has been asked 100 times before
Sent from my GT-I9105P using xda app-developers app

safariking said:
This is a known problem wich has been asked 100 times before
Sent from my GT-I9105P using xda app-developers app
Click to expand...
Click to collapse
How is this message supposed to be of any help? Of course we know that. We have seen a lot of threads. I have read the whole bug report including all the comments on googlegroups, I have browsed dozens of websites and googled my ass of. What I didnt find was an explanation (at this point I dont expect to find a fast solution anymore). After reading the googlegroups bug call I thought it was a problem with the bluetooth stack that apparently is being redeveloped by google. But here cooldevelopment said it isnt a google problem.
I fully understand that it must be annoying for you to see this question a million times but please understand, that it is also annoying (and unsatisfactory) to not know whats going on.

DeKiesel said:
How is this message supposed to be of any help? Of course we know that. We have seen a lot of threads. I have read the whole bug report including all the comments on googlegroups, I have browsed dozens of websites and googled my ass of. What I didnt find was an explanation (at this point I dont expect to find a fast solution anymore). After reading the googlegroups bug call I thought it was a problem with the bluetooth stack that apparently is being redeveloped by google. But here cooldevelopment said it isnt a google problem.
I fully understand that it must be annoying for you to see this question a million times but please understand, that it is also annoying (and unsatisfactory) to not know whats going on.
Click to expand...
Click to collapse
I know what you mean but i think the best method now is to wait until cooldev find a solution to this

As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?

kidmanis said:
As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?
Click to expand...
Click to collapse
Hmm, interesting. I will try this out as well. Might probably be a week though, I am leaving for holidays tonight and cant risk making my phone unusable. Maybe somebody else is willing to give it a try?

kidmanis said:
As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?
Click to expand...
Click to collapse
Thanks now i know where to search the problem.

Hi,
here is a logcat of a bluetooth connection during a call on stock rom/stock kernel.
What I did:
-start logcat
-start bluetooth
-chose a contact
-call contact-
-talk for a minute
-hang up
-stop logcat
I then wanted to flash the mosh kernel and do the same again but the last time I checked there wasnt this huge plethora of different kernels to choose from. Very impressive work!
Could you tell me which one you would like me to flash and I would then redo everything?

Hi,
I tried installing mosh kernel 1.8 and 1.85 (for stock, init.d enabled) on sazy rom but it didnt boot. It stayed at the very first screen you get when you turn the phone on. I then installed your cm11 build8, connected via bluetooth to my car and had someone call me.
Attached is the logcat.
Do I need the samsung stock rom for mosh kernel? I thought sazy rom was a stock rom?

Mic not working during call

I've been experiencing a very frustrating issues where the mic is not working during phone call. I can hear the the other person but they cannot hear me, and if they can it's very very low, so low that they can't make out what I'm saying.
However, the microphone does work again if I go to speaker-phone mode. So i know the Mic itself is working (sound recorder works also).
I think somehow the phone thinks a headset is plugged in and disable the mic unless I'm on speaker-phone mode.
I don't think it is a ROM issues as I have tried a large number of different ROMS, including flashing stock OPO image. None worked.
If anyone know a solution to this issue please help me out. It's very frustrating that I can't make phone calls and have to turn on speaker-phone or use a headset.

Try a different Kernel, had the problem with my 3 different Headsets, i tryed the same ROM with some different Kernels and with the AK Kernel everything worked fine...not with the Furnace! Also try to flash UKM over a Custom Kernel. Check out the AK Kernel there you can find everything you need. If you have done everything right as in the "manual" open up Synapse...there is a point called "Sound", there you can find the point "Microphone", volume it up and try again. if its still not working make a full wipe that your device loses all data and reinstall the original CyanogenMod 11s with this tool here or any tool you want!
http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418
If its still not working delete again everything with the tool, install the CM11s with this tool again, install the CWM Recovery, flash the crDroid Rom (best ROM and everything works for me!), flash GAPPS, flash AK Kernel and last flash UKM!
This is my current setup and everything is working
ROM: http://forum.xda-developers.com/oneplus-one/development/rom-crdroid-v1-t2827599
Kernel: http://forum.xda-developers.com/oneplus-one/orig-development/kernel-ak-t2832168
Recovery: http://forum.xda-developers.com/showthread.php?t=2780894
UKM: http://forum.xda-developers.com/attachment.php?attachmentid=2913442&d=1409088319
Let me know if it worked

EasyGoingXD said:
Try a different Kernel, had the problem with my 3 different Headsets, i tryed the same ROM with some different Kernels and with the AK Kernel everything worked fine...not with the Furnace! Also try to flash UKM over a Custom Kernel. Check out the AK Kernel there you can find everything you need. If you have done everything right as in the "manual" open up Synapse...there is a point called "Sound", there you can find the point "Microphone", volume it up and try again. if its still not working make a full wipe that your device loses all data and reinstall the original CyanogenMod 11s with this tool here or any tool you want!
http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418
If its still not working delete again everything with the tool, install the CM11s with this tool again, install the CWM Recovery, flash the crDroid Rom (best ROM and everything works for me!), flash GAPPS, flash AK Kernel and last flash UKM!
This is my current setup and everything is working
ROM: http://forum.xda-developers.com/oneplus-one/development/rom-crdroid-v1-t2827599
Kernel: http://forum.xda-developers.com/oneplus-one/orig-development/kernel-ak-t2832168
Recovery: http://forum.xda-developers.com/showthread.php?t=2780894
UKM: http://forum.xda-developers.com/attachment.php?attachmentid=2913442&d=1409088319
Let me know if it worked
Click to expand...
Click to collapse
No luck here. : /
I've tried everything from flashing different ROMs to flashing different kernel. I even went back to factory reset, lock/unlock bootloader to wipe device. None of that work. Very frustrating. I'm starting to think it's a hardware issues, since trying out that many ROMs didn't help at all.

Did you informed oneplus already?

EasyGoingXD said:
Did you informed oneplus already?
Click to expand...
Click to collapse
Yep, filed a support/warranty request. But god knows how long it'll take for them to get back to me. There's no phone number support or anything. : /

neyurt said:
I've been experiencing a very frustrating issues where the mic is not working during phone call. I can hear the the other person but they cannot hear me, and if they can it's very very low, so low that they can't make out what I'm saying.
However, the microphone does work again if I go to speaker-phone mode. So i know the Mic itself is working (sound recorder works also).
I think somehow the phone thinks a headset is plugged in and disable the mic unless I'm on speaker-phone mode.
I don't think it is a ROM issues as I have tried a large number of different ROMS, including flashing stock OPO image. None worked.
If anyone know a solution to this issue please help me out. It's very frustrating that I can't make phone calls and have to turn on speaker-phone or use a headset.
Click to expand...
Click to collapse
Hi,
unfortunately I have the same problem. I've tried to fix it even modifying the system/etc/mixer_paths.xml but nothing works (http://forum.xda-developers.com/one...icrophone-ok-google-low-t2805568/post53914918). I noticed when that changing the values of hph-mic and anc-mic to 0, then handsfree mode doesn't work neither. Therefore we have clues to think the main mic is which has the problem.
Curiosly, I do not have had this issue out of the box, I think it began after 30O update. However I've downgraded to 25R and the issue remains.
I hope you the best luck
Regards

neyurt said:
I've been experiencing a very frustrating issues where the mic is not working during phone call. I can hear the the other person but they cannot hear me, and if they can it's very very low, so low that they can't make out what I'm saying.
However, the microphone does work again if I go to speaker-phone mode. So i know the Mic itself is working (sound recorder works also).
I think somehow the phone thinks a headset is plugged in and disable the mic unless I'm on speaker-phone mode.
I don't think it is a ROM issues as I have tried a large number of different ROMS, including flashing stock OPO image. None worked.
If anyone know a solution to this issue please help me out. It's very frustrating that I can't make phone calls and have to turn on speaker-phone or use a headset.
Click to expand...
Click to collapse
Cynogen 11s team is working to add support for CTIA headphones soon. See my post in similar thread (http://forum.xda-developers.com/showpost.php?p=55186894&postcount=25)

OK figured it out I uninstalled the latest hangouts update and made and received several calls all seems to be ok now

Is there any update regarding this issue? I still have this mic problem during calls and no clue on how to fix it.

OPO microphone problem is a hardware problem
Same problem here.
One morning main microphone in my OPO died - no one can hear me during call.
Recording sound with main mic gives some barely audible sounds.
tried reboot/factory defaults /root with fixing mixer paths - to no avail
The only solution is to call with speakerphone or bluetooth headset or normal headset.
Looks like hardware problem. Sadly OPO support sucks.

Jojo_1 said:
Same problem here.
One morning main microphone in my OPO died - no one can hear me during call.
Recording sound with main mic gives some barely audible sounds.
tried reboot/factory defaults /root with fixing mixer paths - to no avail
The only solution is to call with speakerphone or bluetooth headset or normal headset.
Looks like hardware problem. Sadly OPO support sucks.
Click to expand...
Click to collapse
I have a similar problem. Did you find a fix? I did everything. Restarted, ROM changed and everything!

As I wrote - no fix - IMHO it is a hardware fault. Still waiting for response from OPO support in hope for receiving RMA.

I am also thinking to return the phone because of this issue.

Just adding that I also have this problem - phone was working fine until yesterday.
Now mic is extremely quiet in call, unless I switch to speakerphone then it works fine (Video recording sound is fine also, but Google speech to text etc is not working)
I installed Swiftkey last night but I think its unrelated

Has anyone found any solutions for this problem yet?

Yes, I sold the phone!

:laugh:

L1ndon said:
Has anyone found any solutions for this problem yet?
Click to expand...
Click to collapse
I´ve opened a ticket. I advice to do the same.
- They will send you a link, with the ZIP-file in this link you have to reflash the rom. But probably it won´t work.
- Then tell them that it doesn´t work (of course only if it doesn´t work).
- Apply a RMA request
- Send them your ONE
- Receive an new one.
I´m waiting for the TNT courier, at the moment.

same problem here. No response from support. now recently even the emails to [email protected] are bouncing back with error, cannot deliver your email to the address.

So.. I'm having the same problem now..
I can't even submit a RMA, as I bought the phone from a person without the invite - so I have the receipt and everything, but when trying to submit the RMA, I have to select the order - Which I have none of, isn't that just wonderfull?
Did any of you find a solution?
I've had Samsung GS3 and GS4 with almost the same issues now and it is killing me, my will to keep living with these problems are close to none...

In call microphone cutting off/out

Haven't seen a thread about this problem I'm having.
Basically while in-call, something seems to happen (I'm blaming the mic) where I can hear the person on the other end but they can't hear me. I've read up that this could be a lineage os bug. The thing is, it's not as if it cuts out from the start of the call. It happens randomly in-call and probably reboot to fix
- Happens on the most recent LOS14.1 based roms (I was on LOS14.1 then tried halogenOS, now on sultan's LOS14.1).
- I thought it could be a network issue. called a landline et my network seems fine.
- Full wiped and switched (LOS14.1) roms in case.
- I'm ruling out a hardware problem as I've had calls where it works all the way through, but it's hit and miss.
I'm thinking about switching to LOS15 rom(s) but I'm worried it'll turn out the same.
I'm not expecting a solution (apart from downgrading or going to good old outdated oxygenOS) but am I the only one here? Has anyone else had the problem at least once?
Thanks for your help