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 and AOSP. 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. 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 across the world.
Features
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.
LED control: The color and pulsing of the notification LED can be custom set for various applications.
Navigation ring: Actions can be assigned to the navigation ring, to allow for quicker access applications.
Ribbon: Allows users to use swipe gestures anywhere and enables a system-wide custom application shortcuts and actions.
Vibration patterns: Users can build custom vibration patterns to be assigned to notifications from certain applications or calls from certain people.
Native theme support: Themes, downloaded from the Google Play Store or from other sources, can be applied to give a modified appearance to the device interface. AOKP now features Substratum support.
Customization of the hardware and software buttons, including track skip/flashlight while the screen is off, PIE control and the ROM's unique Fling navigation system
UI control, including colour strokes and background blue
Status bar customization, such as battery icon stylization and network activity
Power menu customization
Notification and quick settings configurations, such as how many toggles are displayed on the quick settings header at a time
Release versions
AOKP builds/releases are provided on a milestone and nightly schedule: 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 application that uses the Google Cloud Messaging 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.
Firmware history and development
Not long after the introduction of the HTC Dream mobile phone in September 2008, a method was discovered to attain privileged control 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. 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. 2011
