• Announcements
  • Experimental 9th generation Pixel support is available

Experimental releases of GrapheneOS for the Pixel 9, Pixel 9 Pro and Pixel 9 Pro XL can already be installed with the web installer on our staging site:

https://staging.grapheneos.org/install/web

Can also use the CLI install guide with the releases listed on the staging site releases page.

Our USB-C port control feature with both hardware-level and software-level enforcement hasn't been ported to them yet. They temporarily have our old USB peripherals toggle not depending on changes to device-specific USB HAL and USB-C kernel driver. We aim to get this done soon.

These are production builds signed with the official keys with our standard update system. They'll get updated to future releases without needing to reinstall the OS.

For now, please report issues to our testing chat room rather than our issue tracker: https://grapheneos.org/contact#community-chat.

    I am running 2024082301 on my Pixel 9 Pro XL right now and it is AWESOME. Fast and smooth like butter. In order to truly make the paradigm shift to a private & secure OS, I traded in an iPhone 15 Pro Max to run GrapheneOS on this phone. No regrets & not looking back.

    Again my compliments to the entire GrapheneOS project team, thank you!

    I read that 3GB of RAM were allocated purely for AI on the Pixel 9 Pro and XL, leaving 13GB of RAM for user apps. Is this a software restriction on Stock OS that has been removed on GrapheneOS or is it a hardware restriction?

      Working great for the most part. I noticed media volume control is inoperable. It only adjusts the volume when using the "call volume slider". Otherwise everything is max volume.

      When tinkering with sound settings, it seems when the call slider is adjusted (only in the fullscreen volume settings, not in the quickslider), the media that is currently playing redirects to the earpiece speaker and will respond to the volume sliders position. However, when finished manipulating the slider it reverts to media speakers at full volume.

        DeletedUser88 I read that 3GB of RAM were allocated purely for AI on the Pixel 9 Pro and XL, leaving 13GB of RAM for user apps.

        Discussion of this claim might be more productive if a citation were provided (such as a link).

          DeletedUser88 https://www.androidauthority.com/tested-pixel-9-pro-ai-ram-3472624/

          Thanks!

          Memory is locked when a process with appropriate privileges invokes the mlock or mlock2 system call. So when a Pixel 9 Pro has the AICore app with 3 GB of RAM locked, that means that the app was launched with sufficient privileges, then it allocated memory, then it locked the memory.

          If AICore isn't on a Pixel 9 Pro running GrapheneOS, then it didn't allocate memory and lock it, so the memory shouldn't be allocated (let alone locked). Though I don't have a Pixel 9 of any flavor, I'm pretty confident that without the app the phenomena described in the article won't be happening.

            GrapheneOS Pleased to say I have moved from my P8P to my P9P XL with GOS installed, and is now my daily driver :] First release had no volume control and was set very loud, which was fixed with v.2 today.

            Best way to test IMHO is to use it :] I'll report any other bugs found. Outstanding effort as always from GOS Team!!

            Awesome! Is it possible to use the fancy AI photo features with the Google Camera on GrapheneOS? Or is that feature exclusive to the stock OS?

            • yore replied to this.

              yore
              And for flawlessly use of Google Camera it also needs Google Photos, I guess?
              Because to view a photo you have made, Google Camera app needs Google Photos, otherwise it will crash directly after tapping its “photo preview” (idk if that term is correct, hope you know what I mean).

              This was my experience while using Google Camera on my Pixel 7 Pro.
              In the meantime I use the GOS Camera app.

                Eagle_Owl

                Yeah you need Google Photos and give it network permission the first time, so it enables the feature flags for the Pixel-exclusive features.

                Then all of them will work flawlessly.

                  Hi - I'm unable to mount MTP under linux (arch). I posted here: https://discuss.grapheneos.org/d/15233-anyone-with-mtp-issues-on-pixel-9

                  I've since tried:

                  1. jmtpfs
                  2. MTPfs

                  And aft which is what I typically use.

                  I also tried setting 'USB-C' port to "On" which is supposed to disable all protections.

                  Lemme know what else I can try; my backups from pixel 7 were done with same usbC cable, I also tried the one the pixel9 shipped with. I have rebooted a few times, Transfer File mode is on & the device shows up on the OS.