Android (operating system)


Android 7.0 Nougat (with some Google apps)
Written in Java (UI),[1] C (core), C++
OS family Unix-like
Working state Current
Source model Open source[2] and in most devices with proprietary components[3]
Initial release September 23, 2008 (2008-09-23)[4]
Latest release Android 7.1 Nougat / October 4, 2016 (2016-10-04)
Marketing target Smartphones, tablet computers, Android TV, Android Auto and Android Wear
Available in 100+ languages[5]
Package manager APK (through Google Play)
Platforms 32- and 64-bit ARM, x86,[6] MIPS[7] and MIPS64[lower-alpha 1]
Kernel type Monolithic (modified Linux kernel)
Userland Bionic libc,[8] mksh shell,[9] Toybox as core utilities beginning with Android 6.0,[10][11] previously native core utilities with a few from NetBSD[12][13]
Default user interface Graphical (multi-touch)
License Apache License 2.0
GNU GPL v2 for the Linux kernel modifications[14]
Official website

Android is a mobile operating system developed by Google, based on the Linux kernel and designed primarily for touchscreen mobile devices such as smartphones and tablets. Android's user interface is mainly based on direct manipulation, using touch gestures that loosely correspond to real-world actions, such as swiping, tapping and pinching, to manipulate on-screen objects, along with a virtual keyboard for text input. In addition to touchscreen devices, Google has further developed Android TV for televisions, Android Auto for cars, and Android Wear for wrist watches, each with a specialized user interface. Variants of Android are also used on notebooks, game consoles, digital cameras, and other electronics.

Android has the largest installed base of all operating systems (OS) of any kind.[lower-alpha 2] Android has been the best selling OS on tablets since 2013, and on smartphones it is dominant by any metric.[15][16]

Initially developed by Android, Inc., which Google bought in 2005,[17] Android was unveiled in 2007 along with the founding of the Open Handset Alliance  a consortium of hardware, software, and telecommunication companies devoted to advancing open standards for mobile devices.[18] As of July 2013, the Google Play store has had over one million Android applications ("apps") published  including many "business-class apps"[19] that rival competing mobile platforms[20]  and over 50 billion applications downloaded.[21] An April–May 2013 survey of mobile application developers found that 71% of developers create applications for Android,[22] and a 2015 survey found that 40% of full-time professional developers see Android as their priority target platform, which is comparable to Apple's iOS on 37% with both platforms far above others.[23] In September 2015, Android had 1.4 billion monthly active devices.[24]

Android's source code is released by Google under open source licenses, although most Android devices ultimately ship with a combination of open source and proprietary software, including proprietary software required for accessing Google services.[3] Android is popular with technology companies that require a ready-made, low-cost and customizable operating system for high-tech devices.[25] Its open nature has encouraged a large community of developers and enthusiasts to use the open-source code as a foundation for community-driven projects, which deliver updates to older devices, add new features for advanced users[26] or bring Android to devices originally shipped with other operating systems. The success of Android has made it a target for patent (and copyright) litigation as part of the so-called "smartphone wars" between technology companies.[27][28]


Former Android logo wordmark (2007-2014)

Android, Inc. was founded in Palo Alto, California in October 2003 by Andy Rubin (co-founder of Danger),[29] Rich Miner (co-founder of Wildfire Communications, Inc.),[30] Nick Sears (once VP at T-Mobile),[31] and Chris White (headed design and interface development at WebTV[17]) to develop, in Rubin's words, "smarter mobile devices that are more aware of its owner's location and preferences".[17] The early intentions of the company were to develop an advanced operating system for digital cameras. Though, when it was realized that the market for the devices was not large enough, the company diverted its efforts toward producing a smartphone operating system that would rival Symbian and Microsoft Windows Mobile.[32] Despite the past accomplishments of the founders and early employees, Android Inc. operated secretly, revealing only that it was working on software for mobile phones.[17] That same year, Rubin ran out of money. Steve Perlman, a close friend of Rubin, brought him $10,000 in cash in an envelope and refused a stake in the company.[33]

In July 2005, Google acquired Android Inc. for at least $50 million, whose key employees, including Rubin, Miner and White, stayed at the company after the acquisition.[15][17] Not much was known about Android Inc. at the time, but many assumed that Google was planning to enter the mobile phone market with this move.[17] At Google, the team led by Rubin developed a mobile device platform powered by the Linux kernel. Google marketed the platform to handset makers and carriers on the promise of providing a flexible, upgradeable system. Google had lined up a series of hardware component and software partners and signaled to carriers that it was open to various degrees of cooperation on their part.[34][35][36]

Speculation about Google's intention to enter the mobile communications market continued to build through December 2006.[37] An earlier prototype codenamed "Sooner" had a closer resemblance to a BlackBerry phone, with no touchscreen, and a physical, QWERTY keyboard, but was later re-engineered to support a touchscreen, to compete with other announced devices such as the 2006 LG Prada and 2007 Apple iPhone.[38][39] In September 2007, InformationWeek covered an Evalueserve study reporting that Google had filed several patent applications in the area of mobile telephony.[40][41]

Eric Schmidt, Andy Rubin and Hugo Barra at a 2012 press conference announcing Google's Nexus 7 tablet

On November 5, 2007, the Open Handset Alliance, a consortium of technology companies including Google, device manufacturers such as HTC, Sony and Samsung, wireless carriers such as Sprint Nextel and T-Mobile, and chipset makers such as Qualcomm and Texas Instruments, unveiled itself, with a goal to develop open standards for mobile devices.[18] That day, Android was unveiled as its first product, a mobile device platform built on the Linux kernel.[18][42] The first commercially available smartphone running Android was the HTC Dream, released on October 22, 2008.[43]

Since 2008, Android has seen numerous updates which have incrementally improved the operating system, adding new features and fixing bugs in previous releases. Each major release is named in alphabetical order after a dessert or sugary treat; for example, version 1.5 "Cupcake" was followed by 1.6 "Donut". In 2010, Google launched its Nexus series of devices  a line of smartphones and tablets running the Android operating system, and built by manufacturing partners. HTC collaborated with Google to release the first Nexus smartphone,[44] the Nexus One. Google has since updated the series with newer devices, such as the Nexus 5 phone (made by LG) and the Nexus 7 tablet (made by Asus). Google releases the Nexus phones and tablets to act as their flagship Android devices, demonstrating Android's latest software and hardware features. From 2013 until 2015, Google offered several Google Play Edition devices over Google Play. While not carrying the Google Nexus branding, these were Google-customized Android phones and tablets that also ran the latest version of Android, free from manufacturer or carrier modifications.

From 2010 to 2013, Hugo Barra served as product spokesperson, representing Android at press conferences and Google I/O, Google’s annual developer-focused conference. Barra's product involvement included the entire Android ecosystem of software and hardware, including Honeycomb, Ice Cream Sandwich, Jelly Bean and KitKat operating system launches, the Nexus 4 and Nexus 5 smartphones, the Nexus 7[45] and Nexus 10 tablets,[46] and other related products such as Google Now[47] and Google Voice Search, Google’s speech recognition product comparable to Apple’s Siri.[47] In 2013, Barra left the Android team for Chinese smartphone maker Xiaomi.[48] The same year, Larry Page announced in a blog post that Andy Rubin had moved from the Android division to take on new projects at Google.[49] He was replaced by Sundar Pichai who became the new head of Android and Chrome OS,[50] and, later, by Hiroshi Lockheimer when Pichai became CEO of Google.[51]

In 2014, Google launched Android One, a line of smartphones mainly targeting customers in the developing world. In May 2015, Google announced Project Brillo as a cut-down version of Android that uses its lower levels (excluding the user interface), intended for the "Internet of Things" (IoT) embedded systems.[52]

University of Cambridge research in 2015, concluded that almost 90% of Android phones in use had known but unpatched security vulnerabilities due to lack of updates and support.[53][54] In a year since (mid-2015) that report, well over a billion Android smartphones have been sold (more than the just over billion sold in 2014); and Android 5.0 (with better security) and later, went from 5.4% market share to currently over half, which means that the 90% number must be very outdated; those phones now very likely represent less than half of all Android phones. Recent devices do get security updates;[55][56] Android 5.0 introduced an improved centralized update system.[57][58]



Android's default user interface is mainly based on direct manipulation,[59] using touch inputs that loosely correspond to real-world actions, like swiping, tapping, pinching, and reverse pinching to manipulate on-screen objects, along with a virtual keyboard.[59] Game controllers and full-size physical keyboards are supported via Bluetooth or USB.[60] The response to user input is designed to be immediate and provides a fluid touch interface, often using the vibration capabilities of the device to provide haptic feedback to the user. Internal hardware, such as accelerometers, gyroscopes and proximity sensors[61] are used by some applications to respond to additional user actions, for example adjusting the screen from portrait to landscape depending on how the device is oriented, or allowing the user to steer a vehicle in a racing game by rotating the device, simulating control of a steering wheel.[62]

Android devices boot to the homescreen, the primary navigation and information "hub" on Android devices that is analogous to the desktop found on personal computers. (Android also runs on regular personal computers, as described below). Android homescreens are typically made up of app icons and widgets; app icons launch the associated app, whereas widgets display live, auto-updating content, such as the weather forecast, the user's email inbox, or a news ticker directly on the homescreen.[63] A homescreen may be made up of several pages, between which the user can swipe back and forth, though Android's homescreen interface is heavily customisable, allowing users to adjust the look and feel of the devices to their tastes.[64] Third-party apps available on Google Play and other app stores can extensively re-theme the homescreen, and even mimic the look of other operating systems, such as Windows Phone.[65] Most manufacturers, and some wireless carriers, customise the look and feel of their Android devices to differentiate themselves from their competitors.[66] Applications that handle interactions with the homescreen are called "launchers" because they, among other purposes, launch the applications installed on a device.

Along the top of the screen is a status bar, showing information about the device and its connectivity. This status bar can be "pulled" down to reveal a notification screen where apps display important information or updates, such as a newly received email or SMS text, in a way that does not immediately interrupt or inconvenience the user.[67] Notifications are persistent until read by tapping it, which opens the relevant app, or dismissed by sliding it off the screen. Beginning on Android 4.1, "expanded notifications" can display expanded details or additional functionality; for instance, a music player can display playback controls, and a "missed call" notification provides buttons for calling back or sending the caller an SMS message.[68]

Android provides the ability to run applications that change the default launcher, and hence the appearance and externally visible behaviour of Android. These appearance changes include a multi-page dock or no dock, and many more changes to fundamental features of the user interface.[69]


Applications ("apps"), which extend the functionality of devices, are written using the Android software development kit (SDK) and, often, the Java programming language that has complete access to the Android APIs. Java may be combined with C/C++, together with a choice of non-default runtimes that allow better C++ support;[70][71][72] the Go programming language is also supported since its version 1.4, which can also be used exclusively although with a restricted set of Android APIs.[73] The SDK includes a comprehensive set of development tools,[74] including a debugger, software libraries, a handset emulator based on QEMU, documentation, sample code, and tutorials. Initially, Google's supported integrated development environment (IDE) was Eclipse using the Android Development Tools (ADT) plugin; in December 2014, Google released Android Studio, based on IntelliJ IDEA, as its primary IDE for Android application development. Other development tools are available, including a native development kit (NDK) for applications or extensions in C or C++, Google App Inventor, a visual environment for novice programmers, and various cross platform mobile web applications frameworks. In January 2014, Google unveiled an framework based on Apache Cordova for porting Chrome HTML 5 web applications to Android, wrapped in a native application shell.[75]

Android has a growing selection of third-party applications, which can be acquired by users by downloading and installing the application's APK (Android application package) file, or by downloading them using an application store program that allows users to install, update, and remove applications from their devices. Google Play Store is the primary application store installed on Android devices that comply with Google's compatibility requirements and license the Google Mobile Services software.[3][76] Google Play Store allows users to browse, download and update applications published by Google and third-party developers; as of July 2013, there are more than one million applications available for Android in Play Store.[77] As of July 2013, 50 billion applications have been installed.[78][79] Some carriers offer direct carrier billing for Google Play application purchases, where the cost of the application is added to the user's monthly bill.[80]

Due to the open nature of Android, a number of third-party application marketplaces also exist for Android, either to provide a substitute for devices that are not allowed to ship with Google Play Store, provide applications that cannot be offered on Google Play Store due to policy violations, or for other reasons. Examples of these third-party stores have included the Amazon Appstore, GetJar, and SlideMe. F-Droid, another alternative marketplace, seeks to only provide applications that are distributed under free and open source licenses.[3][81][82][83]

Memory management

Since Android devices are usually battery-powered, Android is designed to manage processes to keep power consumption at a minimum. When an application is not in use the system suspends its operation so that, while available for immediate use rather than closed, it does not use battery power or CPU resources.[84][85]

Android manages the applications stored in memory automatically: when memory is low, the system will begin invisibly and automatically closing inactive processes, starting with those that have been inactive for longest.[86][87] Lifehacker reported in 2011 that third-party task killers were doing more harm than good.[88]

Virtual reality

At Google I/O on May 2016, Google announced Daydream, a virtual reality platform that relies on a smartphone and provides VR capabilities through a virtual reality headset and controller designed by Google itself.[89] The platform is built into Android starting with Android Nougat, differentiating from standalone support for VR capabilities. The software is available for developers, and was released in 2016.


HTC Dream or T-Mobile G1, the first commercially released device running Android (2008).

The main hardware platform for Android is the ARM (ARMv7 and ARMv8-A architectures), with x86 and MIPS architectures also officially supported in later versions of Android. Since Android 5.0 "Lollipop", 64-bit variants of all platforms are supported in addition to the 32-bit variants.[90] The unofficial Android-x86 project provided support for the x86 architectures ahead of the official support.[6][91] MIPS architecture was also supported before Google did. Since 2012, Android devices with Intel processors began to appear, including phones[92] and tablets. While gaining support for 64-bit platforms, Android was first made to run on 64-bit x86 and then on ARM64.

Requirements for the minimum amount of RAM for devices running Android 5.1 range from 512 MB of RAM for normal-density screens, to about 1.8 GB for high-density screens.[93] The recommendation for Android 4.4 is to have at least 512 MB of RAM,[94] while for "low RAM" devices 340 MB is the required minimum amount that does not include memory dedicated to various hardware components such as the baseband processor.[95] Android 4.4 requires a 32-bit ARMv7, MIPS or x86 architecture processor (latter two through unofficial ports),[6][96] together with an OpenGL ES 2.0 compatible graphics processing unit (GPU).[97] Android supports OpenGL ES 1.1, 2.0, 3.0, 3.1 and as of latest major version, 3.2 and Vulkan. Some applications may explicitly require a certain version of the OpenGL ES, and suitable GPU hardware is required to run such applications.[97]

Android devices incorporate many optional hardware components, including still or video cameras, GPS, orientation sensors, dedicated gaming controls, accelerometers, gyroscopes, barometers, magnetometers, proximity sensors, pressure sensors, thermometers, and touchscreens. Some hardware components are not required, but became standard in certain classes of devices, such as smartphones, and additional requirements apply if they are present. Some other hardware was initially required, but those requirements have been relaxed or eliminated altogether. For example, as Android was developed initially as a phone OS, hardware such as microphones were required, while over time the phone function became optional.[79] Android used to require an autofocus camera, which was relaxed to a fixed-focus camera[79] if present at all, since the camera was dropped as a requirement entirely when Android started to be used on set-top boxes.

In addition to running on smartphones and tablets, several vendors run Android natively on regular PC hardware with a keyboard and mouse.[98][99][100][101] In addition to their availability on commercially available hardware, similar PC hardware-friendly versions of Android are freely available from the Android-x86 project, including customized Android 4.4.[102] Using the Android emulator that is part of the Android SDK, or by using BlueStacks or Andy, Android can also run non-natively on x86.[103][104] Chinese companies are building a PC and mobile operating system, based on Android, to "compete directly with Microsoft Windows and Google Android".[105] The Chinese Academy of Engineering noted that "more than a dozen" companies were customising Android following a Chinese ban on the use of Windows 8 on government PCs.[106][107][108]


Android green figure, next to its original packaging

Android is developed in private by Google until the latest changes and updates are ready to be released, at which point the source code is made available publicly.[109] This source code will only run without modification on select devices, usually the Nexus series of devices. The source code is, in turn, adapted by original equipment manufacturers (OEMs) to run on their hardware.[110] Android's source code does not contain the often proprietary device drivers that are needed for certain hardware components.[111]

In 2007, the green Android logo was designed for Google by graphic designer Irina Blok. The design team was tasked with a project to create a universally identifiable icon with the specific inclusion of a robot in the final design. After numerous design developments based on science-fiction and space movies, the team eventually sought inspiration from the human symbol on restroom doors and modified the figure into a robot shape. As Android is open-sourced, it was agreed that the logo should be likewise, and since its launch the green logo has been reinterpreted into countless variations on the original design.[112]

Update schedule

Google provides major incremental upgrades to Android every six to nine months, with confectionery-themed names, which most devices are capable of receiving over the air.[113] The latest major release is Android 7.0 "Nougat".

Compared to its primary rival mobile operating system, iOS, Android updates typically reach various devices with significant delays. Except for devices with the Google Nexus brand, updates often arrive months after the release of the new version, or not at all.[114] This is partly due to the extensive variation in hardware of Android devices, to which each upgrade must be specifically tailored, as the official Google source code only runs on their own Nexus devices. Porting Android to specific hardware is a time- and resource-consuming process for device manufacturers, who prioritize their newest devices and often leave older ones behind.[114] Hence, older smartphones are frequently not updated if the manufacturer decides it is not worth the investment of resources, although the device may be compatible. This problem is compounded when manufacturers customize Android with their own interface and apps, which must be reapplied to each new release. Additional delays can be introduced by wireless carriers who, after receiving updates from manufacturers, further customize and brand Android to their needs and conduct extensive testing on their networks before sending the upgrade out to users.[114]

The lack of after-sale support from manufacturers and carriers has been widely criticized by consumer groups and the technology media.[115][116] Some commentators have noted that the industry has a financial incentive not to upgrade their devices, as the lack of updates for existing devices fuels the purchase of newer ones,[117] an attitude described as "insulting".[116] The Guardian complained that the method of distribution for updates is complicated only because manufacturers and carriers have designed it that way.[116] In 2011, Google partnered with a number of industry players to announce an "Android Update Alliance", pledging to deliver timely updates for every device for 18 months after its release;[118] however, there has not been another official word about that alliance since its announcement.[114][119]

In 2012, Google began decoupling certain aspects of the operating system (particularly core applications) so they could be updated through Google Play Store independently of the operating system. One of these components, Google Play Services, is a closed-source system-level process providing APIs for Google services, installed automatically on nearly all devices running Android version 2.2 and higher. With these changes, Google can add new operating system functionality through Play Services and application updates without having to distribute an upgrade to the operating system itself. As a result, Android 4.2 and 4.3 contained relatively fewer user-facing changes, focusing more on minor changes and platform improvements.[3][120]

In May 2016, it was announced that Google is considering "shaming" smartphone makers who fail to release updated versions of Android to their devices.[121]

Linux kernel

Android's kernel is based on one of the Linux kernel's long-term support (LTS) branches. Since April 2014, Android devices mainly use versions 3.4, 3.10 or 3.18 of the Linux kernel.[122][123] The specific kernel version depends on the actual Android device and its hardware platform;[124][125][126] Android has used various kernel versions since the version 2.6.25 that was used in Android 1.0.[42]

Android's variant of the Linux kernel has further architectural changes that are implemented by Google outside the typical Linux kernel development cycle, such as the inclusion of components like Binder, ashmem, pmem, logger, wakelocks, and different out-of-memory (OOM) handling.[127][128][129] Certain features that Google contributed back to the Linux kernel, notably a power management feature called "wakelocks", were rejected by mainline kernel developers partly because they felt that Google did not show any intent to maintain its own code.[130][131][132] Google announced in April 2010 that they would hire two employees to work with the Linux kernel community,[133] but Greg Kroah-Hartman, the current Linux kernel maintainer for the stable branch, said in December 2010 that he was concerned that Google was no longer trying to get their code changes included in mainstream Linux.[131] Some Google Android developers hinted that "the Android team was getting fed up with the process," because they were a small team and had more urgent work to do on Android.[134]

In August 2011, Linus Torvalds said that "eventually Android and Linux would come back to a common kernel, but it will probably not be for four to five years".[135] In December 2011, Greg Kroah-Hartman announced the start of Android Mainlining Project, which aims to put some Android drivers, patches and features back into the Linux kernel, starting in Linux 3.3.[136] Linux included the autosleep and wakelocks capabilities in the 3.5 kernel, after many previous attempts at merger. The interfaces are the same but the upstream Linux implementation allows for two different suspend modes: to memory (the traditional suspend that Android uses), and to disk (hibernate, as it is known on the desktop).[137] Google maintains a public code repository that contains their experimental work to re-base Android off the latest stable Linux versions.[138][139]

The flash storage on Android devices is split into several partitions, such as /system for the operating system itself, and /data for user data and application installations.[140] In contrast to desktop Linux distributions, Android device owners are not given root access to the operating system and sensitive partitions such as /system are read-only. However, root access can be obtained by exploiting security flaws in Android, which is used frequently by the open-source community to enhance the capabilities of their devices,[141] but also by malicious parties to install viruses and malware.[142]

Android is a Linux distribution according to the Linux Foundation,[143] Google's open-source chief Chris DiBona,[144] and several journalists.[145][146] Others, such as Google engineer Patrick Brady, say that Android is not Linux in the traditional Unix-like Linux distribution sense; Android does not include the GNU C Library (it uses Bionic as an alternative C library) and some of other components typically found in Linux distributions.[147]

Software stack

Android's architecture diagram

On top of the Linux kernel, there are the middleware, libraries and APIs written in C, and application software running on an application framework which includes Java-compatible libraries. Development of the Linux kernel continues independently of other Android's source code bases.

Until version 5.0, Android used Dalvik as a process virtual machine with trace-based just-in-time (JIT) compilation to run Dalvik "dex-code" (Dalvik Executable), which is usually translated from the Java bytecode. Following the trace-based JIT principle, in addition to interpreting the majority of application code, Dalvik performs the compilation and native execution of select frequently executed code segments ("traces") each time an application is launched.[148][149][150] Android 4.4 introduced Android Runtime (ART) as a new runtime environment, which uses ahead-of-time (AOT) compilation to entirely compile the application bytecode into machine code upon the installation of an application. In Android 4.4, ART was an experimental feature and not enabled by default; it became the only runtime option in the next major version of Android, 5.0.[151]

For its Java library, the Android platform uses a subset of the now discontinued Apache Harmony project.[152] In December 2015, Google announced that the next version of Android would switch to a Java implementation based on OpenJDK.[153]

Android's standard C library, Bionic, was developed by Google specifically for Android, as a derivation of the BSD's standard C library code. Bionic itself has been designed with several major features specific to the Linux kernel. The main benefits of using Bionic instead of the GNU C Library (glibc) or uClibc are its smaller runtime footprint, and optimization for low-frequency CPUs. At the same time, Bionic is licensed under the terms of the BSD licence, which Google finds more suitable for the Android's overall licensing model.[150]

Aiming for a different licensing model, toward the end of 2012, Google switched the Bluetooth stack in Android from the GPL-licensed BlueZ to the Apache-licensed BlueDroid.[154]

Android does not have a native X Window System by default, nor does it support the full set of standard GNU libraries. This made it difficult to port existing Linux applications or libraries to Android,[147] until version r5 of the Android Native Development Kit brought support for applications written completely in C or C++.[155] Libraries written in C may also be used in applications by injection of a small shim and usage of the JNI.[156]

Since Marshmallow, "Toybox", a collection of command line utilities (mostly for use by apps, as Android doesn't provide a command line interface by default), replaced similar "Toolbox" collection.[157]

Android has another operating system, Trusty OS, within it, as a part of "Trusty" "software components supporting a Trusted Execution Environment (TEE) on mobile devices." "Trusty and the Trusty API are subject to change. [..] Applications for the Trusty OS can be written in C/C++ (C++ support is limited), and they have access to a small C library. [..] All Trusty applications are single-threaded; multithreading in Trusty userspace currently is unsupported. [..] Third-party application development is not supported in" the current version, and software running on the OS and processor for it, run the "DRM framework for protected content. [..] There are many other uses for a TEE such as mobile payments, secure banking, full-disk encryption, multi-factor authentication, device reset protection, replay-protected persistent storage, wireless display ("cast") of protected content, secure PIN and fingerprint processing, and even malware detection."[158]

Open-source community

Android has an active community of developers and enthusiasts who use the Android Open Source Project (AOSP) source code to develop and distribute their own modified versions of the operating system.[159] These community-developed releases often bring new features and updates to devices faster than through the official manufacturer/carrier channels, with a comparable level of quality;[26] provide continued support for older devices that no longer receive official updates; or bring Android to devices that were officially released running other operating systems, such as the HP TouchPad. Community releases often come pre-rooted and contain modifications not provided by the original vendor, such as the ability to overclock or over/undervolt the device's processor.[160] CyanogenMod is the most widely used community firmware,[161] and acts as a foundation for numerous others. Android-x86 is a version of Android for IBM PC compatibles. There have also been attempts with varying degrees of success to port Android to iPhones, notably the iDroid Project.[162]

Historically, device manufacturers and mobile carriers have typically been unsupportive of third-party firmware development. Manufacturers express concern about improper functioning of devices running unofficial software and the support costs resulting from this.[163] Moreover, modified firmwares such as CyanogenMod sometimes offer features, such as tethering, for which carriers would otherwise charge a premium. As a result, technical obstacles including locked bootloaders and restricted access to root permissions are common in many devices. However, as community-developed software has grown more popular, and following a statement by the Librarian of Congress in the United States that permits the "jailbreaking" of mobile devices,[164] manufacturers and carriers have softened their position regarding third party development, with some, including HTC,[163] Motorola,[165] Samsung[166][167] and Sony,[168] providing support and encouraging development. As a result of this, over time the need to circumvent hardware restrictions to install unofficial firmware has lessened as an increasing number of devices are shipped with unlocked or unlockable bootloaders, similar to Nexus series of phones, although usually requiring that users waive their devices' warranties to do so.[163] However, despite manufacturer acceptance, some carriers in the US still require that phones are locked down, frustrating developers and customers.[169]

Security and privacy

Scope of surveillance by public institutions

As part of the broader 2013 mass surveillance disclosures it was revealed in September 2013 that the American and British intelligence agencies, the National Security Agency (NSA) and Government Communications Headquarters (GCHQ), respectively, have access to the user data on iPhone, BlackBerry, and Android devices. They are reportedly able to read almost all smartphone information, including SMS, location, emails, and notes.[170] In January 2014, further reports revealed the intelligence agencies' capabilities to intercept the personal information transmitted across the Internet by social networks and other popular applications such as Angry Birds, which collect personal information of their users for advertising and other commercial reasons. GCHQ has, according to The Guardian, a wiki-style guide of different apps and advertising networks, and the different data that can be siphoned from each.[171] Later that week, the Finnish Angry Birds developer Rovio announced that it was reconsidering its relationships with its advertising platforms in the light of these revelations, and called upon the wider industry to do the same.[172]

The documents revealed a further effort by the intelligence agencies to intercept Google Maps searches and queries submitted from Android and other smartphones to collect location information in bulk.[171] The NSA and GCHQ insist their activities are in compliance with all relevant domestic and international laws, although the Guardian stated "the latest disclosures could also add to mounting public concern about how the technology sector collects and uses information, especially for those outside the US, who enjoy fewer privacy protections than Americans."[171]

Common security threats

Research from security company Trend Micro lists premium service abuse as the most common type of Android malware, where text messages are sent from infected phones to premium-rate telephone numbers without the consent or even knowledge of the user.[173] Other malware displays unwanted and intrusive advertisements on the device, or sends personal information to unauthorised third parties.[173] Security threats on Android are reportedly growing exponentially; however, Google engineers have argued that the malware and virus threat on Android is being exaggerated by security companies for commercial reasons,[174][175] and have accused the security industry of playing on fears to sell virus protection software to users.[174] Google maintains that dangerous malware is actually extremely rare,[175] and a survey conducted by F-Secure showed that only 0.5% of Android malware reported had come from the Google Play store.[176]

Android's fragmentation is a problem for security, since patches to bugs found in the core operating system often do not reach users of older and lower-price devices.[177][178] One set of researchers say that the failure of vendors to support older devices with patches and updates leaves more than 87% of active devices vulnerable.[179][180] However, the open-source nature of Android allows security contractors to take existing devices and adapt them for highly secure uses. For example, Samsung has worked with General Dynamics through their Open Kernel Labs acquisition to rebuild Jelly Bean on top of their hardened microvisor for the "Knox" project.[181][182]

Android smartphones have the ability to report the location of Wi-Fi access points, encountered as phone users move around, to build databases containing the physical locations of hundreds of millions of such access points. These databases form electronic maps to locate smartphones, allowing them to run apps like Foursquare, Google Latitude, Facebook Places, and to deliver location-based ads.[183] Third party monitoring software such as TaintDroid,[184] an academic research-funded project, can, in some cases, detect when personal information is being sent from applications to remote servers.[185]

Technical security features

Android applications run in a sandbox, an isolated area of the system that does not have access to the rest of the system's resources, unless access permissions are explicitly granted by the user when the application is installed. Before installing an application, Play Store displays all required permissions: a game may need to enable vibration or save data to an SD card, for example, but should not need to read SMS messages or access the phonebook. After reviewing these permissions, the user can choose to accept or refuse them, installing the application only if they accept.[186] The sandboxing and permissions system lessens the impact of vulnerabilities and bugs in applications, but developer confusion and limited documentation has resulted in applications routinely requesting unnecessary permissions, reducing its effectiveness.[187] Google has now pushed an update to Android Verify Apps feature, which will now run in background to detect malicious processes and crack them down.[188]

In Android 6.0 Marshmallow, the permissions system was changed to allow the user to control an application's permissions individually, to block applications if desired from having access to the device's contacts, calendar, phone, sensors, SMS, location, microphone and camera.[189] Full permission control is only possible with root access to the device.[190]

Google uses Google Bouncer malware scanner to watch over and scan applications available in the Google Play Store.[191] It is intended to flag suspicious apps and warn users of any potential threat with an application before they download it.[192] Android version 4.2 Jelly Bean was released in 2012, with enhanced security features, including a malware scanner built into the system, which works in combination with Google Play but can scan apps installed from third party sources as well, and an alert system which notifies the user when an app tries to send a premium-rate text message, blocking the message unless the user explicitly authorises it.[193] Several security firms, such as Lookout Mobile Security,[194] AVG Technologies,[195] and McAfee,[196] have released antivirus software for Android devices. This software is ineffective as sandboxing also applies to such applications, limiting their ability to scan the deeper system for threats.[197][198]

In August 2013, Google released Android Device Manager (ADM), a component that allows users to remotely track, locate, and wipe their Android device through a web interface.[120][199] In December 2013, Google released ADM as an Android application on the Google Play store, where it is available to devices running Android version 2.2 and higher.[200][201]


The source code for Android is open-source: it is developed in private by Google, with the source code released publicly when a new version of Android is released. Google publishes most of the code (including network and telephony stacks) under the non-copyleft Apache License version 2.0. which allows modification and redistribution.[202][203] The license does not grant rights to the "Android" trademark, so device manufacturers and wireless carriers have to license it from Google under individual contracts. Associated Linux kernel changes are released under the copyleft GNU General Public License version 2, developed by the Open Handset Alliance, with the source code publicly available at all times. Typically, Google collaborates with a hardware manufacturer to produce a flagship device (part of the Nexus series) featuring the new version of Android, then makes the source code available after that device has been released.[204] The only Android release which was not immediately made available as source code was the tablet-only 3.0 Honeycomb release. The reason, according to Andy Rubin in an official Android blog post, was because Honeycomb was rushed for production of the Motorola Xoom,[205] and they did not want third parties creating a "really bad user experience" by attempting to put onto smartphones a version of Android intended for tablets.[206]

Only the base Android operating system (including some applications) is open-source software, whereas most Android devices ship with a substantial amount of proprietary software, such as Google Mobile Services, which includes applications such as Google Play Store, Google Search, and Google Play Services  a software layer that provides APIs for the integration with Google-provided services, among others. These applications must be licensed from Google by device makers, and can only be shipped on devices which meet its compatibility guidelines and other requirements.[76][120] Custom, certified distributions of Android produced by manufacturers (such as TouchWiz and HTC Sense) may also replace certain stock Android apps with their own proprietary variants and add additional software not included in the stock Android operating system.[3] There may also be "binary blob" drivers required for certain hardware components in the device.[3][111]

Some stock applications in AOSP code that were formerly used by earlier versions of Android, such as Search, Music, and Calendar, have been abandoned by Google in favor of non-free replacements distributed through Play Store (Google Search, Google Play Music, and Google Calendar) that are no longer open-source. Moreover, open-source variants of some applications also exclude functions that are present in their non-free versions, such as Photosphere panoramas in Camera, and a Google Now page on the default home screen (exclusive to the proprietary version "Google Now Launcher", whose code is embedded within that of the main Google application).[3][207][208][209]

Richard Stallman and the Free Software Foundation have been critical of Android and have recommended the usage of alternatives such as Replicant, because drivers and firmware vital for the proper functioning of Android devices are usually proprietary, and because the Google Play Store application can forcibly install or deinstall applications and, as a result, invite non-free software.[210][211]

Leverage over manufacturers

Google licenses their Google Mobile Services software, along with Android trademarks, only to hardware manufacturers for devices that meet Google's compatibility standards specified in the Android Compatibility Program document.[212] Thus, forks of Android that make major changes to the operating system itself do not include any of Google's non-free components, stay incompatible with applications that require them, and must ship with an alternative software marketplace in lieu of Google Play Store.[3] Examples of such Android forks are Amazon's Fire OS (which is used on the Kindle Fire line of tablets, and oriented toward Amazon services), the Nokia X Software Platform (a fork used by the Nokia X family, oriented primarily toward Nokia and Microsoft services), and other forks that exclude Google apps due to the general unavailability of Google services in certain regions (such as China).[213][214] In 2014, Google also began to require that all Android devices which license the Google Mobile Services software display a prominent "Powered by Android" logo on their boot screens.[76]

Members of the Open Handset Alliance, which include the majority of Android OEMs, are also contractually forbidden from producing Android devices based on forks of the OS;[3][215] in 2012, Acer Inc. was forced by Google to halt production on a device powered by Alibaba Group's Aliyun OS with threats of removal from the OHA, as Google deemed the platform to be an incompatible version of Android. Alibaba Group defended the allegations, arguing that the OS was a distinct platform from Android (primarily using HTML5 apps), but incorporated portions of Android's platform to allow backwards compatibility with third-party Android software. Indeed, the devices did ship with an application store which offered Android apps; however, the majority of them were pirated.[216][217][218]


Android-x86 running on an ASUS EeePC netbook; Android has been unofficially ported to traditional PCs for use as a desktop operating system.

Android received a lukewarm reaction when it was unveiled in 2007. Although analysts were impressed with the respected technology companies that had partnered with Google to form the Open Handset Alliance, it was unclear whether mobile phone manufacturers would be willing to replace their existing operating systems with Android.[219] The idea of an open-source, Linux-based development platform sparked interest,[220] but there were additional worries about Android facing strong competition from established players in the smartphone market, such as Nokia and Microsoft, and rival Linux mobile operating systems that were in development.[221] These established players were skeptical: Nokia was quoted as saying "we don't see this as a threat,"[222] and a member of Microsoft's Windows Mobile team stated "I don't understand the impact that they are going to have."[222]

Since then Android has grown to become the most widely used smartphone operating system[25][223] and "one of the fastest mobile experiences available."[224] Reviewers have highlighted the open-source nature of the operating system as one of its defining strengths, allowing companies such as Nokia (Nokia X family),[225] Amazon (Kindle Fire), Barnes & Noble (Nook), Ouya, Baidu and others to fork the software and release hardware running their own customised version of Android. As a result, it has been described by technology website Ars Technica as "practically the default operating system for launching new hardware" for companies without their own mobile platforms.[25] This openness and flexibility is also present at the level of the end user: Android allows extensive customisation of devices by their owners and apps are freely available from non-Google app stores and third party websites. These have been cited as among the main advantages of Android phones over others.[25][226]

Despite Android's popularity, including an activation rate three times that of iOS, there have been reports that Google has not been able to leverage their other products and web services successfully to turn Android into the money maker that analysts had expected.[227] The Verge suggested that Google is losing control of Android due to the extensive customization and proliferation of non-Google apps and services  Amazon's Kindle Fire line uses Fire OS, a heavily modified fork of Android which does not include or support any of Google's proprietary components, and requires that users obtain software from its competing Amazon Appstore instead of Play Store.[3] In 2014, in an effort to improve prominence of the Android brand, Google began to require that devices featuring its proprietary components display an Android logo on the boot screen.[76]

Android has suffered from "fragmentation",[228] a situation where the variety of Android devices, in terms of both hardware variations and differences in the software running on them, makes the task of developing applications that work consistently across the ecosystem harder than rival platforms such as iOS where hardware and software varies less. For example, according to data from OpenSignal in July 2013, there were 11,868 models of Android device, numerous different screen sizes and eight Android OS versions simultaneously in use, while the large majority of iOS users have upgraded to the latest iteration of that OS.[229] Critics such as Apple Insider have asserted that fragmentation via hardware and software pushed Android's growth through large volumes of low end, budget-priced devices running older versions of Android. They maintain this forces Android developers to write for the "lowest common denominator" to reach as many users as possible, who have too little incentive to make use of the latest hardware or software features only available on a smaller percentage of devices.[230] However, OpenSignal, who develops both Android and iOS apps, concluded that although fragmentation can make development trickier, Android's wider global reach also increases the potential reward.[229]

Market share

Research company Canalys estimated in the second quarter of 2009, that Android had a 2.8% share of worldwide smartphone shipments.[231] By the fourth quarter of 2010, this had grown to 33% of the market becoming the top-selling smartphone platform,[232] overtaking Symbian.[233] By the third quarter of 2011, Gartner estimated that more than half (52.5%) of the smartphone sales belonged to Android.[234] By the third quarter of 2012 Android had a 75% share of the global smartphone market according to the research firm IDC.[235]

In July 2011, Google said that 550,000 Android devices were being activated every day,[236] up from 400,000 per day in May,[237] and more than 100 million devices had been activated[238] with 4.4% growth per week.[236] In September 2012, 500 million devices had been activated with 1.3 million activations per day.[239][240] In May 2013, at Google I/O, Sundar Pichai announced that 900 million Android devices had been activated.[241]

Android market share varies by location. In July 2012, "mobile subscribers aged 13+" in the United States using Android were up to 52%,[242] and rose to 90% in China.[243] During the third quarter of 2012, Android's worldwide smartphone shipment market share was 75%,[235] with 750 million devices activated in total. In April 2013 Android had 1.5 million activations per day.[240] As of May 2013, 48 billion applications ("apps") have been installed from the Google Play store,[244] and by September 2013, one billion Android devices have been activated.[245]

As of July 2013, the Google Play store has had over one million Android applications published, and over 50 billion applications downloaded.[21] A developer survey conducted in April–May 2013 found that Android is used by 71% of mobile developers.[22] The operating system's success has made it a target for patent litigation as part of the so-called "smartphone wars" between technology companies.[27][28]

Android devices account for more than half of smartphone sales in most markets, including the US, while "only in Japan was Apple on top" (September–November 2013 numbers).[246] At the end of 2013, over 1.5 billion Android smartphones have been sold in the four years since 2010,[247][248] making Android the most sold phone and tablet OS. Three billion Android smartphones are estimated to be sold by the end of 2014 (including previous years). According to Gartner research company, Android-based devices outsold all contenders, every year since 2012.[249] In 2013, it outsold Windows 2.8:1 or by 573 million.[250][251][252] As of 2015, Android has the largest installed base of all operating systems;[15] Since 2013, devices running it also sell more than Windows, iOS and Mac OS X devices combined.[253]

According to StatCounter, which tracks only the use for browsing the web, Android is the most popular mobile operating system since August 2013.[254] Android is the most popular operating system for web browsing in India and several other countries (e.g. virtually all of Asia, with Japan and North Korea exceptions). According to StatCounter, Android is most used on mobile in all African countries, and it stated "mobile usage has already overtaken desktop in several countries including India, South Africa and Saudi Arabia",[255] with virtually all countries in Africa having done so already (except for seven countries, including Egypt), such as Ethiopia and Kenya in which mobile (including tablets) usage is at 90.46% (Android only, accounts for 75.81% of all use there[256]).[257]

While Android phones in the Western world commonly include Google's proprietary add-ons (such as Google Play) to the otherwise open-source operating system, this is increasingly not the case in emerging markets; "ABI Research claims that 65 million devices shipped globally with open-source Android in the second quarter of [2014], up from 54 million in the first quarter"; depending on country, percent of phones estimated to be based only on Android's source code (AOSP), forgoing the Android trademark: Thailand (44%), Philippines (38%), Indonesia (31%), India (21%), Malaysia (24%), Mexico (18%), Brazil (9%).[258]

According to a January 2015 Gartner report, "Android surpassed a billion shipments of devices in 2014, and will continue to grow at a double-digit pace in 2015, with a 26 percent increase year over year." This made it the first time that any general-purpose operating system has reached more than one billion end users within a year: by reaching close to 1.16 billion end users in 2014, Android shipped over four times more than iOS and OS X combined, and over three times more than Microsoft Windows. Gartner expected the whole mobile phone market to "reach two billion units in 2016", including Android.[259]

According to a Statistica's estimate, Android smartphones had an installed base of 1.8 billion units in 2015, which was 76% of the estimated total number of smartphones worldwide.[260][261][lower-alpha 3] Android has the largest installed base of any mobile operating system and, since 2013, the highest-selling operating system overall[250][253][263][264][265] with sales in 2012, 2013 and 2014[266] close to the installed base of all PCs.[267] In the third quarter of 2015, Android's share of the global smartphone shipment market was 84.7%, the highest ever.[268] As of September 28, 2016, with 52.5% market share, Samsung remains the leading OEM for shipping Android running smartphoens and tablets, followed by followed by LG, Huawei, Motorola, Lenovo, Sony, HTC, Asus, Alcatel and Xiaomi.[269]

By August 2016, the two biggest continents have gone mobile-majority, judged by web use ("desktop" has 46.92%–55.16% use worldwide, depending on day of the week, making some weeks desktop-minority;[270] lowest full month was at 50.05%[271]); because of Android (see usage share of operating systems), that has majority use on smartphones in virtually all countries (all continents have gone Android-majority, including North America[272][273] except for Oceania, because of Australia),[274] with few exceptions (all of which have iOS-majority); in the US, Android is close to iOS, having exchanged majority position a few times,[275] Canada and the following are also exceptions: Japan, Philippines, Australia and the only exceptions in Europe are the UK, Switzerland, Belgium and the Nordic countries Denmark, Iceland, Sweden and Norway.[276]

By 2016, Android was on the majority of smartphones in virtually all countries in the world,[16][277] excluding United States and Canada (while including North America continent as a whole[278]), Australia and Japan. A few countries, such as the UK, lose Android-majority if tablets are included.

Adoption on tablets

The first-generation Nexus 7 tablet, running Android 4.1 Jelly Bean

Despite its success on smartphones, initially Android tablet adoption was slow.[279] One of the main causes was the chicken or the egg situation where consumers were hesitant to buy an Android tablet due to a lack of high quality tablet applications, but developers were hesitant to spend time and resources developing tablet applications until there was a significant market for them.[280][281] The content and app "ecosystem" proved more important than hardware specs as the selling point for tablets. Due to the lack of Android tablet-specific applications in 2011, early Android tablets had to make do with existing smartphone applications that were ill-suited to larger screen sizes, whereas the dominance of Apple's iPad was reinforced by the large number of tablet-specific iOS applications.[281][282]

Despite app support in its infancy, a considerable number of Android tablets (alongside those using other operating systems, such as the HP TouchPad and BlackBerry PlayBook) were rushed out to market in an attempt to capitalize on the success of the iPad.[281] InfoWorld has suggested that some Android manufacturers initially treated their first tablets as a "Frankenphone business", a short-term low-investment opportunity by placing a smartphone-optimized Android OS (before Android 3.0 Honeycomb for tablets was available) on a device while neglecting user interface. This approach, such as with the Dell Streak, failed to gain market traction with consumers as well as damaging the early reputation of Android tablets.[283][284] Furthermore, several Android tablets such as the Motorola Xoom were priced the same or higher than the iPad, which hurt sales. An exception was the Amazon Kindle Fire, which relied upon lower pricing as well as access to Amazon's ecosystem of applications and content.[281][285]

This began to change in 2012, with the release of the affordable Nexus 7 and a push by Google for developers to write better tablet applications.[286] According to International Data Corporation, shipments of Android-powered tablets surpassed iPads in Q3 2012.[287]

As of the end of 2013, over 191.6 million Android tablets had sold in three years since 2011.[288][289] This made Android tablets the most-sold type of tablet in 2013, surpassing iPads in the second quarter of 2013.[290]

According to the StatCounter's June 2015 web use statistics, Android tablets represent the majority of tablet devices used on the South American[291] (then lost majority) and African continents (60.23%),[292] while they have equaled with the iPad's market share in major countries on all continents (with the North America as an exception, though in El Salvador Android has the majority[293]), and getting close to representing the majority on the whole Asian continent[294] having done so already in India (65.9%),[295] Indonesia (62.22%),[296] and most Middle-Eastern countries.[297] In about half of the European countries, Android tablets have a majority market share.[298] China is an exception for the major developing countries, in which Android phablets (classified as smartphones while similar in size to tablets) are more popular than Android tablets or iPads.

By March 2016, Infoworld stated that Android tablets and smartphones can be a "real part of your business [..] there's no longer a reason to keep Android at arm's length. It can now be as integral to your mobile portfolio as Apple's iOS devices are"[19] as they have "business-class apps",[19] no longer just "OK for email".[19] In 2015, they stated that "Microsoft's Office UI is better on iOS and Android"[20] than in Microsoft's own mobile app for Windows.

Platform usage

  Nougat (0.3%)
  Marshmallow (24.0%)
  Lollipop (34.1%)
  KitKat (24.2%)
  Jelly Bean (13.7%)
  Ice Cream Sandwich (1.3%)
  Gingerbread (1.3%)
  Froyo (0.1%)

Charts in this section provide breakdowns of Android versions, based on devices accessing the Google Play Store in a seven-day period ending on November 7, 2016.[299][lower-alpha 4] Therefore, these statistics exclude devices running various Android forks that do not access the Google Play Store, such as Amazon's Fire tablets.

Version Code name Release date API level DVM/ART Distribution First devices to run version
7.1 Nougat October 4, 2016 25 ART less than 0.1%
7.0 Nougat August 22, 2016 24 ART 0.3% Nexus 5X, Nexus 6P
6.0 Marshmallow October 5, 2015 23 ART 24.0% Nexus 5X, Nexus 6P
5.1 Lollipop March 9, 2015 22 ART 22.8% Android One
5.0 November 3, 2014 21 ART 2.1.0 11.3% Nexus 6
4.4 KitKat October 31, 2013 19 DVM (and ART 1.6.0) 25.2% Nexus 5
4.3 Jelly Bean July 24, 2013 18 DVM 2.0% Nexus 7 2013
4.2 November 13, 2012 17 DVM 6.8% Nexus 4, Nexus 10
4.1 July 9, 2012 16 DVM 4.9% Nexus 7
4.0 Ice Cream Sandwich December 16, 2011 15 DVM 1.3% Galaxy Nexus
2.3.3+ Gingerbread February 9, 2011 10 DVM 1.4.0 1.3% Nexus S
2.2 Froyo May 20, 2010 8 DVM 0.1% Droid 2

Since May 2016, more than half of devices have OpenGL ES 3.0 or higher.

Application piracy

In general, paid Android applications can easily be pirated.[300] In a May 2012 interview with Eurogamer, the developers of Football Manager stated that the ratio of pirated players vs legitimate players was 9:1 for their game Football Manager Handheld.[301] However, not every developer agreed that piracy rates were an issue; for example, in July 2012 the developers of the game Wind-up Knight said that piracy levels of their game were only 12%, and most of the piracy came from China, where people cannot purchase apps from Google Play.[302]

In 2010, Google released a tool for validating authorized purchases for use within apps, but developers complained that this was insufficient and trivial to crack. Google responded that the tool, especially its initial release, was intended as a sample framework for developers to modify and build upon depending on their needs, not as a finished piracy solution.[303] Android "Jelly Bean" introduced the ability for paid applications to be encrypted, so that they may work only on the device for which they were purchased.[304][305]

Legal issues

Further information: Oracle v. Google, Smartphone wars, and Patent troll

Both Android and Android phone manufacturers have been involved in numerous patent lawsuits. On August 12, 2010, Oracle sued Google over claimed infringement of copyrights and patents related to the Java programming language.[306] Oracle originally sought damages up to $6.1 billion,[307] but this valuation was rejected by a United States federal judge who asked Oracle to revise the estimate.[308] In response, Google submitted multiple lines of defense, counterclaiming that Android did not infringe on Oracle's patents or copyright, that Oracle's patents were invalid, and several other defenses. They said that Android's Java runtime environment is based on Apache Harmony, a clean room implementation of the Java class libraries, and an independently developed virtual machine called Dalvik.[309] In May 2012, the jury in this case found that Google did not infringe on Oracle's patents, and the trial judge ruled that the structure of the Java APIs used by Google was not copyrightable.[310][311] The parties agreed to zero dollars in statutory damages for a small amount of copied code.[312] On May 9, 2014, the Federal Circuit partially reversed the district court ruling, ruling in Oracle's favor on the copyrightability issue, and remanding the issue of fair use to the district court.[313][314]

In December 2015, Google announced that the next major release of Android (Android Nougat) would switch to OpenJDK, which is the official open-source implementation of the Java platform, instead of using the now-discontinued Apache Harmony project as its runtime. Code reflecting this change was also posted to the AOSP source repository.[152] In its announcement, Google claimed this was part of an effort to create a "common code base" between Java on Android and other platforms.[153] Google later admitted in a court filing that this was part of an effort to address the disputes with Oracle, as its use of OpenJDK code is governed under the GNU General Public License (GPL) with a linking exception, and that "any damages claim associated with the new versions expressly licensed by Oracle under OpenJDK would require a separate analysis of damages from earlier releases".[152] In June 2016, a United States federal court ruled in favor of Google, stating that its use of the APIs was fair use.[315]

In addition to lawsuits against Google directly, various proxy wars have been waged against Android indirectly by targeting manufacturers of Android devices, with the effect of discouraging manufacturers from adopting the platform by increasing the costs of bringing an Android device to market.[316] Both Apple and Microsoft have sued several manufacturers for patent infringement, with Apple's ongoing legal action against Samsung being a particularly high-profile case. In October 2011, Microsoft said they had signed patent license agreements with ten Android device manufacturers, whose products account for "70% in the U.S.".  and 55% of the worldwide revenue for Android devices.[317] These include Samsung and HTC.[318] Samsung's patent settlement with Microsoft included an agreement to allocate more resources to developing and marketing phones running Microsoft's Windows Phone operating system.[316] Microsoft has also tied its own Android software to patent licenses, requiring the bundling of Microsoft Office Mobile and Skype applications on Android devices to subsidize the licensing fees, while at the same time helping to promote its software lines.[319][320]

Google has publicly expressed its frustration for the current patent landscape in the United States, accusing Apple, Oracle and Microsoft of trying to take down Android through patent litigation, rather than innovating and competing with better products and services.[321] In September 2011, Google purchased Motorola Mobility for US$12.5 billion, which was viewed in part as a defensive measure to protect Android, since Motorola Mobility held more than 17,000 patents.[322] In December 2011, Google bought over a thousand patents from IBM.[323]

In 2013, FairSearch, a lobbying organization supported by Microsoft, Oracle and others, filed a complaint regarding Android with the European Commission, alleging that its free-of-charge distribution model constituted anti-competitive predatory pricing. The Free Software Foundation Europe, whose donors include Google, disputed the Fairsearch allegations.[324] On April 20, 2016, the EU filed a formal antitrust complaint against Google based upon the FairSearch allegations, arguing that its leverage over Android vendors, including the mandatory bundling of the entire suite of proprietary Google software, hindering the ability for competing search providers to be integrated into Android, and barring vendors from producing devices running forks of Android, constituted anti-competitive practices.[325]

Other uses

Ouya, a video game console which runs Android

The open and customizable nature of Android allows it to be used on other electronics aside from smartphones and tablets, including laptops and netbooks, smartbooks,[326] smart TVs (Android TV, Google TV) and cameras (E.g. Galaxy Camera).[327] In addition, the Android operating system has seen applications on smart glasses (Google Glass), smartwatches,[328] headphones,[329] car CD and DVD players,[330] mirrors,[331] portable media players,[332] landline[333] and Voice over IP phones.[334] Ouya, a video game console running Android, became one of the most successful Kickstarter campaigns, crowdfunding US$8.5m for its development,[335][336] and was later followed by other Android-based consoles, such as Nvidia's Shield Portable  an Android device in a video game controller form factor.[337]

In 2011, Google demonstrated "Android@Home", a home automation technology which uses Android to control a range of household devices including light switches, power sockets and thermostats.[338] Prototype light bulbs were announced that could be controlled from an Android phone or tablet, but Android head Andy Rubin was cautious to note that "turning a lightbulb on and off is nothing new", pointing to numerous failed home automation services. Google, he said, was thinking more ambitiously and the intention was to use their position as a cloud services provider to bring Google products into customers' homes.[339][340]

Parrot unveiled an Android-based car stereo system known as Asteroid in 2011,[341] followed by a successor, the touchscreen-based Asteroid Smart, in 2012.[342] In 2013, Clarion released its own Android-based car stereo, the AX1.[343] In January 2014, at the Consumer Electronics Show (CES), Google announced the formation of the Open Automotive Alliance, a group including several major automobile makers (Audi, General Motors, Hyundai, and Honda) and Nvidia, which aims to produce Android-based in car entertainment systems for automobiles, "[bringing] the best of Android into the automobile in a safe and seamless way."[344]

On March 18, 2014, Google announced Android Wear, an Android-based platform specifically intended for smartwatches and other wearable devices; only a developer preview was made publicly available.[345] This was followed by the unveiling of two Android-Wear-based devices, the LG G Watch and Moto 360.[346]

On June 25, 2014, at Google I/O, it was announced that Android TV, a Smart TV platform, is replacing the previously released Google TV. Google also announced Android Auto for use in cars.[347]

Android comes preinstalled on a few laptops (a similar functionality of running Android applications is also available in Google's Chrome OS) and can also be installed on personal computers by end users.[348] On those platforms Android provides additional functionality for physical keyboards[349] and mice, together with the "Alt-Tab" key combination for switching applications quickly with a keyboard. In December 2014, one reviewer commented that Android's notification system is "vastly more complete and robust than in most environments" and that Android is "absolutely usable" as one's primary desktop operating system.[350]

In October 2015, The Wall Street Journal reported that Android will serve as Google's future main laptop operating system, with the plan to fold Chrome OS into it by 2017.[351][352] Google's Sundar Pichai, who led the development of Android, explained that "mobile as a computing paradigm is eventually going to blend with what we think of as desktop today."[351] and back in 2009, Google co-founder Sergey Brin himself said that Chrome OS and Android would "likely converge over time."[353] Lockheimer, who replaced Pichai as head of Android and Chrome OS, responded to this claim with an official Google blog post stating that "While we've been working on ways to bring together the best of both operating systems, there's no plan to phase out Chrome OS [which has] guaranteed auto-updates for five years".[354] That is unlike Android where support is shorter with "EOL dates [being..] at least 3 years [into the future] for Android tablets for education".[355]

See also


  1. Official 64-bit support for all platforms was introduced in Android 5.0 "Lollipop".
  2. Operating systems for microcontrollers are a special case, and not considered here, as they are not meant to be general purpose computers. They are known to outnumber regular computers, and use specialized real-time operating system (RTOS), or no operating system at all. All Android devices with network capabilities, also include an RTOS as their second OS.
  3. To put the Statistica's numbers in context: by Strategy Analytics estimates, Windows the most popular "desktop" operating system, has an estimated installed base of about 1.3 billion at best;[262] they also estimate the overall tablet installed base to be already of comparable size to the PC market and predict tablets will have surpassed them by 2018.
  4. Versions accounting for less than 0.1% are not included.


  1. "Android Code Analysis". Retrieved June 6, 2012.
  2. "The Android Source Code: Governance Philosophy". December 17, 2014. Retrieved January 25, 2015.
  3. 1 2 3 4 5 6 7 8 9 10 11 "Google's iron grip on Android: Controlling open source by any means necessary". Ars Technica. Retrieved December 8, 2013.
  4. "Announcing the Android 1.0 SDK, release 1". September 9, 2008. Retrieved September 21, 2012.
  5. "Android 7.0 Nougat". Retrieved September 5, 2016. Internationalization
    Multi-locale support [..]
    New languages supported: Coupled with allowing you to select multiple languages preferences, Android Nougat allows you to select from 100 new languages and 25 locales for commonly used languages such as English, Spanish, French, and Arabic. This enables Apps to better support and understanding your language preferences even if your devices lacks official support for it.
  6. 1 2 3 Shah, Agam (December 1, 2011). "Google's Android 4.0 ported to x86 processors". Computerworld. International Data Group. Retrieved February 20, 2012.
  7. "MIPS gets sweet with Honeycomb". Retrieved February 20, 2012.
  8. "android/platform/bionic/".
  9. "android/platform/external/mksh/".
  10. "android/platform/external/toybox/toys/".
  11. "Android gets a toybox".
  12. "android/platform/system/core/toolbox/". Archived from the original on February 9, 2014.
  13. "dd command from NetBSD as an example". Archived from the original on March 19, 2014.
  14. "Licenses". Android Open Source Project. Open Handset Alliance. Retrieved September 9, 2012. The preferred license for the Android Open Source Project is the Apache Software License, 2.0. ... Why Apache Software License? ... For userspace (that is, non-kernel) software, we do in fact prefer ASL2.0 (and similar licenses like BSD, MIT, etc.) over other licenses such as LGPL. Android is about freedom and choice. The purpose of Android is promote openness in the mobile world, but we don't believe it's possible to predict or dictate all the uses to which people will want to put our software. So, while we encourage everyone to make devices that are open and modifiable, we don't believe it is our place to force them to do so. Using LGPL libraries would often force them to do so.
  15. 1 2 3 Manjoo, Farhad (May 27, 2015). "A Murky Road Ahead for Android, Despite Market Dominance". The New York Times. ISSN 0362-4331. Retrieved May 27, 2015.
  16. 1 2 "Top Mobile Operating Systems Per Country, Jan 2016".
  17. 1 2 3 4 5 6 Elgin, Ben (August 17, 2005). "Google Buys Android for Its Mobile Arsenal". Bloomberg Businessweek. Bloomberg. Archived from the original on February 24, 2011. Retrieved February 20, 2012. In what could be a key move in its nascent wireless strategy, Google (GOOG) has quietly acquired startup Android, Inc., ...
  18. 1 2 3 "Industry Leaders Announce Open Platform for Mobile Devices" (Press release). Open Handset Alliance. November 5, 2007. Retrieved February 17, 2012.
  19. 1 2 3 4 Gruman, Galen (March 24, 2016). "How to make Android a real part of your business: Android smartphone and tablets can now safely join iPhones and iPads in your mobile portfolio". InfoWorld.
  20. 1 2 "Office Mobile: Better on iPads than on Windows 10 tablets". August 7, 2015. Microsoft's Office UI is better on iOS and Android
  21. 1 2 "Android's Google Play beats App Store with over 1 billion apps, now officially largest". Retrieved August 28, 2013.
  22. 1 2 "Developer Economics Q3 2013 analyst report".
  23. "Developer Economics Q1 2015: State of the Developer Nation". February 17, 2015. Retrieved May 14, 2015.
  24. Callaham, John (September 29, 2015). "Google says there are now 1.4 billion active Android devices worldwide".
  25. 1 2 3 4 Brodkin, Jon (November 5, 2012). "On its 5th birthday, 5 things we love about Android". Ars Technica.
  26. 1 2 "Custom ROMs For Android Explained – Here Is Why You Want Them". August 20, 2012. Retrieved September 15, 2012.
  27. 1 2 Reardon, Marguerite (August 15, 2011). "Google just bought itself patent protection". Retrieved May 1, 2013.
  28. 1 2 Douglas Perry (July 16, 2011). "Google Android Now on 135 Million Devices". Retrieved May 1, 2013.
  29. Markoff, John (November 4, 2007). "I, Robot: The Man Behind the Google Phone". The New York Times. Retrieved February 15, 2012.
  30. Kirsner, Scott (September 2, 2007). "Introducing the Google Phone". The Boston Globe. Archived from the original on January 4, 2010. Retrieved February 15, 2012.
  31. Vogelstein, Fred (April 2011). "How the Android Ecosystem Threatens the iPhone". Wired. Retrieved June 2, 2012.
  32. Chris Welch (April 16, 2013). "Before it took over smartphones, Android was originally destined for cameras". The Verge. Retrieved May 1, 2013.
  33. Vance, Ashlee (July 27, 2011). "Steve Perlman's Wireless Fix". Bloomberg Businessweek. Bloomberg. Retrieved November 3, 2012.
  34. Block, Ryan (August 28, 2007). "Google is working on a mobile OS, and it's due out shortly". Engadget. Retrieved February 17, 2012.
  35. Sharma, Amol; Delaney, Kevin J. (August 2, 2007). "Google Pushes Tailored Phones To Win Lucrative Ad Market". The Wall Street Journal. Retrieved February 17, 2012.
  36. "Google admits to mobile phone plan". Google News. March 20, 2007. Archived from the original on July 3, 2007. Retrieved February 17, 2012.
  37. McKay, Martha (December 21, 2006). "Can iPhone become your phone?; Linksys introduces versatile line for cordless service". The Record (Bergen County). p. L9. Retrieved February 21, 2012. And don't hold your breath, but the same cell phone-obsessed tech watchers say it won't be long before Google jumps headfirst into the phone biz. Phone, anyone?
  38. Ionescu, Daniel (April 26, 2012). "Original Android Prototype Revealed During Google, Oracle Trial". PCWorld. Retrieved February 23, 2014.
  39. Lee, Timothy B. (February 23, 2012). "If Android is a "stolen product," then so was the iPhone". Ars Technica. Retrieved July 11, 2014.
  40. Claburn, Thomas (September 19, 2007). "Google's Secret Patent Portfolio Predicts gPhone". InformationWeek. Archived from the original on March 17, 2008. Retrieved February 17, 2012.
  41. Pearce, James Quintana (September 20, 2007). "Google's Strong Mobile-Related Patent Portfolio". Retrieved February 17, 2012.
  42. 1 2 "Android Kernel Versions". July 7, 2011. Retrieved November 3, 2013.
  43. Mark Wilson (September 23, 2008). "T-Mobile G1: Full Details of the HTC Dream Android Phone". Retrieved December 27, 2013.
  44. Richard Wray (March 14, 2010). "Google forced to delay British launch of Nexus phone". London: Retrieved February 17, 2012.
  45. "Google Unveils a New, Nicer, Pricier Nexus 7 Tablet". Time.
  46. "Hugo Barra: where are the Android tablets of HTC One-like quality?". Android Authority.
  47. 1 2 "Android Director: 'We Have the Most Accurate, Conversational, Synthesized Voice in the World'". Wired.
  48. "Xiaomi co-founder on why ex-Google exec Barra and its own firmware are key to international success". The Next Web.
  49. Charles Arthur (March 13, 2013). "Andy Rubin moved from Android to take on 'moonshots' at Google | Technology |". London: Guardian. Retrieved March 14, 2013.
  50. Page, Larry. "Official Blog: Update from the CEO". Retrieved March 14, 2013.
  51. "Sundar Pichai promotes Hiroshi Lockheimer to oversee Android, Chrome OS and Chromecast". Android Central.
  52. Miller, Ross (May 28, 2015). "Google announces Brillo, an operating system for the Internet of Things: Developer preview coming in Q3". Retrieved June 4, 2015.
  53. "Android Vulnerabilities". Computer Science department, University of Cambridge. Retrieved October 17, 2015.
  54. Amadeo, Ron. "Waiting for Android's inevitable security Armageddon". Ars Technica. Retrieved October 17, 2015.
  55. "Android 6.0.1 security update now rolling out to Samsung Galaxy S7 devices in Canada -". Retrieved November 30, 2016.
  56. "Google Groups". Retrieved November 30, 2016.
  57. "OTA Updates". Android devices in the field can receive and install over-the-air (OTA) updates to the system and application software. [..] This section describes the OTA system as of the Android 5.x release
  58. "Block-Based OTAs". Android 5.0 and later versions use block OTA updates to ensure that each device uses the exact same partition. [..] Android 4.4 and earlier versions used file OTA updates
  59. 1 2 "Touch Devices | Android Open Source". Retrieved September 15, 2012.
  60. "Handling Controller Actions".
  61. "Sensors Overview (Android Developers)". Retrieved October 29, 2013.
  62. "Real Racing 2 Speeds Into The Android Market – Leaves Part 1 In The Dust". September 22, 2011. Retrieved September 15, 2012.
  63. "Widgets | Android Developers". Retrieved September 15, 2012.
  64. "General Android instructions". October 2012. Retrieved October 29, 2013.
  65. "Launcher 7 Brings Windows Phone's Simple, Attractive Interface to Android". May 20, 2011. Retrieved November 24, 2012.
  66. Begun, Daniel A. (March 2011) [2011]. "Dealing with fragmentation on Android devices". Amazing Android Apps. For Dummies. Wiley. p. 7. ISBN 978-0-470-93629-0. Retrieved May 22, 2013.
  67. "UI Overview | Android Developers". Retrieved September 15, 2012.
  68. "Notifications | Android Developers". Retrieved September 15, 2012.
  69. "Launchers". Retrieved February 3, 2014.
  70. "C++ Library Support". Android. libC++ runtime [..] 99% of tests pass when compiling libc++ with Clang 3.4 for all supported ABIs. The failures are mostly in the areas of wchar_t and locales that Android bionic doesn't support.
  71. "Android NDK Native APIs". Retrieved June 10, 2015. The Android NDK provides a set of native headers and shared library files that has gradually increased with successive releases of new Android API levels.
  72. "Sample: hello-jni". Retrieved June 10, 2015.
  73. "Package app, which lets you write Apps for Android (and eventually, iOS)". Retrieved June 9, 2015. There are two ways to use Go in an Android App. The first is as a library called from Java, the second is to use a restricted set of features but work entirely in Go.[..] An app can be written entirely in Go. This results in a significantly simpler programming environment (and eventually, portability to iOS), however only a very restricted set of Android APIs are available. The provided interfaces are focused on games. It is expected that the app will draw to the entire screen (via OpenGL, see the package), and that none of the platform's screen management infrastructure is exposed. On Android, this means a native app is equivalent to a single Activity (in particular a NativeActivity) and on iOS, a single UIWindow. Touch events will be accessible via this package. When Android support is out of preview, all APIs supported by the Android NDK will be exposed via a Go package.
  74. "Tools Overview". Android Developers. July 21, 2009.
  75. Savov, Vlad (January 28, 2014). "Chrome Apps are coming to iOS and Android". The Verge. Retrieved February 2, 2014.
  76. 1 2 3 4 "Google mandates 'Powered by Android' branding on new devices". Retrieved March 28, 2014.
  77. "Google Play Hits 1 Million Apps". Mashable. July 24, 2013. Retrieved January 2, 2014.
  78. Warren, Christina. "Google Play Hits 1 Million Apps". Mashable. Retrieved June 4, 2014.
  79. 1 2 3 "Android Compatibility". Android Developers. Retrieved November 16, 2013.
  80. Chu, Eric (April 13, 2011). "Android Developers Blog: New Carrier Billing Options on Android Market". Retrieved May 15, 2011.
  81. Ganapati, Priya (June 11, 2010). "Independent App Stores Take On Google's Android Market". Wired News. Retrieved February 20, 2012.
  82. "The great Ars experiment—free and open source software on a smartphone?!". Ars Technica. Retrieved October 6, 2014.
  83. "Google evicts ad-blocking software from Google Play store". Ars Technica. Retrieved October 6, 2014.
  84. "The truth about Android task killers and why you don't need them". PhoneDog. June 26, 2011. Retrieved October 30, 2012.
  85. Victor Matos (September 9, 2013). "Lesson 3: Android Application's Life Cycle" (PDF). Cleveland State University. Archived from the original (PDF) on February 22, 2014. Retrieved April 15, 2014.
  86. "Android PSA: Stop Using Task Killer Apps". June 16, 2011. Retrieved October 30, 2012.
  87. Reto Meier. Professional Android 4 Application Development. Retrieved February 9, 2014.
  88. "Updates". Retrieved November 2, 2012.
  89. Howley, Daniel (May 18, 2016). "New Google Virtual Reality". YahooTech. Retrieved May 19, 2016.
  90. "Android Lollipop". Retrieved November 24, 2014. It's supported on ARM, x86, and MIPS architectures and is fully 64-bit compatible.
  91. "Android on Intel Architecture". July 11, 2013. Retrieved February 9, 2014.
  92. Warman, Matt (June 7, 2012). "Orange San Diego Intel Android mobile phone review". The Daily Telegraph. Telegraph Media Group Limited. Retrieved June 19, 2013.
  94. "Android KitKat". Android Developers Portal. Retrieved November 16, 2013.
  95. "7.6.1". Android Compatibility Definition Document (PDF) (4.4 ed.). Google. November 27, 2013. p. 33.
  96. "Android on Intel Architecture". July 11, 2013. Retrieved February 9, 2014.
  97. 1 2 "Android Developers: Graphics". Retrieved November 15, 2013.
  98. "Lenovo N308 Desktop specs". PCWorld. Retrieved November 1, 2014.
  99. "Remix OS - The Future of Android PC is now on Android Marshmallow". Retrieved September 14, 2016.
  100. Michael Brown (May 8, 2014). "Three Android all-in-one PCs reviewed". PCWorld. Retrieved November 1, 2014.
  101. Shawn Knight. "Acer TA272 HUL Android All-in-One Review". TechSpot. Retrieved November 1, 2014.
  102. "ReleaseNote 4.4-r1 – Android-x86 – Porting Android to x86". Retrieved November 1, 2014.
  103. "4 Ways to Run Android on Your PC and Make Your Own "Dual OS" System". January 13, 2014. Retrieved April 7, 2014.
  104. Brad Chacos (September 6, 2013). "Hybrid hijinks: How to install Android on your PC". PCWorld. Retrieved April 7, 2014.
  105. Jose Pagliery (August 25, 2014). "China ditching Windows and Android for its own operating system". CNNMoney. Retrieved November 1, 2014.
  106. "BBC News – China plans new PC operating system in October". BBC News. Retrieved November 1, 2014.
  107. Paul Mozur (March 5, 2013). "China Criticizes Android's Dominance". WSJ. Retrieved November 1, 2014.
  108. "China targets own operating system to take on likes of Microsoft, Google". Reuters. Retrieved November 1, 2014.
  109. At
  110. John McCann  (December 13, 2012). "Android 4.1 Jelly Bean source code released | News". TechRadar. Retrieved December 20, 2012.
  111. 1 2 "Building for devices". Android Open Source Project. Retrieved December 20, 2012.
  112. Kennedy, Pagan (October 11, 2013). "Who Made That Android Logo?". The New York Times, October 11, 2013.
  113. Isacc, Mike (October 21, 2011). "A deep-dive tour of Ice Cream Sandwich with Android's chief engineer". Ars Technica. Retrieved September 15, 2012.
  114. 1 2 3 4 Cunningham, Andrew (June 27, 2012). "What happened to the Android Update Alliance?". Ars Technica. Retrieved September 15, 2012.
  115. "Make Sure You Know Which Version Of Android Is On That Phone Before Buying It – The Consumerist". March 15, 2010. Retrieved November 24, 2012.
  116. 1 2 3 Gillmor, Dan (September 28, 2007). "Android's smartphone OS upgrade issues need more than a quick fix". London: The Guardian. Retrieved November 24, 2012.
  117. "Security takes a backseat on Android in update shambles". The Register. November 22, 2011. Retrieved November 2, 2012.
  118. "Android Update Alliance examined, results since Google I/O found lacking". SlashGear. Retrieved September 15, 2012.
  119. JR Raphael (February 13, 2014). "It's time to rethink the Android upgrade standard". Computerworld Inc. Retrieved March 6, 2014.
  120. 1 2 3 "Balky carriers and slow OEMs step aside: Google is defragging Android". Ars Technica. Retrieved September 3, 2013.
  121. "Google to shame smartphone makers to fix one of the problems with Android". Yahoo Tech. May 26, 2016. Retrieved May 26, 2016.
  122. "Android 4.4.2 KitKat running Kernel 3.10 on the Samsung Galaxy Ace Style". April 3, 2013. Retrieved April 11, 2014.
  123. "Android 4.4.2 KitKat running Kernel 3.10 on the Exynos variant of the Samsung Galaxy S5 (SM-G900H)". May 5, 2014. Retrieved May 5, 2014.
  124. Ryan Whitwam (November 25, 2013). "HTC Posts Android 4.4 Kernel Source And Framework Files For One Google Play Edition, OTA Update Can't Be Far Off". Retrieved December 2, 2013.
  125. "Android 4.4.2 on a Nexus 5 (screenshot)". December 9, 2013. Retrieved January 20, 2014.
  126. "Android 4.4.2 on a Galaxy Note 3 (screenshot)". January 12, 2014. Retrieved January 20, 2014.
  127. Androidology – Part 1 of 3 – Architecture Overview (Video). YouTube. September 6, 2008. Retrieved November 7, 2007.
  128. "Android Anatomy and Physiology" (PDF). Google I/O. May 28, 2008. Retrieved May 23, 2014.
  129. "Android Kernel Features".
  130. David Meyer (February 3, 2010). "Linux developer explains Android kernel code removal". ZDNet. Retrieved February 20, 2012.
  131. 1 2 Greg Kroah-Hartman (February 2, 2010). "Android and the Linux kernel community". Retrieved February 20, 2012. Google shows no sign of working to get their code upstream anymore. Some companies are trying to strip the Android-specific interfaces from their codebase and push that upstream, but that causes a much larger engineering effort, and is a pain that just should not be necessary.
  132. Brian Proffitt (August 10, 2010). "Garrett's LinuxCon Talk Emphasizes Lessons Learned from Android/Kernel Saga". Retrieved February 21, 2012.
  133. Brian Proffitt (April 15, 2010). "DiBona: Google will hire two Android coders to work with". Retrieved February 20, 2012.
  134. Steven J. Vaughan-Nichols (September 7, 2010). "Android/Linux kernel fight continues". Computerworld. Retrieved February 20, 2012.
  135. Steven J. Vaughan-Nichols (August 18, 2011). "Linus Torvalds on Android, the Linux fork". Retrieved February 15, 2012.
  136. Chris von Eitzen (December 23, 2011). "Android drivers to be included in Linux 3.3 kernel". Archived from the original on December 8, 2013. Retrieved February 15, 2012.
  137. Jonathan, Corbet. "Autosleep and wakelocks". LWN.
  138. "Google Working On Android Based On Linux 3.8". February 28, 2013. Retrieved February 28, 2013.
  139. "Google working on experimental Linux Kernel 3.10 for Android". Retrieved September 3, 2013.
  140. Raja, Haroon Q. (May 19, 2011). "Android Partitions Explained: boot, system, recovery, data, cache & misc". Retrieved September 15, 2012.
  141. See rooting
  142. Jools Whitehorn . "Android malware gives itself root access | News". TechRadar. Retrieved September 15, 2012.
  143. McPherson, Amanda (December 13, 2012). "What a Year for Linux: Please Join us in Celebration". Linux Foundation. Retrieved April 16, 2014.
  144. Proschofsky, Andreas (July 10, 2011). "Google: "Android is the Linux desktop dream come true"". Retrieved March 14, 2013.
  145. Hildenbrand, Jerry (November 8, 2012). "Ask AC: Is Android Linux?". Android Central. Retrieved March 14, 2013.
  146. Lynch, Jim (August 20, 2013). "Is Android really a Linux distribution?". ITworld. Retrieved April 17, 2014.
  147. 1 2 Paul, Ryan (February 24, 2009). "Dream(sheep++): A developer's introduction to Google Android". Ars Technica. Retrieved April 3, 2013.
  148. Ben Cheng; Bill Buzbee (May 2010). "A JIT Compiler for Android's Dalvik VM" (PDF). Google. pp. 5–14. Retrieved March 18, 2015.
  149. Phil Nickinson (May 26, 2010). "Google Android developer explains more about Dalvik and the JIT in Froyo". Retrieved July 8, 2014.
  150. 1 2 Burnette, Ed (June 4, 2008). "Patrick Brady dissects Android". ZDNet. Retrieved April 27, 2014.
  151. Toombs, Cody (November 6, 2013). "Meet ART, Part 1: The New Super-Fast Android Runtime Google Has Been Working On In Secret For Over 2 Years Debuts In KitKat". Android Police. Retrieved April 27, 2014.
  152. 1 2 3 "Android N switches to OpenJDK, Google tells Oracle it is protected by the GPL". Ars Technica. Retrieved January 7, 2016.
  153. 1 2 "Google confirms next Android version won't implement Oracle's proprietary Java APIs". VentureBeat. Retrieved December 30, 2015.
  154. "Returning BlueZ to Android". May 6, 2014.
  155. Pruett, Chris (January 11, 2011). "Gingerbread NDK Awesomeness". Android Developers Blog. Google, Inc. Retrieved April 22, 2014.
  156. "Simple DirectMedia Layer for Android". SDL. August 12, 2012. Archived from the original on June 4, 2012.
  157. Android gets a toybox on by Jake Edge (January 14, 2015)
  158. "Trusty TEE".
  159. McFerran, Damien (April 17, 2012). "Best custom ROMs for the Samsung Galaxy S2 | Reviews | CNET UK". Retrieved September 15, 2012.
  160. Isaac, Mike (April 11, 2011). "Android OS Hack Gives Virtual Early Upgrade | Gadget Lab". Retrieved September 15, 2012.
  161. "CyanogenMod Has Now Been Installed On Over 2 Million Devices, Doubles Install Numbers Since January". May 28, 2012. Retrieved September 15, 2012.
  162. "Main Page". Retrieved August 1, 2015.
  163. 1 2 3 "HTC's bootloader unlock page". Retrieved September 15, 2012.
  164. Sadun, Erica (July 26, 2010). "LoC rules in favor of jailbreaking". Retrieved September 15, 2012.
  165. Crook, Jordan (October 24, 2011). "Motorola Offers Unlocked Bootloader Tool". Retrieved September 15, 2012.
  166. "CyanogenMod 7 for Samsung Galaxy S2 (II): Development Already Started!". Inspired Geek. June 8, 2011.
  167. "CyanogenMod coming to the Galaxy S 2, thanks to Samsung". Android Central. June 6, 2011.
  168. Forian, Daniel. "Sony Ericsson supports independent developers – Developer World". Retrieved September 15, 2012.
  169. Kopstein, Joshua (November 20, 2012). "Access Denied: why Android's broken promise of unlocked bootloaders needs to be fixed". The Verge. Retrieved November 24, 2012.
  170. Staff (September 7, 2013). "Privacy Scandal: NSA Can Spy on Smart Phone Data". Retrieved September 7, 2013.
  171. 1 2 3 James Ball. "Angry Birds and 'leaky' phone apps targeted by NSA and GCHQ for user data | World news". Retrieved February 2, 2014.
  172. James Ball (January 28, 2014). "Angry Birds firm calls for industry to respond to NSA spying revelations | World news". Retrieved February 2, 2014.
  173. 1 2 Protalinski, Emil (July 17, 2012). "Android malware numbers explode to 25,000 in June 2012". ZDNet. Retrieved November 9, 2012.
  174. 1 2 "Mobile malware exaggerated by "charlatan" vendors, says Google engineer". PC Advisor. November 24, 2011. Retrieved November 9, 2012.
  175. 1 2 "Android 4.2 brings new security features to scan sideloaded apps". Android Central. Retrieved November 9, 2012.
  176. "Android malware perspective: only 0.5% comes from the Play Store". Retrieved March 14, 2013.
  177. Franceschi-Bicchierai, Lorenzo. "Goodbye, Android". Motherboard. Vice. Retrieved August 2, 2015.
  178. Kingsley-Hughes, Adrian. "The toxic hellstew survival guide". ZDnet. Retrieved August 2, 2015.
  179. Tung, Liam (October 13, 2015). "Android security a 'market for lemons' that leaves 87 percent vulnerable". ZDNet. Retrieved 2015-10-14.
  180. Thomas, Daniel R.; Beresford, Alastair R.; Rice, Andrew. "Security Metrics for the Android Ecosystem" (PDF). Computer Laboratory, University of Cambridge. doi:10.1145/2808117.2808118. Retrieved 2015-10-14.
  181. "Air-to-ground rocket men flog top-secret mobe-crypto to Brad in accounts". The Register. February 28, 2013. Retrieved August 8, 2013.
  182. "Samsung Armors Android to Take On BlackBerry". The New York Times. February 28, 2013.
  183. Steve Lohr (May 8, 2011). "Suit Opens a Window Into Google". The New York Times. ISSN 0362-4331. Retrieved February 16, 2012.
  184. " Real Time Privacy Monitoring on Smartphones". Retrieved February 21, 2012.
  185. Ganapati, Priya (September 30, 2010). "Study Shows Some Android Apps Leak User Data Without Clear Notifications | Gadget Lab". Retrieved January 30, 2012.
  186. "Android Security Overview". Android Open Source Project. Retrieved February 20, 2012.
  187. Felt, Adrienne Porte; Chin, Erika; Hanna, Steve; Song, Dawn; Wagner, David. "Android Permissions Demystified" (PDF). Retrieved February 20, 2012.
  188. Ojas Kulkarni (April 10, 2014). "Google goes hard on Malware for Android platform". Retrieved April 15, 2014.
  189. "Android 6.0 Marshmallow, thoroughly reviewed". Ars Technica.
  190. "[New App] XPrivacy Gives You Massive Control Over What Your Installed Apps Are Allowed To Do". June 23, 2013. Retrieved February 19, 2014.
  191. Chirgwin, Richard. "Google Bouncer flaw". Tech news site and blog. The Register. Retrieved November 20, 2012.
  192. Whittaker, Zack (October 15, 2012). "Google building malware scanner for Google Play: report". ZDNet. Retrieved November 9, 2012.
  193. "Exclusive: Inside Android 4.2's powerful new security system | Computerworld Blogs". November 1, 2012. Retrieved November 9, 2012.
  194. "Lookout Mobile Security". Lookout. Retrieved July 5, 2012.
  195. "Antivirus for Android Smartphones". AVG. Retrieved February 16, 2012.
  196. "McAfee Mobile Security for Android". Retrieved February 16, 2012.
  197. "Android antivirus apps are useless, here's what to do instead". Retrieved April 10, 2012.
  198. Jason Nova (September 14, 2014). "The State of Antivirus for Android". Retrieved November 18, 2014.
  199. "Google announces tool to track lost Android phones". The Verge. Retrieved September 3, 2013.
  200. "Android Device Manager Now Available in Play Store". December 12, 2013. Retrieved December 16, 2013.
  201. "Android Device Manager now available for downloading on Google Play". December 11, 2013. Retrieved December 16, 2013.
  202. Boulton, Clint (October 21, 2008). "Google Open-Sources Android on Eve of G1 Launch". eWeek. Retrieved February 17, 2012.
  203. Ryan Paul (November 6, 2007). "Why Google chose the Apache Software License over GPLv2 for Android". Ars Technica. Retrieved February 16, 2012.
  204. "Frequently Asked Questions: What is involved in releasing the source code for a new Android version?". Android Open Source Project. Retrieved February 16, 2012.
  205. Bray, Tim (April 6, 2011). "Android Developers Blog: I think I'm having a Gene Amdahl moment". Retrieved February 16, 2012.
  206. Jerry Hildenbrand (March 24, 2011). "Honeycomb won't be open-sourced? Say it ain't so!". Retrieved February 16, 2012.
  207. Amadeo, Ron (February 26, 2014). ""Google Now Launcher" hits Play Store, brings Google homescreen to GPE & Nexus devices". Ars Technica. Retrieved February 27, 2014.
  208. Brian Klug (November 14, 2013). "Android 4.4 Factory Images Now Available for Nexus 4, 7 (2012 and 2013), and 10". AnandTech. Retrieved November 19, 2013.
  209. "The Nexus 5's "exclusive" launcher suspiciously receives support for other devices". Ars Technica. Retrieved November 19, 2013.
  210. Stallman, Richard (September 19, 2011). "Is Android really free software?". London: The Guardian. Retrieved September 9, 2012.
  211. Stallman, Richard (August 5, 2012). "Android and Users' Freedom – Support the Free Your Android campaign". Free Software Foundation. Retrieved September 9, 2012.
  212. Android Compatibility Definition Document (PDF) (5.0 ed.). Google. January 11, 2015. Retrieved 2015-03-03.
  213. "This is Nokia X: Android and Windows Phone collide". The Verge. Retrieved March 28, 2014.
  214. Yun Qing, Liau. "Phonemakers make Android China-friendly." ZDNet, October 15, 2012.
  215. "Android Open Source Project Frequently Asked Questions: Compatibility". Retrieved March 13, 2011.
  216. "Alibaba: Google just plan wrong about our OS". CNET. Retrieved March 28, 2014.
  217. Brodkin, Jon. "Google blocked Acer's rival phone to prevent Android "fragmentation"". Ars Technica. Retrieved March 28, 2014.
  218. Jon Brodkin (September 17, 2012). "Pirated Android apps featured prominently on Aliyun app store". Ars Technica. Retrieved March 28, 2014.
  219. "Technology | Q&A: Google's Android". BBC News. November 6, 2007. Retrieved November 9, 2012.
  220. Reardon, Marguerite (February 11, 2008). "Google Android prototypes debut at MWC | Crave – CNET". Retrieved November 9, 2012.
  221. "Android's outing at Barcelona – BizTech – Technology". Sydney Morning Herald. February 12, 2008. Retrieved November 9, 2012.
  222. 1 2 "Symbian, Nokia, Microsoft and Apple downplay Android relevance". Engadget. Retrieved November 9, 2012.
  223. Reisinger, Don (January 16, 2015). "Driverless Cars and Green Tech: What Google Is Doing Outside of Search". eWeek. slide 2.
  224. "On its fifth birthday, Android is "closer to our actual vision" for mobile supremacy". Retrieved November 9, 2012.
  225. "Microsoft Selling Nokia X Android Phones". Business Insider. April 28, 2014. Retrieved May 26, 2014.
  226. "Best Android apps for personalizing and customizing your phone". July 13, 2012. Retrieved November 9, 2012.
  227. Adrianne Jeffries (March 19, 2013). "Disconnect: why Andy Rubin and Android called it quits". The Verge. Retrieved April 3, 2013.
  228. Steve Kovach (July 30, 2013). "Android Fragmentation Report". Business Insider. Retrieved October 19, 2013.
  229. 1 2 Arthur, Charles (July 30, 2013). "Android fragmentation 'worse than ever' – but OpenSignal says that's good". The Guardian. Retrieved August 1, 2013.
  230. Eran, Daniel (October 16, 2013). "Strong demand of Apple's iPhone 5 series driving an "anti-fragmentation" of iOS". Retrieved October 19, 2013.
  231. McLean, Prince (August 21, 2009). "Canalys: iPhone outsold all Windows Mobile phones in Q2 2009". AppleInsider. Retrieved February 16, 2012.
  232. "Google's Android becomes the world's leading smart phone platform". Canalys. January 31, 2011. Retrieved February 15, 2012.
  233. "Android steals Symbian's top smartphone OS crown". Phone arena. Retrieved May 14, 2013.
  234. "Gartner Says Sales of Mobile Devices Grew 5.6 Percent in Third Quarter of 2011; Smartphone Sales Increased 42 Percent". Gartner. November 15, 2011. Retrieved February 16, 2012.
  235. 1 2 "Android Marks Fourth Anniversary Since Launch with 75.0% Market Share in Third Quarter, According to IDC – prUS23771812". Retrieved November 3, 2012.
  236. 1 2 Kumparak, Greg (July 14, 2011). "Android Now Seeing 550,000 Activations Per Day". Techcrunch. Retrieved February 16, 2012.
  237. Van Camp, Jeffrey (June 28, 2011). "Google activates 500,000 Android devices a day, may reach 1 million in October". Yahoo News. Retrieved February 16, 2012.
  238. Barra, Hugo (May 10, 2011). "Android: momentum, mobile and more at Google I/O". The Official Google Blog. Retrieved February 16, 2012.
  239. "500 million devices activated globally, and over 1.3 million added every single day". official Android Engineering teams. September 12, 2012. Archived from the original on October 5, 2012.
  240. 1 2 "Google now at 1.5 million Android activations per day". Engadget. April 16, 2013.
  241. "Google: 900 million Android activations to date, 48 billion app installs". The Verge. May 15, 2013.
  242. Fingas, Jon (September 4, 2012). "ComScore: Android tops 52 percent of US smartphone share, iPhone cracks the 33 percent mark". Retrieved November 24, 2012.
  243. "Report: Android Rises to 90% of Smartphone Market in China". Retrieved November 24, 2012.
  244. "BBC Google activations and downloads update May 2013". BBC News. May 15, 2013. Retrieved May 16, 2013.
  245. Gundotra, Vic. "Just back from a whirlwind trip to Asia visiting our…". Retrieved September 3, 2013.
  246. Whitney, Lance (January 6, 2014). "iPhone market share shrinks as Android, Windows Phone grow". Retrieved January 27, 2014.
  247. "Global smartphone sales by operating system 2009-2016, by quarter". Statista.
  248. "Gartner Says Annual Smartphone Sales Surpassed Sales of Feature Phones for the First Time in 2013".
  249. "Gartner Says Worldwide Traditional PC, Tablet, Ultramobile and Mobile Phone Shipments On Pace to Grow 7.6 Percent in 2014".
  250. 1 2 "Gartner Says Sales of Tablets Will Represent Less Than 10 Percent of All Devices in 2014: Smartphones to Represent 71 Percent of the Global Mobile Phone Market in 2014: Android Device Shipments to Reach One Billion in Emerging Markets in 2015" (Press release). Gartner. October 15, 2014. Retrieved October 19, 2014.
  251. "Tablet Sales Growth Plummets In 2014 As Android Smartphones Continue To Soar: Gartner". TechCrunch. October 15, 2014.
  252. "Global PC Shipments Exceed Forecast with Mild Improvement in Consumer Demand, While Apple Moves to #5 Spot, According to IDC".
  253. 1 2 Yarow, Jay (March 28, 2014). "This Chart Shows Google's Incredible Domination Of The World's Computing Platforms". Retrieved April 23, 2014.
  254. "Mobile/Tablet Browser Market Share by OS". Retrieved September 13, 2015.
  255. "Mobile internet usage soars by 67%". Retrieved October 21, 2014.
  256. StatCounter. "StatCounter Global Stats - Browser, OS, Search Engine including Mobile Usage Share". Retrieved November 30, 2016.
  257. "Global Stats – Browser, OS, Search Engine including Mobile Usage Share". StatCounter. Retrieved September 23, 2016.
  258. Grush, Andrew (October 21, 2014). "Google hoping to lure smaller manufacturers to Google's Android, over AOSP". Android Authority. Retrieved October 22, 2014./
  259. "Tablet Sales Continue to Be Slow in 2015: Tablet Sales to Reach 8 Percent Growth in 2015 While PC Market to Grow 1 Percent". Gartner. January 5, 2015. Retrieved January 23, 2015.
  260. "Installed base of smartphones by operating system in 2015 (in million units)". Statistica. Retrieved November 1, 2016.
  261. "Market share of smartphone OS of total smartphone installed base in 2013 and 2014". Statistica. Retrieved February 18, 2015.
  262. "Replacement Demand to Boost PC Sales in 2015, says Strategy Analytics: More than 70 percent of Developed Market Households Will Continue to Own PCs through 2018". Strategy Analytics. Retrieved February 18, 2015.
  263. Mahapatra, Lisa (November 11, 2013). "Android Vs. iOS: What's The Most Popular Mobile Operating System In Your Country?". Retrieved January 30, 2014.
  264. Elmer-DeWitt, Philip (January 10, 2014). "Don't mistake Apple's market share for its installed base". CNN. Retrieved January 30, 2014.
  265. "Samsung sells more smartphones than all major manufacturers combined in Q1". Retrieved May 12, 2014.
  266. "Global mobile statistics 2014 Part A: Mobile subscribers; handset market share; mobile operators". mobiThinking. May 2014. Retrieved September 9, 2014.
  267. Rowinski, Dan (December 10, 2013). "The Post-PC Era Begins In Earnest Next Year: In 2014, smartphones will most likely eclipse PCs in terms of the number of devices in use around the world". readwrite. Retrieved September 9, 2014.
  268. "Smartphone OS global market share 2009-2016 - Statistic". Retrieved November 30, 2016.
  269. "Android phone manufacturer market share - AppBrain". Retrieved November 30, 2016.
  270. "StatCounter Global Stats – Browser, OS, Search Engine including Mobile Usage Share".
  271. StatCounter. "StatCounter Global Stats - Browser, OS, Search Engine including Mobile Usage Share". Retrieved November 30, 2016.
  272. "StatCounter Global Stats – Browser, OS, Search Engine including Mobile Usage Share".
  273. "StatCounter Global Stats – Browser, OS, Search Engine including Mobile Usage Share".
  274. "StatCounter Global Stats – Browser, OS, Search Engine including Mobile Usage Share".
  275. "StatCounter Global Stats – Browser, OS, Search Engine including Mobile Usage Share".
  276. StatCounter. "StatCounter Global Stats - Browser, OS, Search Engine including Mobile Usage Share". Retrieved November 30, 2016.
  277. StatCounter. "StatCounter Global Stats - Browser, OS, Search Engine including Mobile Usage Share". Retrieved November 30, 2016.
  278. "StatCounter Global Stats - Browser, OS, Search Engine including Mobile Usage Share".
  279. Wilson Rothman (October 24, 2012). "Why iPad is stomping Android tabs 24 to 1 – Technology on". Retrieved November 9, 2012.
  280. Kevin C. Tofel (March 19, 2012). "What devs say about iPad (but not Android tablets)". Retrieved November 9, 2012.
  281. 1 2 3 4 "Why there aren't more Android tablet apps, by the numbers". ZDNet. March 21, 2012. Retrieved November 9, 2012.
  282. Poeter, Damon (December 7, 2012). "Goldman Highlights Microsoft's Shrinking Market Share". PC Magazine. Retrieved December 10, 2012.
  283. Gruman, Galen (April 5, 2011). "Why Google's tighter control over Android is a good thing | Mobile Technology". InfoWorld. Retrieved March 14, 2013.
  284. Gruman, Galen. "Anatomy of failure: Mobile flops from RIM, Microsoft, and Nokia". Macworld. Retrieved May 14, 2013.
  285. Hiner, Jason (January 5, 2012). "Why Android tablets failed: A postmortem". TechRepublic. Retrieved November 9, 2012.
  286. Cunningham, Andrew (October 8, 2012). "Google to Android devs: make nicer tablet apps, pretty please?". Ars Technica. Retrieved November 9, 2012.
  287. Kovach, Steve. "Android Now Ahead Of Apple's iOS In Tablet Market Share". Business Insider.
  288. "Gartner Says Worldwide Tablet Sales Grew 68 Percent in 2013, With Android Capturing 62 Percent of the Market".
  289. "Gartner Says Worldwide Media Tablets Sales to Reach 119 Million Units in 2012".
  290. "Android Ecosystem Takes the Baton from Apple iPad in the Tablet Race". ABIresearch. September 27, 2013. Retrieved September 10, 2014.
  291. "StatCounter Global Stats – Browser, OS, Search Engine including Mobile Usage Share". Retrieved August 1, 2015.
  292. "Top 7 Tablet OSs in Africa from Mar 2014 to Jun 2015". Retrieved March 19, 2015.
  293. "StatCounter Global Stats – Browser, OS, Search Engine including Mobile Usage Share". Retrieved August 1, 2015.
  294. "StatCounter Global Stats – Browser, OS, Search Engine including Mobile Usage Share". Retrieved August 1, 2015.
  295. "Top 7 Tablet OSs in India from Mar 2014 to Jun 2015".
  296. "Top 7 Tablet OSs in Indonesia from Mar 2014 to Jun 2015".
  297. "StatCounter Global Stats – Browser, OS, Search Engine including Mobile Usage Share". Retrieved August 1, 2015.
  298. "StatCounter Global Stats – Browser, OS, Search Engine including Mobile Usage Share". Retrieved August 1, 2015.
  299. "Android Developers: Dashboards". November 7, 2016. Retrieved November 7, 2016.
  300. Wired UK (May 3, 2012). "Op-Ed: Android Piracy Is Huge Problem for Game Devs | Game|Life". Retrieved September 15, 2012.
  301. Yin, Wesley (April 24, 2012). "Football Manager dev hopes to stick with Android despite 9:1 piracy rate". Retrieved September 15, 2012.
  302. Armasu, Lucian (July 30, 2012). "Wind-up Kinght developer: Piracy rates on iOS and Android are comparable, China is the main source". Retrieved October 6, 2012.
  303. Paul, Ryan (August 25, 2010). "Android antipiracy cracked, Google says devs used it wrong". Ars Technica. Retrieved September 15, 2012.
  304. "Update: Google posts DRM workaround for paid Android Wear apps". Ars Technica. Retrieved September 7, 2015.
  305. McAllister, Neil (August 8, 2012). "Android app DRM quietly disabled due to bug". The Register. Retrieved June 10, 2012.
  306. Niccolai, James (August 12, 2010). "Update: Oracle sues Google over Java use in Android". Computerworld. IDG. Retrieved February 16, 2012.
  307. "Oracle seeks up to $6.1 billion in Google lawsuit". Reuters. June 18, 2011. Retrieved September 7, 2011.
  308. "Judge tosses Oracle's $6.1 billion damage estimate in claim against Google". July 22, 2011. Retrieved September 7, 2011.
  309. Singel, Ryan (October 5, 2010). "Calling Oracle Hypocritical, Google Denies Patent Infringement". Wired. Retrieved February 16, 2012.
  310. Josh Lowensohn (May 23, 2012). "Jury clears Google of infringing on Oracle's patents". ZDNet. Retrieved May 25, 2012.
  311. Joe Mullin (May 31, 2012). "Google wins crucial API ruling, Oracle's case decimated". Ars Technica. Retrieved June 1, 2012.
  312. Niccolai, James (June 20, 2012). "Oracle agrees to 'zero' damages in Google lawsuit, eyes appeal". Retrieved June 23, 2012.
  313. Rosenblatt, Seth (May 9, 2014). "Court sides with Oracle over Android in Java patent appeal". CNET. Retrieved May 10, 2014.
  314. "ORACLE AMERICA, INC. , Plaintiff – Appellant, v. GOOGLE INC., Defendant – Cross – Appellant." (PDF). Court of Appeals for the Federal Circuit. May 9, 2014. Retrieved May 10, 2014.
  315. "Google beats Oracle—Android makes "fair use" of Java APIs". Ars Technica. Retrieved June 30, 2016.
  316. 1 2 Newman, Jared (September 28, 2011). "Microsoft-Samsung Patent Deal: Great News for Windows Phones". PCWorld. Retrieved September 15, 2012.
  317. "Microsoft collects license fees on 50% of Android devices, tells Google to "wake up"". Ars Technica. Retrieved February 16, 2012.
  318. Mikael Ricknäs (September 28, 2011). "Microsoft signs Android licensing deal with Samsung". Computerworld. Retrieved February 16, 2012.
  319. Trent, Rod. "Microsoft Inside: 20 New Android Device Manufacturers Sign-on to Pre-Install Office and Skype". SuperSite for Windows. Penton. Retrieved August 23, 2016.
  320. "Xiaomi will bundle Microsoft's Office and Skype apps on its Android devices". The Verge. Retrieved August 23, 2016.
  321. Jacqui Cheng (August 3, 2011). "Google publicly accuses Apple, Microsoft, Oracle of patent bullying". Retrieved February 16, 2012.
  322. Casey Johnston (August 15, 2011). "Google, needing patents, buys Motorola wireless for $12.5 billion". Retrieved February 16, 2012.
  323. Paul, Ryan (January 4, 2012). "Google buys another round of IBM patents as its Oracle trial nears". Ars Technica. Retrieved February 16, 2012.
  324. "FSFE objects to claims of 'predatory pricing' in Free Software". Free Software Foundation Europe. Retrieved September 28, 2013.
  325. "Google faces EU charge over Android 'abuse of dominance'". BBC News. Retrieved April 20, 2016.
  326. Laura June (September 6, 2010). "Toshiba AC100 Android smartbook hits the United Kingdom". Engadget. Retrieved February 20, 2012.
  327. Samsung (August 29, 2012). "Samsung Galaxy Camera". Retrieved August 30, 2012.
  328. Hollister, Sean (January 10, 2012). "Sony Smart Watch (aka Sony Ericsson LiveView 2) hands-on". The Verge. Retrieved February 16, 2012.
  329. Rik Myslewski (January 12, 2011). "Android-powered touchscreen Wi-Fi headphones". Retrieved January 16, 2012.
  330. "Car Player Android-Car Player Android Manufacturers, Suppliers and Exporters on". Retrieved February 20, 2012.
  331. "Android Everywhere: 10 Types of Devices That Android Is Making Better". February 26, 2012. Retrieved September 15, 2012.
  332. Will G. (December 1, 2011). "Top Android MP3 Players for 2011". Retrieved February 16, 2012.
  333. "Archos Smart Home Phone". Android Central. January 19, 2012. Retrieved January 30, 2012.
  334. "Grandstream Announces Android IP Phone".
  335. "OUYA interview: Julie Uhrman tackles consoles & critics". Destructoid. Retrieved November 2, 2012.
  336. Erik Kain (April 18, 2012). "An Interview With 'Ouya' Founder Julie Uhrman On A New Breed Of Video Game Console". Forbes. Retrieved November 2, 2012.
  337. "NVIDIA Shield ships July 31st, barely meets delayed launch window". Engadget. July 21, 2013. Retrieved July 21, 2013.
  338. "Editorial: Android@Home is the best worst thing that could happen to home automation". Engadget. Retrieved November 2, 2012.
  339. Nilay Patel (February 27, 2012). "Home in the clouds: Google's home automation platform to have major services integration". The Verge. Retrieved November 2, 2012.
  340. "Why the time has come for Android @Home to finally make a splash by Janko Roettgers".
  341. "Parrot Asteroid car receiver packs Android and apps into your dash". Engadget. Retrieved January 24, 2014.
  342. "Parrot unveils Asteroid Smart, Tablet and Mini car infotainment systems, we go hands-on". Engadget. Retrieved January 24, 2014.
  343. Low, Aloysius (September 13, 2013). "Clarion launches new Android-based AX1 car stereo". CNET Asia. CBS Interactive. Retrieved November 12, 2013.
  344. Souppouris, Aaron (January 6, 2014). "Google launches the Android-based Open Automotive Alliance with Audi, Honda, GM, and more". The Verge. Retrieved January 24, 2014.
  345. "Android Wear | Android Developers". Retrieved March 20, 2014.
  346. Palladino, Valentina (September 30, 2013). "Google reveals Android Wear, an operating system for smartwatches". The Verge. Retrieved March 20, 2014.
  347. "Google I/O: Android TV, Smart Cars, Wearables, and More". CBS. June 25, 2014. Retrieved October 11, 2015.
  348. "Android-x86 – Porting Android to x86".
  349. "Keyboard Devices".
  350. Lunduke, Bryan (December 1, 2014). "The Linux desktop-a-week review: Android as a desktop environment". Network World. Retrieved March 24, 2015.
  351. 1 2 Alistair Barr (October 30, 2015). "Alphabet's Google to Fold Chrome Operating System Into Android". WSJ. Retrieved November 5, 2015.
  352. Sam Tran. "Chrome OS Will Be Merged Into Android - OMG! Chrome!". OMG! Chrome!. Retrieved November 14, 2015.
  353. Sam Byford (October 30, 2015). "Google is 'very committed' to Chrome OS after Android merger reports". The Verge. Vox Media.
  354. Lockheimer, Hiroshi (November 2, 2015). "Chrome OS is here to stay". Retrieved November 27, 2015.
  355. "Android End of Life policy - Chrome for Work and Education Help".

External links

Wikimedia Commons has media related to Android (operating system).
This article is issued from Wikipedia - version of the 11/30/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.