Database Info

Having problems going to CM12

I'm having a problem when I flash the CM12 ROM.
While having CM11.x I go to Settings and navigate to "CM Updates" where I can see a list of Nightlys and stable CM releases. When I install the new CM update this way everything seems to go okay, however This may be normal, I get a message from CWM "Possible Root loss, fix?",.. I select yes and it boots up, runs through the whole "Android is upgrading" message and all. When the phone is finally ready for use I get spammed with millions of messages saying "Application has stopped" and they will pop up infinity in less then a second. I have to hold power and tell the phone to reboot into recovery so I can resotre from backup.
I also downloaded the ROM from CM website and flashed it using "ROM manager". I get the exact same issues sadly.
What could be the problem?
Is CWM not compatible with lollipop?
Do I need to run a factory reset and wipe my phone before flashing?
I've been fiddling with this all day now. -Sigh-
EDIT:
Should I flash the latest version of "gapps" ?

You're going to need to do some reading. Installing LP over KK thru a nightly isn't going to work. You'll need LP Gapps for starters and you'll need to go into recovery and do some wiping before you flash. There are some good LP roms here: http://forum.xda-developers.com/lg-g2/development with full installation procedures. Also, most are using TWRP for recovery: http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705 You may also need to flash a different baseband but you'll find everything you need in the general development section. Also, next time you really should post your questions in the Q&A section. Anyway, do some reading and you'll be good to go! :good:

Thanks. I actually did get everything up and running
after going back a restore point, I
1: Flashed 10O Radio
2: Factory Reset
3: Flashed CM 12
4 Flashed gapps 5.0
I used latest version of CWM. I had TWRP years ago and I have never liked it compared to CWM
I'm curious about the Radio Modem though, Should I have 10O or Should I have 10D ?

Traceguy said:
Thanks. I actually did get everything up and running
after going back a restore point, I
1: Flashed 10O Radio
2: Factory Reset
3: Flashed CM 12
4 Flashed gapps 5.0
I used latest version of CWM. I had TWRP years ago and I have never liked it compared to CWM
I'm curious about the Radio Modem though, Should I have 10O or Should I have 10D ?
Click to expand...
Click to collapse
First let me apologise, I see that you are in Q&A and I'm the one that doesn't know which forum he's in.
Next, well I've used both CWM and TWRP. Personally I prefer TWRP but as long as you're on the latest and greatest you should have no problems from what I've read. And if you do just flash over to the other and see if it fixes the problem. I've been using the 10D radio for quite some time now and it works for me.
As I go from rom to rom I always do a clean flash, wiping data, system, dalvik and cache. I rarely do a dirty flash but that's just me. As long as you can recover from the occasional boot loop you'll be good. :laugh:

[Q] TWRP not restoring backups

I have encountered a strange problem. Please help.
1. I was running CM12 nightly (April 10 build). I also have TWRP backups of Apr 8 image and my old CM11S (44R) image.
2. I downloaded OxygenOS to try it out. Booted the phone into TWRP and tried flashing the ZIP.
3. Got an error while flashing the ZIP.
4. Rebooted the phone into recovery and tried restoring the Apr 10 image.
5. Restore says it is successful.
6. On reboot, the phone stays on the "Powered by Android" screen. It does not boot up into the ROM image. It boots up into recovery instead.
7. I tried the same process with Apr 8 image and the same issue.
8. Finally, I restored the backup image of CM11S and that works well.
Can someone please advise how can I get my backup ROMs to work?
I have now tried backing up ROMs for Cyanogen CMOS12 as well as Oxygen. None of the restores are working. I am backing up all partitions. Where am I going wrong? The restore does not give any error, but the boot is stuck at the logo. When I restore CMOS12, it gets stuck on the screen that says "Cyanogen". When I restore Oxygen, it gets stuck at the boot animation of Oxygen.
I am using TWRP 2.8.6 for restore and Online nandroid manager for backing up.
Is it possible that OnlineNandroid manager uses a different version of recovery for backup?
Please help.
.

I'm new to the CM 12 stuff but I thought I read that TWRP had an issue with compression during a certain range of weeklies, and due to that, would/could not restore from that range.
I think I also read to make sure you have the most up to date TWRP, and a weekly after 4/22, or so. I don't recall the exact date of the compressed weeklies causing the issue,but I think the compression problem began in April, sometime. Hopefully someone will come by and further clarify or identify your issue.
What version of TWRP do you have and what's the date of your weekly?

JeffDC said:
I'm new to the CM 12 stuff but I thought I read that TWRP had an issue with compression during a certain range of weeklies, and due to that, would/could not restore from that range.
I think I also read to make sure you have the most up to date TWRP, and a weekly after 4/22, or so. I don't recall the exact date of the compressed weeklies causing the issue,but I think the compression problem began in April, sometime. Hopefully someone will come by and further clarify or identify your issue.
What version of TWRP do you have and what's the date of your weekly?
Click to expand...
Click to collapse
I am using TWRP 2.8.6. I have tried restoring Oxygen, CM12, CM12S backups and none of them are working. Restore takes reasonable time and says it was successful.

indoliya said:
I am using TWRP 2.8.6. I have tried restoring Oxygen, CM12, CM12S backups and none of them are working. Restore takes reasonable time and says it was successful.
Click to expand...
Click to collapse
see if this link has any relationship to your general issue
https://forums.oneplus.net/threads/...cm12-1-nightlies.300277/page-78#post-11010591
read around a bit as some folks seem to have had the same issue as you, there is also an xda topic for the nightlies, as well which may be a good place to search

indoliya said:
I am using TWRP 2.8.6. I have tried restoring Oxygen, CM12, CM12S backups and none of them are working. Restore takes reasonable time and says it was successful.
Click to expand...
Click to collapse
Did you wiped cacha/Dalvik? I personnaly do these wipes before and after flashing/restoring.
If I were you, I'd try to flash the latest cm12 nightly "on" you restore, maybe it could help..

You might have to flash the right firmware for the CM 12/11 you want to restore. TWRP doesn't backup firmware by default, only ROM/Data. So flash the right formware for the ROM you want to restore and then restore your nandroid.

real_sl4cker said:
You might have to flash the right firmware for the CM 12/11 you want to restore. TWRP doesn't backup firmware by default, only ROM/Data. So flash the right formware for the ROM you want to restore and then restore your nandroid.
Click to expand...
Click to collapse
Thank you! Previously, I was switching between CM11 and CM12 without any problem. Are you sure about this?

indoliya said:
Thank you! Previously, I was switching between CM11 and CM12 without any problem. Are you sure about this?
Click to expand...
Click to collapse
Not sure as in "Yes, that's the way to go, do it!" but it's worth a try. I haven't switched back to CM11 from CM12 (updated to CM12 just yesterday) up to now.
What I'm pretty sure about is that TWRP (by default) only backs up system and data, no modem and stuff. And CM11 and CM12 come with different firmware. Flashing the right firmware for your build won't do any harm anyway

real_sl4cker said:
Not sure as in "Yes, that's the way to go, do it!" but it's worth a try. I haven't switched back to CM11 from CM12 (updated to CM12 just yesterday) up to now.
What I'm pretty sure about is that TWRP (by default) only backs up system and data, no modem and stuff. And CM11 and CM12 come with different firmware. Flashing the right firmware for your build won't do any harm anyway
Click to expand...
Click to collapse
Finally resolved this by going to Online Nandroid app and changed the shell to default and busybox to default. Now the backups taken with these settings are getting restored successfully.

[Q] Urgent CM 12.1 Issue!

Hey everyone,
Thank you all for reading this...
Today, I wanted to update my phone from cm-12.1-20150429-NIGHTLY-bacon.zip to cm-12.1-20150502-NIGHTLY-bacon.zip and after optimizing all 199 applications the lock screen appeared and everything seemed fine. However a second later, a pop-up appeared delivering the crash of the google play services. After pressing on "ok" (the only option), the phone switched off and began optimizing the apps again and again, showing the boot sequence in-between. After a while, I tried to install the update again through TWRP and I failed again. Then I tried to restore my backup from the 19th April I had probably made with Nandroid Backup (not exactly sure) and I failed again. Now I have turned off my phone entirely so that it won´t get too hot.
Does anybody know how to fix this issue (preferably without wiping)? And do you think, should I stay with the nightlies or switch to Cyanogen OS 12 (how?)
Best regards from the android newbie,
George (ambach10)

Try reflashing slim's gapps package.
Edit: Link to thread: http://forum.xda-developers.com/oneplus-one/themes-apps/gapps-modified-slim-gapps-calkulin-t3082242

Thanks for helping me. I did, but it just continued to optimize. I also tried to install the newest cm12.1 update "cm-12.1-20150505-NIGHTLY-bacon.zip" by downloading it via a mac (is that a problem?) so that it would work with the newest gapps zip but I couldn´t even download the cm12.1 zip as it turned into a useless folder. Do you, or anyone else, know what to do know? I´m really frustrated that I cannot have access to my phone. I am also ready to wipe it, if necessary.

ambach10 said:
Thanks for helping me. I did, but it just continued to optimize. I also tried to install the newest cm12.1 update "cm-12.1-20150505-NIGHTLY-bacon.zip" by downloading it via a mac (is that a problem?) so that it would work with the newest gapps zip but I couldn´t even download the cm12.1 zip as it turned into a useless folder. Do you, or anyone else, know what to do know? I´m really frustrated that I cannot have access to my phone. I am also ready to wipe it, if necessary.
Click to expand...
Click to collapse
Follow this steps to first turn on your phone https://forums.oneplus.net/threads/guide-how-to-revert-back-to-cm11s-from-oxygen-guide.290605/
It's CM11S.
Easy way to revert back.

ambach10 said:
Thanks for helping me. I did, but it just continued to optimize. I also tried to install the newest cm12.1 update "cm-12.1-20150505-NIGHTLY-bacon.zip" by downloading it via a mac (is that a problem?) so that it would work with the newest gapps zip but I couldn´t even download the cm12.1 zip as it turned into a useless folder. Do you, or anyone else, know what to do know? I´m really frustrated that I cannot have access to my phone. I am also ready to wipe it, if necessary.
Click to expand...
Click to collapse
I've had this issue before. To fix it, I used these gapps, did a full wipe, then flashed everything all over again and it was working without any problems.
Also, I ended up just switching over to COS12 and am still running that. If you want, you can get that here.

ambach10 said:
Thanks for helping me. I did, but it just continued to optimize. I also tried to install the newest cm12.1 update "cm-12.1-20150505-NIGHTLY-bacon.zip" by downloading it via a mac (is that a problem?) so that it would work with the newest gapps zip but I couldn´t even download the cm12.1 zip as it turned into a useless folder. Do you, or anyone else, know what to do know? I´m really frustrated that I cannot have access to my phone. I am also ready to wipe it, if necessary.
Click to expand...
Click to collapse
Also, make sure you are running latest version of TWRP recovery (or whatever recovery you are using)... there are compression incompatibilities with some of the older versions.

Thanks everybody!
Thank you all for helping me out:
@frieked I have twrp v2.8.5.1. Is that ok and if not how can i update that?
@The_Symbiote should i install the apps before the full wipe and is there something not to wipe (USB_OTG)?
@Mr hOaX does it also work for cm12.1 nightlies or only for oxygenos?

ambach10 said:
Thank you all for helping me out:
@frieked I have twrp v2.8.5.1. Is that ok and if not how can i update that?
@The_Symbiote should i install the apps before the full wipe and is there something not to wipe (USB_OTG)?
@Mr hOaX does it also work for cm12.1 nightlies or only for oxygenos?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2766186 Here is the TWRP thread 2.8.6.0 is the latest. You can update using the TWRP Manager app available on the play store.

ambach10 said:
@The_Symbiote should i install the apps before the full wipe and is there something not to wipe (USB_OTG)?
Click to expand...
Click to collapse
I wiped everything other than Internal Storage, flashed the rom, flashed the gapps, and then rebooted and it booted just fine.

ambach10 said:
Thank you all for helping me out:
frieked I have twrp v2.8.5.1. Is that ok and if not how can i update that?
The_Symbiote should i install the apps before the full wipe and is there something not to wipe (USB_OTG)?
Mr hOaX does it also work for cm12.1 nightlies or only for oxygenos?
Click to expand...
Click to collapse
It works for all lollipop based ROMs.
I hope now your device is working fine.
Sorry for replying late.

Wifi and bluetooth not working in R7 plusf

I run CM 13 and want to back to color os because it is not run so smooth. I format and then flash stock recovery image (then recovery) via twrp and reboot to stock recovery.
In stock recovery i wipe data and cache. That's problem come. Before finish, the screen goes black. I try to power on the device, back to wipe data then the screen goes to black again. I try to boot to recovery and fastboot but it remain the same, back to wipe data and then the screen goes to black..
I try repair it using msm tool but because my comp not recognize the device, i use QFIL. And then i can use the fastboot to boot stock recovery. Suceed. But no os inside. Try and error many times, i can power on the device at the end.
But now the other problem comes. My wifi and bluetooth not work. And message nv backup appear.
Flash project spectrum. Wifi and bluetooth work. I flash back to stock os. Wifi and bluetooth not work again..
May someone help me to solve the problem (make bluetooth and wifi work again)?

To get back to ColorOS from spectrum flash this rom from internal storage.
http://community.oppo.com/en/forum.php?mod=viewthread&tid=41945
Sent from my R7plusf using XDA-Developers mobile app

uyab.com said:
I run CM 13 and want to back to color os because it is not run so smooth.
Click to expand...
Click to collapse
I think your initial problem was that you didn't flash open Gapps right after you flashed CM13.
Most users who are new to custom roms don't know that they have to flash Google apps separately.

kishd said:
To get back to ColorOS from spectrum flash this rom from internal storage.
http://community.oppo.com/en/forum.php?mod=viewthread&tid=41945
Sent from my R7plusf using XDA-Developers mobile app
Click to expand...
Click to collapse
I use color os now. Have no problem bout back to color from spectrum. The problem occures after that. Wifi and bluetooth do not work.

celoxocis said:
I think your initial problem was that you didn't flash open Gapps right after you flashed CM13.
Most users who are new to custom roms don't know that they have to flash Google apps separately.
Click to expand...
Click to collapse
I flashed pico after flash CM. Pico TTS unfortunately has stopped. I use browser, unfortunately stopped. Facebook stopped. Camera stopped. That's the beginning of all the problem because after that i format the phone.

uyab.com said:
I flashed pico after flash CM. Pico TTS unfortunately has stopped. I use browser, unfortunately stopped. Facebook stopped. Camera stopped. That's the beginning of all the problem because after that i format the phone.
Click to expand...
Click to collapse
Did you boot into CM after flashing CM? and then installed Gapps later on? This could explain corrupted cache.
Always follow these steps on custom roms. (first time install not upgrade)
Boot into TWRP, select wipe/factory reset.
1. Install CM Rom
after that select the next zip (or add more zips to flash)
2. install Gapps.
Let it boot and setup your phone.
If you follow this you will never have a problem in CM.
Especially the R7 series. Every change to the code is closely tripled (even quadruple) checked by devs.
Because the R5, R7, R7Plus, R7S all share the same base and its tested in on every phone.

celoxocis said:
Did you boot into CM after flashing CM? and then installed Gapps later on? This could explain corrupted cache.
Always follow these steps on custom roms. (first time install not upgrade)
Boot into TWRP, select wipe/factory reset.
1. Install CM Rom
after that select the next zip (or add more zips to flash)
2. install Gapps.
Let it boot and setup your phone.
If you follow this you will never have a problem in CM.
Especially the R7 series. Every change to the code is closely tripled (even quadruple) checked by devs.
Because the R5, R7, R7Plus, R7S all share the same base and its tested in on every phone.
Click to expand...
Click to collapse
Of course not. I flash CM and after that i flash pico right away. Not yet boot into CM. After CM and pico install then wipe dalvik then reboot.

uyab.com said:
Of course not. I flash CM and after that i flash pico right away. Not yet boot into CM. After CM and pico install then wipe dalvik then reboot.
Click to expand...
Click to collapse
But did you wipe factory reset before flashing all the above? Coming from ColorOS. Else those errors can't be explained.

celoxocis said:
But did you wipe factory reset before flashing all the above? Coming from ColorOS. Else those errors can't be explained.
Click to expand...
Click to collapse
Yes. I wipe all but not the internal storage. Is it the cause? I do not know why twrp cannot read otg. So i put CM file on internal storage.

uyab.com said:
Yes. I wipe all but not the internal storage. Is it the cause? I do not know why twrp cannot read otg. So i put CM file on internal storage.
Click to expand...
Click to collapse
I don't know about the R7Plus TWRP. I don't maintain that TWRP. I know that my R7S TWRP works with OTG.
Internal storage should have been fine. I think it will stay a mystery why you received those errors.

celoxocis said:
I don't know about the R7Plus TWRP. I don't maintain that TWRP. I know that my R7S TWRP works with OTG.
Internal storage should have been fine. I think it will stay a mystery why you received those errors.
Click to expand...
Click to collapse
wish me luck. I will try your suggestion.

uyab.com said:
I use color os now. Have no problem bout back to color from spectrum. The problem occures after that. Wifi and bluetooth do not work.
Click to expand...
Click to collapse
Once back on ColorOs from Spectrum. Flash this older version of ColorOs and then CM everything including bluetooth should work fine.
https://www.dropbox.com/s/xmh77xyinz2iero/R7plusfEX_11_OTA_012_all_201512251816.zip?dl=0

kishd said:
Once back on ColorOs from Spectrum. Flash this older version of ColorOs and then CM everything including bluetooth should work fine.
https://www.dropbox.com/s/xmh77xyinz2iero/R7plusfEX_11_OTA_012_all_201512251816.zip?dl=0
Click to expand...
Click to collapse
Oya.. Let me try it..

Solved. WiFi and Bluetooth work fine. Run smooth in CM.

uyab.com said:
Solved. WiFi and Bluetooth work fine. Run smooth in CM.
Click to expand...
Click to collapse
Which method fixed the issue in the end?

Maybe bad repaired or bad flashing. Persist folder is empty. Thats why i can not install CM and unvailable wifi and bluetooth address. So flashing persist.img after remove the old one.

uyab.com said:
Solved. WiFi and Bluetooth work fine. Run smooth in CM.
Click to expand...
Click to collapse
hi sir im having the same problem with my R7 plus can you help me
i already flash my phone using QFIL with Oppo_R7_Plusf_EX_11_A.15_160612_By(GsmTechSupport)
result is only OPPO Logo
flash the phone with Msm8x38 with Oppo_R7_Plusf_EX_11_A.15_160612_By(GsmTechSupport)
result is phone will boot normal but the problem is same with your problem with WIFI and Bluetooth also appear something with NV partion but can be manage with *#268# but with wifi and bluetooth i cant solve
please help me.
thank you in advance

I'm so sorry. I just log in after a long time and read your problem. Have you solved the problem?

same problem for me, no wifi and no bluetooth after flashing stock rom.
Any idea?

uyab.com said:
Maybe bad repaired or bad flashing. Persist folder is empty. Thats why i can not install CM and unvailable wifi and bluetooth address. So flashing persist.img after remove the old one.
Click to expand...
Click to collapse
hello,
please ask me where to find persist.img and the method for flashing it.
thanks in advance

Google Maps reboot my phone on any ROM that I have tried for 7.X

Everytime I try and use Google Maps either flashed with gapps/bean or installed later from play store all reboot my phone. Stock does not have any issue.
Tried:
ASOP-CAF
ASOP-EX
MOTOPURE
Lineage
TESLA
I just wonder why if the stock maps app works on 6.0 why not on 7.0?? The only thing I can think of is the GPS.
Any tips or suggestions?
Thanks!

Tried nano, pico and full for ARM and Android 7
open_gapps-arm-7.1-full-20170523
open_gapps-arm-7.1-nano-20170511
open_gapps-arm-7.1-pico-20170513
also BeansGapps-Full-7.1.x-20170509 BeansGapps-Mini-7.1.x-20170509

Ok I have found that other maps reboot the phone too. Tried a GPS test app from play store and soon as I allowed it to access my location it rebooted. So it seems to be definately a GPS issue.

grantdb said:
Ok I have found that other maps reboot the phone too. Tried a GPS test app from play store and soon as I allowed it to access my location it rebooted. So it seems to be definately a GPS issue.
Click to expand...
Click to collapse
Return to stock by fastboot the lastest images available, flashing everything including the wipes (of course, skip gpt.bin and bootloader.bin if necessary), then take the lastest OTA's, verify operation of GPS... After that install TWRP, backup everything, and flash a ROM and Gapps, do not restore anything and test again.
I can't see how GPS would work with stock and not with ANY custom ROM...

acejavelin said:
Return to stock by fastboot the lastest images available, flashing everything including the wipes (of course, skip gpt.bin and bootloader.bin if necessary), then take the lastest OTA's, verify operation of GPS... After that install TWRP, backup everything, and flash a ROM and Gapps, do not restore anything and test again.
I can't see how GPS would work with stock and not with ANY custom ROM...
Click to expand...
Click to collapse
Thanks for helping me, do you mean bootloader.img?

Ok done reflash stock, OTA's and checked gps is fine now backing up... going to use the PureNexus rom or ASOP-CAF

ARRRRRGGGGG Same damn issue... Maps crashes the phone.... so frustrating I am going to give up soon and stick with stock.
Going to try an get a logfile maybe someone can take a look at it
Thanks

ok after phone crashed the first time I rebooted a couple times and its working!!!!!!!!
Thanks to @acejavelin and @Vikas Tewatia for trying to help me with this issue.
I think one of the problems was the way I was wiping after stock to install a custom ROM, instead of just standard TWRP wipe I was using individual selections?
Anyways I am going to further test and then report back. I will close this thread once I am sure everything is working.
Thanks

grantdb said:
ok after phone crashed the first time I rebooted a couple times and its working!!!!!!!!
Thanks to @acejavelin and @Vikas Tewatia for trying to help me with this issue.
I think one of the problems was the way I was wiping after stock to install a custom ROM, instead of just standard TWRP wipe I was using individual selections?
Anyways I am going to further test and then report back. I will close this thread once I am sure everything is working.
Thanks
Click to expand...
Click to collapse
The recommended way to wipe before installing a ROM is to manually wipe system, data, caches, and internal storage (kind of optional, make sure to move TWRP backups and other info to SD card first), then flash ROM and Gapps. Some people say flash ROM, boot, then shutdown and flash Gapps, but I have never had to do that.
I would be curious to see a logcat of the crash... this is not normal. Are you installing ANYTHING else besides the ROM and Gapps at this point?

acejavelin said:
The recommended way to wipe before installing a ROM is to manually wipe system, data, caches, and internal storage (kind of optional, make sure to move TWRP backups and other info to SD card first), then flash ROM and Gapps. Some people say flash ROM, boot, then shutdown and flash Gapps, but I have never had to do that.
I would be curious to see a logcat of the crash... this is not normal. Are you installing ANYTHING else besides the ROM and Gapps at this point?
Click to expand...
Click to collapse
I started a bug report (interactive) when I tried to use the maps again but thats when it started working properly. lol
If you know of a way to get logs from the first crash off my phone I would be more than happy to send it to you.
I did a twrp standard wipe this time rather than each partition under advanced wipe, I didn't install anything other than a ROM and either gapps or bean depending on the ROM creators suggestion and that's it!

grantdb said:
I started a bug report (interactive) when I tried to use the maps again but thats when it started working properly. lol
If you know of a way to get logs from the first crash off my phone I would be more than happy to send it to you.
I did a twrp standard wipe this time rather than each partition under advanced wipe, I didn't install anything other than a ROM and either gapps or bean depending on the ROM creators suggestion and that's it!
Click to expand...
Click to collapse
You can use ADB to get real-time logging of the crash on your PC... Use Google to find the command.

acejavelin said:
The recommended way to wipe before installing a ROM is to manually wipe system, data, caches, and internal storage (kind of optional, make sure to move TWRP backups and other info to SD card first), then flash ROM and Gapps. Some people say flash ROM, boot, then shutdown and flash Gapps, but I have never had to do that.
I would be curious to see a logcat of the crash... this is not normal. Are you installing ANYTHING else besides the ROM and Gapps at this point?
Click to expand...
Click to collapse
Sent you logcat via pm thanks again!

Well I started getting random reboots in Pure Nexus ROM and so tried LOS and right away I had the reboot from Maps. I give up, staying with stock.
Thanks

Seems like one of my problems could be ASOP-CAF ROM as the version I was flashing uses a custom Kernel that has known issues with 7.1.2 and causes bootloops and crashes. The UltraDev kernel changes some things in the modem and could be why any roms I tried after flashing ASOP-CAF would not change the modem and were 7.1.2 based.
Anyways...

Well I think I have tried almost every 7.x ROM I can find and every single one has a problem with any gps app on my phone.

grantdb said:
Well I think I have tried almost every 7.x ROM I can find and every single one has a problem with any gps app on my phone.
Click to expand...
Click to collapse
Check out this bug report. It might be your APNs... https://jira.lineageos.org/browse/BUGBASH-248

By messing with my APN settings as per above bug report I can use maps and have no more random reboots. Woop woop