Related
Hi folks
I have a Nexus S (i9020a). It has stock 4.1.2 Jelly bean from Google (downloaded the stock image and flashed it). It worked fine for over a month.
Suddenly few days back this device got a problem. When I dial any number I can't hear any dialing sounds and even after the call has connected I can't hear the opposite person and the opposite person also can't hear me (The phone still shows as 'Dialing' though it's already connected). The same is true when I answer any call. Both parties can't hear anything.
This is solved by rebooting the phone for the first phone call only. After I reboot, the 1st phone call works fine, then this problem persists for any calls I make/receive until I reboot the phone again.
I tried flashing a different radio but this problem is still there. I tried my sim card on a different phone and it works fine, so the problem is not that too. My 3G data works just fine.
I need this phone for the next few days/weeks (hopefully not months) before my Nexus 4 gets delivered :laugh:
Thanks..
Edit: Modified the title; Probably gave the wrong meaning that the problem is solved.
<bump> Modified the title. Earlier title gave an impression that the problem is solved whereas I still have a problem.
Have you installed any apps which could somehow affect the dialler?
Unless someone else can give you a different advice, I can't think of any other option than do a full wipe and reflash.
I haven't installed any such apps.
Also, I already did a full wipe and flashed the stock image again. The problem is still there.
Don't know what else you could try, sorry mate - hope someone else can help you sort it out!
Thanks for trying. I think I will go to some hardware shop and see if they can figure out..
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
ej8989 said:
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
Click to expand...
Click to collapse
That's the first thing that I tried... doesnt work.
mailrachit said:
That's the first thing that I tried... doesnt work.
Click to expand...
Click to collapse
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
_android_ said:
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
Click to expand...
Click to collapse
Thanks for the suggestion!
I tried this too but doesn't work...
Try any custom ROM instead of stock ROM and a different kernel too. There could be chances that you've flashed the wrong ROM / radio too.
Sent from my Nexus S
Problem solved.
I went to a hardware store today. The guy said that it's a problem with the 3G service of my carrier (Vodafone India). The moment I enabled the '2G only' option in the Mobile networks settings area, this problem was gone. The technician said that this issue is affecting some people randomly. He said that since 3G service was launched just last year, the networks are not yet capable of handling all kinds of devices (he claims that the bug is so erratic that another Nexus S i9020a may work just fine with the very same bootloader/radio/rom which doesn't make any sense). When I said that 3G service was working fine before, he said that most probably my carrier changed some settings on their side which is causing this issue for me.
I have tried this for 6-8 hours now, making a lot of phone calls and it seems that the issue is gone. It saddens me that I am off 3G for now but at least my phone calls and basic EDGE internet works fine. I will have to work with Vodafone to solve this or simply wait for my new phone (Nexus 4) and hope it won't have the same problem..
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
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...
Guys, this issue has been pestering for a month now and I seem to have not found a fix for this yet. I first started to notice the problem with my phone when I was unable to attend the calls, the screen will usually get stuck or i will not be able to swipe up the green button during the call. Even if sometimes I manage to i will be able to hear the other person speak but I wont be able to speak to them. So sometimes once I restart the phone it will seem to work fine for an indefinite period of time and again it starts.
Then things started getting very bad, sometimes during normal device usage, the screen just turns to a monochrome black and white screen ( just as you see when there was no signal on older television sets). And when I switch to the bootloader screen, when I power the device on, I get a very thin green line for an instant on the screen and then the booting sequence starts.
I have made a lot of factory resets and stock image flashing, and by far I noticed one considerably situation, the times when the sound functions fine, the booting sequence where the 4 google dots animation appears and when there is no sound, the booting sequence gets stuck on Google and made by Google screen.
Other observations are during abnormal device behavior, no function related to sound will properly. To elaborate it, Google assistant wont work, videos cannot be played and even the system sounds wont be heard. I am open to suggestions here. Please let me know what can be done to test the phone out. FYI I know there is a problem with the Pixel microphone, but I am not convinced that its the exact problem. Please correct me if I am wrong. Thank you.
Sounds like a hardware defect. RMA if possible.
Sent from my Pixel using XDA Labs
It is a hardware issue indeed, I am facing the same issue, I contacted google , they told that replacement is possible tho I'm out of Canada at the moment so I'm just dealing with it through my Bluetooth earphones, everybody works fine with Bluetooth.
That's the only way I suppose!...did you get the phone directly from the Google store?...are they accepting phones bought from a retailer?...since I am in Singapore now...Google support is next to nothing here...try contacting them but it's of no use...only when I get to India I will be able to go forward with the replacement!.....but the thing is .... yesterday...I updated the phone to Oreo and the audio stopped working completely....and after repeated switching between safe and normal mode....the speakers are working now...but the microphone is still busted.
This happened to me, I was given a replacement phone from EE UK
Current update guys...as per the pixel support centre person's suggestion ...I rebooted the device to safe mode to check if the phone is operating normally ...which it did not....but surprisingly ...after restarting to normal mode ...it started working normally again...my query is how is this zeroed down to an hardware issue if in case it's perfectly working for a while and at some point goes bonkers...can you guys please enlighten me on this...coz I don't have much knowledge on the hardware field.
MK1207 said:
Current update guys...as per the pixel support centre person's suggestion ...I rebooted the device to safe mode to check if the phone is operating normally ...which it did not....but surprisingly ...after restarting to normal mode ...it started working normally again...my query is how is this zeroed down to an hardware issue if in case it's perfectly working for a while and at some point goes bonkers...can you guys please enlighten me on this...coz I don't have much knowledge on the hardware field.
Click to expand...
Click to collapse
hello, i am facing the same things as you do since updating to oreo, my question is how do i test everything in safe mode, to see if everything is alright as you did
ndiri said:
hello, i am facing the same things as you do since updating to oreo, my question is how do i test everything in safe mode, to see if everything is alright as you did
Click to expand...
Click to collapse
Tough luck mate! Sorry to hear that....you can check it out by pressing down the power button until you get the power off and restart menu. Keeping pressing down on the power off menu...it will reboot to safe mode without your prompt. In safe mode for me it was the same....maybe you will have a better luck...try it out!
MK1207 said:
Tough luck mate! Sorry to hear that....you can check it out by pressing down the power button until you get the power off and restart menu. Keeping pressing down on the power off menu...it will reboot to safe mode without your prompt. In safe mode for me it was the same....maybe you will have a better luck...try it out!
Click to expand...
Click to collapse
well, its been almost an hour the phone wont turn sound back on.
Keep switching it to and out of safe mode...at some point ideally at least the speakers must start lest the microphone. Tried contacting Google about it and no response at all...mine started acting weird only for the past month...I suppose from the Aug months patch update....tried reverting it back to previous stock versions...but I suppose the damage is permanently done
When I contacted google, they told me to send it back to Canada and let someone there give it to google.. which won't happen in my case , my phone also started acting like this after Oreo beta . Now I will restart the phone whenever it happens to get it back working :/
The only reason I am still sticking to this phone is coz of it's camera. Planning to get back to India around December to get this fixed. Support for pixel in Singapore now is next to nothing since it wasn't launched here. I had no problem at all with the Nexus line up but this is kind of a disappointment.
Alaadragonfire said:
It is a hardware issue indeed, I am facing the same issue, I contacted google , they told that replacement is possible tho I'm out of Canada at the moment so I'm just dealing with it through my Bluetooth earphones, everybody works fine with Bluetooth.
Click to expand...
Click to collapse
You've mentioned it as through Bluetooth it works fine....care to elaborate on this?...are you able to input voice commands to Google assistant and speak over calls using it ?...since I am planning to buy one in case its a perfect workaround
MK1207 said:
You've mentioned it as through Bluetooth it works fine....care to elaborate on this?...are you able to input voice commands to Google assistant and speak over calls using it ?...since I am planning to buy one in case its a perfect workaround
Click to expand...
Click to collapse
Yea, Bluetooth works fine for calls, as for google assistant voice command you can enable that from google app settings. Of course other media will be working with Bluetooth as music, YouTube, etc..
Alaadragonfire said:
Yea, Bluetooth works fine for calls, as for google assistant voice command you can enable that from google app settings. Of course other media will be working with Bluetooth as music, YouTube, etc..
Click to expand...
Click to collapse
Excellent!...thanks for the input....let me check and get myself one and I will have to manage with it till December....and are you able to connect to a laptop thru Bluetooth...coz I am unable to do so...it just says paired...but the bt symbol in the phone doesn't change to connected..did you try that out ?
MK1207 said:
Excellent!...thanks for the input....let me check and get myself one and I will have to manage with it till December....and are you able to connect to a laptop thru Bluetooth...coz I am unable to do so...it just says paired...but the bt symbol in the phone doesn't change to connected..did you try that out ?
Click to expand...
Click to collapse
Hmmm I don't remember connecting to a laptop via Bluetooth.. you mean for file transfer ? Anyway Bluetooth has nothing to do with the sound issue we are facing, it might be your laptop Bluetooth driver needs to be updated
Alaadragonfire said:
Hmmm I don't remember connecting to a laptop via Bluetooth.. you mean for file transfer ? Anyway Bluetooth has nothing to do with the sound issue we are facing, it might be your laptop Bluetooth driver needs to be updated
Click to expand...
Click to collapse
Just bought a Bluetooth headset....works fine for the most part...but sometimes during calls...the phone just hangs and it automatically restarts....sigh! pixel just can't be trusted to be my daily driver?
MK1207 said:
Just bought a Bluetooth headset....works fine for the most part...but sometimes during calls...the phone just hangs and it automatically restarts....sigh! pixel just can't be trusted to be my daily driver?
Click to expand...
Click to collapse
Sorry to hear so, I actually installed ElementalX kernel and it is less to happen. Try to flash the kernel.
Alaadragonfire said:
Sorry to hear so, I actually installed ElementalX kernel and it is less to happen. Try to flash the kernel.
Click to expand...
Click to collapse
Planning to do just that....I may have better luck with a custom kernel...will post an update once I have flashed it.
I had been on the 8.0 beta for a while. Then got 8.0.
Though just 2 days ago, my mic was starting to have issues. Then yesterday, only my speaker phone would work.
Now I can't get any audio/mic except though Bluetooth (I've got a portable speaker with a mic, and Bluetooth on my car.
Contacted Google support. Will be getting a replacement on their warranty.
They didn't tell me this, but I did some searching, and apparently many of the pixels (mostly from the first 3 months of production) had an issue with the soldering of the audio codec. though usage, little bumps here and there, that soldering can get loose. Which explains why my audio and mic were spotty, and within an hour yesterday morning, all aspects of it stopped working.
So, it's a hardware issue.
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.