Volte restarting - Xiaomi Mi A1 Questions & Answers

I am currently using latest RR build and previously used LiquidOS. Every time i try to make call or every time i receive any call the volte service restart it started after i flashed android LOS. does anyone know why is this happening

+1

I've got solution. Just remove ims.apk from /system/app/ims and reboot.

Related

CM 12.1 calling problem

First of all hello everyone..!
this might seem like a noob questions, but the issue I am facing are real..
I installed the latest update of cm 12.1 yesterday "cm-12.1-20150911-UNOFFICIAL-ms013g-ver_AIO"..
I had been using "cm-12.1-20150614-UNOFFICIAL-ms013g-ver4_2" till yesterday
and overall, all the improvements in the latest ROM are fantastic..
ISSUE: right from my first boot, every time I get a call, and end it, it just doesn't hang up and the phone just shows the error: com.android.phone has stopped, and right after I click okay another error pops up: Dialer has stopped working
and then I neither can hang up the current call, nor I can make/take another call, the contact name of the first caller also gets stuck on the screen...until I restart the phone..and then it happens all over again..!
i.e.: A called me first, hanged up and the error appeared, now even if B calls me, the screen shows A calling, and I can't answer or reject the call..!
Can anyone please tell me how to get past that?
Flash the latest CM12.1 by Mukul SOni or Aapav

CM reboots when making or receiving calls :confused:

Hi guys, I had to give up using CM Roms since the phone reboots every time I try making a call or receive one, I understand there is some king of bug with the dialer framework included in the GAPPS package and that installing the Google Dialer from the play store should solve it but in my case i hasn't. This is what I've tried to no avail:
- Intalled Google DIaler from PlayStore/APK and set it default with all the permissions enabled.
- Installed Google Dialer apk as system app and set it default with all the permissions enabled.
- Installed the full GAPPS package.
- Removed the stock dialer and did all things above.
Hope someone can help me out here,
Thanks.
This happens when you have multiple phone dialer apps enabled. To use any other dialer than the included (when you flash Gapps Tiny or Micro which is recommended since the bigger packs replaces the CM app).
If you don't like the CM one, you should still flash a smaller Gapps and then disable CM dialer and download the one you want. If you already flashed a bigger Gapps, you should format system, cache and dalvik/arts partition and then reflash CM and then the smaller Gapps.
Should be enough to go settings, apps, click the gear weel (next to 3 dot menu), choose standard apps from this menu and determine your dailer as standard app..
This is a classical issue..
Sent from my OnePlus2 using XDA Labs
Sam Nakamura said:
Should be enough to go settings, apps, click the gear weel (next to 3 dot menu), choose standard apps from this menu and determine your dailer as standard app..
This is a classical issue..
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Hi Sam, that's what I mean when I've set it as default.
pitrus- said:
This happens when you have multiple phone dialer apps enabled. To use any other dialer than the included (when you flash Gapps Tiny or Micro which is recommended since the bigger packs replaces the CM app).
If you don't like the CM one, you should still flash a smaller Gapps and then disable CM dialer and download the one you want. If you already flashed a bigger Gapps, you should format system, cache and dalvik/arts partition and then reflash CM and then the smaller Gapps.
Click to expand...
Click to collapse
Hey pitrus, this issue actually started while only having CM dialer installed since I mainly flash pico gapps.
Will try it again since its been like a month since I gave up on it. Let you know later.
J3RI3L said:
Hi Sam, that's what I mean when I've set it as default.
Click to expand...
Click to collapse
Well, okay.. Thanks for clarification :good:
Maybe you'd like to give Banks a shot, I think it's worth to try...
https://download.dirtyunicorns.com/gapps/Banks/
I never had this specific problem, only when it wasn't set to be default but a also only use one dailer.. The one that is default on cm based roms..
Sent from my OnePlus2 using XDA Labs
Guys I've had no luck, tried with a clean install of CM14 and still facing the same problem. Just today did a CM14.1 install and it is still present for me.
I guess that I could flash just CM and not gapps but I rely on Google services for a lot of stuff. Will keep trying though.
I'm having the exact same problem, random reboots during calls only, sometimes I don't even have time to answer. I'm running CM13 and only have one phone app, also set as default. When running stock and Cyanogen all was fine, this only started after flashing CM13.
Developemt for Cyanogen stopped that's why I switched, maybe coming from another rom is causing this? I did a full wipe when flashing and have updated to several nightlies and the problem remains. Maybe I'll try another rom and test it for a while.
Installed Dirty Unicorns a few days ago and the problem seemed to have been fixed, but yesterday it started acting out again. Is there a way to check if this problem is hardware related?
I'm now doing a factory reset and installing Oxigen hoping that'll fix this once and for all.
It's a problem related to Gapps
rtorresz said:
Installed Dirty Unicorns a few days ago and the problem seemed to have been fixed, but yesterday it started acting out again. Is there a way to check if this problem is hardware related?
I'm now doing a factory reset and installing Oxigen hoping that'll fix this once and for all.
Click to expand...
Click to collapse
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
J3RI3L said:
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
Click to expand...
Click to collapse
Sounds like you flashed the full version of Gapps instead of the recommended Nano or Micro which does not replace the dialer app with Googles own, try the smaller Gapps and you should be ok.
pitrus- said:
Sounds like you flashed the full version of Gapps instead of the recommended Nano or Micro which does not replace the dialer app with Googles own, try the smaller Gapps and you should be ok.
Click to expand...
Click to collapse
I've installed them all with the same result, last time I was using Pico Gapps with Seraph's CM14 and it happened eandomly, sometimes I could make and receive calls normally but a most of the time it would reboot as soon as the phone started ringing.
Currently I've tried a lot of solutions so I'm not really sure of what's wrong.
J3RI3L said:
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
Click to expand...
Click to collapse
I flashed the latest OOS and now things are only a little bit better, instead of reboots I get dropped calls and a "No available network" message. This seems to happen only when I'm on a 3G or 4G network, if I change to a 2G network I can make calls without problems. This is driving me crazy, I've tried almost everything and I can't see what I'm missing.
rtorresz said:
I flashed the latest OOS and now things are only a little bit better, instead of reboots I get dropped calls and a "No available network" message. This seems to happen only when I'm on a 3G or 4G network, if I change to a 2G network I can make calls without problems. This is driving me crazy, I've tried almost everything and I can't see what I'm missing.
Click to expand...
Click to collapse
Its happening to me as well just as you describe it. It is very weird. In thinking of flashing the stock OOS 2.2.0 just to check whether it makes any diference.
Yesterday I restored my phone back to stock, but the problen remains.
This definitely has something to do with mobile data. If I disconnect mobile data I can make calls without any problem, when I'm connected to a wifi network too (I'm guessing because the phone has no need to use mobile data).
Some suggest that this might be related to VoLTE and operators not supporting it, but I can't find anyway to see if this is even exists or if its activated in OOS.
Later today I'll try Hydrogen and see what happens.
UPDATE: Flashing Hyrogen didn't solve the issue, calls keep dropping when mobile data is activated on LTE network.
UPDATE 2: Going back to OOS 2.2.1 didn't solve the problem either.
Kinda solved now
rtorresz said:
Yesterday I restored my phone back to stock, but the problen remains.
UPDATE: Flashing Hyrogen didn't solve the issue, calls keep dropping when mobile data is activated on LTE network.
UPDATE 2: Going back to OOS 2.2.1 didn't solve the problem either.
Click to expand...
Click to collapse
It seems I have solved my problem with the reboots and I think might help with your droped calls as well.
Firstly I flashed this OOS 3 firmware https://www.androidfilehost.com/?fid=24591020540821656, it comes with a hybrid TWRP, after that flashed the official CM14.1 and pico Open Gapps.
I think the firmware file did the trick or maybe it was the recovery since I haven't had a reboot in the past 2 days when receiving calls or making them.
Hope it helps
It's been a few days since I tried the last solution and so far my problem seems to be solved.
What worked for me was flashing the latest modem from H2OS 2.5 which also is supposed to enable VoLTE, but I can't confirm this since my carrier does not support VoLTE yet. To do this I first flashed CM 14.1 and then the modem, it worked fine since the first boot. Since my battery life wasn't the best in Nougat I went back to CM13 and the phone is still working fine.

Lose signal after every call

I install linageo 14.1 and had data bug so igot back to cm 13, but now every time a call finished, i lose signal!
i flash every posible rom, stock cm linageo all and had the same problem!
Any idea?!
Try reflashing stock with RSD lite. It looks like it's a radio image problem.
Other thing I noticed us that only can make calls with late selected or active, but every time it finish lost signal! I will try rsd to lollipop, I read something about volte but it's so wired that happens in all roms i check
I noticed just now it happened to me also on stock rom!what can cause this?

Can't make calls after switching to diff. Custom ROM

Call ends automatically after dialing.
I was on OctOS latest build and I switched to RR latest, I restored apps and data everything was fine but then I found out I couldn't make calls. I tried updating OpenGapps, downgrading RR, then switching back to OctOS again.
I clean flashed OctOS again, didnt work. Tried switching sims, didnt work.
When I dial a number on my sim, do not disturb logo appears and call automatically ends
IMEI is not corrupt/damaged, I checked and it's still valid. I tried other phone apps, same problem

Incoming call issues On HavoC and Aex

hey,
is there any one experiencing incoming call issue , from other end if someone calls rings from their side but on phone there is no ring is coming and that calls goes to voicemail
I get that sometimes but only when my phone has been locked for a long time. Feels like calls don't come in because of some doze setting.
Have you find any workaround? i tried to dissable magisk and xposed then also its exist so it not doze issue right ?
alwynjoshy said:
Have you find any workaround? i tried to dissable magisk and xposed then also its exist so it not doze issue right ?
Click to expand...
Click to collapse
Unfortunately I haven't found any solution. It still happens to me sometimes when my phone is locked for a while.
Now i. Am using non treble AeX rom, its okay still now no issues
Try change "preferred network type" to Global. Doing that solved the issue for me.
Some dirty flash updates can cause those issues. I have 2 backups, and one of them is creating this issue. Selecting Global as @christoophat proposed didn't fixed the issue in the failing backup. It actually was always configured as Global. Encryption has nothing to do. Clean flash worked fine. You all having this issue can test it by doing a TWRP backup of your data partition, wipe dalvik/cache/data and reboot. You don't need to go through all the google setup just skip all and test your incoming call.
Oki said:
Some dirty flash updates can cause those issues. I have 2 backups, and one of them is creating this issue. Selecting Global as @christoophat proposed didn't fixed the issue in the failing backup. It actually was always configured as Global. Encryption has nothing to do. Clean flash worked fine. You all having this issue can test it by doing a TWRP backup of your data partition, wipe dalvik/cache/data and reboot. You don't need to go through all the google setup just skip all and test your incoming call.
Click to expand...
Click to collapse
Since I never dirty flash, never even do backups, not sure why you think that here.
And no, my phone (until the latest clean install of LOS 07/23 build I did last night) has never been set as Global default before on this phone, but either LTE/GSM or just LTE
I just tell you what worked on my phone, up to you to try or not. :highfive:
christoophat said:
Since I never dirty flash, never even do backups, not sure why you think that here.
And no, my phone (until the latest clean install of LOS 07/23 build I did last night) has never been set as Global default before on this phone, but either LTE/GSMA or just LTE
I just tell you what worked on my phone, up to you to try or not. :highfive:
Click to expand...
Click to collapse
Sorry @christoophat, I wasn't answering you since you hav already found your fix. As you, I was adding info to bring some light to the issue, thinking on the other members still having the issue. I was asking them to try other things so we all could figure out all the possible causes of this behavior. I am in T-Mobile USA and I don't have the issue. I had to recover an old backup to reproduce the issue.
I am also on TMo USA too.

Categories

Resources