I got my S8 G950FD running using e-0.9-p-2020051454091-dev-dreamlte.zip and connected to wifi without a problem. Put in a working Verizon SIM and registered to the network from “automatically select network”. Phone Services reports "Selected network (Verizon Wireless) unavailable.
I re-flashed the original stock image and then recreated the /e/ install. Same result. Calls work with stock but not with /e/. Does anybody have the same issue or a functional S8?
If you don’t have a network with your SIM card, this may be due to the APN settings. With this setting, your S8"dreamlte" knows which network it should dial into at best.
APN is the abbreviation for Access Point Name. The best way to find out is to go to your mobile operator’s help pages on the Internet. There you will find the APN data. Now you’ve to match this data with the settings in the menu of your device.
Device > Settings > Mobile networks > Access point names > APNs
Under APNs, the phone showed 4 choices with the “Verizon Internet” option selected. When I hold down the choice to edit, it’s all greyed out with the relevant options (MMSC, port, etc.) showing “not set”. I don’t see any way to add a APN or edit the existing ones.
Verizon Wireless is known for its restrictive distribution policy. For example, they block bootloaders for life. Maybe they have SIM protection against custom ROMs?
6…Is my 4G SIM card compatible with any other provider’s device? Possibly. Many providers are GSM-based (meaning their service also uses a SIM card), however, Verizon Wireless can only support Verizon Wireless-Certified 4G devices. See a list of Verizon Wireless certified devices.
Samsung’s Galaxy S8 is in the list of Verizon Wireless certified devices - with StockROM Android. Verizon is a known opponent of custom ROMs.
I went in to the Verizon store and they claim that the IMEI on the device doesn’t work with the Verizon network. Strange because I successfully made a call with the stock ROM.
But there is the problem S8 G950FD + Custom ROM to solve. We’ve to find out if the problem is due to LineageOS or /e/ OS. Therefore it would be good to try an (unofficial) LineageOS ROM or an AOSP ROM to narrow down the issue.