GrapheneOS version 2026030500 released:
-
GrapheneOS version 2026030500 released:
GrapheneOS releases
Official releases of GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.
GrapheneOS (grapheneos.org)
See the linked release notes for a summary of the improvements over the previous release.
Forum discussion thread:
-
R relay@relay.publicsquare.global shared this topic
-
GrapheneOS version 2026030500 released:
GrapheneOS releases
Official releases of GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.
GrapheneOS (grapheneos.org)
See the linked release notes for a summary of the improvements over the previous release.
Forum discussion thread:
@GrapheneOS Awesome!
I know because of the recent AOSP release schedule changes it's unlikely, but will we see an Android 16 QPR3 release for GrapheneOS?
-
@GrapheneOS Awesome!
I know because of the recent AOSP release schedule changes it's unlikely, but will we see an Android 16 QPR3 release for GrapheneOS?
@tedstechtips Only if Google decides to release it for use beyond the stock Pixel OS. Otherwise, Android 17 will be the next release used by GrapheneOS and then Android 17 QPR2. Only the yearly and QPR2 releases are currently being made available for other OEMs to use and for AOSP. We strongly disagree with it and will continue pushing back against it. It makes properly supporting Pixels harder but won't impact our partnership with Motorola where we'll have official device support code provided.
-
@tedstechtips Only if Google decides to release it for use beyond the stock Pixel OS. Otherwise, Android 17 will be the next release used by GrapheneOS and then Android 17 QPR2. Only the yearly and QPR2 releases are currently being made available for other OEMs to use and for AOSP. We strongly disagree with it and will continue pushing back against it. It makes properly supporting Pixels harder but won't impact our partnership with Motorola where we'll have official device support code provided.
@GrapheneOS Thanks for the clarification!
Would the partnership with Motorola allow you to use the A16 QPR3 source code and release that way?
-
@tedstechtips Only if Google decides to release it for use beyond the stock Pixel OS. Otherwise, Android 17 will be the next release used by GrapheneOS and then Android 17 QPR2. Only the yearly and QPR2 releases are currently being made available for other OEMs to use and for AOSP. We strongly disagree with it and will continue pushing back against it. It makes properly supporting Pixels harder but won't impact our partnership with Motorola where we'll have official device support code provided.
@tedstechtips Motorola reached out to us after our complaints about Android 16 removing official Pixel support from AOSP which we reimplemented ourselves for Android 16 in June followed by greatly improving it to what we have now where we no longer use any device trees for Pixels but rather generate everything we need with our adevtool and other projects. adevtool was made as a collaboration between ProtonAOSP and GrapheneOS to replace an earlier project we forked due to poor AOSP Pixel support.
-
@tedstechtips Motorola reached out to us after our complaints about Android 16 removing official Pixel support from AOSP which we reimplemented ourselves for Android 16 in June followed by greatly improving it to what we have now where we no longer use any device trees for Pixels but rather generate everything we need with our adevtool and other projects. adevtool was made as a collaboration between ProtonAOSP and GrapheneOS to replace an earlier project we forked due to poor AOSP Pixel support.
@tedstechtips They never provided everything we actually needed to do production support for Pixels for AOSP without a bunch of our own work. However, it got a lot worse with Android 16 and we don't expect it to get better. We're going to continue supporting Pixels but we've given up on being able to harden the drivers, etc. in the way we want and will focus on the Motorola partnership for hardware, firmware and driver hardening. Pixels can remain fully supported but it takes a lot more time.
-
@GrapheneOS Thanks for the clarification!
Would the partnership with Motorola allow you to use the A16 QPR3 source code and release that way?
@tedstechtips Google only intends for OEMs to use the yearly releases and QPR2 releases. They very recently started making security backports to QPR2 in addition to the yearly releases in anticipation of OEMs beginning to use it. They don't need the backports for Pixels since they do that separately for the monthly and QPR1/QPR3 releases. Monthly releases are nearly non-existent now though. They moved most security patches to quarterly security releases alongside the quarterly updates too.
-
@tedstechtips Google only intends for OEMs to use the yearly releases and QPR2 releases. They very recently started making security backports to QPR2 in addition to the yearly releases in anticipation of OEMs beginning to use it. They don't need the backports for Pixels since they do that separately for the monthly and QPR1/QPR3 releases. Monthly releases are nearly non-existent now though. They moved most security patches to quarterly security releases alongside the quarterly updates too.
@tedstechtips QPR1 and QPR3 are officially Pixel exclusive now, as are the monthly updates. Motorola has access to the sources and we can have access to them through them which we can use for porting early. However, we'd need permission to release QPR1 and QPR3 releases as open source which may be hard to get. It's entirely possible that we can get it permitted especially since there are antitrust issues in play and an Android OEM is now involved in working with us where that's very relevant.
-
@tedstechtips QPR1 and QPR3 are officially Pixel exclusive now, as are the monthly updates. Motorola has access to the sources and we can have access to them through them which we can use for porting early. However, we'd need permission to release QPR1 and QPR3 releases as open source which may be hard to get. It's entirely possible that we can get it permitted especially since there are antitrust issues in play and an Android OEM is now involved in working with us where that's very relevant.
@GrapheneOS Thank you for the information, this is all great to know!
-
R relay@relay.mycrowd.ca shared this topic
