The Difference Between Android AOSP and OHA

There are two “flavors” of the Android OS: (1) OHA — Open Handset Alliance — which needs to be licensed from Google and used within their T&Cs, and (2) AOSP, which is the open source version of Android that anyone can fork, modify and use as they wish.

Here’s a quick explanation of the two.

Google develops the Android OS. This development happens behind closed doors and once every so often Google publishes the latest version to open source.

Open Handset Alliance

The OHA version of Google contains this Android OS as well as apps and services (that are NOT open source) provided by Google. Apps such as Google Maps, YouTube, GMail are part of this bundle. The Google Play Store itself is a big part – that allows users to find and download apps and content from this appstore. Most importantly, the bundle includes Google Play Services – which is a set of services that 3rd party apps can use on this version of Android. For example, authentication using the user’s Google account, in-app purchases through Google Wallet, distributing / updating apps through the Play Store, push notifications, etc.

Google Play Services

The OHA version of Android is built for Google’s line of Nexus devices. You may see it referred to as “vanilla android”. When a handset manufacturer licenses this from Google, it is obligated to adhere to certain rules: there are some UI restrictions, a suite of Google Apps need to be present on the device – Google Maps, YouTube, GMail, Calendar, etc. Google Search will need to be the default search engine. There is a long document describing all these rules that Google calls the Compatibility Definition Document. Additionally, the manufacturer is now tied into Google’s ecosystem. It cannot build any device that does follow these rules.

Android Open Source Project

AOSP is the open source version of Android. Any one can fork it, modify and use it however they wish, without restriction. However, this is simply the OS without any supporting ecosystem – no app store, cloud infrastructure, push notification system, or any Google Apps. In fact, manufacturers using just AOSP (without adhering to compatibility) can not include Google Apps on their device.

It is possible for users to install Google’s apps on their AOSP devices (some of them, at least) but this is usually not formally supported and users do it at their own risk.

Amazon’s Kindle Fire is perhaps the most famous fork of AOSP. CyanogenMod is another.