Serious microfone problem - Galaxy S III Q&A, Help & Troubleshooting

Hi all
Am I the only one experiencing microfone problems on my new galaxy S3?? Im on my third I9300, because of this issue...
People complaining about that the mic vol goes up and down...

I'm also facing similar issues. I'm going to get mine replaced also.

First of all guys make sure 100% it's not the mic. Record some song and see if you still have the problem. I was facing similar issues with the mic going up and down durring calls.
In my case it was the simcard. Don't ask me why, because the same simcard was working fine in another phone, but after getting a replacement everybody said that they can hear me a whole lot better.

mikesoftwiz said:
First of all guys make sure 100% it's not the mic. Record some song and see if you still have the problem. I was facing similar issues with the mic going up and down durring calls.
In my case it was the simcard. Don't ask me why, because the same simcard was working fine in another phone, but after getting a replacement everybody said that they can hear me a whole lot better.
Click to expand...
Click to collapse
I am going through the very same issues.
I had a mic problem with my first S3 during phone calls. It was really annoying me because I couldn't do anything about it everyone was saying they couldn't hear me etc.
The sim I am using is an British UK O2 micro simcard that I used in a iphone 4, cheap samsung, and samsung S2 previously with no problems at all.
I then returned the phone to the T-mobile shop retailers, they said it was rare and not a common fault.
My new one is doing the exact same thing, I didn't update it nor is there a new update.
Can someone please help. Thank you.

I am getting the same issue but not everytime. I am sure that it is not the fault in mic that is causing this problem, as i recorded my voice (using both mics, the one at the top and at the bottom) and it was crytal clear.

turn off Noise Cancelling... fixed my problems

same problem
Had the same issue ,also with the s 2 , but the trick then (witch also worked now ) was to turn off the noise cancellation .
During a call just take the phone away from your ear and under the callers picture there u will find the option to do so

I have literally just started having the same issue today.
Am on FoxHound Rom 1.4 with Siyah Kernel. Had no problems, even made calls last night, perfect.
Then I tried switching Fast Dormancy on, flashed stock kernel and this morning I find when I made calls to Orange customer services, they were saying they couldn't hear me.
Tried testing it myself, and no matter who I call no-one can hear me.
I've tried:
re-flashing rom, kernel
Tried latest stock roms such as I9300XXBLG8_I9300OXABLG8_I9300XXLG8_HOME.tar.md5, none have made a difference. Even Roms I had backed up in clockworkmod that were working perfectly, like CM10 preview and CM9 have stopped working.
I've tried disabling Noise reduction, which has had no effect. Tried factory reset, flashing modems, kernels, roms, stock roms, nothing has made a difference. I can record video, google talk, anything else fine, just not get anything from the mic when making phone calls.
Tried putting a friends 3 SIM in, and the same thing, so it's definitely not network related either. I definately hope it isn't a hardware fault, as I bought mine on ebay and it isn't insured. Was kinda hoping for more than 2 mores usage out of a phone :crying:

Related

Phone mic voice too soft

My phone is giving me a problem in this area. When i talk on the phone (without using bluetooth or handsfree) people say i sound very far, or very soft. I've tried alot of different radios, and schaps diff versions. Including the latest 4.22ROM
Other then the rom itself i didn't install any other thing. But yet i'm still having this problem.
I've read in other topics that might be about setAcoustic.exe problem, but it doesnt' seem to solve my problem.
Anyone got any other suggestions? It's been causing me a big pain :
anyone know how to fix this??
update, it seems to be happening at random atm, some phone calls it's very clean, other it's too far..
hi, im having this same problem on my 8525. sometimes people can hear me and sometimes people can't hear me at all. any one else have this problem?
there was an old thread on this, search setAcoustic and you'll find it. if that fails , then i guess you can join me to wait for another solution
on the side note, bluetooth works nicely and i don't get any voice distortion or volume too soft.
Update:
So far things seems to be better atm, but it still happens. Sometimes while talking halfway, my signal can get very bad.. does this have to do with radio?
hey guys .... this is my first post here and i too am facing the exact same problem.... any solutuins? please HELP! (sorry for the caps)
Sylpheed said:
My phone is giving me a problem in this area. When i talk on the phone (without using bluetooth or handsfree) people say i sound very far, or very soft. I've tried alot of different radios, and schaps diff versions. Including the latest 4.22ROM
Other then the rom itself i didn't install any other thing. But yet i'm still having this problem.
I've read in other topics that might be about setAcoustic.exe problem, but it doesnt' seem to solve my problem.
Anyone got any other suggestions? It's been causing me a big pain :
Click to expand...
Click to collapse
Here's something to try the next time someone complains you sound far away/too soft: Switch over to your bluetooth handsfree without moving the phone. If you start sounding better then, I would guess that your built-in mic isn't working properly. You'd never know especially since you got it from eBay
Signal strength shouldn't matter too much, unless you start getting a marginal signal (say, one bar), and if that happens, try moving your head about (with your phone) - that should help the signal a little.
kltye said:
Here's something to try the next time someone complains you sound far away/too soft: Switch over to your bluetooth handsfree without moving the phone. If you start sounding better then, I would guess that your built-in mic isn't working properly. You'd never know especially since you got it from eBay
Signal strength shouldn't matter too much, unless you start getting a marginal signal (say, one bar), and if that happens, try moving your head about (with your phone) - that should help the signal a little.
Click to expand...
Click to collapse
haha yeah, recently it seems to be working though, a few times people called me and said can't hear me but i called them back and it worked.
well just an update, nothing seems to be working for me.
Flashing to the latest schap's rom = not working
flasing to other radio versions = not working
Changing to non 3G network, same problem
i'm beginning to be convinced that it might be my phone hardware that's screwed up.
now i'm flashing back to original official dopod rom. see if that fixes things.
Update: While installing my officail dopod rom, i realize that the officail ones install alot more stuff into my Dopod.
Is this normal/ as per compared to schap's roms?
this is the 1st time i'm installing a WM6 official rom, does it make any diff? Everytime you reinstall a rom = kinda like format drive C and reinstalling windows right?
If startup animation is enabled, and set acoustic parameter is not ran. You will have low volume issue. It is Rom/WM related, not necessarily a hardware problem. My Rom ahs startup animation disabled, acoustic parameter is properly set.
Second that, I highly recommend u all try k's 1.30b rom!
how do you make sure acoustic parameter is properly set?
bump.. any one figure this out yet? im tired of texting i just want to talk on my phone hahah. ive come to the point that im gonna buy a razr.
hi all, just another update.
things was working very well for a long while while using K's rom, but now it's starting to happen again while i'm on k's rom.
setAcoustic Param is done (i read in K's rom it's set properly)
anyone got any other suggestions?
update: I've been reflashing a few diff roms, apparently all of them have the same problem, including K's one which i see setAcoustic running at 1st run.
I really have no clue why my voice is too soft. Now i'm flashing the official HTC one, hopefully it works...
anyone got any new info on this? i'm still having the same problem
if it is an hardware issue, is there anyway to figure if it is an hardware issue? or how do i open my phone?
just another update.
Now my voice fades in and out.. it's literally mood swings.. sometimes sounds good, other times sounds bad..
but i'm resorting to use wireless for now. it seems that wireless is more stable. there was 1 time which i was trying to talk on the phone's mic but the other party couldn't hear me, so i switched to wireless immediate on the same call and the other party could hear me immediately.
I've changed countless of roms already, the problem is still there regardless of what rom, official ones from HTC or others cooked in here, (schaps, k's, and many others) i can only assume that my mic is broken....
this i'm in malaysia and this is a orange phone.. i wonder if i can get any warrenty here at all.. or someone that knows how to repair this phone..
Hopefully this will be my last update
I've sent my phone for repairs. hardware wise, they say they fixed it. After that, my volume is pretty stable.
There are once or twice that my voice still went out, however, i found out that by disabling WOW HD Settings, it solved my problem too.
So far, i'm happy with my hermes

mic not working sometimes during calls

i noticed a few times when i either make a call or answer one the microphone just doesn't work - it doesn't happen all the time, sp i assumed it would either be a network or sim card issue. however, i have another phone on the same network (an android phone) which never has the same glitch.
i'd since sent my lumia back to resolve a camera quality issue (which they fixed), but the mic glitch happened again. i know i'll have to send it back for repair again, i was just wondering if this has happened to anybody else?
on a good note, the phone came back with a much MUCH improved camera (prior, the pictures taken on auto were all yellow and badly focused, unless i played about with specific settings. the battery was also much improved, even after the update (which lead me to believe a certain weather app was the cause, as i haven't redownloaded that app after receiving back the phone)
I have problem with mic too (actually my Mom ;>)
Phone was sent to repair three times, and nothing...
There is more about this in topic I made:
http://forum.xda-developers.com/showthread.php?t=1518169&highlight=microphone
I think I must record call with my mom and then play it to them, because they say all is good (but with shi**y old SE everything is great, and signal is worse than in this SE...)
Same problem here, how did u get this fixed?

No call sound, not a hardware issue?

***** started working again after 2 hours... *****
So this happened once before back in November, started working again the after a day or two but wasn't a huge issue as was on holiday so not making calls anyway. It's just happened now, but I need to use my phone. It's not a hardware issue as they can hear me fine and my speakers are working fine as I'm listening to music and it's working in other apps. Any ideas? When I make a call I get the little beep to say the call is initialised, but never hear the ringing or them talking when they answer, I also get the beep when the call is ended. Already tried cache wipe/restart.
I've read every thread I could find on google and most just say either heat up the sound chip (lose connection), or send to Samsung, which is fine if it's a hardware issue but mine isn't.
I'd prefer not to factory reset tbh. Any idea of a fix? AS it's done it before and sorted itself there must be a way to do something?
And not working again?
Did u try flashing latest boeffla kernel. Someone solved in this way
sent from Neatrom'd i9300

Voice echoing on other end of phone call?

EDIT: Read the other comments in this thread to see what I've tried and what hasn't worked. Thank you!
I love my Galaxy S5 so far, but currently it's sucking at being an actual phone. On the other end of the phone line, the people I've talked to have complained of the audio sort of cutting in and out like someone is interrupting me. This happens when I'm in quiet rooms alone, so I'm confused. At first I though it was the case on my phone (Supcase), but after replicating the problem for myself, that doesn't seem to be the case. So at this point I'm not really sure if my phone is possessed or if it's a hardware problem. For reference, I'm running XtreSoLite rom and I have a few Viper4Android audio things running. I'm not sure if that could be the problem. Anyway, if someone could help me solve this issue, I'd really appreciate it. Thank you!
jtc276 said:
I love my Galaxy S5 so far, but currently it's sucking at being an actual phone. On the other end of the phone line, the people I've talked to have complained of the audio sort of cutting in and out like someone is interrupting me. This happens when I'm in quiet rooms alone, so I'm confused. At first I though it was the case on my phone (Supcase), but after replicating the problem for myself, that doesn't seem to be the case. So at this point I'm not really sure if my phone is possessed or if it's a hardware problem. For reference, I'm running XtreSoLite rom and I have a few Viper4Android audio things running. I'm not sure if that could be the problem. Anyway, if someone could help me solve this issue, I'd really appreciate it. Thank you!
Click to expand...
Click to collapse
It's certainly not normal. Not with stock firmware or custom ROMs like Phoenix. I have no idea if your custom ROM is a factor, bit it seems unlikely.
Possibly your problems are reflective of being in a location with a weak and tenuous signal strength. Generally speaking dropouts and feedback are data latency issues seen more with Voip and VoLTE calls. You don't have nearly enough information to do more than guess yet.. but I would make your audio app (Viper) to be the prime suspect.
See if you can exempt voice calls from Viper or temporarily uninstall it. Also find out if any background apps are using high CPU and in particular if any audio apps are set to high priority. Find out if you arwe using VoLTE. CPU (power saving) apps?
If you can't narrow it down, make a backup and then revert to 100% stock to rule out hardware issues. Then install apps one at a time, watching for the issue to return. You could also open a carrier support ticket to see if your account is misconfigured, using a low grade codec, etc.
.
fffft said:
It's certainly not normal. Not with stock firmware or custom ROMs like Phoenix. I have no idea if your custom ROM is a factor, bit it seems unlikely.
Possibly your problems are reflective of being in a location with a weak and tenuous signal strength. Generally speaking dropouts and feedback are data latency issues seen more with Voip and VoLTE calls. You don't have nearly enough information to do more than guess yet.. but I would make your audio app (Viper) to be the prime suspect.
See if you can exempt voice calls from Viper or temporarily uninstall it. Also find out if any background apps are using high CPU and in particular if any audio apps are set to high priority. Find out if you arwe using VoLTE. CPU (power saving) apps?
If you can't narrow it down, make a backup and then revert to 100% stock to rule out hardware issues. Then install apps one at a time, watching for the issue to return. You could also open a carrier support ticket to see if your account is misconfigured, using a low grade codec, etc.
.
Click to expand...
Click to collapse
Thank you for all of this! I'm having an unfortunate week because I'm actually away from home and have very limited internet access, so factory resetting my phone isn't currently an option. However, I did turn VoLTE off and I'll be wiping my cache because I read somewhere that might work. I'll also be watching my apps, but I'm not sure that's the problem. I generally have the same apps on all of the phones I use and this is the only phone people have said I sound bad on. And I don't think Viper is the culprit either because I've disabled it and nothing has changed. So hopefully turning off VoLTE works or simply wiping the cache does the trick. If not, I'll definitely do everything that you recommended because I want to avoid RMAing this device at all costs.
It seems that a factory reset solved the problem. I still have no idea what the problem was, though, but I'm happy it seems to be gone.
So the problem has returned. I factory reset once again and it hasn't done the trick. Everyone is describing it as an echo and telling me they can hear themselves echoing when they speak, although it sounds fine on my end. I don't know what else to do. I have:
Factory reset
Taken the sim out and put it back in
Changed APNs
I don't know what else I can do. Really hoping I don't have to RMA this device. Does anyone know how Samsung is with RMAs?
Bump
Still having this problem. I hope there's someone out there who knows how to fix it.
you ain't alone mine was fine for a while then after the new update it came back i call t-mobile.they put in a open repair tickets as others around my town also complain.my signal is always -114 to -119.they have heard it it when i call them.i get the echo or it brakes up or call turns into noise and then calls drop and they have to call me back on house phone they claim it is a tower/signal issue.??
jtc276 said:
Still having this problem. I hope there's someone out there who knows how to fix it.
Click to expand...
Click to collapse
i had this on my first two handsets it happened in the first 14 days so i had no trouble going into tmo store and exchanging it twice. people could not hear me and the echo was really bad. third s5 call quality super clear now.
been you had exchange the phone and new one working fine what software is it on NF6 or the new NG3 that would tell us a lot???before i downgrade back to the nf6
420soljah808 said:
i had this on my first two handsets it happened in the first 14 days so i had no trouble going into tmo store and exchanging it twice. people could not hear me and the echo was really bad. third s5 call quality super clear now.
Click to expand...
Click to collapse
I had this same issue as well. I could hear people jsut fine, but when they tried to talk to me, be it over tmo network or through wifi calling, they heard bad echoes and noise. I even did as you did; factory reset and it sorta worked. When it happened again, I cleared caches (the official fix from tmo 611) and that worked for a couple hours. Eventually, they told me to take it back to the store and get a replacement.
I believe it's a hardware issue related to the mic; here's why:
When I'm in my car and on bluetooth people on other end hear me just fine and crystal clear. When I used a bluetooth headset, same thing. As soon as I disconnect from BT and go to just the normal mic, echo pops in.
One thing you can do is call 611 and use the voice prompts. It was so bad on my end that the voice prompts picked up itself (well the echoes from the voice prompts). If you do and the voice prompt system routs you even when you don't say anything (it routes your call because of the echoes) then you definitely have a bad handset.
I was rooted, custom recovery, knox tripped and mailed my phone in. Nothing happened. But they did charge me $20 for a return/replacement fee. The new phone I got works no problem.

[Poll] Starting to hate the G2

Okay guys, this entire month I have been considering getting rid of my G2. Will try to keep the story short.
About 4 months ago, I sent my G2 (D802) to repair center. Issue was: at times, people could not hear me during calls. They ended up giving me a completely new G2 few months ago. This week alone, I have experienced at least 5 times where people could not hear me. Only workaround when this happens is to turn on speakers (however, everyone next to you will hear the conversation which it is not exactly great).
Getting sick of it. Calls. I repeat, CALLS I can not even make properly with this phone. Everytime I pick up the phone/call someone, I have to wonder if they will be able to hear me.
Currently I am on completely stock unrooted 20H KitKat, I have tried lollipop firmware but the issue remains. Happened on KitKat 20D too. There's a chance the issue is not on Jelly Bean but I have not tested that because I don't really want to be on JB.
I assume I am not the only one on this boat seeing as the issue is reported by a lot. Share thoughts, possible solutions, etc.
@eepyikes @vPro97 join the discussion.
What kind of cover do you use?
_____________________________________Read more write less and be smart
Are you covering your mic with your finger maybe?It happens easily on g2.
No cover is being used. Pretty darn sure I am not holding anything over the mic. But I'll pay more attention to that from now on.
Look at how many people have reported this issue...
Sent from my LG-D802
I have the same 'hate' to the gps of this phone but..this phone is great all is working great and fast after 1y and 4m..only the gps is super weak.
had you think that maybe your signal/phone provider is to blame? if signal is weak you should try another sim card or another place
Gemc666 said:
had you think that maybe your signal/phone provider is to blame? if signal is weak you should try another sim card or another place
Click to expand...
Click to collapse
Nah. Changed provider about two months ago. Same same.
I have an issue when people are not able to hear me, and it always happens if i want my hands to be free and phone is held between my ears and shoulders(Maybe some issue with noise cancelling or misaligned microphone). Otherwise it just works fine.
This may help you....
If you have turn on "Ok Google "detection from any screen!
I have faced similar problems...I thought that was hardware issue but When I turn off that feature My G2 was back on form and now they can hear me properly
Or another way to get rid away of this **** is to try custom rom also......
i have that problem with ANY stock or stock-based rom..... which is why i got fed up and installed CM12 permanently...... the "ok google" detection thing didn't work for me.... i tried taping the top mic but then i ran into random issues where the mic fails if loudspeaker is on.... no such problems with CM...
chewdaniel said:
i have that problem with ANY stock or stock-based rom..... which is why i got fed up and installed CM12 permanently...... the "ok google" detection thing didn't work for me.... i tried taping the top mic but then i ran into random issues where the mic fails if loudspeaker is on.... no such problems with CM...
Click to expand...
Click to collapse
I asked in one thread if CM/AOSP ROMs had the same issue. Never got the answer until now. Thank you. This is probably the only solution.
Personally, I usually prefer stock based ROMs but that is about to change.
Note: disabling "ok Google" to fix it is only a myth. It does not help. Tried that and so did many others.
Sent from my LG-D802
and to be honest because of this i hope CM doesn't get the 2nd mic working. lol
It's the Google now detection, open Google now, goto settings and turn off From any screen
Maybe there is some dust or some other stuff in the small holes where the mic is which is making your voice more quiet or almost completely mutes the sound you are trying to record.
You should try and DISABLE Voice enhancement at Settings>Networks>Call..
it helped my whatsapp voice messages to be played clearly
Have had 5 G2s for different reasons and never ran into a Mic problem.
Have even used various Roms from stock JB to KK to Optimus G3.
Am on Tmobile and used nothing but D801s.
All have been white.
Not sure if that helps
There's hope for you if you're able to sell and replace your phone with another used G2 in mint condition
My experience is, once you've done a repair and things look botched, change the phone.
Sent from my SM-N910H using XDA Premium HD app
Have you tried increasing the volume of the mic by editing the mixer_paths.xml.
Sent from my LG-D802 using XDA Free mobile app
I had the same problem after i've bought my G2 last year. Even asked in offical german LG forum but got no answer.
Solution for me was flashing custom kernel (dorimanx). Since that time i've alway been on custom rom (stock and aosp) and never had that problem again.
Wich rev do you have?

Categories

Resources