Verizon eSIM not working with eOS on Pixel 8

Okay this is a weird one to me, but maybe to some of you Droid-masters it will make perfect sense:

I use US Mobile as my carrier, and they allow me to hop between networks (Verizon, T-Mobile, and AT&T) as part of my plan. This of course requires me to reinstall/provision a new eSIM each time, so I don’t do it often. I normally stick with Verizon, but recent switched to T-Mobile because I was working in an area with no Verizon coverage. Now, I want to switch back to Verizon, but the Verizon eSIM isn’t working on eOS. I worked with US Mobile support to reinstall/provision three separate eSIMs with the same result - Signal received, but no network.

Today, I tried re-flashing the stock OS and then re-flashing eOS. In the window of time on was back on stock, the eSIM was working fine. But, as soon as I was back on eOS, it stopped working again.

Anyone know what might be going on here? Is it something I can fix or something that needs to be patched? I will be away from my desk for a couple hours, so if you respond it will be a bit before I can reply.

After doing some digging, I think it may be an issue of missing Access Point Names (APNs). I got the APN info from my carrier, but I don’t know how to manually add them to the phone. Is there a way without using a third-party app?

Open settings then search in the top searchbar ‘APN’ and you should get there.

1 Like

If it helps USmobile features in this (Solved) thread Murena Teraube 2s doesn't work with USmobile? (warp)

I can find the APN settings. Within those settings I can view/edit an existing APN but cannot manually add one.

I have been using US Mobile with Warp (Verizon network) on the same phone with eOS for about 6 months without any issues. I switched to Light Speed (T-Mobile network) for a couple of weeks and only started having issues when I switched back to Warp. So, I know that as of 2-3 weeks ago the Pixel 8 running eOS on USMobile with Warp worked fine.

Trying to remember when my eOS updated from A14 to A15. Maybe something was lost in the update?

I am having a similar issue on a Pixel 8 I bought Unlocked. I installed eOS A15 official release when it became available in the /e/ web flash tool. I then moved my sim card for US Mobile Warp to the pixel 8 and couldn’t get any data or voice. After a long time with US Mobile support they couldn’t help me because I also have no + button to add more APN settings, they even tried having me download an app that was supposed to force change the APN but that did nothing except show me the directions to add manually and led to the same road block of no + sign. They ended up sending me a new SIM for the Warp network and I put the Pixel 8 back to stock A15 using google’s web flash tool so I could verify my phone wasn’t carrier locked or anything. When the new SIM arrived I activated it just fine in stock android and had voice and data. I then re flashed eOS A15 and tried it and it has the same issue as before. No voice, no data, and no ability to add to the APN settings.

I tend to think that USA apn issues are likely due to any sorts of “Lock in” you have over there.

However there is also this unresolved APN thread FP6 mobile data connection shows no internet connection and Gitlab issue where “Failure of ability to edit” is the subject.

There is a change in the pipeline for APN so input to the issue would probably be appreciated. Report an issue.

There are some possibly useful suggestions here: https://xdaforums.com/t/solved-edit-greyed-out-apn-on-pixel-7-pro-no-root.4593337/

I’m still working through it myself. I needed a working phone, so I switched to the Dark Star (AT&T) network on USMobile and was still having issues. The difference is that the + button was there after I switched and I was able to add a functional APN for Dark Star.

Why would the + button be there for one eSIM, but not the other? I would think that the ability to add an APN would be controlled by the OS (eOS in this case), but maybe I’m misunderstanding. Perhaps some carries permit you to manage the APN info and others don’t. Maybe it is locked or unlocked during the provisioning process of the eSIM.

Either way, I’m beginning to get a bit frustrated by USMobile. I may attempt one more time to switch back to Warp, and if it doesn’t work, I’ll probably leave USMobile for Visible. I’ll update this thread in the coming days with anything I learn.

I’ll have to read through the links provided by @aibd and @Taurus later tonight.

1 Like

Well, I gave up trying to get Warp (Verizon) to work on USMobile. But, I really wanted the Verizon towers, so I switched to Visible. The eSIM on Visible provisioned without any issues, the APN was preconfigured properly, and the mobile network is now working beautifully.

I can’t say with certainty that the eSIM through USMobile was the problem, but it sure seems that way.

Hope this helps.