Android 16 QPR1’s source code is nowhere to be found, but Google swears it’s coming

Last week, Google rolled out the Android 16 QPR1 update, bringing the company’s long-awaited Material 3 Expressive design overhaul and other exciting features to Pixel users. If you want to try new Android features but don’t own a Pixel device, your best option is usually to install a custom ROM based on the open-source version of the operating system. Google typically publishes the source code for new Android versions within 1-2 days of release, allowing independent developers to quickly start porting the new changes to their custom ROMs. That hasn’t happened this time, though, leaving many developers to wonder if Google’s history of timely open source releases is over.

AOSP, short for the Android Open Source Project, is an operating system Google releases under the permissive Apache 2.0 License, which allows anyone to use, modify, and distribute their own AOSP-based operating systems without paying fees or releasing their modified source code. This licensing structure is what allowed Android to become so popular, but it’s also why the OS looks so different across devices. The software experience only feels familiar across most smartphones, tablets, watches, and TVs running Android because companies must follow certain guidelines to get access to Google Mobile Services (GMS) — Google’s suite of proprietary apps that includes the Play Store.

Even if your company doesn’t license GMS, you can still build your own operating system from AOSP. The source code is freely available under the Apache 2.0 license, and Google regularly publishes new code to AOSP shortly after releasing a new Android version. Within hours of rolling out a new quarterly or major release to its Pixel devices, Google typically begins uploading the corresponding source code to AOSP. This process usually takes 24-48 hours due to the codebase’s size and complexity.

It’s been a week since Google released Android 16 QPR1, and there are no signs that the company has even begun to upload its source code. Normally, a minor delay wouldn’t be a cause for concern; perhaps the team responsible for AOSP releases is understaffed, or maybe there’s another complication. However, given recent changes to AOSP, developers are understandably concerned this delay is intentional. They’re worried about the impact these delays could have on their projects, as users have grown accustomed to fast turnarounds following a new Android release.

We reached out to Google a few days ago for comment on whether and when it plans to release the source code for Android 16 QPR1. In a statement to Android Authority, Google confirmed it will release the source code “in the coming weeks.” The company didn’t explain the reason for the delay or offer a more specific timeline, but its statement reassures developers that the code is coming — just later than usual.

Although AOSP is open source, nearly all of its development happens privately, with Google contributing the bulk of the code. Google used to develop some parts of Android in public, but it fully privatized development earlier this year to simplify its workflow. Aware that this would spark concern, Google told Android Authority that it remained committed to publishing Android’s source code.

This commitment was tested when Google released Android 16 back in June. While the company did publish the operating system’s source code, it dealt a huge blow to the Pixel custom ROM community by omitting code for Pixel-specific hardware features. This omission, while not affecting the core OS, fueled speculation that Google was planning to discontinue AOSP. In response to the outcry, Google’s VP and GM of Android Platform, Seang Chau, posted on X, stating that “AOSP is NOT going away.”

Though some skepticism remained, that statement from Google’s VP quelled most doubts at the time. However, the delayed release of security patch backports, coupled with the lack of source code for Android 16 QPR1, has reignited concerns about the company’s commitment to AOSP. If these delays become the new norm, the custom ROM community will have to adjust its release schedules accordingly. We asked Google whether to expect delays for future releases or if this is a one-time issue, and we’ll update this article when we hear back.