|Written in||C (core), C++ (some third party libraries), Java (UI)|
|OS family||Embedded operating system (Linux/Android)|
|Source model||Open source|
|Initial release||Ice Cream Sandwich 4.0 (Maguro)|
|Latest release||jb-mr2-milestone1 (Android 4.3.1) / 18 December 2013|
|Latest preview||kitkat (Android 4.4.4) / 25 June 2014|
|Marketing target||firmware replacement for Android mobile devices|
|Available in||English, Catalan, Traditional Chinese, Simplified Chinese, Dutch, Finnish, French, German, Italian, Japanese, Korean, Polish, Portuguese, Russian, Spanish, Swedish, Turkish|
|Package manager||Google Play / APK|
|Kernel type||Monolithic, Linux kernel modified|
|Default user interface||Stock Android UI|
|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. 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.
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.
AOKP is designed to increase performance and reliability over official stock firmware releases.
Milestones: Most stable builds which are usually released once a month
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 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.
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. 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"). 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.
AOKP is developed using a distributed revision control system with the official repositories hosted on GitHub 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. Contributions may be tested by anyone, voted up or down by registered users, and ultimately accepted into the code by AOKP developers.
AOKP Ice Cream Sandwich (ICS) Android 4.0.X
AOKP Jelly Bean (JB) Android 4.1.X
AOKP Jelly Bean (JB-MR1) Android 4.2.X AOKP Jelly Bean (JB) Android 4.3.X
AOKP KitKat Android 4.4.X
AOKP Lollipop Android 5.0.x
AOKP Marshmellow Android 6.0.1
AOKP Nougat Android 7.0
AOKP Nougat Android 7.1.x
None of the audio/visual content is hosted on this site. All media is embedded from other sites such as GoogleVideo, Wikipedia, YouTube etc. Therefore, this site has no control over the copyright issues of the streaming media.
All issues concerning copyright violations should be aimed at the sites hosting the material. This site does not host any of the streaming media and the owner has not uploaded any of the material to the video hosting servers. Anyone can find the same content on Google Video or YouTube by themselves.
The owner of this site cannot know which documentaries are in public domain, which has been uploaded to e.g. YouTube by the owner and which has been uploaded without permission. The copyright owner must contact the source if he wants his material off the Internet completely.