Thanks to you, i was somehow "blind" to see ;-)You are wrong. Go to:
Settings
Connected devices
Connection preferences
I have them where they have been before, with Bluetooth and Android Auto.Am i wrong? I don't find settings for NFC anymore. Not implemented yet under LOS 19.1?
I've been having issues on verizon as well, though not sure if it's the same band. Mine will switch networks to an invalid network when I have a poor signal, then not switch back until I manually select the right apn. Have you tried messing with the apns-conf.xml file at all? I'm playing around with it with varying degrees of success... If I find one that works I'll post itThis does not work with Verizon LTE Band 13. I am able to get 3G connection, but that's all. I used this phone for years with Verizon on stock firmware and no problems, so it's not a compatibility issue.
The rom will not save the selected APN. There are 3, StraightTalk Verizon, Verizon, and XFINITY Mobile. Selecting the correct one, Verizon, shows it is selected, until I close settings and go back into it.
I have also tried changing Preferred network type to many different options. I either get no data or 3G.
I have had this problem before with another Motorola phone. Something about the way Lineage implements this in Motorola phones is broken when it comes to Verizon.
Too bad, I was looking forward to Android 12.
Other than that, rom seems stable for daily use. But the phone cannot be used as a phone with Verizon considering they are switching everything over calls and texts to LTE.
No, messing with system stuff has been a pita for like the last 3-4 android revisions so i dont mess with it.I've been having issues on verizon as well, though not sure if it's the same band. Mine will switch networks to an invalid network when I have a poor signal, then not switch back until I manually select the right apn. Have you tried messing with the apns-conf.xml file at all? I'm playing around with it with varying degrees of success... If I find one that works I'll post it
The APN looks fine but I didnt dig into it. Considering the phone refuses to save the selected APN leads me to believe it's broken in the use of the APN, not the APN itself.
fastboot.exe getvar max-sparse-size
fastboot.exe oem fb_mode_set
fastboot.exe flash partition gpt.bin
fastboot.exe flash bootloader bootloader.img
fastboot.exe flash modem NON-HLOS.bin
fastboot.exe flash fsg fsg.mbn
fastboot.exe flash bluetooth BTFM.bin
fastboot.exe flash dsp dspso.bin
fastboot.exe flash logo logo.bin
fastboot.exe flash boot boot.img
fastboot.exe flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash system system.img_sparsechunk.3
fastboot.exe flash system system.img_sparsechunk.4
fastboot.exe flash system system.img_sparsechunk.5
fastboot.exe flash system system.img_sparsechunk.6
fastboot.exe flash system_b system_other.img
fastboot.exe flash oem oem.img
fastboot.exe erase carrier
fastboot.exe erase userdata
fastboot.exe erase ddr
fastboot.exe oem fb_mode_clear
fastboot.exe reboot bootloader
fastboot flash boot lineage-19.1-20220517-recovery-payton.img
fastboot reboot recovery
adb sideload lineage-19.1-20220517-nightly-payton-signed.zip
@rseiler @skiwarz
However I did fix my issue. There was something wrong with the oem partition, I'm guessing it was outdated. Or there is something wrong with the copy-partitions zip that is linked in official lineageos guide. Because it's a possibility I didn't even use it because the stock firmware occupied system_b and oem
note - DO NOT flash the copy-partitions zip from the documentation
The problem I'm assuming is if someone had come from an older stock Android version that did not have the system_b or oem partition setup. This isn't needed when using a new stock image, and you can verify that by looking at the flashfile.xml that comes with the firmware and see if it flashes these two partitions.The purpose of that small (and over year-old) archive file is:
"In some cases, the inactive slot can be unpopulated or contain much older firmware than the active slot, leading to various issues including a potential hard-brick. We can ensure none of that will happen by copying the contents of the active slot to the inactive slot."
But using it might prevent you from saving an APN. That would seem to make for a bit of a rock and a hard place for others who come along. Not doing it worked for you, but I'm not sure that's a risk many will take. Is there maybe a way to examine whatever these slots are ahead of time to determine if the conditions they're talking about exist? If so, how?
And I don't think the problem is it not letting you save the APN, the problem is it just isn't communicating with the modem correctly due to invalid drivers copied from the copy partition zip., so it doesn't save an APN. I believe that's just the effect, not the cause.
There is no risk not flashing the copy partition zip. I know what the zip is supposed to be doing and why. It just isn't working properly, the reason is irrelevant. As long as the stock firmware flashes the system_b and oem partition, and you followed the steps above, then it will work just fine. I'm not sure where you are getting this idea of a "risk", it makes no sense. If you're already flashing the phone, then no harm could be done?
That's why I switched to Google Fi after ~23 years w/ ATT (...& Cingular before them, & Centennial before them). And my bill is ~half now too. ;-)I learned in the U.S. that ATT has blocked receivng/making phone calls on this device.
I flashed lineage 12.1 released today.
The only issue I have is that some apps have been blocked in Play Store:
Star+ / Netflix
This happened to me in android 11, but just when I flashed magisk.
This time I just flashed lineage + mindthegapps
@rseiler @skiwarz
However I did fix my issue. There was something wrong with the system_b or oem partition, I'm guessing it was outdated. Or there is something wrong with the copy-partitions zip that is linked in official lineageos guide. Because it's a possibility I didn't even use it because the stock firmware occupied system_b and oem.
This is an issue when using LineageOS recovery on the X4. It can’t find the vendor_b partition when coming from stock. You need to use TWRP recovery on the initial install.
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
fastboot.exe getvar max-sparse-size
fastboot.exe oem fb_mode_set
fastboot.exe flash partition gpt.bin
fastboot.exe flash bootloader bootloader.img
fastboot.exe flash modem NON-HLOS.bin
fastboot.exe flash fsg fsg.mbn
fastboot.exe flash bluetooth BTFM.bin
fastboot.exe flash dsp dspso.bin
fastboot.exe flash logo logo.bin
fastboot.exe flash boot boot.img
fastboot.exe flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash system system.img_sparsechunk.3
fastboot.exe flash system system.img_sparsechunk.4
fastboot.exe flash system system.img_sparsechunk.5
fastboot.exe flash system system.img_sparsechunk.6
fastboot.exe flash system_b system_other.img
fastboot.exe flash oem oem.img
fastboot.exe erase carrier
fastboot.exe erase userdata
fastboot.exe erase ddr
fastboot.exe oem fb_mode_clear
fastboot.exe reboot bootloader
fastboot flash boot lineage-19.1-20220517-recovery-payton.img
fastboot reboot recovery
adb sideload lineage-19.1-20220517-nightly-payton-signed.zip