Android ownership is divided: the source code is open source (AOSP), but the brand and services are controlled by Google.
The question of who exactly owns the rights to the world's most popular mobile operating system often causes confusion among users and even some developers. On the one hand, Android is positioned as an open platform, available for modification and free use. On the other hand, the vast majority of devices on the market are strictly tied to the Google ecosystem. This creates the illusion of a complete monopoly, although the legal reality is much more complex and interesting.
Initially, the system was developed by Android Inc., which was acquired by the search giant in 2005. Since then, it has been Google the main beneficiary and controller of the development of the platform. However, it is important to understand the difference between ownership of a trademark, control over device compatibility, and rights to the software code itself. Many smartphone manufacturers use the so-called “naked” version of the system without Google services, which is legally acceptable within certain limits.
In this article we will analyze in detail the structure of property rights, the role of the OHA alliance, the differences between open source and proprietary add-ons, as well as the impact of antitrust regulations on the distribution of rights. You will find out why Xiaomi or Samsung can use Android, but do not have the right to call their forks full-fledged Android without certification.
History of creation and transfer of ownership
The history of rights to Android began not within the walls of Google, but in a small Californian company Android Inc.founded in 2003 by Andy Rubin, Rich Mainal, Nick Sears and Chris White. Initially, the project was conceived as an operating system for digital cameras, but quickly retrained for smartphones due to the growing market for mobile devices. In 2005, Google acquired the company, and from that moment on, all intellectual rights were transferred to the search giant.
The purchase was a strategic move that allowed Google to enter the mobile software market, which was dominated by Symbian and Windows Mobile. It is important to note that Google did not make the system completely closed, like iOS. Instead, an open core strategy was adopted, allowing it to quickly capture market share by collaborating with multiple hardware vendors. The rights to the code were transferred to the community through the AOSP project, but control of the brand remained with the corporation.
From the moment of purchase to this day, Google is the sole owner of the "Android" trademark and the green robot logo. This means that any commercial use of the system name requires permission from the copyright holder. Even if a manufacturer takes open source code and creates its own shell, it cannot legally call the product "Android Phone" unless it undergoes certification and enters into appropriate licensing agreements with Google.
⚠️ Attention: Using the Android logo or system name in marketing materials without a formal agreement with Google is a violation of trademark rights and may result in legal action.
Even if you develop AOSP-based firmware for personal use, publicly distributing it under the name "Android" without prefixes may violate trademark rules.
The role of the Open Handset Alliance in platform management
To manage the development of the platform and prevent fragmentation, Google initiated the creation in 2007 Open Handset Alliance (OHA). This consortium brings together phone manufacturers, telecom operators, chipset and software developers. Membership in the alliance imposes certain obligations: participants agree not to release devices based on Android forks that are not compatible with Google standards.
In fact, OHA serves as a mechanism for quality control and unity of the ecosystem. Although the code is technically open source, alliance members are bound by legal contracts. If a company that is part of OHA (such as Samsung or LG in the past) decides to release a phone with a heavily modified version of the system without Google services, it risks being excluded from the alliance. This will deprive it of access to new versions of Android and the right to use the brand on future devices.
The management structure within the alliance assumes that the main decisions on the development of the API and core are made by Google, in consultation with partners. However, the platform owner always has the final say. This creates a unique situation where an "open" system is de facto managed by one corporation through a network of partnership agreements.
The difference between AOSP and GMS: two levels of rights
The key to understanding rights on Android lies in dividing the system into two independent parts: the open source project AOSP (Android Open Source Project) and the proprietary package applications GMS (Google Mobile Services). The rights to these components are subject to various licenses and agreements. AOSP is available to everyone under the Apache 2.0 license, which allows free use, modification and distribution of the code, even for commercial purposes.
At the same time, GMS includes Google Play Store, Gmail, YouTube, Google Maps and frameworks for running these applications. The rights to GMS belong exclusively to Google and are distributed only under a proprietary license. Device manufacturers are required to enter into a MADA (Mobile Application Distribution Agreement) to pre-install these applications. Without this agreement, an AOSP-based phone remains “empty” for a Western user.
Below is a table showing the main differences in rights and access to system components:
| Component | License type | Rights owner | Availability |
|---|---|---|---|
| Linux Kernel | GPL v2 | Linux Community | Open Source |
| AOSP (Framework) | Apache 2.0 | Google (shared with community) | Open source |
| GMS (Services) | Proprietary | Google LLC | Licensed only |
| Trademark | Trademark | Google LLC | Protected by law |
It is the presence of GMS that is Google’s main lever of influence. Chinese manufacturers, such as Huawei, faced restrictions specifically at the level of access to GMS, although no one took away the right to use the AOSP code from them. This proves that the real power lies not in the lines of code, but in the ecosystem of services.
Why is the Apache 2.0 license important?
The Apache 2.0 license allows vendors to close their code modifications. Unlike the GPL license, which requires all changes to be made public, Apache gives the freedom to create proprietary shells on top of the open core, which is good for the business of companies like Samsung and Xiaomi.
Trademark and brand restrictions
Many users mistakenly believe that if they download the Android source code, they can call their product "Android TV" or "Android Phone." This is a gross misconception. The name "Android" and the image of the green robot are protected by trademark law. Google strictly regulates who can use this brand and how.
There is a certification app CTS (Compatibility Test Suite). To be eligible to use the Android logo, a device must pass hundreds of compatibility tests. This ensures that apps from the Play Store will work correctly on the device. If a manufacturer skips tests or makes critical changes to the kernel that violate compatibility, Google revokes the right to use the brand.
As a result, there are devices on the market that run Android code, but are not legally Android devices. They are often called "Linux devices" or use their own OS names (like Amazon's Fire OS). Amazon, for example, has created a powerful fork of Android, but does not have the right to call Fire tablets "Android tablets" in marketing, since it does not use Google services and has not passed CTS certification.
⚠️ Attention: An attempt to name custom firmware with the word "Android" in the name of an application on Google Play may lead to the publication being rejected by store moderators due to a violation of trademark rules.
Patent wars and technology licensing
In addition to copyrights to code and trademarks, patents play a huge role. The Android operating system contains thousands of patented technologies related to the interface, networking, power management and multimedia. Some of these patents are owned by Google, some are owned by other OHA members, and some are owned by third parties not directly involved in the mobile market.
Google licenses its patent portfolio to device manufacturers free of charge, but only as part of a collaboration agreement. This serves as a defense against patent trolls: if a company sues one of the Android manufacturers over patents, Google can retaliate by suing for violating its patents. This mutual protection has made the ecosystem attractive to large vendors.
However, there are patents that are not part of Google's portfolio. For example, Oracle waged years of legal battles against Google, claiming that the use of the Java API in Android violated their rights. Although the US Supreme Court ultimately sided with Google, ruling that the API was fair use, this example shows the fragility of the legal construct. Manufacturers have to pay licensing fees to companies like Microsoft for every Android smartphone sold, despite the fact that it is a competitive platform.
☑️ Checking the legality of the firmware
The impact of antitrust regulations on Google's rights
Google's dominant position in the distribution of rights to Android has repeatedly become the subject investigations by antitrust authorities around the world. The European Union, United States and other jurisdictions have accused the company of abuse of power by requiring manufacturers to pre-install Google apps in exchange for access to the Play brand and store.
As a result of these proceedings, Google was forced to change some licensing terms in Europe. Manufacturers can now sell devices without Google apps pre-installed, and users have more search engine choices when first setting up. However, the fundamental rights to the code and brand remained with the corporation. Regulators are trying to balance between market freedom and intellectual property protection.
These changes have led to the emergence of new licensing models. For example, Google has started charging a GMS license fee in some regions for manufacturers who want to pre-install services but don't meet the new "clean" installation requirements. This sets a precedent where rights to use the ecosystem become a paid product rather than a free bonus to an open OS.
⚠️ Attention: Antitrust laws vary from country to country. What a manufacturer is allowed to do in Europe (for example, selling a phone without Chrome) may not be possible in other regions due to local Google requirements or lack of infrastructure.
Antitrust measures do not eliminate Google's property rights, but they limit the ways in which they can be used commercially, forcing the corporation to make the ecosystem more flexible.
FAQ: Frequently asked questions about Android rights
Can I take Android code and create my own operating system?
Yes, you can download the AOSP source code, modify it and build your own operating system. The Apache 2.0 license allows this. However, you won't be able to call it "Android", use the robot logo, or pre-install the Google Play Store without a separate agreement with Google.
Does the Android community or Google own the code?
Legally, Google owns the copyright for code created by Google engineers. However, they voluntarily contributed it to the AOSP project under a free license. The community can propose changes, but moderation and inclusion of them in the main development branch is controlled by Google.
Why can’t Huawei use Google services?
This is not due to the rights to the Android code, but to US sanctions, which prohibited American companies from doing business with Huawei. Google was forced to revoke the license to use GMS (proprietary services). The AOSP code remains available because it is open source, but the Google ecosystem has become inaccessible.
Is Amazon Fire OS a version of Android?
Technically, Fire OS is a fork of Android (based on AOSP). But legally and marketing-wise, this is a separate OS. Amazon does not use the Android brand and does not have Google services, so in terms of rights and ecosystem it is a completely different product.
Can the rights to Android go to another company?
Theoretically, yes, if Google decides to sell the Android division or is acquired by another corporation. However, given the strategic importance of the platform for advertising and data collection, such a scenario is unlikely in the near future without the intervention of antitrust authorities, which may require the division of assets.