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.

zodiac-glove

Hi folks, reporting in that I'm on Pixel 9, have used eSims without issue on stock OS for about a year (including today). Just installed GrapheneOS today, can't enable a new esim (yes, esim has been enabled) similar to other commenters.

For clarity, my phone is combination physical and esim, the physical sim still works fine.

Can't report whether the existing esim still works as I wasn't aware that esims are not stored on the OS, and requested a replacement esim, now can't enable the new one.

I think this is a GrapheneOS issue based on the fact my esim was working a-okay for over a year, and still working today on stock OS.

I will provide logs as soon as I figure out how. Of course I am biased, but I believe this is a decently serious issue because it makes core functionality to a phone.

Kind regards.

MetropleX

Just a heads up that the relevant dev in the team who needs to put eyes on the logs has them.

pixelpls

I can confirm the issue on a used pixel 9 pro that I bought yesterday (with factory rom):

boot device with factory rom without sim card, install latest updates
install graphene os according to the website instructions
install google play, services in the owner profile, log in with google account
activate eSIM support, reboot
add new sim card, set up esim
scan QR code OR paste activation code supplied by carrier
sim card not activated, with this information (German):

SIM nicht aktiviert

Beim Aktivieren deiner SIM ist ein Fehler aufgetreten.

Unfortunately, this leads me with an unusable phone until I re-order a physical SIM.

Some logs that seem interesting:

04-07 06:39:02.137  2948  4539 I EuiccGoogle: [157] NetworkCache.switchToEmbeddedSlot: switchToEmbeddedSlot hasEsimFeature: true, isEuiccSlotPresent: false, multiSim: true, isSlotSwitchRequired: true, allowSlotSwitchInMultiPsimEsimMode: false
04-07 06:39:02.137  2948  4539 E EuiccGoogle: [157] NetworkCache.switchToEmbeddedSlot: Slot switch is not allowed in multiSim mode, ignore switch request

04-07 06:39:02.164  2948  2948 I EuiccGoogle: [2] NetworkCache.getFirstActiveEuiccSlotId: isRemovableEsimDefault: false
04-07 06:39:02.166  2948  2948 I EuiccGoogle: [2] EuiccServiceImpl.onCreate: onCreate DSDS mode: simCardState is 0
04-07 06:39:02.167  2948  4539 I EuiccGoogle: [157] IInternalEuiccService$Stub.executeDiscoveryJob: IInternalEuiccService.executeDiscoveryJob
04-07 06:39:02.167  2948  4539 I EuiccGoogle: [157] NetworkCache.getFirstActiveEuiccSlotId: isRemovableEsimDefault: false
04-07 06:39:02.168  2948  4539 I EuiccGoogle: [157] EuiccServiceImpl.ensureSlotIsEuiccAndActive$ar$ds: ensureSlotIsEuiccAndActive: slotId = -1, forceDeactivateSim = false
04-07 06:39:02.168  2948  4539 I EuiccGoogle: [157] EuiccServiceImpl.ensureSlotIsEuiccAndActive$ar$ds: Passed in slotId=-1; euiccIsActive=false; targetSlotIsRemovable=false; forceDeactivateSim=false, multiSimEnabled=true, euiccSlotPresent=false, allowSlotSwitchInMultiPsimEsimMode=false.
04-07 06:39:02.168  2948  4539 E EuiccGoogle: [157] EuiccServiceImpl.ensureSlotIsEuiccAndActive$ar$ds: Slot switch is not allowed in multiSim mode, ignore switch request
04-07 06:39:02.168  2948  4539 I EuiccGoogle: [157] EuiccServiceImpl.onGetDefaultDownloadableSubscriptionList: onGetDefaultDownloadableSubscriptionListInternal: ensureSlotIsEuiccAndActive = EuiccOperationResult{errorCode=131083, switchedToEsim=false, slotMappings=[]} eventType = 5.

04-07 06:39:03.598  2948  2948 I EuiccGoogle: [2] NetworkCache.getFirstActiveEuiccSlotId: isRemovableEsimDefault: false
04-07 06:39:03.599  2948  2948 I EuiccGoogle: [2] EuiccServiceImpl.onCreate: onCreate DSDS mode: simCardState is 0
04-07 06:39:03.599  2948  2948 I EuiccGoogle: [2] Partner.getResourceEntry$ar$ds$ar$class_merging$ar$class_merging$ar$class_merging: Partner app=com.google.android.euiccoverlay, Resource name=esim_supported_countries, type=string, partnerResId = 0
04-07 06:39:03.599  2948  2948 I EuiccGoogle: [2] Partner.getResourceEntry$ar$ds$ar$class_merging$ar$class_merging$ar$class_merging: Partner app=com.google.android.euiccoverlay, Resource name=esim_unsupported_countries, type=string, partnerResId = 2131689526
04-07 06:39:03.599  2948  2948 I EuiccGoogle: [2] PhenotypeUpdatedReceiver.setPsimConversionSupportedCarriers: pSIM conversion feature is not enabled
04-07 06:39:03.603  2948  4556 I EuiccGoogle: [166] EuiccServiceImpl.ensureSlotIsEuiccAndActive$ar$ds: ensureSlotIsEuiccAndActive: slotId = 0, forceDeactivateSim = false
04-07 06:39:03.603  2948  4556 I EuiccGoogle: [166] EuiccServiceImpl.onGetDefaultDownloadableSubscriptionList: onGetDefaultDownloadableSubscriptionListInternal: ensureSlotIsEuiccAndActive = EuiccOperationResult{errorCode=131082, switchedToEsim=false, slotMappings=[]} eventType = 0.
04-07 06:39:03.603  2948  4556 I EuiccGoogle: [166] ViewCompat$Api30Impl.setTokenRegistrationRetryRequired:  eventType: 0 isRetryRequired: true
04-07 06:39:03.603  2948  4556 I EuiccGoogle: [166] ViewCompat$Api30Impl.setTokenRegistrationRetryRequired: Not push token registration, ignore
04-07 06:39:03.603  2948  4556 I EuiccGoogle: [166] EuiccServiceImpl.onGetDefaultDownloadableSubscriptionList: onGetDefaultDownloadableSubscriptionList errorCode: 131082
04-07 06:39:03.604  2948 23577 I EuiccGoogle: [146] WindowInsetsCompat$TypeImpl30.isEsimOnlyDevice: Device Hardware SKU: GEC77
04-07 06:39:03.606  2948 23577 I EuiccGoogle: [146] ClearcutServerLog$$ExternalSyntheticLambda15.call: NetworkUtil
04-07 06:39:03.607  2948  3152 D GEuiccLpa: replaced getText() with empty string: %1$s hat Probleme mit Google Play-Diensten. Bitte versuche es noch einmal.
04-07 06:39:03.607  2948  2948 I EuiccGoogle: [2] EuiccOperationSidecar$1.onReceive: Result code : 2; detailed code : 131082
04-07 06:39:03.607  2948  3152 W GooglePlayServicesUtil: com.google.android.euicc requires the Google Play Store, but it is missing.
04-07 06:39:03.607  2948  3152 W GoogleApiManager: The service for com.google.android.gms.usagereporting.internal.UsageReportingClientImpl is not available: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null, clientMethodKey=null}
04-07 06:39:03.607  2948  2948 E EuiccGoogle: [2] GetMetadataFromDefaultServersFragment.onStateChange: Error retrieving default subscription list with result code: 2.
04-07 06:39:03.607  2948  3152 D GEuiccLpa: replaced getText() with empty string: %1$s hat Probleme mit Google Play-Diensten. Bitte versuche es noch einmal.
04-07 06:39:03.607  2948  2948 I EuiccGoogle: [2] SmdsDownloadActivity.onNext: eSIM SMDS activation flow: requestCode = 15, result = 3
04-07 06:39:03.607  2948  3152 W GooglePlayServicesUtil: com.google.android.euicc requires the Google Play Store, but it is missing.
04-07 06:39:03.607  2948  2948 I EuiccGoogle: [2] DownloadActivity.finishWithResult: finishWithResult: result code = 6.

04-07 06:39:13.376  2948  2948 I EuiccGoogle: [2] EuiccOperationSidecar$1.onReceive: Result code : 2; detailed code : 33564438
04-07 06:39:13.376  2948  2948 I EuiccGoogle: [2] GetMetadataFromSubscriptionFragment.getNextSubMetadataOrDeliverResults: Successfully get 0/1 profiles' metadata out of 1.

If helpful, I can supply the full logs.

Johnnyloans

pixelpls Some logs
@MetropleX

Welcome to the club mate! The pixel 9 family has more issues with the esim--even on stockOS. Return now if you desire esim functionality like for 2 or more saved SIMs for travel or what not.

Sorry this happened :[
Thanks for the logs

Johnnyloans

pixelpls

I can forward your logs to the developers if you wish. You can find my email under my profile:
https://discuss.grapheneos.org/u/Johnnyloans

It looks like your phone tried to use esim slot -1 first thing.

error code 13108\d is consistent with the other failure logs that I've seen.

Most esim failure logs say:
Failed to get downloadable subscriptions from SM-DS lpa.live.esimdiscovery.com
Failed to retrieve EuiccInfo2
Unable to retrieve eOS version

It appears that the Pixel 9 family has more issues with esims. Sorry mate, if it's important to have 2+ SIMs for travel or whatnot, I'd return or warranty the phone.

Mixxer5

Hello. I've similar issue to other people here- trying to register esim fails with "sim not activated" message (I don't use qr code but LPA text) on Pixel 9 xl pro.
Few things of note:

Error message is instant and the same no matter what I type (even a single letter produces same result).
Disabling DSDS seems to cause infinite loading animation instead of error message.
Most curious thing, imo- when I followed instructions from previous post to reset network/erase esims different things happened:
A. [Resetting network] Entering PIN to auth request had no effect (multiple times, PIN was correct).
B. [Erasing esims] - seemingly succeeded, got no success/error message.
C. [Resetting network] got me an error message (resetting device didn't help) - can't erase Esims, something went wrong, try restarting device.

Attaching logs (this is just a sample, I've 500kb from 15 attempts but I don't see an option to attach file here)

beginning of main
04-07 19:31:34.237 10121 3067 3067 I EuiccGoogle: [2] Partner.getResourceEntry$ar$ds$ar$class_merging$ar$class_merging$ar$class_merging: Partner app=com.google.android.euiccoverlay, Resource name=esim_supported_countries, type=string, partnerResId = 0
04-07 19:31:34.237 10121 3067 3067 I EuiccGoogle: [2] Partner.getResourceEntry$ar$ds$ar$class_merging$ar$class_merging$ar$class_merging: Partner app=com.google.android.euiccoverlay, Resource name=esim_unsupported_countries, type=string, partnerResId = 2131689526
04-07 19:31:34.256 10121 3067 3275 W GooglePlayServicesUtil: com.google.android.euicc requires the Google Play Store, but it is missing.
04-07 19:31:34.256 10121 3067 3275 W GooglePlayServicesUtil: com.google.android.euicc requires the Google Play Store, but it is missing.
04-07 19:31:34.260 10121 3067 3275 W GooglePlayServicesUtil: com.google.android.euicc requires the Google Play Store, but it is missing.
04-07 19:31:39.269 10121 3067 3275 W GooglePlayServicesUtil: com.google.android.euicc requires the Google Play Store, but it is missing.
04-07 19:31:47.591 10121 3067 3275 W GooglePlayServicesUtil: com.google.android.euicc requires the Google Play Store, but it is missing.
04-07 19:31:47.591 10121 3067 3275 W GooglePlayServicesUtil: com.google.android.euicc requires the Google Play Store, but it is missing.
04-07 19:31:47.594 10121 3067 3275 W GooglePlayServicesUtil: com.google.android.euicc requires the Google Play Store, but it is missing.
--------- switch to system
04-07 19:32:57.660 1000 1387 1886 D ActivityManager: freezing 3067 com.google.android.euicc
--------- switch to events
04-07 19:32:57.663 1000 1387 1886 I am_freeze: [Pid=3067,Process Name=com.google.android.euicc]
04-07 19:32:59.057 1000 1387 1886 I am_compact: [Pid=3067,Process Name=com.google.android.euicc,Action=ANON,BeforeRssTotal=381376B,BeforeRssFile=202316B,BeforeRssAnon=177876B,BeforeRssSwap=61140B,DeltaRssTotal=-177876B,DeltaRssFile=0B,DeltaRssAnon=-177876B,DeltaRssSwap=181696B,Time=1.391s,FULL,2090145,905,19,1388488,-70200]
--------- switch to main
04-07 19:33:24.866 10081 7630 7630 D LogcatActivity: command: logcat --buffer=main,system,crash,events,kernel -d --dividers --format=UTC,printable,uid,descriptive --regex=com.google.android.euicc *:V !<

Pinging @Johnnyloans as requested

As a side note- this seems a bit odd that relatively mature phone has this many esim related issues just recently and those seem to impact GOS users mostly. Yeah, there are reports from stock users having esim issues but I've done some searching and this thread alone has 4 or 5 impacted people. Had it been a hardware issue, wouldn't it be a lot more widespread problem, reported a lot more by stock users?

Johnnyloans

Mixxer5

greetings,
Mandatory, I don't speak for GrapheneOS.

Nice observations and thank you. My email is in my profile for sending logs. Please label each log file and possibly add a description differentiating the files in the email if there is a lot of context. (e.g. DSDS is off and inputting garbage for the manual activation code)

These snippets don't have anything important. The 1st one says Sending google telemetry isn't functioning on your GOS phone. Working esims say this as well.

1) Usually the failure happens in the first few seconds after pushing add esim, before the QR code or manual code.
2) Some carriers/phones experience this. It is noted under esim support.

Note that if the eSIM installation process does not progress past the "Checking network info..." stage despite having a stable Internet connection, you may need to ... enable DSDS ...
-https://grapheneos.org/usage#rcs
3) That'll be good if you have the logs from this session.

this seems a bit odd that relatively mature phone has this many esim related issues just recently and those seem to impact GOS users mostly.

The pixel 8/8pro/8proXL has a display ribbon cable that rubs up against metal, potentially cutting into it for some users.
This Australian telecom observed high failure rate on stockOS pixel 9s in particular as well as other pixels.
https://airsims.com.au/blogs/blog/google-pixel-9-pixel-series-esim-issues-chip-failures-our-refund-promise

There could be substance to your observations; however, there are 300k-400k GOS users I believe. I've seen ~8 people reporting an issue. Some of those are with brand new phones untested in stockOS.
Related to this conclusion: not accounting for base rate, selection bias, availability heuristic.

I've done this before too. Everyone on a huge forum are aligned and then real life turns out far different.

Mixxer5 install OpenEUICC

It'll be interesting if you find something interesting.

If esim is important to you for 2+ SIMs for travel or whatnot, I'd attempt to return the phone or warranty it if you're within the allotted time period.

Mixxer5

And here are logs from Sim Manager when DSDS is off. I put garbage as a value but from what I understand it fails to make a connection anyway:
switch to main 04-07 20:46:10.778 3295 3498 W GoogleApiManager: The service for com.google.android.gms.clearcut.internal.ClearcutLoggerClientImpl is not available: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null, clientMethodKey=null} 04-07 20:46:10.778 3295 3295 D WindowOnBackDispatcher: setTopOnBackInvokedCallback (unwrapped): null 04-07 20:46:10.778 3295 3498 I ClearcutMetricXmitter: Transmission has failed: com.google.android.gms.common.api.ApiException: 17: API: ClearcutLogger.API is not available on this device. Connection failed with: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null, clientMethodKey=null} 04-07 20:46:10.782 3295 3295 D ViewRootImpl: Skipping stats log for color mode 04-07 20:46:20.770 3295 3495 W ProxyAndroidLoggerBackend: Too many Flogger logs received before configuration. Dropping old logs. 04-07 20:46:20.771 3295 3495 W ProxyAndroidLoggerBackend: Too many Flogger logs received before configuration. Dropping old logs. 04-07 20:46:20.771 3295 3498 D GEuiccLpa: replaced getText() with empty string: %1$s is having trouble with Google Play services. Please try again. 04-07 20:46:20.772 3295 3498 W GooglePlayServicesUtil: com.google.android.euicc requires the Google Play Store, but it is missing. 04-07 20:46:20.772 3295 3498 W GoogleApiManager: The service for com.google.android.gms.usagereporting.internal.UsageReportingClientImpl is not available: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null, clientMethodKey=null} 04-07 20:46:20.773 3295 3498 E CheckboxChecker: fetching usage reporting opt-in failed 04-07 20:46:20.773 3295 3498 E CheckboxChecker: com.google.android.gms.common.api.ApiException: 17: API: UsageReporting.API is not available on this device. Connection failed with: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null, clientMethodKey=null} 04-07 20:46:20.773 3295 3498 E CheckboxChecker: at com.google.android.gms.clearcut.internal.batcher.DropLargestEventBatchReductionAlgorithm.fromStatus(PG:13) 04-07 20:46:20.773 3295 3498 E CheckboxChecker: at com.google.android.gms.common.api.internal.ApiCallRunner$TaskRunner.reportFailure(PG:3) 04-07 20:46:20.773 3295 3498 E CheckboxChecker: at com.google.android.gms.common.api.internal.GoogleApiManager$ClientConnection.failEnqueuedMethods(PG:48) 04-07 20:46:20.773 3295 3498 E CheckboxChecker: at com.google.android.gms.common.api.internal.GoogleApiManager$ClientConnection.failAllEnqueuedMethods(PG:10) 04-07 20:46:20.773 3295 3498 E CheckboxChecker: at com.google.android.gms.common.api.internal.GoogleApiManager$ClientConnection.onConnectionFailed(PG:164) 04-07 20:46:20.773 3295 3498 E CheckboxChecker: at com.google.android.gms.common.api.internal.GoogleApiManager$ClientConnection.onConnectionFailed(PG:174) 04-07 20:46:20.773 3295 3498 E CheckboxChecker: at com.google.android.gms.common.api.internal.GoogleApiManager$ClientConnection.connect(PG:163) 04-07 20:46:20.773 3295 3498 E CheckboxChecker: at com.google.android.gms.common.api.internal.GoogleApiManager$ClientConnection.enqueue(PG:51) 04-07 20:46:20.773 3295 3498 E CheckboxChecker: at com.google.android.gms.common.api.internal.GoogleApiManager.handleMessage(PG:844) 04-07 20:46:20.773 3295 3498 E CheckboxChecker: at android.os.Handler.dispatchMessage(Handler.java:128) 04-07 20:46:20.773 3295 3498 E CheckboxChecker: at android.os.Looper.dispatchMessage(Looper.java:333) 04-07 20:46:20.773 3295 3498 E CheckboxChecker: at android.os.Looper.loopOnce(Looper.java:263) 04-07 20:46:20.773 3295 3498 E CheckboxChecker: at android.os.Looper.loop(Looper.java:367) 04-07 20:46:20.773 3295 3498 E CheckboxChecker: at android.os.HandlerThread.run(HandlerThread.java:139) 04-07 20:46:20.773 3295 3498 D GEuiccLpa: replaced getText() with empty string: %1$s is having trouble with Google Play services. Please try again. 04-07 20:46:20.773 3295 3498 W GooglePlayServicesUtil: com.google.android.euicc requires the Google Play Store, but it is missing. 04-07 20:46:20.773 3295 3498 W GoogleApiManager: The service for com.google.android.gms.clearcut.internal.ClearcutLoggerClientImpl is not available: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null, clientMethodKey=null} 04-07 20:46:20.774 3295 3498 I ClearcutMetricXmitter: Transmission has failed: com.google.android.gms.common.api.ApiException: 17: API: ClearcutLogger.API is not available on this device. Connection failed with: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null, clientMethodKey=null} 04-07 20:46:55.351 3295 3295 I EuiccGoogle: [2] EuiccServiceImpl.onDestroy: onDestroy: EuiccService on destroy.

Edit: I'm somewhat tempted to try to root my device and install OpenEUICC as a system app to see if it would manage to get it working. I won't as tomorrow I should have new physical SIM and I don't care that much about esim but I'm definitely curious.

rofmol

I think I'm experiencing the same issue. I have a pixel 9 pro, eSIM couldn't activate after I flashed GOS. I didn't attempt before. Would it be helpful to post logs here? I'm not sure how to do that yet, but I can figure it out.

de0u

zodiac-glove I want to reiterate that my eSIM was working fine on Pixel 9 stock OS before coming to GrapheneOS.

I'm not a dev, but I'm not sure how that couldn't be GrapheneOS related.

Related to, maybe, but that doesn't mean the same thing as caused by (see: post-hoc fallacy).

The link provided by Johnnyloans doesn't mention GrapheneOS, and it seems quite possible that the carrier isn't even aware of GrapheneOS. Note that part of that page is:

It may occur after:

A routine software update

A system crash or freeze

Battery depletion

Restarting the device

Physical chip degradation as device ages

Electronic failure due to heat cycling (phones are surprisingly subject to extremes, such as being left in the sun, vibrations, cold, humidity)

No clear reason at all (any combination of the above factors)

Your eSIM may stop working overnight even though nothing changed.

Note that many Android devices are not restarted except for system updates, and that GrapheneOS devices are restarted for system updates more often than devices running Google's stock OS. So if it's true that every device restart has some small risk of an EUICC failure then running GrapheneOS could be associated with a higher rate of EUICC failure than running the stock OS. To be clear, I don't know how relevant those listed factors are, but it's one way that related to and caused by might not be the same.

Hopefully if there is a big spike of reports to Google of EUICC failures on Pixel 9 devices Google will do something. If there is a systematic problem, perhaps it's reversible.

de0u

goda90 Multiple people in this thread are reporting that the eSIMs work in stock at first, then they flash gOS and it stops working, then they revert to stock and it still doesn't work.

True, but six days ago in this thread it was made clear that this is happening often enough that at least one carrier has a web page about it (Johnnyloans de0u).

goda90 Google isn't going to be interested in fixing something that appears to be caused by flashing another OS.

If it happens to users who flash GrapheneOS and users who never flash GrapheneOS then... ...perhaps Google won't be interested in it, but if they're not interested in it then their disinterest won't be caused by GrapheneOS.

pixelpls

Johnnyloans

Thanks for your soothing words. However, I'm not planning on returning the phone. I have ordered a physical SIM as a workaround. I have the feeling that this bug is GOS related as users mentioned eSIM working on stock before flashing GOS. There is also this issue on GitHub dealing with the same (?) problem, including full logs: https://github.com/GrapheneOS/os-issue-tracker/issues/7541

Anyway, I'd like to help resolve this or narrow it down to make eSIM usage on GOS more robust. Any idea how I could participate or which is the best channel to provide information on this or other issues (this thread, GitHub, Matrix, Discord,...)? Where/how would you

forward [my] logs to the developers if [I] wish

zodiac-glove

I think the selection bias goes both ways here, both that only certain users will bother posting to forums, and because many users never use eSIM at all - and wouldn't be aware something is broken.

I want to reiterate that my eSIM was working fine on Pixel 9 stock OS before coming to GrapheneOS.

I'm not a dev, but I'm not sure how that couldn't be GrapheneOS related.

Apologies for not providing my own logs yet, but there's a but of a learning curve for me to make sure I'm not leaking personal information.

Kind regards.

Johnnyloans

zodiac-glove

It might say your carrier or your 2 character country code. Search the 3 character country code just in case.

Johnnyloans

pixelpls

MetropleX is a moderator with their contact info on their profile: https://discuss.grapheneos.org/u/MetropleX

You can message them privately.

MetropleX

Okay I have been provided feedback from the developer:

Unfortunately, none of those logs include the actual radio log buffer like the framework server code that talks to the eUICC. The logs are only from the code from Google's eUICC app that talks to the framework's EuiccController

We would need a system log (with the radio log buffer enabled in the top-right menu, because it's disabled by default) this is required to be done, AFTER attempting eSIM activation or a full bug report, both of which would contain sensitive info.

The emphasis above being mine, I would like to request that if people here are comfortable in continuing to assist that they contact/reach out to myself on Matrix or Discord so that I can safely collect and collate the logs and provide them again to the developer looking into and after this case.

They did also try to reproduce the problem on BOTH Pixel 9 & Pixel 9 Pro, activating several eSIMs (2 on Pixel 9, 1 on Pixel 9 Pro) and wasn't able to with them, being successful on all occasions.

drydosera

MetropleX Most of the reports seem to be on the 9XL Pro. I wonder if there is a hardware defect in some production runs that made the euicc chips vulnerable to firmware changes. Maybe tied to region? That may explain why the issue is reproducible for some users.

« Previous Page Next Page »