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.