GrapheneOS
@grapheneos.org
Open source privacy and security focused mobile OS with Android app compatibility.
https://grapheneos.org/
https://grapheneos.org/
Android 16 was released in June 2025 and GrapheneOS fully migrated it in June 2025. We already have the Android 16 UI changes.
Android 16 QPR1 is a newer release currently exclusive to the stock Pixel OS which has not been released to the Android Open Source Project so we can't migrate to it yet.
Android 16 QPR1 is a newer release currently exclusive to the stock Pixel OS which has not been released to the Android Open Source Project so we can't migrate to it yet.
November 9, 2025 at 11:23 AM
Android 16 was released in June 2025 and GrapheneOS fully migrated it in June 2025. We already have the Android 16 UI changes.
Android 16 QPR1 is a newer release currently exclusive to the stock Pixel OS which has not been released to the Android Open Source Project so we can't migrate to it yet.
Android 16 QPR1 is a newer release currently exclusive to the stock Pixel OS which has not been released to the Android Open Source Project so we can't migrate to it yet.
November 8, 2025 at 3:56 AM
Yes, at least for the Pixel 10, Pixel 10 Pro and Pixel 10 Pro XL. Pixel 10 Pro Fold will take longer due to the lack of an Android 16 QPR1 release for AOSP. Android made a huge mess with delayed 16 QPR1 release, changes to security patches and dropping Pixel support from AOSP which burns our time.
November 7, 2025 at 7:04 PM
Yes, at least for the Pixel 10, Pixel 10 Pro and Pixel 10 Pro XL. Pixel 10 Pro Fold will take longer due to the lack of an Android 16 QPR1 release for AOSP. Android made a huge mess with delayed 16 QPR1 release, changes to security patches and dropping Pixel support from AOSP which burns our time.
> at least some other degoogled phone
See discuss.grapheneos.org/d/24134-devi... for a representative example of how that usually goes. iPhones provide much better privacy from apps and services than nearly all niche products advertised as private. /e/ even sends sensitive data to OpenAI itself.
See discuss.grapheneos.org/d/24134-devi... for a representative example of how that usually goes. iPhones provide much better privacy from apps and services than nearly all niche products advertised as private. /e/ even sends sensitive data to OpenAI itself.
November 7, 2025 at 8:32 AM
> at least some other degoogled phone
See discuss.grapheneos.org/d/24134-devi... for a representative example of how that usually goes. iPhones provide much better privacy from apps and services than nearly all niche products advertised as private. /e/ even sends sensitive data to OpenAI itself.
See discuss.grapheneos.org/d/24134-devi... for a representative example of how that usually goes. iPhones provide much better privacy from apps and services than nearly all niche products advertised as private. /e/ even sends sensitive data to OpenAI itself.
November 6, 2025 at 5:49 AM
It's likely an upstream Android bug related to update_engine which was triggered by the power loss where it got into a weird state it wasn't happy with. Don't really understand why the screen would be going black. Is the device new or old? Which device model is it?
November 4, 2025 at 2:37 PM
It's likely an upstream Android bug related to update_engine which was triggered by the power loss where it got into a weird state it wasn't happy with. Don't really understand why the screen would be going black. Is the device new or old? Which device model is it?
You can clear data for System Updater but it seems something is wrong with the update_engine / system_server state for updates, likely due to an upstream bug. Maybe clearing data for System Updater and rebooting will resolve it after giving update_engine some time to settle down before updating.
November 4, 2025 at 5:50 AM
You can clear data for System Updater but it seems something is wrong with the update_engine / system_server state for updates, likely due to an upstream bug. Maybe clearing data for System Updater and rebooting will resolve it after giving update_engine some time to settle down before updating.
Try turning it off completely and then back on as a starting point.
November 4, 2025 at 5:35 AM
Try turning it off completely and then back on as a starting point.
Have you charged it above a very low battery level again? You can pause booting on the verified boot screen if needed.
November 4, 2025 at 5:28 AM
Have you charged it above a very low battery level again? You can pause booting on the verified boot screen if needed.
The new security patch system being used by Android is confusing for users and bad for the security of anyone not using GrapheneOS with our security preview releases. We could have set the patch level string to 2025-11-01 in early September but in this case we didn't do that.
November 3, 2025 at 11:24 PM
The new security patch system being used by Android is confusing for users and bad for the security of anyone not using GrapheneOS with our security preview releases. We could have set the patch level string to 2025-11-01 in early September but in this case we didn't do that.
Our security preview releases shipped all available December 2025 security patches in September 2025 and have continued adding the remaining patches. It should be frozen soon, but most of the patches have remained the same since September. Some were deferred to future bulletins.
November 3, 2025 at 11:19 PM
Our security preview releases shipped all available December 2025 security patches in September 2025 and have continued adding the remaining patches. It should be frozen soon, but most of the patches have remained the same since September. Some were deferred to future bulletins.
Due to having early access to the patches which we can use for our security preview releases, we've been able to determine that a subset were pushed to AOSP and other projects prior to the official embargo ending which means we'll be including those in our regular releases soon.
November 3, 2025 at 11:14 PM
Due to having early access to the patches which we can use for our security preview releases, we've been able to determine that a subset were pushed to AOSP and other projects prior to the official embargo ending which means we'll be including those in our regular releases soon.
Our security preview releases currently have the December 2025 and January 2026 patches.
December 2025 has a huge set of patches due to being a quarterly patch level. January 2026 will likely be empty.
We should have quarterly March 2026 patches to ship within a couple weeks.
December 2025 has a huge set of patches due to being a quarterly patch level. January 2026 will likely be empty.
We should have quarterly March 2026 patches to ship within a couple weeks.
November 3, 2025 at 11:12 PM
Our security preview releases currently have the December 2025 and January 2026 patches.
December 2025 has a huge set of patches due to being a quarterly patch level. January 2026 will likely be empty.
We should have quarterly March 2026 patches to ship within a couple weeks.
December 2025 has a huge set of patches due to being a quarterly patch level. January 2026 will likely be empty.
We should have quarterly March 2026 patches to ship within a couple weeks.
It's because these two patches were included in the full September 2025 bulletin patches we shipped but were made optional until November 2025.
Later in September, we started our security preview releases able to provide Android Security Bulletin patches around 2-3 months early.
Later in September, we started our security preview releases able to provide Android Security Bulletin patches around 2-3 months early.
November 3, 2025 at 11:10 PM
It's because these two patches were included in the full September 2025 bulletin patches we shipped but were made optional until November 2025.
Later in September, we started our security preview releases able to provide Android Security Bulletin patches around 2-3 months early.
Later in September, we started our security preview releases able to provide Android Security Bulletin patches around 2-3 months early.
See the privacy and security focused comparison at eylenburg.github.io/android_comp... as a good starting point. The site also has comparisons of other kinds of software such as messaging apps.
Comparison of Android-based Operating Systems
Comparison of Android-based Operating Systems
eylenburg.github.io
November 3, 2025 at 7:52 PM
See the privacy and security focused comparison at eylenburg.github.io/android_comp... as a good starting point. The site also has comparisons of other kinds of software such as messaging apps.
See grapheneos.org/faq#recommen... for the devices we recommend for it. There's also a section on the full list of supported devices further up.
You can likely do it yourself without help. It's easiest from macOS or another Android device due to avoiding some steps on Windows and desktop Linux.
You can likely do it yourself without help. It's easiest from macOS or another Android device due to avoiding some steps on Windows and desktop Linux.
November 3, 2025 at 3:10 PM
See grapheneos.org/faq#recommen... for the devices we recommend for it. There's also a section on the full list of supported devices further up.
You can likely do it yourself without help. It's easiest from macOS or another Android device due to avoiding some steps on Windows and desktop Linux.
You can likely do it yourself without help. It's easiest from macOS or another Android device due to avoiding some steps on Windows and desktop Linux.
It's very easy to install with grapheneos.org/install/web. If needed, you can get real-time help with it in our main General chat room at any time of day. Alternatively, we have a discussion forum for longer form discussions also usable for it. You need officially supported devices to use it.
November 3, 2025 at 3:09 PM
It's very easy to install with grapheneos.org/install/web. If needed, you can get real-time help with it in our main General chat room at any time of day. Alternatively, we have a discussion forum for longer form discussions also usable for it. You need officially supported devices to use it.
GrapheneOS is nearly entirely developed by developers paid by the GrapheneOS Foundation. Our funding entirely comes from donations (grapheneos.org/donate). The article saying volunteers develop it has been fixed. It'd be nice if they stopped saying "custom ROM" which is a misleading/inaccurate term.
October 31, 2025 at 4:45 PM
GrapheneOS is nearly entirely developed by developers paid by the GrapheneOS Foundation. Our funding entirely comes from donations (grapheneos.org/donate). The article saying volunteers develop it has been fixed. It'd be nice if they stopped saying "custom ROM" which is a misleading/inaccurate term.
If they have the password from the user they can unlock it, enable developer options including ADB, authorize ADB access, install apps, grant permissions, etc. ADB shell provides a massive amount of access. Despite that, they appear to have lost the ability to exploit GrapheneOS through that (FFS).
October 31, 2025 at 4:40 PM
If they have the password from the user they can unlock it, enable developer options including ADB, authorize ADB access, install apps, grant permissions, etc. ADB shell provides a massive amount of access. Despite that, they appear to have lost the ability to exploit GrapheneOS through that (FFS).
If they reboot it into fastboot mode, they can try to exploit the fastboot mode firmware. Since April 2024, Pixels zero memory before enabling USB in fastboot mode based on a proposal by us in January 2024 to block that for AFU. GrapheneOS zeroes memory as it's freed and wipes it at boot time too.
October 31, 2025 at 4:37 PM
If they reboot it into fastboot mode, they can try to exploit the fastboot mode firmware. Since April 2024, Pixels zero memory before enabling USB in fastboot mode based on a proposal by us in January 2024 to block that for AFU. GrapheneOS zeroes memory as it's freed and wipes it at boot time too.