Related
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...
When I purchased this phone on Swappa, everything worked, with the exception of phone calls. I assumed it was a ROM issue, but I have since tried mulitiple ROMs, with no success at resolving it. The culmination came this morning when I used the LG flash tool to fully restore it to factory settings, and the problem persists. The symptoms are as follows: when trying to make a call, the dialer opens, the call tries to connect, shows "dialing" then disconects. On a very rare occaision it will successfully connect, but I have yet to observe any pattern. Everything else works, sms, data, etc, and I have replaced the SIM card to rule that out. I will post a logcat in the first comment of when it fails, and I will try to get one of when it connects for comparison, but we'll see how that goes.
Code:
[ 02-15 15:28:14.035 4864: 4874 I/CallHandlerService ]
CallHandlerService - onDisconnected: Call{mCallId=6, mState=DISCONNECTED, mDisconnectCause=ERROR_UNSPECIFIED, mCapabilities=530, mConnectTime=0, mChildCallIds=[], mGatewayNumber=null, mGatewayPackage=null, mIdentification=CallIdentification{mCallId=6, mNumber=xxxxxxxxxx, mNumberPresentation=1, mCnapName=null, mCnapNamePresentation=0, mTelephonyCallerInfo={contactNumber=, okToGetTelephonyCallerInfo=false, cachedPhotoIcon=null, phoneNumber=, person_id=0, photoResource=0, name=, contactExists=false, contactExistsCount=0, cachedPhoto=null}}, mSsNotification=null, mConnectionInfo=ConnectionInfo{mCallId=6, mAddress=xxxxxxxxxx, mOriginalNumber=xxxxxxxxxx, mCdnipNumber=null, mToa=129}, mLine1Number=xxxxxxxxxxx, mSubscription=0, mRoamingCallIsIncoming=0, mRoamingRadMode=0, mRoamingPrefix=null, mIsConfConn=0, mPrivacyKeeperState=NONE}
[ 02-15 15:28:14.035 4864: 4864 I/CallHandlerService ]
CallHandlerService - ON_DISCONNECT_CALL: Call{mCallId=6, mState=DISCONNECTED, mDisconnectCause=ERROR_UNSPECIFIED, mCapabilities=530, mConnectTime=0, mChildCallIds=[], mGatewayNumber=null, mGatewayPackage=null, mIdentification=CallIdentification{mCallId=6, mNumber=xxxxxxxxxx, mNumberPresentation=1, mCnapName=null, mCnapNamePresentation=0, mTelephonyCallerInfo={contactNumber=, okToGetTelephonyCallerInfo=false, cachedPhotoIcon=null, phoneNumber=, person_id=0, photoResource=0, name=, contactExists=false, contactExistsCount=0, cachedPhoto=null}}, mSsNotification=null, mConnectionInfo=ConnectionInfo{mCallId=6, mAddress=xxxxxxxxxx, mOriginalNumber=xxxxxxxxxx, mCdnipNumber=null, mToa=129}, mLine1Number=xxxxxxxxxxx, mSubscription=0, mRoamingCallIsIncoming=0, mRoamingRadMode=0, mRoamingPrefix=null, mIsConfConn=0, mPrivacyKeeperState=NONE}
[ 02-15 15:28:14.035 1471: 1471 D/CallNotifier ]
onDisconnect: cause = ERROR_UNSPECIFIED, incoming = false, date = 1455568080816, subscription = 0
That seems to be the most relevant series of lines from the failure logcat. Full log attached, if anyone knows what specifically to look for.
I really don't know what to look for, and the full log is too long to post, so I will attach it here.
Does anyone have any ideas what is wrong, or what I need to do to get this device to work reliably? Is it possible that it is the SIM reader? (seems unlikely since SMS and data work, and calls work intermittently.) Also worth noting, calls seem to connect immediately after a reboot fairly consistently.
Bump?
Bump x 2?
Desperation bump? LG says they can only evaluate the device if I provide a copy of the original sales reciept, which the guy I bought it from says he can't get. He guarentees the device was working when he shipped it, though I have some doubts, as he did indicate he wasn't using it, just made some test calls, and the phone seems ot work immeidately aftera reboot... Any ideas at all??
rassawyer said:
Desperation bump? LG says they can only evaluate the device if I provide a copy of the original sales reciept, which the guy I bought it from says he can't get. He guarentees the device was working when he shipped it, though I have some doubts, as he did indicate he wasn't using it, just made some test calls, and the phone seems ot work immeidately aftera reboot... Any ideas at all??
Click to expand...
Click to collapse
I don't think it's hardware. Sounds like an internal setting got messed up. I assume you've cleared everything that's clearable from recovery.
I suggest you flash CM13. If you still have the problem, ask the CM guys for help.
I have the same problem. Wife has same phone, doesn't have problem (but has software version d85021q). I am currently using sock rooted 20f, flashed 21r modem. tried different roms all have the same problem. sim works fine in my old S4. data and texts work fine. Calls try but then stop with call ended. problems with receiving calls too. Signal strength is -108db same as hers, the S4 is about the same maybe -106db. here's a list I have tried.
1. stock KK rom
2. stock rooted 20f rom
3. RR 5.5.8 rom
4. fulmics 2.7 rom
5. latest cm 12.1 nightly
6. flashed 20f modem
7. flashed 21r modem
I would try flashing MM roms but without the baseband updates would I be in the same boat? Also worried about being stuck with MM if I want to return to LP.
I did pretty much everything possible to try to resolve this, with not success. I tried multiple custom roms, I used the LG Flash Tool to try multiple version of factory rom, and never had any luck. Always the same issue, everything worked but phone calls. I gave up, and bought a device with a shattered screen, and swapped the board over into my good body. Of anyone comes up with any ideas, I'm very interested. I have the equipment to even do on board repairs/component replacements, but I don't know what to try to replace, since the radio obviously works or data and texts wouldn't work.
I've tried pretty much everything imaginable from a software/firmware standpoint... I've tried multiple custom ROMs, I've used the LG Flash Tool to flash multiple version of stock, and multiple modems, etc. I always ended up with the same result. Everything worked but phone calls. I finally gave up and bought a device with a smashed screen, and swapped that board into my body. I'd still be interested if anyone has any insights. I have the equipment necessary to replace board level components, etc, but I don't have the equipment to test them, so I don't know what to try replacing. The radio is obviously functional, since text + data work...
If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
I have no idea when calling functionality begins to be lost because I can still send and receive texts, but I can't make or receive calls. I don't even get a wave of missed calls or anything when it works after a reboot.
Google Assistant has it's own issues when this happens too. It won't come up with "Hey, Google" at all. When I long press the home button, Google Assistant comes up, but I just get the floating dots. Fortunately, it doesn't freeze when I try this. Restart the phone and I'm good for about 10 minutes or so. I tried installing 3rd party calling apps, but the problem persists.
Hoping this is a Pie issue and waiting for the next security patch, will likely do a sideload flash-all. Any suggestions as to what the problem is from? Could my SIM card be the problem? Any apps I could try to help narrow down the issue? I had no issues with Oreo.
Thanks in advance.
Tried rebooting in safe mode. Slightly similar results: works fine for about 10 minutes but then it's just the mic not working. I can make and receive calls with out the phone freezing, but no mic.
mbstone said:
If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
Click to expand...
Click to collapse
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, with everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (a few days later, rarely get/make calls). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
After continued issues I parked phone in drawer a bit then pulled out and tinkered with a few weeks later. Tried to isolate problem using logcat and on a hunch I flashed TWRP and a custom ROM but NOT any gapps package. Sticking sim in and using the built in phone app (Resurrection Remix -com.android.dialer) it works without issue. What? I flashed gapps (correct version/etc) and sure enough the problem returned. Went back to rom minus gapps, works fine. So, with straight up stock rom - stock phone dialer fails, custom rom - it works without a gapps package but not with.
Aimless Rambler said:
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (about 5 days later). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
Click to expand...
Click to collapse
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
brkshr said:
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
Click to expand...
Click to collapse
AT&T
---------- Post added at 07:47 AM ---------- Previous post was at 07:45 AM ----------
mbstone said:
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Click to expand...
Click to collapse
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
See my updated post (# 3) for what I've tried since..
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
brkshr said:
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
Click to expand...
Click to collapse
Older/newer phone dialer apps didn't work for me either ... custom rom and eliminating google play services did (no gapps). I'm still tinkering with the device ... installing frequently used apps using F-droid and Yalp, will test it. Not quite sure why but it works.
I ended up flashing Lineageos for Microg, presents it's own problems in the learning experience but it works.
Nothing ever worked in the end. No, not with Verizon. Bought through Canadian carrier called Fido.
Called Google tech and they weren't overly helpful. I started a chat with a Google Tech and they suggested I take it to UBreakIFix. They did a free diagnostic test and I referenced https://support.google.com/pixelphone/forum/AAAAb4-OgUsIW_gxTpXX3s/?hl=by that thread. Said they'd fix it for free even thought I was out of warranty. Got a new motherboard and my phone works like a charm.
My Google Pixels microphone randomly died after some point in its lifespan, but happened recently. First i updated version to Android Q Beta 1 (and it was working all right on that version) but when i updated it to Android Q Beta 2 (microphone stopped working and whole UI experience was buggy, some apps not working, random restarts, etc...) but then i got it back on Android Pie, and it worked for few minutes into boot and died yet again... Then i installed custom ROM (Pixel Dust) with TWRP recovery and Root, but nothing of those helped, then i got it back on Android Pie via adb sideload OTA. That didn't help either... So i don't know is it the software problem (because it seems to work first few minutes after i boot it) or is it the hardware problem. I use my phone mostly for phone calls and now because microphone is dead, it lost its functionality... But speaker was working,earpiece and 3.5mm jack.. Any suggestions??
i'm having a similar problem at the moment. Since the April OTA update, phone calls stopped working. Even when using a BT headset. I tried reverting to Full Recovery Image from february, but that only helped a bit. Also, any other audio app was not able to use the speaker. With the Feb version, youtube and google music were back working, but phone calls are still not possible, causing the telephone app to freeze. I was thinking about installing some custom rom too, but that doesn't seem to do the trick. Did you try to wipe the cache in recovery?
Update
found three possible workarounds for people having the same issue, perhaps one of those helps. I'll go through them today evening.
You could try enabling the "Disable USB audio routing" in developer options and see if that works for you. It did work for me
Click to expand...
Click to collapse
A couple of days ago one of the CEs here pointed out to me that I needed to enable the setting for wired headphones in Google Settings > Search, Assistant & Voice > Voice > Hands Free and toggle on the ‘wired headset’ setting,
Click to expand...
Click to collapse
Change your launcher, for example, on nova launcher, disallow permission to microphone for google app and never let him this permission, do not use google assistant.
Click to expand...
Click to collapse
LaTerminator said:
My Google Pixels microphone randomly died after some point in its lifespan, but happened recently. First i updated version to Android Q Beta 1 (and it was working all right on that version) but when i updated it to Android Q Beta 2 (microphone stopped working and whole UI experience was buggy, some apps not working, random restarts, etc...) but then i got it back on Android Pie, and it worked for few minutes into boot and died yet again... Then i installed custom ROM (Pixel Dust) with TWRP recovery and Root, but nothing of those helped, then i got it back on Android Pie via adb sideload OTA. That didn't help either... So i don't know is it the software problem (because it seems to work first few minutes after i boot it) or is it the hardware problem. I use my phone mostly for phone calls and now because microphone is dead, it lost its functionality... But speaker was working,earpiece and 3.5mm jack.. Any suggestions??
Click to expand...
Click to collapse
Maybe is a kernel error..but definitely is not a hardware problem. maybe try changing kernels. o downgrading to 7.
since none of the above tricks worked in my case, i booted TWRP to clean the caches. Didn't bring any good result. So i flashed ElementalX Kernel and now i got some kind of a better result, even if it's still weird. Everything works now except incoming calls. I can actively call other persons, use whatsapp or facebook audio calls and all is good. Only if i receive calls, still mic is muted.
I will try everything from above, and hopefully something will actually work and get my Pixel back in life. I will get you updated guys.
Thanks for the support.
toxic_garden said:
i'm having a similar problem at the moment. Since the April OTA update, phone calls stopped working. Even when using a BT headset. I tried reverting to Full Recovery Image from february, but that only helped a bit. Also, any other audio app was not able to use the speaker. With the Feb version, youtube and google music were back working, but phone calls are still not possible, causing the telephone app to freeze. I was thinking about installing some custom rom too, but that doesn't seem to do the trick. Did you try to wipe the cache in recovery?
Update
found three possible workarounds for people having the same issue, perhaps one of those helps. I'll go through them today evening.
Click to expand...
Click to collapse
None of those helped so far, i'll try flashing some kernel then...
I discovered that when i try to record with my camera video, it says "Can't record audio. Another app is using the mic." Also when i try to record audio message on Messenger app, as soon as i click on microphone icon it says some error.
Update, my sound and video won't record, both on Youtube or Instagram or any kind of video audio playback.
Update
I flashed ElementalX kernel and same stuff happened, phone calls and microphone was working for first 30 minutes then it got back to old days, not working as usual. Now i think this is hardware problem
LaTerminator said:
Update
I flashed ElementalX kernel and same stuff happened, phone calls and microphone was working for first 30 minutes then it got back to old days, not working as usual. Now i think this is hardware problem
Click to expand...
Click to collapse
have you tried chaging vendor image, or getting a vendor image from a working pixel?
I installed lineageos 16 without gapps and is working good for hours until installed gapps.
ericksidaroth said:
have you tried chaging vendor image, or getting a vendor image from a working pixel?
Click to expand...
Click to collapse
how do i change vendor image actually??
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.