Bottom line: GrapheneOS has finished its Android 17 port for every supported Pixel; alpha builds land in public repositories today and public alpha testing starts tomorrow, but stable-channel users should wait for their device to show green in the release tables.
Port Complete, Alpha Begins Tomorrow
The GrapheneOS team announced that the hardened Android distribution has been fully ported to Android 17 and the code is being pushed to public repositories, according to the project’s official forum post. A final Android 16 QPR2 release is building today, and the first Android 17 alpha release targets tomorrow. This timeline places GrapheneOS among the fastest third-party distributions to align with a major Android version drop.
Which Devices Are Supported?
Testing has already been performed on the Pixel 6a, 7, 7a, 8, 10a, 10, and 10 Pro Fold, the project says. The team emphasizes that the port covers all currently supported devices, not just the models explicitly listed for pre-release validation. Developers and advanced users can begin building from source later today once the repository push completes.
This device list is notable for including the Pixel 10 series and 10 Pro Fold, confirming GrapheneOS support for Google’s latest hardware generation at launch. The Pixel 6a and 7 series remain supported, extending the practical lifespan of devices that Google itself may deprioritize. For a full per-device status, see the GrapheneOS release tables.
Rollout Cadence: Alpha → Beta → Stable
The project will start public testing for official releases tomorrow, entering a standard alpha/beta/stable progression. Most users on the default stable channel will not receive Android 17 when the announcement goes out — this is expected behavior, not a failure.
| Channel | Typical Audience | Downgrade Path |
|---|---|---|
| Alpha | Developers, testers | Full data wipe required |
| Beta | Enthusiasts, early adopters | Full data wipe required |
| Stable | General users | Full data wipe required |
Users who want early access can switch the System Updater to the alpha channel, but the project warns of potential instability and the inability to downgrade to Android 16 without a full data wipe. Historical cadence suggests several weeks of alpha/beta testing per device before stable promotion.
Pixel 6 / 6 Pro: Status Uncertain
Community discussion has surfaced questions about the Pixel 6 and 6 Pro. Google’s Android 17 blog post did not specify device eligibility, leading to speculation that the 2021 flagships may be excluded from the official Pixel OS update. GrapheneOS has not issued a definitive statement on whether it will maintain support for these devices independently. One forum participant claimed the Pixel 6 received an Android 17 update, but this remains unverified by the project. For sysadmins managing fleets and developers targeting a device matrix, treat Pixel 6/6 Pro support as uncertain until GrapheneOS explicitly confirms otherwise. See also our Pixel device support lifecycle tracker.
Practical Guidance by Role
Developers can begin validating apps against the Android 17 SDK on GrapheneOS today by building from source. The project’s rapid port suggests minimal API-surface breakage, but hardware-backed keystore, attestation, and memory tagging (MTE) behaviors should be regression-tested on each device tier.
Sysadmins should:
– Monitor per-device release tables before approving fleet upgrades
– Keep devices on stable channel until Android 17 reaches stable for that model
– Prepare wipe-and-reprovision workflows for any alpha/beta test devices
Product managers evaluating GrapheneOS for BYOD or dedicated-device programs should note that the alpha/beta cycle may extend several weeks. The data-wipe requirement for downgrade makes rollback planning essential.
Data/AI engineers running on-device inference (e.g., via ML Kit or custom TFLite models) should verify GPU delegate and NNAPI compatibility on Android 17, as driver updates often accompany major version bumps. Our Android security hardening guide covers MTE and attestation in depth.
Why the Speed Matters
GrapheneOS’s same-day port capability reflects a mature, automated rebase pipeline — a significant engineering achievement for a project that maintains extensive hardening patches (hardened_malloc, vanilla kernel hardening, sandboxed Google Play compatibility layer) atop AOSP. The speed also signals that Google’s Generic Kernel Image (GKI) and Project Mainline modularization are reducing the friction that historically delayed third-party Android ports by months.
For the broader ecosystem, GrapheneOS remains the reference implementation for a de-Googled, exploit-mitigated Android. Its Android 17 baseline will influence downstream projects (DivestOS, CalyxOS, /e/OS) that cherry-pick GrapheneOS hardening commits. The project’s transparency about the alpha/beta/stable cadence — and its public release tables — sets a standard for release observability that many commercial vendors still lack. Compare approaches in our hardened Android distros roundup.
Immediate Next Steps
- If you run GrapheneOS: Stay on stable until your device shows green in the release table.
- If you build or test: The source is arriving now; begin regression testing MTE, attestation, and keystore paths.
- If you manage Pixel 6/6 Pro fleets: Treat Android 16 QPR2 as the last guaranteed release until the project speaks.
FAQ: GrapheneOS Android 17 Port
When does alpha testing start?
Public alpha testing begins tomorrow, June 18, 2026, per the project forum announcement.
Can I downgrade from alpha to Android 16 without wiping data?
No. The project explicitly states a full data wipe is required to downgrade from any alpha, beta, or stable Android 17 build.
Will my Pixel 6 or 6 Pro get Android 17 on GrapheneOS?
Uncertain. Google has not confirmed Android 17 eligibility for the 2021 flagships, and GrapheneOS has not issued a definitive statement. Treat support as unconfirmed.
How long until stable releases?
Historical cadence suggests several weeks of alpha/beta testing per device before stable promotion. Watch the release tables for your specific model.
Where do I find per-device release status?
The official GrapheneOS release tables show green checkmarks when a device reaches stable.
Sources
1. GrapheneOS forum announcement — https://discuss.grapheneos.org/d/36469-grapheneos-has-been-ported-to-android-17-and-official-releases-are-coming-soon
2. GrapheneOS release status pages — https://grapheneos.org/releases
3. Android 17 developer preview documentation — https://developer.android.com/about/versions/17
