The microphone does not work and appears disabled.
In telephone calls the microphone appears crossed with a line as if it were disabled.
However with other applications it work, Including incoming phone calls. Its not hardware driven issue as the mic(s) work under all other circumstances. Does not work when I make a phone call (or make a call through whatsapp.)
I have tried several custom roms on my OP3 but the problem hasn't been solved yet (Now I have installed oxygenOS 4.0).
Thanx 4 your help
Related
Hello. My first posting. I have looked to see if this has already been asked.... After using mute or vibrate function on my XDA 2s unit, and then switching to making a call or trying to receive a call I can't hear the dial tone, or the other person on the other end of the call. I can only make and receive calls once I soft reset the unit. This is becoming a regular occurence. Any ideas would be much apprecaited.
Craig.
same problem
I also have same problem. my XDA IIs often have a problem with the incoming/outgoing calls which is I can't hear the tone nor the person's on the other end of the call (but the person on the other end of the call could hear my voice). It often (not always) happens without the device had a recent setting change or running program so on one occassion it just handles the calls perfectly and suddenly the problem happens and I also have to soft-reset it to make it back to normal, and it is becoming regular.
This is unfortunately a well known bug that none radio upgrade could solve so far...
Look at : http://forum.xda-developers.com/viewtopic.php?t=40417
The problem seems to occur only when Bluetooth is off... So the solution is to turn Bt On (and then off if you wish so) and it's ok without soft reset...
The best way to avoid it is to let Bt ON but to uncheck "Allow other devices to detect me" (forgive me if the english translation is not accurate but my PocketPC is in French) in the Bt parameters to avoid power consumption.
It worked for me so have a try
As the title says:
I'm currently trying to run the FRX06 release on my Touch Pro 2 RHOD 100. The problem is that when receiving and making calls the call seems to "go through" but there is no sound in the speaker but noise, and the microphone is not working.
Since making and receiving calls is a very vital part of my phone usage , I would like to know if any of you have experienced the same problem or have a solution for this?
BR
Cairhien
EDIT:
I found a solution. I followed the guide for android on SD-card and now it works - sort of... I still have to hit the speaker button when receiving calls - but that one is to live with. Besides that I havn't found any "show-stopper" yet. Or at least the bugs that I have found is nothing compared to how annoying WM 6.5 is....
Hi guys, hope you can help with an odd problem...
Very, very occasionally (maybe 1 in 50 calls) I get an issue where I can't hear the other party, as if the earpiece was dead. If I drop the call and re-dial, 99% of the time everything is fine. (I think I had one time in 6 months where the 2nd call did the same.)
Now, I can't decide if this is a network issue (Vodafone) or a phone issue. I mostly use a Bluetooth headset due to the size of the Note but I doubt it's headset related as I have tried two different high end brands and it happens with either.
Things I have noticed:
Problem applies to incoming AND outgoing calls
I have checked I haven't accidently muted the call
My Bluetooth headsets all chime at the start of a call but there is no call audio
The other party can hear me but I can't hear them
System sounds are all fine, only call audio is affected
Switching between headset, phone and speaker phone make no difference
Applies to all incoming call audio, including ringing tones and busy tones
I reboot my phone sometimes but as the issue is rare I couldn't say if it makes a difference. Also this is a standard Note II (not a branded Vodafone one) with all the latest patches downloaded. Looking through my app downloads I can't see any obvious ones that might affect the phone. Apart from the stock Samsung apps I most connect to CCTV systems. I have CSipSimple but I haven't used it in ages.
Any suggestions on how to investigate this further?
Regards,
Andy
Seriously... no ideas?
So, no one's ever had this problem and no one has any ideas?!
:crying:
I've got a head scratcher that I can't fix. I can't hear anything in calls and the other end can't hear me. My speaker and mic work perfectly in all other applications - I can record video and hear the audio in that, I can make and receive calls in Skype and Viber and the speaker and mic work flawlessly in both but the standard phone just doesn't work. I hear the rising been after dialling and then nothing - I can't hear it ringing and can't hear anything once it is answere and the other end don't hear me.
Phone was totally stock (not even rooted) when this first happened and I figured I'd fix it through a new rom so I rooted and first one I tried was an old familiar ARHD (I'd used the equivalent on my last phone) and it was odd as I think that seemed to fix it for the first test call and then stopped again. This seemed to be an oddity as no other rom I've tried even worked once.
I figured something Samsung was still updating after the install and causing the problem so next I tried Cyanogen 11 - didn't work even once. Tried Cyanogen 10.1.3, same thing. Just tried the AOSB rom and still the same thing...
Really not sure what to do now - any ideas?
Thanks,
DF
Hi,
Custom ROMs can be difficult and might be a source of the issue itself. Since your issue was present before installing the custom ROM, we might be able to assist. Please open a support ticket at this link: http://bit.ly/1aOwGy2 and a support agent will be in touch.
dannyfranks76 said:
I've got a head scratcher that I can't fix. I can't hear anything in calls and the other end can't hear me. My speaker and mic work perfectly in all other applications - I can record video and hear the audio in that, I can make and receive calls in Skype and Viber and the speaker and mic work flawlessly in both but the standard phone just doesn't work. I hear the rising been after dialling and then nothing - I can't hear it ringing and can't hear anything once it is answere and the other end don't hear me.
Phone was totally stock (not even rooted) when this first happened and I figured I'd fix it through a new rom so I rooted and first one I tried was an old familiar ARHD (I'd used the equivalent on my last phone) and it was odd as I think that seemed to fix it for the first test call and then stopped again. This seemed to be an oddity as no other rom I've tried even worked once.
I figured something Samsung was still updating after the install and causing the problem so next I tried Cyanogen 11 - didn't work even once. Tried Cyanogen 10.1.3, same thing. Just tried the AOSB rom and still the same thing...
Really not sure what to do now - any ideas?
Thanks,
DF
Click to expand...
Click to collapse
Viber Team said:
Hi,
Custom ROMs can be difficult and might be a source of the issue itself. Since your issue was present before installing the custom ROM, we might be able to assist. Please open a support ticket at this link: http://bit.ly/1aOwGy2 and a support agent will be in touch.
Click to expand...
Click to collapse
Hi,
Thanks for the offer of help but Viber actually works perfectly - it's just the built in phone that stopped working. Unfortunately GiffGaff don't seem to support Viber In for all calls otherwise I would just enable that and not worry about the normal phone not working...
Thanks,
DF
Samsung s9 exynos
After update the ui2.5 my mic isn't working properly when i receive the call the other person don't hear my voice until i put it on the speaker and once mic started then i can put the speaker off.
But when i make the call the mic works properly. I don't need to put the call on speaker.
I also had this same issue, thought something was wrong with my phone. I fixed mine by flashing latest rom through odin.
Dear, after some tests it seems properly working removing bixby features: vocal activation, automatic listening, use with locked smartphone and other features letting bixby automatic activation. After different incoming calls it seems properly working. Please let me know your experience.
I have the exact same issue with my S9 over the last few months or so. Does anyone know what caused it or a less intrusive fix (other than reflashing stock OS)?