Device: Google Pixel 7 (bought from the official iodé shop) OS Version: iodéOS v6.9 Carrier / eSIM Provider: High Mobile Baseband Version: g5300q-241205-250127-B-13973597
Description of the problem:
I am experiencing serious issues with the eSIM functionality on my Pixel 7 running iodéOS v6.9.
Problems with the eSIM:
eSIM does not work correctly:
Mobile data via the eSIM is completely unavailable.
Incoming calls are very unreliable — sometimes they come through, sometimes they only appear as an SMS notification: “missed call from …”
I have conducted numerous tests over the last days in coordination with my mobile provider.
APN settings have been checked multiple times and are correctly configured.
2 different eSIMs have been sent to me both with the same results
Therefore, the problem does not lie with the provider.
Additional details:
All tests performed on both 4G and 5G networks.
All tests have been repeated without the physical SIM inserted and all other APNs deleted
The issue persists even after (numerous) reboots and network resets.
I can not „just swap to the physical SIM“ slot. It is used for another SIM.
Phone calls actually work (from time to time). In most cases I get a SMS about the missed call a few minutes later. But sometimes a phonecall works normally too.
I am seeking help or guidance: is anyone else experiencing the same problem with Pixel 7 and iodéOS v6.9? Are there known fixes or workarounds for eSIM instability or call/data issues?
Just to confirm, the eSIM registration process using the OpenEUICC app went fine, it is just that after getting registered you have the mobile data and call reliability issues?
No, I didn’t use the OpenEUICC app to register, but activated the eSIM via the normal system settings (Settings → Network & Internet → SIM cards → Add SIM card).
That shouldn’t make any difference or cause any problems, right?
The eSIM is also displayed in the OpenEUICC app (but not the physical SIM).
Sorry I have never used an eSIM so I couldn’t say. But I do know that OpenEUICC is the app to manage them, I would need to check with the team to clarify if adding an eSIM via System Settings should work the same. If it doesn’t, we should certainly hide the ability to add an eSIM from System Settings.
Are you able to delete and re-add the eSIM using OpenEUICC to confirm it also does not work?
Yes, i deleted the eSIM, and bought (10€ -.-”) a new one. 3 eSIMs tested now, last one i registered using the OpenEUICC-App. No improvement, it looks exactly the same….
Forgive me if this is too obvious, but… you do have VoLTE (4G calling) enabled, right? (Assuming it’s required or recommended by your mobile provider.)
I don’t see that you posted your carrier details. I know that they even checked the APN entry, but with some carriers even official documentation is sometimes wrong (in the USA we have had issues in the past with T-Mobile, for example, needing fast.tmobile.com instead of fast.t-mobile.com as their documentation stated (but their MMSC for MMS messages needs t-mobile.com as part of its entry, not tmobile.com as the APN needed!
As mentioned, I’ve carefully double-checked all the entries several times. With the carrier and without. I don’t think trying random variations would help at this point. On my carrier’s side, everything is confirmed to be open and all tests are green. It seems likely that the issue might be related to the eSIM registration. I’d really appreciate if we could focus on finding a solution together rather than figuring out where to place the responsibility.
Yes I fully agree. With carrier details and your current APN details we can better search for clarification on if there is a conflict between their documentation.