Does AOSP stop releasing pixels' device repositories?

542 views
Skip to first unread message

CLF BBN

unread,
Jun 11, 2025, 7:57:47 PM6/11/25
to Android Building
In the current AOSP release of Android 16, I find that no pixel device repositories are updated to the android 16 tag. Does it mean AOSP stops releasing them? Or will it be available at a later date?

Bill Yi

unread,
Jun 11, 2025, 8:08:51 PM6/11/25
to Android Building
We remain committed to AOSP updates. You continue to have the option to build Cuttlefish and GSI targets from the sources for experimentation.

bill

Dae Euhwa

unread,
Mar 19, 2026, 3:55:41 PM (2 days ago) Mar 19
to Android Building
Hi Bill,
I’d like to get a clear technical clarification regarding Android 16 and Pixel device sources:
Device trees (DTS/DTB) are not optional. They are required to build a working kernel for a device, and without them, the shipped Pixel kernel cannot be reproduced.
GKI does not replace the full device kernel. While GKI provides a generic kernel core, it does not include Pixel-specific hardware initialization. As such, it is not equivalent to the shipped product.
Current AOSP sources appear to lack Pixel-specific device trees. If these sources remain private, it is technically impossible to reproduce the shipped kernel.
Could you clarify how GPL compliance is addressed under these circumstances? From a practical standpoint, the shipped product cannot be reconstructed from public sources, and any reliance on GKI alone does not resolve this gap.
I’d appreciate a non-standard, detailed response rather than the usual statement about “building GSI or Cuttlefish targets,” since those do not address Pixel-specific reproducibility.
Thank you, I appreciate you taking the time to respond.

PS:
Any response that does not directly address the technical and factual points outlined will be documented for public reference, as it reflects both on the reproducibility and compliance of the shipped product and on the responsibility of Google staff to provide accurate, truthful guidance.

Bill Yi

unread,
Mar 19, 2026, 4:39:03 PM (2 days ago) Mar 19
to Android Building

To get the source code for third-party components distributed by Google in binary form within an Android product, where the open source license grants you the right to receive the source, go to http://android.googlesource.com. You can find instructions for downloading the source at Download the Android source.

If the source code for the component isn't available on http://android.googlesource.com, you can receive a copy of the source code by submitting the following form: https://source.android.com/opensourcerequest#

bill
Reply all
Reply to author
Forward
0 new messages