So, I was using my phone at a mall. I stepped into a store and I noticed I had no more LTE. The signal was weak, so I thought it was just the building. So I got to a stronger area and restarted the phone, and still no data. I tried restarting several times and I tried selecting different APNs (I'm running 7/15 nightly of CM13). Eventually, I took the sim card out of my wife's iPhone 6S and the LTE worked fine. My sim card worked OK in here phone as well. But once I put mine back in, I have no data (not even 2g or 3g). I thought it was just my sim card, but then I can't understand why it works in my wife's iPhone 6S. Any ideas? I'm updating to the latest nightly of CM13.
ambig88 said:
So, I was using my phone at a mall. I stepped into a store and I noticed I had no more LTE. The signal was weak, so I thought it was just the building. So I got to a stronger area and restarted the phone, and still no data. I tried restarting several times and I tried selecting different APNs (I'm running 7/15 nightly of CM13). Eventually, I took the sim card out of my wife's iPhone 6S and the LTE worked fine. My sim card worked OK in here phone as well. But once I put mine back in, I have no data (not even 2g or 3g). I thought it was just my sim card, but then I can't understand why it works in my wife's iPhone 6S. Any ideas? I'm updating to the latest nightly of CM13.
Click to expand...
Click to collapse
My suggestion is to start fresh by fastboot flashing the latest 6.0.1 factory images. Verify that your mobile data/LTE are working. Then, install TWRP. I would also download a fresh copy if the CM13 ROM and verify the md5 is correct. Flash CM13 again and see if you have LTE again. If you don't have LTE after flashing CM13 again we know it is something that has changed in the ROM.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
My suggestion is to start fresh by fastboot flashing the latest 6.0.1 factory images. Verify that your mobile data/LTE are working. Then, install TWRP. I would also download a fresh copy if the CM13 ROM and verify the md5 is correct. Flash CM13 again and see if you have LTE again. If you don't have LTE after flashing CM13 again we know it is something that has changed in the ROM.
Click to expand...
Click to collapse
I think you're right. I'm going to have to do this. I got a new SIM card from Verizon and data was fine. Then once I went to work and entered into my office, which has a poor signal, I wasn't able to get data back (can still call and send/receive texts). It makes no sense as to why it won't reconnect after a reboot, but I guess this is the only option.
Yeah I agree. Fastboot flash the factory images to give yourself a fresh start. Confirm that everything is working on a fully stock build. Then root, recovery and flash. I would try a different ROM that is not CM based to see how your voice and data works. Let us know how it goes that way others in the forum who may run into this issue can read about what was performed on your device and know what to do to help themselves. Good luck.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Yeah I agree. Fastboot flash the factory images to give yourself a fresh start. Confirm that everything is working on a fully stock build. Then root, recovery and flash. I would try a different ROM that is not CM based to see how your voice and data works. Let us know how it goes that way others in the forum who may run into this issue can read about what was performed on your device and know what to do to help themselves. Good luck.
Click to expand...
Click to collapse
So I flashed the factory images back onto my phone and I got data back. I guess there is a strange bug in the latest nightly of CM13. Of course, I haven't been able to go to an area where I have poor reception. Now I have to find a ROM that offers the LiveDisplay feature CM13 offered. I like my screen to be a bit colder than what Huawei calibrates their displays to.
ambig88 said:
So I flashed the factory images back onto my phone and I got data back. I guess there is a strange bug in the latest nightly of CM13. Of course, I haven't been able to go to an area where I have poor reception. Now I have to find a ROM that offers the LiveDisplay feature CM13 offered. I like my screen to be a bit colder than what Huawei calibrates their displays to.
Click to expand...
Click to collapse
I knew there was something in the CM13 based ROM's that was causing you to lose data. Also, If you use a custom kernel like Elemental or Elite you can control the screen colors and make it how you like it. Give Pure Nexus a try. It's a super nice ROM. The dev is awesome. He does great work. Maybe give Chroma a shot. Also, you could try Resurrection Remix. It's a CM based ROM but it may not give you the data issues. It's worth a try. Lemme know what works. Good job on getting the factory images flashed and getting data back too.
Sent from my Nexus 6 using XDA-Developers mobile app
Related
Hey there guys, I apologize if this has been covered, as I feel its related to an "efs" folder type of issue. I'm just not quite sure where the hell to even begin searching.
I've been on 4.3 since the leak and have been using Cataclysm 4.3 JWR ROM for a while now, problem free. All was running great until yesterday I was downloading some media and transferring it to my laptop (~10gb of traffic before I noticed the problem), and my WiFi shut off and restarted itself. My mobile data kicked in at that point for all of 10 seconds until the WiFi reconnected and within 30 minutes my signal bars suddenly dropped to zero and calls couldn't be made. "Mobile network not available." message appears. So I figured i'd pull the SIM, replace and reboot. When that didn't work I tried rebooting without the SIM, to see if it would detect no SIM card and prompt me to put one in and reboot to be able to connect to mobile network. Well nothing was detected. A full wipe, reflash of identical ROM, reflash of updated ROM, reflash of original JWR deodexed & rooted backup, all with the same outcome. I have tried everything short of downloading the stock image and flashing that but I haven't got around to it since I haven't had time to backup my internal SD before losing all data. I should note that I'm on baseband .84/4.3 bootloader and have been since Google pushed JWR & JSS. I haven't tried flashing a new modem, I figured that wouldn't been an issue. I suppose I'll try flashing .48 and update.
Edit: I forgot to mention that yes, WiFi is in fact working. Mobile signal seems to be the only thing affected.
Edit: Reflashing baseband .84 and .48 didn't work.
I really appreciate any ideas guys, I'd like to sort this out rather than having to flash stock and RMA it or something :/
All settled, it was an issue with the frequency band my provided operates on. Mod can lock/delete thread thanks.
Sent from my Nexus 4 using xda app-developers app
Hi All,
I just got a new used Samsung Galaxy S4 on Sprint and brought it over to Ting (way, way, way cheaper). I got everything working with the stock ROM, including GPS, but I wanted to install Cyanogenmod, so I rooted it, flashed TWRP 7.8, and flashed the latest Cyanogenmod (snapshot M12), with Gapps, and a zip file with the Ting data XML files to get 3G and LTE working.
Everything seemed to work great, but then while driving I noticed that the GPS just did not get a lock. After trying for an hour, it still had nothing. I installed GPS Status and saw that it had no satellites. Clearing the GPS cache and re-downloading data with that app did not solve the problem. I tried GPS Doctor without success and the GPS fix equally without success.
I rebooted, then factory reset, then erased everything and flashed the latest CM nightly, all with no success.
I found some similar problems online at these places:
http://myblog-online.co.uk/2013/12/the-continuing-saga-of-my-galaxy-s4-custom-roms/
http://forum.cyanogenmod.org/topic/98811-gps-not-working-23rd-nightly/
http://forum.xda-developers.com/showthread.php?t=2172670
These are all old and none gave me anything that useful. Is it a GPS radio issue? Is there anything I can do?
I also just found this page: http://wiki.cyanogenmod.org/w/Known_Issues_page_for_d2lte, but it is for the S3, not sure what to make of it.
I made a nandroid backup of my stock rom, but then I copied it to my computer, and when I copied it back again it didn't work. TWRP failed to restore with the error "No partition selected for restore".
My plan now is to flash the stock rom with odin, confirm that GPS works there, and then try again, but this is becoming a huge time sink and I have a lot of other things to do.
Does anyone have any ideas how I can fix this? I am pretty sure it isn't a hardware issue.
MikeDacre said:
Hi All,
I just got a new used Samsung Galaxy S4 on Sprint and brought it over to Ting (way, way, way cheaper). I got everything working with the stock ROM, including GPS, but I wanted to install Cyanogenmod, so I rooted it, flashed TWRP 7.8, and flashed the latest Cyanogenmod (snapshot M12), with Gapps, and a zip file with the Ting data XML files to get 3G and LTE working.
Everything seemed to work great, but then while driving I noticed that the GPS just did not get a lock. After trying for an hour, it still had nothing. I installed GPS Status and saw that it had no satellites. Clearing the GPS cache and re-downloading data with that app did not solve the problem. I tried GPS Doctor without success and the GPS fix equally without success.
I rebooted, then factory reset, then erased everything and flashed the latest CM nightly, all with no success.
I found some similar problems online at these places:
http://myblog-online.co.uk/2013/12/the-continuing-saga-of-my-galaxy-s4-custom-roms/
http://forum.cyanogenmod.org/topic/98811-gps-not-working-23rd-nightly/
http://forum.xda-developers.com/showthread.php?t=2172670
These are all old and none gave me anything that useful. Is it a GPS radio issue? Is there anything I can do?
I also just found this page: http://wiki.cyanogenmod.org/w/Known_Issues_page_for_d2lte, but it is for the S3, not sure what to make of it.
I made a nandroid backup of my stock rom, but then I copied it to my computer, and when I copied it back again it didn't work. TWRP failed to restore with the error "No partition selected for restore".
My plan now is to flash the stock rom with odin, confirm that GPS works there, and then try again, but this is becoming a huge time sink and I have a lot of other things to do.
Does anyone have any ideas how I can fix this? I am pretty sure it isn't a hardware issue.
Click to expand...
Click to collapse
That's is pretty much what you have to do. Its go back to stock and get a lock there in maps. When you have a lock just go back to recovery and flash your custom ROM of choice. That is pretty much the only fix.
Sent from my GT-I9505G using XDA Free mobile app
ROMANTiC KiD said:
That's is pretty much what you have to do. Its go back to stock and get a lock there in maps. When you have a lock just go back to recovery and flash your custom ROM of choice. That is pretty much the only fix.
Sent from my GT-I9505G using XDA Free mobile app
Click to expand...
Click to collapse
Thanks ROMANTiC KiD,
Good to know that I am heading down the right path before I spend a lot of time on this.
Should I not erase everything when I flash the custom ROM? I am pretty sure last time I used TWRP advanced erase to clear everything on the phone before installing. Should I just do a regular factory reset in TWRP to install CM in order to keep GPS functionality?
Thanks!
MikeDacre said:
Thanks ROMANTiC KiD,
Good to know that I am heading down the right path before I spend a lot of time on this.
Should I not erase everything when I flash the custom ROM? I am pretty sure last time I used TWRP advanced erase to clear everything on the phone before installing. Should I just do a regular factory reset in TWRP to install CM in order to keep GPS functionality?
Thanks!
Click to expand...
Click to collapse
Yes sir you can factory reset in twrp just remember to back up your files first! And you should still retain GPS lock.
Sent from my GT-I9505G using XDA Free mobile app
ROMANTiC KiD said:
Yes sir you can factory reset in twrp just remember to back up your files first! And you should still retain GPS lock.
Sent from my GT-I9505G using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the confirmation. I did exactly that and I can confirm that it did indeed work.
Thanks so much for the help.
Hi all,
Sorry to resurrect an old thread, but I am having this issue and the stock firmware flash isn't solving the issue. It is all very odd because it doesn't actually retain any kind of lock after flashing. I'm following instruction on here, but after locking gps on stock, then going to CM I cannot get a fix. It either had a massive radius on Maps, or it just locks to my home or work location.
Since trying much more I have managed to get the occasional satellite lock via GPS Locker, but even then as soon as I move from either my house or work, it can't find anything to lock onto and just defaults to a static location.
Is there anything you would recommend? I have 2 Samsung GS4's and they both exhibit the same problem. I have also tried this on an S4 Mini, but that retained lock just fine. I'm really confused as to what to actually try. If you could recommend anything I'd be very grateful.
Again, I'm sorry to res an old thread, but no one has been replying to the one I started for this issue :/
Your problem may be that there is some new issue with the newer firmware. I had success by first flashing the *old* firmware (you can download it from my dropbox here: https://www.dropbox.com/s/o3f3ynyezyy4yw9/L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5?dl=0) and then upgrading to the second to last firmware update for the GS4: which gives you Android 5 but without fixing the MMS bug.
After that I flash TWRP with Odin, and then do a full erase in TWRP followed by flashing the latest CM. That series of steps works for me every time, although I found that large changes to my physical location (e.g. flying to England from California) cause it to break again. I actually had to sit in a cafe in an English airport with my laptop out flashing my phone back to stock just so that I could use Google maps to get to my mother's house. It was pretty ridiculous. Because of that and other issues, I now just use stock. I hate it, but I do it anyway. Good luck.
Hi I got problems with my lux on every cm based rom. On every cm rom I get no reception of my carrier. I don't know if it's a device tree issue or just apn trouble. Since there are no aosp roms, I'm a little hung up. Stock rom works fine. I own the xt1562 operating on German carrier o2. Sometimes I get a few seconds of reception on cm roms, but it's leading just to no signal after a few seconds again. I nearly tired everything, flashed a different firmware etc. When I've flashed a rom I get the information that no sim card was found. After I restart the device he's asking for a pin. Also tried another sim card with the same result. Really could need some help.
flash the original fimrware from ur carrier or region
flash twrp
install cm and see if works
if not,flash only the radio modem from original firmware
Already did. Didn't work. Flashed the new cm12.1 from h2o64. This one is working.
I have the exact same problem with my XT1562 I bought from Germany through Moto Maker.
I installed h2o64's CM build from 10-10 after a full wipe (everything except internal data), and never got any proper signal. I tried squid2's CM build 10-12 as well, to no avail. Installing the XT1562 EU stock firmware following the linked explanation in the stock firmwares thread I had good, working signal, but then installing h2o64's CM build 10-14 with a factory reset rather than a full wipe resulted in the same issues described in this thread again.
I've read about these issues in different threads, mostly resolved somehow by installing the stock firmware, sometimes by selecting LTE as the preferred network type. I've tried these suggestions, but haven't had any success, and I don't know how to proceed.
Did I install the right stock firmware? (I would think so as it worked while it was installed.)
Did I forget to do something (like wipe, fix permissions, reboot the phone three times, howl at the moon,...)?
I use OpenGApps rather than tkruzze's since they're available in x64 as well so I can use them on all my devices. But that surely can't be it?
I'm at a complete loss at the moment, which is rather frustrating. Can anyone provide any help?
Gesendet von meinem Nexus 9 mit Hilfe von XDA Forums Pro.
I managed to install h2o64's CM build 10-14 and getting proper signal now.
I flashed the RETASIA firmware from XMoDuLeSx's Official stock firmwares added for xt1562,xt1563 thread following the instructions linked in the first post, and then after a wipe of system, data, cache, dalvik-cache I installed [ROM][lux][5.1.1] Cyanogenmod 12.1 - 2015-10-14 [UNIFIED].
Keep in mind that I have ordered my Moto X Play from Germany, so it shouldn't require a RETASIA firmware. I'm not advising to install this, as it was nothing but a shot in the dark that surprisingly didn't brick my phone. Still, I wanted to share that I got it working after all, simply to follow up my previous post properly. Should the signal break again, I'll update this thread; if I haven't, assume that it's still working.
Either way, though: If you decide to go down this road and install a firmware that isn't right for your phone and brick it, don't come to me. I'm advising against doing this.
Seems i'm having the same issue...
I did all the wipes and clean installs but I can't connect to my carrier.
Although my phone only supports one sim card, settings shows two. The first one is the one i'm using and it is displayed correctly. The quick settings tile though tells me that there is no sim card inserted.
I came from stock, unlocked, flashed TWRP from squid2's kernel page, rooted, flashed CM(squid2), kernel(squid2) and OpenGApps.
Did I do something wrong?
Is there any news on how to fix this problem or do I have to try again and again an hope to hit the spot?
Mafaldine said:
Seems i'm having the same issue...
I did all the wipes and clean installs but I can't connect to my carrier.
Although my phone only supports one sim card, settings shows two. The first one is the one i'm using and it is displayed correctly. The quick settings tile though tells me that there is no sim card inserted.
I came from stock, unlocked, flashed TWRP from squid2's kernel page, rooted, flashed CM(squid2), kernel(squid2) and OpenGApps.
Did I do something wrong?
Is there any news on how to fix this problem or do I have to try again and again an hope to hit the spot?
Click to expand...
Click to collapse
You need two more posts before you can post this in the CM thread from squid2. Squid2 is always fast with bugfixes. So make 2 other post and then explain your problem to him.
Lennyz1988 said:
You need two more posts before you can post this in the CM thread from squid2. Squid2 is always fast with bugfixes. So make 2 other post and then explain your problem to him.
Click to expand...
Click to collapse
Thanks for your reply!
I will do that
Meanwhile I managed to get a connection to my carrier by flashing h2o64's CM build 10-14 and then squid2's on top without wiping anything...
RR Lux 5.5.8 didn't work Wifi, after 2 clean instalation, wifi turn on and off then
Phone seemed to stop working yesterday. Last time I used it was via Bluetooth paired with my wife's car.
I get signal and can text, just not send/receive calls.
I was on dirty unicorns official and had not messed with anything in several weeks.
I just updated radio and vendor and installed latest weekly of dirty unicorns.
Anybody go through this before? Any advice?
Thanks.
SwimDrewid said:
Phone seemed to stop working yesterday. Last time I used it was via Bluetooth paired with my wife's car.
I get signal and can text, just not send/receive calls.
I was on dirty unicorns official and had not messed with anything in several weeks.
I just updated radio and vendor and installed latest weekly of dirty unicorns.
Anybody go through this before? Any advice?
Thanks.
Click to expand...
Click to collapse
I had something like this before on my Nexus 5. Clearing the cache from the 'phone' app did it for me. Worth trying
maarten08 said:
I had something like this before on my Nexus 5. Clearing the cache from the 'phone' app did it for me. Worth trying
Click to expand...
Click to collapse
Already tried that. Then clean flash. Then updated ROM with latest vendor and radio images. No luck
i have a similar issue when connect to my Huawei Watch. once i turn off bluetooth i can call correctly.
do you still have an IMEI under settings
Gytole said:
do you still have an IMEI under settings
Click to expand...
Click to collapse
Yeah. Att thinks it's hardware. Time to test my Google warranty
SwimDrewid said:
Yeah. Att thinks it's hardware. Time to test my Google warranty
Click to expand...
Click to collapse
What does your prl version say under your IMEI settings? I had this exact problem when I flashed the latest PN build. I tried everything to fix it. Flashing my EFS backup worked for a while but sometimes on a reboot I had the same issue again. Flashing EFS would fix it again but it was temporary. The permanent fix for me was a clean flash of Chroma ROM. Just curious but what carrier are you on? It seems like this issue has been affecting CDMA carriers like Verizon more than others.
murphyjasonc said:
What does your prl version say under your IMEI settings? I had this exact problem when I flashed the latest PN build. I tried everything to fix it. Flashing my EFS backup worked for a while but sometimes on a reboot I had the same issue again. Flashing EFS would fix it again but it was temporary. The permanent fix for me was a clean flash of Chroma ROM. Just curious but what carrier are you on? It seems like this issue has been affecting CDMA carriers like Verizon more than others.
Click to expand...
Click to collapse
On att
Emei sv: 61
Says not roaming but I have that set
SwimDrewid said:
On att
Emei sv: 61
Says not roaming but I have that set
Click to expand...
Click to collapse
When I had this problem the prl version in my screenshot said unknown as well as the MIN number. If you problem started after flashing an update I'll guarantee its software and not hardware. If you have an EFS backup I would try and flash that first if not I would do a backup in TWRP and then clean flash Chroma. If it doesn't work you can always just flash your backup and be back to where you are now.
murphyjasonc said:
When I had this problem the prl version in my screenshot said unknown as well as the MIN number. If you problem started after flashing an update I'll guarantee its software and not hardware. If you have an EFS backup I would try and flash that first if not I would do a backup in TWRP and then clean flash Chroma. If it doesn't work you can always just flash your backup and be back to where you are now.
Click to expand...
Click to collapse
Ah. I don't have that info. Didn't do update till after this problem. May not have efs backed up. But did full clean install of latest du weekly including radio and vendor this morning.
Will check if I have efs backed up
SwimDrewid said:
On att
Emei sv: 61
Says not roaming but I have that set
Click to expand...
Click to collapse
I'm sure you have already checked the APN settings but it would be a good idea to make sure they were not changed when you updated. Are you in a good LTE area? A lot of people with this issue could make and receive calls over LTE but when they didn't have it they couldn't even though they had service. That's why I think it affected CDMA carriers more. LTE goes over GSM and 3g goes over CDMA. Does your phone number show up under SIm info?
murphyjasonc said:
I'm sure you have already checked the APN settings but it would be a good idea to make sure they were not changed when you updated. Are you in a good LTE area? A lot of people with this issue could make and receive calls over LTE but when they didn't have it they couldn't even though they had service. That's why I think it affected CDMA carriers more. LTE goes over GSM and 3g goes over CDMA. Does your phone number show up under SIm info?
Click to expand...
Click to collapse
Checked APN. I have efs from November MDBO8M from when I first got phone
SwimDrewid said:
Checked APN. I have efs from November MDBO8M from when I first got phone
Click to expand...
Click to collapse
The EFS doesn't change. The original backup you have is all you need as long as you have a backup of just the EFS partition and nothing else with it. It might not fix your issue but it won't hurt anything. I tried Chroma after reading it fixed a lot of others problems with the same issue and that worked for me also. I'm still running it but others have said they were able to go back to their preferred ROM after flashing it and all was good.
SwimDrewid said:
Phone seemed to stop working yesterday. Last time I used it was via Bluetooth paired with my wife's car.
I get signal and can text, just not send/receive calls.
I was on dirty unicorns official and had not messed with anything in several weeks.
I just updated radio and vendor and installed latest weekly of dirty unicorns.
Anybody go through this before? Any advice?
Thanks.
Click to expand...
Click to collapse
Could it be a sim card issue? Have you tried remove and re-inserting the sim?
ckarrow2 said:
Could it be a sim card issue? Have you tried remove and re-inserting the sim?
Click to expand...
Click to collapse
Yep. Removed / reinserted before coming here
murphyjasonc said:
The EFS doesn't change. The original backup you have is all you need as long as you have a backup of just the EFS partition and nothing else with it. It might not fix your issue but it won't hurt anything. I tried Chroma after reading it fixed a lot of others problems with the same issue and that worked for me also. I'm still running it but others have said they were able to go back to their preferred ROM after flashing it and all was good.
Click to expand...
Click to collapse
I'll transfer to my phone and try in a bit. Any known problems going from DU to chroma? I'll try that too
ckarrow2 said:
Could it be a sim card issue? Have you tried remove and re-inserting the sim?
Click to expand...
Click to collapse
SwimDrewid said:
I'll transfer to my phone and try in a bit. Any known problems going from DU to chroma? I'll try that too
Click to expand...
Click to collapse
As long as you clean flash their shouldn't be any issues. Just go to advance wipe and select system, data, cache and dalvic. Just make sure you don't check internal storage. Then flash chroma and the recommended gapps and you should be good to go. Make a backup first and you can always just flash back to the point where you are now if it doesn't work.
murphyjasonc said:
As long as you clean flash their shouldn't be any issues. Just go to advance wipe and select system, data, cache and dalvic. Just make sure you don't check internal storage. Then flash chroma and the recommended gapps and you should be good to go. Make a backup first and you can always just flash back to the point where you are now if it doesn't work.
Click to expand...
Click to collapse
I don't have an EFS backup on my google drive (like I thought I did). I think I have the backup in the office, but not available now.
No joy on the Chroma -- still no PRL data, no phone sound on dialing, no receiving calls
At this point, I figure it's hardware related
Thanks for your help
SwimDrewid said:
I don't have an EFS backup on my google drive (like I thought I did). I think I have the backup in the office, but not available now.
No joy on the Chroma -- still no PRL data, no phone sound on dialing, no receiving calls
At this point, I figure it's hardware related
Thanks for your help
Click to expand...
Click to collapse
Have you changed any settings in the test menu? Another option would be to swap sim cards out with another phone to see if yours works in theirs and vice versa. As a last resort before you RMA you should wipe everything and flash the stock images and start fresh. Even if that doesn't fix it I think you would have an easier time with the RMA process being completely stock and relocking your bootloader.
murphyjasonc said:
Have you changed any settings in the test menu? Another option would be to swap sim cards out with another phone to see if yours works in theirs and vice versa. As a last resort before you RMA you should wipe everything and flash the stock images and start fresh. Even if that doesn't fix it I think you would have an easier time with the RMA process being completely stock and relocking your bootloader.
Click to expand...
Click to collapse
So, uh, I forgot to mention a critical piece of data: I live in Georgia, but this occurred at one of the South Carolina beaches, over 300 miles away.
I had full LTE, but noticed the phone said Not Roaming (or roaming: false).
As soon as we got home today, boom -- could make and receive calls again.
So, I think I can close this thread and open a new thread on how to get roaming to stick.
Thanks for all your help! :good:
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.