Google's Two-Year Source Code Slowdown Threatens LineageOS While EU Lawyers Eye Mobile OS Lockout
Google is planning to cut Android source code releases to twice yearly while simultaneously rolling out developer verification and app attestation measures.
The raw takes show a deep split. Many point to corporate greed as the main driver for these moves. Custom ROM advocates, citing DacoTaco and mellejwz, argue the reduction severely harms projects like LineageOS because OEMs retain preferential access via existing Google deals. Meanwhile, some technical users, like Arghblarg, are actively finding ways to bypass these new restrictions by stripping enforcement code from APKs. Others, like other8026, suggest GrapheneOS can sidestep verification because the enforcement remains within privileged Google apps, not AOSP.
The consensus screams anti-competition. The weight of opinion suggests Google is tightening the screws, forcing OS developers into a harder position, which some believe only legal action, particularly from the EU, can break. The fault lines exist between reliance on established OEM deals versus the technical ability of open-source projects to rebuild key components like Pixel code, as noted by LedgeDrop.
Key Points
Reducing source code releases to twice per year harms custom ROMs.
DacoTaco and mellejwz explicitly state this move disadvantages custom ROMs compared to OEMs with established deals.
Google's new verification tools are circumventable by dedicated builders.
Arghblarg reported GrapheneOS users are already stripping enforcement code to maintain sideloading ability.
OEM deals grant preferential access Google can't deny.
mellejwz noted that Samsung and others hold deals giving them early access to source material.
Regulatory action, especially in the EU, may force platform choice.
nicgentile anticipates legal challenges leading to a more diverse 'mobile OS arms race'.
Google's technical support for reference designs is narrowing.
LedgeDrop observed Google is now shipping only an 'emulator' when it previously provided full 'reference designs' for Pixel builds.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.