SIMs greyed out since android 17 - Multiple devices

pfaus

Test 3

Android 16 Device - Added an eSIM + Put physical sim in
Reboot device a few times just to be sure its connected/working
Allow Android 17 update to come through
Update device. Again, reboot a few times just to make sure, sims are working fine.
Remove Physical Sim + Factory Reset (Delete eSIM option toggled)
Issue occurs.

Notes
This seems to confirm that this can be replicated by anyone as this device was tested in a way that mimics a regular users scenario.

To replicate the issue-
Remove physical Sims + Remove any eSIMS on the device
Factory Reset device
Enable eSIM Management
SIMs is now greyed out and unable to add a new eSIM until a physical sim is inserted, or the ADB command is run.

This seems to confirm this is a separate issue to the github linked ones where peoples euicc chips were faulty from factory.

Remaining Tests
1) Flash to Default Google Android 17 - See if issue is there.
2) Flash to Google Android 16 then update to Google Android 17. See if the issue is there.
To confirm if the issue happens only on Graphenes

Dont think there are any other tests for me to try

pfaus

Flashed Google default OS 17 - Same issue occurs -> Guess I gotta raise this to googs, dont think the existing tickets they have relate to this seperate issue from what I've seen

de0u

pfaus Android 16 Device - Added an eSIM + Put physical sim in
Reboot device a few times just to be sure its connected/working
Allow Android 17 update to come through
Update device. Again, reboot a few times just to make sure, sims are working fine.
Remove Physical Sim + Factory Reset (Delete eSIM option toggled)
Issue occurs.

Awesome!

Well, not really. But it's important for the GrapheneOS community to know about it, since even if Google fixes it tomorrow the source code won't be pushed for six months. 🙁

de0u

pfaus Flashed Google default OS 17 - Same issue occurs -> Guess I gotta raise this to googs, dont think the existing tickets they have relate to this seperate issue from what I've seen

I agree that what you're reporting is not a typical usage scenario, and raising it with them is probably good. Putting their ticketing info into the GrapheneOS GitHub issue would probably be useful.

pfaus

de0u Is there a proper way to raise a ticket?
I can only see Feedback in the phone section. I assume this will most likely be missed or be a while before it is read.
Cant find any place to open a ticket

de0u

pfaus It's good that the discovery process has advanced quite a bit. To be clear, the GrapheneOS developers really do not want GitHub issue threads to get six posts in half a day, with an update every time an individual experiment is run. Discussion should happen here, in the discussion forum (that's what it's for). Once details are nailed down, a single post to the GitHub thread that clearly summarizes the problem (how to reproduce, how to work around, Google ticket) will be helpful to the developers (de0u).

To that end:

When you have a ticket number from Google, please post it here (not in the GitHub issue).
My ambition is that we can agree here on a single succinct description, which can be posted once to the GitHub issue, with the expectation that there will be no further posts until a developer responds.

de0u

pfaus Is there a proper way to raise a ticket?

I think only registered Android developers can open tickets. Are you registered?

pfaus I assume this will most likely be missed or be a while before it is read.

Oh, I would expect when you file they may not read it for weeks or months! But at least you have a couple of workarounds (even one that works on the 10 devices without a physical SIM slot).

Johnnyloans

pfaus Is there a proper way to raise a ticket?

Here you can :)
https://issuetracker.google.com/issues/new?component=2080036&template=2304220

Be detailed on what happened. What works, what doesn't (clearing phone services storage)

Johnnyloans

We aren't on google build numbers, so I guess for build number put AOSP branch: android17-release

Fay_Wilmont

@pfaus

So without ADB your workarounds are:

inserting a SIM card
dialing the emergency number (possibly in a faraday bag/out of reach of cell towers/while connected to a cell controlled by you)

Is that correct?

It's a mystery to me why pm clear com.android.phone does work while clearing its data through the UI doesn't.

I noticed they added a new screen to the hidden menu accessed by dialing *#*#4636#*#* (4636 = info). The activities that can be accessed through this are part of Phone Services. Is there anything you can do from the Phone information or Phone information V2 screens that fixes the issue? Or any information listed there that provides more insight?

pfaus

Fay_Wilmont

Ive tried disabling/enabling radio and all the settings within the menu with no luck

I also tried changing the "SOS" number to a random landline instead of 000, knowing that call wouldn't go through but hoping it'd kickstart something to make it work, but unfortunately if it doesn't actually make the call, it doesnt fix the issue

pfaus

@Johnnyloans if you are developer, would you be able to raise the issue?
They closed my ticket off as I am not a developer and just pointed me to the general help forum :')

Andromxda

pfaus There are at least 6 open issues on the Google issue tracker:

hecates-hex

Not sure if this 'solution' has worked for others or been posted so apologies if doubling up on info

Greyed out sim issue with Pixel 10A (Android 17)
Unable to install esim
Developer options turned on
Sim no longer greyed out
Installed and activated esim successfully
Developer options turned off
Esim continued to work, sim option no longer greyed out, nil further issues

**esim management option was previously activated

Novaliss

hecates-hex Interesting, since so simple. Can any other user reproduce this?

hecates-hex

Novaliss I'd be really interested to know that too, honestly was very surprised it worked (and is still working)

Johnnyloans

Andromxda There are at least 6 open issues on the Google issue tracker:

These all don't look like the issue of Settings > network > SIMs is unreachable because SIMs is greyed out.

esimuser

Has anyone not experienced this issue while upgrading a GrapheneOS device (which never previously had an eSIM) from Android 16 to Android 17? I haven't seen cases of people saying it's working as expected after upgrading.

If that's true, does this mean that anyone who buys a new Pixel phone without provisioning an eSIM and installs a GrapheneOS version based on Android 17 breaks the eSIM functionality?

hecates-hex

esimuser

Yes - my pixel 9a with a working esim on android 16 upgraded to android 17 no issues.
Purchased a 10a about 3 days ago, installed graphene os and esim functionality broke.
As per previous post I have managed to get it working though by putting developer options on, installing esim then turning developer options back off.
Unsure if just got lucky or if this is something that can be replicated.

Edit:
Apologies just realised that I misread your original post so my response doesn't answer your question 😅

GrapheneOS

esimuser It's clear that it's not an issue for vast majority of people. It's also clear that it's an upstream issue not specific to GrapheneOS since there are many reports of it happening with the stock OS.

« Previous Page Next Page »