Google open-sources Android 16 QPR1, two months late

Google finally pushed the Android 16 QPR1 source to its public code site—two months late—and the comments lit up. For the non-nerds: this is the base code phone makers and hobby devs need to build Android. Without it, custom Android projects were stuck waiting, even though the lower-level “engine parts” (kernel and firmware) landed in September. Cue eye-rolls, theories, and a dash of meme salt.

Confused readers led the thread with “Can someone explain?” while one helpful soul dropped a “link or it didn’t happen” moment with a direct peek at the code. The real brawl? Whether Google was just dragging its feet or being hamstrung by new European rules. One commenter claimed it’s not laziness at all, but legal commitments triggered by release timing—translation: “expect more delays.”

Meanwhile, a bombshell take set the vibe: the custom ROM scene (think community-made Androids like LineageOS) is “mostly dead,” with only a few big names still thriving and smaller teams “kanging” (copying) old features instead of offering real support. That sparked nostalgia, debate, and some gallows humor: devs joked Google arrived “fashionably late” to its own code party, while others sighed that their weekend build plans just got resurrected. Drama served, code delivered, patience tested.