Pixel 10 - Experimental support for GrapheneOS is now available!

alonely0

Happened to me as well, disconnecting the cable and connecting it again fixed it instantly; did not even have to grant device permissions again through the browser UI.

stargazer7

akc3n hmm, i tried again but same problem both with stock cable and an alternative.

I'm only running vanadium and only one tab open, I have changed WEBusb from default to enabled in chrome://flags.
USB port in system settings is set to "charging-only when locked".

Maybe I should try to install via the computer.

stargazer7

stargazer7 Installed on my 10PXL via the computer, worked like a charm!

Big thanks the GOS-team!

CappyT

Being completely ignorant to the hardware/firmware side of things: how much Google not releasing some firmware parts source impacts the security of grapheneos on the pixel 10 series? I mean, is the pixel 10 series any less secure that 9 and below?

VAULT

I've just got to say it:

Firstly, I find it challenging to truly express my gratitude for GOS, which I consider to be a world-class secure private OS that's available to the public. Astounding!

Secondly, the GOS Team: To produce what they do, under the current circumstances, and the current pre, pre, pre-Alpha version of Series 10 GOS. Seriously, I've been running it on my DD within hours of its release, and it's been incredibly stable and functional on my P10PXL... other than two shared modem crashes I would not have known it wasn't the official stable release. Amazing work!!

VAULT

starglider

VAULT Seriously. The GOS team's version of "experimental" is more stable than Microsoft's server products.

VAULT

starglider Absolutely. I've been in engineering and IT for 35 years and that's soooo true it's very funny :]

bwells2

If you were to flash the experimental release now, would you have to do the unlocking and flashing process again once the official release comes out, or would you be able to update to the official version through a normal software update in the phones settings?

also, this may be a dumb question, but is the experimental release functional (like can make calls and texts) or should it really only be tested on beater phones that aren't actively in use? Thanks!

spl4tt

bwells2 https://bsky.app/profile/grapheneos.org/post/3m6kvyfnhy22m

You can upgrade to production as normal, no wiping or unlocking needed. I'm using the experimental right now, and it's working quite well for my daily user experience.

bwells2

spl4tt Awesome, thanks!

googolplex

Is it worth it downloading the experimental release now? Or should I wait for a stable release? Never used GrapheneOS before, but I would say I am more tech literate than most people.

hetter

If the X app refuses to login and throws an 'attestation refused' error, is that related to the Auditor attestation failure? Is it due to the experimental build for the 10pro?

vodka

hetter If the X app refuses to login and throws an 'attestation refused' error, is that related to the Auditor attestation failure? Is it due to the experimental build for the 10pro?

X has added server-side attestation recently, new logins will fail on anything but the latest unmodified app installed via google play.

I can login just fine in X when installed via play store, if I do revanced to strip ads and annoyances from the app, it fails. (On a 10 Pro Fold with GOS)

tylerwylie

hetter I had this issue on my 9 too with the latest app, the workaround for me was to enable a Passkey login via my password manager and then I was able to login without any error on both my 9 and 10.

hetter

vodka interesting. I'm using the unmodified app from the play store. I changed my password to no avail - and got the same attestation error on my 6a when I attempted to log back in on that.

I will try the passkey workaround.

Frostily7047

vodka On a 10 Pro Fold with GOS

😱

BF sale $450 off... But still an eye watering $1949 CDN

bwells2

apologies if this has been mentioned somewhere previously, but I just got the experimental release up and running and the only issue I've run into so far is that when I connect my 10 pro XL to my PC with a usb c to c cable, it just starts charging and I see no way to change the connection mode to file transfer. is this just a limitation of the experimental release or is there a setting somewhere? Developer options was disabled once I finished up the install (i read that it could be that).

tilt

bwells2 It require some patient. Keep trying and changing ports. Also disable all usb c protections and from nowhere you while get the notification

starglider

bwells2 I ran into this same exact issue. I think it's a bug. I was able to work around it by enabling developer options and changing the default USB-C behavior to "file transfer." You can then turn dev options back off, restart, and when you connect a data cable, you'll get the notification that file transfer is enabled. You can then switch it to USB Tethering or whatever else you want.

Obviously, this is not ideal from a security perspective, but as long as you keep the GOS option to disable USB-C when locked, I don't think it's a major security issue.

bwells2

tilt Can't seem to get it to work. tried both USB ports (front and rear) and even tried a USB a to c cable on every port, front and back. none of them do anything but charge. Checked my motherboard (AsRock B550 Taichi) BIOS and didnt see anything related to USB C protections under the USB settings.

tilt

bwells2 I was referring to USB C protection that Graphene has, Settings > Security and Privacy > Exploit Protection > USB C > Off. Once you have finished remember to change it back to the one you prefer to still have the protection, but it takes some trial and error mine took me a while to get the notification, I think should be fixed in the next release hopefully

bwells2

tilt Ah, ok. That didn't do anything either, but I'll keep fiddlin' with it. I'm fine to wait for a fix, just wanted to make sure it wasn't something I was doing wrong. Thanks!

hetter

bwells2 I had to restart my machine in order to get it to see the device.

bwells2

hetter yeah, i had to do that anyway to get into the BIOS when i thought tilt was talking about USB settings there. Didn't do anything for me. Guess I'll just wait. I'm sure if its a Graphene issue, it'll be solved in due time. Bluetooth transfers work from PC to phone though.

« Previous Page Next Page »