Android 17 is the first since 3.x to add new APIs without releasing to the AOSP
Google's latest Android 17 update restricts new APIs and critical security patches to Pixel devices for months, sparking outrage among the open-source community and custom ROM developers like GrapheneOS. This move intensifies fears of Android becoming a fully closed ecosystem, mirroring Apple, and directly challenges the project's ability to maintain secure, de-Googled devices. HN is buzzing with discussions about Google's anti-competitive behavior, the future of Android openness, and the perennial search for viable mobile alternatives.
The Lowdown
GrapheneOS is sounding the alarm over Google's decision to make Android 17 QPR1 updates, including new APIs and crucial security patches, exclusive to Pixel devices for several months before they become available to AOSP and other OEMs. This development marks a significant shift, as it's the first time since Android 3.x that new APIs aren't immediately accessible to the broader Android ecosystem.
- Android 17 QPR1 introduces new APIs and security patches that GrapheneOS and other non-Pixel OEMs cannot release until Android 17 QPR2, slated for December 2026.
- Google is also reportedly withholding standard Android platform security patches from OEMs, forcing GrapheneOS to either reverse engineer fixes or endure months of delay.
- This situation makes supporting Pixel devices, which GrapheneOS has historically relied on for their robust security features, significantly more challenging and diverts resources from core privacy and security development.
- GrapheneOS is now exploring partnerships with other OEMs, citing Motorola's commitment to 7 years of support and better firmware access as a promising alternative.
- Further complicating matters, Google is also criticized for weeks-long delays in fulfilling GPL source code requests.
Overall, GrapheneOS's report highlights escalating concerns about Google's tightening control over the Android ecosystem, its potential impact on open-source projects, and what many perceive as anti-competitive practices favoring its own hardware.
The Gossip
Google's Grip: The Android Lock-Down
Many commenters express frustration and anger over Google's actions, viewing them as a deliberate strategy to lock down Android, erode its open-source nature, and prioritize Pixel devices. This fuels a narrative that Google regrets Android ever being open source, pushing it towards a more closed, Apple-like ecosystem. Accusations of anti-competitive practices are common.
Open Source Obfuscation: The Decline of AOSP
Discussion centers on how Android has deviated from its initial open-source ethos, with many lamenting the increasing challenges for alternative Android distributions like GrapheneOS. Concerns are raised about the future of AOSP, the decreasing utility of a 'de-Googled' Android, and the potential for Google to kill off AOSP entirely, turning it into a mere code base rather than a truly open platform.
GrapheneOS's Gambit: Privacy Pioneer or Pixel Pain?
Users praise GrapheneOS for its dedication to privacy and security, with some calling it a liberating experience. However, Google's actions are making GrapheneOS's mission harder. Commenters discuss the project's pivot to supporting Motorola devices, the challenges of maintaining support for Pixels, and whether GrapheneOS's user base is substantial enough to truly impact Google's strategy. There's a mix of admiration for GrapheneOS's resilience and concern for its future viability.
Alternative Avenues: Beyond the Duopoly
The discussion broadens to the need for viable alternatives to the Google/Apple duopoly. Calls for 'Linux phones' (like Librem 5 or PostmarketOS), HarmonyOS, Plasma Mobile, or even new browser foundations like Firefox and Ladybird are made. However, skepticism abounds regarding their mainstream appeal, the significant resources required to develop and maintain them, and the practical challenges faced by average users in adopting them.
Corporate Conduct and Competitive Conundrums
Commenters delve into Google's motives, often attributing its actions to pure profit-seeking and a desire to gain a competitive edge for Pixel devices. The discussion touches upon the Friedman doctrine (companies act solely for shareholder benefit) and the potential for regulatory bodies, like the EU with its DMA Act, to force Google to open up certain APIs. There's a strong sentiment that Google's actions are deliberate and harmful to competition and consumer choice.