Android (operating system)

From SytechPedia

Lua error in Module:Effective_protection_level at line 63: attempt to index field 'TitleBlacklist' (a nil value). Template:Infobox OS Android is a mobile operating system based on a modified version of the Linux kernel and other open source software, designed primarily for touchscreen mobile devices such as smartphones and tablets. Android is developed by a consortium of developers known as the Open Handset Alliance and commercially sponsored by Google. It was unveiled in November 2007, with the first commercial Android device, the HTC Dream, being launched in September 2008.

Most versions of Android are proprietary. The core components are taken from the Android Open Source Project (AOSP), which is free and open-source software (FOSS) primarily licensed under the Apache License. When Android is installed on devices, ability to modify the otherwise FOSS software is usually restricted, either by not providing the corresponding source code or preventing reinstallation through technical measures, rendering the installed version proprietary. Most Android devices ship with additional proprietary software pre-installed,[1] most notably Google Mobile Services (GMS)[2] which includes core apps such as Google Chrome, the digital distribution platform Google Play, and associated Google Play Services development platform.

Over 70 percent of Android smartphones run Google's ecosystem; some with vendor-customized user interface and software suite, such as TouchWiz and later One UI by Samsung, and HTC Sense.[3] Competing Android ecosystems and forks include Fire OS (developed by Amazon), ColorOS by OPPO, OriginOS by vivo and MagicUI by Honor or custom ROM such as LineageOS. However, the "Android" name and logo are trademarks of Google which imposes standards to restrict the use of Android branding by "uncertified" devices outside their ecosystem.[4][5]

The source code has been used to develop variants of Android on a range of other electronics, such as game consoles, digital cameras, portable media players, PCs, each with a specialized user interface. Some well known derivatives include Android TV for televisions and Wear OS for wearables, both developed by Google. Software packages on Android, which use the APK format, are generally distributed through proprietary application stores like Google Play Store, Amazon Appstore (including for Windows 11), Samsung Galaxy Store, Huawei AppGallery, Cafe Bazaar, and GetJar, or open source platforms like Aptoide or F-Droid.

Android has been the best-selling OS worldwide on smartphones since 2011 and on tablets since 2013. As of May 2021, it has over three billion monthly active users, the largest installed base of any operating system,[6] and as of January 2021, the Google Play Store features over 3 million apps.[7] Android 13, released on August 15, 2022, is the latest version.[8]

History[edit]

Features[edit]

Interface[edit]

Android's default user interface is mainly based on direct manipulation, 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.[9] Game controllers and full-size physical keyboards are supported via Bluetooth or USB.[10][11] 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 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,[12] or allowing the user to steer a vehicle in a racing game by rotating the device, simulating control of a steering wheel.[13]

Home screen[edit]

Android devices boot to the home screen, the primary navigation and information "hub" on Android devices, analogous to the desktop found on personal computers. Android home screens are typically made up of app icons and widgets; app icons launch the associated app, whereas widgets display live, auto-updating content, such as a weather forecast, the user's email inbox, or a news ticker directly on the home screen.[14] A home screen may be made up of several pages, between which the user can swipe back and forth.[15] Third-party apps available on Google Play and other app stores can extensively re-theme the home screen,[16] and even mimic the look of other operating systems, such as Windows Phone.[17] Most manufacturers customize the look and features of their Android devices to differentiate themselves from their competitors.[18]

Status bar[edit]

Along the top of the screen is a status bar, showing information about the device and its connectivity. This status bar can be pulled (swiped) down from to reveal a notification screen where apps display important information or updates, as well as quick access to system controls and toggles such as display brightness, connectivity settings (WiFi, Bluetooth, cellular data), audio mode, and flashlight.[15] Vendors may implement extended settings such as the ability to adjust the flashlight brightness.[19]

Notifications[edit]

Notifications are "short, timely, and relevant information about your app when it's not in use", and when tapped, users are directed to a screen inside the app relating to the notification.[20] Beginning with Android 4.1 "Jelly Bean", "expandable notifications" allow the user to tap an icon on the notification in order for it to expand and display more information and possible app actions right from the notification.[21]

App lists[edit]

An "All Apps" screen lists all installed applications, with the ability for users to drag an app from the list onto the home screen. The app list may be accessed using a gesture or a button, depending on the Android version. A "Recents" screen, also known as "Overview", lets users switch between recently used apps.[15]

The recent list may appear side-by-side or overlapping, depending on the Android version and manufacturer.[22]

Navigation buttons[edit]

Front buttons (home, menu/options, go back, search) and optical track pad of an HTC Desire, a 2010 smartphone with Android OS

Many early Android OS smartphones were equipped with a dedicated search button for quick access to a web search engine and individual apps' internal search feature. More recent devices typically allow the former through a long press or swipe away from the home button.[23]

The dedicated option key, also known as menu key, and its on-screen simulation, is no longer supported since Android version 10. Google recommends mobile application developers to locate menus within the user interface.[23] On more recent phones, its place is occupied by a task key used to access the list of recently used apps when actuated. Depending on device, its long press may simulate a menu button press or engage split screen view, the latter of which is the default behaviour since stock Android version 7.[24][25][26]

Split-screen view[edit]

Native support for split screen view has been added in stock Android version 7.0 Nougat.[26]

The earliest vendor-customized Android-based smartphones known to have featured a split-screen view mode are the 2012 Samsung Galaxy S3 and Note 2, the former of which received this feature with the premium suite upgrade delivered in TouchWiz with Android 4.1 Jelly Bean.[27]

Charging while powered off[edit]

When connecting or disconnecting charging power and when shortly actuating the power button or home button, all while the device is powered off, a visual battery meter whose appearance varies among vendors appears on the screen, allowing the user to quickly assess the charge status of a powered-off without having to boot it up first. Some display the battery percentage.[28]

Audio-coupled haptic effect[edit]

Since stock Android version 12, released early 2021, synchronous vibration can be set to complement audio.[29][30] Such feature initially existed under the name "Auto Haptic" on the Android-based 2012 Samsung Galaxy S III, released with a vendor-modified (TouchWiz) installation of Android 4.1 Jelly Bean.[31]

Applications[edit]

Many, to almost all, Android devices come with preinstalled Google apps including Gmail, Google Maps, Google Chrome, YouTube, Google Play Music, Google Play Movies & TV, and many more.

Applications ("apps"), which extend the functionality of devices (and must be 64-bit[32]), are written using the Android software development kit (SDK)[33] and, often, Kotlin programming language, which replaced Java as Google's preferred language for Android app development in May 2019,[34] and was originally announced in May 2017.[35][36] Java is still supported (originally the only option for user-space programs, and is often mixed with Kotlin), as is C++.[37] Java or other JVM languages, such as Kotlin, may be combined with C/C++,[38] together with a choice of non-default runtimes that allow better C++ support.[39] The Go programming language is also supported, although with a limited set of application programming interfaces (API).[40]

The SDK includes a comprehensive set of development tools,[41] 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 a framework based on Apache Cordova for porting Chrome HTML 5 web applications to Android, wrapped in a native application shell.[42] Additionally, Firebase was acquired by Google in 2014 that provides helpful tools for app and web developers.[43]

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.[44][45] Google Play Store allows users to browse, download and update applications published by Google and third-party developers; as of January 2021, there are more than three million applications available for Android in Play Store.[7][46] As of July 2013, 50 billion application installations had been performed.[47][48] 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.[49] As of May 2017, there are over one billion active users a month for Gmail, Android, Chrome, Google Play and Maps.

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.[44][50][51][52]

In October 2020, Google removed several Android applications from Play Store, as they were identified breaching its data collection rules. The firm was informed by International Digital Accountability Council (IDAC) that apps for children like Number Coloring, Princess Salon and Cats & Cosplay, with collective downloads of 20 million, were violating Google's policies.[53]

At the Windows 11 announcement event in June 2021, Microsoft showcased the new Windows Subsystem for Android (WSA) that will enable support for the Android Open Source Project (AOSP) and will allow users to run Android apps on their Windows desktop.[54]

Storage[edit]

The storage of Android devices can be expanded using secondary devices such as SD cards. Android recognizes two types of secondary storage: portable storage (which is used by default), and adoptable storage. Portable storage is treated as an external storage device. Adoptable storage, introduced on Android 6.0, allows the internal storage of the device to be spanned with the SD card, treating it as an extension of the internal storage. This has the disadvantage of preventing the memory card from being used with another device unless it is reformatted.[55]

Android 4.4 introduced the Storage Access Framework (SAF), a set of APIs for accessing files on the device's filesystem.[56] As of Android 11, Android has required apps to conform to a data privacy policy known as scoped storage, under which apps may only automatically have access to certain directories (such as those for pictures, music, and video), and app-specific directories they have created themselves. Apps are required to use the SAF to access any other part of the filesystem.[57][58][59]

Memory management[edit]

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.[60][61] 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 the longest amount of time.[62][63] Lifehacker reported in 2011 that third-party task-killer applications were doing more harm than good.[64]

Developer options[edit]

Some settings for use by developers for debugging and power users are located in a "Developer options" sub menu, such as the ability to highlight updating parts of the display, show an overlay with the current status of the touch screen, show touching spots for possible use in screencasting, notify the user of unresponsive background processes with the option to end them ("Show all ANRs", i.e. "App's Not Responding"), prevent a Bluetooth audio client from controlling the system volume ("Disable absolute volume"), and adjust the duration of transition animations or deactivate them completely to speed up navigation.[65][66][67]

Developer options are initially hidden since Android 4.2 "Jelly Bean", but can be enabled by actuating the operating system's build number in the device information seven times. Hiding developers options again requires deleting user data for the "Settings" app, possibly resetting some other preferences.[68][69][70]

Hardware[edit]

The main hardware platform for Android is ARM (the ARMv7 and ARMv8-A architectures), with x86 and x86-64 architectures also officially supported in later versions of Android.[71][72][73] The unofficial Android-x86 project provided support for x86 architectures ahead of the official support.[74][75] Since 2012, Android devices with Intel processors began to appear, including phones[76] and tablets. While gaining support for 64-bit platforms, Android was first made to run on 64-bit x86 and then on ARM64. Since Android 5.0 "Lollipop", 64-bit variants of all platforms are supported in addition to the 32-bit variants.[71] An unofficial experimental port of the operating system to the RISC-V architecture was released in 2021.[77]

Requirements for the minimum amount of RAM for devices running Android 7.1 range from in practice 2 GB for best hardware, down to 1 GB for the most common screen. Android supports all versions of OpenGL ES and Vulkan (and version 1.1 available for some devices[78]).

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.[48] Android used to require an autofocus camera, which was relaxed to a fixed-focus camera[48] 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.[79][80][81][82] 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.[83] Using the Android emulator that is part of the Android SDK, or third-party emulators, Android can also run non-natively on x86 architectures.[84][85] Chinese companies are building a PC and mobile operating system, based on Android, to "compete directly with Microsoft Windows and Google Android".[86] The Chinese Academy of Engineering noted that "more than a dozen" companies were customizing Android following a Chinese ban on the use of Windows 8 on government PCs.[87][88][89]

Development[edit]

The stack of Android Open Source Project

Android is developed by Google until the latest changes and updates are ready to be released, at which point the source code is made available to the Android Open Source Project (AOSP),[90] an open source initiative led by Google.[91] The AOSP code can be found with minimal modifications on select devices, mainly the former Nexus and current Android One series of devices.[92]

The source code is, in turn, customized by original equipment manufacturers (OEMs) to run on their hardware.[93][94] Android's source code does not contain the device drivers, often proprietary, that are needed for certain hardware components.[95] As a result, most Android devices, including Google's own, ship with a combination of free and open source and proprietary software, with the software required for accessing Google services falling into the latter category.[citation needed]

Update schedule[edit]

Google provides annual[96] Android releases, both for factory installation in new devices, and for over-the-air updates to existing devices.[97] The latest major release is Android 13.

The extensive variation of hardware[98] in Android devices has caused significant delays for software upgrades and security patches. Each upgrade has had to be specifically tailored, a time- and resource-consuming process.[99] Except for devices within the Google Nexus and Pixel brands, updates have often arrived months after the release of the new version, or not at all.[100] Manufacturers often prioritize their newest devices and leave old ones behind.[101] Additional delays can be introduced by wireless carriers who, after receiving updates from manufacturers, further customize Android to their needs and conduct extensive testing on their networks before sending out the upgrade.[101][102] There are also situations in which upgrades are impossible due to a manufacturer not updating necessary drivers.[103]

The lack of after-sale support from manufacturers and carriers has been widely criticized by consumer groups and the technology media.[104][105][106] 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,[107] an attitude described as "insulting".[106] The Guardian complained that the method of distribution for updates is complicated only because manufacturers and carriers have designed it that way.[106] 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; however, there has not been another official word about that alliance since its announcement.[101][108]

In 2012, Google began de-coupling certain aspects of the operating system (particularly its central applications) so they could be updated through the Google Play store independently of the OS. One of those components, Google Play Services, is a closed-source system-level process providing APIs for Google services, installed automatically on nearly all devices running Android 2.2 "Froyo" and higher. With these changes, Google can add new system functions and update apps without having to distribute an upgrade to the operating system itself.[109] As a result, Android 4.2 and 4.3 "Jelly Bean" contained relatively fewer user-facing changes, focusing more on minor changes and platform improvements.[110]

HTC's then-executive Jason Mackenzie called monthly security updates "unrealistic" in 2015, and Google was trying to persuade carriers to exclude security patches from the full testing procedures. In May 2016, Bloomberg Businessweek reported that Google was making efforts to keep Android more up-to-date, including accelerated rates of security updates, rolling out technological workarounds, reducing requirements for phone testing, and ranking phone makers in an attempt to "shame" them into better behavior. As stated by Bloomberg: "As smartphones get more capable, complex and hackable, having the latest software work closely with the hardware is increasingly important". Hiroshi Lockheimer, the Android lead, admitted that "It's not an ideal situation", further commenting that the lack of updates is "the weakest link on security on Android". Wireless carriers were described in the report as the "most challenging discussions", due to their slow approval time while testing on their networks, despite some carriers, including Verizon Wireless and Sprint Corporation, already shortening their approval times. In a further effort for persuasion, Google shared a list of top phone makers measured by updated devices with its Android partners, and is considering making the list public.Template:When Mike Chan, co-founder of phone maker Nextbit and former Android developer, said that "The best way to solve this problem is a massive re-architecture of the operating system", "or Google could invest in training manufacturers and carriers 'to be good Android citizens

  1. REDIRECT Template:Single+double.[111][112][113]

In May 2017, with the announcement of Android 8.0, Google introduced Project Treble, a major re-architect of the Android OS framework designed to make it easier, faster, and less costly for manufacturers to update devices to newer versions of Android. Project Treble separates the vendor implementation (device-specific, lower-level software written by silicon manufacturers) from the Android OS framework via a new "vendor interface". In Android 7.0 and earlier, no formal vendor interface exists, so device makers must update large portions of the Android code to move a device to a newer version of the operating system. With Treble, the new stable vendor interface provides access to the hardware-specific parts of Android, enabling device makers to deliver new Android releases simply by updating the Android OS framework, "without any additional work required from the silicon manufacturers."[114]

In September 2017, Google's Project Treble team revealed that, as part of their efforts to improve the security lifecycle of Android devices, Google had managed to get the Linux Foundation to agree to extend the support lifecycle of the Linux Long-Term Support (LTS) kernel branch from the 2 years that it has historically lasted to 6 years for future versions of the LTS kernel, starting with Linux kernel 4.4.[115]

In May 2019, with the announcement of Android 10, Google introduced Project Mainline to simplify and expedite delivery of updates to the Android ecosystem. Project Mainline enables updates to core OS components through the Google Play Store. As a result, important security and performance improvements that previously needed to be part of full OS updates can be downloaded and installed as easily as an app update.[116]

Google reported rolling out new amendments in Android 12 aimed at making the use of third-party application stores easier. This announcement rectified the concerns reported regarding the development of Android apps, including a fight over an alternative in-app payment system and difficulties faced by businesses moving online because of COVID-19.[117]

Linux kernel[edit]

Android's kernel is based on the Linux kernel's long-term support (LTS) branches. As of 2021, Android uses versions 4.14, 4.19 or 5.4 of the Linux kernel.[118] The actual kernel depends on the individual device.[119]

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 device trees, ashmem, ION, and different out of memory (OOM) handling.[120][121] Certain features that Google contributed back to the Linux kernel, notably a power management feature called "wakelocks",[122] were initially rejected by mainline kernel developers partly because they felt that Google did not show any intent to maintain its own code.[123][124] Google announced in April 2010 that they would hire two employees to work with the Linux kernel community,[125] 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.[124] Google engineer Patrick Brady once stated in the company's developer conference that "Android is not Linux",[126] with Computerworld adding that "Let me make it simple for you, without Linux, there is no Android".[127] Ars Technica wrote that "Although Android is built on top of the Linux kernel, the platform has very little in common with the conventional desktop Linux stack".[126]

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".[128] 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.[129] Linux included the autosleep and wakelocks capabilities in the 3.5 kernel, after many previous attempts at a 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).[130] Google maintains a public code repository that contains their experimental work to re-base Android off the latest stable Linux versions.[131][132]

Android is a Linux distribution according to the Linux Foundation,[133] Google's open-source chief Chris DiBona,[134] and several journalists.[135][136] 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 other components typically found in Linux distributions.[137]

With the release of Android Oreo in 2017, Google began to require that devices shipped with new SoCs had Linux kernel version 4.4 or newer, for security reasons. Existing devices upgraded to Oreo, and new products launched with older SoCs, were exempt from this rule.[138][139]

Rooting[edit]

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 typical 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 and customizability of their devices, but also by malicious parties to install viruses and malware.[141] Root access can also be obtained by unlocking the bootloader via the OEM Unlocking option on certain devices including most Google Pixel and OnePlus models. The unlocking process resets the system to factory state, erasing all user data.[142]

Software stack[edit]

Android's architecture diagram Template:Obsolete source

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 Android's other source code projects.

Android uses Android Runtime (ART) as its runtime environment (introduced in version 4.4), 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.[143] In versions no longer supported, until version 5.0 when ART took over, Android previously 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.[144][145][146] For its Java library, the Android platform uses a subset of the now discontinued Apache Harmony project.[147] In December 2015, Google announced that the next version of Android would switch to a Java implementation based on the OpenJDK project.[148]

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

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.[149] A new Bluetooth stack, called Gabeldorsche, was developed to try to fix the bugs in the BlueDroid implementation.[150]

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,[137] until version r5 of the Android Native Development Kit brought support for applications written completely in C or C++.[151] Libraries written in C may also be used in applications by injection of a small shim and usage of the JNI.[152]

In current versions of Android, "Toybox", a collection of command-line utilities (mostly for use by apps, as Android does not provide a command-line interface by default), is used (since the release of Marshmallow) replacing a similar "Toolbox" collection found in previous Android versions.[153]

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."[154]

Open-source community[edit]

Android's source code is released by Google under an open source license, and 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 or bring Android to devices originally shipped with other operating systems.[155] 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;[156] 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.[157] CyanogenMod was the most widely used community firmware,[158] now discontinued and succeeded by LineageOS.[159]

There are, as of August 2019, a handful of notable custom Android distributions (ROMs) of the latest Android version 9.0 Pie, which was released publicly in August 2018. See List of custom Android distributions.

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.[160] Moreover, modified firmware 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,[161] manufacturers and carriers have softened their position regarding third party development, with some, including HTC,[160] Motorola,[162] Samsung[163][164] and Sony,[165] 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.[160] However, despite manufacturer acceptance, some carriers in the US still require that phones are locked down, frustrating developers and customers.[166]

Device codenames[edit]

Internally, Android identifies each supported device by its device codename, a short string,[167] which may or may not be similar to the model name used in marketing the device. For example, the device codename of the Pixel smartphone is sailfish.

The device codename is usually not visible to the end user, but is important for determining compatibility with modified Android versions. It is sometimes also mentioned in articles discussing a device, because it allows to distinguish different hardware variants of a device, even if the manufacturer offers them under the same name. The device codename is available to running applications under android.os.Build.DEVICE.[168]

Security and privacy[edit]

Licensing[edit]

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.[169][170] 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.[171] 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,[172] 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.[173]

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.[45] Custom, certified distributions of Android produced by manufacturers (such as Samsung Experience) may also replace certain stock Android apps with their own proprietary variants and add additional software not included in the stock Android operating system.[44] With the advent of the Google Pixel line of devices, Google itself has also made specific Android features timed or permanent exclusives to the Pixel series.[174][175] There may also be "binary blob" drivers required for certain hardware components in the device.[44][95] The best known fully open source Android services are the LineageOS distribution and MicroG which acts as an open source replacement of Google Play Services.

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 uninstall applications and, as a result, invite non-free software. In both cases, the use of closed-source software causes the system to become vulnerable to backdoors.[176][177]

It has been argued that because developers are often required to purchase the Google-branded Android license, this has turned the theoretically open system into a freemium service.[178]<span title="Script error: No such module "DecodeEncode".">: 20 

Leverage over manufacturers[edit]

Google licenses their Google Mobile Services software, along with the Android trademarks, only to hardware manufacturers for devices that meet Google's compatibility standards specified in the Android Compatibility Program document.[179] 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.[44] A prominent example of such an Android fork is Amazon's Fire OS, which is used on the Kindle Fire line of tablets, and oriented toward Amazon services.[44] The shipment of Android devices without GMS is also common in mainland China, as Google does not do business there.[180][181][182]

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.[45] Google has also enforced preferential bundling and placement of Google Mobile Services on devices, including mandated bundling of the entire main suite of Google applications, mandatory placement of shortcuts to Google Search and the Play Store app on or near the main home screen page in its default configuration,[183] and granting a larger share of search revenue to OEMs who agree to not include third-party app stores on their devices.[184] In March 2018, it was reported that Google had begun to block "uncertified" Android devices from using Google Mobile Services software, and display a warning indicating that "the device manufacturer has preloaded Google apps and services without certification from Google". Users of custom ROMs can register their device ID to their Google account to remove this block.[185]

Some stock applications and components in AOSP code that were formerly used by earlier versions of Android, such as Search, Music, Calendar, and the location API, were abandoned by Google in favor of non-free replacements distributed through Play Store (Google Search, Google Play Music, and Google Calendar) and Google Play Services, which are no longer open-source. Moreover, open-source variants of some applications also exclude functions that are present in their non-free versions.[44][186][187][188] These measures are likely intended to discourage forks and encourage commercial licensing in line with Google requirements, as the majority of the operating system's core functionality is dependent on proprietary components licensed exclusively by Google, and it would take significant development resources to develop an alternative suite of software and APIs to replicate or replace them. Apps that do not use Google components would also be at a functional disadvantage, as they can only use APIs contained within the OS itself. In turn, third-party apps may have dependencies on Google Play Services.[189]

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;[44][190] 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.[191][192][193]

Reception[edit]

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.[194] The idea of an open-source, Linux-based development platform sparked interest,[195] 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.[196] These established players were skeptical: Nokia was quoted as saying "we don't see this as a threat", and a member of Microsoft's Windows Mobile team stated "I don't understand the impact that they are going to have."[197]

Since then Android has grown to become the most widely used smartphone operating system[198][199] and "one of the fastest mobile experiences available".[200] 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),[201] 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.[198] 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.[198][202]

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.[203] 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.[44] 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.[45]

Android has suffered from "fragmentation",[204] 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 devices, numerous 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.[205] 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.[206] 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.[205]

Market share[edit]

Android is the most used operating system on phones in virtually all countries, with some countries, such as India, having over 96% market share.[207] On tablets, usage is more even, as iOS is a bit more popular globally.

Research company Canalys estimated in the second quarter of 2009, that Android had a 2.8% share of worldwide smartphone shipments.[208] By May 2010, Android had a 10% worldwide smartphone market share, overtaking Windows Mobile,[209] whilst in the US Android held a 28% share, overtaking iPhone OS.[210] By the fourth quarter of 2010, its worldwide share had grown to 33% of the market becoming the top-selling smartphone platform,[211] overtaking Symbian.[212] In the US it became the top-selling platform in April 2011, overtaking BlackBerry OS with a 31.2% smartphone share, according to comScore.[213]

By the third quarter of 2011, Gartner estimated that more than half (52.5%) of the smartphone sales belonged to Android.[214] By the third quarter of 2012 Android had a 75% share of the global smartphone market according to the research firm IDC.[215]

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

Android market share varies by location. In July 2012, "mobile subscribers aged 13+" in the United States using Android were up to 52%,[222] and rose to 90% in China.[223] During the third quarter of 2012, Android's worldwide smartphone shipment market share was 75%,[215] with 750 million devices activated in total. In April 2013, Android had 1.5 million activations per day.[220] As of May 2013, 48 billion application ("app") installation have been performed from the Google Play store,[224] and by September 2013, one billion Android devices had been activated.[225]

As of August 2020, the Google Play store had over 3 million Android applications published,[7][226] and as of May 2016, apps had been downloaded more than 65 billion times.[227] The operating system's success has made it a target for patent litigation as part of the so-called "smartphone wars" between technology companies.[228][229]

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).[230] At the end of 2013, over 1.5 billion Android smartphones had been sold in the four years since 2010,[231][232] making Android the most sold phone and tablet OS. Three billion Android smartphones were 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.[233] In 2013, it outsold Windows 2.8:1 or by 573 million.[234][235][236] As of 2015, Android has the largest installed base of all operating systems;[237] Since 2013, devices running it also sell more than Windows, iOS and Mac OS X devices combined.[238]

According to StatCounter, which tracks only the use for browsing the web, Android is the most popular mobile operating system since August 2013.[239] 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",[240] 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).[241][242]

While Android phones in the Western world almost always include Google's proprietary code (such as Google Play) in the otherwise open-source operating system, Google's proprietary code and trademark is increasingly not used in emerging markets; "The growth of AOSP Android devices goes way beyond just China [..] 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 AOSP source code, forgoing the Android trademark: Thailand (44%), Philippines (38%), Indonesia (31%), India (21%), Malaysia (24%), Mexico (18%), Brazil (9%).[243]

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.[244] Describing the statistics, Farhad Manjoo wrote in The New York Times that "About one of every two computers sold today is running Android. [It] has become Earth's dominant computing platform."[237]

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.[245][246][lower-alpha 1] Android has the largest installed base of any mobile operating system and, since 2013, the highest-selling operating system overall[234][238][248][249][250] with sales in 2012, 2013 and 2014[251] close to the installed base of all PCs.[252]

In the second quarter of 2014, Android's share of the global smartphone shipment market was 84.7%, a new record.[253][254] This had grown to 87.5% worldwide market share by the third quarter of 2016,[255] leaving main competitor iOS with 12.1% market share.[256]

According to an April 2017 StatCounter report, Android overtook Microsoft Windows to become the most popular operating system for total Internet usage.[257][258] It has maintained the plurality since then.[259]

In September 2015, Google announced that Android had 1.4 billion monthly active users.[260][261] This changed to 2 billion monthly active users in May 2017.[262][263]

Adoption on tablets[edit]

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

Despite its success on smartphones, initially Android tablet adoption was slow,[264] then later caught up with the iPad, in most countries. 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.[265][266] 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.[266][267]

Despite app support in its infancy, a considerable number of Android tablets, like the Barnes & Noble Nook (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.[266] 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.[268][269] 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.[266][270]

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.[271] According to International Data Corporation, shipments of Android-powered tablets surpassed iPads in Q3 2012.[272]

Barnes & Noble Nook running Android

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

According to StatCounter's web use statistics, as of 2020, Android tablets represent the majority of tablet devices used in Africa (70%), South America (65%), while less than half elsewhere, e.g. Europe (44%), Asia (44%), North America (34%) and Oceania/Australia (18%). There are countries on all continents where Android tablets are the majority, for example, Mexico.[276]

In March 2016, Galen Gruman of InfoWorld stated that Android devices could 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".[277] A year earlier, Gruman had stated that Microsoft's own mobile Office apps were "better on iOS and Android" than on Microsoft's own Windows 10 devices.[278]

Platform information[edit]

Android 11 is, and was just before the release of Android 12, the most popular Android version, on both smartphones and tablets.

As of May 2022, Android 11 is most popular on smartphones at 35%,[279] with Android 10 2nd at 24%, then Android 12 at 12%. Usage of Android 10 and newer, i.e. supported versions, is at 71%, the rest of users are not supported with security updates. Android 12 is most popular in a few countries including the United States,[280] but Android 11 is most used in most countries, including India, while in many others, including China, Android 10 is the most popular version.[281]

On tablets, Android 11 is most popular at 27%[282][283] overtaking Android 9.0 Pie in July 2021, which is now second at 16% (topped out at over 20%).[284] Usage of Android 10 and newer, i.e. supported versions, is at 34% on Android tablets, with Pie 9.O, until recently supported, at 50.4%. The usage share varies a lot by country: e.g. Android 9.0 Pie is the version with the greatest usage share in the United States (also in the UK) at 34%, while Android 11 is also very popular e.g. most used in India, Canada, Australia, and most European countries, and others all over the world; Oreo 8.1 most used in China.[285]

Version Marketing name Release date API level Kernel Runtime Launched with
13 33 5.x ART Pixel 4, Pixel 4 XL, Pixel 5, Pixel 5a, Pixel 6, Pixel 6 Pro, Asus ZenFone 8, Lenovo P12 Pro, OnePlus 10 Pro, Oppo Find X5 Pro, Vivo X80 Pro, Realme GT2 Pro, Xiaomi 12, Xiaomi 12 Pro, Xiaomi Pad 5, Redmi K50 Pro, Sharp AQUOS sense6, Tecno Camon 19 Pro, ZTE Axon 40 Ultra[286]
12L 12 March 7, 2022 32 5.x ART Pixel 3, Pixel 3 XL, Pixel 3a, Pixel 3a XL, Pixel 4, Pixel 4 XL, Pixel 4a, Pixel 5, Pixel 5a
12 Template:Dts 31 5.x ART Pixel 3, Pixel 3 XL, Pixel 3a, Pixel 3a XL, Pixel 4, Pixel 4 XL, Pixel 5, Pixel 6, Pixel 6 Pro, Asus ZenFone 8, Nokia X20, OnePlus 9, OnePlus 9 Pro, Oppo Find X3 Pro, iQOO 7 Legend, Realme GT,[287] TCL 20 Pro 5G, Xiaomi Mi 11, Xiaomi Mi 11 Ultra, Xiaomi Mi 11i/Mi 11X Pro,[288] Tecno Camon 17, ZTE Axon 30 Ultra
11 11 Template:Dts 30 5.x ART Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL, Pixel 3a, Pixel 3a XL, Pixel 4, Pixel 4 XL,[289] OnePlus 8, OnePlus 8 Pro, Oppo Find X2, Oppo Find X2 Pro, Vivo NEX 3S, Xiaomi Mi 10, Xiaomi Mi 10 Pro, POCO F2 Pro,[290] Realme X50 Pro, Sharp AQUOS Zero 2
10 10 Template:Dts 29 5.x ART Asus ZenFone 5Z, Essential Phone, Pixel, Pixel XL, Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL, Pixel 3a, Pixel 3a XL, OnePlus 6, OnePlus 6T, OnePlus 7, OnePlus 7 Pro, Oppo Reno, Sony Xperia XZ3, Vivo X27, Vivo NEX S, Vivo NEX A, Xiaomi Mi MIX 3 5G, Xiaomi Mi 9, Tecno Spark 3 Pro, Huawei Mate 20 Pro, LG G8, Nokia 8.1, Realme 3 Pro[291]
9 Pie Template:Dts 28 4.x ART Essential Phone, Pixel, Pixel XL, Pixel 2, Pixel 2 XL, Nokia 7 Plus, OnePlus 6, Oppo R15 Pro, Sony Xperia XZ2, Vivo X21UD, Vivo X21, Xiaomi Mi Mix 2S[292]
8.1 Oreo Template:Dts 27 4.x ART Pixel, Pixel XL, Nexus 6P, Nexus 5X
8.0 Template:Dts 26 4.x ART
7.1 Nougat Template:Dts 25 4.x ART Pixel, Pixel XL
7.0 Template:Dts 24 4.x ART Nexus 5X, Nexus 6P, LG V20
6.0 Marshmallow Template:Dts 23 4.x ART Nexus 5X, Nexus 6P
5.1 Lollipop Template:Dts 22 3.x ART Android One
5.0 Template:Dts 21 3.x ART 2.1.0 Nexus 6, Nexus 9
4.4 KitKat Template:Dts 19 3.x Dalvik (and ART 1.6.0) Nexus 5
4.3 Jelly Bean Template:Dts 18 3.x Dalvik Nexus 7 2013
4.2 Template:Dts 17 3.x Dalvik Nexus 4, Nexus 10
4.1 Template:Dts 16 3.x Dalvik Nexus 7
4.0 Ice Cream Sandwich Template:Dts 15 3.x Dalvik Galaxy Nexus
2.3 Gingerbread Template:Dts 10 2.6.32 Dalvik 1.4.0 Nexus S

As of July 2021, 66% of devices have Vulkan support (47% on newer Vulkan 1.1),[293] the successor to OpenGL. At the same time 91.5% of the devices have support for OpenGL ES 3.0 or higher (in addition, the rest of devices, 8.50%, use version 2.0), with 73.50% using the latest version OpenGL ES 3.2.

Application piracy[edit]

In general, paid Android applications can easily be pirated.[294] 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.[295] 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.[296]

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.[297] 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.[298][299]

Legal issues[edit]

The success of Android has made it a target for patent and copyright litigation between technology companies, both Android and Android phone manufacturers having been involved in numerous patent lawsuits and other legal challenges.

Patent lawsuit with Oracle[edit]

On August 12, 2010, Oracle sued Google over claimed infringement of copyrights and patents related to the Java programming language.[300] Oracle originally sought damages up to $6.1 billion,[301] but this valuation was rejected by a United States federal judge who asked Oracle to revise the estimate.[302] 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.[303] 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.[304][305] The parties agreed to zero dollars in statutory damages for a small amount of copied code.[306] 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.[307][308]

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.[147] In its announcement, Google claimed this was part of an effort to create a "common code base" between Java on Android and other platforms.[148] 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".[147] In June 2016, a United States federal court ruled in favor of Google, stating that its use of the APIs was fair use.[309]

In April 2021, the United Supreme Court ruled that Google's use of the Java APIs was within the bounds of fair use, reversing the Federal Circuit Appeals Court ruling and remanding the case for further hearing. The majority opinion began with the assumption that the APIs may be copyrightable, and thus proceeded with a review of the factors that contributed to fair use.[310]

Anti-competitive challenges in Europe[edit]

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.[311] 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.[312] In August 2016, Google was fined US$6.75 million by the Russian Federal Antimonopoly Service (FAS) under similar allegations by Yandex.[313] The European Commission issued its decision on July 18, 2018, determining that Google had conducted three operations related to Android that were in violation of antitrust regulations: bundling Google's search and Chrome as part of Android, blocking phone manufacturers from using forked versions of Android, and establishing deals with phone manufacturers and network providers to exclusively bundle the Google search application on handsets (a practice Google ended by 2014). The EU fined Google for Template:€ (about Template:USD) and required the company to end this conduct within 90 days.[314] Google filed its appeal of the ruling in October 2018, though will not ask for any interim measures to delay the onset of conduct requirements.[315]

On October 16, 2018, Google announced that it would change its distribution model for Google Mobile Services in the EU, since part of its revenues streams for Android which came through use of Google Search and Chrome were now prohibited by the EU's ruling. While the core Android system remains free, OEMs in Europe would be required to purchase a paid license to the core suite of Google applications, such as Gmail, Google Maps and the Google Play Store. Google Search will be licensed separately, with an option to include Google Chrome at no additional cost atop Search. European OEMs can bundle third-party alternatives on phones and devices sold to customers, if they so choose. OEMs will no longer be barred from selling any device running incompatible versions of Android in Europe.[316]

Others[edit]

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.[317] 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 January 2012, Microsoft said they had signed patent license agreements with eleven Android device manufacturers, whose products account for "70 percent of all Android smartphones" sold in the US[318] and 55% of the worldwide revenue for Android devices.[319] These include Samsung and HTC.[320] 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.[317] 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.[321][322]

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.[323] In August 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.[324][325] In December 2011, Google bought over a thousand patents from IBM.[326]

Turkey's competition authority investigations about default search engine in Android, started in 2017, led to a US$17.4 million fine in September 2018 and a fine of 0.05 percent of Google's revenue per day in November 2019 when Google didn't meet the requirements.[327] In December 2019, Google stopped issuing licenses for new Android phone models sold in Turkey.[327]

Other uses[edit]

Ouya, a video game console which runs Android

Google has developed several variations of Android for specific use cases, including Android Wear, later renamed Wear OS, for wearable devices such as wrist watches,[328][329] Android TV for televisions,[330][331] Android Things for smart or Internet of things devices and Android Automotive for cars.[332][333] Additionally, by providing infrastructure that combines dedicated hardware and dedicated applications running on regular Android, Google have opened up the platform for its use in particular usage scenarios, such as the Android Auto app for cars,[334][335] and Daydream, a Virtual Reality platform.[336]

The open and customizable nature of Android allows device makers to use it on other electronics as well, including laptops, netbooks,[337][338] and desktop computers,[339] cameras,[340] headphones,[341] home automation systems, game consoles,[342] media players,[343] satellites,[344] routers,[345] printers,[346] payment terminals,[347] automated teller machines,[348] and robots.[349] Additionally, Android has been installed and run on a variety of less-technical objects, including calculators,[350] single-board computers,[351] feature phones,[352] electronic dictionaries,[353] alarm clocks,[354] refrigerators,[355] landline telephones,[356] coffee machines,[357] bicycles,[358] and mirrors.[342]

Ouya, a video game console running Android, became one of the most successful Kickstarter campaigns, crowdfunding US$8.5m for its development,[359][360] 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.[361]

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.[362] 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.[363][364]

Android-x86 running on an ASUS Eee PC netbook

Parrot unveiled an Android-based car stereo system known as Asteroid in 2011,[365] followed by a successor, the touchscreen-based Asteroid Smart, in 2012.[366] In 2013, Clarion released its own Android-based car stereo, the AX1.[367] 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."[368]

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.[369][370] On those platforms Android provides additional functionality for physical keyboards[371] 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.[372]

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.[373][374] 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."[373] Also, back in 2009, Google co-founder Sergey Brin himself said that Chrome OS and Android would "likely converge over time."[375] 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".[376] That is unlike Android where support is shorter with "EOL dates [being..] at least 3 years [into the future] for Android tablets for education".[377]

At Google I/O in 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.[336] 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.

Mascot[edit]

Android robot logo
A giant Android mascot at Googleplex in 2008

The mascot of Android is a green android robot, as related to the software's name. Although it has no official name, the Android team at Google reportedly call it "Bugdroid".[378]

It was designed by then-Google graphic designer Irina Blok on November 5, 2007, when Android was announced. Contrary to reports that she was tasked with a project to create an icon,[379] Blok confirmed in an interview that she independently developed it and made it open source. The robot design was initially not presented to Google, but it quickly became commonplace in the Android development team, with various variations of it created by the developers there who liked the figure, as it was free under a Creative Commons license.[380][381] Its popularity amongst the development team eventually led to Google adopting it as an official icon as part of the Android logo when it launched to consumers in 2008.

See also[edit]

References[edit]

Explanatory notes[edit]

  1. To put the Statistica's numbers in context: by Strategy Analytics estimates, Windows the most popular "desktop" operating system, was estimated to have an installed base of about 1.3 billion at best;[247] 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.

Citations[edit]

  1. "Is Android Really Open Source? And Does It Even Matter?". MakeUseOf. March 28, 2016.
  2. "Android – Google Mobile Services". Android. Retrieved October 21, 2018. While the Android Open Source Project (AOSP) provides common, device-level functionalities such as email and calling, GMS is not part of AOSP. GMS is only available through a license with Google [..] We ask GMS partners to pass a simple compatibility test and adhere to our compatibility requirements for their Android devices.
  3. Hughes, Terry (July 28, 2014). "Google and Android Are Not the Same... and That's a Good Thing". App Developer Magazine. Retrieved July 29, 2020.
  4. "Frequently Asked Questions". Android Open Source Project. Retrieved January 4, 2021.
  5. Simon, Michael (December 26, 2016). "With Cyanogen dead, Google's control over Android is tighter than ever". www.greenbot.com. Retrieved January 4, 2021.
  6. Cranz, Alex (May 18, 2021). "There are over 3 billion active Android devices". The Verge. Retrieved March 24, 2022.
  7. 7.0 7.1 7.2 "Number of Android applications on the Google Play store". AppBrain. Retrieved August 12, 2020.
  8. "Android 13 is in AOSP!".
  9. "Touch Devices". Android Open Source Project. Archived from the original on January 25, 2012. Retrieved March 12, 2017.
  10. "Handling Controller Actions". Android Developers. Archived from the original on March 12, 2017. Retrieved March 12, 2017.
  11. "Handling Keyboard Input". Android Developers. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
  12. "Sensors Overview". Android Developers. Archived from the original on February 16, 2017. Retrieved March 12, 2017.
  13. Chavez, Chris (December 22, 2011). "Real Racing 2 Speeds Into The Android Market – Leaves Part 1 In The Dust". Phandroid. Archived from the original on February 19, 2017. Retrieved March 12, 2017.
  14. "Widgets". Android Developers. Archived from the original on March 12, 2017. Retrieved March 12, 2017.
  15. 15.0 15.1 15.2 "Phones & Tablets". Android Developers. Archived from the original on March 31, 2017. Retrieved March 12, 2017.
  16. Hindy, Joe (February 4, 2017). "15 best Android launcher apps of 2017". Android Authority. Archived from the original on May 1, 2017. Retrieved March 12, 2017.
  17. Gordon, Whitson (May 20, 2011). "Launcher 7 Brings Windows Phone's Simple, Attractive Interface to Android". Lifehacker. Univision Communications. Archived from the original on January 8, 2017. Retrieved March 12, 2017.
  18. Begun, Daniel A. "Looking at the Android operating system". For Dummies. Archived from the original on March 12, 2017. Retrieved March 12, 2017.
  19. "Nougat Tip: Change the intensity of the flashlight on your Galaxy S7 or S7 edge". SamMobile.
  20. "Notifications". Material Design. Archived from the original on March 22, 2017. Retrieved March 12, 2017.
  21. "Notifications". Material Design. Archived from the original on December 8, 2012. Retrieved March 12, 2017.
  22. "How to Get Android P's New 'Recent Apps' Layout for Your Samsung Smartphone". Lifehacker. June 25, 2018.
  23. 23.0 23.1 Corbin Davenport (November 13, 2019). "The menu navigation button has finally been retired in Android 10".
  24. "How to use the Hidden Menu Key in Samsung Galaxy S5 [with Recent Key]". Android Advices. April 17, 2014.
  25. "The Samsung Galaxy S5 still has a menu button, it's just hidden". Android Central. April 12, 2014.
  26. 26.0 26.1 Ghani, Uzair (August 29, 2016). "How To Use And Master Android 7.0 Nougat Split-Screen Multitasking". Wccftech.
  27. Reisinger, Don (December 7, 2012). "Samsung's Galaxy S3 to get Premium Suite upgrade". CNET. Retrieved April 3, 2021.
  28. "How to change offline charging animation for Android devices". Appuals.com. December 10, 2015.
  29. "Check Out Android 12's Audio-Coupled Haptic Effect In Action". Android Headlines. February 23, 2021.
  30. "Android 12's audio-coupled haptic effect is even cooler than it sounds". xda-developers. February 23, 2021.
  31. "What is Auto-Haptic feature in Jelly Bean 4.1 based Samsung Smartphones? | Support | SAMSUNG UK (mirror)". skp.samsungcsportal.com. Archived from the original on April 3, 2021. Retrieved April 3, 2021.
  32. "Get your apps ready for the 64-bit requirement". Android Developers Blog. Retrieved August 14, 2020.
  33. Mullis, Alex (November 21, 2016). "How to install the Android SDK (Software Development Kit)". Android Authority. Archived from the original on May 3, 2017. Retrieved March 12, 2017.
  34. "Kotlin is now Google's preferred language for Android app development". TechCrunch. Retrieved May 8, 2019.
  35. Miller, Paul (May 17, 2017). "Google is adding Kotlin as an official programming language for Android development". The Verge. Vox Media. Archived from the original on May 17, 2017. Retrieved May 22, 2017.
  36. Lardinois, Frederic (May 17, 2017). "Google makes Kotlin a first-class language for writing Android apps". TechCrunch. AOL. Archived from the original on May 22, 2017. Retrieved May 22, 2017.
  37. Sinicki, Adam (August 10, 2019). "I want to develop Android Apps—What languages should I learn?". Android Authority. Retrieved September 12, 2019.
  38. "Android NDK Native APIs". Android Developers. Archived from the original on March 12, 2017. Retrieved March 12, 2017.
  39. "C++ Library Support". Android Developers. Archived from the original on March 12, 2017. Retrieved March 12, 2017.
  40. "package app". GoDoc. Archived from the original on March 29, 2017. Retrieved March 12, 2017.
  41. "Tools Overview". Android Developers. July 21, 2009. Archived from the original on June 13, 2012.
  42. Opam, Kwame (January 28, 2014). "Chrome Apps are coming to iOS and Android". The Verge. Vox Media. Archived from the original on February 10, 2017. Retrieved March 11, 2017.
  43. "Google Acquires Firebase To Help Developers Build Better Real-Time Apps". TechCrunch. Retrieved April 25, 2020.
  44. 44.0 44.1 44.2 44.3 44.4 44.5 44.6 44.7 44.8 Amadeo, Ron (October 21, 2013). "Google's iron grip on Android: Controlling open source by any means necessary". Ars Technica. Condé Nast. Archived from the original on March 10, 2017. Retrieved March 11, 2017.
  45. 45.0 45.1 45.2 45.3 "Google mandates 'Powered by Android' branding on new devices". Geek.com. Archived from the original on March 28, 2014. Retrieved March 28, 2014.
  46. "Google Play Hits 1 Million Apps". Mashable. July 24, 2013. Archived from the original on January 2, 2014. Retrieved January 2, 2014.
  47. Warren, Christina (July 24, 2013). "Google Play Hits 1 Million Apps". Mashable. Archived from the original on May 30, 2014. Retrieved June 4, 2014.
  48. 48.0 48.1 48.2 "Android Compatibility". Android Developers. Archived from the original on October 17, 2013. Retrieved November 16, 2013.
  49. Chu, Eric (April 13, 2011). "Android Developers Blog: New Carrier Billing Options on Android Market". android-developers.blogspot.com. Archived from the original on June 28, 2011. Retrieved May 15, 2011.
  50. Ganapati, Priya (June 11, 2010). "Independent App Stores Take On Google's Android Market". Wired News. Archived from the original on February 23, 2012. Retrieved February 20, 2012.
  51. Amadeo, Ron (July 29, 2014). "The great Ars experiment—free and open source software on a smartphone?!". Ars Technica. Condé Nast. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
  52. Hutchinson, Lee (March 14, 2013). "Google evicts ad-blocking software from Google Play store". Ars Technica. Condé Nast. Archived from the original on February 10, 2017. Retrieved March 11, 2017.
  53. "Android apps for children were actually stealing user data". TechRadar. October 26, 2020. Retrieved October 26, 2020.
  54. Parmar, Mayank (June 27, 2021). "Microsoft confirms Android apps will run on all Windows 11 PCs". Windows Latest. Retrieved June 28, 2021.
  55. Amadeo, Ron (October 5, 2015). "Android 6.0 Marshmallow, thoroughly reviewed". Ars Technica. Condé Nast. Retrieved March 6, 2017.
  56. Ho, Joshua. "Examining MicroSD changes in Android 4.4". Anandtech. Retrieved March 28, 2014.
  57. "Behavior changes: Apps targeting Android 11". Android Developers. Retrieved August 18, 2020.
  58. "Android Q Scoped Storage: Best Practices and Updates". Android Developers Blog. Retrieved August 15, 2019.
  59. "Android Q privacy change: Scoped storage". Android Developers. Archived from the original on July 11, 2019. Retrieved August 15, 2019.
  60. "The truth about Android task killers and why you don't need them". PhoneDog. June 26, 2011. Archived from the original on October 23, 2012. Retrieved October 30, 2012.
  61. Victor Matos (September 9, 2013). "Lesson 3: Android Application's Life Cycle" (PDF). grail.cba.csuohio.edu. Cleveland State University. Archived from the original (PDF) on February 22, 2014. Retrieved April 15, 2014.
  62. "Android PSA: Stop Using Task Killer Apps". Phandroid.com. June 16, 2011. Archived from the original on February 17, 2013. Retrieved October 30, 2012.
  63. Reto Meier (2012). Professional Android 4 Application Development. John Wiley & Sons. ISBN 978-1-118-23722-9. Archived from the original on January 21, 2016.
  64. "Updates". Lifehacker.com. November 28, 2011. Archived from the original on November 5, 2012. Retrieved November 2, 2012.
  65. "Your phone's dev options, explained". Android Central. September 22, 2014. Retrieved June 13, 2021.
  66. "How To Increase Bluetooth Headset Volume For Your Phone". thedroidguy.com.
  67. Summerson, Cameron (December 15, 2017). "How to Speed Up Animations to Make Android Feel Faster". How-To Geek. Retrieved June 13, 2021.
  68. "Turn Off Developer Options on Android Devices - Tutorial". DroidViews. December 29, 2018. Retrieved June 13, 2021.
  69. Duino, Justin (June 11, 2017). "How to hide Android's Developer options". 9to5Google. Retrieved June 13, 2021.
  70. Cipriani, Jason. "Restore the Developer Options menu in Android 4.2". CNET. Retrieved June 13, 2021.
  71. 71.0 71.1 "Android Lollipop". Android Developers. Archived from the original on January 30, 2017. Retrieved March 11, 2017.
  72. "Support for 64-bit x86". Android Developers. Archived from the original on March 6, 2017. Retrieved March 11, 2017.
  73. "NDK Revision History". Android Developers. Retrieved July 17, 2018.
  74. Shah, Agam (December 1, 2011). "Google's Android 4.0 ported to x86 processors". Computerworld. International Data Group. Archived from the original on January 24, 2012. Retrieved March 11, 2017.
  75. "Android on Intel Architecture". 01.org. July 11, 2013. Archived from the original on February 9, 2014. Retrieved February 9, 2014.
  76. Warman, Matt (June 7, 2012). "Orange San Diego Intel Android mobile phone review". The Daily Telegraph. Archived from the original on January 10, 2022. Retrieved June 19, 2013.
  77. "Android has been ported to a RISC-V board". xda-developers. January 21, 2021. Retrieved January 25, 2021.
  78. "Vulkan on Android". NVIDIA Developer. February 10, 2016. Archived from the original on January 23, 2018. Retrieved March 21, 2018. Vulkan 1.1 is available as a Developer Preview OTA for the NVIDIA SHIELD TV.
  79. "Lenovo N308 Desktop specs". PCWorld. May 8, 2014. Archived from the original on October 28, 2014. Retrieved November 1, 2014.
  80. "Remix OS for PC". Archived from the original on September 27, 2017. Retrieved September 22, 2017. Now powered by Android Marshmallow.
  81. Michael Brown (May 8, 2014). "Three Android all-in-one PCs reviewed". PCWorld. Archived from the original on October 28, 2014. Retrieved November 1, 2014.
  82. Shawn Knight. "Acer TA272 HUL Android All-in-One Review". TechSpot. Archived from the original on October 28, 2014. Retrieved November 1, 2014.
  83. "ReleaseNote 4.4-r1 – Android-x86 – Porting Android to x86". Archived from the original on October 28, 2014. Retrieved November 1, 2014.
  84. "4 Ways to Run Android on Your PC and Make Your Own "Dual OS" System". Howtogeek.com. January 13, 2014. Archived from the original on April 7, 2014. Retrieved April 7, 2014.
  85. Brad Chacos (September 6, 2013). "Hybrid hijinks: How to install Android on your PC". PCWorld. Archived from the original on April 7, 2014. Retrieved April 7, 2014.
  86. Jose Pagliery (August 25, 2014). "China ditching Windows and Android for its own operating system". CNNMoney. Archived from the original on October 28, 2014. Retrieved November 1, 2014.
  87. "BBC News – China plans new PC operating system in October". BBC News. August 25, 2014. Archived from the original on November 12, 2014. Retrieved November 1, 2014.
  88. Paul Mozur (March 5, 2013). "China Criticizes Android's Dominance". WSJ. Retrieved November 1, 2014.
  89. "China targets own operating system to take on likes of Microsoft, Google". Reuters. August 24, 2014. Archived from the original on October 28, 2014. Retrieved November 1, 2014.
  90. "Welcome to the Android Open Source Project!". Android Source. Archived from the original on March 12, 2017. Retrieved March 13, 2017.
  91. "Android Open Source Project". Archived from the original on December 22, 2017. Retrieved December 22, 2017.
  92. La, Lynn; Bennett, Brian (November 14, 2014). "Powerful, pure Android handsets (roundup)". CNET. CBS Interactive. Archived from the original on March 14, 2017. Retrieved March 13, 2017.
  93. Lawler, Richard (July 9, 2012). "Android 4.1 Jelly Bean source code now available". Engadget. AOL. Archived from the original on March 14, 2017. Retrieved March 13, 2017.
  94. McCann, John (July 10, 2012). "Android 4.1 Jelly Bean source code released". TechRadar. Future plc. Archived from the original on July 13, 2012. Retrieved March 13, 2017.
  95. 95.0 95.1 "Building for devices". Android Open Source Project. Archived from the original on January 7, 2012. Retrieved March 13, 2017.
  96. K., Peter (May 27, 2015). "We'll get a major Android release every year from now on: Android M tomorrow, Android N in 2016". PhoneArena. Archived from the original on March 13, 2017. Retrieved March 13, 2017.
  97. "OTA Updates". Android Source. Archived from the original on December 25, 2016. Retrieved March 13, 2017.
  98. Johnston, Casey (May 16, 2012). "Android fragmentation: one developer encounters 3,997 devices". Ars Technica. Condé Nast. Archived from the original on March 14, 2017. Retrieved March 13, 2017.
  99. Dobie, Alex (January 18, 2014). "Solving the impossible problem of Android updates". Android Central. Mobile Nations. Archived from the original on March 3, 2017. Retrieved March 13, 2017.
  100. Villas-Boas, Antonio (September 14, 2016). "The latest Android delay is why I'm sticking to iPhone". Business Insider. Axel Springer SE. Archived from the original on March 14, 2017. Retrieved March 13, 2017.
  101. 101.0 101.1 101.2 Cunningham, Andrew (June 28, 2011). "What happened to the Android Update Alliance?". Ars Technica. Condé Nast. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
  102. Hoffman, Chris (May 25, 2013). "Why Do Carriers Delay Updates for Android But Not iPhone?". How-To Keep. Archived from the original on March 12, 2017. Retrieved March 13, 2017.
  103. Cunningham, Andrew (August 31, 2016). "Why isn't your old phone getting Nougat? There's blame enough to go around". Ars Technica. Condé Nast. Archived from the original on April 3, 2017. Retrieved April 3, 2017.
  104. Ganapati, Priya (March 15, 2010). "New Phones Still Sold With Old Versions of Android". Wired. Condé Nast. Archived from the original on March 14, 2017. Retrieved March 13, 2017.
  105. cwalters (March 15, 2010). "Make Sure You Know Which Version Of Android Is On That Phone Before Buying It". Consumerist. Consumer Reports. Archived from the original on June 14, 2017. Retrieved March 13, 2017.
  106. 106.0 106.1 106.2 Gillmor, Dan (October 28, 2012). "Android's smartphone OS upgrade issues need more than a quick fix". The Guardian. Archived from the original on March 14, 2017. Retrieved March 13, 2017.
  107. Leyden, John (November 22, 2011). "Security takes a backseat on Android in update shambles". The Register. Situation Publishing. Archived from the original on March 14, 2017. Retrieved March 13, 2017.
  108. Raphael, JR (February 13, 2014). "It's time to rethink the Android upgrade standard". Computerworld. International Data Group. Archived from the original on February 13, 2017. Retrieved March 13, 2017.
  109. Amadeo, Ron (September 3, 2013). "Balky carriers and slow OEMs step aside: Google is defragging Android". Ars Technica. Condé Nast. Archived from the original on September 3, 2013. Retrieved March 11, 2017.
  110. Cunningham, Andrew (August 9, 2013). "Review: Android 4.3's multitude of minor changes future-proofs the platform". Ars Technica. Condé Nast. Archived from the original on March 14, 2017. Retrieved March 13, 2017.
  111. Clark, Jack; Moritz, Scott (May 25, 2016). "Google Steps Up Pressure on Partners Tardy in Updating Android". Bloomberg L.P. Archived from the original on March 30, 2017. Retrieved March 15, 2017.
  112. Amadeo, Ron (May 26, 2016). "Google's making a list: Android OEMs to be ranked, shamed by update speed". Ars Technica. Condé Nast. Archived from the original on March 16, 2017. Retrieved March 15, 2017.
  113. Li, Abner (May 25, 2016). "Report: Google pressuring OEMs and carriers to speed up Android updates, security patches". 9to5Google. Archived from the original on March 16, 2017. Retrieved March 15, 2017.
  114. Amadeo, Ron (May 12, 2017). "Google's "Project Treble" solves one of Android's many update roadblocks". Ars Technica. Condé Nast. Archived from the original on December 3, 2017. Retrieved November 10, 2017.
  115. Amadeo, Ron (September 29, 2017). "Android users rejoice! Linux kernel LTS releases are now good for 6 years". Ars Technica. Condé Nast. Archived from the original on November 11, 2017. Retrieved November 10, 2017.
  116. "Fresher OS with Projects Treble and Mainline". Android Developers Blog. Retrieved July 29, 2019.
  117. "Google says Android 12 will make using third-party app stores easier". The Verge. September 28, 2020. Retrieved September 28, 2020.
  118. "Android Common Kernels". Android Open Source Project. February 2, 2021. Retrieved March 25, 2021.
  119. Hildenbrand, Jerry (January 23, 2012). "What is a kernel?". Android Central. Archived from the original on May 27, 2017. Retrieved June 20, 2017.
  120. "What Are The Major Changes That Android Made To The Linux Kernel?". Forbes. May 13, 2013. Archived from the original on January 4, 2017. Retrieved June 20, 2017.
  121. "LMG Upstreaming". Linaro. December 5, 2016. Archived from the original on January 9, 2018. Retrieved June 26, 2017.
  122. Proffitt, Brian (August 10, 2010). "Garrett's LinuxCon Talk Emphasizes Lessons Learned from Android/Kernel Saga". LinuxCon. Linux Foundation. Archived from the original on June 29, 2017. Retrieved June 20, 2017.
  123. Meyer, David (February 3, 2010). "Linux developer explains Android kernel code removal". ZDNet. CBS Interactive. Archived from the original on October 15, 2016. Retrieved March 11, 2017.
  124. 124.0 124.1 Kroah-Hartman, Greg (December 9, 2010). "Android and the Linux kernel community". Linux kernel monkey log. Retrieved June 20, 2017.
  125. Rooney, Paula (April 15, 2010). "DiBona: Google will hire two Android coders to work with kernel.org". ZDNet. CBS Interactive. Archived from the original on June 17, 2010. Retrieved March 11, 2017.
  126. 126.0 126.1 Paul, Ryan (February 24, 2009). "Dream(sheep++): A developer's introduction to Google Android". Ars Technica. Condé Nast. Archived from the original on July 4, 2017. Retrieved June 20, 2017.
  127. Vaughan-Nichols, Steven J. (September 7, 2010). "Android/Linux kernel fight continues". Computerworld. International Data Group. Archived from the original on February 14, 2017. Retrieved June 20, 2017.
  128. Vaughan-Nichols, Steven J. (August 18, 2011). "Linus Torvalds on Android, the Linux fork". ZDNet. CBS Interactive. Archived from the original on February 18, 2017. Retrieved March 11, 2017.
  129. Chris von Eitzen (December 23, 2011). "Android drivers to be included in Linux 3.3 kernel". h-online.com. Archived from the original on December 8, 2013. Retrieved February 15, 2012.
  130. Jonathan, Corbet. "Autosleep and wakelocks". LWN. Archived from the original on August 26, 2012.
  131. "Google Working On Android Based On Linux 3.8". February 28, 2013. Archived from the original on March 2, 2013. Retrieved February 28, 2013.
  132. "Google working on experimental Linux Kernel 3.10 for Android". Pocketdroid.net. Archived from the original on August 27, 2013. Retrieved September 3, 2013.
  133. McPherson, Amanda (December 13, 2012). "What a Year for Linux: Please Join us in Celebration". Linux Foundation. Archived from the original on April 17, 2014. Retrieved April 16, 2014.
  134. Proschofsky, Andreas (July 10, 2011). "Google: "Android is the Linux desktop dream come true"". derStandard.at. Archived from the original on April 22, 2013. Retrieved March 14, 2013.
  135. Hildenbrand, Jerry (November 8, 2012). "Ask AC: Is Android Linux?". Android Central. Mobile Nations. Archived from the original on April 8, 2017. Retrieved March 11, 2017.
  136. Lynch, Jim (August 20, 2013). "Is Android really a Linux distribution?". ITworld. Archived from the original on February 5, 2014. Retrieved April 17, 2014.
  137. 137.0 137.1 Paul, Ryan (February 24, 2009). "Dream(sheep++): A developer's introduction to Google Android". Ars Technica. Condé Nast. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
  138. Lynch, Doug (September 2, 2017). "Google is Mandating Linux Kernel Versions in Android Oreo". XDA Developers. Archived from the original on September 4, 2017. Retrieved November 9, 2017.
  139. Wyciślik-Wilson, Sofia (September 3, 2017). "With Android Oreo, Google is introducing Linux kernel requirements". BetaNews. eFront. Archived from the original on November 7, 2017. Retrieved November 9, 2017.
  140. Raja, Haroon Q. (May 19, 2011). "Android Partitions Explained: boot, system, recovery, data, cache & misc". Addictivetips.com. Archived from the original on September 22, 2012. Retrieved September 15, 2012.
  141. Jools Whitehorn (February 10, 2012). "Android malware gives itself root access | News". TechRadar. Archived from the original on September 1, 2012. Retrieved September 15, 2012.
  142. "Bootloader, Recovery, and the joy of unlocking". iFixit. April 29, 2016.
  143. 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. Archived from the original on May 13, 2014. Retrieved April 27, 2014.
  144. Ben Cheng; Bill Buzbee (May 2010). "A JIT Compiler for Android's Dalvik VM" (PDF). android-app-developer.co.uk. pp. 5–14. Archived from the original (PDF) on November 6, 2015. Retrieved March 18, 2015.
  145. Nickinson, Phil (May 26, 2010). "Google Android developer explains more about Dalvik and the JIT in Froyo". Android Central. Mobile Nations. Archived from the original on April 8, 2017. Retrieved March 11, 2017.
  146. 146.0 146.1 Burnette, Ed (June 4, 2008). "Patrick Brady dissects Android". ZDNet. CBS Interactive. Archived from the original on July 5, 2017. Retrieved March 11, 2017.
  147. 147.0 147.1 147.2 Amadeo, Ron (January 6, 2012). "Android N switches to OpenJDK, Google tells Oracle it is protected by the GPL". Ars Technica. Condé Nast. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
  148. 148.0 148.1 "Google confirms next Android version won't implement Oracle's proprietary Java APIs". VentureBeat. December 29, 2015. Archived from the original on December 30, 2015. Retrieved December 30, 2015.
  149. "Returning BlueZ to Android". LWN.net. May 6, 2014. Archived from the original on June 25, 2014.
  150. Android 11's new 'Gabeldorsche' Bluetooth stack was given its name for a great reason
  151. Pruett, Chris (January 11, 2011). "Gingerbread NDK Awesomeness". Android Developers Blog. Google, Inc. Archived from the original on February 19, 2014. Retrieved April 22, 2014.
  152. "Simple DirectMedia Layer for Android". SDL. August 12, 2012. Archived from the original on June 4, 2012.
  153. Android gets a toybox Archived March 4, 2016, at the Wayback Machine on lwn.net by Jake Edge (January 14, 2015)
  154. "Trusty TEE". Archived from the original on October 18, 2016.
  155. McFerran, Damien (April 17, 2012). "Best custom ROMs for the Samsung Galaxy S2". CNET. CBS Interactive. Archived from the original on April 19, 2012. Retrieved March 11, 2017.
  156. Russakovskii, Artem (May 1, 2010). "Custom ROMs For Android Explained – Here Is Why You Want Them". Android Police. Archived from the original on January 28, 2017. Retrieved March 12, 2017.
  157. Isaac, Mike (April 11, 2011). "Android OS Hack Gives Virtual Early Upgrade | Gadget Lab". Wired.com. Archived from the original on May 2, 2012. Retrieved September 15, 2012.
  158. "CyanogenMod Has Now Been Installed On Over 2 Million Devices, Doubles Install Numbers Since January". Androidpolice.com. May 28, 2012. Archived from the original on August 4, 2012. Retrieved September 15, 2012.
  159. OS, Lineage. "Lineage OS – Lineage OS Android Distribution". lineageos.org. Archived from the original on December 25, 2016. Retrieved January 31, 2017.
  160. 160.0 160.1 160.2 "HTC's bootloader unlock page". Htcdev.com. Archived from the original on October 19, 2012. Retrieved September 15, 2012.
  161. Sadun, Erica (July 26, 2010). "LoC rules in favor of jailbreaking". Tuaw.com. Archived from the original on October 30, 2012. Retrieved September 15, 2012.
  162. Crook, Jordan (October 24, 2011). "Motorola Offers Unlocked Bootloader Tool For Droid RAZR, Verizon Removes It". TechCrunch. AOL. Archived from the original on October 25, 2011. Retrieved June 25, 2017.
  163. "CyanogenMod 7 for Samsung Galaxy S2 (II): Development Already Started!". Inspired Geek. June 8, 2011. Archived from the original on August 22, 2012. Retrieved September 15, 2012.
  164. Menno (June 6, 2011). "CyanogenMod coming to the Galaxy S 2, thanks to Samsung". Android Central. Mobile Nations. Archived from the original on April 8, 2017. Retrieved March 11, 2017.
  165. Forian, Daniel. "Sony Ericsson supports independent developers – Developer World". Developer.sonyericsson.com. Archived from the original on February 12, 2012. Retrieved September 15, 2012.
  166. Kopfstein, Janus (November 20, 2012). "Access Denied: why Android's broken promise of unlocked bootloaders needs to be fixed". The Verge. Vox Media. Archived from the original on February 10, 2017. Retrieved March 11, 2017.
  167. "Device codename – XDA-Developers". forum.xda-developers.com. Retrieved March 13, 2019.
  168. "Documentation of the Build class". Android Developers. Retrieved March 13, 2019.
  169. Boulton, Clint (October 21, 2008). "Google Open-Sources Android on Eve of G1 Launch". eWeek. Retrieved February 17, 2012.
  170. Paul, Ryan (November 6, 2007). "Why Google chose the Apache Software License over GPLv2 for Android". Ars Technica. Condé Nast. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
  171. "Frequently Asked Questions: What is involved in releasing the source code for a new Android version?". Android Open Source Project. Archived from the original on August 3, 2010. Retrieved February 16, 2012.
  172. Bray, Tim (April 6, 2011). "Android Developers Blog: I think I'm having a Gene Amdahl moment". Android-developers.blogspot.com. Archived from the original on January 3, 2012. Retrieved February 16, 2012.
  173. Jerry Hildenbrand (March 24, 2011). "Honeycomb won't be open-sourced? Say it ain't so!". Androidcentral.com. Archived from the original on February 1, 2012. Retrieved February 16, 2012.
  174. Bohn, Dieter (December 10, 2019). "The Google Pixel will get bigger, more regular software updates you might actually remember". The Verge. Retrieved March 26, 2020.
  175. Pocket-lint (October 19, 2016). "Google Pixel exclusive features explored: A cut above the rest of Android?". Pocket-lint. Retrieved March 26, 2020.
  176. Stallman, Richard (September 19, 2011). "Is Android really free software?". The Guardian. London. Archived from the original on September 26, 2013. Retrieved September 9, 2012.
  177. Stallman, Richard (August 5, 2012). "Android and Users' Freedom – Support the Free Your Android campaign". GNU.org. Free Software Foundation. Archived from the original on September 5, 2012. Retrieved September 9, 2012.
  178. Dariusz Jemielniak; Aleksandra Przegalinska (February 18, 2020). Collaborative Society. MIT Press. ISBN 978-0-262-35645-9.
  179. Android Compatibility Definition Document (PDF) (5.0 ed.). January 11, 2015. Archived from the original (PDF) on March 4, 2014. Retrieved March 3, 2015.
  180. Warren, Tom (September 19, 2019). "Huawei confirms the new Mate 30 Pro won't come with Google's Android apps". The Verge. Retrieved March 26, 2020.
  181. Qing, Liau Yun (October 15, 2012). "Phonemakers make Android China-friendly". ZDNet. CBS Interactive. Archived from the original on October 13, 2016. Retrieved March 11, 2017.
  182. Byford, Sam (October 17, 2018). "How China rips off the iPhone and reinvents Android". The Verge. Retrieved March 26, 2020.
  183. "New Android OEM licensing terms leak; "Open" comes with a lot of restrictions". Ars Technica. Archived from the original on March 26, 2018. Retrieved March 26, 2018.
  184. Welch, Chris (August 19, 2021). "Google gave phone makers extra money to ditch third-party app stores". The Verge. Retrieved August 20, 2021.
  185. "Google starts blocking "uncertified" Android devices from logging in". Ars Technica. Archived from the original on March 26, 2018. Retrieved March 26, 2018.
  186. Amadeo, Ron (February 26, 2014). ""Google Now Launcher" hits Play Store, brings Google homescreen to GPE & Nexus devices". Ars Technica. Condé Nast. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
  187. Brian Klug (November 14, 2013). "Android 4.4 Factory Images Now Available for Nexus 4, 7 (2012 and 2013), and 10". AnandTech. Archived from the original on November 19, 2013. Retrieved November 19, 2013.
  188. Amadeo, Ron (November 14, 2013). "The Nexus 5's "exclusive" launcher suspiciously receives support for other devices". Ars Technica. Condé Nast. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
  189. "Neither Microsoft, Nokia, nor anyone else should fork Android. It's unforkable". Ars Technica. Condé Nast. Archived from the original on March 13, 2018. Retrieved March 12, 2018.
  190. "Android Open Source Project Frequently Asked Questions: Compatibility". source.android.com. Archived from the original on August 3, 2010. Retrieved March 13, 2011.
  191. Moyer, Edward (September 15, 2012). "Alibaba: Google just plain wrong about our OS". CNET. CBS Interactive. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
  192. Brodkin, Jon (September 15, 2012). "Google blocked Acer's rival phone to prevent Android "fragmentation"". Ars Technica. Condé Nast. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
  193. Brodkin, Jon (September 17, 2012). "Pirated Android apps featured prominently on Aliyun app store". Ars Technica. Condé Nast. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
  194. "Technology | Q&A: Google's Android". BBC News. November 6, 2007. Retrieved November 9, 2012.
  195. Reardon, Marguerite (February 11, 2008). "Google Android prototypes debut at MWC". CNET. CBS Interactive. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
  196. "Android's outing at Barcelona – BizTech – Technology". Sydney Morning Herald. February 12, 2008. Archived from the original on March 8, 2013. Retrieved November 9, 2012.
  197. Miller, Paul (November 5, 2007). "Symbian, Nokia, Microsoft and Apple downplay Android relevance". Engadget. AOL. Archived from the original on April 19, 2017. Retrieved March 11, 2017.
  198. 198.0 198.1 198.2 Brodkin, Jon (November 5, 2012). "On its 5th birthday, 5 things we love about Android". Ars Technica. Condé Nast. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
  199. Reisinger, Don (January 16, 2015). "Driverless Cars and Green Tech: What Google Is Doing Outside of Search". eWeek. slide 2.
  200. "On its fifth birthday, Android is "closer to our actual vision" for mobile supremacy". MobileSyrup.com. November 5, 2012. Archived from the original on November 9, 2012. Retrieved November 9, 2012.
  201. "Microsoft Selling Nokia X Android Phones". Business Insider. April 28, 2014. Archived from the original on May 4, 2014. Retrieved May 26, 2014.
  202. "Best Android apps for personalizing and customizing your phone". Androidauthority.com. July 13, 2012. Archived from the original on November 12, 2012. Retrieved November 9, 2012.
  203. Jeffries, Adrianne (March 19, 2013). "Disconnect: why Andy Rubin and Android called it quits". The Verge. Vox Media. Archived from the original on April 11, 2013. Retrieved March 11, 2017.
  204. Steve Kovach (July 30, 2013). "Android Fragmentation Report". Business Insider. Archived from the original on October 7, 2013. Retrieved October 19, 2013.
  205. 205.0 205.1 Arthur, Charles (July 30, 2013). "Android fragmentation 'worse than ever' – but OpenSignal says that's good". The Guardian. Archived from the original on August 1, 2013. Retrieved August 1, 2013.
  206. Eran, Daniel (October 16, 2013). "Strong demand of Apple's iPhone 5 series driving an "anti-fragmentation" of iOS". Appleinsider.com. Archived from the original on October 21, 2013. Retrieved October 19, 2013.
  207. "Mobile Operating System Market Share Worldwide". StatCounter Global Stats. Retrieved January 4, 2021.
  208. McLean, Prince (August 21, 2009). "Canalys: iPhone outsold all Windows Mobile phones in Q2 2009". AppleInsider. Archived from the original on January 17, 2012. Retrieved February 16, 2012.
  209. "Android Overtakes Windows in Smartphones". Financial Times. May 19, 2010. Archived from the original on August 18, 2017.
  210. "Android Overtakes iPhone Market Share in the US – Tug Agency". www.tugagency.com. May 11, 2010. Archived from the original on August 17, 2017.
  211. "Google's Android becomes the world's leading smart phone platform". Canalys. January 31, 2011. Archived from the original on February 25, 2012. Retrieved February 15, 2012.
  212. "Android steals Symbian's top smartphone OS crown". Phone arena. Archived from the original on May 9, 2013. Retrieved May 14, 2013.
  213. Goldman, David. "Android surpasses BlackBerry as No. 1 U.S. smartphone OS – Mar. 7, 2011". money.cnn.com. Archived from the original on August 18, 2017.
  214. "Gartner Says Sales of Mobile Devices Grew 5.6 Percent in Third Quarter of 2011; Smartphone Sales Increased 42 Percent". gartner.com. Gartner. November 15, 2011. Archived from the original on May 16, 2012. Retrieved February 16, 2012.
  215. 215.0 215.1 "Android Marks Fourth Anniversary Since Launch with 75.0% Market Share in Third Quarter, According to IDC – prUS23771812". Idc.com. Archived from the original on November 3, 2012. Retrieved November 3, 2012.
  216. 216.0 216.1 Kumparak, Greg (July 14, 2011). "Android Now Seeing 550,000 Activations Per Day". TechCrunch. AOL. Archived from the original on July 7, 2017. Retrieved June 25, 2017.
  217. Van Camp, Jeffrey (June 28, 2011). "Google activates 500,000 Android devices a day, may reach 1 million in October". Yahoo News. Archived from the original on December 25, 2012. Retrieved February 16, 2012.
  218. Barra, Hugo (May 10, 2011). "Android: momentum, mobile and more at Google I/O". The Official Google Blog. Archived from the original on January 30, 2012. Retrieved February 16, 2012.
  219. "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.
  220. 220.0 220.1 Melanson, Donald (April 16, 2013). "Eric Schmidt: Google now at 1.5 million Android activations per day". Engadget. AOL. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
  221. Welch, Chris (May 15, 2013). "Google: 900 million Android activations to date, 48 billion app installs". The Verge. Vox Media. Archived from the original on February 10, 2017. Retrieved March 11, 2017.
  222. Fingas, Jon (September 4, 2012). "ComScore: Android tops 52 percent of US smartphone share, iPhone cracks the 33 percent mark". Engadget. AOL. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
  223. "Report: Android Rises to 90% of Smartphone Market in China". Techinasia.com. Archived from the original on November 22, 2012. Retrieved November 24, 2012.
  224. "BBC Google activations and downloads update May 2013". BBC News. May 15, 2013. Archived from the original on May 16, 2013. Retrieved May 16, 2013.
  225. Gundotra, Vic. "Just back from a whirlwind trip to Asia visiting our…". Archived from the original on October 3, 2013. Retrieved September 3, 2013.
  226. "Number of available applications in the Google Play Store from December 2009 to March 2020". Statista. Retrieved May 10, 2020.
  227. Statt, Nick (May 18, 2016). "Android Users Have Installed More Than 65 Billion Apps from Google Play in the Last Year". The Verge. Vox Media. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
  228. Reardon, Marguertite (August 15, 2011). "Google just bought itself patent protection". CNET. CBS Interactive. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
  229. Perry, Douglas (July 16, 2011). "Google Android Now on 135 Million Devices". Tom's Guide. Purch Group. Archived from the original on June 20, 2017. Retrieved March 11, 2017.
  230. Whitney, Lance (January 6, 2014). "iPhone market share shrinks as Android, Windows Phone grow". CNET. CBS Interactive. Archived from the original on March 11, 2017. Retrieved March 11, 2017.
  231. "Global smartphone sales by operating system 2009–2016, by quarter". Statista. Archived from the original on August 17, 2014.
  232. "Gartner Says Annual Smartphone Sales Surpassed Sales of Feature Phones for the First Time in 2013". Archived from the original on February 14, 2014.
  233. "Gartner Says Worldwide Traditional PC, Tablet, Ultramobile and Mobile Phone Shipments On Pace to Grow 7.6 Percent in 2014". Archived from the original on June 19, 2014.
  234. 234.0 234.1 Template:Cite press release
  235. Lunden, Ingrid (October 15, 2014). "Tablet Sales Growth Plummets In 2014 As Android Smartphones Continue To Soar: Gartner". TechCrunch. AOL. Archived from the original on November 27, 2016. Retrieved June 25, 2017.
  236. "Global PC Shipments Exceed Forecast with Mild Improvement in Consumer Demand, While Apple Moves to #5 Spot, According to IDC". IDC.com. Archived from the original on October 11, 2014.
  237. 237.0 237.1 Cite error: Invalid <ref> tag; no text was provided for refs named Murky road despite dominance
  238. 238.0 238.1 Yarow, Jay (March 28, 2014). "This Chart Shows Google's Incredible Domination Of The World's Computing Platforms". Archived from the original on April 25, 2014. Retrieved April 23, 2014.
  239. "Mobile/Tablet Browser Market Share by OS". Archived from the original on May 26, 2012. Retrieved September 13, 2015.
  240. Template:Cite press release
  241. StatCounter. "StatCounter Global Stats – Browser, OS, Search Engine including Mobile Usage Share". Archived from the original on May 26, 2012. Retrieved November 30, 2016.
  242. "Global Stats – Browser, OS, Search Engine including Mobile Usage Share". StatCounter. Archived from the original on May 26, 2012. Retrieved September 23, 2016.
  243. Grush, Andrew (October 21, 2014). "Google hoping to lure smaller manufacturers to Google's Android, over AOSP". Android Authority. Archived from the original on October 22, 2014. Retrieved October 22, 2014./
  244. "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. Archived from the original on February 8, 2015. Retrieved January 23, 2015.
  245. "Installed base of smartphones by operating system in 2015 (in million units)". Statistica. Archived from the original on October 12, 2016. Retrieved November 1, 2016.
  246. "Market share of smartphone OS of total smartphone installed base in 2013 and 2014". Statistica. Archived from the original on February 18, 2015. Retrieved February 18, 2015.
  247. "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. Archived from the original on February 18, 2015. Retrieved February 18, 2015.
  248. Mahapatra, Lisa (November 11, 2013). "Android Vs. iOS: What's The Most Popular Mobile Operating System In Your Country?". International Business Times. Archived from the original on February 22, 2014. Retrieved January 30, 2014.
  249. Elmer-DeWitt, Philip (January 10, 2014). "Don't mistake Apple's market share for its installed base". CNN. Archived from the original on January 30, 2014. Retrieved January 30, 2014.
  250. "Samsung sells more smartphones than all major manufacturers combined in Q1". Archived from the original on May 12, 2014. Retrieved May 12, 2014.
  251. "Global mobile statistics 2014 Part A: Mobile subscribers; handset market share; mobile operators". mobiThinking. May 2014. Archived from the original on September 6, 2014. Retrieved September 9, 2014.
  252. 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. Archived from the original on September 9, 2014. Retrieved September 9, 2014.
  253. Martinez, Juan (August 14, 2014). "84.7% of all global smartphone shipments run Android". TechRadar. Future plc. Archived from the original on October 11, 2017. Retrieved October 11, 2017.
  254. Ruddock, David (August 14, 2014). "IDC: Android Now Accounts For 84.7% Of All Smartphone Shipments, Grew 33.3% Year-Over-Year This Quarter". Android Police. Illogical Robot. Archived from the original on October 11, 2017. Retrieved October 11, 2017.
  255. Walter, Derek (November 3, 2016). "Report: Nearly 90 percent of smartphones worldwide run Android". Greenbot. International Data Group. Archived from the original on October 11, 2017. Retrieved October 11, 2017.
  256. Bhattacharya, Ananya (November 3, 2016). "Android just hit a record 88% market share of all smartphones". Quartz. Atlantic Media. Archived from the original on October 11, 2017. Retrieved October 11, 2017.
  257. Russell, Jon (April 3, 2017). "Report: Android overtakes Windows as the internet's most used operating system". TechCrunch. AOL. Archived from the original on September 3, 2017. Retrieved September 3, 2017.
  258. Protalinski, Emil (April 3, 2017). "StatCounter: Android overtakes Windows as world's most-used operating system". VentureBeat. Archived from the original on September 3, 2017. Retrieved September 3, 2017.
  259. "Operating System Market Share Worldwide". StatCounter. Archived from the original on August 31, 2017. Retrieved September 3, 2017.
  260. Vincent, James (September 29, 2015). "Android is now used by 1.4 billion people". The Verge. Vox Media. Archived from the original on January 14, 2017. Retrieved March 12, 2017.
  261. Lomas, Natasha (September 29, 2015). "Android Now Has 1.4 Billion 30-Day Active Users Globally". TechCrunch. AOL. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
  262. Protalinski, Emil (May 17, 2017). "Android passes 2 billion monthly active devices". VentureBeat. Archived from the original on May 17, 2017. Retrieved May 17, 2017.
  263. Ng, Alfred (May 17, 2017). "Google's Android now powers more than 2 billion devices". CNET. CBS Interactive. Archived from the original on May 17, 2017. Retrieved May 17, 2017.
  264. Wilson Rothman (October 24, 2012). "Why iPad is stomping Android tabs 24 to 1 – Technology on". Nbcnews.com. Archived from the original on January 26, 2013. Retrieved November 9, 2012.
  265. Kevin C. Tofel (March 19, 2012). "What devs say about iPad (but not Android tablets)". Gigaom.com. Archived from the original on August 15, 2012. Retrieved November 9, 2012.
  266. 266.0 266.1 266.2 266.3 Kendrick, James (March 21, 2012). "Why there aren't more Android tablet apps, by the numbers". ZDNet. CBS Interactive. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
  267. Poeter, Damon (December 7, 2012). "Goldman Highlights Microsoft's Shrinking Market Share". PC Magazine. Archived from the original on December 12, 2012. Retrieved December 10, 2012.
  268. Gruman, Galen (April 5, 2011). "Why Google's tighter control over Android is a good thing | Mobile Technology". InfoWorld. Archived from the original on June 3, 2013. Retrieved March 14, 2013.
  269. Gruman, Galen (April 30, 2011). "Anatomy of failure: Mobile flops from RIM, Microsoft, and Nokia". Macworld. Archived from the original on May 1, 2013. Retrieved May 14, 2013.
  270. Hiner, Jason (January 5, 2012). "Why Android tablets failed: A postmortem". TechRepublic. Archived from the original on October 17, 2012. Retrieved November 9, 2012.
  271. Cunningham, Andrew (October 8, 2012). "Google to Android devs: make nicer tablet apps, pretty please?". Ars Technica. Condé Nast. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
  272. Kovach, Steve. "Android Now Ahead Of Apple's iOS In Tablet Market Share". Business Insider. Archived from the original on May 3, 2013.
  273. "Gartner Says Worldwide Tablet Sales Grew 68 Percent in 2013, With Android Capturing 62 Percent of the Market". Archived from the original on April 17, 2014.
  274. "Gartner Says Worldwide Media Tablets Sales to Reach 119 Million Units in 2012". Archived from the original on May 24, 2014.
  275. "Android Ecosystem Takes the Baton from Apple iPad in the Tablet Race". ABIresearch. September 27, 2013. Retrieved September 10, 2014.
  276. "Tablet Operating System Market Share Worldwide". StatCounter Global Stats. Retrieved December 16, 2020.
  277. Gruman, Galen (March 24, 2016). "How to make Android a real part of your business". InfoWorld. International Data Group. Archived from the original on February 23, 2017. Retrieved March 12, 2017. Template:Registration required
  278. Gruman, Galen (August 7, 2015). "Office Mobile: Better on iPads than on Windows 10 tablets". InfoWorld. International Data Group. Archived from the original on February 11, 2017. Retrieved March 12, 2017.
  279. "Mobile Android Version Market Share Worldwide". StatCounter Global Stats.
  280. "Mobile Android Version Market Share Worldwide". StatCounter Global Stats. Retrieved May 4, 2022.
  281. "Mobile Android Version Market Share Worldwide". StatCounter Global Stats. Retrieved October 2, 2021.
  282. "Tablet Android Version Market Share Worldwide". StatCounter Global Stats. Retrieved May 4, 2022.
  283. "Tablet Android Version Market Share Worldwide". StatCounter Global Stats. Retrieved September 1, 2021.
  284. "Tablet Android Version Market Share Worldwide". StatCounter Global Stats. Retrieved September 1, 2021.
  285. "Tablet Android Version Market Share Worldwide". StatCounter Global Stats. Retrieved May 4, 2022.
  286. "Android 13 Beta devices". Android Developers. Retrieved May 11, 2022.
  287. "Realme GT gets Android 12 Beta 1 this month". GSMArena.com. Retrieved May 11, 2022.
  288. "Android 12 Beta 1 is Now Available for Mi 11, Mi 11 Ultra, Mi 11i/Mi 11X Pro. Download Now! - MIUI ROM - Xiaomi Community - Xiaomi". c.mi.com. Retrieved May 11, 2022.
  289. "Get Android 11". Android Developers. Retrieved February 21, 2020.
  290. "Android 11 Beta 1 is Now Available for Mi 10, Mi 10 Pro and POCO F2 Pro. Download Now!! - General - Xiaomi Community - Xiaomi". c.mi.com. Retrieved May 11, 2022.
  291. "Android Beta Program". www.google.com. Retrieved September 7, 2019.
  292. "Android P Beta Devices". Android Developers. Archived from the original on May 10, 2018. Retrieved July 13, 2018.
  293. "Distribution dashboard". Android Developers. July 2021. Retrieved October 12, 2021.
  294. Wired UK (May 3, 2012). "Op-Ed: Android Piracy Is Huge Problem for Game Devs | Game|Life". Wired.com. Archived from the original on September 6, 2012. Retrieved September 15, 2012.
  295. Yin, Wesley (April 24, 2012). "Football Manager dev hopes to stick with Android despite 9:1 piracy rate". Eurogamer.net. Archived from the original on September 16, 2012. Retrieved September 15, 2012.
  296. Armasu, Lucian (July 30, 2012). "Wind-up Knight developer: Piracy rates on iOS and Android are comparable, China is the main source". Androidauthority.com. Archived from the original on October 20, 2012. Retrieved October 6, 2012.
  297. Paul, Ryan (August 25, 2010). "Android antipiracy cracked, Google says devs used it wrong". Ars Technica. Condé Nast. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
  298. Amadeo, Ron (July 9, 2014). "Update: Google posts DRM workaround for paid Android Wear apps". Ars Technica. Condé Nast. Archived from the original on February 10, 2017. Retrieved March 11, 2017.
  299. McAllister, Neil (August 8, 2012). "Android app DRM quietly disabled due to bug". The Register. Archived from the original on August 11, 2012. Retrieved June 10, 2012.
  300. Niccolai, James (August 12, 2010). "Update: Oracle sues Google over Java use in Android". Computerworld. IDG. Archived from the original on January 6, 2012. Retrieved February 16, 2012.
  301. "Oracle seeks up to $6.1 billion in Google lawsuit". Reuters. June 18, 2011. Archived from the original on September 2, 2011. Retrieved September 7, 2011.
  302. "Judge tosses Oracle's $6.1 billion damage estimate in claim against Google". MercuryNews.com. July 22, 2011. Archived from the original on January 18, 2012. Retrieved September 7, 2011.
  303. Singel, Ryan (October 5, 2010). "Calling Oracle Hypocritical, Google Denies Patent Infringement". Wired. Archived from the original on November 28, 2011. Retrieved February 16, 2012.
  304. Lowensohn, Josh (May 23, 2012). "Jury clears Google of infringing on Oracle patents". ZDNet. CBS Interactive. Archived from the original on April 23, 2017. Retrieved March 11, 2017.
  305. Mullin, Joe (May 31, 2012). "Google wins crucial API ruling, Oracle's case decimated". Ars Technica. Condé Nast. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
  306. Niccolai, James (June 20, 2012). "Oracle agrees to 'zero' damages in Google lawsuit, eyes appeal". Archived from the original on November 17, 2012. Retrieved June 23, 2012.
  307. Rosenblatt, Seth (May 9, 2014). "Court sides with Oracle over Android in Java patent appeal". CNET. CBS Interactive. Archived from the original on April 19, 2017. Retrieved March 11, 2017.
  308. "ORACLE AMERICA, INC., Plaintiff – Appellant, v. GOOGLE INC., Defendant – Cross – Appellant" (PDF). Court of Appeals for the Federal Circuit. May 9, 2014. Archived from the original (PDF) on June 1, 2014. Retrieved May 10, 2014.
  309. Mullin, Joe (May 26, 2016). "Google beats Oracle—Android makes "fair use" of Java APIs". Ars Technica. Condé Nast. Archived from the original on January 18, 2017. Retrieved March 11, 2017.
  310. Mann, Ronald (April 6, 2021). "Justices validate Google's use of Java platform in Android software code". SCOTUSBlog. Retrieved April 7, 2021.
  311. "FSFE objects to claims of 'predatory pricing' in Free Software". Free Software Foundation Europe. Archived from the original on October 2, 2013. Retrieved September 28, 2013.
  312. Rawlinson, Kevin (April 20, 2016). "Google faces EU charge over Android 'abuse of dominance'". Archived from the original on April 20, 2016. Retrieved April 20, 2016.
  313. "Russia fines Google $6.75 million for preinstalling apps on Android". The Verge. Vox Media. August 12, 2016. Archived from the original on March 24, 2017. Retrieved March 23, 2017.
  314. Warren, Tom (July 18, 2018). "Google fined a record $5 billion by the EU for Android antitrust violations". The Verge. Retrieved July 18, 2018.
  315. Schechner, Sam (October 9, 2018). "Google Appeals $5 Billion EU Fine in Android Case". The Wall Street Journal. Retrieved October 9, 2018.
  316. Kastrenakes, Jacob; Patel, Nilay (October 16, 2018). "Google will start charging Android device makers a fee for using its apps in Europe". The Verge. Retrieved October 17, 2018.
  317. 317.0 317.1 Newman, Jared (September 28, 2011). "Microsoft-Samsung Patent Deal: Great News for Windows Phones". PCWorld. Archived from the original on January 29, 2012. Retrieved September 15, 2012.
  318. Template:Cite press release
  319. Brodkin, Jon (October 23, 2011). "Microsoft collects license fees on 50% of Android devices, tells Google to "wake up"". Ars Technica. Condé Nast. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
  320. Mikael Ricknäs (September 28, 2011). "Microsoft signs Android licensing deal with Samsung". Computerworld. Archived from the original on January 7, 2012. Retrieved February 16, 2012.
  321. Trent, Rod. "Microsoft Inside: 20 New Android Device Manufacturers Sign-on to Pre-Install Office and Skype". SuperSite for Windows. Penton. Archived from the original on August 28, 2016. Retrieved August 23, 2016.
  322. The time allocated for running scripts has expired.
  323. The time allocated for running scripts has expired.
  324. The time allocated for running scripts has expired.
  325. The time allocated for running scripts has expired.
  326. The time allocated for running scripts has expired.
  327. 327.0 327.1 The time allocated for running scripts has expired.
  328. The time allocated for running scripts has expired.
  329. The time allocated for running scripts has expired.
  330. The time allocated for running scripts has expired.
  331. The time allocated for running scripts has expired.
  332. The time allocated for running scripts has expired.
  333. The time allocated for running scripts has expired.
  334. The time allocated for running scripts has expired.
  335. The time allocated for running scripts has expired.
  336. 336.0 336.1 The time allocated for running scripts has expired.
  337. The time allocated for running scripts has expired.
  338. The time allocated for running scripts has expired.
  339. The time allocated for running scripts has expired.
  340. The time allocated for running scripts has expired.
  341. The time allocated for running scripts has expired.
  342. 342.0 342.1 The time allocated for running scripts has expired.
  343. The time allocated for running scripts has expired.
  344. The time allocated for running scripts has expired.
  345. The time allocated for running scripts has expired.
  346. The time allocated for running scripts has expired.
  347. The time allocated for running scripts has expired.
  348. The time allocated for running scripts has expired.
  349. The time allocated for running scripts has expired.
  350. The time allocated for running scripts has expired.
  351. The time allocated for running scripts has expired.
  352. The time allocated for running scripts has expired.
  353. The time allocated for running scripts has expired.
  354. The time allocated for running scripts has expired.
  355. The time allocated for running scripts has expired.
  356. The time allocated for running scripts has expired.
  357. The time allocated for running scripts has expired.
  358. The time allocated for running scripts has expired.
  359. The time allocated for running scripts has expired.
  360. The time allocated for running scripts has expired.
  361. The time allocated for running scripts has expired.
  362. The time allocated for running scripts has expired.
  363. The time allocated for running scripts has expired.
  364. The time allocated for running scripts has expired.
  365. The time allocated for running scripts has expired.
  366. The time allocated for running scripts has expired.
  367. The time allocated for running scripts has expired.
  368. The time allocated for running scripts has expired.
  369. The time allocated for running scripts has expired.
  370. The time allocated for running scripts has expired.
  371. The time allocated for running scripts has expired.
  372. The time allocated for running scripts has expired.
  373. 373.0 373.1 The time allocated for running scripts has expired.
  374. The time allocated for running scripts has expired.
  375. The time allocated for running scripts has expired.
  376. The time allocated for running scripts has expired.
  377. The time allocated for running scripts has expired.
  378. The time allocated for running scripts has expired.
  379. The time allocated for running scripts has expired.
  380. The time allocated for running scripts has expired.
  381. The time allocated for running scripts has expired.

The time allocated for running scripts has expired.

External links[edit]

The time allocated for running scripts has expired.

The time allocated for running scripts has expired. Template:Mobile operating systems Template:Linux distributions The time allocated for running scripts has expired.The time allocated for running scripts has expired.