Pixel 10 - Support for GrapheneOS is now available!

Dboy

I made it twice and both are orange

Dboy

nandohyphen1 what is your device?

nandohyphen1

Dboy I have a Pixel 6a. I'll see what else I can find out about Auditor being orange and if I find anything I'll follow up in the other thread you created.

de0u

wizoatk I think I found it.

I agree. Thanks!

Dboy

nandohyphen1 You can have a look. Now it works: avoid clearing pairings during the 2 processes. Then green background should appear.

Cheers!

spl4tt

I also don't really understand auditor. My Pixel 9 Pro Fold and Pixel 10 Pro XL are green, while my Pixel 8 Pro is orange.

Do older devices just don't have enough hardware security features?

Novalissoide

spl4tt Pixel 8 Pro is orange.

Do older devices just don't have enough hardware security features?

P8p isn't lacking features, Auditor lacks explaination for the colours indexing to respective verdict/meaning/coding/correspondence. This is constructive critique not bashing at all, and I've been totally wrong before so please correct me if I'm in the wrong furthermore.

https://attestation.app/
At any of the adjecent clickables

here; try search 'Green', 'Color', 'Colour', 'Yellow', 'Verdict', 'Indication', and any of the like you'll find no help about the colours.

3ch0

Hi everyone! Just installed GOS on a P10Pro, been waiting for a long time. Everything seems to work fine (still reconfiguring everything, since I'm trying to divide between profiles), but I'm having a problem with turning on the eSIM (spanish operator).

It's added fine with no problems, but when turning it on, it doesn't activate. I've checked that both eSIM support and DSDS (as stated in the guide) is active, tried to deleting and adding it again... Zero errors appear but doesn't turn on.

Auditor gives the green check, zero issues on installing GOS

Anyone with similar problems? Is operator-dependent (i.e. some work fine, some don't...)?

taxonomy

3ch0 I ended up having to call my provider and they set it up on their end. Good luck!

3ch0

taxonomy what did they needed to do? Is there somewhere to see any logs related to this so I can relayed to them? Because I'm guessing they may not know why it is hapenning since it worked for me just fine on stock OS (guessing they won't know what is even GrapheneOS)

taxonomy

3ch0 I didn't mention anything about Graphene. I just said my eSim setup through their app didn't work. They asked for my device's IMEI then they figured it all out on their end.

3ch0

taxonomy I see, it's not the same then I think. But did it happen the same too (added with zero errors, but when turning it on the popup with 'Turning on SIM' appears, then disappears with zero errors but it just doesn't turn on).

In this case, setup was through QR code (I'll try directly from app although I don't think it will change), and it worked as intended in stock OS, but not in GOS. From your comment I thought maybe the servers detected GOS and for some it was blocked, so they needed to authorise in some way.

I'll keep trying other things, even GOS reinstall, just in case before going and get a physical SIM (thus losing the physical SIM frlm work and need to use another phone for that)

3ch0

3ch0 Update: setup through app didn't work either (same behaviour: added ok, but not turning on). Also no luck with adding Google Play services, giving permissions to it...
Tomorrow I'll call carrier support (in case anyone wonders or even there is here any spaniard, carrier is O2) to see if there is any luck, although I'll also keep watching this thread.

3ch0

3ch0 Update 2: seems like I've managed to get it working: installed stock OS, added eSIM with zero issues and working, NOT ADDING PIN for the eSIM, and reinstall of GOS (I let it finishing system updatecompletely before doing anything else). Also, as stated in the Usage guide, eSIM support is disabled by default, but works fine. Added the second physical SIM and works too.

Don't know if it is the same problem as @Bismark had here or this GitHub issue, but at least I have it working now

robin2046

Can I build my own GrapheneOS image for Pixel10? I did not see Pixel10 series devices listed on the supported target list of build page https://grapheneos.org/build#build-targets

nandohyphen1

robin2046 the 10 series is there.

https://grapheneos.org/faq#supported-devices

Pixel 10 Pro Fold (rango)
Pixel 10 Pro XL (mustang)
Pixel 10 Pro (blazer)
Pixel 10 (frankel)
Pixel 9a (tegu)
Pixel 9 Pro Fold (comet)
Pixel 9 Pro XL (komodo)
Pixel 9 Pro (caiman)
Pixel 9 (tokay)
Pixel 8a (akita)
Pixel 8 Pro (husky)
Pixel 8 (shiba)
Pixel Fold (felix)
Pixel Tablet (tangorpro)
Pixel 7a (lynx)
Pixel 7 Pro (cheetah)
Pixel 7 (panther)
Pixel 6a (bluejay)
Pixel 6 Pro (raven)
Pixel 6 (oriole)

robin2046

nandohyphen1
Thanks for your reply. My understanding is that the list you have provided is the supported devices which can run official GrapheneOS images.

But I want to build my own Pixel 10 images. I used to do it by building it from AOSP source code and Google released vendor drivers/binaries. However since Google stopped to release those binaries, I found GrapheneOS.

On the build page https://grapheneos.org/build I can see the step to get the correct binaries for the build is:
adevtool generate-all -d PIXEL_CODENAME
But pixel 10 series is not listed in the supported build-targets currently.

de0u

robin2046 Give it a shot! I suspect it will work.

nandohyphen1

robin2046 oh, I see now. Even though its not listed there, try it for sure. If it works, report back maybe and then possibly someone can add it as a supported device for custom GOS builds

wizoatk

robin2046 But pixel 10 series is not listed in the supported build-targets currently.

I presume it's just an oversight.

Just to be 99% sure, I gave it a try. A full clean build built and signed a set of images for me.
Probably works. I don't have a Pixel 10.

-rw-r--r-- 1 debian debian 2054729359 Jan 20 19:25 frankel-factory-2026012000.zip
-rw-r--r-- 1 debian debian 1902934040 Jan 20 19:25 frankel-img-2026012000.zip
-rw-r--r-- 1 debian debian 1901500136 Jan 20 19:29 frankel-install-2026012000.zip
-rw-r--r-- 1 debian debian 1494193113 Jan 20 19:25 frankel-ota_update-2026012000.zip
-rw------- 1 debian debian 3800847034 Jan 20 19:24 frankel-target_files.zip

Stayjuice

When will the pixel 10 get an official release (non beta)

wizoatk

Stayjuice

Already happened. I think January 16 (plus or minus a day).

https://grapheneos.org/releases#frankel

userofgos

Stayjuice https://xcancel.com/GrapheneOS/status/2013367840191963375#m

Pixel 10 support is no longer considered experimental since after our 2026011000 release which fixed the USB issues impacting 10th gen Pixels:

« Previous Page Next Page »