Android 17 Goes Closed

GrapheneOS reports that Android 17 QPR1 is the first Android release since version 3.x (Honeycomb) to add new APIs without releasing the corresponding source code to the Android Open Source Project. The post hit 733 points on Hacker News with 359 comments, and the community response is not kind to Google.

The history matters here. Android 3.x Honeycomb was the tablet-only release that Google kept closed in 2011 because the platform was not ready for larger screens. The source eventually arrived with Android 4.0 Ice Cream Sandwich. At the time, Google framed the closure as temporary and exceptional. Now it looks like a precedent.

What changed with Android 17

Android 17 QPR1 introduces new APIs that are simply not in AOSP. This is not a delay. Google has moved from "we release source late" to "we release some source never." The GrapheneOS team, which builds a privacy-focused Android fork and depends on AOSP source for security patches and feature porting, is directly affected.

The community comments tell the story. Google is delaying source patches upstream, imposing embargos, and creating attestation issues for custom Android distributions. The practical effect is that forks like GrapheneOS, CalyxOS, and LineageOS face growing gaps between what Google ships on Pixel devices and what the open-source community can build from AOSP.

Google regrets open source

The Hacker News consensus is blunt: Google simply regrets Android being open source. Android achieved its market dominance partly because it was open. Manufacturers adopted it, carriers pushed it, developers built for it, and contributors outside Google improved it. Now that the market share is locked in, the open-source commitment is being quietly walked back.

This is the same playbook Google tried with Chromium. The browser is technically open source, but Google controls the direction, the feature decisions, and the timing. "Just because it is open source does not mean they do not control it," as one commenter put it.

Why this matters beyond Android

The pattern is familiar. A company builds dominance on an open-source foundation, then gradually closes the gaps once competitors are locked in. The open-source license remains, but the practical openness erodes. Source drops become incomplete. New APIs ship in proprietary binaries. The fork becomes unsustainable not because of licensing but because of information asymmetry.

For the Android custom ROM community, this means an increasingly hard choice: ship outdated code, reverse-engineer Google's proprietary additions, or give up. For users who chose Android specifically because it was open, the value proposition is weakening.

The lesson for the broader open-source community is that a CLA (Contributor License Agreement) and a corporate-controlled source tree are not the same thing as a community project. Android was never a community project in the way Linux is. It was always Google's. The source was a strategic decision, not a principle. When the strategy changes, the source changes with it.