Android 17 is the first since 3.x to add new APIs without releasing to the AOSP

Original Article ↗ Hacker News Discussion ↗

Google’s decision to ship new Android 17 APIs first in Pixel‑only quarterly releases, without simultaneously updating the Android Open Source Project (AOSP), is seen as a turning point in how open Android really is. Commenters argue this gives Pixels an unfair competitive edge, complicates life for projects like GrapheneOS and other OEMs, and fits a broader pattern of Google tightening control over Android and Chromium. Many raise security, antitrust, and long‑term ecosystem concerns, while others look to Linux‑based mobile systems and alternative browsers as the only credible path away from Google’s growing dominance.

Android 17, QPRs, and Pixel‑Exclusive APIs

  • Android 17 introduces new standard APIs only in QPR1, which is now a Pixel‑only quarterly release.
  • QPR1 and QPR3 stopped being published to AOSP starting with Android 16; OEMs and AOSP forks only get them later via QPR2.
  • Some see this as the first time since Android 3.x that app‑visible APIs are effectively non‑AOSP for months.

Impact on AOSP Forks and GrapheneOS

  • Custom ROMs and security‑focused forks complain about: delayed source drops, embargoed patches, attestation changes, and now API timing.
  • Claim: Pixels get months‑early access to features and some security fixes, giving them an unfair advantage over other Android vendors.
  • GrapheneOS is said to need heavy reverse‑engineering to keep supporting Pixels; some expect Motorola devices to become easier targets.

Security, Privacy, and User Control

  • Many argue Android’s original “open” pitch has been steadily replaced by Apple‑like lock‑down, with Google prioritizing data collection and control.
  • Others note OEMs themselves like tighter control (locked bootloaders, anti‑theft justifications) and can’t or won’t maintain their own OS.
  • There’s debate over GrapheneOS’s strict hardware requirements: some praise “maximal” security; others want broader, “good‑enough” support.

Alternative OS Efforts

  • Mentioned options: GrapheneOS, LineageOS, postmarketOS, Ubuntu Touch, SailfishOS, Plasma Mobile, Librem 5, HarmonyOS, and Linux‑based phones from smaller vendors.
  • Skepticism: poor hardware support, weak app ecosystems, stability issues, and hard installs keep these niche.
  • Some think long‑term hope lies in a well‑funded third platform (possibly Linux‑based, Steam/Valve‑backed, or similar).

Licensing, Governance, and Antitrust

  • Discussion of GPL vs permissive licenses: belief that copyleft (as with Linux) better constrains corporate “embrace, extend, extinguish” behavior.
  • Concern that without strong enforcement, even GPL can be eroded (e.g., awkward kernel source distribution).
  • Several see Google’s moves as classic monopoly behavior; others doubt regulators will intervene, noting past cases and Pixel’s small market share.

Broader Sentiment

  • Emotions range from anger and calls to abandon Android/Google, to pragmatic resignation (“most users don’t care and nothing will change”).
  • Some Android power users say they’ll move to iOS or Linux phones; others double down on Firefox and non‑Google ecosystems as a parallel fight.