Is Android still open source? What changed in 2025-26

What “open source” means for Android

Two things share the Android name, and only one of them is open source. AOSP is the base operating system. Google’s apps and services, including the Play Store, Gmail, Maps and Google Play services, are proprietary and licensed separately.

Google says Apache 2.0 is the preferred license for AOSP and covers most Android software. The Linux kernel underneath stays under GPLv2. Google prefers Apache 2.0 partly because licenses like the LGPL would force phone makers to ship source code and allow user modification. That freedom is one reason brands can ship heavily customized versions.

To ship Google’s apps, a phone maker has to meet Google’s compatibility requirements. Google has said this since 2011. Andy Rubin, then head of Android, wrote that device makers were free to modify Android, but anyone wanting to market a device as Android-compatible or include Google apps had to meet those rules.

Part of Android	Open source?	Who can use it
AOSP (core OS, framework, many system apps)	Yes, mostly Apache 2.0	Anyone
Linux kernel	Yes, GPLv2	Anyone
Google Play Store, Play services, Gmail, Maps	No	Licensed phone makers
Pixel drivers and device files	No longer published in full	Google and partners

2011: the first time Google held code back

Honeycomb, Android 3.0 for tablets, is the version Google held back. Honeycomb tablets were on sale from early 2011, but Google chose not to release the source code (TechCrunch).

On April 6, 2011, Rubin wrote that the delay was temporary. The team was still bringing Honeycomb’s features to phones and would publish the code once that work was done. He said it did not represent a change in strategy.

That turned out to be true. On November 14, 2011, Google released the source for Android 4.0.1 Ice Cream Sandwich, and the Honeycomb code was included in its history (TechCrunch). TechCrunch reported that Honeycomb had been thrown together quickly, and Google discouraged anyone from building on its code.

Gadget Daily News argued at the time that the delay was aimed at Amazon, which had just opened its own Android app store and, the post guessed, might launch its own tablet. Amazon’s tablets did end up on Fire OS with Amazon’s own app store instead of Google Play (TechCrunch). Honeycomb’s code was held back for most of 2011. The 2025–26 changes are standing policy.

What changed in 2025 and 2026

Google still releases Android’s code, but later and in bigger chunks. Here’s what changed.

Development went private. In March 2025 Google confirmed to Android Authority that all Android development would move into Google’s internal branches. Google also said it remained committed to publishing Android’s source code. Outside developers now see the code when Google publishes a release, not while it’s being written.

Source drops are less frequent. Google’s AOSP site now says that from 2026 it will publish source code to AOSP in Q2 and Q4 only. Android 17’s source arrived in June 2026.

Some pieces arrive late or not at all. The LineageOS team wrote in October 2025 that Google hadn’t pushed the Android 16 QPR1 source to AOSP when it reached Pixels, so only contracted partners had it. It also said Google now offers Pixel kernels only as history-stripped tarballs on request, with no device trees, and that monthly security bulletins now publish only high-risk fixes, with the rest bundled quarterly.

Issue	2011 (Honeycomb)	2025–2026
Is the code published?	Held back for most of 2011, then released	Yes, twice a year (Q2 and Q4)
Can outsiders watch development?	Yes, for other versions	No, development is internal
Pixel device code	Not relevant	Device trees no longer published
Monthly security patches in AOSP	Not applicable	High-risk fixes only, rest quarterly
Google’s stated reason	Code not ready for phones	Trunk-stable model, platform stability

Developer verification and sideloading

This is the change most likely to affect ordinary users. Google is starting to require that apps installed on certified Android devices come from developers who’ve verified their identity and registered their apps, including apps distributed outside Google Play.

The rollout, per Google’s Android Developers Blog as of October 2026:

Date	What happens
March 2026	Verification launches for developers
August 2026	Advanced flow for power users and free limited distribution accounts launch
September 30, 2026	Required for installs from participating stores in Brazil, Indonesia, Singapore and Thailand
2027	Google plans to expand the requirement globally

The first phase covers seven stores: Google Play, Samsung Galaxy Store, Xiaomi GetApps, HONOR App Market, OPPO App Market, vivo V-Appstore and Transsion’s Palm Store. Google says unregistered apps can still be installed with Android Debug Bridge (adb) or the advanced flow.

The advanced flow is how a power user installs an app from an unverified developer. You turn on developer mode, confirm nobody is coaching you, restart and re-authenticate, then wait one day before confirming with your fingerprint, face or PIN. After that you can allow unverified installs for 7 days or indefinitely, and you’ll still see a warning on each install. Google says the waiting period is there to break the pressure scammers put on victims.

Hobbyists and students get a separate route. Limited distribution accounts let them share an app with up to 20 devices without a government ID or a fee.

US users aren’t covered yet. Nothing changes in the US until the global rollout Google has scheduled for 2027, and Google hasn’t given an exact date. As Google describes it, the requirement targets certified devices. We found no Google statement saying it applies to custom systems built from AOSP.

What it means for forks: Fire OS, GrapheneOS and LineageOS

Forks still exist because the code is still open. But less frequent source drops and missing Pixel files make the work slower, and each fork has gone its own way.

Amazon Fire OS has powered Amazon’s tablets with Amazon’s own app store instead of Google Play. That’s changing. On October 8, 2026, Amazon announced Alexa tablets that run Android with the full Google Play Store, on sale in the US from October 14. TechCrunch lists starting prices of $229.99 for the Alexa Tablet 8, $329.99 for the Tablet 11 and $499.99 for the Tablet 12 Pro. Amazon told TechCrunch these are a new product line with a new OS, not a rebrand of Fire tablets.

GrapheneOS is a hardened, security-focused system built on AOSP by the nonprofit GrapheneOS Foundation. It has supported Google’s Pixel phones, and its website keeps the current device list. On March 2, 2026, Motorola announced a long-term partnership with the foundation to work on future devices with GrapheneOS compatibility. Motorola didn’t name a phone or a date.

LineageOS is a long-running community Android build that keeps older phones updated. LineageOS 23.0, based on Android 16, came out in October 2025. Its team warned that Pixels are “no longer guaranteed ‘day one’ devices,” and that many older devices on Linux 4.4 and 4.9 kernels can’t move to Android 16 yet.

Option	Built on	Google Play?	Who it suits
Fire OS (older Fire tablets)	Amazon’s Fire OS	No, Amazon Appstore	Budget Amazon-content users
Amazon Alexa tablets (October 2026)	Android	Yes	Amazon users who want Play apps
GrapheneOS	AOSP	Not included	Privacy-focused buyers with a supported phone
LineageOS	AOSP	Not included	Owners of older supported phones

Open code never guaranteed any single brand a future, either. HTC built the first Android phone and still lost its place, as what happened to HTC explains. If you own an older Fire tablet, our guide on which Amazon tablet to buy covers the new lineup, and what happened to Amazon’s Free App of the Day covers the Appstore side.

Does any of this matter if you just buy a phone?

For most buyers, very little changes in 2026. Phones from Samsung, Google and Motorola still run Android with Google’s apps, and Google says over 99% of apps on Google Play were registered automatically.

It matters in three cases. If you sideload apps from outside the big stores, expect extra steps from 2027 in the US. If you want a de-Googled phone, GrapheneOS on a supported phone is the main route, and Motorola hasn’t shipped a supported model yet. And if you keep phones for many years, the 2025 changes make it harder for community builds to support them after the maker stops.

What to do next

Check where your apps come from. If you rely on apps from outside Google Play or the big stores, find out whether the developers have registered for verification before the 2027 US rollout.
If you sideload often, learn the advanced flow now. It needs a one-day wait, so don’t leave it until you need an app urgently.
For a privacy-focused phone, check the supported device list on grapheneos.org before you buy.
To keep an older phone going, look it up on the LineageOS wiki and check which version it supports.
If you want a cheap tablet with Google Play, compare Amazon’s new Alexa tablets with Fire tablets, which still lack Play.

Is Android still open source?