Android 17 QPR1 adds new APIs without an AOSP release, a first since Android 3.x

Android 17 QPR1 is the first Android release since Android Honeycomb (3.x) to add new APIs for app developers without a corresponding release to the Android Open Source Project, the GrapheneOS project said in a Mastodon post on 16 September 2026.

According to the post, the new APIs are currently exclusive to Pixel OS and are not available to other Android OEMs. They are expected to reach AOSP and other manufacturers with Android 17 QPR2, which is due in December 2026.

Why this happened

Since Android 16, QPR1 and QPR3 releases are no longer handed to AOSP and ship only on Pixel devices. GrapheneOS describes Android 17 QPR1 as the first case where new public APIs appeared inside such a Pixel-only release. The APIs themselves are standard Android platform interfaces rather than a Pixel exclusive feature — they simply arrived early, as part of the Pixel build.

Security patches are delayed too

The project pointed out that the September 2026 Pixel Update Bulletin includes additional patches to standard Android platform components that non-Pixel devices also rely on. Those changes were published neither in the September 2026 Android Security Bulletin nor in the preview patches, so other vendors will only receive them in December with QPR2.

GrapheneOS said it can reverse engineer the code and ship those patches before December. It also reported that Google is once again slow to comply with GPL source requests: the project asked for the CD1A.260905.001.A1 sources on 1 September and was given access only on 16 September.

What it means for custom ROMs

GrapheneOS had already ported its code to Android 17 QPR1 before the 15 September release, but it does not yet have permission to publish that work. In the meantime it is backporting Pixel firmware, kernel drivers, userspace drivers and HALs from Android 17 QPR1 to Android 17.

Supporting Pixels has become significantly harder for the project, and it expects the Motorola partnership to be easier because official firmware and driver code will be provided. In the thread, GrapheneOS also argued that Pixels now get months of early access to new features and some security patches ahead of Google's OEM partners.