Bottom line: GrapheneOS on Android 17 is real, building, and landing tomorrow — but the stable ride is still weeks out. Plan your testing accordingly, and remember that the first Android 17 boot is a one-way door.
GrapheneOS has completed its port to Android 17 and will publish initial official builds tomorrow, June 17, 2026. The project confirmed today that code is being pushed to public repositories after successful testing on every currently supported Pixel device — from the Pixel 6a through the Pixel 10 Pro Fold.
Most users on the stable channel will not see the update immediately; the release will follow the standard alpha, beta, and stable progression, and downgrading to Android 16 will require a full data wipe.
Port complete across the full supported lineup
The GrapheneOS team announced today that the Android 17 port is finished for all supported devices, not just the subset they have already built and tested internally.
Their validation matrix covers the Pixel 6a, 7, 7a, 8, 10a, 10, and 10 Pro Fold — a list that reflects the project’s current device support window GrapheneOS has been ported to Android 17 and official releases are coming soon. The initial public release tomorrow will be available for every device in that window once per-device testing wraps up.
Today the project is also shipping a final Android 16 QPR2-based stable release, effectively closing out the Android 16 cycle before the Android 17 wave begins GrapheneOS has been ported to Android 17 and official releases are coming soon. Developers and enthusiasts who build from source can start compiling the new code later today once the push completes.
Release channels and what “soon” actually means
GrapheneOS reiterated that Android 17 will move through the standard alpha → beta → stable cycle. The vast majority of users sit on the stable channel, so the announcement tomorrow does not mean an immediate OTA for most people GrapheneOS has been ported to Android 17 and official releases are coming soon. Rollout progress for each device is tracked in the project’s public release tables — for example, the Pixel 9a status page shows the exact channel state per build.
| Channel | Typical audience | Risk profile |
|---|---|---|
| Alpha | Testers, developers | High — may have regressions |
| Beta | Early adopters | Moderate — fewer showstoppers |
| Stable | General users | Low — production-ready |
Users who want Android 17 immediately can switch the System Updater to the alpha channel, but the project warns that alpha testing can have negative side effects and that serious issues could take days to resolve GrapheneOS has been ported to Android 17 and official releases are coming soon. Once a device installs an Android 17 build, rolling back to Android 16 is not possible without wiping all data.
Device support implications for Pixel 6 series
A recurring question in the community concerns the Pixel 6 and 6 Pro. Google’s own Android 17 blog post did not specify device eligibility, leading to speculation that the Pixel 6 series might be excluded from the upstream release GrapheneOS has been ported to Android 17 and official releases are coming soon.
GrapheneOS has not issued a separate statement on the Pixel 6/6 Pro in this announcement, but the project’s supported-device list has historically tracked Google’s extended support commitments. Users on those devices should watch the release tables for definitive status.
Practical takeaways for each reader
- Developers / builders: Source drops later today; you can compile and test immediately. Expect the usual AOSP upstream deltas plus GrapheneOS hardening patches (hardened malloc, vanilla kernel hardening, sandbox improvements).
- Sysadmins / fleet managers: Do not flip managed devices to alpha. Wait for the stable entry in the release table for each device model before scheduling OTAs. Document the no-rollback rule in your runbooks.
- Privacy-focused power users: If you run a secondary device, the alpha channel is a safe way to validate app compatibility early. Primary devices should stay on stable until the channel marker flips.
- Product managers / app teams: Treat tomorrow as “Android 17 exists for GrapheneOS.” Begin compatibility testing against the alpha images; the stable API surface will not change, but GrapheneOS-specific permissions (Network, Sensors, Local network access) may expose new toggles.
What comes next
The project will open public testing tomorrow and iterate through alpha and beta milestones. The release tables are the single source of truth for per-device channel status — bookmark the page for your hardware. For teams maintaining custom GrapheneOS builds, the Android 17 rebase is now the baseline; factor the QPR2 final release into your merge window today.
FAQ: GrapheneOS Android 17 port
- 1.When will stable Android 17 builds arrive for my Pixel?The project follows a multi-week alpha → beta → stable cycle. Stable timing varies by device; check the release tables for your model.
- 2.Can I downgrade from Android 17 to Android 16 without losing data?No. The project explicitly states that rolling back requires a full data wipe GrapheneOS has been ported to Android 17 and official releases are coming soon.
- 3.Will the Pixel 6 and 6 Pro get GrapheneOS Android 17?Google has not confirmed Android 17 support for Pixel 6 series. GrapheneOS historically tracks Google's extended support window; watch the release tables for final word.
- 4.What hardening features carry over to Android 17?Hardened malloc, vanilla kernel hardening, and sandbox improvements remain part of the GrapheneOS delta on top of AOSP.
