Sprint LTE Data issues on AOSP ROM's - LG V30 Questions & Answers

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
Code:
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:
Here is a apn fix for Sprint users only I need tested.
Please do a clean install before flashing this before the first boot for best results.
If you don't do this, you may have to reset your apns to default in settings. Preferred network mode should be set to Global.
https://drive.google.com/file/d/1VK7t3fEAS263fWA9oE7yiQNcIhormO7o/view
This should bring up LTE on first boot. Worked for me but I'm still having the odd network issue. Test it and let me know.
Click to expand...
Click to collapse
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
Code:
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.
Quote:
Originally Posted by x86cpu
This was the commit, which has the needed files and what to do. You'd need to add to vendor area. You can pull out the VZW stuff. Again.. no idea if this will work.
https://github.com/x86cpu/proprietary_vendor_lge/commit/da73a25c10ffaf1b4cee00a88c0188f872db7a91
Click to expand...
Click to collapse
Quote:
Originally Posted by x86cpu
It could be the SprintDM/SprintHM .apks that are included. They are Sprint "helpers". Unsure fully what they do, but maybe. The ones for the msm8996 devices that are used for the v20/g5/g6 are pulled from the pixel (marlin), since it has the same msm8996 chipset. You'd need one similar for the v30 chipset.
Click to expand...
Click to collapse
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
Code:
# 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/[email protected]:vendor/lib/[email protected]|22d159d210b6bc5adfd7be6cc5056d4b7790dab9
lib64/libril_wrapper.so:vendor/lib64/libril_wrapper.so
lib64/libuicc.so:vendor/lib64/libuicc.so
lib64/[email protected]:vendor/lib64/[email protected]|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/[email protected]_vendor.so
vendor/lib/[email protected]_vendor.so
vendor/lib/[email protected]_vendor.so
vendor/lib/[email protected]_vendor.so
vendor/lib/[email protected]_vendor.so
vendor/lib/[email protected]_vendor.so
vendor/lib/[email protected]_vendor.so
vendor/lib/[email protected]_vendor.so
vendor/lib/[email protected]_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/[email protected]_vendor.so
vendor/lib64/[email protected]_vendor.so
vendor/lib64/[email protected]_vendor.so
vendor/lib64/[email protected]_vendor.so
vendor/lib64/[email protected]_vendor.so
vendor/lib64/[email protected]_vendor.so
vendor/lib64/[email protected]_vendor.so
vendor/lib64/[email protected]_vendor.so
vendor/lib64/[email protected]_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]
cityneversleepz said:
@whitewidow01
Same issue on Snapchat. I get theirs but they don't get mine.
Click to expand...
Click to collapse
[ROM]-[UN-Official]-Havoc-OS-2.4[9.0][H932]-[H930]
mfinlay04 said:
Yes the build name is 4/13, but on the website it shows 4/15, sorry. You are correct about dslreports, wyze, and Snapchat. I have the same issues on my device as well.
Click to expand...
Click to collapse
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 @x86cpu 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://forum.xda-developers.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

---

Thanks for this, will keep my eyes open for anything I think can help. You are right we are probably missing specific blobs for AOSP from our device.

---

Probably known, but these same limitations do not apply to 3g. I'm able to render dslreports and other perfectly while on 3g, or connected to a VPN on LTE.

---

mfinlay04 said:
Probably known, but these same limitations do not apply to 3g. I'm able to render dslreports and other perfectly while on 3g, or connected to a VPN on LTE.
Click to expand...
Click to collapse
Interesting.
I tried to use my torguard vpn and I still have the same issues. Even changed the dns to cloudflares

---

WhiteWidows said:
Interesting.
I tried to use my torguard vpn and I still have the same issues. Even changed the dns to cloudflares
Click to expand...
Click to collapse
I was using PIA. I'm going to confirm today when I get back into an area that I get LTE but I think using adaway and whitelisting websites will make them work. I'll post back to confirm you results.
Overall, the issue is 100% with Sprint LTE and the V30. I was roaming today on TMO band 4 and was able to resolve dalreports.com without issue. A few minutes later when I was back on Sprint Band 26 it failed to load

---

mfinlay04 said:
Overall, the issue is 100% with Sprint LTE and the V30. I was roaming today on TMO band 4 and was able to resolve dalreports.com without issue. A few minutes later when I was back on Sprint Band 26 it failed to load
Click to expand...
Click to collapse
Same.
I believe we need to build specifically for the ls998 and extract the proprietary vendor blobs from the stock zip, as well as the sprintdm and sprinthm apks from the pixel 2 xl. Hopefully I will attempt this soon. Then if a rom built for the ls998 work we can create a flashable zip for Sprint users on any AOSP rom to flash. I'm just spitballing here so if any devs have a better idea please chime in.

---

WhiteWidows said:
Interesting.
I tried to use my torguard vpn and I still have the same issues. Even changed the dns to cloudflares
Click to expand...
Click to collapse
WhiteWidows said:
Same.
I believe we need to build specifically for the ls998 and extract the proprietary vendor blobs from the stock zip, as well as the sprintdm and sprinthm apks from the pixel 2 xl. Hopefully I will attempt this soon. Then if a rom built for the ls998 work we can create a flashable zip for Sprint users on any AOSP rom to flash. I'm just spitballing here so if any devs have a better idea please chime in.
Click to expand...
Click to collapse
Have you tried to pull the SprintDM and HM apks from the Sprint LS998 ROM? I know that it's probably more than those two apps that are needed to fix everything but wonder why it has to be from the pixel 2xl

---

mfinlay04 said:
Have you tried to pull the SprintDM and HM apks from the Sprint LS998 ROM? I know that it's probably more than those two apps that are needed to fix everything but wonder why it has to be from the pixel 2xl
Click to expand...
Click to collapse
Not from the stock rom. I have the ones from the Pixel 2 xl in app-priv but they do nothing. There is other files that probably need to be in place. x86cpu's suggested using them from the pixel that has the same chipset.

---

Found some differences between in the android_device_lge_ls997/vendor_prop.mk and android_device_lge_joan-common/vendor_prop.mk that might be relevant:
Code:
diff -u android_device_lge_ls997/vendor_prop.mk android_device_lge_joan-common/vendor_prop.mk
--- android_device_lge_ls997/vendor_prop.mk 2019-05-12 17:21:41.891604752 -0400
+++ android_device_lge_joan-common/vendor_prop.mk 2019-05-12 17:13:08.340389278 -0400
# Radio
PRODUCT_PROPERTY_OVERRIDES += \
[ snipped ]
- ro.cdma.home.operator.numeric=310120 \
- ro.cdma.home.operator.alpha=Sprint \
- ro.telephony.default_cdma_sub=1 \
[ snipped ]
Also found the following differences between taimen (pixel 2 xl) and joan in their proprietary-files.txt from: https://github.com/CarbonROM/androi...81dd310a5dbfc387/device-proprietary-files.txt
Code:
diff -u android_device_google_taimen/device-proprietary-files.txt android_device_lge_joan-common/proprietary-files.txt
--- android_device_google_taimen/device-proprietary-files.txt 2019-05-12 17:48:00.434649463 -0400
+++ android_device_lge_joan-common/proprietary-files.txt 2019-05-12 17:13:08.340389278 -0400
[snipped]
-# Sprint/Project Fi
--app/Tycho/Tycho.apk;PRESIGNED
-etc/permissions/com.android.omadm.service.xml
-etc/permissions/com.android.sdm.plugins.connmo.xml
-etc/permissions/com.android.sdm.plugins.sprintdm.xml
-etc/permissions/obdm_permissions.xml
-etc/sysconfig/whitelist_com.android.omadm.service.xml
-lib/libdmengine.so
-lib/libdmjavaplugin.so
--priv-app/CarrierServices/CarrierServices.apk;PRESIGNED
--priv-app/CarrierSetup/CarrierSetup.apk;PRESIGNED
--priv-app/ConnMO/ConnMO.apk
--priv-app/DCMO/DCMO.apk
--priv-app/DMService/DMService.apk
--priv-app/obdm_stub/obdm_stub.apk;PRESIGNED
--priv-app/OBDM_Permissions/OBDM_Permissions.apk;PRESIGNED
--priv-app/OemDmTrigger/OemDmTrigger.apk
--priv-app/SprintDM/SprintDM.apk
--priv-app/SprintHM/SprintHM.apk
-
-# VZW
--app/VZWAPNLib/VZWAPNLib.apk;PRESIGNED
-etc/permissions/com.android.vzwomatrigger.xml
-etc/permissions/com.verizon.apn.xml
-etc/permissions/com.verizon.embms.xml
-etc/permissions/com.verizon.llkagent.xml
-etc/permissions/com.verizon.provider.xml
-etc/permissions/com.verizon.services.xml
-etc/permissions/features-verizon.xml
-etc/permissions/vzw_mvs_permissions.xml
--framework/VerizonUnifiedSettings.jar;PRESIGNED
-priv-app/MyVerizonServices/lib/arm64/libmotricity.so
--priv-app/MyVerizonServices/MyVerizonServices.apk;PRESIGNED
--priv-app/VerizonAuthDialog/VerizonAuthDialog.apk;PRESIGNED
--priv-app/VzwOmaTrigger/VzwOmaTrigger.apk;PRESIGNED
--priv-app/WfcActivation/WfcActivation.apk;PRESIGNED
[snipped]
Additionally, you will probably need to copy the DM_* parts from the taimen Android.mk here: https://github.com/CarbonROM/androi...abd73db1dae171031b81dd310a5dbfc387/Android.mk
Code:
DM_LIBS := libdmengine.so libdmjavaplugin.so
DM_SYMLINKS := $(addprefix $(TARGET_OUT)/priv-app/DMService/lib/arm/,$(notdir $(DM_LIBS)))
$(DM_SYMLINKS): $(LOCAL_INSTALLED_MODULE)
@echo "DMService lib link: [email protected]"
@mkdir -p $(dir [email protected])
@rm -rf [email protected]
$(hide) ln -sf /system/lib/$(notdir [email protected]) [email protected]
ALL_DEFAULT_INSTALLED_MODULES += $(DM_SYMLINKS)

---

P_1 said:
Found some differences between in the android_device_lge_ls997/vendor_prop.mk and android_device_lge_joan-common/vendor_prop.mk that might be relevant:
Also found the following differences between taimen (pixel 2 xl) and joan in their proprietary-files.txt from: https://github.com/CarbonROM/androi...81dd310a5dbfc387/device-proprietary-files.txt
Additionally, you will probably need to copy the DM_* parts from the taimen Android.mk here: https://github.com/CarbonROM/androi...abd73db1dae171031b81dd310a5dbfc387/Android.mk
Click to expand...
Click to collapse
I wonder if these changes would allow for project fi service on a v30?

---

From what I know, Sprint is the underlying carrier for project fi, so I think it should work once Sprint is working.

---

P_1 said:
From what I know, Sprint is the underlying carrier for project fi, so I think it should work once Sprint is working.
Click to expand...
Click to collapse
It is.

---

Bump and thanks in hopes Verizon ready AOSP and Lineage ROMS exist in the future

---

Thanks for this. Very informative. I been having issues with Havoc and Sprint to properly work. Mostly with the mms service. Cant reply on group mss chats.
Im on LS998>US998>Havoc
Question: Do I need to flash LS998 modem each time I dirty flash a new version of Havoc?
Again Thanks for this!!

---

WhiteWidows said:
It is.
Click to expand...
Click to collapse
What rom are you currently using?

---

Hey @WhiteWidows
I just wanted to leave a short ty message for you for taking the time to put all of this information into a guide, and in its own thread.
Just between you and I theres been many, too many hours spent trying to fix this issue. From hacking into sprint's device, understanding the problem, reverse engineering their bull****, debugging and testing testing testing... Thank You for making this one of your priorities!
I will be busy this weekend (next few days) so I cant test much, but if you dont mind I have just one quick yes or no question: Can we start thinking about using our LS998's on Sprint as a daily driver phone, with AOSP ROM's now? I will read your post more thoroughly when I can to understand specifics a little better, but for now I would be thrilled if the answer to that is anything but "NO!" haha
~syndre

---

Any news on getting things to work correctly?

---

jhienk said:
Any news on getting things to work correctly?
Click to expand...
Click to collapse
A test build of LOS was just released.
https://drive.google.com/open?id=1IBGi-6dp3KwXsRysfXpPzy6rQccnT7Wy

---

WhiteWidows said:
A test build of LOS was just released.
https://drive.google.com/open?id=1IBGi-6dp3KwXsRysfXpPzy6rQccnT7Wy
Click to expand...
Click to collapse
Need logs of the stuff there appearantly crashing, pls thx ^^

---

SGCMarkus said:
Need logs of the stuff there appearantly crashing, pls thx ^^
Click to expand...
Click to collapse
Hopefully tomorrow I can get one, I needed my phone all day today. But I should be able to grab it after work tomorrow.