| Bodystyle: | width:30% |
| AOKP | |
| Author: | Team Kang |
| Developer: | Team Kang |
| Family: | Embedded operating system (Linux/Android) |
| Source Model: | Open source |
| Supported Platforms: | ARM |
| Ui: | Stock Android UI |
| Released: | Ice Cream Sandwich 4.0 (Maguro) |
| Latest Release Version: | 9 |
| Marketing Target: | firmware replacement for Android mobile devices |
| Programmed In: | C (core), C++ (some third party libraries), Java (UI) |
| Kernel Type: | Monolithic, Linux kernel modified |
| Language: | English, Catalan, Traditional Chinese, Simplified Chinese, Dutch, Finnish, French, German, Italian, Japanese, Korean, Polish, Portuguese, Russian, Spanish, Swedish, Turkish |
| Package Manager: | Google Play / APK |
| License: | Apache License 2 (Android UI) GNU General Public License v2 (Linux Kernel) |
AOKP, short for Android Open Kang Project, is an open-source replacement distribution for smartphones and tablet computers based on the Android mobile operating system. The name is a play on the word kang (slang for stolen code) and AOSP (Android Open Source Project). The name was a joke, but it stuck.[1] It was started as free and open-source software by Roman Birg based on the official releases of Android Open Source Project by Google, with added original and third-party code, features, and control.[2] [3] [4]
Although only a portion of the total AOKP users elect to report their use of the firmware, as of September 2013, it is used by more than 3.5 million devices around the world.[5] [6]
AOKP allows users to change many aspects of the OS including its appearance and its functions. It allows customizations normally not permitted by the factory firmware.[7]
AOKP builds/releases are provided on a milestone and nightly schedule:[8]
Milestones: Most stable builds which are usually released once a month. However, milestone builds have not been released for several years and the AOKP team appears to just release nightlies as of Nougat builds.
Nightlies: Automatic builds every 3 days with the latest code committed but may contain bugs
To be notified of new releases, users can get the AOKPush[9] application that uses the Google Cloud Messaging (GCM) service provided by Google to immediately receive push notifications when a build is complete and ready to download. With AOKPush, users also get the available test builds and random messages from the developer team. GCM is integrated into the Android framework so the application does not wake up the device periodically to fetch data nor use extra battery. There are also devices that would rely on AOKP to get latest android update.[10]
Not long after the introduction of the HTC Dream (named the "T-Mobile G1" in the United States) mobile phone in September 2008, a method was discovered to attain privileged control (termed "root access") within Android's Linux-based subsystem.[11] Having root access, combined with the open source nature of the Android operating system, allowed the phone's stock firmware to be modified and re-installed onto the phone.
In the following years, several modified firmware releases for mobile devices were developed and distributed by Android enthusiasts. One, maintained by a developer named Roman Birg of AOKP, quickly became popular among several high-end Android mobile owners. AOKP started in November 2011 and quickly grew in popularity, forming a small community of developers called the AOKP Team (also known as "Team Kang"[12]). Within a few months, the number of devices and features supported by AOKP escalated, and AOKP quickly became the second most popular Android firmware distributions, CyanogenMod being the first.[13]
AOKP is developed using a distributed revision control system with the official repositories hosted on GitHub[14] like many other open source projects. New features or bug fix changes made by contributors are submitted using Google's source code review system, Gerrit.[15] Contributions may be tested by anyone, voted up or down by registered users, and ultimately accepted into the code by AOKP developers.
In early 2020 AOKP Developers posted a blog outlining parity with LineageOS upstream. "Device support will be a bit different this time around. We can support any device that is getting Lineage 16.0 builds. We just need a maintainer to test builds and maintain a forum thread."[16]
2011
2012
2013
2014
2014
2015
2016
2017
2020