No Voice Transmission during Phone Calls - Galaxy S6 Q&A, Help & Troubleshooting

(Duplicated from previous post as per suggestion by admin. See here: https://forum.xda-developers.com/general/help/voice-transmission-phone-calls-t3690651 See Addendum notes)
Hello! Long-time lurker, first time poster.
I have a sudden problem with my Android phone (Samsung Galaxy S6 running Android 7.0). Hopefully you bright gentlemen and gentle-ladies can help me:
Approximately 1 week ago (edit: 3 weeks ago), my phone stopped transmitting Voice data on phone calls. I cannot hear what the other user says on their phone, and they cannot hear me, however, pressing number keys DOES transmit the dial-tone to the other user (both ways). It does not matter if I call them or if they call me. It does not matter where I am physically, I have tried in several locations around the city (likely on several towers). It does not matter if they are using a mobile or land-line. (Addendum: Hangouts dialer functions perfectly with the hardware, before and after factory reset(s), Bluetooth headset works with Hangouts but not regular Phone)
During this time, all of my data connections work fine. Texts, Email and Browsing is unaffected. Phone performance is normal.
Since this has occurred, I have:
- Simulated battery disconnect
- Wiped Cache Partition
- Force-stopped the Phone app (all three instances)
- Verified the physical Microphone is working using the Voice Recorder app (it works fine)
- Booted the phone in Safe Mode
- Contacted my service provider to check in there was any problems with my account or transmissions.
- Transferred my Sim card to another device to test if my card/connection was ok. (Voice worked 100% on the secondary device)
- And lastly today (two weeks ago); Completed a Factory Reset
(Addendum:
- Flashed stock firmware from Sammobile via Odin
- Attempted to clean out the Microphones with toothpicks and blunt metal objects, just to be sure
- Plugged in and removed a wired headset as well as checking for debris)
I am sitting here now trying to understand how a hardware problem could possibly cause a failure of Voice encoding on only one app, and how to fix it. Or how a software problem survived the Factory Reset (and Firmware flash) into the fresh install. I did indeed try without any 3rd party apps being installed, without even adding my Google or Samsung accounts to the phone, just plain old Android; no dice.
Any suggestions?
I recall one fixing another phone that had a problem with its Capacitive Touch Screen being not sensitive enough/not reading presses problem by accessing a special menu that allowed me to re-download the driver. Is there anything like that for the Voice? (Addendum - I have looked at all the star ** codes available for this model and tried several, nothing has worked so far)
Thanks!
Thoughts today (Oct 31/17): I am not sure that flashing a custom rom is really what may fix the phone. I am willing to do so, but it is somewhat frowned upon by Canadian carriers (or at least it used to be). I was curious if it was a problem with Noise Cancellation or an SD Card problem as those are issues brought up when googling the issue. My current plan is to flash to a stock Android 6.0.1 and see if the phone works then. If so, then try the standard upgrade path. Any suggestions will be helpful!

Related

[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

No Voice Transmission during Phone Calls

Hello! Long-time lurker, first time poster.
I have a sudden problem with my Android phone (Samsung Galaxy S6 running Android 7.0). Hopefully you bright gentlemen and gentle-ladies can help me:
Approximately 1 week ago, my phone stopped transmitting Voice data on phone calls. I cannot hear what the other user says on their phone, and they cannot hear me, however, pressing number keys DOES transmit the dial-tone to the other user (both ways). It does not matter if I call them or if they call me. It does not matter where I am physically, I have tried in several locations around the city (likely on several towers). It does not matter if they are using a mobile or land-line.
During this time, all of my data connections work fine. Texts, Email and Browsing is unaffected. Phone performance is normal.
Since this has occurred, I have:
- Simulated battery disconnect
- Wiped Cache Partition
- Force-stopped the Phone app (all three instances)
- Verified the physical Microphone is working using the Voice Recorder app (it works fine)
- Booted the phone in Safe Mode
- Contacted my service provider to check in there was any problems with my account or transmissions.
- Transferred my Sim card to another device to test if my card/connection was ok. (Voice worked 100% on the secondary device)
- And lastly today; Completed a Factory Reset
I am sitting here now trying to understand how a hardware problem could possibly cause a failure of Voice encoding on only one app, and how to fix it. Or how a software problem survived the Factory Reset into the (semi-)fresh install.
Any suggestions?
I recall one fixing another phone that had a problem with its Capacitive Touch Screen being not sensitive enough/not reading presses problem by accessing a special menu that allowed me to re-download the driver. Is there anything like that for the Voice?
Thanks!
Ack, only 10 views and buried on page 3 already. Chances of resolution seem low...

Know about phone fixing? here's a challenge for you!

Hello! I'm going to need some help on someone that might know more than I do.
Here's the challenge:
Phone: Samsung Galaxy S7 AT&T Unlocked (G930A)
Build: G930AUCS4BRA1 (latest)
This phone has two really hard to pin down issues that will surely make a challenge.
First one, is the microphone. Calling or receiving a call makes the person on the other end to hear themselves. It is not explained by the other person using speakers, since it happens 100% of the time, even testing it with the express instruction to not use a speaker.
What the hard-to-pin-down issue is? It doesn't happen with any other calling program. I can voice call from WhatsApp or from an app from my provider using Wi-Fi or 4G and the issue disappears. Only happens if I receive or make a call from the phone without using Internet.
Second one, is a new one that happens randomly. The phone freezes, shuts down and restarts in a loop, about 3 or 4 times, and then works normally. Happens about 2-3 times a day and started two days ago, without any physical damage as a cause.
What has been done to try to fix this issue?
Cleared cache
Phone reset
Installed updates (twice, one from 6.0 to 7.0, and then updated the build number), once by using Odin, and the other one to update from SD Card.
Nothing has fixed any of these issues.
Any ideas?

Cannot make/receive calls, but mobile data/SMS/WiFi/Bluetooth work fine.

I want to start by saying thank you to everyone on this forum. I have learned so much from reading the guides and resources (particularly those by @Gawd, @spanna, @Heisenberg, @EddyOS, and @Timmmmaaahh. I know some may have moved on but you legacy remains.).
This issue seems to have come up before on the forum, but I have not found one that matches my own situation with a solution, unless I am missing something. I am also lucky in that I have access to another near identical OPO without the issue for comparison. I am visiting my family and we all have OPO.
I have noticed that my phone will have decent to good signal (1-4 bars of Tomobile LTE) be able to use cellular data and send SMS, but not make and receive phone calls in certain areas. I would have been content saying this was a reception/carrier issue. However, I am visiting family for Memorial day and have been able to troubleshoot this with their phones. I bought my parents OPOs when it came out and my brother has a Find7, so we all have essentially the same hardware. For my troubleshooting I used primarily my mother's OPO (not updated since CM11S) and occasionally my brother's Find7. Both my mother and I have the 64 GB edition of OPO purchased around Oct-Nov 2014. Both are cobranded with Cyanogen, though mine was purchased a month or two prior to hers. When comparing the OPOs I notice her phone is able to send and receive calls in places where mine is not able. We have similar reception. I have cellular data and can still SMS. The issue is just with calls. I have tried the following (i have bolded things which I noted were different):
Basic stuff:
1) Making and receiving calls with both phones side by side. Her phone can send and receive calls in all areas (even with just one bar), while mine can only make and receive calls in some areas. My brothers Find7 has identical performance as my mothers phone.
2)Toggling airplane mode. -- Same result.
3)Toggling LTEonly, 3g only, and 2g only. -- Same result.
4)Verifying APN -- Identical for all three phones
5)Swapping SIM Cards -- both phones perform the same irrespective of which sim card is in it.
6)Verfied IMEI -- present in all phones.
7)Verifying signal strength (dBm/asu) in phone settings (*#*#INFO#*#*) -- near identical between phones. Our dBm numbers were the same but my asu number was sometimes triple her phone's asu. Her's was identical to the Find7.
More advanced stuff:
8) Removing the back cover and making sure the terminal are making contact to the backplate antennae.
9) Changing roms and firmware. No success.
- I had recently upgraded from the final release COS 13 to the latest Oreo RR with a clean wipe using TWRP. I was running RR when I first started this.
- First I tried flashing my recovery file with TWRP. It says it ran successfully, but didn't make any changes to the system.
- Since my mothers phone has no issues I tried to replicate her setup. I fastboot flashed the cm-11.0-XNPH05Q-bacon-signed-fastboot.zip provided by spannaa.
- I found some similar posts to my problem which linked to gawds firmware. I verified that both my mother's working OPO and mine had the same OS (XNPH05Q) and baseband (c7-00020) I also tried flashing different firmwares with no benefit.
- I tried fastboot flashing back to COS 11 XNPH33R (what my OPO came out out of the box with).
- I then used EddyOS guide to return device to stock COS 13.1.2. with no change.
- Thinking another new ROM may include a better firmware. I most recently did a clean install of AOSPExtedned and currently have baseband c6-0241.
Going forward:
- I was thinking of flashing gawds firmwares with AOSPExtedned. Is this safe?
- Looking to disable/unlink my google voice account from my cell number. My mom does not have this set-up. I noticed a delay in making calls, and that my google voice account has a log of all my missed calls (those that never make it to my cell). Maybe it interfering with my calls going in and out.
- Any suggestions on diagnostics I can run while I have access to my Mom's functioning OPO.
Much thanks for everyone's help.

Microphone works for recordings, but not calls or CIT

I'm at my wits end:
I recently tried installing vanced youtube on an unrooted Poco X3 NFC. Afterwards a few permissions were reset, but everything seemed fine, except that somehow during calls no one could hear me anymore. I reversed the whole setup, but the problem persists that no one can hear me during calls.
Recording apps or voice recordings in WhatsApp work fine though. Recordings are clear.
I tried Simple Caller as well, but the same problem persists.
CIT tests of Main Mic show low volume coming in, but never to full volume, even when I blow into the microphone hole.
Has anyone encountered this problem before? I was thinking it might have something to do with the MicroG installation, since MIUI (as always) doesn't play nice with any software hacks.
Enter test menu to double check hardware is not a problem. Just dial * # * # 64663 # * # * and do all mic tests.
If you running Magisk, disable it completely on its settings, so no module/other will change system files systemlessly (on "fake/mirror" system) after a reboot and test again all mics.
Besides that I suggest to flash again the ROM you are using and try it. May be a dirty flash if using some custom ROM....just to be sure actual system on system partition files are not touched.
Another 2 points to consider: have you been playing around with flashing Firmware and/or Kernel? This can be affecting hardware access. If so, then consider to flash again newest available that known to work fine for your very specific variant / Android version.
As a last resort a full flash of newest stock ROM (MIUI v12.5.1+) by fastboot + factory reset afterwards can be interesting to do a final test.
Just to remember: voice recording, whatsapp call (VoiP)....this is not processed as same way as a regular phone call (PSTN), the hardware that deals with the voice processing (after mics; DAC) are different. For instance you can skip (and also test) this when putting a regular call by using a bluetooth phone/mic...the bluetooth device will do the voice process this way.
wilsonhlacerda said:
Enter test menu to double check hardware is not a problem. Just dial * # * # 64663 # * # * and do all mic tests.
If you running Magisk, disable it completely on its settings, so no module/other will change system files systemlessly (on "fake/mirror" system) after a reboot and test again all mics.
Besides that I suggest to flash again the ROM you are using and try it. May be a dirty flash if using some custom ROM....just to be sure actual system on system partition files are not touched.
Click to expand...
Click to collapse
I did do the CIT tests. Main MIC recognizes some input, but the "speedometer", never passes the third marking (of 10), no matter how loud I am. Same is true for the Top MIC.
The phone is still locked, so I don't have Magisk or anything else installed. I'm on Stock ROM with newest version (MIUI 12.5.2 (RJGEUXM))
Immortal68 said:
I did do the CIT tests. Main MIC recognizes some input, but the "speedometer", never passes the third marking (of 10), no matter how loud I am. Same is true for the Top MIC.
The phone is still locked, so I don't have Magisk or anything else installed. I'm on Stock ROM with newest version (MIUI 12.5.2 (RJGEUXM))
Click to expand...
Click to collapse
While you replying me I've edited my message. Read it again, please.
And now knowing those additional information I'd suggest you to BACKUP your data and factory reset device. And test again with it clean. Specially if have updated MIUI recently.
You can also test it before and after factory reset with a bluetooth mic. Put regular phone calls using bluetooth.
It would be nice to also try your SIM card on the other SIM slot or better test another SIM card on your mobile (both slots). Or at least test your current SIM card on an old / third-party device.
wilsonhlacerda said:
While you replying me I've edited my message. Read it again, please.
And now knowing those additional information I'd suggest you to BACKUP your data and factory reset device. And test again with it clean. Specially if have updated MIUI recently.
You can also test it before and after factory reset with a bluetooth mic. Put regular phone calls using bluetooth.
It would be nice to also try your SIM card on the other SIM slot or better test another SIM card on your mobile (both slots). Or at least test your current SIM card on an old / third-party device.
Click to expand...
Click to collapse
Thank you for your quick reply. It's quite interesting to know there's a difference between phone calls and voice recordings.
I connected my bluetooth earphones and tried call and recorder again, but it yielded the same result as before - call: the other side couldn't hear me; recording: perfectly fine.
I'm afraid a factory reset might be needed. I'm just trying to get around it and it's baffling to me, that the microhpone works perfectly everywhere else - only not at all during calls.
I tried switching the SIM card from slot 2 to slot 1, but it didn't change anything either.
Immortal68 said:
Thank you for your quick reply. It's quite interesting to know there's a difference between phone calls and voice recordings.
I connected my bluetooth earphones and tried call and recorder again, but it yielded the same result as before - call: the other side couldn't hear me; recording: perfectly fine.
I'm afraid a factory reset might be needed. I'm just trying to get around it and it's baffling to me, that the microhpone works perfectly everywhere else - only not at all during calls.
I tried switching the SIM card from slot 2 to slot 1, but it didn't change anything either.
Click to expand...
Click to collapse
Your bluetooth not working to call in fact are good news: this suggests more a software problem and not a DAC/hardware problem on mobile mainboard. And this does happen, my girlfriend has a Samsung with this kind of problem and I've also read similar others.
By the way I've read a few weeks ago in a local Poco X3 Facebook group of my country a guy with exactly same problem as you. He started to have the problem after upgrading MIUI v12.0.x to v12.5.1 if I can remember, but preserving data. After he tried everything that I suggested he endup factory reseting and this finally solved his problem. At least in his case seems it was some kind of data getting corrupted/incompatible when updating MIUI.
wilsonhlacerda said:
Your bluetooth not working to call in fact are good news: this suggests more a software problem and not a DAC/hardware problem on mobile mainboard. And this does happen, my girlfriend has a Samsung with this kind of problem and I've also read similar others.
By the way I've read a few weeks ago in a local Poco X3 Facebook group of my country a guy with exactly same problem as you. He started to have the problem after upgrading MIUI v12.0.x to v12.5.1 if I can remember, but preserving data. After he tried everything that I suggested he endup factory reseting and this finally solved his problem. At least in his case seems it was some kind of data getting corrupted/incompatible when updating MIUI.
Click to expand...
Click to collapse
That's good to hear. I may have to factory reset it tomorrow then. It's the phone of a friend, which is why I tried to get around it (the whole backing up of stuff, etc.), but it does seem to be the only solution. Thank you for your help. I'll report back if it worked, if I do it.
Short update. Somehow the thing fixed itself over night. Next day the microphone worked again. Idk why, but this meant I didn't have to factory reset.

Categories

Resources