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.
Related
I'm sorry to sound noobish, but every time I flash a ROM on my Nexus 4 (mako) that isn't a Cyanogenmod build (10.2-20130904-NIGHTLY-mako) , my home softkey becomes completely useless and the AOSP or AOKP keyboard constantly crashes. I was told this is a known bug in certain source codes as far as the keyboard is concerned in 4.2.2 builds, but I'm still mystified by the home button issue and as to why I other people can be using the same ROMs that I can't without a problem. Is there a certain version of GAPPS that I can flash to avoid this problem, or is there a known fix? I always wipe data and cache when flashing, so I'm pretty sure this isn't a user error, other than which version of GAPPS I'm flashing (gapps-jb-20130813-signed.zip).
trevorftard said:
I'm sorry to sound noobish, but every time I flash a ROM on my Nexus 4 (mako) that isn't a Cyanogenmod build (10.2-20130904-NIGHTLY-mako) , my home softkey becomes completely useless and the AOSP or AOKP keyboard constantly crashes. I was told this is a known bug in certain source codes as far as the keyboard is concerned in 4.2.2 builds, but I'm still mystified by the home button issue and as to why I other people can be using the same ROMs that I can't without a problem. Is there a certain version of GAPPS that I can flash to avoid this problem, or is there a known fix? I always wipe data and cache when flashing, so I'm pretty sure this isn't a user error, other than which version of GAPPS I'm flashing (gapps-jb-20130813-signed.zip).
Click to expand...
Click to collapse
The known issue you are talking about is the JSS deadlocks? if yes, then it is not the problem with you.. for you it force closes the keyboard.. are you following the procedure of installing rom properly? are you doing dirty flash (flash without wiping data)? you can find out if gapps is responsible by booting into a freshly installed rom without installing gapps and see if the problem persists..
You should also format the /system partition when you flash a new rom.
For some roms the Home button stop working for me and to fix it I had to install gapps, but most CM based roms I use don't have that issue.
As for keyboard, I always delete the default keyboard from the rom and use Google Keyboard.
Andre_Vitto said:
The known issue you are talking about is the JSS deadlocks? if yes, then it is not the problem with you.. for you it force closes the keyboard.. are you following the procedure of installing rom properly? are you doing dirty flash (flash without wiping data)? you can find out if gapps is responsible by booting into a freshly installed rom without installing gapps and see if the problem persists..
Click to expand...
Click to collapse
Please explain what JSS deadlocks are. I don't dirty flash. I always wipe data. As for the keyboard and home buttons not functioning properly,I have this problem with XenonHD, PACman ROM, AOKP and CM variants.
trevorftard said:
Please explain what JSS deadlocks are. I don't dirty flash. I always wipe data. As for the keyboard and home buttons not functioning properly,I have this problem with XenonHD, PACman ROM, AOKP and CM variants.
Click to expand...
Click to collapse
No your problem is not the jss deadlocks.. it happens when you type very fast or something.. it phone vibrates for like 5-10 sec and then restarts. I dont think its your problem. Sorry mate I have no idea why you are having the keyboard and homescreen issue even when you are are doing a factory reset every time you flash.. and why its not happening with CM 10.2..
Andre_Vitto said:
No your problem is not the jss deadlocks.. it happens when you type very fast or something.. it phone vibrates for like 5-10 sec and then restarts. I dont think its your problem. Sorry mate I have no idea why you are having the keyboard and homescreen issue even when you are are doing a factory reset every time you flash.. and why its not happening with CM 10.2..
Click to expand...
Click to collapse
Well, that's unfortunate. I've found that the RevoltHD ROM doesn't have problems, but that's because it's got integrated GAPPS.
Been having the same issue with my Nexus 4, after installing GAPPS the keyboard crashes and the home button stops responding. Did anyone figured it out by any chance? Thanks.
I still don't know what caused it, but I figured out that more recent nightly versions of those ROMs don't have that problem. I'm using AOKP currently and that used to be a problem ROM.
Take off vibration and sound and all the bells and whistles and your keyboard should be fine if the issue isn't Rom specific. Also, it could be kernel related.....try boosting touch input if nothing else
Sent by flying midget
I get the same problem, I factory reset each time I switch ROMs. I was trying with Vanir a couple of days ago and couldn't get the home button to work, tried OmniROM and it worked perfectly, went back to Paranoid it worked perfectly again, went back to Vanir and it didn't work. Was odd.
Hello Everyone,
Nexus 4
Paranoid Android 4.2Beta1
Franco Kernel
I just upgraded to PA 4.2Beta1 from PA 4.1.......
after installing the rom.....when i use my browser or messenger where we require keyboard....the Keyboard doesnt pop up....whats up with this....and also the back button of my navigation bar doesnt work.......this even happened with carbon rom a few days back...when i was experimenting with it.....but then i restored to PA4.1 due to the above given problems....plz offer a solution to this...
The same problem
keyboards not working
please help me my keyboards are not working . i have installed an custom rom.
i used to love miui for my I9500
but lately its causing me hell
i dont which update started it but my BT isnt working at all, once i switch it on and try to connect to any device its crashing
my cell signal goes kaput for a minute and then comes back, and it cycles all over again
same thing happens when i try to use wifi hotspot
i get crashes when watching youtube videos sometimes
i tried starting all over again, flashed a stock rom and then miui after wiping everything of course
and still after a fresh install it happens again
what am i doing wrong ?
maybe its my kernel ?
the only thing thats conssistent is after i flash a stock rom, i flash cwm recovery, does it comes with a kernel that could be not compatible with miui ?
is there a recommended kernel that should work better ?
AzurA86 said:
i used to love miui for my I9500
but lately its causing me hell
i dont which update started it but my BT isnt working at all, once i switch it on and try to connect to any device its crashing
my cell signal goes kaput for a minute and then comes back, and it cycles all over again
same thing happens when i try to use wifi hotspot
i get crashes when watching youtube videos sometimes
i tried starting all over again, flashed a stock rom and then miui after wiping everything of course
and still after a fresh install it happens again
what am i doing wrong ?
maybe its my kernel ?
the only thing thats conssistent is after i flash a stock rom, i flash cwm recovery, does it comes with a kernel that could be not compatible with miui ?
is there a recommended kernel that should work better ?
Click to expand...
Click to collapse
Yes, Somehow it is not stable yet maybe. My I9500 with the latest MIUI 5 4.12.5 suffer a few problem, but BT is ok, hotspot ok too. when turning on hotspot it will force close, but the hotspot is turn on e few seconds later.
the main problem is when I flash Gapps. the phone get freeze and restarted.
I tryed another release but the same problem still happen with Gapps. without GApps the phone works properly.
h6x said:
Yes, Somehow it is not stable yet maybe. My I9500 with the latest MIUI 5 4.12.5 suffer a few problem, but BT is ok, hotspot ok too. when turning on hotspot it will force close, but the hotspot is turn on e few seconds later.
the main problem is when I flash Gapps. the phone get freeze and restarted.
I tryed another release but the same problem still happen with Gapps. without GApps the phone works properly.
Click to expand...
Click to collapse
well about gapps
what i do is go into the bulit in Market app
type google play at the top
and download google installer
from there install what you need
AzurA86 said:
well about gapps
what i do is go into the bulit in Market app
type google play at the top
and download google installer
from there install what you need
Click to expand...
Click to collapse
I've tried it. but google play service doesnt work properly... so my phone live with no gapps... T_T
Hey guys.
I don´t wanted to create a thread about this but after some troubleshooting without a solution i don´t know what to do.
After i installed (i think it happens after that) kingmercians hydrogen os, i doesn´t matter which rom i use (cm13, cm12, aicp, ......) i got random reboots. I did´nt install any new app, tried it with gapps, without gapps.... Sometimes it happened right after the first boot of a new rom, sometimes while i restored via TB (no system apps!). It´s not reproducible for me.
I don´t want to make it factory fresh but i know this could be the last way.
Any suggestions?
Thanks in advance!
Trinaaa said:
Hey guys.
I don´t wanted to create a thread about this but after some troubleshooting without a solution i don´t know what to do.
After i installed (i think it happens after that) kingmercians hydrogen os, i doesn´t matter which rom i use (cm13, cm12, aicp, ......) i got random reboots. I did´nt install any new app, tried it with gapps, without gapps.... Sometimes it happened right after the first boot of a new rom, sometimes while i restored via TB (no system apps!). It´s not reproducible for me.
I don´t want to make it factory fresh but i know this could be the last way.
Any suggestions?
Thanks in advance!
Click to expand...
Click to collapse
Did you wipe before you installed new rom ? , also have to say that cyanogenmods like 12.1 and 13 are still unstable tried all myself too . I suggest you to wipe everything but not internal storage , after you installed those ROM's and gapps did you wipe ? also what gapps are you using ?
chrismomike said:
Did you wipe before you installed new rom ? , also have to say that cyanogenmods like 12.1 and 13 are still unstable tried all myself too . I suggest you to wipe everything but not internal storage , after you installed those ROM's and gapps did you wipe ? also what gapps are you using ?
Click to expand...
Click to collapse
First, thank you for your reply!
Yeah.... Every time i switch between roms i wipe everything, cache, data, dalvik and system. And after gapps, i wipe dalvik and cache.
The strange thing is, the roms i used before without any problems (installed for example razor rom which i still had on my internal memory) causes reboots. That never happens before.
Trinaaa said:
First, thank you for your reply!
Yeah.... Every time i switch between roms i wipe everything, cache, data, dalvik and system. And after gapps, i wipe dalvik and cache.
The strange thing is, the roms i used before without any problems (installed for example razor rom which i still had on my internal memory) causes reboots. That never happens before.
Click to expand...
Click to collapse
I installed H2O by king but didn't had issues I changed it because of the notification system , sometimes it took minutes untill I've got a notification on screen off ,and sometimes I had to open the app to see that I got notifications (apps like Whatsapp , Facebook messenger ), after that I installed cm 12.1 and 13 also , on both had problems on camera and rebooted every single time I opened Camera app and Wifi/Data change didn't always worked , they are still unstable I suggest you to install OxigenOS with boeffa kernel and try some of those profiles there my phone working way better than before http://forum.xda-developers.com/oneplus-2/general/unofficial-boeffla-kernel-profiles-t3289395 , or if you like custom ROM's what gapps are you using ?
chrismomike said:
I installed H2O by king but didn't had issues I changed it because of the notification system , sometimes it took minutes untill I've got a notification on screen off ,and sometimes I had to open the app to see that I got notifications (apps like Whatsapp , Facebook messenger ), after that I installed cm 12.1 and 13 also , on both had problems on camera and rebooted every single time I opened Camera app and Wifi/Data change didn't always worked , they are still unstable I suggest you to install OxigenOS with boeffa kernel and try some of those profiles there my phone working way better than before http://forum.xda-developers.com/oneplus-2/general/unofficial-boeffla-kernel-profiles-t3289395 , or if you like custom ROM's what gapps are you using ?
Click to expand...
Click to collapse
Thanks again for your clarification and suggestion!
I used open gapps mini. Used them on every rom. But yesterday i thought to go with OxySlim and the included Boeffla Kernel and yes, works like a charm! No reboots since 14 hours. Eyerything is like it should right now.
Trinaaa said:
Thanks again for your clarification and suggestion!
I used open gapps mini. Used them on every rom. But yesterday i thought to go with OxySlim and the included Boeffla Kernel and yes, works like a charm! No reboots since 14 hours. Eyerything is like it should right now.
Click to expand...
Click to collapse
Glad to help your welcome :good:
hey, i have random reboots and it always happens when I am in another location that is not my home. I thought that it was related to location and wifi but that is not the case. I clean flash and I accidentally wiped out my internal storage. My phone works now but please help
Hello all,
I am running the XT1768 variant, Qualcomm version, rooted with Resurrection Remix version 5.8.5 unofficial. I have twrp as my recovery.
Everything was going smoothly until mms blew up. I can't send or receive pictures/files at all.
Here's what I've done so far:
I've checked the apn settings at least a dozen times and they are correct as per my carrier's website.
Tried different messaging apps and the problem persists through all of them.
I've reached out to my carrier and my favorite texting app developers and they have no clue.
I got a momentary reprieve when I force stopped the messaging service and rebooted the phone, but that trick is no longer working somehow. I tried it three times before coming here.
Everything else is working perfectly, including humongous texts. I am so confused right now.
SashaNT86 said:
Hello all,
I am running the XT1768 variant, Qualcomm version, rooted with Resurrection Remix version 5.8.5 unofficial. I have twrp as my recovery.
Everything was going smoothly until mms blew up. I can't send or receive pictures/files at all.
Here's what I've done so far:
I've checked the apn settings at least a dozen times and they are correct as per my carrier's website.
Tried different messaging apps and the problem persists through all of them.
I've reached out to my carrier and my favorite texting app developers and they have no clue.
I got a momentary reprieve when I force stopped the messaging service and rebooted the phone, but that trick is no longer working somehow. I tried it three times before coming here.
Everything else is working perfectly, including humongous texts. I am so confused right now.
Click to expand...
Click to collapse
Try a clean install of your rom. Or even a dirty flash first to see if you borked something.
madbat99 said:
Try a clean install of your rom. Or even a dirty flash first to see if you borked something.
Click to expand...
Click to collapse
If that fails try returning to stock to see if the problem persists. Occationally mms dysfunction can be upstream and require carrier involvement.
madbat99 said:
Try a clean install of your rom. Or even a dirty flash first to see if you borked something.
Click to expand...
Click to collapse
A dirty flash seems to have done the trick,though I will say I used a different download for the flash. Loving it so far.
Thank you for the help!
Davey216, I will keep that in mind if it comes back. Stock is kinda icky but I need my mms. Thank you for the reply!
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.