Database Info

[SOLVED] Crespo 4.4.2 SMS inbound works but outbound doesn't. MMS is fine.

I've been pulling my hair out for a couple of weeks with this. SMS inbound + MMS inbound/outbound works. SMS outbound does not work.
This started when I upgraded to a CM11 nightly. I've also tried a pretty decent AOSP custom ROM (see http://forum.xda-developers.com/nexus-s/development/rom-aosp-kitkat-4-4-2-mod-nexus-s-build-t2410844) with the same result. No custom kernels have been tried, which leaves me to think that it must be related to the CM11 crespo kernel, as the AOSP custom ROM mentioned is based off of the CM11 kernel.
Using latest version CWM, I completely wiped (system, data, sdcard, cache, dalvik, you name it) and installed these ROMs. I've checked, double-checked and triple-checked the APN settings. I've gone into my mobile provider's store (Koodo, in Canada) and gotten them to test the SIM card in another phone - everything worked fine, so it's nothing on their end. They verified the APNs as well.
There have been other reports of this being an issue - see http://forum.xda-developers.com/showthread.php?t=2561308 for instance. They say that changing some setting in Voice+ (something that accompanies Google Voice?) is a good workaround... however, being in Canada prevents me from doing anything with Google Voice. I found the APK and manually installed it (can't install from Google Play as I'm in Canada), but couldn't sign into it, so couldn't see any settings. So, I'm left with NO outbound SMS until there's a fix or someone tells me what I can hack via terminal/shell. If there is anything.
Someone has also created a JIRA against CM11-M2-crespo (https://jira.cyanogenmod.org/browse/CYAN-3157) to which I added some details, but it's been closed for lack of a log file. Not sure how to create that, but will likely look into it soon.
Does anyone have any input? This is driving me nuts. Thanks.
EDIT: Added solution below.
Apparently this is a SIM card issue, related to the SMSC number. I have no idea how it got out of wack, but playing with the SMSC settings helped things to 'just work'. How to get into the SMSC settings screen:
- Dial *#*#4636#*#*
- Go into Phone Information
At the bottom of the resulting screen, you can try Refreshing. That seems to have done it for others. In other cases, they had to manually Update with a new number.

KitKang
Have you tried KitKang EurosKank's rom.
Because I have no problems with the SMS on it.

KnoMeNot said:
Have you tried KitKang EurosKank's rom.
Click to expand...
Click to collapse
No, I haven't - but I see it's using a CM11 kernel as well, so likely will exhibit the same problems... but I'll give it a shot tonight, along with any other suggestions people might have.
Thanks!

KnoMeNot said:
Have you tried KitKang EurosKank's rom.
Click to expand...
Click to collapse
Ok, I just tried EurosKank's cm-11-20140117.0925-crespo - exact same failed result. I'm so confused. How can it work for some people, but not others?

CM-11 testing for sm-t325 (mondrianlte), no radio support

I'm working on adding support for a WiFi only build of CM-11 for the SM-T325.
I am making no attempt at this time to add cellular support because I don't own the device and it would be very painful to try to do that without the device. However, a WiFi only version seems possible and I want to use this thread to validate that.
As a first step, I'm looking for people to test that this recovery works for them on a SM-T325: cwmr-20140528-mondrianlte.
You'll need to unzip the file and then flash it in Odin. If you don't know how to do that, then a test build is probably not for you!

Yes..it works!!!
crpalmer said:
I'm working on adding support for a WiFi only build of CM-11 for the SM-T325.
I am making no attempt at this time to add cellular support because I don't own the device and it would be very painful to try to do that without the device. However, a WiFi only version seems possible and I want to use this thread to validate that.
As a first step, I'm looking for people to test that this recovery works for them on a SM-T325: cwmr-20140528-mondrianlte.
You'll need to unzip the file and then flash it in Odin. If you don't know how to do that, then a test build is probably not for you!
Click to expand...
Click to collapse
i can confirm that this recovery does indeed function as expected...i installed my rom (ran into a weird "android is upgrading" bootloop but it eventually loaded...that may be my experimental multiwindow mod i'm using or the fact that i have completely deleted the touchwiz launcher) as well as created a backup (didnt restore) & all seems to be in order. I may be overreaching a bit about my abilities but im sure if u get a working wifi version going for us then the least i can do is get the cellular working...on a sort of related note would u happen to know if its possible to output through hdmi while in recovery mode? As far as this build is conncerned...anything else u may need tested just give me a shout
edit: looked for the backup which is usually on the internal sd (read:accessible from pc) and although the folder is there its empty...finally found it in "data-media-clockworkmod" & just wanted to know is this normal?

THEDEVIOUS1 said:
i can confirm that this recovery does indeed function as expected...i installed my rom (ran into a weird "android is upgrading" bootloop but it eventually loaded...that may be my experimental multiwindow mod i'm using or the fact that i have completely deleted the touchwiz launcher) as well as created a backup (didnt restore) & all seems to be in order. I may be overreaching a bit about my abilities but im sure if u get a working wifi version going for us then the least i can do is get the cellular working...on a sort of related note would u happen to know if its possible to output through hdmi while in recovery mode? As far as this build is conncerned...anything else u may need tested just give me a shout
edit: looked for the backup which is usually on the internal sd (read:accessible from pc) and although the folder is there its empty...finally found it in "data-media-clockworkmod" & just wanted to know is this normal?
Click to expand...
Click to collapse
That is normal (it is independent of users and /sdcard is specific to user 0 of the tablet).
If you want to work on the radio, you'll need to be able to build sm-t320. If you get that to build, I'll push up my current repos for the sm-t325.
Would you mind booting into recovery and grabbing a dmesg (/proc/kmsg) for me?
Hopefully I can post a cm 11 build in a couple of hours and we can see how that works.

crpalmer said:
That is normal (it is independent of users and /sdcard is specific to user 0 of the tablet).
If you want to work on the radio, you'll need to be able to build sm-t320. If you get that to build, I'll push up my current repos for the sm-t325.
Would you mind booting into recovery and grabbing a dmesg (/proc/kmsg) for me?
Hopefully I can post a cm 11 build in a couple of hours and we can see how that works.
Click to expand...
Click to collapse
either i dont know what i'm doing or adb isnt working properly in cwm...when i connect i get a weird "usb recognized but there's a problem" sound instead of the usual "affirmative" noise if that makes sense (windows)

Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.

crpalmer said:
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
Click to expand...
Click to collapse
I will give it a try. No mobile Internet with this rom, right? Which gapps I should use? Or is gapps for every rom the same?

works perfectly...thx
crpalmer said:
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
Click to expand...
Click to collapse
everything seems to be ok on my end although i cant test as thoroughly as i'd like to because my screen is screwed (broken lcd)...gps took a long time to track & still never redrew the map after it did but that was without high accuracy mode enabled & no data of course. Mic, camera, mhl/hdmi, sound, video playback, wifi, bluetooth (wait let me check...yep!), auto brightness, lid sensor are all working properly...so now i need your permission. Besides getting data working...i just want to know am i free to use this in a dual boot configuration with my rom & post it in my thread? Also...this is not important but do u know if screen mirroring works with the wifi version?

THEDEVIOUS1 said:
everything seems to be ok on my end although i cant test as thoroughly as i'd like to because my screen is screwed (broken lcd)...gps took a long time to track & still never redrew the map after it did but that was without high accuracy mode enabled & no data of course. Mic, camera, mhl/hdmi, sound, video playback, wifi, bluetooth (wait let me check...yep!), auto brightness, lid sensor are all working properly...so now i need your permission. Besides getting data working...i just want to know am i free to use this in a dual boot configuration with my rom & post it in my thread? Also...this is not important but do u know if screen mirroring works with the wifi version?
Click to expand...
Click to collapse
I don't know whether or not screen mirroring works. No one has complained but I don't have any way to test it.
You can (obviously) post a link to the thread. I would prefer that you didn't link to a specific version as I hope to post more test builds here (although so far only 3 people have downloaded it which shows either a lack of interest or a lack of early adopters).

crpalmer said:
I don't know whether or not screen mirroring works. No one has complained but I don't have any way to test it.
You can (obviously) post a link to the thread. I would prefer that you didn't link to a specific version as I hope to post more test builds here (although so far only 3 people have downloaded it which shows either a lack of interest or a lack of early adopters).
Click to expand...
Click to collapse
Hello, I will root my device and download the test build as well ! Will post back soon.
Thanks for trying to bring support for this device !

Bautinho88 said:
I will give it a try. No mobile Internet with this rom, right? Which gapps I should use? Or is gapps for every rom the same?
Click to expand...
Click to collapse
Sorry, I missed this post... Use the gapps from the sm-t320 thread.

crpalmer said:
Sorry, I missed this post... Use the gapps from the sm-t320 thread.
Click to expand...
Click to collapse
woohoo...well i got data working but calls are a no go as of right now. i can assure u the lack of activity in this thread is definitely not due to lack of intereset....more than likely its because its barely been a full day not to mention that there are not that many of us lte users but best believe once word gets round they'll come running. As far as my permission request...what i was thinking is that i'll just wait until the monthly releases start coming, make the proper changes for data (unless u actually make ours official also which would be awesome) & include it in a dualboot (hopefully multirom) setup. From what i've read ...alterations will need to be made to both kernels/roms which is why i was asking could i use it. I would definitely put a "use at your risk" disclaimer up as to not have the official thread flooded with issues not actually related to cm itself...let me know if u need anthing else on my end
edit: i do have one weird issue though...i copied the dialer app from another device with cm11 but it doesnt show up in the app drawer but is in fact found within the app manager in settings (i know i can just download another dialer but thought i would ask)
edit 2: calls not working yet & but i did get the phone app to appear & sms are also good to go (no mms at the moment)...got rid of the error message on outgoing calls (incoming wont even ring at all) but now it just force closes before it dials out (even with a different dialer)

THEDEVIOUS1 said:
woohoo...well i got data working but calls are a no go as of right now. i can assure u the lack of activity in this thread is definitely not due to lack of intereset....more than likely its because its barely been a full day not to mention that there are not that many of us lte users but best believe once word gets round they'll come running. As far as my permission request...what i was thinking is that i'll just wait until the monthly releases start coming, make the proper changes for data (unless u actually make ours official also which would be awesome) & include it in a dualboot (hopefully multirom) setup. From what i've read ...alterations will need to be made to both kernels/roms which is why i was asking could i use it. I would definitely put a "use at your risk" disclaimer up as to not have the official thread flooded with issues not actually related to cm itself...let me know if u need anthing else on my end
edit: i do have one weird issue though...i copied the dialer app from another device with cm11 but it doesnt show up in the app drawer but is in fact found within the app manager in settings (i know i can just download another dialer but thought i would ask)
edit 2: calls not working yet & but i did get the phone app to appear & sms are also good to go (no mms at the moment)...got rid of the error message on outgoing calls (incoming wont even ring at all) but now it just force closes before it dials out (even with a different dialer)
Click to expand...
Click to collapse
Here's a new build that has all of the telephony bits enabled. I haven't tried booting it (I'm at work, the tablet is at home) but it should have the dialer and all the other framework that is needed for telephony. Let me know if you get calls working with it:
cm-11-20140529-beta

crpalmer said:
Here's a new build that has all of the telephony bits enabled. I haven't tried booting it (I'm at work, the tablet is at home) but it should have the dialer and all the other framework that is needed for telephony. Let me know if you get calls working with it:
cm-11-20140529-beta
Click to expand...
Click to collapse
Can I use TWRP or must be done under recovery (cwmr-20140528-mondrianlte) from the first post?

megatooth said:
Can I use TWRP or must be done under recovery (cwmr-20140528-mondrianlte) from the first post?
Click to expand...
Click to collapse
twrp is fine. The recovery was just because the first step is to make sure that boots before bothering to get the whole system to boot..

I will install your latest build and return with impressions.
Edit: @crpalmer: Phone.apk/dialer is missing and I have no service.

megatooth said:
I will install your latest build and return with impressions.
Edit: @crpalmer: Phone.apk/dialer is missing and I have no service.
Click to expand...
Click to collapse
Yeah, I made no attempt to get the radio working, hence the title...
@THEDEVIOUS1, did you make any progress on modifying the build I posted to get voice working? If so, let me know what changes you've made and I'll see if I can incorporate them.

crpalmer said:
Yeah, I made no attempt to get the radio working, hence the title...
@THEDEVIOUS1, did you make any progress on modifying the build I posted to get voice working? If so, let me know what changes you've made and I'll see if I can incorporate them.
Click to expand...
Click to collapse
Long story short...still no voice. Now for the rest of it...i've gotten it to the point where i can dial out but neither the mic nor speaker works when the call is answered by the other party (i think this is due to the fact that it reports that the call ends as soon as it begins on my device). As far as receiving calls is concerned...NOTHING. I have even gone as far as flashing a note 3 modem (yeah i know...stupid :silly in an attempt to fix it & still no go...i just recently found the build prop edit to allow outgoing calls so hopefully the rest is as simple as editing the build prop. Speaking of which...getting data/phone working is NOT quite so simple but i've gotten it down to the bare minimum number of changes that need to be made. So far we need to add the "lib-qcril-hook-oem.so" from the n9005 cm11 rom & the "libsec-ril.so" as well "libril.so" from the stock T325 rom (which is enough by itself to get data working) as well as decompile the framework-res.apk & and change both the sms & voice config bools enable to true (which i'm sure there is a flag for in source)...this makes the phone app appear as well as allows u to send texts then we need to add the line "ro.telephony.ril.v3=newDialCode" to the prop which allows us to dial out. Well...thats where i'm at as of right now so its back to google for me to put together the rest of the pieces unless u have some insight from working on devices with radios that can be of some assistance

THEDEVIOUS1 said:
Long story short...still no voice. Now for the rest of it...i've gotten it to the point where i can dial out but neither the mic nor speaker works when the call is answered by the other party (i think this is due to the fact that it reports that the call ends as soon as it begins on my device). As far as receiving calls is concerned...NOTHING. I have even gone as far as flashing a note 3 modem (yeah i know...stupid :silly in an attempt to fix it & still no go...i just recently found the build prop edit to allow outgoing calls so hopefully the rest is as simple as editing the build prop. Speaking of which...getting data/phone working is NOT quite so simple but i've gotten it down to the bare minimum number of changes that need to be made. So far we need to add the "lib-qcril-hook-oem.so" from the n9005 cm11 rom & the "libsec-ril.so" as well "libril.so" from the stock T325 rom (which is enough by itself to get data working) as well as decompile the framework-res.apk & and change both the sms & voice config bools enable to true (which i'm sure there is a flag for in source)...this makes the phone app appear as well as allows u to send texts then we need to add the line "ro.telephony.ril.v3=newDialCode" to the prop which allows us to dial out. Well...thats where i'm at as of right now so its back to google for me to put together the rest of the pieces unless u have some insight from working on devices with radios that can be of some assistance
Click to expand...
Click to collapse
Can you send me a logcat of making a call?

crpalmer said:
Can you send me a logcat of making a call?
Click to expand...
Click to collapse
Keep an eye on this post...i just jumped off the deep in end & tried to install the hlte version as is (with kernel swap of course ) so it may take me a minute to get back (i have a nandroid but like to make the cjanges manually so i know the exact process & origin of files). Well i'll be damned...incoming calls work (complete with mic & speaker) with note 3 version of cm11! Outoing still seem to be an issue but this clears up a few gray areas i had concerning whether the ril files matched the modem & so on...i had the bright idea of swapping a few of the framework files then just thought they were so similar that the whole thing should boot. Anyway....shouldnt be long to figure out what the hold up is now bu tgive me a few & i'll post the log after i test a ouple of things then flash back to the other setup
edit: Aaaaaaannnnddd....done! added the line i spoke about in my previous post to the build.prop & now both incoming & outgoing calls are working with the N9005 version...just out of curiosity i'm about to go through & see whats broken the first of which i notice is rotation (i personally hate portrait) but seems like everything else is as well including wifi, camera, lid, bluetooth, & ironically speaker audio (video playback & apollo play no audio through loudspeaker...both work through wired headset). I will still get that logcat a lil later...at this point i dont think it has anything else to do with the build prop because i had already added most of the stuff i found missing in ours from the hlte & it didnt work. I'm thinking maybe another lib file that needs to be swapped...perhaps maybe something in framework

THEDEVIOUS1 said:
Keep an eye on this post...i just jumped off the deep in end & tried to install the hlte version as is (with kernel swap of course ) so it may take me a minute to get back (i have a nandroid but like to make the cjanges manually so i know the exact process & origin of files). Well i'll be damned...incoming calls work (complete with mic & speaker) with note 3 version of cm11! Outoing still seem to be an issue but this clears up a few gray areas i had concerning whether the ril files matched the modem & so on...i had the bright idea of swapping a few of the framework files then just thought they were so similar that the whole thing should boot. Anyway....shouldnt be long to figure out what the hold up is now bu tgive me a few & i'll post the log after i test a ouple of things then flash back to the other setup
edit: Aaaaaaannnnddd....done! added the line i spoke about in my previous post to the build.prop & now both incoming & outgoing calls are working with the N9005 version...just out of curiosity i'm about to go through & see whats broken the first of which i notice is rotation (i personally hate portrait) but seems like everything else is as well including wifi, camera, lid, bluetooth, & ironically speaker audio (video playback & apollo play no audio through loudspeaker...both work through wired headset). I will still get that logcat a lil later...at this point i dont think it has anything else to do with the build prop because i had already added most of the stuff i found missing in ours from the hlte & it didnt work. I'm thinking maybe another lib file that needs to be swapped...perhaps maybe something in framework
Click to expand...
Click to collapse
The outgoing call issue is likely just that the audio configuration is missing the use cases for voice calls. That's why I wanted the logcat because that should be easy to add.
When you're done with the hlte version (which is actually not a great idea for a daily driver as there are other things that are different that you may not notice (two biggest I can think of is that the hardware is different and several of the HAL libraries need to enable/disable different files in /sys/ and the networking configuration is different which may break some kernel/user-space interactions).
But if you can send me the logcat, the build.prop that you are happiest with and detailed information about anything else that you chnaged (e.g. exactly what you changed in frameworks so I'm not guessing) then I'll take a look at another test build.

[Q] Everything works except phone doesn't receive calls

Hey everyone,
I have a verizon s3, rooted and currently running the latest stable CM11. Everything works, I have internet and get sms/mms, and can also make calls. However I don't receive calls from known numbers. However unknown and private numbers come through (has happened once, but I have heard of others with this issue, so I assume that's what's happening here).
I'm in Israel, so I'm guessing that may have something to do with it possibly? However when we got the phone from a friend, and I put my sim card, and set the network to global, it worked. Only have I rooted it did it stop receiving calls.
Thought? Advice?
Many thanks.

Twan313 said:
Hey everyone,
I have a verizon s3, rooted and currently running the latest stable CM11. Everything works, I have internet and get sms/mms, and can also make calls. However I don't receive calls from known numbers. However unknown and private numbers come through (has happened once, but I have heard of others with this issue, so I assume that's what's happening here).
I'm in Israel, so I'm guessing that may have something to do with it possibly? However when we got the phone from a friend, and I put my sim card, and set the network to global, it worked. Only have I rooted it did it stop receiving calls.
Thought? Advice?
Many thanks.
Click to expand...
Click to collapse
I had the same problem with CM12 and AICP rom
I solved with this
d2gsm_rilblobs.zip
instructions
1 - install clean rom
CM12 or AICP
2 - install gapss
3-install modem
d2vzw_NE1_modem.zip
4 - flash zip
d2gsm_rilblobs.zip
restart and wait

So CM 14 is out for KLTE and is 90% stable, who wants to try on sprint?

Link to download it here (credit to AICP CM devs on their google plus page): https://plus.google.com/101577397694816898663/posts/GS4FcdKVomX
From the comments of the post, this is a write up of what is working:
I did dirty flash and all still works. I'd love to see a change log but I know that's asking a lot.
Boot time was fairly quick after flash approx 60 secs.
File explorer still can't see the sd card but as optix told me before, you can use rootbrowser app or just go to settings storage and you can see and manipulate sd.(I believe it's due to a superuser issue not related to ROM.)
BT worked fine for me last night on previous build except when not using it auto disconnected but as soon as media was played again it auto connected and plays normal. Will test BT further.
Also I know that cm theme manager is based on cm's C-apps and it's code base hasn't been updated to work in SDK 24 ie n-7.0 but I'm sure that will come soon.
There is a delay when connecting calls. The delay seems less when placing calls then when receiving. As long as the caller is patient it does connect. This might not be a Rom issue as I use Greenify and I've read some where that this issue had been encountered on other Roms.
As long as you can deal with the stock N theme, 20-30 ssecond call cconnect delay, and not having Xposed untill it's updated to work on SDK 24 then this is totaly daily driveable.
PS thank you to the Devs, please tell me how I can be of service helping or testing and I'm all yours.
Click to expand...
Click to collapse
Who wants to try?

not i, said the fly. still happy with MOAR 7.0

following nightlys
I have the sprint g900p and am following the nightlys build for cm 14, so far I've ran into a few issues, rotate doesn't always work, it is dependent on app. YouTube works but the stock cm chrome will not. Also I cannot send any SMS unless I force the radio to move from LTE to 3g.
And of course the SD card issue.
Just so you know, started with stock ROM, updated everything, clean Odin flash with twrp.
If you need any info let me know otherwise I'll post as I find bugs.

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.