Since the last update, I've been unable to configure the eSIM, which is in "emergency call only" mode, so I can't make or receive calls, and the same goes for SMS, even if I delete and reconfigure the APN.
I installed the same eSIM on my wife's iPhone to test it out and it works perfectly well for calls and texts.
UWB still broken on Pixel 9Pro XL.
Stewart That's unrelated to the update.
VAULT It's a known upstream bug in Android causing shortcuts to be lost in certain edge cases. We fixed a similar upstream issue for widgets recently but not shortcuts yet.
ScarletKing07 carlnickel We know Seedvault doesn't work well. It's not GrapheneOS-specific, it doesn't work well anywhere and keeps having major regressions. It's clear that it's never going to be a good app and needs to be replaced.
GrapheneOS So where is the problem coming from? I've reset the mobile network settings and even done a factory reset and the problem persists.
What can/should I do?
I have noticed that I cannot activate the esim via qr. The camera under the esim activation does not recognize the qr code.
However, if I read the qr code with the normal camera app, I get the code translated and can activate the esim manually
This is the first time I have noticed this in the new version. It worked in the previous versions.
Stewart IMEI may be blacklisted. Can you try another SIM?
GrapheneOS I don't think my IMEI is blacklisted. I tried my eSIM on my wife's iPhone and I had no problems, it works, receives and can make calls, and the same goes for messages.
What's more, I use a SIM card and an eSIM, the SIM works normally but not the eSIM, which is in "emergency call only" mode.
You're never going to believe this, my eSIM is working again, it hadn't been working for 2-3 days because in the SIM settings in "preferred network type" I had only ticked 4G and by switching it back to 5G (recommended) everything is working again.
Why ?
Would love if the 2FU could unlock the phone after the correct number of digits as the primary code can. It slows my routine already but with pressing on "enter" it takes even longer.
Also a little idea, couldn't multiple wrong 2FU pins end in the same way as multiple wrong fingerprints, so lock the phone and go for primary instead.
Does this means Whatsapp works now? I guess I'm on the last build and it just wont send a text or call to verify.
Since the last update everytime I use the camera in selfie mode, the kernel crashes and the device reboot.
slannmage
I've had no problem with WhatsApp. Stuffed it into its own profile with only Play Services, inter profile sharing, and my keyboard of choice installed.
It runs fine. Although I don't recommend putting it in your main profile. Its a Meta product that is greedy for information to share, like a complete list of all apps installed on that profile.
JollyRancher it works for me with standard android and iPhone, won't work with graphene :/ I just do not get a text or call, but it'll send a text to my phone with graphene, so something about the request sent from graphene is broken.
Stewart Maybe the provider of your esim only supports 5G? Might not effect calls, but that seems to fix it regardless. I have zero clue how Vo5G works, cellular specification are beyond me.
grapheneos-enthusiast
I never use the camera in selfie mode, but to test this phenomenon you mentioned and this is my experience:
Pixel 8 Pro and Pixel 9 Pro XL: no issue, no crashes.
Pixel 7 Pro: crashes, but w/o reboot. The rest of the system works fine.
But I have to close the camera app manually with a swipe upwards.
Eagle_Owl I'm using pixel 6a
grapheneos-enthusiast in 8a also no problem. Did you try to delete data and cashe in the camera app?
