Pixel 10 - Experimental support for GrapheneOS is now available!

Joe_Koba

SirMixAlot I also have 11GB of Android sytem files and 19GB of temp system files.

I have now transferred all my apps and data from my old P4a and everything seems to work smoothly. Only two small hickups that are probably more related to buggy apps than to GrapheneOS:

The "Flip DND" app (to turn on do not disturb when the phone is put screen downward on a table) doesn't seem to work anymore. Which is sad, because GrapheneOS doesn't privide this function which is native to stock android.
The Private Lock app (that locks the screen when sudden movement is detected, e.g. when someone snatches the phone from your hands) locks the screen to the primary passphrase and not, as I hoped, to the secondary fingerprint+pin. Again, stock Android provides this as "theft security" but GrapheneOS doesn't, so without this app there's no solution.

userofgos

Joe_Koba Again, stock Android provides this as "theft security" but GrapheneOS doesn't, so without this app there's no solution.

There is an open issue for this: https://github.com/GrapheneOS/os-issue-tracker/issues/207

(as with all issues please don't add comments like "I want this too" which can be better expressed with emoji's and will prevent unnecessary pings to the devs.)

Joe_Koba

*Correction: the "Flip DND" app works perfectly, I was simply stupid as I had already toggled do not disturb manually, so of course the app couldn't do anything 🤦

spl4tt

chenxiaolong Oh my, thanks a lot man!

tmp

Installed via CLI (Alpine Linux) w/o issue. Was not able to attest via Auditor w/ P8 as auditor. Will continue to set it up as see how things go, perhaps drop by a local ATT shop to get the eSim working tomorrow.

gflixos

chenxiaolong Hearing this, I installed GOS yesterday. Looking forward to setting it to 480Hz PWM again when your PR got merged.

Even though it is an experimental version, it works very well! My Pixel is running way cooler now and everything works fine. Just experiencing some random crashes and reboots from time to time, which I can live with until a stable release becomes available. Thank you GOS Team!!

Echoz

A few weeks ago my P7Pro's screen became so unreliable (a long standing hardware issue but mostly intermittent) that I went and impulse bought a P10Pro (in hindsight I should have gotten a P9Pro). I've been mashing F5 on this thread ever since, and dreading my existence with the stock OS that seems to be littered with footguns to make you opt into some kind of data collection at every turn.

When I saw the staging release I dropped everything and installed without a second thought. Everything worked flawlessly, from the web installer to the OS itself. It once again feels like I have my old phone but newer. I can't thank the GOS team enough for delivering so quickly in spite of all the roadblocks. Really good work! I hope whatever you have cooking with another OEM turns out great so we no longer need to be at the mercy of Google's antics, because GOS is the only reason I'm still willing to have a smartphone.

Conjure6589

I got a couple of "shared_modem_platform has crashed" errors. Should I report this somewhere or is it already a known issue?

Joe_Koba

Conjure6589 https://github.com/GrapheneOS/os-issue-tracker/issues/6599 ;-)

Conjure6589

Joe_Koba looks like I'm tardy to the party lol glad its not just me

stargazer7

Have had GOS on my Pixel 6a for almost 2 years, love it.

But now i bought a Pixel 10 Pro XL, tried to install the test version only to realise tech savvy me was at the normal GOS install, not staging.

The bootloader was unlocked, but now when i try to install the actual test version from staging the device doesnt show up. I only get the red text saying "Error: Failed to execute 'requestDevice' on 'USB': No device selected." under both the unlock bootloader button and the obtaining factory images button.

I am using my Pixel 6a and vanadium to install it on the 10ProXL, whenever i plug in the USB-C cable to the 10proXL in fastboot mode, the device shows up on the 6a (when you need to choose which device to unlock bootloader for) for half a second then it disappears and it says no device was found.

Any ideas?

Best regards

akc3n

stargazer7 "Error: Failed to execute 'requestDevice' on 'USB': No device selected."

This indicates that the browser cannot detect your Google Pixel device in the correct mode and typically happens because:

the device isn't properly connected to the bootloader/fastboot mode (need to use either the stock cable or a high quality one)
hasn't been authorized to USB communication (chrome://flags search for WebUSB to find out or follow next steps below)
another program/instance is claiming the control of the USB interface (restart and make sure you have 1 installation tab running and no other installer duplicate tabs).

stargazer7 I am using my Pixel 6a and vanadium to install it on the 10ProXL, whenever i plug in the USB-C cable to the 10proXL in fastboot mode, the device shows up on the 6a (when you need to choose which device to unlock bootloader for) for half a second then it disappears and it says no device was found.

Make sure you haven’t disabled WebUSB and double check the site settings, perhaps you may have tapped rejecting it accidentally earlier. Press the site settings icon in the navigation bar to check over the permissions, then try plugging it in again while your GrapheneOS phone is unlocked.
i.e., chrome://settings/content/siteDetails?site=https%3A%2F%2Fgrapheneos.org#USB%20devices

Also, check your device USB-C port system settings in Settings > Security.

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.

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

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!

« Previous Page Next Page »