AOKP

AOKP
Developer Team Kang
Written in C (core), C++ (some third party libraries), Java (UI)
OS family Embedded operating system (Linux/Android)
Working state Current
Source model Open source
Initial release Ice Cream Sandwich 4.0 (Maguro)
Latest release jb-mr2-milestone1 (Android 4.3.1) / 18 December 2013 (2013-12-18)
Latest preview kitkat (Android 4.4.4) / 25 June 2014 (2014-06-25)
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
Platforms ARM
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)
Official website www.aokp.co

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 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][5]

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.[6][7]

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.[8]

AOKP is designed to increase performance and reliability over official stock firmware releases.[9]

Release versions

AOKP builds/releases are provided on a milestone and nightly schedule:[10]

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[11] 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.[12]

Firmware history and development

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.[13] 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 firmwares 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"[14]). 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.[15]

AOKP is developed using a distributed revision control system with the official repositories hosted on GitHub[16] 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.[17] Contributions may be tested by anyone, voted up or down by registered users, and ultimately accepted into the code by AOKP developers.

2011

AOKP Ice Cream Sandwich (ICS) Android 4.0.X

2012

AOKP Jelly Bean (JB) Android 4.1.X

2013

AOKP Jelly Bean (JB-MR1) Android 4.2.X AOKP Jelly Bean (JB) Android 4.3.X

2014

AOKP KitKat Android 4.4.X

Supported devices

ASUS
HTC
LG
Motorola
Oppo
Samsung
Sony
OnePlus

See also

References

  1. ↑ "What is AOKP?". aokp.co. Retrieved 2014-05-03.
  2. ↑ Brad Linder (2014-01-24). "CyanogenMod's new hires: Founders of AOKP, Chameleon ROM". Liliputing. Retrieved 2014-04-18.
  3. ↑ "AOSP、AOKP、CM ROM 究竟有哪些区别？". Xda.cn. 2013-01-07. Retrieved 2014-03-04.
  4. ↑ Motorola il iDEN (2014-03-31). "Infographic: Features of AOKP Custom Android ROM". Intomobile.com. Retrieved 2014-04-18.
  5. ↑ "AOKP is a popular new ROM, what are the differences to CyanogenMod?". Androidauthority.com. Retrieved 2014-04-18.
  6. ↑ "AOKP ROM Passes 3.5 Million Users, Android 4.3 Nightlies Available Now". Androidpolice.com. 2013-09-28. Retrieved 2014-04-18.
  7. ↑ "AOKP ROM crosses 3.5 million users; Releases Android 4.3 based nightlies". Androidbeat.com. 2013-09-29. Retrieved 2014-04-18.
  8. ↑ "AOKP Feature Overview". aokp.co. Retrieved 2014-05-03.
  9. ↑ "[JB 4.3][ROM]Infamous AOKP 1.1". xda-developers.com. Retrieved 2014-05-03.
  10. ↑ "AOKP Release Versioning". aokp.co. Retrieved 2014-05-03.
  11. ↑ "Extras that help support our devs.". aokp.co. Retrieved 2014-05-03.
  12. ↑ GMT (2014-01-12). "Galaxy Nexus GT-I9250 Gets Android 4.4.2 KitKat with Official AOKP ROM [How to Install]". Ibtimes.co.uk. Retrieved 2014-04-18.
  13. ↑ Ben Marvin (14 May 2009). "How To: Root Your G1 And Install Android 1.5 Cupcake". The Android Site. Retrieved 2010-10-28.
  14. ↑ "Who we are". aokp.co. Retrieved 2014-05-15.
  15. ↑ "AOKP hits 1 million downloads as first Milestone is released". androidcentral.com. Retrieved 2014-05-15.
  16. ↑ "AOKP Source Code at Github".
  17. ↑ "AOKP Gerrit Site".

External links

This article is issued from Wikipedia - version of the 3/21/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.