Free Download Android Language Project Download

Language packs are generated automatically from the work of translators on the. For more details, see the. Additional language packs may be installed on your Moodle site via Administration >Site administration >Language >Language packs, or manually. For more details, see the.

The 'Sooner' prototype phone, running a pre-release version of Android Android Inc. Was founded in in October 2003 by,, 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, 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 and Microsoft. Rubin had difficulty attracting investors early on, and Android was facing eviction from its office space., 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, 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. Google marketed the platform to and on the promise of providing a flexible, upgradeable system.

May 23, 2017. Android Language Project Full Version. The inventors of the bittorrent protocol and developers of the #1 bittorrent download client. Language pack. For BitTorrent 7.10.0 build. Android By.What is Android Language Project Crack Full Version Free. More information about Android Language Project Crack. Sample Multilingual Android App. Throughout this tutorial we've used a sample application, written especially to explain how to create multilingual Android apps. Feel free to download it and experiment yourself: ICL-LocalizationExample.zip (4MB).

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'. Speculation about Google's intention to enter the mobile communications market continued to build through December 2006. An early had a close resemblance to a phone, with no touchscreen and a physical, but the arrival of 2007's 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'. In September 2007, covered an Evalueserve study reporting that Google had filed several applications in the area of mobile telephony.

And at a 2012 press conference announcing Google's Nexus 7 tablet On November 5, 2007, the, a of technology companies including Google, device manufacturers such as, and, wireless carriers such as and, and chipset makers such as and, unveiled itself, with a goal to develop 'the first truly open and comprehensive platform for mobile devices'. The first commercially available smartphone running Android was the, also known as T-Mobile G1, announced on September 23, 2008. In 2007, the green Android logo was designed for Google by graphic designer.

The design team was tasked with a project to create a universally identifiable icon with the specific inclusion of a robot in the final design. After numerous design developments based on and space movies, the team eventually sought inspiration from the human symbol on restroom doors and modified the figure into a robot shape. As Android is open-source, it was agreed that the logo should be likewise, and since its launch the green logo has been reinterpreted into countless variations on the original design. Since 2008, Android has seen which have incrementally improved the operating system, adding new features and fixing 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 ', ', ', and ', in that order. During its announcement of 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 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 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 ' software with 'timely [.] updates'. At its in May 2013, Google announced a special version of the, 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 program, and was followed by other devices, including the Google Play edition, and Google Play edition. In 2015, 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, served as product spokesperson, representing Android at press conferences and, Google’s annual developer-focused conference. He left Google in August 2013 to join Chinese phone maker. Less than six months earlier, Google's then- announced in a blog post that Andy Rubin had moved from the Android division to take on new projects at Google, and that 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 conglomerate, making the new head of Android. In June 2014, Google announced, 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, 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 in October 2016, marketed as being the first phones made by Google, and exclusively featured certain software features, such as the, before wider rollout. The Pixel phones replaced the Nexus series, with a new generation of Pixel phones launched in October 2017. See also: Interface Android's default user interface is mainly based on, 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.

And full-size physical are supported via. 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 to the user. Internal hardware, such as, and 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 by rotating the device, simulating control of a. Android devices boot to the homescreen, the primary navigation and information 'hub' on Android devices, analogous to the found on personal computers. Android homescreens are typically made up of app icons and; app icons launch the associated app, whereas widgets display live, auto-updating content, such as a, the user's email inbox, or a 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 and other app stores can extensively re- the homescreen, and even mimic the look of other operating systems, such as. 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, '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. See also: and Applications ('), which extend the functionality of devices, are written using the kit (SDK) and, often, the programming language.

Java may be combined with /, together with a choice of non-default that allow better C++ support. The programming language is also supported, although with a limited set of (API). In May 2017, Google announced support for Android app development in the. The SDK includes a comprehensive set of development tools, including a,, a handset based on, documentation, sample code, and tutorials. Initially, Google's supported (IDE) was using the Android Development Tools (ADT) plugin; in December 2014, Google released, based on, as its primary IDE for Android application development. Other development tools are available, including a (NDK) for applications or extensions in C or C++,, a visual environment for novice programmers, and various.

In January 2014, Google unveiled an framework based on for porting to Android, wrapped in a native application shell. Android has a growing selection of third-party applications, which can be acquired by users by downloading and installing the application's (Android application package) file, or by downloading them using an program that allows users to from their devices. 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 July 2013, there are more than one million applications available for Android in Play Store. As of July 2013, 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, 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,, and SlideMe., another alternative marketplace, seeks to only provide applications that are distributed under.

Memory management Since Android devices are usually battery-powered, Android is designed to manage processes to keep power consumption at a minimum. When an application is not in use the system 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 longest. Lifehacker reported in 2011 that third-party task killers were doing more harm than good. See also: The main hardware platform for Android is the ( and architectures), with,, and architectures also officially supported in later versions of Android.

The unofficial project provided support for the x86 architectures ahead of the official support. MIPS architecture was also supported before Google did. Since 2012, Android devices with 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.

Since Android 5.0 'Lollipop', variants of all platforms are supported in addition to the variants. Requirements for the minimum amount of 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 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. Android 4.4 requires a, or architecture processor (latter two through unofficial ports), together with an 2.0 compatible (GPU). Android supports OpenGL ES 1.1, 2.0, 3.0, 3.1 and as of latest major version, 3.2 and.

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,,, dedicated gaming controls,,, barometers,,,, thermometers, and.

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 camera, which was relaxed to a camera if present at all, since the camera was dropped as a requirement entirely when Android started to be used on. 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 that is part of the, 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 green figure, next to its original packaging Android is developed by until the latest changes and updates are ready to be released, at which point the is made available to the Android Open Source Project (AOSP), an initiative led by Google. The AOSP code can be found without modification on select devices, mainly the and series of devices. The source code is, in turn, customized and adapted by (OEMs) to run on their hardware. Also, Android's source code does not contain the often proprietary that are needed for certain hardware components. As a result, most Android devices, including Google's own, ultimately ship with a combination of and software, with the software required for accessing Google services falling into the latter category. Update schedule.

See also: Google announces major incremental upgrades to Android on a yearly basis. The updates can be installed on devices. The latest major release is, announced in March 2017, and released the following August. Compared to its primary rival mobile operating system, 's, Android updates typically reach various devices with significant delays.

Except for devices within the Google Nexus brand, updates often arrive months after the release of the new version, or not at all. This is partly due to the extensive variation in in Android devices, to which each upgrade must be specifically tailored, a time- and resource-consuming process. Manufacturers often prioritize their newest devices and leave old ones behind. Additional delays can be introduced by wireless carriers that, after receiving updates from manufacturers, further customize and brand Android to their needs and conduct extensive testing on their networks before sending the upgrade out to users. There are also situations in which upgrades are not possible due to one manufacturing partner not providing necessary updates to.

The extensive variation of hardware in Android devices causes significant delays for software upgrades, with new versions of the operating system and typically taking months before reaching consumers, or sometimes not at all. 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'.

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 decoupling certain aspects of the operating system (particularly its core applications) so they could be updated through the store independently of the OS.

One of those components,, is a system-level process providing for Google services, installed automatically on nearly all devices running and higher. With these changes, Google can add new system functionality through Play Services and update apps without having to distribute an upgrade to the operating system itself. As a result, contained relatively fewer user-facing changes, focusing more on minor changes and platform improvements. In May 2016, 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 carriers' slow approval time due to testing on their networks, despite some carriers, including and, having already shortened their respective approval times. '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 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. 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, 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.

Linux kernel Android's is based on one of the 's (LTS) branches. As of 2017, Android devices mainly use versions 3.18 or 4.4 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 (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, 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 that 'Android is not Linux', with adding that 'Let me make it simple for you, without Linux, there is no Android'.

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, 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, 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 Android off the latest stable Linux versions. The 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 access to the operating system and sensitive partitions such as /system are. However, root access can be obtained by exploiting in Android, which is used frequently by the to enhance the capabilities of their devices, but also by malicious parties to install and.

Android is a according to the, Google's open-source chief, and several journalists. Others, such as Google engineer Patrick Brady, say that Android is not Linux in the traditional Linux distribution sense; Android does not include the (it uses as an alternative C library) and some of other components typically found in Linux distributions. With the release of in 2017, Google began to require that devices shipped with new processor chips had Linux kernel version 4.4 or newer, for security reasons.

Existing devices upgraded to Oreo, and new products launched with older processor chips, were exempt from this rule. Software stack. Android's architecture diagram On top of the Linux kernel, there are the, and written in, and running on an which includes -compatible libraries. Change Sizing Software Engineering. Development of the Linux kernel continues independently of other Android's source code bases. Until version 5.0, Android used as a with to run Dalvik 'dex-code' (Dalvik Executable), which is usually translated from the. Following the trace-based JIT principle, in addition to the majority of application code, Dalvik performs the compilation and of select frequently executed code segments ('traces') each time an application is launched.

Android 4.4 introduced (ART) as a new runtime environment, which uses to entirely compile the application bytecode into upon the installation of an application. Architectural And Cultural Guide Pyongyang Pdf To Jpg there. 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.

For its Java library, the Android platform uses a subset of the now discontinued project. In December 2015, Google announced that the next version of Android would switch to a Java implementation based on. Android's,, was developed by Google specifically for Android, as a derivation of the '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 (glibc) or are its smaller runtime footprint, and optimization for low-frequency CPUs.

At the same time, Bionic is licensed under the terms of the, which Google finds more suitable for the Android's overall licensing model. Aiming for a different licensing model, toward the end of 2012, Google switched the Bluetooth stack in Android from the GPL-licensed to the Apache-licensed BlueDroid. Android does not have a native by default, nor does it support the full set of standard libraries. This made it difficult to port existing Linux applications or libraries to Android, until version r5 of the brought support for applications written completely in. Libraries written in C may also be used in applications by injection of a small and usage of the.

Since Marshmallow, ', a collection of command line utilities (mostly for use by apps, as Android doesn't provide a by default), replaced similar 'Toolbox' collection. 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 ' 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.'

Open-source community Android's is released by Google under an, 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. Community releases often come pre- and contain modifications not provided by the original vendor, such as the ability to or the device's processor. Was the most widely used community firmware, now discontinued and succeded. Historically, device manufacturers and mobile carriers have typically been unsupportive of third-party 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, for which carriers would otherwise charge a premium. As a result, technical obstacles including locked 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 that permits the ' of mobile devices, manufacturers and carriers have softened their position regarding third party development, with some, including,, and, providing support and encouraging development. As a result of this, over time the need to circumvent to install unofficial firmware has lessened as an increasing number of devices are shipped with unlocked or unlockable, similar to 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. Security and privacy.

See also: and Scope of surveillance by public institutions As part of the broader it was revealed in September 2013 that the American and British intelligence agencies, the (NSA) and (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, which collect personal information of their users for advertising and other commercial reasons. GCHQ has, according to, a -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 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 are in compliance with all relevant domestic and international laws, although the Guardian stated 'the latest disclosures could also add to mounting public concern about how the technology sector collects and uses information, especially for those outside the US, who enjoy fewer privacy protections than Americans.' Common security threats Research from security company lists premium service abuse as the most common type of Android malware, where text messages are sent from infected phones to 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 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 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 series would begin to receive monthly security. 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.' The following October, researchers at the concluded that 87.7% of Android phones in use had known but unpatched due to lack of updates and support. Ron Amadeo of 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, 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 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 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,,, 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.

Technical security features Android applications run in a, 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. Since February 2012, Google has used its 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 operating system version, to scan all apps, both from Google Play and from third-party sources, for malicious behavior.

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 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, 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.

The new permissions model is used only by applications developed for Marshmallow using its (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 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,,,,,,,,,, and, 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. Licensing The for Android is: 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 ) under the 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 version 2, developed by the, with the source code publicly available at all times. Typically, Google collaborates with a hardware manufacturer to produce a flagship device (part of the Nexus series) featuring the new version of Android, then makes the source code available after that device has been released. 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 in an official Android blog post, was because Honeycomb was rushed for production of the, 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, which includes applications such as, Google Search, and – a software layer that provides 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 and ) may also replace certain stock Android apps with their own proprietary variants and add additional software not included in the stock Android operating system. There may also be ' required for certain hardware components in the device. Some stock applications in AOSP code that were formerly used by earlier versions of Android, such as Search, Music, and Calendar, have been by Google in favor of replacements distributed through Play Store (Google Search, Google Play Music, and Google Calendar) that are no longer open-source. Moreover, open-source variants of some applications also exclude functions that are present in their non-free versions, such as Photosphere panoramas in Camera, and a page on the default home screen (exclusive to the proprietary version 'Google Now Launcher', whose code is embedded within that of the main Google application). And the have been critical of Android and have recommended the usage of alternatives such as, because drivers and firmware vital for the proper functioning of Android devices are usually proprietary, and because the Google Play Store application can forcibly install or deinstall applications and, as a result, invite non-free software; although the Free Software Foundation has not found Google to use it for malicious reasons. Leverage over manufacturers Google licenses their Google Mobile Services software, along with Android trademarks, only to hardware manufacturers for devices that meet Google's compatibility standards specified in the Android Compatibility Program document. 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.

Examples of such Android forks are 's (which is used on the line of tablets, and oriented toward Amazon services), the (a fork used by the, oriented primarily toward and services), and other forks that exclude Google apps due to the general unavailability of Google services in certain regions (such as ). 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. 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, was forced by Google to halt production on a device powered by 's 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 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. Running on an ASUS netbook; Android has been unofficially ported to traditional PCs for use as a desktop operating system. Android received a lukewarm reaction when it was unveiled in 2007.

Although analysts were impressed with the respected technology companies that had partnered with Google to form the Open Handset Alliance, it was unclear whether mobile phone manufacturers would be willing to replace their existing operating systems with Android. The idea of an open-source, Linux-based 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: 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 (), (), (),, and others to the software and release hardware running their own customised version of Android. As a result, it has been described by technology website 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. 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, 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 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 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 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. Market share.

Main article: Research company Canalys estimated in the second quarter of 2009, that Android had a 2.8% share of worldwide shipments. By May 2010, Android had a 10% worldwide smartphone market share, overtaking, whilst in the US Android held a 28% share, overtaking. By the fourth quarter of 2010, its worldwide share had grown to 33% of the market becoming the top-selling smartphone platform, overtaking. In the US it became the top-selling platform in April 2011, overtaking with a 31.2% smartphone share, according to comScore. By the third quarter of 2011, 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, 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, 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 February 2017, the store has over 2.7 million Android applications published, and As of May 2016, 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 ' 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, Android has the largest of all operating systems; Since 2013, devices running it also sell more than Windows, iOS and Mac OS X devices combined.

According to, 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 commonly include Google's proprietary add-ons (such as Google Play) to the otherwise open-source operating system, this is increasingly not the case in emerging markets; 'ABI Research claims that 65 million devices shipped globally with open-source Android in the second quarter of [2014], up from 54 million in the first quarter'; depending on country, percent of phones estimated to be based only on 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 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 and combined, and over three times more than. Gartner expected the whole mobile phone market to 'reach two billion units in 2016', including Android. Describing the statistics, Farhad Manjoo wrote in that 'About one of every two computers sold today is running Android.

[It] has become Earth’s dominant computing platform.' According to a '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. Android has the largest installed base of any 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 with 12.1% market share.

According to an April 2017 report, Android overtook Microsoft Windows to become the most popular operating system for total Internet usage. It has maintained the plurality since then. In September 2015, Google announced that Android had 1.4 billion monthly active users. This changed to 2 billion monthly active users in May 2017.

Adoption on tablets. The tablet, running Android 4.1 Jelly Bean Despite its success on smartphones, initially Android tablet adoption was slow. One of the main causes was the 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 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 was reinforced by the large number of tablet-specific applications.

Despite app support in its infancy, a considerable number of Android tablets (alongside those using other operating systems, such as the and ) 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, failed to gain market traction with consumers as well as damaging the early reputation of Android tablets. Furthermore, several Android tablets such as the were priced the same or higher than the, which hurt sales. An exception was the, 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 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, Android tablets represent the majority of tablet devices used in (57.46%) and (69.08%), while being a distant second to iOS in North America (25.29%) and Europe (32.64%), despite having sizeable majorities in many,, and states. ) and representing the majority in Asia (51.25%) notably in India (65.98%) and (82.18%).

Android is an extremely distant second at 11.93% in as well, mostly due to (10.71%) and (16.9%), while in some countries such as 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, which has no permanent population. In March 2016, Galen Gruman of 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 's devices are'.

A year earlier, Gruman had stated that 's own were 'better on iOS and Android' than on Microsoft's own devices. Platform usage. Gingerbread (0.4%) Charts in this section provide breakdowns of Android versions, based on devices accessing the in a seven-day period ending on December 11, 2017. Therefore, these statistics exclude devices running various Android that do not access the Google Play Store, such as Amazon's. Further information:,, and 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.

On August 12, 2010, sued Google over claimed infringement of copyrights and patents related to the 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, a implementation of the Java class libraries, and an independently developed virtual machine called.

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 for a small amount of copied code. On May 9, 2014, the partially reversed the district court ruling, ruling in Oracle's favor on the copyrightability issue, and the issue of to the district court. In December 2015, Google announced that the next major release of Android () would switch to, 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 (GPL) with a, 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. In addition to lawsuits against Google directly, various 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 and Microsoft have sued several manufacturers for patent infringement, with Apple's ongoing 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 and.

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 its own Android software to patent licenses, requiring the bundling of and 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 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.

In 2013,, a lobbying organization supported by Microsoft, Oracle and others, filed a complaint regarding Android with the, alleging that its free-of-charge distribution model constituted anti-competitive. The, 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 (FAS) under similar allegations. A which runs Android Google has developed several variations of Android for specific use cases, including for wearable devices such as wrist watches, for televisions, for cars, Brillo, later renamed, for smart devices and, and, a Virtual Reality platform.

The open and customizable nature of Android allows to use it on other electronics as well, including laptops,, and desktop computers, cameras, headphones, home automation systems, game consoles, media players, satellites,,,,, and. Additionally, Android has been installed and run on a variety of less-technical objects, including calculators,,,,, refrigerators, telephones, coffee machines,, and mirrors., a video game console running Android, became one of the most successful campaigns, US$8.5m for its development, and was later followed by other Android-based consoles, such as 's – an Android device in a 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 services provider to bring Google products into customers' homes. Unveiled an Android-based system known as Asteroid in 2011, followed by a successor, the touchscreen-based Asteroid Smart, in 2012. In 2013, released its own Android-based car stereo, the AX1.

In January 2014, at the (CES), Google announced the formation of the, a group including several major automobile makers (,,, and ) and, which aims to produce Android-based 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 ) and can also be installed on by end users. On those platforms Android provides additional functionality for physical and, together with the ' 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, 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.'

And 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 ' dates [being.] at least 3 years [into the future] for Android tablets for education'.

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