Pixel 9 - No mobile data

Xyzven

So I recently upgraded from my Pixel 7 running GrapheneOS (build 2025080600) to a new Pixel 9 with an eSIM running stock android. I performed the web migration to GrapheneOS (build 2025080600) and everything went swimmingly until I left for work today.

After I departed my dear home wifi, I noticed I could not play Apple music. Turns out I had 5G connectivity but it had an exclamation mark in it. I realized it was a data connectivity issue and did my research in checking things.

I have (reviewed as many threads as I could relevant to this topic in this forum)

restarted the phone,
reset the network connections, (SETTINGS > SYSTEM > RESET OPTIONS > RESET MOBILE NETWORK SETTINGS),
verified that mobile data is turned on (SETTINGS > NETWORK AND INTERNET > SIMS > MOBILE DATA set to on,
checked APN settings (SETTINGS > NETWORK AND INTERNET > SIMS > SIM1 > ACCESS POINT NAMES) and
even tried to manually enter a few new APNs to test out.
Switched to LTE, LTE Only, 3G.

None of the above items effected any change. (Edit: Roaming is on)

I can make calls and get SMS but I cannot seem to do any activities that involve data traffic. I DID not test the phone while in stock android and I am hoping to avoid that as a debug step (but I will if needed). Just need to make sure I closed off all items that should be tested/checked before reverting back.

thanks,
D

Eirikr70

Xyzven If you use a private DNS, have you tried returning to the usual DNS?

Xyzven

Eirikr70 Private DNS is off (SETTING > NETWORK & INTERNET > PRIVATE DNS). I have no need for private DNS and switching between automatic and off makes no difference.

Also, I am not using any VPNs or doing anything special/funky with connection.
Just in case, I am in Canada and using the Bell Mobile network (if anyone else experiences this issue and does a search).

n3t_admin

Xyzven I had a similar issue where I had to delete and re-provision my eSIM. I would try that next. Especially if the eSIM was already present on device at the time of install. In that case, definitely try my suggestion above.

Xyzven

n3t_admin LOL, did that yesterday thinking that was the problem. They did a "recovery" after I deleted the eSIM (yes I paid $10 for a recovery). I have tried most things I can think of and read and my last resort is to revert to stock android (after I do a seedvault backup) to see if that fixes it. I was hoping someone suggested something to try that I didn't think of.

n3t_admin

Xyzven well, that was worth a shot.

Crazy thing but... have you tried contacting Bell customer service? Sometimes it's not even your device, but something on their end.

Xyzven

I feel this is an APN issue as most people who get a fix do a manual APN.

Here is what is provided: https://support.bell.ca/mobility/smartphones_and_mobile_internet/configure_mobile_devices_for_bell_mobility_network
Name: Bell Mobility
APN: pda.bell.ca
MMSC: http://mms.bell.ca/mms.wapenc or MMSC URL: http://mms.bell.ca/mms/wapenc
MCC: 302
MNC: 610
APN protocol: IPv4/IPv6
APN roaming protocol: IPv4

Of course MCC and MNC are auto-set (looks like) by Graphene. If someone see something that doesn't make sense or seems to be missing, please let me know so that I can try that.

Xyzven

n3t_admin Only if I move to stock android and it's still not working. Because then if it indeed THEIR network issue, I will be able to revert back to Graphene knowing it was a network issue.

I'll do that. I'll move back to stock, test, and let you know. If it fixes in stock, I'll probably do one more migration back to Graphene to see if it repeats or fixes. If it repeats, then I know I have to stay in stock for now.

I'll update all here on my conclusion for knowledge purposes. Thanks all.

n3t_admin

Xyzven if you do move back to GOS after testing on Stock, remove the eSIM first from the device and only enroll it after toggling the "eSIM support" toggle in settings. That's the last thing I can think of that might be problematic.

Xyzven

n3t_admin Yeah, I was thinking that too. I might move to a physical sim today before moving back to stock as a last resort. That way provisioning is not linked to the eSIM.

Xyzven

Short story, I got impatient in the evening and didn't want to deal with any Bell rep. I also figured if I had any eSIM issue, they would not support GOS since it's not the "official" OS the phone shipped with. Moved back to stock Goog-le and lo and behold the eSIM still cannot provision the data.

It's clearly a system issue and not a GOS issue. I'll be moving to a physical SIM this afternoon just in case as I'll want to move back to GOS ASAP after I get this flippin issue fixed.

Xyzven

verified it's a provision issue with the telecom. Switched to a physical sim and issue persists, so if you are like me and tuck, it's not a GOS issue.