[LG V30 Questions & Answers] WhiteWidows:
Im trying to resolve issues with Sprint LTE data on AOSP based ROM's on converted LS998's. A quick discription of the bug/issue is 2 fold.

First upon initial boot AOSP roms are using the wrong APN's for this device. n.ispsn was depreciated for newer devices like the LS998, x.ispsn is what is needed. There was commit in LOS15 regarding the n.ispsn and x.ispsn apn issue that I dont belive was brought over to LOS16 yet, or they are using a different method of handling because x.ispsn in not in our LOS16 apn-conf.xml

https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/220026

apns: sprint: Default to legacy n.*, allow x.* as an alternative

* Newer Sprint devices will only get LTE on the x.* variant of
the APN. Though, using this breaks all legacy Sprint devices
LTE connection. until we have a majority of post 8996 era
devices, default to the n.* variant of the APN.

This can be resolved by either flashing this Sprint APN in TWRP, but note this will delete all apns except the ones needed for Sprint:

Or manually entering a new APN by going to:

1) Settings

2) Network & Internet

3) Mobile Network

4) Advance

5) Temporally change "Preferred Network Type" to "LTE / WCDMA" then go back

6) This will show "Access Point Names" choose that

7) Tap the 3 dots in the top right and pick "New APN"

8) Enter the following in the new apn

Name: Sprint LTE
APN: x.ispsn
MMSC: http://mms.sprintpcs.com
MMS proxy: oap7.sprintpcs.com
MMS port: 80
MCC: 310
MNC: 120
APN type: default,supl,mms,cbs,ia
APN protocol: IPv4/IPv6
APN Roaming protocol: IPv4/IPv6
Bearer: eHRPD, LTE

9) tap the 3 dots and choose "Save"

10) Tap the dot next to the new x.ispsn apn and make sure its highlighted.

11) Tap the back arrow in the top left

12) Tap "Preferred Network Type"

13) Chose "Global" or "CDMA + LTE/EvDo"

14) LTE should come up, if not reboot

This should get LTE(Band 25) and LTE+(Band 41) working on either the Sprint LS998 modem as well as the US998 modem. I would suggest the LS998 modem.

The next issue/bug Im running into is odd network behavior with some apps and resolving some websites. While in LTE Using Snapchat as an example as a test incoming messages work fine, but if I send a private message out, it just hangs until I reconnect to wifi or forcing 3G. The camera app WYZE will not login unless on WiFi or 3G. Also www.dslreports.com will not resolve on LTE.

x86cpu (the LS997 LOS DEV) is suggesting that there is Sprint and Verizon specific blobs and apps are missing.

We will need to "borrow" the apk's from the Pixel 2 XL "taimen" as its the same chipset which I have done and placed in the app-priv directory and applied the correct permissions.

I have went a bit further and copied all the "radio" files from the LS998 to a AOSP rom with no luck:

https://github.com/SGCMarkus/android_device_lge_joan-common/blob/lineage-16.0/proprietary-files.txt

# Radio
-app/QtiTelephonyService/QtiTelephonyService.apk
etc/permissions/qcrilhook.xml:vendor/etc/permissions/qcrilhook.xml|cf740b4339659e7a30cabcd1c2fe5066e69b8760
etc/permissions/telephonyservice.xml:vendor/etc/permissions/telephonyservice.xml|ff2c9f3456ad73f97adb7ef314fe916fa9cbfb81
framework/qcrilhook.jar:vendor/framework/qcrilhook.jar
framework/QtiTelephonyServicelibrary.jar:vendor/framework/QtiTelephonyServicelibrary.jar
lib/libril_wrapper.so:vendor/lib/libril_wrapper.so
lib/vendor.lge.hardware.radio@1.0.so:vendor/lib/vendor.lge.hardware.radio@1.0.so|22d159d210b6bc5adfd7be6cc5056d4b7790dab9
lib64/libril_wrapper.so:vendor/lib64/libril_wrapper.so
lib64/libuicc.so:vendor/lib64/libuicc.so
lib64/vendor.lge.hardware.radio@1.0.so:vendor/lib64/vendor.lge.hardware.radio@1.0.so|7c8d2bc07575131849736181ed26e4fe3c1c9c87
-priv-app/qcrilmsgtunnel/qcrilmsgtunnel.apk
-vendor/app/SVIService/SVIService.apk
vendor/bin/hw/rild
vendor/bin/ATFWD-daemon
vendor/bin/ipacm-diag
vendor/bin/netmgrd
vendor/bin/pd-mapper
vendor/bin/qti
vendor/bin/rmt_storage
vendor/bin/tftp_server
vendor/etc/data/dsi_config.xml
vendor/etc/data/netmgr_config.xml
vendor/lib/libmdmdetect.so
vendor/lib/libpdmapper.so
vendor/lib/libpdnotifier.so
-vendor/lib/libqmiservices.so
vendor/lib/libril.so
vendor/lib/vendor.qti.hardware.radio.am@1.0_vendor.so
vendor/lib/vendor.qti.hardware.radio.atcmdfwd@1.0_vendor.so
vendor/lib/vendor.qti.hardware.radio.ims@1.0_vendor.so
vendor/lib/vendor.qti.hardware.radio.lpa@1.0_vendor.so
vendor/lib/vendor.qti.hardware.radio.qcrilhook@1.0_vendor.so
vendor/lib/vendor.qti.hardware.radio.qtiradio@1.0_vendor.so
vendor/lib/vendor.qti.hardware.radio.uim_remote_client@1.0_vendor.so
vendor/lib/vendor.qti.hardware.radio.uim_remote_server@1.0_vendor.so
vendor/lib/vendor.qti.hardware.radio.uim@1.0_vendor.so
vendor/lib64/libconfigdb.so
vendor/lib64/liblqe.so
vendor/lib64/libmdmdetect.so
vendor/lib64/libnetmgr.so
vendor/lib64/libpdmapper.so
vendor/lib64/libpdnotifier.so
-vendor/lib64/libqmiservices.so
vendor/lib64/libril.so
vendor/lib64/libril-qc-ltedirectdisc.so
vendor/lib64/libril-qc-qmi-1.so|c9bdfa948b4479c9c152ef8ed6ab54a5de33af94
vendor/lib64/libril-qc-radioconfig.so
vendor/lib64/libril-qcril-hook-oem.so
vendor/lib64/librilqmiservices.so
vendor/lib64/libsettings.so
vendor/lib64/libsystem_health_mon.so
vendor/lib64/vendor.qti.hardware.radio.am@1.0_vendor.so
vendor/lib64/vendor.qti.hardware.radio.atcmdfwd@1.0_vendor.so
vendor/lib64/vendor.qti.hardware.radio.ims@1.0_vendor.so
vendor/lib64/vendor.qti.hardware.radio.lpa@1.0_vendor.so
vendor/lib64/vendor.qti.hardware.radio.qcrilhook@1.0_vendor.so
vendor/lib64/vendor.qti.hardware.radio.qtiradio@1.0_vendor.so
vendor/lib64/vendor.qti.hardware.radio.uim_remote_client@1.0_vendor.so
vendor/lib64/vendor.qti.hardware.radio.uim_remote_server@1.0_vendor.so
vendor/lib64/vendor.qti.hardware.radio.uim@1.0_vendor.so
vendor/radio/qcril_database/qcril.db

If anyone can help with this matter it would be greatly appreciated, If you are on Sprint please try to replicate these issues (Ive had one user confirm in the LOS16 thread) and if possible get a logcat.

[ROM][9.0.0]LineageOS-16.0[Joan][Unofficial]

[ROM]-[UN-Official]-Havoc-OS-2.4[9.0][H932]-[H930]

Im working on putting together a PC to build on but at the moment I cannot afford to complete it. By the end of the month hopefully it will be completed.

Any DEV's who are currently building AOSP ROM's I suggest looking into [MENTION=2881807]x86cpu[/MENTION] LS997 github and XDA thread because that device did have issue on Sprint but are now resolved. He actually builds a separate ROM for each v20 variant.

https://xdaforums.com/v20/development/rom-unofficial-lineageos-16-0-lg-v20-t3869244

https://github.com/LineageOS/android...msm8996-common

https://github.com/LineageOS/android...lge_v20-common

https://github.com/LineageOS/android_device_lge_ls997