Hi to all,
As explained in the title, in all CAF ROMs I tried up to now, I always have very bad sound (at reception side) transforming my voice to a robot voice very hardly understanable for the recipient. Normal phone calls and other apps like Viber are not affected.
The point is that I largely prefer CAF for all the other aspects too long to explain here.
Does anyone know if there is a fix somewhere for that VERY annoying problem (I need to use Skype for business) ?
Thanks in advance.
Am I the only one who encounters this problem whith CAF ROMs??
Thanks
Related
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
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
Hi, I've got some kind of problem with my Mi4c microphone. During calls no one can hear me if I don't use the loudspeaker option, and when I try to record something it's really quiet. I've tried stock ROM, cyanogenmod 12.1 and 13.1. Does anyone know what may be causing it? And what's the fix? Thanks in advance.
same problem
I have same problem to, i've try to change microphone with other, but it still same..
Please help thus isue...
Same problem with me. My partner couldn't hear my voice when we made video call with facebook, hangout, duo etc. But using line working normally
Same problem here. It started after updating CM 13.1 TS to version 20161007.
It looks like other phones are having the same problem, so I guess it's not an mi4c specific issue... As for Skype, 7.00.0.655 works. See https://community.skype.com/t5/Android/Microphone-not-working-android/td-p/4417354/page/4
Extremely low microphone volume when doing Skype Echo call test on stock MIUI8, but works normally when calling somebody. Weird.
On having installed the some roms they work well but there is a problem, does not leave me to send notes of voice for whatssap or sometimes they are cut, practically it notices them of voice they do not work (the microphone this one good) it happens to me with cm 12 or roms verision 5.1 pls me:good:
Hi Guys,
well, the mic issue is not really an unknown to OPO users - I have never experienced such issue, but some time ago my mom let me know she has problems with mic for long time now (she has inherited my OPO), so there I went - looking for an intel regarding this issue.
I have come across some standard fixes for Cyanogen (the last official one by OPO themselves):
- blow out dust/debris from the microphones (done with a vacuum cleaner),
- remove TrueCaller, voice recorder, turn off "Ok google" recogniton (basically not a problem for us, we have Slovak language, thus no support anyway),
- tried other services - like Viber and it worked perfectly!
- tried speaker mode - worked!
So after this I came into the conclusion maybe a drop or something has damaged or something the rear mic for ambient noise suppression (maybe?).
But then I found some info the CnM is the problem itself, so I have just switched to the LineageOS (it is not really a change when I am thinking about it now, well is it?), but this has not helped, still the same problem.
I have found this too and applied too, but, again, no success.
Do you happen to have any other suggestion? How is it possible Viber works? Can be some app such as Viber used as the phone app too?
Thank you, in an advance...and I hope we will come to some conclusions here, I am wasted from all of this...
dropadred said:
Hi Guys,
well, the mic issue is not really an unknown to OPO users - I have never experienced such issue, but some time ago my mom let me know she has problems with mic for long time now (she has inherited my OPO), so there I went - looking for an intel regarding this issue.
I have come across some standard fixes for Cyanogen (the last official one by OPO themselves):
- blow out dust/debris from the microphones (done with a vacuum cleaner),
- remove TrueCaller, voice recorder, turn off "Ok google" recogniton (basically not a problem for us, we have Slovak language, thus no support anyway),
- tried other services - like Viber and it worked perfectly!
- tried speaker mode - worked!
So after this I came into the conclusion maybe a drop or something has damaged or something the rear mic for ambient noise suppression (maybe?).
But then I found some info the CnM is the problem itself, so I have just switched to the LineageOS (it is not really a change when I am thinking about it now, well is it?), but this has not helped, still the same problem.
I have found this too and applied too, but, again, no success.
Do you happen to have any other suggestion? How is it possible Viber works? Can be some app such as Viber used as the phone app too?
Thank you, in an advance...and I hope we will come to some conclusions here, I am wasted from all of this...
Click to expand...
Click to collapse
Just a little search,and look what I found!
https://forum.xda-developers.com/showpost.php?p=74316182&postcount=2267
Oh, I thought I will get around it without a root, thus why I did not try any of the "must be rooted" approaches. But yes, it is fixed now, however...
This is a very unwanted outcome - the phone has been used for recording band's sessions as well where the mic array was used fully, but now calls, yes, are ok, but the recording quality is horrid - basically it was recording like when you switch a call to the speaker mode, where other microphones were recording too and giving that full-bodied sound, now it is like through a gaming headset with a noise cancellation.
What is this issue caused by, anyway? Is it because of a damage of one of the microphones?
Anyone? The rear mic was really handy for the music recording (full sounding). Is it possible to make it somehow toggleable?