Android 17 Ships New APIs Without AOSP Source — a First Since Honeycomb

GrapheneOS flags a notable break in Android’s open-source posture: Android 17 introduces new APIs whose corresponding source has not been published to the Android Open Source Project. According to the post, this is the first time Google has done so since the Android 3.x (Honeycomb) era over a decade ago, when the tablet-focused release was famously withheld from AOSP before later versions restored open publication.

The significance is less about any single API and more about the direction it signals. Custom ROMs and privacy-focused distributions like GrapheneOS, LineageOS, and CalyxOS depend on timely, complete AOSP source drops to rebuild the platform and stay compatible with app expectations. When APIs exist in shipping devices but their implementations are absent from AOSP, downstream projects are left to reverse-engineer or stub functionality, widening the gap between Google’s proprietary Android and its nominally open base.

This is a single social-media observation rather than a confirmed policy statement from Google, so the scope and permanence remain unclear. Still, it lands amid ongoing concern that Google is steadily shifting functionality out of AOSP and into closed Play Services and system components — a trend that erodes the practical openness the platform has long claimed.