Calls not connecting on AOSP ROM - Xiaomi Poco X3 NFC Questions & Answers

Just flashed Resurrection. Everything is cool except my calls don't connect. When I dial, the call immediately ends. If I toggle airplane mode a few times the call will finally connect. I figured this is an AOSP thing. Does anyone know of a fix?
Metro pcs is my service provider by the way

Bump.. been checking around and I've found nothing. However I'm able to dial Google voice numbers without issue

DonSolo said:
Does anyone know of a fix?
Click to expand...
Click to collapse
I know a fix, but you're not going to like it. Flash something else. See if the problem persist. If not, boom, problem fixed. If yes, make a log. Post it in the ROM thread together with problem description. Wait for fix.
edit:
If the same problem persist also on another ROM could be also HW problem.

jeryll said:
I know a fix, but you're not going to like it. Flash something else. See if the problem persist. If not, boom, problem fixed. If yes, make a log. Post it in the ROM thread together with problem description. Wait for fix.
edit:
If the same problem persist also on another ROM could be also HW problem.
Click to expand...
Click to collapse
I actually love flashing new ROMs lol. Unfortunately flashing a different rom didn't help. Same thing is happening. I ended up flashing Official Android 11 Pixel Experience.
At this point I'm sure it's an AOSP thing or custom ROM (don't think it's HW atm). When my bootloader was locked for the "168 hour" wait period I was able to make all of the outbound calls I wanted. I'll post some logs in both threads just for the record while I continue to find a fix.

I've found a workaround for my issue. I installed an MIUI ROM. I've been able to make calls without issue.
Not sure why MIUI allows me to dial out and AOSP doesn't. If anyone can chime in, that would be awesome. Otherwise I'll rock with MIUI ROMs for the time being.

DonSolo said:
I've found a workaround for my issue. I installed an MIUI ROM. I've been able to make calls without issue.
Not sure why MIUI allows me to dial out and AOSP doesn't. If anyone can chime in, that would be awesome. Otherwise I'll rock with MIUI ROMs for the time being.
Click to expand...
Click to collapse
I am now on pixel experience android 11 rom.I am also facing the same issue.Should I shift to miui rom?

Mushfiq Khan said:
I am now on pixel experience android 11 rom.I am also facing the same issue.Should I shift to miui rom?
Click to expand...
Click to collapse
Pixel Experience hasn't been updated for a long time if I'm not mistaken.
I personally use ArrowOS 12.1 and have no issues. Even automatic call recording works for me

Noter2017 said:
Pixel Experience hasn't been updated for a long time if I'm not mistaken.
I personally use ArrowOS 12.1 and have no issues. Even automatic call recording works for me
Click to expand...
Click to collapse
I was previously on awaken os android 13 version.I noticed this call problem when I was on that rom.So I shifted to pixel experience.
But I just turned off Volte toggle and now calls are seems to be working.So could it be issue from my network provider side?

Mushfiq Khan said:
I was previously on awaken os android 13 version.I noticed this call problem when I was on that rom.So I shifted to pixel experience.
But I just turned off Volte toggle and now calls are seems to be working.So could it be issue from my network provider side?
Click to expand...
Click to collapse
To be absolutely sure that it's your provider's fault, I would probably also flash MIUI to be 100% sure

Noter2017 said:
To be absolutely sure that it's your provider's fault, I would probably also flash MIUI to be 100% sure
Click to expand...
Click to collapse
Will any miui based rom work?Like Eu rom?

Related

Severe outgoing call issue

Hi,
Description of the problem : I am not able to hear, and my correspondant won't hear either, until I turn the loudspeaker on. However, when I turn it off again, It magically works. Also, no problem with ingoing calls.
I am able to hear a voicemail without this manipulation.
I tried different CM12 roms, and use the last firmware and google play services.
Anyone facing this issue? Is there a workaround?
thryy said:
Hi,
Description of the problem : I am not able to hear, and my correspondant won't hear either, until I turn the loudspeaker on. However, when I turn it off again, It magically works. Also, no problem with ingoing calls.
I am able to hear a voicemail without this manipulation.
I tried different CM12 roms, and use the last firmware and google play services.
Anyone facing this issue? Is there a workaround?
Click to expand...
Click to collapse
Have you tried a NON-CM12 rom ? Does it do that on CM11S ?
Cholerabob said:
Have you tried a NON-CM12 rom ? Does it do that on CM11S ?
Click to expand...
Click to collapse
I don't really want to put CM11s back on my phone, as I am not using MultiRom and love CM12. All I know is that It didn't happen back in the time when I was using CM11s.
This imply it could be either a CM12 problem or a google play services update problem, right ?
thryy said:
Hi,
Description of the problem : I am not able to hear, and my correspondant won't hear either, until I turn the loudspeaker on. However, when I turn it off again, It magically works. Also, no problem with ingoing calls.
I am able to hear a voicemail without this manipulation.
I tried different CM12 roms, and use the last firmware and google play services.
Anyone facing this issue? Is there a workaround?
Click to expand...
Click to collapse
I also have this issue which does not produce each time. I changed the kernel to Franco to see if something solve the problem and for now, I don't have any issue.
Try another kernel, just check if it's compatible with CM12.
Keep this thread updated if you find a permanent solution.
Seems i'ts a knew bug: https://jira.cyanogenmod.org/browse/BACON-729
Please register and vote for this bug!
MickyMax said:
I also have this issue which does not produce each time. I changed the kernel to Franco to see if something solve the problem and for now, I don't have any issue.
Try another kernel, just check if it's compatible with CM12.
Keep this thread updated if you find a permanent solution.
Seems i'ts a knew bug: https://jira.cyanogenmod.org/browse/BACON-729
Please register and vote for this bug!
Click to expand...
Click to collapse
Not sure if it's the same problem.. Mine started occuring 1 month ago, what's more, nobody mentioned the trick with on/off speakerphone to solve the issue temporarily.
I'm testing different ways of solving this problem, will update this thread when I find a permanent solution !
I have exactly the same issue. I have opened a jira bug here:
https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/NIGHTLIES-526
I found a LG3 user that has the same issue too on the CyanogenMod forum.
http://forum.cyanogenmod.org/topic/103756-silent-outgoing-calls/
---------- Post added at 05:51 PM ---------- Previous post was at 05:49 PM ----------
Cholerabob said:
Have you tried a NON-CM12 rom ? Does it do that on CM11S ?
Click to expand...
Click to collapse
CM11s or the latest CM11 nightly don't have this annoying bug.
@thryy So the solution is in order to get all outgoing calls working "Touch Sound" need to be activated. Settings ->Sound and notifications-> Other Sounds
dubazar said:
@thryy So the solution is in order to get all outgoing calls working "Touch Sound" need to be activated. Settings ->Sound and notifications-> Other Sounds
Click to expand...
Click to collapse
Thank you very much
It works fine now for me
Souleymane93 said:
Thank you very much
It works fine now for me
Click to expand...
Click to collapse
Problem is still there in latest nightly please vote and report here: https://jira.cyanogenmod.org/browse/NIGHTLIES-526 thanks
Voted!
Maybe related according the comments http://review.cyanogenmod.org/#/c/87378/
I just tried the new nightly 02.20 in order to make some new tests. It seems in my case that the issue was caused by the gapps I was using. In fact, with a new gapps package I don't have this issue for the moment. ?

[Q] Problems receiving calls and sms on CM12 nightly

Hey guys,
So I'm experiencing issues receiving calls and SMS on my OPO ever since I flashed a CM12 nightly in early February. I don't know for sure that CM12 is the issue because I can't find anyone that has a similar problem, but since the problem didn't start until after the initial clean install of CM12, I'd say this is a good place to start.
I'm currently running CM 12-20150223-NIGHTLY-bacon and have not changed anything else (kernal, xposed, etc...). I use AT&T and am located in the US.
SMS Problem: First off, I use Hangouts as my SMS application. Sometimes I will go hours without receiving any text messages, only to have a dozen of them all come flooding in at once. Usually this is prompted by me sending myself an SMS. I also occasionally have trouble downloading group MMS.
Call Problem: About 80% of the time, calls do not come through to me. My wife tells me the phone rings twice and then goes to voicemail. I do not receive any notifications of missed calls but if the caller leaves a voice mail, then I do get notified of that most of the time.
Does anyone know if this is strictly a CM12 nightly issue, or is something else going on? If the answer is just a full wipe and clean install of another ROM I'm ok with that, just wanted to get opinions from the community before I proceed.
Thanks in advance!
I am having the same issue with SMS. I am running the 20150225 nightly.
Bump.
Still having this problem. Is the only way to fix it to go back to KitKat?
You have described my exact problem to a T. Any updates on this issue? I am thinking about going back to CM11. Every nightly I update in hopes that it resolves this issue but it hasn't yet.
Zurtri said:
You have described my exact problem to a T. Any updates on this issue? I am thinking about going back to CM11. Every nightly I update in hopes that it resolves this issue but it hasn't yet.
Click to expand...
Click to collapse
No fix that I've found yet. Here is another thread on the issue that has seen more interaction than mine. http://forum.xda-developers.com/oneplus-one/help/cm12-delayed-messages-missed-calls-t3049583
Have you come across any fix yet?
Yesterday there were several updates related to mms..if you still use cm12...then install cynadelta app select last bacon zip. Then click on refresh, it will check the latest bacon file and update only incremental data..means you dont have to download entire rom. Saves your time and data package.
Once you see all the components are working.. Take backup using twrp and keep it in USB.. Incase you need to restore.
Click like if its helpful:thumbup:
Sent from my A0001 using XDA Free mobile app
solution?
NikoStone said:
Hey guys,
So I'm experiencing issues receiving calls and SMS on my OPO ever since I flashed a CM12 nightly in early February. I don't know for sure that CM12 is the issue because I can't find anyone that has a similar problem, but since the problem didn't start until after the initial clean install of CM12, I'd say this is a good place to start.
I'm currently running CM 12-20150223-NIGHTLY-bacon and have not changed anything else (kernal, xposed, etc...). I use AT&T and am located in the US.
SMS Problem: First off, I use Hangouts as my SMS application. Sometimes I will go hours without receiving any text messages, only to have a dozen of them all come flooding in at once. Usually this is prompted by me sending myself an SMS. I also occasionally have trouble downloading group MMS.
Call Problem: About 80% of the time, calls do not come through to me. My wife tells me the phone rings twice and then goes to voicemail. I do not receive any notifications of missed calls but if the caller leaves a voice mail, then I do get notified of that most of the time.
Does anyone know if this is strictly a CM12 nightly issue, or is something else going on? If the answer is just a full wipe and clean install of another ROM I'm ok with that, just wanted to get opinions from the community before I proceed.
Thanks in advance!
Click to expand...
Click to collapse
Hi! I har the same problem after updating to cm12. I solved it by go to settings/ mobile network/ preffered network and chose 3g. That worked for me. Much longer batterylife too.
Setting connection to 3g is not a solution, but a workaround. For those of use who actually use LTE/4G, that's not really an option.
I have this same issue, but I'm using Carbon ROM. So it would appear it is a CM-based issue that has carried over.
Edit: I was just in contact with my carrier Tele2, and this is a known issue with 4G/LTE systems. If you have this issue, contact your carrier, and they can likely help you sort it out.
cyruskane said:
I am having the same issue with SMS. I am running the 20150225 nightly.
Click to expand...
Click to collapse
NikoStone said:
Bump.
Still having this problem. Is the only way to fix it to go back to KitKat?
Click to expand...
Click to collapse
Zurtri said:
You have described my exact problem to a T. Any updates on this issue? I am thinking about going back to CM11. Every nightly I update in hopes that it resolves this issue but it hasn't yet.
Click to expand...
Click to collapse
NikoStone said:
No fix that I've found yet. Here is another thread on the issue that has seen more interaction than mine. http://forum.xda-developers.com/oneplus-one/help/cm12-delayed-messages-missed-calls-t3049583
Have you come across any fix yet?
Click to expand...
Click to collapse
nadeem.patel said:
Yesterday there were several updates related to mms..if you still use cm12...then install cynadelta app select last bacon zip. Then click on refresh, it will check the latest bacon file and update only incremental data..means you dont have to download entire rom. Saves your time and data package.
Once you see all the components are working.. Take backup using twrp and keep it in USB.. Incase you need to restore.
Click like if its helpful:thumbup:
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
lillsmartdude said:
Hi! I har the same problem after updating to cm12. I solved it by go to settings/ mobile network/ preffered network and chose 3g. That worked for me. Much longer batterylife too.
Click to expand...
Click to collapse
SweStag said:
Setting connection to 3g is not a solution, but a workaround. For those of use who actually use LTE/4G, that's not really an option.
I have this same issue, but I'm using Carbon ROM. So it would appear it is a CM-based issue that has carried over.
Edit: I was just in contact with my carrier Tele2, and this is a known issue with 4G/LTE systems. If you have this issue, contact your carrier, and they can likely help you sort it out.
Click to expand...
Click to collapse
Anyone that is still experiencing the issue please follow this link and vote this subject up.
https://jira.cyanogenmod.org/browse/BACON-3371
This is the bug log for Cyanogen and they just escalated the issue to critical.

Stable ROMs?

I'm on stock rooted MM and want a stable ROM since I've been having problems like sudden short freezes and now my internal storage says 96% full when it's not even close to that. I'm thinking of going back to Lollipop with MOAR v7. Is there any other stable ROMs you guys suggest?
I'm using cm and lineage and they are alright, cm from November has less bugs right now
What bugs are you seeing on Lineage?
jdinkel said:
What bugs are you seeing on Lineage?
Click to expand...
Click to collapse
Sprint variant, normal cm complaints early: SMS issues, some calling issues, can't cheat at pokemon go, 5ghz WiFi crashes for me 900p on lollipop bootloader...ok4 firmware
I went ahead and installed it this weekend. I'm not having any problem with 5ghz wifi, but I am having calling issues - when making or receiving a call the call screen just doesn't show up. The phone looks like I'm not even in a call but I'm certainly talking to someone on it. So I can't send any number presses (was impossible to navigate a businesses caller menu) and I can't hang up - either they have to hang up first, or I have to reboot my phone to know for sure it is hung up.
Other than that it is working great. Performance seems better and I'm loving the Pixel launcher. I don't see any sms issue, but I do all sms through Google Voice/Hangouts. The phone issue is going to force me back to CM13 though.
jdinkel said:
I went ahead and installed it this weekend. I'm not having any problem with 5ghz wifi, but I am having calling issues - when making or receiving a call the call screen just doesn't show up. The phone looks like I'm not even in a call but I'm certainly talking to someone on it. So I can't send any number presses (was impossible to navigate a businesses caller menu) and I can't hang up - either they have to hang up first, or I have to reboot my phone to know for sure it is hung up.
Other than that it is working great. Performance seems better and I'm loving the Pixel launcher. I don't see any sms issue, but I do all sms through Google Voice/Hangouts. The phone issue is going to force me back to CM13 though.
Click to expand...
Click to collapse
Is it a bug in the. .looking at the screen thing? My cm flashes sometimes because it thinks Im looking at it or not
i7vSa7vi7y said:
I'm on stock rooted MM and want a stable ROM since I've been having problems like sudden short freezes and now my internal storage says 96% full when it's not even close to that. I'm thinking of going back to Lollipop with MOAR v7. Is there any other stable ROMs you guys suggest?
Click to expand...
Click to collapse
the internal storage issue youre having isnt ROM specific, its basically an issue with the ROM basically ghosting your internal storage and ignoring whats there by not looking at the table of contents. Ive been looking for a solution for this myself and not finding much. If i find a solution, ill post something up

Question Google Voice Issue on Xiaomi Android 11 Phones

Phone: Redmi Note 10 Pro Max, Poco X3 ProOS: Android 11, on MIUI 12.5 and MIUI 12
Issue:
When I pick Voice to be my default call redirecting app, it does not make calls.
The Phone app just stays stuck on dialing and never dials. Never rings on the other end either.
Sometimes, it causes the phone app to stop functioning altogether to the point that I have to restart the phone to regain functionality. I have sought help for the issue all over the internet and cannot seem to get any info on it.
I don't have an issue with going into Voice app itself and making the call over Wifi. It just will not redirect via the phone app, which was very convienient.
I believe it might be specific to Xiaomi phones, but then again, I used a Phone that uses Google Dialer, and it is the same result, albeit, it was also a Xiaomi phone with Global ROM containing Google apps as defaults.
I believe this to be an issue with Xiaomi ROMs. If I make the call from any other Android 11 ROM, the call works just fine.
Any assistance with this will be very helpful. Google Voice is my most used app on my phone.
No one else is having these issues? Or is it that people don't use Google Voice as much?
Given all permission it requires? Allow auto-start up? Is the phone you said working fine a Xiaomi phone with custom Rom Android 11?
If custom Rom works fine, then it's MIUI's problem.
If it's MIUI problem, ask in Xiaomi official forum or online customer support service.
If custom Rom still having issue, it might be Google Voice issue. Either hardware or software issue.
I have given it all the permissions it needs. And I do believe it might be a Xiaomi thing because I have installed other phone apps and they too can't work. I've posted the issue in Xiaomi forums.
I was hoping other people might be facing the same issue and could help with solutions
Try turn off MIUI optimization in developer menu and see if it works.
Maybe also try this
https://www.reddit.com/r/Xiaomi/comments/bqasnd
MIUI optimization is nowhere to be found in this ROM. I am looking to see how I can disable it otherwise.
Damionix said:
MIUI optimization is nowhere to be found in this ROM. I am looking to see how I can disable it otherwise.
Click to expand...
Click to collapse
Go into developer setting, scroll down to the botton, press the reset to default setting multiple times. Then the MIUI optimization should show up.
I saw that, and tried it several times but it would not appear.
Damionix said:
I saw that, and tried it several times but it would not appear.
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...eming-turn-on-miui-optimization-gone.4254555/
pl1992aw said:
https://forum.xda-developers.com/t/...eming-turn-on-miui-optimization-gone.4254555/
Click to expand...
Click to collapse
Thanks. That made it show up. I tried the call with optimization off, same thing. Optimization on, and still the same thing. I think it's a problem with Miui itself. Something in Miui is blocking voice from making calls when it's being redirected.

Question Every custom ROM used receiving call goes down after 30 seconds.

Hi, would like to ask for some help to the community because every ROM i've tested, Arrow, Pixel Experience, etc etc i have an issue regarding receiving calls. When someone calls me, after 30 seconds call goes off. If i am the one who calls, all seems fine.
How can i make a better report for what is happening to me? I have no idea why this happens.
Now i tried ACIP ROM, and the same happened. Just after a clean install, the only ROM that this doesn't happen is MIUI latest. I am completely losing hope on using custom ROMS. Would love some help to log or whatever.
Is 30 seconds a time to screen off?
I observe similar behavior in Lineageos, but it is only screen off, not disconnect.
No, just the call. between 20 - 30 seconds it just disconnects.
Try turning off Wifi-calling
i_sagnik said:
Try turning off Wifi-calling
Click to expand...
Click to collapse
i will try that, but i don't think that comes by default.
Is there anyway i can log the moment it happens so i can post it here?
hfmls said:
i will try that, but i don't think that comes by default.
Is there anyway i can log the moment it happens so i can post it here?
Click to expand...
Click to collapse
Wifi calling caused my phone to double call, it would call hang up then call again.
Maybe its a network provider issue?
Have you tried format data and also if you use Wifi calling do calls get disconnected ?
I dont use wi-fi connection.
Strange that Miui works fine. Is there a way i can make a log?
still having this issue, any thoughts on this? how to debug it?
have you tried using other cards or networks?
@OP - is the phone still under warranty? Sounds like a hardware connection problem.
plskillme said:
@OP - is the phone still under warranty? Sounds like a hardware connection problem.
Click to expand...
Click to collapse
i thought that, but using MIUI works fine. Any custom ROM it doesn't.
hfmls said:
i thought that, but using MIUI works fine. Any custom ROM it doesn't.
Click to expand...
Click to collapse
Bruh that's weird, i've never experienced apps like this going ape crazy in the long run of me installing ROMs from here in XDA. Everything works fine except in all the custom ROMs
Ever tried to backup that "working" phone app and installing it on the custom ROMs?
Not sure if there's a way to log that event if ever you want logs to be saved and documented for troubleshooting.
hfmls said:
I dont use wi-fi connection.
Strange that Miui works fine. Is there a way i can make a log?
Click to expand...
Click to collapse
https://f-droid.org/repo/com.dp.logcatapp
Set Filter for errors, save output to file and analyze on a another device or try live? You could try to call somebody with speakers enabled while watching logcat
edit: forgot to mention - settings->buffers release don't stupidity

Categories

Resources