GrapheneOS hits Android 17, but only if you bought the right Pixel
The Android 17 port is already running on seven Pixel models. The recurring complaint in the thread isn't about the OS at all: it's that you still have to buy Google hardware to escape Google.
Tested so far on the Pixel 6a, 7, 7a, 8, 10a, 10 and 10 Pro Fold, with official releases coming soon and longer security-patch support than Android 16 gets.
Notably absent from the list: the Pixel 9 and 9a, which several owners in the thread are still waiting on.
The bigger flip: a privacy OS that only installs on phones from the company you're trying to leave, and Pixels aren't even sold worldwide.
A degoogled OS that ships only on Google phones
GrapheneOS announced that its build has been ported to Android 17 and that official releases are coming soon. The forum post was loading-flaky at fetch time, but the announcement's hard fact was quoted verbatim in the thread.

Seven Pixels in, two conspicuously out
The device list, pulled straight from the post by a user running it:
"We've already tested the Android 17 port of GrapheneOS on the Pixel 6a, 7, 7a, 8, 10a, 10 and 10 Pro Fold." — a 9a owner reading the announcement
The Pixel 6a, 7, 7a, 8, 10a, 10 and 10 Pro Fold are covered; the Pixel 9 and 9a are missing, a gap multiple owners flagged in the thread. A core selling point is longevity: Android 17 will receive security patches for longer than Android 16 will, which matters most for users stretching old hardware. The day-to-day verdict from a year-plus user was warm with caveats: a Pixel 7a switch he doesn't regret, missing only swipe-to-move-cursor on the space bar and clean reaction emojis in the texting app.
The gatekeeping nobody on the project chose
The loudest reversal had nothing to do with code quality. To run the most private Android, you must first buy a phone from the company whose tracking you're fleeing:
"So I still need to buy a Google phone to get it? No thank you." — a commenter rejecting the hardware requirement
And Pixels aren't sold everywhere, which one developer framed as accidental rationing of security:
"Pixel phones are not sold worldwide so it feels like they're gatekeeping security." — an independent mobile and server developer
There was also a sharp technical asterisk: the project still leans on extracted proprietary binary blobs, which is exactly why a new kernel version is "such a chore/achievement." The motive to switch keeps shifting, though. The headline reason used to be degoogling; in this thread, multiple converts cited something plainer, like the iPhone user of nearly 20 years now eyeing a Pixel. The pitch that landed wasn't privacy at all: "It behave like a computer." The real bottleneck for that pitch isn't the Android 17 port. It's the checkout page.
Get breakdowns like this every day
The top Hacker News stories, unpacked — by email, Telegram, or RSS.
'Stop using JWTs' meets the people who run JWTs at scale
A gist tells you to drop JWTs for plain session cookies. Then the AWS and identity-platform crowd showed up to point out the standard quietly authenticates half their infrastructure.