GrapheneOS releases
grapheneos.org
Official releases of GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.

Pixel 4a (5G) and Pixel 5 are end-of-life and shouldn’t be used anymore due to lack of security patches for firmware and drivers. We provide extended support for harm reduction.

Tags:

  • 2024082000-redfin (Pixel 4a (5G), Pixel 5)
  • 2024082000 (Pixel 5a, Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, Pixel 8, Pixel 8 Pro, Pixel 8a, emulator, generic, other targets)

Changes since the 2024080600 release:

  • Settings: enable Safety Center and port all of the relevant GrapheneOS settings to it both to provide the more modern user interface and to prepare for the release of Android 15
  • hide Safety Center camera extensions fallback toggle when it’s not relevant (not used on Pixels)
  • Package Installer: fix upstream bug causing null pointer exception in rare edge cases including a rare race condition
  • require Owner user credential to check whether a duress PIN/password is enabled as hardening against potential UI bugs such as the upstream predictive back gesture issue we patched in the Settings app
  • apply upstream change for 6th generation Pixels making snapuserd available in recovery to avoid a problem in a rare edge case where a factory reset occurs before finishing booting a new update
  • apply minor upstream fixes for Settings which were temporarily only shipped for certain Pixels
  • add fastboot to otatools.zip for optimized factory images generation
  • flash-all: raise minimum fastboot version to 35.0.1
  • kernel (5.10): update to latest GKI LTS branch revision including update to 5.10.223
  • kernel (5.15): update to latest GKI LTS branch revision including update to 5.15.164
  • kernel (6.1): update to latest GKI LTS branch revision including update to 6.1.95
  • kernel (6.6): update to latest GKI LTS branch revision including update to 6.6.45
  • remove duplicate Android.bp from unpacked otatools.zip to avoid breaking subsequent builds when it’s unpacked in the source tree
  • add Android 15 Beta build configuration for early development/testing of our Android 15 port via an ap2f release configuration enabling all of the available Android 15 feature flags
  • port GrapheneOS changes to new code for Android 15 used by our Android 15 Beta build configuration
  • Vanadium: update to version 127.0.6533.104.0
  • Vanadium: update to version 127.0.6533.104.1
  • Vanadium: update to version 127.0.6533.104.2
  • Vanadium: update to version 127.0.6533.104.3
  • GmsCompatConfig: update to version 128
  • GmsCompatConfig: update to version 129
  • GmsCompatConfig: update to version 130
    • piracysails@lemm.eeEnglish
      1·
      2 months ago

      Could you provide some use cases for this?

      If you want privacy when you offer you phone, try pinning applications.

      There are also third party applications that can achieve this.

      • LordBelphegor@lemm.eeEnglish
        0·
        2 months ago

        imagine i give my phone to someone else, and i just dont want them to access 1 or 2 apps, so like i lock just those few apps.

        currently I use a third party app to lock apps, but its user experience is pretty bad and not as convenient as on when I used ColorOS.

        Yes I can make a separate user account for just those few apps, but like in some apps I like to share stuff to another app and that’s not possible when the user account is different.

        I Also miss hiding apps on ColorOS. where when I lend my phone to others, they won’t know that I have certain apps installed.

        • piracysails@lemm.eeEnglish
          2·
          2 months ago

          I see, fair points. I think but I am not sure, hiding applications, may be coming to aosp in Android 15.