Unable to activate eSIM

Foyer9054

None of the links you provided are relevant to the specific issue experienced in this thread. Links 1 & 2 don't describe anything comparable. 3 is specifically "Scan QR code from EE", likely network locked. 4 is unrelated.

One of the first things people should do before instantly thinking we have a process breaking bug

Nobody here "instantly" assumed GrapheneOS had a process breaking bug.
Multiple people have flashed stock, tested, ordered new phones, tested, and narrowed it down to the process of flashing GrapheneOS. I have confirmed this with two Pixels, and so has aceblack and a couple of others.
So it's quite reasonable that we expect the install of GrapheneOS the be the cause.

Something people could try is grabbing the QR data and seeing if they can add it manually which appeared to work for one user in the previous links.

This has already been tried in this thread and does not work. The eUICC appears to be stuck in a read only state.

GrapheneOS

Foyer9054 There's no actual evidence of it being caused by GrapheneOS. There are reports of it happening with the stock OS, so why do you think it's GrapheneOS causing it?

Foyer9054

GrapheneOS

The evidence is mine and aceblack's scenarios: noticed eSIM not working after flashing GrapheneOS, flashed stock and still didn't work, bought another Pixel 9 Pro XL, eSIM confirmed working on stock, flashed GrapheneOS, eSIM broken (writes like adding/erasing), reflashed stock and still broken. As well as others comments here where they confirmed eSIM worked on stock but not after flashing GrapheneOS.

That's a reproducible sequence on a fresh device where the issue begins when GrapheneOS is installed.
The same logic applies in reverse, there's no evidence that GrapheneOS isn't the cause either.
The reports of Pixel 9 Pro XL eSIM issues online like the ones linked previously are unrelated, so can't be used as evidence.

MetropleX

Foyer9054 then foyer if we are to progress this and ascertain actual causes we're going to need people to start providing logs.

These can be provided to any of the team via Matrix or Discord DMs or by the contact details. When the issue isn't being reported en mass by all 9th Gen users across all release channels for updates and being reported in our testing rooms there is a limit to the support we can provide, especially when our own development devices are not able to replicate.

I appreciate the issue may be frustrating to you and the others experiencing it but until we get the aforementioned logs there isn't much we can do and repeatedly directing the cause to the OS is not productive. A quick look over our releases demonstrates a reactivity to issues we can find and fix where a downstream solution exists.

Johnnyloans

I forwarded the logs from: drydosera, GR0DA, maximilanpegasus, and shawnsc to MetropleX.

« Previous Page