Closed jorgeluiscarrillo closed 2 years ago
Current suspect cause of the issue is something fishy with the handling of GIDs.
Assets are preferred over Resources because resource overlays only support using MCC+MNC and that doesn't work with MVNOs
Not sure if further investigation was done, but I suspect this issue applies to all MVNOs? Seems like the current way we are handling this is to use the resources file vendor.xml
which is why that comment caught my attention.
Another user has today reported this, with the MVNO in question being US Mobile with the infrastructure provider also being Verizon.
New report from a user on TracFone (Verizon MVNO). Similar issue as the user on US Mobile: Can't receive SMS.
I've got regular Verizon on a Pixel 5a 5g (barbet) and am unable to receive SMS. Sending works fine.
Edit: Google search brought me to this issue but it appears to be a different cause, same symptom (not receiving sms). For me, I had to contact Verizon directly and ask them to enable the CDMA-less feature on my account. OP/repo owners feel free to delete my comment unless there may be a related fix.
This should be resolved by the upcoming release.
Device: sunfish
Spectrum Mobile is a Verizon MVNO. It seems that a generic Verizon carrier config (
verizon_us-30000000115.37
) is being applied rather than the carrier config for Spectrum Mobile (spectrum_us-30000000480.37
). Various areas of the OS such as the status bar, show "Verizon" or "Verizon Wifi-Calling". Dialing*611
(customer support number) calls Verizon customer support rather than Spectrum Mobile customer support. Oddly enough, the APN is correct (verified w/ stock OS) and everything seems to work including VoLTE and VoWiFi without any further configuration. Resetting network settings does not fix it.I've extracted the carrier configs myself using the scripts in APV, but not sure how to further debug this issue.
This is the current generic Verizon carrier config that is being applied:
This is the correct carrier config for Spectrum Mobile: