AOSP project is coming to an end

Original Article ↗ Hacker News Discussion ↗

What actually changed with Android 16 and AOSP

  • Android 16 source has been pushed to AOSP, but Google did not release device‑specific source for current Pixel phones (device trees, hardware repos, etc.), unlike previous years.
  • Only platform/framework code is public so far; this means AOSP 16 cannot be easily built or booted on recent Pixels using only official source.
  • It’s unclear in the thread whether this is a temporary delay or a permanent policy shift; some see it as just a workflow change, others as the start of closing Pixel.

Impact on custom ROMs, security projects, and users

  • Custom ROM projects (GrapheneOS, CalyxOS, LineageOS, etc.) are heavily affected because Pixel was the de facto reference device with good security and good AOSP support.
  • Without official Pixel device trees, ROMs must do more low‑level bringup work, similar to what they already do for Snapdragon/MediaTek devices.
  • Commenters worry this could be the “final nail” for custom ROMs on modern, high‑end hardware and a serious disruption for security researchers and organizations relying on the Pixel ecosystem.
  • Some users reconsider Pixel purchases, citing both this change and Pixel hardware reliability concerns, while others highlight that GrapheneOS is “still going strong” for now.

Licensing, legal obligations, and openness

  • Most of AOSP is under Apache 2.0, allowing Google to keep future code closed; kernel‑related parts are GPL, with debate over whether device trees are copyrightable “code” or just data.
  • There’s discussion of GPL/LGPL anti‑tivoization obligations and one German case, but it’s noted that case settled and doesn’t set firm precedent.
  • Several commenters call this a “RedHatification” or continuation of the long trend of moving features from AOSP into proprietary Google Mobile Services.

Alternative devices and ROM ecosystems

  • Alternatives mentioned: Fairphone (with Qualcomm BSP access), some newer Motorola and OnePlus devices, and many older devices via LineageOS, though often with weaker hardware or security.
  • Concerns arise over whether Fairphone and others, who depend on Google/Qualcomm partner channels, will be affected similarly in future.

Google’s stated position vs speculation

  • Google representatives publicly state AOSP is not being discontinued and emphasize Cuttlefish and GSI as the reference targets.
  • Multiple commenters read “between the lines” that while AOSP continues, Pixel as the public reference hardware target is being locked down, which they see as a major but overstated change relative to the thread’s title.