Android (operating system)
From Wikipedia the free encyclopedia
Commercial logo as used by Google, since 2019
|Developer||Various (mostly Google and the Open Handset Alliance)|
|Written in||Java (UI), C (core), C++ and others|
|OS family||Unix-like (Modified Linux kernel)|
|Source model||Open source (most devices include proprietary components, such as Google Play)|
|Initial release||September 23, 2008|
|Latest release||Android 11 / September 8, 2020|
|Marketing target||Smartphones, tablet computers, smart TVs (Android TV), Android Auto and smartwatches (Wear OS)|
|Available in||100+ languages|
|Platforms||64-bit (32-bit being dropped) ARM, x86 and x86-64|
|Kernel type||Linux kernel|
|Userland||Bionic libc, mksh shell, Toybox as core utilities (beginning with Android 6.0)|
|Default user interface||Graphical (multi-touch)|
|Articles in the series|
|Android version history|
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 launched in September 2008.
It is free and open source software; its source code is known as Android Open Source Project (AOSP), which is primarily licensed under the Apache License. However most Android devices ship with additional proprietary software pre-installed, most notably Google Mobile Services (GMS) which includes core apps such as Google Chrome, the digital distribution platform Google Play and associated Google Play Services development platform. About 70 percent of Android smartphones run Google's ecosystem; competing Android ecosystems and forks include Fire OS (developed by Amazon) or LineageOS. However the "Android" name and logo are trademarks of Google which impose standards to restrict "uncertified" devices outside their ecosystem to use Android branding.
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 and others, 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, Samsung Galaxy Store, and Huawei AppGallery, 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 2017[update], it has over two billion monthly active users, the largest installed base of any operating system, and as of August 2020[update], the Google Play Store features over 3 million apps. The current stable version is Android 11, released on September 8, 2020.
Android Inc. was founded in Palo Alto, California, in October 2003 by Andy Rubin, Rich Miner, Nick Sears, and Chris White. Rubin described the Android project as "tremendous potential in developing smarter mobile devices that are more aware of its owner's location and preferences". The early intentions of the company were to develop an advanced operating system for digital cameras, and this was the basis of its pitch to investors in April 2004. The company then decided that the market for cameras was not large enough for its goals, and by five months later it had diverted its efforts and was pitching Android as a handset operating system that would rival Symbian and Microsoft Windows Mobile.
Rubin had difficulty attracting investors early on, and Android was facing eviction from its office space. Steve Perlman, a close friend of Rubin, brought him $10,000 in cash in an envelope, and shortly thereafter wired an undisclosed amount as seed funding. Perlman refused a stake in the company, and has stated "I did it because I believed in the thing, and I wanted to help Andy."
In July 2005, Google acquired Android Inc. for at least $50 million. Its key employees, including Rubin, Miner and White, joined Google as part of the acquisition. Not much was known about the secretive Android at the time, with the company having provided few details other than that it was making software for mobile phones. At Google, the team led by Rubin developed a mobile device platform powered by the Linux kernel. Google marketed the platform to handset makers and carriers on the promise of providing a flexible, upgradeable system. Google had "lined up a series of hardware components and software partners and signaled to carriers that it was open to various degrees of cooperation".[attribution needed]
Speculation about Google's intention to enter the mobile communications market continued to build through December 2006. An early prototype had a close resemblance to a BlackBerry phone, with no touchscreen and a physical QWERTY keyboard, but the arrival of 2007's Apple iPhone meant that Android "had to go back to the drawing board". Google later changed its Android specification documents to state that "Touchscreens will be supported", although "the Product was designed with the presence of discrete physical buttons as an assumption, therefore a touchscreen cannot completely replace physical buttons". By 2008, both Nokia and BlackBerry announced touch-based smartphones to rival the iPhone 3G, and Android's focus eventually switched to just touchscreens. The first commercially available smartphone running Android was the HTC Dream, also known as T-Mobile G1, announced on September 23, 2008.
On November 5, 2007, the Open Handset Alliance, a consortium of technology companies including Google, device manufacturers such as HTC, Motorola and Samsung, wireless carriers such as Sprint and T-Mobile, and chipset makers such as Qualcomm and Texas Instruments, unveiled itself, with a goal to develop "the first truly open and comprehensive platform for mobile devices". Within a year, the Open Handset Alliance faced two other open source competitors, the Symbian Foundation and the LiMo Foundation, the latter also developing a Linux-based mobile operating system like Google. In September 2007, InformationWeek covered an Evalueserve study reporting that Google had filed several patent applications in the area of mobile telephony.
Since 2008, Android has seen numerous updates which have incrementally improved the operating system, adding new features and fixing bugs in previous releases. Each major release is named in alphabetical order after a dessert or sugary treat, with the first few Android versions being called "Cupcake", "Donut", "Eclair", and "Froyo", in that order. During its announcement of Android KitKat in 2013, Google explained that "Since these devices make our lives so sweet, each Android version is named after a dessert", although a Google spokesperson told CNN in an interview that "It's kind of like an internal team thing, and we prefer to be a little bit — how should I say — a bit inscrutable in the matter, I'll say".
In 2010, Google launched its Nexus series of devices, a lineup in which Google partnered with different device manufacturers to produce new devices and introduce new Android versions. The series was described as having "played a pivotal role in Android's history by introducing new software iterations and hardware standards across the board", and became known for its "bloat-free" software with "timely ... updates". At its developer conference in May 2013, Google announced a special version of the Samsung Galaxy S4, where, instead of using Samsung's own Android customization, the phone ran "stock Android" and was promised to receive new system updates fast. The device would become the start of the Google Play edition program, and was followed by other devices, including the HTC One Google Play edition, and Moto G Google Play edition. In 2015, Ars Technica wrote that "Earlier this week, the last of the Google Play edition Android phones in Google's online storefront were listed as "no longer available for sale" and that "Now they're all gone, and it looks a whole lot like the program has wrapped up".
From 2008 to 2013, Hugo Barra served as product spokesperson, representing Android at press conferences and Google I/O, Google's annual developer-focused conference. He left Google in August 2013 to join Chinese phone maker Xiaomi. Less than six months earlier, Google's then-CEO Larry Page announced in a blog post that Andy Rubin had moved from the Android division to take on new projects at Google, and that Sundar Pichai would become the new Android lead. Pichai himself would eventually switch positions, becoming the new CEO of Google in August 2015 following the company's restructure into the Alphabet conglomerate, making Hiroshi Lockheimer the new head of Android.
In June 2014, Google announced Android One, a set of "hardware reference models" that would "allow [device makers] to easily create high-quality phones at low costs", designed for consumers in developing countries. In September, Google announced the first set of Android One phones for release in India. However, Recode reported in June 2015 that the project was "a disappointment", citing "reluctant consumers and manufacturing partners" and "misfires from the search company that has never quite cracked hardware". Plans to relaunch Android One surfaced in August 2015, with Africa announced as the next location for the program a week later. A report from The Information in January 2017 stated that Google is expanding its low-cost Android One program into the United States, although The Verge notes that the company will presumably not produce the actual devices itself.
Google introduced the Pixel and Pixel XL smartphones in October 2016, marketed as being the first phones made by Google, and exclusively featured certain software features, such as the Google Assistant, before wider rollout. The Pixel phones replaced the Nexus series, with a new generation of Pixel phones launched in October 2017.
In May 2019, the operating system became entangled in the trade war between China and the United States involving Huawei which like many other tech firms have become dependent on access to the Android platform. In the summer of 2019, Huawei announced it would create an alternative operating system to Android known as Harmony OS, and have filed for intellectual property rights across major global markets. Huawei does not currently have any plans to replace Android in the near future, as Harmony OS is designed for internet of things devices, rather than for smartphones.
On August 22, 2019, it was announced that Android "Q" would officially be branded as Android 10, ending the historic practice of naming major versions after desserts. Google stated that these names were not "inclusive" to international users (due either to the aforementioned foods not being internationally known, or being difficult to pronounce in some languages). On the same day, Android Police reported that Google had commissioned a statue of a giant number "10" to be installed in the lobby of the developers' new office. Android 10 was released on September 3, 2019 to Google Pixel phones first.
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. Game controllers and full-size physical keyboards are supported via Bluetooth or USB. 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, or allowing the user to steer a vehicle in a racing game by rotating the device, simulating control of a steering wheel.
Android devices boot to the homescreen, the primary navigation and information "hub" on Android devices, analogous to the desktop found on personal computers. Android homescreens are typically made up of app icons and widgets; app icons launch the associated app, whereas widgets display live, auto-updating content, such as a weather forecast, the user's email inbox, or a news ticker directly on the homescreen. A homescreen may be made up of several pages, between which the user can swipe back and forth. Third-party apps available on Google Play and other app stores can extensively re-theme the homescreen, and even mimic the look of other operating systems, such as Windows Phone. Most manufacturers customize the look and features of their Android devices to differentiate themselves from their competitors.
Along the top of the screen is a status bar, showing information about the device and its connectivity. This status bar can be "pulled" down to reveal a notification screen where apps display important information or updates. 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. 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.
An All Apps screen lists all installed applications, with the ability for users to drag an app from the list onto the home screen. A Recents screen lets users switch between recently used apps.
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), are written using the Android software development kit (SDK) and, often, Kotlin programming language, which replaced Java as Google's preferred language for Android app development in May 2019, and was originally announced in May 2017. Java is still supported (originally the only option for user-space programs, and is often mixed with Kotlin), as is C++. Java and/or other JVM languages, such as Kotlin, may be combined with C/C++, together with a choice of non-default runtimes that allow better C++ support. The Go programming language is also supported, although with a limited set of application programming interfaces (API).
The SDK includes a comprehensive set of development tools, 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. Additionally, Firebase was acquired by Google in 2014 that provides helpful tools for app and web developers.
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. Google Play Store allows users to browse, download and update applications published by Google and third-party developers; as of August 2020[update], there are more than three million applications available for Android in Play Store. As of July 2013[update], 50 billion applications have been installed. 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. As of May 2017[update], 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.
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. 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. Lifehacker reported in 2011 that third-party task killer applications were doing more harm than good.
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. The unofficial Android-x86 project provided support for x86 architectures ahead of the official support. The ARMv5TE and MIPS32/64 architectures were also historically supported but removed in later Android releases. Since 2012, Android devices with Intel processors began to appear, including phones 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.
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, to absolute minimum 512 MB for the lowest spec 32-bit smartphone. The recommendation for Android 4.4 is to have at least 512 MB of RAM, while for "low RAM" devices 340 MB is the required minimum amount that does not include memory dedicated to various hardware components such as the baseband processor. Android 4.4 requires a 32-bit ARMv7, MIPS or x86 architecture processor (latter two through unofficial ports), together with an OpenGL ES 2.0 compatible graphics processing unit (GPU). Android supports OpenGL ES 1.1, 2.0, 3.0, 3.1 and 3.2 and since Android 7.0 Vulkan (and version 1.1 available for some devices). Some applications may explicitly require a certain version of the OpenGL ES, and suitable GPU hardware is required to run such applications.
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. Android used to require an autofocus camera, which was relaxed to a fixed-focus camera 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. 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. Using the Android emulator that is part of the Android SDK, or third-party emulators, Android can also run non-natively on x86 architectures. Chinese companies are building a PC and mobile operating system, based on Android, to "compete directly with Microsoft Windows and Google Android". The Chinese Academy of Engineering noted that "more than a dozen" companies were customising Android following a Chinese ban on the use of Windows 8 on government PCs.
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), an open source initiative led by Google. The AOSP code can be found without modification on select devices, mainly the former Nexus and current Android One series of devices.
The source code is, in turn, customized by original equipment manufacturers (OEMs) to run on their hardware. Android's source code does not contain the device drivers, often proprietary, that are needed for certain hardware components. 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.
The extensive variation of hardware 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. 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. Manufacturers often prioritize their newest devices and leave old ones behind. 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. There are also situations in which upgrades are impossible due to a manufacturer not updating necessary drivers.
The lack of after-sale support from manufacturers and carriers has been widely criticized by consumer groups and the technology media. 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, an attitude described as "insulting". The Guardian complained that the method of distribution for updates is complicated only because manufacturers and carriers have designed it that way. 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.
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. 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.
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.[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'".
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."
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.
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.
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 app, including a fight over an alternative in-app payment system and difficulties faced by businesses moving online because of Covid-19.
Android's kernel is based on the Linux kernel's long-term support (LTS) branches. As of 2020[update], Android uses versions 4.4, 4.9 or 4.14 of the Linux kernel. The actual kernel depends on the individual device.
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. Certain features that Google contributed back to the Linux kernel, notably a power management feature called "wakelocks", were initially rejected by mainline kernel developers partly because they felt that Google did not show any intent to maintain its own code. Google announced in April 2010 that they would hire two employees to work with the Linux kernel community, 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. Google engineer Patrick Brady once stated in the company's developer conference that "Android is not Linux", with Computerworld adding that "Let me make it simple for you, without Linux, there is no Android". 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".
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". 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. Linux included the autosleep and wakelocks capabilities in the 3.5 kernel, after many previous attempts at merger. The interfaces are the same but the upstream Linux implementation allows for two different suspend modes: to memory (the traditional suspend that Android uses), and to disk (hibernate, as it is known on the desktop). Google maintains a public code repository that contains their experimental work to re-base Android off the latest stable Linux versions.
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. In contrast to desktop Linux distributions, Android device owners are not given root access to the operating system and sensitive partitions such as /system are read-only. However, root access can be obtained by exploiting security flaws in Android, which is used frequently by the open-source community to enhance the capabilities of their devices, but also by malicious parties to install viruses and malware.
Android is a Linux distribution according to the Linux Foundation, Google's open-source chief Chris DiBona, and several journalists. Others, such as Google engineer Patrick Brady, say that Android is not Linux in the traditional Unix-like Linux distribution sense; Android does not include the GNU C Library (it uses Bionic as an alternative C library) and some of other components typically found in Linux distributions.
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.
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. 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. For its Java library, the Android platform uses a subset of the now discontinued Apache Harmony project. In December 2015, Google announced that the next version of Android would switch to a Java implementation based on the OpenJDK project.
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.
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, until version r5 of the Android Native Development Kit brought support for applications written completely in C or C++. Libraries written in C may also be used in applications by injection of a small shim and usage of the JNI.
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.
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."
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. 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; 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. CyanogenMod was the most widely used community firmware, now discontinued and succeeded by LineageOS.
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. 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, manufacturers and carriers have softened their position regarding third party development, with some, including HTC, Motorola, Samsung and Sony, 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. However, despite manufacturer acceptance, some carriers in the US still require that phones are locked down, frustrating developers and customers.
Internally, Android identifies each supported device by its device codename, a short string, 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
Security and privacy
Scope of surveillance by public institutions
As part of the broader 2013 mass surveillance disclosures it was revealed in September 2013 that the American and British intelligence agencies, the National Security Agency (NSA) and Government Communications Headquarters (GCHQ), respectively, have access to the user data on iPhone, BlackBerry, and Android devices. They are reportedly able to read almost all smartphone information, including SMS, location, emails, and notes. In January 2014, further reports revealed the intelligence agencies' capabilities to intercept the personal information transmitted across the Internet by social networks and other popular applications such as Angry Birds, which collect personal information of their users for advertising and other commercial reasons. GCHQ has, according to The Guardian, a wiki-style guide of different apps and advertising networks, and the different data that can be siphoned from each. Later that week, the Finnish Angry Birds developer Rovio announced that it was reconsidering its relationships with its advertising platforms in the light of these revelations, and called upon the wider industry to do the same.
The documents revealed a further effort by the intelligence agencies to intercept Google Maps searches and queries submitted from Android and other smartphones to collect location information in bulk. The NSA and GCHQ insist their activities comply with all relevant domestic and international laws, although the Guardian stated "the latest disclosures could also add to mounting public concern about how the technology sector collects and uses information, especially for those outside the US, who enjoy fewer privacy protections than Americans."
Leaked documents published by WikiLeaks, codenamed Vault 7 and dated from 2013 to 2016, detail the capabilities of the Central Intelligence Agency (CIA) to perform electronic surveillance and cyber warfare, including the ability to compromise the operating systems of most smartphones (including Android).
Common security threats
Research from security company Trend Micro lists premium service abuse as the most common type of Android malware, where text messages are sent from infected phones to premium-rate telephone numbers without the consent or even knowledge of the user. Other malware displays unwanted and intrusive advertisements on the device, or sends personal information to unauthorised third parties. Security threats on Android are reportedly growing exponentially; however, Google engineers have argued that the malware and virus threat on Android is being exaggerated by security companies for commercial reasons, and have accused the security industry of playing on fears to sell virus protection software to users. Google maintains that dangerous malware is actually extremely rare, and a survey conducted by F-Secure showed that only 0.5% of Android malware reported had come from the Google Play store.
In August 2015, Google announced that devices in the Google Nexus series would begin to receive monthly security patches. Google also wrote that "Nexus devices will continue to receive major updates for at least two years and security patches for the longer of three years from initial availability or 18 months from last sale of the device via the Google Store." The following October, researchers at the University of Cambridge concluded that 87.7% of Android phones in use had known but unpatched security vulnerabilities due to lack of updates and support. Ron Amadeo of Ars Technica wrote also in August 2015 that "Android was originally designed, above all else, to be widely adopted. Google was starting from scratch with zero percent market share, so it was happy to give up control and give everyone a seat at the table in exchange for adoption. [...] Now, though, Android has around 75–80 percent of the worldwide smartphone market—making it not just the world's most popular mobile operating system but arguably the most popular operating system, period. As such, security has become a big issue. Android still uses a software update chain-of-command designed back when the Android ecosystem had zero devices to update, and it just doesn't work". Following news of Google's monthly schedule, some manufacturers, including Samsung and LG, promised to issue monthly security updates, but, as noted by Jerry Hildenbrand in Android Central in February 2016, "instead we got a few updates on specific versions of a small handful of models. And a bunch of broken promises".
In a March 2017 post on Google's Security Blog, Android security leads Adrian Ludwig and Mel Miller wrote that "More than 735 million devices from 200+ manufacturers received a platform security update in 2016" and that "Our carrier and hardware partners helped expand deployment of these updates, releasing updates for over half of the top 50 devices worldwide in the last quarter of 2016". They also wrote that "About half of devices in use at the end of 2016 had not received a platform security update in the previous year", stating that their work would continue to focus on streamlining the security updates program for easier deployment by manufacturers. Furthermore, in a comment to TechCrunch, Ludwig stated that the wait time for security updates had been reduced from "six to nine weeks down to just a few days", with 78% of flagship devices in North America being up-to-date on security at the end of 2016.
Patches to bugs found in the core operating system often do not reach users of older and lower-priced devices. However, the open-source nature of Android allows security contractors to take existing devices and adapt them for highly secure uses. For example, Samsung has worked with General Dynamics through their Open Kernel Labs acquisition to rebuild Jelly Bean on top of their hardened microvisor for the "Knox" project.
Android smartphones have the ability to report the location of Wi-Fi access points, encountered as phone users move around, to build databases containing the physical locations of hundreds of millions of such access points. These databases form electronic maps to locate smartphones, allowing them to run apps like Foursquare, Google Latitude, Facebook Places, and to deliver location-based ads. Third party monitoring software such as TaintDroid, an academic research-funded project, can, in some cases, detect when personal information is being sent from applications to remote servers.
In 2018, Norwegian security firm Promon has unearthed a serious Android security hole which can be exploited including to steal login credential, access messages, and track location, which the vulnerability could be found in all versions of Android, including Android 10. The vulnerability came by exploiting a bug in multitasking system and enabling malicious app to overlay legitimate apps with fake login screens that the users did not aware when handing security credentials. The users can also be tricked into granting additional permissions to the malicious apps, which later enable the apps to perform all manner of nefarious activities from intercepting texts and calls to stealing banking credentials and money. Avast Threat Labs also discovered that many pre-installed apps of new Android device that containing dangerous malware and adware on several hundred different Android device models and versions. Some of the preinstalled malwares can commit ad fraud, or even take over its host device.
In 2020, the Which? watchdog reported that more than a billion Android devices released in 2012 or earlier, which is 40% of Android devices worldwide, are at risk of being hacked. This conclusion stemmed from the fact that no security updates were issued for the Android versions below 7.0 in 2019. Which? collaborated with the AV Comparatives anti-virus lab to infect five phone models with malware, and it succeeded in each case. Google refused to comment on the watchdog's speculations.
On August 5, 2020, Twitter published a blog urging its users to update their applications to the latest version with regards to a security concern that allowed others to access direct messages. A hacker could easily use the “Android system permissions” to fetch the account credentials in order to do so. The security issue is only with Android OS 8 (Android Oreo) and Android OS 9 (Android Pie). Twitter confirmed that updating the app will restrict such practices.
Technical security features
Android applications run in a sandbox, an isolated area of the system that does not have access to the rest of the system's resources, unless access permissions are explicitly granted by the user when the application is installed, however this may not be possible for pre-installed apps. It is not possible, for example, to turn off the microphone access of the pre-installed camera app without disabling the camera completely. This is valid also in Android versions 7 and 8.
Since February 2012, Google has used its Google Bouncer malware scanner to watch over and scan apps available in the Google Play store. A "Verify Apps" feature was introduced in November 2012, as part of the Android 4.2 "Jelly Bean" operating system version, to scan all apps, both from Google Play and from third-party sources, for malicious behaviour. Originally only doing so during installation, Verify Apps received an update in 2014 to "constantly" scan apps, and in 2017 the feature was made visible to users through a menu in Settings.
Before installing an application, the Google Play store displays a list of the requirements an app needs to function. After reviewing these permissions, the user can choose to accept or refuse them, installing the application only if they accept. In Android 6.0 "Marshmallow", the permissions system was changed; apps are no longer automatically granted all of their specified permissions at installation time. An opt-in system is used instead, in which users are prompted to grant or deny individual permissions to an app when they are needed for the first time. Applications remember the grants, which can be revoked by the user at any time. Pre-installed apps, however, are not always part of this approach. In some cases it may not be possible to deny certain permissions to pre-installed apps, nor be possible to disable them. The Google Play Services app cannot be uninstalled, nor disabled. Any force stop attempt, result in the app restarting itself. The new permissions model is used only by applications developed for Marshmallow using its software development kit (SDK), and older apps will continue to use the previous all-or-nothing approach. Permissions can still be revoked for those apps, though this might prevent them from working properly, and a warning is displayed to that effect.
In September 2014, Jason Nova of Android Authority reported on a study by the German security company Fraunhofer AISEC in antivirus software and malware threats on Android. Nova wrote that "The Android operating system deals with software packages by sandboxing them; this does not allow applications to list the directory contents of other apps to keep the system safe. By not allowing the antivirus to list the directories of other apps after installation, applications that show no inherent suspicious behavior when downloaded are cleared as safe. If then later on parts of the app are activated that turn out to be malicious, the antivirus will have no way to know since it is inside the app and out of the antivirus’ jurisdiction". The study by Fraunhofer AISEC, examining antivirus software from Avast, AVG, Bitdefender, ESET, F-Secure, Kaspersky, Lookout, McAfee (formerly Intel Security), Norton, Sophos, and Trend Micro, revealed that "the tested antivirus apps do not provide protection against customized malware or targeted attacks", and that "the tested antivirus apps were also not able to detect malware which is completely unknown to date but does not make any efforts to hide its malignity".
In August 2013, Google announced Android Device Manager (renamed Find My Device in May 2017), a service that allows users to remotely track, locate, and wipe their Android device, with an Android app for the service released in December. In December 2016, Google introduced a Trusted Contacts app, letting users request location-tracking of loved ones during emergencies.
On October 8, 2018 Google announced new Google Play store requirements to combat over-sharing of potentially sensitive information, including call and text logs. The issue stems from the fact that many apps request permissions to access user's personal information (even if this information is not needed for the app to function) and some users unquestionably grant these permissions. Alternatively, a permission might be listed in the app manifest as required (as opposed to optional) and app would not install unless user grants the permission; user can withdraw any, even required, permission from any app in the device settings after app installation, but few users do this. Google promised to work with developers and create exceptions if their apps require Phone or SMS permissions for "core app functionality". The new policies enforcement started on January 6, 2019, 90 days after policy announcement on October 8, 2018. Furthermore, Google announced a new "target API level requirement" (
targetSdkVersion in manifest) at least Android 8.0 (API level 26) for all new apps and app updates. The API level requirement might combat practice of app developers bypassing some permission screens by specifying early Android versions that had more coarse permission model.
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. 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. 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, 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.
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. 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. 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. There may also be "binary blob" drivers required for certain hardware components in the device. 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.
Leverage over manufacturers
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. 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. 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. The shipment of Android devices without GMS is also common in mainland China, as Google does not do business there.
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. 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, and that shortcuts to Google Search and the Play Store app must be present on or near the main home screen page in its default configuration. 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.
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. 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.
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; 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.
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. The idea of an open-source, Linux-based development platform sparked interest, 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. 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."
Since then Android has grown to become the most widely used smartphone operating system and "one of the fastest mobile experiences available". 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), 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. 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.
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. 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. 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.
Android has suffered from "fragmentation", a situation where the variety of Android devices, in terms of both hardware variations and differences in the software running on them, makes the task of developing applications that work consistently across the ecosystem harder than rival platforms such as iOS where hardware and software varies less. For example, according to data from OpenSignal in July 2013, there were 11,868 models of Android device, numerous different screen sizes and eight Android OS versions simultaneously in use, while the large majority of iOS users have upgraded to the latest iteration of that OS. 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. 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.
Research company Canalys estimated in the second quarter of 2009, that Android had a 2.8% share of worldwide smartphone shipments. By May 2010, Android had a 10% worldwide smartphone market share, overtaking Windows Mobile, whilst in the US Android held a 28% share, overtaking iPhone OS. By the fourth quarter of 2010, its worldwide share had grown to 33% of the market becoming the top-selling smartphone platform, overtaking Symbian. In the US it became the top-selling platform in April 2011, overtaking BlackBerry OS with a 31.2% smartphone share, according to comScore.
By the third quarter of 2011, Gartner estimated that more than half (52.5%) of the smartphone sales belonged to Android. By the third quarter of 2012 Android had a 75% share of the global smartphone market according to the research firm IDC.
In July 2011, Google said that 550,000 Android devices were being activated every day, up from 400,000 per day in May, and more than 100 million devices had been activated with 4.4% growth per week. In September 2012, 500 million devices had been activated with 1.3 million activations per day. In May 2013, at Google I/O, Sundar Pichai announced that 900 million Android devices had been activated.
Android market share varies by location. In July 2012, "mobile subscribers aged 13+" in the United States using Android were up to 52%, and rose to 90% in China. During the third quarter of 2012, Android's worldwide smartphone shipment market share was 75%, with 750 million devices activated in total. In April 2013, Android had 1.5 million activations per day. As of May 2013[update], 48 billion applications ("apps") have been installed from the Google Play store, and by September 2013, one billion Android devices have been activated.
As of August 2020[update], the Google Play store has over 3 million Android applications published, and as of May 2016[update], apps have been downloaded more than 65 billion times. The operating system's success has made it a target for patent litigation as part of the so-called "smartphone wars" between technology companies.
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). At the end of 2013, over 1.5 billion Android smartphones have been sold in the four years since 2010, making Android the most sold phone and tablet OS. Three billion Android smartphones are estimated to be sold by the end of 2014 (including previous years). According to Gartner research company, Android-based devices outsold all contenders, every year since 2012. In 2013, it outsold Windows 2.8:1 or by 573 million. As of 2015[update], Android has the largest installed base of all operating systems; Since 2013, devices running it also sell more than Windows, iOS and Mac OS X devices combined.
According to StatCounter, which tracks only the use for browsing the web, Android is the most popular mobile operating system since August 2013. 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", 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).
While Android phones in the Western world commonly include Google's proprietary add-ons (such as Google Play) to the otherwise open-source operating system, this is increasingly not the case in emerging markets; "ABI Research claims that 65 million devices shipped globally with open-source Android in the second quarter of , 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%).
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. 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."
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.[a] Android has the largest installed base of any mobile operating system and, since 2013, the highest-selling operating system overall with sales in 2012, 2013 and 2014 close to the installed base of all PCs.
In the second quarter of 2014, Android's share of the global smartphone shipment market was 84.7%, a new record. This had grown to 87.5% worldwide market share by the third quarter of 2016, leaving main competitor iOS with 12.1% market share.
According to an April 2017 StatCounter report, Android overtook Microsoft Windows to become the most popular operating system for total Internet usage. It has maintained the plurality since then.
Adoption on tablets
Despite its success on smartphones, initially Android tablet adoption was slow. 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. 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.
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. 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. 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.
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. According to International Data Corporation, shipments of Android-powered tablets surpassed iPads in Q3 2012.
As of the end of 2013, over 191.6 million Android tablets had sold in three years since 2011. This made Android tablets the most-sold type of tablet in 2013, surpassing iPads in the second quarter of 2013.
According to StatCounter's web use statistics, as of August 15, 2017[update], Android tablets represent the majority of tablet devices used in South America (57.46%) and Africa (69.08%), while being a distant second to iOS in North America (25.29%) and Europe (32.64%), despite having sizeable majorities in many Central American, Caribbean, and Eastern European states.) and representing the majority in Asia (51.25%) notably in India (65.98%) and Indonesia (82.18%). Android is an extremely distant second at 11.93% in Oceania as well, mostly due to Australia (10.71%) and New Zealand (16.9%), while in some countries such as Nauru over 80% of tablets are believed to use Android. As well, Android is more often than not used by the minority of web users in Antarctica, which has no permanent population.
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". 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.
As of September 2020[update], Android 10 is the most popular version at 32% and Android 9.0 Pie the next most popular with 27%, giving those two latest releases well over half the share. In several countries is Android 10 alone at or over 50% share (or close to). Android 9.0 alone is also commonly near half of the market share, or over, on smartphones. One in four devices run on version older than Android 8.0, meaning not supported with security updates. On tablets, Android 5.1 Lollipop is the single most widespread version at 16.68% (most Android tablets use unsupported Android versions), and Android KitKat 4.4 thereafter at 15.16%, then Android Pie 9.0 at 11.7%. And Android 10 has grown its share over 10-fold in 8 weeks, to 9%. The usage share of Android on tablets varies a lot by country; still, Lollipop 5.1 is the single version with the greatest usage share in the United States at 32.27%, while a recent Pie 9.0 version is most widespread in e.g. Australia and India, some European countries, and Oreo 8.1 in China, and Egypt. In Australia, Android Pie 9.0 is the most popular at 30.22%, and in India at 25.94%. In some countries, such as Thailand and Kuwait, latest Android 10 is most popular at 20%.
|Version||Marketing name||Release date||API level||Runtime||Launched with|
|11||11||February 19, 2020||30||ART||Google Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL, Pixel 3a, Pixel 3a XL, Pixel 4, Pixel 4XL|
|10||10||September 3, 2019||29||ART||Pixel, Pixel XL, Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL, Pixel 3a, Pixel 3a XL|
|9||Pie||August 6, 2018||28||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|
|8.1||Oreo||December 5, 2017||27||ART||Pixel, Pixel XL, Nexus 6P, Nexus 5X|
|8.0||August 21, 2017||26||ART||N/A|
|7.1||Nougat||October 4, 2016||25||ART||Pixel, Pixel XL|
|7.0||August 22, 2016||24||ART||Nexus 5X, Nexus 6P|
|6.0||Marshmallow||October 5, 2015||23||ART|
|5.1||Lollipop||March 9, 2015||22||ART||Android One|
|5.0||November 3, 2014||21||ART 2.1.0||Nexus 6, Nexus 9|
|4.4||KitKat||October 31, 2013||19||Dalvik (and ART 1.6.0)||Nexus 5|
|4.3||Jelly Bean||July 24, 2013||18||Dalvik||Nexus 7 2013|
|4.2||November 13, 2012||17||Dalvik||Nexus 4, Nexus 10|
|4.1||July 9, 2012||16||Dalvik||Nexus 7|
|4.0||Ice Cream Sandwich||October 19, 2011||15||Dalvik||Galaxy Nexus|
|2.3||Gingerbread||February 9, 2011||10||Dalvik 1.4.0||Nexus S|
As of September 2020[update], 53% of devices have Vulkan support (28% on newer Vulkan 1.1), the successor to OpenGL. At the same time 86.6% of the devices have support for OpenGL ES 3.0 or higher; 60.1% are on latest version OpenGL ES 3.2.
In general, paid Android applications can easily be pirated. 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. 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.
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. 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.
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
On August 12, 2010, Oracle sued Google over claimed infringement of copyrights and patents related to the Java programming language. Oracle originally sought damages up to $6.1 billion, but this valuation was rejected by a United States federal judge who asked Oracle to revise the estimate. 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. 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. The parties agreed to zero dollars in statutory damages for a small amount of copied code. 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.
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. In its announcement, Google claimed this was part of an effort to create a "common code base" between Java on Android and other platforms. 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". In June 2016, a United States federal court ruled in favor of Google, stating that its use of the APIs was fair use.
Anti-competitive challenges in Europe
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. 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. In August 2016, Google was fined US$6.75 million by the Russian Federal Antimonopoly Service (FAS) under similar allegations by Yandex. 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 €4.3 billion (about US$5 billion) and required the company to end this conduct within 90 days. 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.
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.
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. 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 and 55% of the worldwide revenue for Android devices. These include Samsung and HTC. 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. 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.
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. 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. In December 2011, Google bought over a thousand patents from IBM.
Turkey's competition authority investigations about default search engine in Android, started in 2017, led to a 7.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. In December 2019, Google stopped issuing licenses for new Android phone models sold in Turkey.
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, Android TV for televisions, and Android Things for smart devices and Internet of things. 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 Android Auto for cars, and Daydream, a Virtual Reality platform.
The open and customizable nature of Android allows device makers to use it on other electronics as well, including laptops, netbooks, and desktop computers, cameras, headphones, home automation systems, game consoles, media players, satellites, routers, printers, payment terminals, automated teller machines, and robots. Additionally, Android has been installed and run on a variety of less-technical objects, including calculators, single-board computers, feature phones, electronic dictionaries, alarm clocks, refrigerators, landline telephones, coffee machines, bicycles, and mirrors.
Ouya, a video game console running Android, became one of the most successful Kickstarter campaigns, crowdfunding US$8.5m for its development, 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.
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. 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.
Parrot unveiled an Android-based car stereo system known as Asteroid in 2011, followed by a successor, the touchscreen-based Asteroid Smart, in 2012. In 2013, Clarion released its own Android-based car stereo, the AX1. 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."
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. On those platforms Android provides additional functionality for physical keyboards 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.
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. 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." Also, back in 2009, Google co-founder Sergey Brin himself said that Chrome OS and Android would "likely converge over time." 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". That is unlike Android where support is shorter with "EOL dates [being..] at least 3 years [into the future] for Android tablets for education".
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. 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.
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". Due to Android's high popularity in the 2010s, it has become one of the most recognizable icons in the technology world.
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, 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. 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.
- To put the Statistica's numbers in context: by Strategy Analytics estimates, Windows the most popular "desktop" operating system, has an estimated installed base of about 1.3 billion at best; 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.
- "Android Language Breakdown". Open Hub. October 25, 2017. Archived from the original on December 14, 2017. Retrieved December 15, 2017.
- Morrill, Dan (September 23, 2008). "Announcing the Android 1.0 SDK, release 1". Android Developers Blog. Archived from the original on March 5, 2017. Retrieved March 11, 2017.
- Gartenberg, Chaim (September 8, 2020). "Android 11 is here — and not just for Google Pixel phones". The Verge.
- "Android 7.0 Nougat". Archived from the original on August 22, 2016. Retrieved September 5, 2016.
Multi-locale support [..]
New languages supported: Coupled with allowing you to select multiple languages preferences, Android Nougat allows you to select from 100 new languages and 25 locales for commonly used languages such as English, Spanish, French, and Arabic. This enables Apps to better support and understanding your language preferences even if your devices lacks official support for it.
- "android/platform/bionic/". Archived from the original on December 3, 2017.
- "android/platform/external/mksh/". Archived from the original on January 21, 2016.
- "android/platform/external/toybox/toys/". Archived from the original on March 14, 2016.
- "Android gets a toybox". Archived from the original on March 4, 2016.
- "Licenses". Android Source. Archived from the original on December 15, 2016. Retrieved March 11, 2017.
- "Is Android Really Open Source? And Does It Even Matter?". MakeUseOf.
- "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.
- 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.
- "Number of Android applications on the Google Play store". AppBrain. Retrieved August 12, 2020.
- "Google's Android OS: Past, Present, and Future". PhoneArena. August 18, 2011. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- Elgin, Ben (August 17, 2005). "Google Buys Android for Its Mobile Arsenal". Bloomberg Businessweek. Bloomberg L.P. Archived from the original on February 5, 2011. Retrieved March 12, 2017.
- Alabaster, Jay (April 16, 2013). "Android founder: We aimed to make a camera OS". PC World. International Data Group. Archived from the original on May 10, 2017. Retrieved May 9, 2017.
- Welch, Chris (April 16, 2013). "Before it took over smartphones, Android was originally destined for cameras". The Verge. Vox Media. Archived from the original on April 29, 2017. Retrieved May 9, 2017.
- Eadicicco, Lisa (March 27, 2015). "THE RISE OF ANDROID: How a flailing startup became the world's biggest computing platform". Business Insider. Axel Springer SE. Archived from the original on May 20, 2017. Retrieved May 9, 2017.
- Vance, Ashlee (July 29, 2011). "Steve Perlman's Wireless Fix". Bloomberg Businessweek. Bloomberg L.P. Archived from the original on March 19, 2017. Retrieved March 12, 2017.
- Manjoo, Farhad (May 27, 2015). "A Murky Road Ahead for Android, Despite Market Dominance". The New York Times. Archived from the original on July 6, 2017. Retrieved March 12, 2017.
- Block, Ryan (August 28, 2007). "Google is working on a mobile OS, and it's due out shortly". Engadget. AOL. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
- Sharma, Amol; Delaney, Kevin J. (August 2, 2007). "Google Pushes Tailored Phones To Win Lucrative Ad Market". The Wall Street Journal. Archived from the original on July 29, 2017. Retrieved July 24, 2017.
- McKay, Martha (December 21, 2006). "Can iPhone become your phone?; Linksys introduces versatile line for cordless service". The Record (Bergen County). p. L9. Archived from the original on February 5, 2013. Retrieved February 21, 2012.
And don't hold your breath, but the same cell phone-obsessed tech watchers say it won't be long before Google jumps headfirst into the phone biz. Phone, anyone?
- Ionescu, Daniel (April 26, 2012). "Original Android Prototype Revealed During Google, Oracle Trial". PC World. International Data Group. Archived from the original on February 11, 2017. Retrieved March 12, 2017.
- Ziegler, Chris (April 25, 2012). "This was the original 'Google Phone' presented in 2006". The Verge. Vox Media. Archived from the original on March 25, 2017. Retrieved March 12, 2017.
- Ziegler, Chris (April 25, 2012). "Google in 2007: 'a touchscreen cannot completely replace physical buttons'". The Verge. Vox Media. Archived from the original on June 23, 2017. Retrieved March 12, 2017.
- Aamoth, Doug (September 23, 2008). "T-Mobile officially announces the G1 Android phone". TechCrunch. AOL. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- Gao, Richard (September 23, 2016). "Android and its first purchasable product, the T-Mobile G1, celebrate their 8th birthdays today". Android Police. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- "Industry Leaders Announce Open Platform for Mobile Devices". Open Handset Alliance. November 5, 2007. Archived from the original on March 9, 2012. Retrieved March 12, 2017.
- Schonfeld, Erick (November 5, 2007). "Breaking: Google Announces Android and Open Handset Alliance". TechCrunch. AOL. Archived from the original on June 22, 2017. Retrieved March 12, 2017.
- Rubin, Andy (November 5, 2007). "Where's my Gphone?". Official Google Blog. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- Claburn, Thomas (September 19, 2007). "Google's Secret Patent Portfolio Predicts gPhone". InformationWeek. Archived from the original on March 17, 2008. Retrieved March 12, 2017.
- Pearce, James Quintana (September 20, 2007). "Google's Strong Mobile-Related Patent Portfolio". Gigaom. Knowingly, Corp. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- Menon, Murali K. (July 3, 2016). "Android Nougat: Here's why Google names the OS after sweets". The Indian Express. Indian Express Limited. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- Ion, Florence (May 15, 2013). "From Nexus One to Nexus 10: a brief history of Google's flagship devices". Ars Technica. Condé Nast. Archived from the original on June 24, 2017. Retrieved March 12, 2017.
- Hollister, Sean (May 15, 2013). "Google turns the Samsung Galaxy S4 into a Nexus phone, coming June 26th for $649". The Verge. Vox Media. Archived from the original on December 26, 2016. Retrieved March 12, 2017.
- Cunningham, Andrew (July 4, 2013). "Review: The HTC One Google Play edition offers the best of both worlds". Ars Technica. Condé Nast. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- Cunningham, Andrew (January 14, 2014). "Moto G Google Play edition replaces near-stock Android with stock Android". Ars Technica. Condé Nast. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- Cunningham, Andrew (January 25, 2015). "Don't cry for the Google Play edition program; it was already dead". Ars Technica. Condé Nast. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- Chavez, Chris (January 21, 2015). "Google kills off the last remaining Google Play Edition device in the Play Store". Phandroid. Archived from the original on November 29, 2016. Retrieved March 12, 2017.
- Smith, Mat (August 28, 2013). "Android VP Hugo Barra leaves Google, joins Chinese phone maker Xiaomi (updated)". Engadget. AOL. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- Orion, Egan (August 28, 2013). "Google's Android VP Hugo Barra joins Chinese phone maker Xiaomi". The Inquirer. Incisive Media. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- Page, Larry (March 13, 2013). "Update from the CEO". Official Google Blog. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- Arthur, Charles (March 13, 2013). "Andy Rubin moved from Android to take on 'moonshots' at Google". The Guardian. Archived from the original on March 12, 2017. Retrieved March 12, 2017.
- Brandom, Russell (August 10, 2015). "Google is reorganizing and Sundar Pichai will become new CEO". The Verge. Vox Media. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- Conditt, Jessica (August 10, 2015). "Google gets an overhaul and a new CEO: Sundar Pichai". Engadget. AOL. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- Bergen, Mark (October 9, 2015). "New Google CEO Sundar Pichai Makes First Major Executive Picks". Recode. Vox Media. Archived from the original on January 14, 2017. Retrieved March 12, 2017.
- Martonik, Andrew (October 9, 2015). "Sundar Pichai promotes Hiroshi Lockheimer to oversee Android, Chrome OS and Chromecast". Android Central. Mobile Nations. Archived from the original on February 23, 2017. Retrieved March 12, 2017.
- Kastrenakes, Jacob (June 25, 2014). "Android One will help manufacturers build low-cost phones for developing markets". The Verge. Vox Media. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- Seifert, Dan (June 26, 2014). "With Android One, Google is poised to own the entire world". The Verge. Vox Media. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- Woods, Ben (June 25, 2014). "Google announces 'Android One' standard for affordable devices, arriving first in India at under $100". The Next Web. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- Pichai, Sundar (September 15, 2014). "For the next five billion: Android One". Official Google Blog. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- "Android One smartphones released in India". BBC News. September 15, 2014. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- Bergen, Mark (June 11, 2015). "Beset With Failures, Google Tries to Breathe New Life Into Android One". Recode. Vox Media. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- D'Orazio, Dante (August 9, 2015). "Google will take another shot at low-cost Android One initiative". The Verge. Vox Media. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- Lomas, Natasha (August 18, 2015). "Google Pushes Android One To Africa". TechCrunch. AOL. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- Cooper, Daniel (August 18, 2015). "Google brings Android One devices to Africa". Engadget. AOL. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- Efrati, Amir (January 17, 2017). "Google's New Stab at Boosting Android Brand in U.S." The Information. Archived from the original on November 1, 2017. Retrieved November 9, 2017. (subscription required)
- Bohn, Dieter (January 17, 2017). "Low-cost Android One phones reportedly coming to the US". The Verge. Vox Media. Archived from the original on November 3, 2017. Retrieved November 9, 2017.
- Savov, Vlad (October 4, 2016). "Pixel 'phone by Google' announced". The Verge. Vox Media. Archived from the original on October 5, 2016. Retrieved March 13, 2017.
- Lawler, Richard (October 4, 2016). "Google's Pixel phones make their debut". Engadget. AOL. Archived from the original on March 13, 2017. Retrieved March 13, 2017.
- Seifert, Dan (October 4, 2016). "Google's new Pixel phones come with Android 7.1 Nougat". The Verge. Vox Media. Archived from the original on May 11, 2017. Retrieved March 13, 2017.
- Ng, Alfred (October 6, 2016). "Pixel won't share Google Assistant with other Android phones". CNET. CBS Interactive. Archived from the original on March 13, 2017. Retrieved March 13, 2017.
- Bohn, Dieter (October 4, 2016). "The Google Phone". The Verge. Vox Media. Archived from the original on January 6, 2017. Retrieved March 13, 2017.
- Kastrenakes, Jacob (October 4, 2017). "Google Pixel 2 and 2 XL announced with water resistance, 'dual-pixel' camera, and always-on display". The Verge. Vox Media. Archived from the original on October 11, 2017. Retrieved October 12, 2017.
- Sottek, T.C. (May 19, 2019). "Google pulls Huawei's Android license, forcing it to use open source version". The Verge. VOX Media. Retrieved July 20, 2019.
A dramatic escalation in the US war on Chinese tech firms
- Cook, James (May 20, 2019). "Google restricts Huawei from using Android: Here's what that could mean for you". Technology Intelligence. The Telegraph. Retrieved July 20, 2019.
Huawei, which is the world's second largest seller of smartphones after Samsung, has long relied on Google's Android operating system to run its smartphones and tablets. The ban means that new Huawei phones will no longer be able to access certain apps, such as Google Maps and YouTube, and existing phones will not be able to update their Android operating systems.
- Ma, Si (June 11, 2019). "Huawei's operating system in pipeline". Business and Companies. China Daily. Retrieved August 10, 2019.
The move is part of Huawei's broader effort to offset the fallout of the US administration's ban on the world's second-largest smartphone vendor and the world's largest telecom equipment maker.
- Reichert, Corinne (June 14, 2019). "Huawei moves to trademark its own OS while objecting to US ban". Tech News. CNET. Retrieved August 10, 2019.
Huawei is moving to trademark the name of its operating system, "Hongmeng," in Peru.
- Sohail, Omar (May 20, 2019). "Huawei's Own Smartphone Operating System Reportedly Named HongMeng OS, According to Foreign Sources". Mobile tech. Where Consumers Come First (Wccf). Retrieved August 10, 2019.
- Jie, Yang; Strumpf, Dan (May 24, 2019). "Who Needs Google's Android? Huawei Trademarks Its Own Smartphone OS". Tech. The Wall Street Journal. Retrieved August 10, 2019.
Chinese tech giant plans to launch its own operating system this year as access to U.S. software is hit by export ban
- England, Jason (June 14, 2019). "Huawei begins trademarking its Android replacement OS — HongMeng". Android Central. Retrieved August 10, 2019.
The trademark's been filed in Canada, the European Union, Mexico, and more.
- Porter, Jon (August 9, 2019). "Huawei's new operating system is called HarmonyOS". The Verge. Retrieved August 9, 2019.
- Bohn, Dieter (August 22, 2019). "Google deserts desserts: Android 10 is the official name for Android Q". The Verge. Retrieved August 22, 2019.
- Amadeo, Ron (August 22, 2019). "Unsweetened: Android swaps sugary codenames for boring numbers". Ars Technica. Retrieved August 22, 2019.
- "Android's iconic dessert names are going away, starting with Android 10". Android Police. August 22, 2019. Retrieved August 22, 2019.
- "Touch Devices". Android Open Source Project. Archived from the original on January 25, 2012. Retrieved March 12, 2017.
- "Handling Controller Actions". Android Developers. Archived from the original on March 12, 2017. Retrieved March 12, 2017.
- "Handling Keyboard Input". Android Developers. Archived from the original on March 13, 2017. Retrieved March 12, 2017.
- "Sensors Overview". Android Developers. Archived from the original on February 16, 2017. Retrieved March 12, 2017.
- 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.
- "Widgets". Android Developers. Archived from the original on March 12, 2017. Retrieved March 12, 2017.
- "Phones & Tablets". Android Developers. Archived from the original on March 31, 2017. Retrieved March 12, 2017.
- 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.
- 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.
- Begun, Daniel A. "Looking at the Android operating system". For Dummies. Archived from the original on March 12, 2017. Retrieved March 12, 2017.
- "Notifications". Material Design. Archived from the original on March 22, 2017. Retrieved March 12, 2017.
- "Notifications". Android Developers. Archived from the original on December 8, 2012. Retrieved March 12, 2017.
- "Get your apps ready for the 64-bit requirement". Android Developers Blog. Retrieved August 14, 2020.
- 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.
- "Kotlin is now Google's preferred language for Android app development". TechCrunch. Retrieved May 8, 2019.
- 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.
- 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.
- Sinicki, Adam. "I want to develop Android Apps — What languages should I learn?". Android Authority. Retrieved September 12, 2019.
- "Android NDK Native APIs". Android Developers. Archived from the original on March 12, 2017. Retrieved March 12, 2017.
- "C++ Library Support". Android Developers. Archived from the original on March 12, 2017. Retrieved March 12, 2017.
- "package app". GoDoc. Archived from the original on March 29, 2017. Retrieved March 12, 2017.
- "Tools Overview". Android Developers. July 21, 2009. Archived from the original on June 13, 2012.
- 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.
- "Google Acquires Firebase To Help Developers Build Better Real-Time Apps". TechCrunch. Retrieved April 25, 2020.
- "What is Firebase? 15 Reasons to Master It". Firebase Tutorials. December 7, 2019. Retrieved April 25, 2020.
- 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.
- "Google mandates 'Powered by Android' branding on new devices". Geek.com. Archived from the original on March 28, 2014. Retrieved March 28, 2014.
- "Google Play Hits 1 Million Apps". Mashable. July 24, 2013. Archived from the original on January 2, 2014. Retrieved January 2, 2014.
- Warren, Christina. "Google Play Hits 1 Million Apps". Mashable. Archived from the original on May 30, 2014. Retrieved June 4, 2014.
- "Android Compatibility". Android Developers. Archived from the original on October 17, 2013. Retrieved November 16, 2013.
- 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.
- 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.
- 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.
- 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.
- "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.
- 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.
- "Android PSA: Stop Using Task Killer Apps". Phandroid.com. June 16, 2011. Archived from the original on February 17, 2013. Retrieved October 30, 2012.
- 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.
- "Updates". Lifehacker.com. Archived from the original on November 5, 2012. Retrieved November 2, 2012.
- "Android Lollipop". Android Developers. Archived from the original on January 30, 2017. Retrieved March 11, 2017.
- "Support for 64-bit x86". Android Developers. Archived from the original on March 6, 2017. Retrieved March 11, 2017.
- LaPedus, Mark (April 26, 2011). "Update: MIPS gets sweet with Honeycomb". EE Times. AspenCore Media. Archived from the original on March 14, 2017. Retrieved March 11, 2017.
- "NDK Revision History". Android Developers. Retrieved July 17, 2018.
- 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.
- "Android on Intel Architecture". 01.org. July 11, 2013. Archived from the original on February 9, 2014. Retrieved February 9, 2014.
- "ABI Management". Android Developers. Retrieved July 17, 2018.
- Warman, Matt (June 7, 2012). "Orange San Diego Intel Android mobile phone review". The Daily Telegraph. Retrieved June 19, 2013.
- "Android KitKat". Android Developers Portal. android.com. Archived from the original on October 31, 2013. Retrieved November 16, 2013.
- "7.6.1". Android Compatibility Definition Document (PDF) (4.4 ed.). November 27, 2013. p. 33. Archived from the original (PDF) on March 4, 2014.
- "Android Developers: Graphics". android.com. Archived from the original on October 10, 2014. Retrieved November 15, 2013.
- "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.
- "Lenovo N308 Desktop specs". PCWorld. Archived from the original on October 28, 2014. Retrieved November 1, 2014.
- "Remix OS for PC". Archived from the original on September 27, 2017. Retrieved September 22, 2017.
Now powered by Android Marshmallow.
- 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.
- Shawn Knight. "Acer TA272 HUL Android All-in-One Review". TechSpot. Archived from the original on October 28, 2014. Retrieved November 1, 2014.
- "ReleaseNote 4.4-r1 – Android-x86 – Porting Android to x86". Archived from the original on October 28, 2014. Retrieved November 1, 2014.
- "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.
- 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.
- 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.
- "BBC News – China plans new PC operating system in October". BBC News. Archived from the original on November 12, 2014. Retrieved November 1, 2014.
- Paul Mozur (March 5, 2013). "China Criticizes Android's Dominance". WSJ. Retrieved November 1, 2014.
- "China targets own operating system to take on likes of Microsoft, Google". Reuters. Archived from the original on October 28, 2014. Retrieved November 1, 2014.
- "Welcome to the Android Open Source Project!". Android Source. Archived from the original on March 12, 2017. Retrieved March 13, 2017.
- "Android Open Source Project". Archived from the original on December 22, 2017. Retrieved December 22, 2017.
- 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.
- 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.
- 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.
- "Building for devices". Android Open Source Project. Archived from the original on January 7, 2012. Retrieved March 13, 2017.
- 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.
- "OTA Updates". Android Source. Archived from the original on December 25, 2016. Retrieved March 13, 2017.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- Gillmor, Dan (October 28, 2012). "Android's smartphone OS upgrade issues need more than a quick fix". The Guardian. Guardian Media Group. Archived from the original on March 14, 2017. Retrieved March 13, 2017.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- "Fresher OS with Projects Treble and Mainline". Android Developers Blog. Retrieved July 29, 2019.
- "Google says Android 12 will make using third-party app stores easier". The Verge. Retrieved September 28, 2020.
- "Modular Kernel Requirements". Android Open Source Project. August 6, 2018. Retrieved August 7, 2018.
- Hildenbrand, Jerry (January 23, 2012). "What is a kernel?". Android Central. Archived from the original on May 27, 2017. Retrieved June 20, 2017.
- "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.
- "LMG Upstreaming". Linaro. December 5, 2016. Archived from the original on January 9, 2018. Retrieved June 26, 2017.
- 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.
- 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.
- Kroah-Hartman, Greg (December 9, 2010). "Android and the Linux kernel community". Linux kernel monkey log. Retrieved June 20, 2017.
- 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.
- 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.
- 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.
- 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.
- 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.
- Jonathan, Corbet. "Autosleep and wakelocks". LWN. Archived from the original on August 26, 2012.
- "Google Working On Android Based On Linux 3.8". February 28, 2013. Archived from the original on March 2, 2013. Retrieved February 28, 2013.
- "Google working on experimental Linux Kernel 3.10 for Android". Pocketdroid.net. Archived from the original on August 27, 2013. Retrieved September 3, 2013.
- 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.
- Jools Whitehorn. "Android malware gives itself root access | News". TechRadar. Archived from the original on September 1, 2012. Retrieved September 15, 2012.
- 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.
- 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.
- 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.
- Lynch, Jim (August 20, 2013). "Is Android really a Linux distribution?". ITworld. Archived from the original on February 5, 2014. Retrieved April 17, 2014.
- 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.
- 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.
- Wycislik-Wilson, Mark (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.
- 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.
- 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.
- 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.
- Burnette, Ed (June 4, 2008). "Patrick Brady dissects Android". ZDNet. CBS Interactive. Archived from the original on July 5, 2017. Retrieved March 11, 2017.
- 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.
- "Google confirms next Android version won't implement Oracle's proprietary Java APIs". VentureBeat. Archived from the original on December 30, 2015. Retrieved December 30, 2015.
- "Returning BlueZ to Android". LWN.net. May 6, 2014. Archived from the original on June 25, 2014.
- 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.
- "Simple DirectMedia Layer for Android". SDL. August 12, 2012. Archived from the original on June 4, 2012.
- Android gets a toybox Archived March 4, 2016, at the Wayback Machine on lwn.net by Jake Edge (January 14, 2015)
- "Trusty TEE". Archived from the original on October 18, 2016.
- 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.
- 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.
- 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.
- "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.
- OS, Lineage. "Lineage OS – Lineage OS Android Distribution". lineageos.org. Archived from the original on December 25, 2016. Retrieved January 31, 2017.
- "HTC's bootloader unlock page". Htcdev.com. Archived from the original on October 19, 2012. Retrieved September 15, 2012.
- 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.
- 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.
- "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.
- 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.
- Forian, Daniel. "Sony Ericsson supports independent developers – Developer World". Developer.sonyericsson.com. Archived from the original on February 12, 2012. Retrieved September 15, 2012.
- 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.
- "Device codename – XDA-Developers". forum.xda-developers.com. Retrieved March 13, 2019.
- "Documentation of the Build class". Android Developers. Retrieved March 13, 2019.
- Tom Pritchard. "Google Pixel 5 just got a lot more appealing — here's why". Tom's Guide. Retrieved October 5, 2020.
- "Google launches initiative to improve the security of non-Pixel devices". xda-developers. October 2, 2020. Retrieved October 3, 2020.
- "Google is forming an Android security team to find bugs in sensitive apps". xda-developers. October 5, 2020. Retrieved October 5, 2020.
- "Privacy Scandal: NSA Can Spy on Smart Phone Data". September 7, 2013. Retrieved September 7, 2013.
- James Ball. "Angry Birds and 'leaky' phone apps targeted by NSA and GCHQ for user data | World news". theguardian.com. Archived from the original on March 2, 2014. Retrieved February 2, 2014.
- James Ball (January 28, 2014). "Angry Birds firm calls for industry to respond to NSA spying revelations | World news". theguardian.com. Archived from the original on January 30, 2014. Retrieved February 2, 2014.
- "Vault 7: Wikileaks reveals details of CIA's hacks of Android, iPhone Windows, Linux, MacOS, and even Samsung TVs". Computing. March 7, 2017.
- Greenberg, Andy (March 7, 2017). "How the CIA Can Hack Your Phone, PC, and TV (Says WikiLeaks)". WIRED.
- Protalinski, Emil (July 17, 2012). "Android malware numbers explode to 25,000 in June 2012". ZDNet. CBS Interactive. Archived from the original on October 12, 2016. Retrieved March 11, 2017.
- "Mobile malware exaggerated by "charlatan" vendors, says Google engineer". PC Advisor. November 24, 2011. Archived from the original on March 8, 2013. Retrieved November 9, 2012.
- Hildenbrand, Jerry (November 2, 2012). "Android 4.2 brings new security features to scan sideloaded apps". Android Central. Mobile Nations. Archived from the original on April 8, 2017. Retrieved March 11, 2017.
- "Android malware perspective: only 0.5% comes from the Play Store". Phonearena.com. Archived from the original on May 9, 2013. Retrieved March 14, 2013.
- Ludwig, Adrian; Rapaka, Venkat (August 5, 2015). "An Update to Nexus Devices". Official Android Blog. Archived from the original on March 18, 2017. Retrieved March 16, 2017.
- Whitwam, Ryan (August 5, 2015). "Google Announces New Update Policy For Nexus Devices Including Monthly Security Patches For 3 Years And Major OTAs For 2 Years From Release". Android Police. Archived from the original on January 26, 2017. Retrieved March 16, 2017.
- Chester, Brandon (August 5, 2015). "Google Commits To Monthly Security Updates For Nexus Devices". AnandTech. Purch Group. Archived from the original on March 17, 2017. Retrieved March 16, 2017.
- "87% of Android devices insecure". Android Vulnerabilities. University of Cambridge. October 8, 2015. Archived from the original on February 22, 2017. Retrieved March 11, 2017.
- Thomas, Daniel R.; Beresford, Alastair R.; Rice, Andrew. "Security Metrics for the Android Ecosystem" (PDF). Computer Laboratory, University of Cambridge. Archived (PDF) from the original on February 22, 2017. Retrieved March 16, 2017.
- Amadeo, Ron (October 14, 2015). "University of Cambridge study finds 87% of Android devices are insecure". Ars Technica. Condé Nast. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
- Amadeo, Ron (August 6, 2015). "Waiting for Android's inevitable security Armageddon". Ars Technica. Condé Nast. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
- Tung, Liam (August 6, 2015). "After Stagefright, Samsung and LG join Google with monthly Android patches". ZDNet. CBS Interactive. Archived from the original on March 12, 2017. Retrieved March 11, 2017.
- Hildenbrand, Jerry (February 19, 2016). "Monthly security patches are the most important updates you'll never get". Android Central. Mobile Nations. Archived from the original on January 15, 2017. Retrieved March 11, 2017.
- Ludwig, Adrian; Miller, Mel (March 22, 2017). "Diverse protections for a diverse ecosystem: Android Security 2016 Year in Review". Google Security Blog. Archived from the original on March 22, 2017. Retrieved March 22, 2017.
We released monthly Android security updates throughout the year for devices running Android 4.4.4 and up—that accounts for 86.3 percent of all active Android devices worldwide.
- Conger, Kate (March 22, 2017). "Android plans to improve security update speed this year". TechCrunch. AOL. Archived from the original on March 22, 2017. Retrieved March 22, 2017.
- Franceschi-Bicchierai, Lorenzo (July 29, 2015). "Goodbye, Android". Motherboard. Vice Media. Archived from the original on March 16, 2017. Retrieved March 16, 2017.
- Kingsley-Hughes, Adrian (June 9, 2014). "The Android 'toxic hellstew' survival guide". ZDNet. CBS Interactive. Archived from the original on March 27, 2017. Retrieved March 11, 2017.
- "Air-to-ground rocket men flog top-secret mobe-crypto to Brad in accounts". The Register. February 28, 2013. Archived from the original on July 28, 2013. Retrieved August 8, 2013.
- "Samsung Armors Android to Take On BlackBerry". The New York Times. February 28, 2013. Archived from the original on June 23, 2017.
- Steve Lohr (May 8, 2011). "Suit Opens a Window Into Google". The New York Times. ISSN 0362-4331. Archived from the original on November 16, 2012. Retrieved February 16, 2012.
- "AppAnalysis.org: Real Time Privacy Monitoring on Smartphones". March 15, 2018. Archived from the original on March 15, 2012. Retrieved October 9, 2018.
- Ganapati, Priya (September 30, 2010). "Study Shows Some Android Apps Leak User Data Without Clear Notifications | Gadget Lab". Wired.com. Archived from the original on October 4, 2011. Retrieved January 30, 2012.
- A Serious Android bug Could Be Exploited To Steal Your Banking Credentials TechRadar
- Avast Threat Labs analyzed malware that has affected thousands of users around the world Avast
- Google Warning Tens of Millions of Android Phones Come Preloaded With Dangerous Malware Forbes
- "One billion Android devices at risk of hacking". BBC News. March 6, 2020. Retrieved March 6, 2020.
- "Twitter urges Android users to update after breach gives hackers access to private messages". Independent. Retrieved August 6, 2020.
- Sims, Gary (May 30, 2012). "How secure is Android?". Android Authority. Archived from the original on March 16, 2017. Retrieved March 15, 2017.
- Lockheimer, Hiroshi (February 2, 2012). "Android and Security". Google Mobile Blog. Archived from the original on February 27, 2017. Retrieved March 22, 2017.
- Albanesius, Chloe (February 2, 2012). "Google 'Bouncer' Now Scanning Android Market for Malware". PC Magazine. Ziff Davis. Archived from the original on February 27, 2017. Retrieved March 22, 2017.
- Raphael, JR (November 1, 2012). "Exclusive: Inside Android 4.2's powerful new security system". Computerworld. International Data Group. Archived from the original on March 17, 2017. Retrieved March 22, 2017.
- Whitwam, Ryan (February 13, 2017). "Google's Verify Apps now shows apps that it has recently scanned". Android Police. Archived from the original on March 16, 2017. Retrieved March 15, 2017.
- Wiggers, Kyle (February 15, 2017). "Google's virus-scanning Verify Apps feature for Android now reveals its secrets". Digital Trends. Archived from the original on March 16, 2017. Retrieved March 15, 2017.
- "Review app permissions thru Android 5.9". Google Play Help. Archived from the original on March 16, 2017. Retrieved March 15, 2017.
- Mediati, Nick (October 12, 2015). "How to toggle app permissions in Android Marshmallow". Greenbot. International Data Group. Archived from the original on March 7, 2017. Retrieved March 15, 2017.
- Seifert, Dan (May 28, 2015). "Google announces Android M, available later this year". The Verge. Vox Media. Archived from the original on March 28, 2017. Retrieved March 15, 2017.
- Hoffman, Chris (October 11, 2015). "How to Manage App Permissions on Android 6.0". How-To Geek. Archived from the original on March 7, 2017. Retrieved March 6, 2017.
- Wagoner, Ara (November 1, 2015). "How to take advantage of the new App Permissions in Marshmallow". Android Central. Mobile Nations. Archived from the original on May 19, 2017. Retrieved March 6, 2017.
- Nova, Jason (September 14, 2014). "The State of Antivirus for Android". Android Authority. Archived from the original on June 21, 2017. Retrieved March 22, 2017.
- Hager, Ryne (May 17, 2017). "Android Device Manager updated for the first time in two years and renamed to Find My Device [APK Download]". Android Police. Archived from the original on May 17, 2017. Retrieved May 17, 2017.
- Welch, Chris (May 17, 2017). "Google's app for lost Android phones is now called Find My Device". The Verge. Vox Media. Archived from the original on May 17, 2017. Retrieved May 17, 2017.
- Protalinski, Emil (August 2, 2013). "Google announces Android Device Manager coming later this month, an app that helps you find your lost phone". The Next Web. Archived from the original on March 14, 2017. Retrieved March 13, 2017.
- Kastrenakes, Jacob (August 2, 2013). "Google announces tool to track lost Android phones". The Verge. Vox Media. Archived from the original on February 10, 2017. Retrieved March 13, 2017.
- Heater, Brian (December 11, 2013). "Android Device Manager now available for your downloading pleasure on Google Play". Engadget. AOL. Archived from the original on June 2, 2017. Retrieved March 11, 2017.
- Whitwam, Ryan (December 11, 2013). "[New App] Google Releases Android Device Manager App In Play Store". Android Police. Archived from the original on March 14, 2017. Retrieved March 13, 2017.
- Garun, Natt (December 5, 2016). "Google's new Trusted Contacts app lets you share your location during emergencies". The Verge. Vox Media. Archived from the original on April 4, 2017. Retrieved April 4, 2017.
- Lardinois, Frederic (December 5, 2016). "Google's new Trusted Contacts app lets you share your location in emergencies". TechCrunch. AOL. Archived from the original on June 22, 2017. Retrieved April 4, 2017.
- Bradshaw, Kyle (October 8, 2018). "New Play Store policy will help prevent Android call and text data leaks". 9to5Google. Retrieved January 16, 2019.
- "Providing a safe and secure experience for our users". Android Developers Blog. Retrieved January 16, 2019.
- Boulton, Clint (October 21, 2008). "Google Open-Sources Android on Eve of G1 Launch". eWeek. Retrieved February 17, 2012.
- Paul, Ryan (November 6, 2007). "Why Google chose the Apache Software License over GPLv2 for Android". Ars Technica. Condé Nast. Archived