Android: Difference between revisions
mNo edit summary |
|||
| (35 intermediate revisions by 24 users not shown) | |||
| Line 1: | Line 1: | ||
{{StubNotice}} | {{StubNotice}} | ||
{{ | {{ProductLineCargo | ||
| | |ArticleType= Product | ||
| | |Category= Software | ||
| | |Company= Google | ||
| | |InProduction= Yes | ||
| | |Logo= Android Logo.svg | ||
| | |ReleaseYear= 2008 | ||
|Website= https://android.com/ | |||
|Description= Android is the world's most widely used mobile operating system, with over 3.5 billion active users. Android devices collect extensive user data, often without clear opt-out options. Google's Android System SafetyCore was installed silently on all devices in 2025. Many manufacturers lock bootloaders, making it difficult for users to modify their software. Starting in 2026, third-party apps will face restrictions in several regions. Google's Chromecast protocol limits casting to Google-signed receivers. Google delayed the AOSP 16 QPR1 update without explanation. | |||
}} | }} | ||
'''{{Wplink|Android (operating_system)|Android}}''' is an operating system which started in 2003 and was acquired by '''[[Google]]''' in 2005,<ref>{{Cite web |last=Elgin |first=Ben |title=Google Buys Android for Its Mobile Arsenal |url=http://www.businessweek.com/technology/content/aug2005/tc20050817_0949_tc024.htm |website=Bloomberg Businessweek |date=17 Aug 2005 |access-date=12 Jul 2025 |url-status=dead |archive-url=https://web.archive.org/web/20110227182929/http://www.businessweek.com/technology/content/aug2005/tc20050817_0949_tc024.htm |archive-date=27 Feb 2011}}</ref> which made its first official release (Android 1.0) in 2008.<ref>{{Cite web |author= |title=Announcing the Android 1.0 SDK, release 1 |url=https://android-developers.googleblog.com/2008/09/announcing-android-10-sdk-release-1.html |website=Android Developers Blog |date=23 Sep 2008 |access-date=8 Apr 2026 |url-status=live |archive-url=http://web.archive.org/web/20251216120521/https://android-developers.googleblog.com/2008/09/announcing-android-10-sdk-release-1.html |archive-date=16 Dec 2025}}</ref> It is based on a modified version of the {{Wplink|Linux kernel}} and other open-source software, designed primarily for touchscreen-based mobile devices such as smartphones and tablets, but is also used in smart TVs, cameras, in-car infotainment systems, etc.<ref>{{Cite web |author= |title=Why Android? |url=https://www.android.com/why-android/ |website=Android |date= |access-date=12 Jul 2025 |url-status=live |archive-url=http://web.archive.org/web/20260221233734/https://www.android.com/why-android/ |archive-date=21 Feb 2026}}</ref> | |||
The original "philosophy and goals" page of Android stated that its aim was "to make sure that there was no central point of failure, where one industry player could restrict or control the innovations of any other".<ref>{{Cite web |author= |title=Philosophy and Goals |url=http://source.android.com/about/philosophy.html |website=Android |date= |access-date= |url-status=dead |archive-url=https://web.archive.org/web/20120111091238/http://source.android.com/about/philosophy.html |archive-date=11 Jan 2012}}</ref> This founding principle was abandoned with the [[Android Developer Verification]] plan announced in 2025 that is scheduled to come in effect in September 2026. | |||
==Consumer impact summary== | ==Consumer impact summary== | ||
{{Ph-C-CIS}} | |||
With over 3.5 billion active users, open-source flexibility, affordability, and extensive device ecosystems continue to shape consumer behavior, regional adoption, and technological advancements.<ref name=":0">{{Cite web |last=G. |first=Nick |title=Android Market Share in 2025: Global Dominance and Key Insights |url=https://techjury.net/industry-analysis/android-market-share |website=techjury |date=4 Sep 2024 |access-date=8 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20250629102621/https://techjury.net/industry-analysis/android-market-share/ |archive-date=29 Jun 2025}}</ref> Android's global reach, affordability, and device diversity make it the preferred OS for billions, particularly in emerging economies. It remains the world's most widely used mobile operating system, but its dominance has been accompanied by controversies from security vulnerabilities and privacy concerns to accusations of anti-competitive behavior and declining open-source commitments. | |||
===Market control=== | |||
Android remains the world's dominant mobile operating system (OS) as of 2025, holding a 72.23% global market share compared to iOS with 27.39%.<ref name=":0" /> | |||
*Asia & Africa: Android dominates with 95.16% in India, 86.8% in Indonesia, and 80.88% in Africa due to affordability and device variety.<ref name=":0" /><ref name=":2">{{Cite web |last1=Qadir |first1=Salam |last2=Shaikh |first2=Sohaib |title=Android vs iOS Statistics 2025: Users, Revenue, and Global Trends |url=https://www.tekrevol.com/blogs/android-vs-ios-statistics/ |website=Tekrevol |date=10 Apr 2025 |access-date=15 May 2025 |url-status=deviated |archive-url=https://web.archive.org/web/20250515022542/https://www.tekrevol.com/blogs/android-vs-ios-statistics/ |archive-date=15 May 2025}}</ref> | |||
*North America: Android holds 45% market share, trailing iOS (57.68%) in the U.S.A.<ref name=":0" /><ref name=":3">{{Cite web |last=Howarth |first=Josh |title=iPhone vs Android User Stats (2025 Data) |url=https://explodingtopics.com/blog/iphone-android-users |website=ExplodingTopics |date=24 Apr 2025 |access-date=8 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20250709235506/https://explodingtopics.com/blog/iphone-android-users |archive-date=9 Jul 2025}}</ref> | |||
*Europe: Android leads with 65% market share, though iOS is strong in the UK (52.29%).<ref name=":0" /><ref name=":3" /> | |||
*Affordability: Android devices range from $100 budget phones to premium flagships, making them accessible in emerging markets.<ref name=":0" /><ref name=":2" /> | |||
*Device Variety: Multiple manufacturers ([[Samsung]], [[Xiaomi]], [[Oppo]]) offer diverse options, unlike Apple's closed ecosystem.<ref name=":4">{{Cite web |last=Frąckiewicz |first=Marcin |title=Smartphone Wars 2025: Inside the Global Market Shake-Up, Trends, and Future Tech Disruptions |url=https://ts2.tech/en/smartphone-wars-2025-inside-the-global-market-shake-up-trends-and-future-tech-disruptions/ |website=Techstock<sup>2</sup> |date=16 May 2025 |access-date=8 Apr 2025 |url-status=live |archive-url=https://web.archive.org/web/20250720045846/https://ts2.tech/en/smartphone-wars-2025-inside-the-global-market-shake-up-trends-and-future-tech-disruptions/ |archive-date=20 Jul 2025}}</ref> | |||
==Incidents== | ==Incidents== | ||
This is a list of all consumer protection incidents related to this software. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]]. | |||
===Apps cannot run writable files=== | |||
Apps targeting Android 10 are not allowed to execute files from their "home" folder, as this is enforced by the system.<ref>{{Cite web |author= |title=Behavior changes: apps targeting API 29+ | |||
|url=https://developer.android.com/about/versions/10/behavior-changes-10#execute-permission |website=Android |date= |access-date=2 Mar 2026 |url-status=live |archive-url=https://web.archive.org/web/20260209004831/https://developer.android.com/about/versions/10/behavior-changes-10#execute-permission |archive-date=9 Feb 2026}}</ref> While "targeting" any version is an opt-in choice, [[Google Play]] policy forbids apps that target old Android versions.<ref>{{Cite web |author= |title=Meet Google Play's target API level requirement |url=https://developer.android.com/google/play/requirements/target-sdk |website=Android |date= |access-date=8 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20260318030349/https://developer.android.com/google/play/requirements/target-sdk |archive-date=18 Mar 2026}}</ref><ref>{{Cite web |author= |title=Google Play's Target API Level Policy |url=https://support.google.com/googleplay/android-developer/answer/16561298?hl=en |website=[[Google]] |date= |access-date=8 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20260211153736/https://support.google.com/googleplay/android-developer/answer/16561298?hl=en |archive-date=11 Feb 2026}}</ref><ref>{{Cite web |author= |title=Target API level requirements for Google Play apps |url=https://support.google.com/googleplay/android-developer/answer/11926878 |website=[[Google]] |date= |access-date=8 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20260318030448/https://support.google.com/googleplay/android-developer/answer/11926878 |archive-date=18 Mar 2026}}</ref> This negatively impacts apps such as {{Wplink|Termux}},<ref>{{Cite web |author=n0n3m4 |title=No more exec from data folder on targetAPI >= Android Q |url=https://github.com/termux/termux-app/issues/1072 |website=[[GitHub]] |date=18 Mar 2019 |access-date=2 Mar 2026 |url-status=live |archive-url=https://web.archive.org/web/20260315024821/https://github.com/termux/termux-app/issues/1072 |archive-date=15 Mar 2026}}</ref> which must be "[[Sideloading|sideloaded]]" so that the policy is not applicable, otherwise they must find a way to bypass it (risking legal issues).<ref>{{Cite web |last=Kang <!-- Display name is "iamahuman" as of 8 Apr 2026. -Sojourna --> |first=Jinoh |title=Revisit the Android W^X problem |url=https://github.com/termux/termux-app/issues/2155 |website=[[GitHub]] |date=3 Jul 2021 |access-date=2 Mar 2026 |url-status=live |archive-url=https://web.archive.org/web/20260315024819/https://github.com/termux/termux-app/issues/2155 |archive-date=15 Mar 2026}}</ref> | |||
===Blocking sideloading of unverified Android apps (''2026—2027'')=== | |||
{{Main|Google Android restrict app sideloading}} | |||
Google announced in August 2025 that starting September 2026, unmodified Android devices in Brazil, Indonesia, Singapore and Thailand will no longer be allowed to install applications outside of the [[Google Play]] store unless the developer has verified their identity with Google. The policy is aimed to be enforced world-wide in 2027.<ref>{{Cite web |last=Whitwam |first=Ryan |title=Google will block sideloading of unverified Android apps starting next year |url=https://arstechnica.com/gadgets/2025/08/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |website=ArsTechnica |date=26 Aug 2025 |access-date=8 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20250826032858/https://arstechnica.com/gadgets/2025/08/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |archive-date=26 Aug 2025}}</ref><ref>{{Cite web |author=DoorStepSamm |title=Google's plan to end sideloading on Android | |||
|url=https://xdaforums.com/t/googles-plan-to-end-sideloading-on-android.4756353/ |website=XDA |date=26 Aug 2025 |access-date=8 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20260409033222/https://xdaforums.com/t/ongoing-september-2026-googles-plan-to-end-sideloading-on-android.4756353/ |archive-date=9 Apr 2026}}</ref> Devices without Google Mobile Service (GMS) or running a third-party {{Wplink|Read-only memory|ROM}} will be unaffected. However it's hard for users to bypass or spoof [[Google Play Integrity API|Google Play Integrity]] to hide their ROM or [[Jailbreak|root]] status to use utility apps such as most of banking apps.<ref>{{Cite web |author=HippoMan |title=[Discussion] The root-and-mod-hiding/fingerprint-spoofing/keybox-stealing cat-and-mouse game |url=https://xdaforums.com/t/discussion-the-root-and-mod-hiding-fingerprint-spoofing-keybox-stealing-cat-and-mouse-game.4425939/ |website=XDA |date=3 Apr 2022 |access-date=8 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20250823095950/https://xdaforums.com/t/discussion-the-root-and-mod-hiding-fingerprint-spoofing-keybox-stealing-cat-and-mouse-game.4425939/ |archive-date=23 Aug 2025}}</ref> | |||
===Data collection=== | |||
{{Main|Android data collection}} | |||
Android mobile devices, even when minimally configured, collect and share extensive user data with Google and provide few options for opting-out, raising privacy concerns. Settings for opting-out of sharing data with Google are generally hard to find, requiring users to search the device's settings and Google's settings to locate and toggle the settings on or off. The data shared with Google is sensitive user data including call logs, messages, data recorded from the device's microphone and camera, and more. This data is used by Google to improve the targeting of personalized advertisements and as training data for [[Google Gemini]]. | |||
===Android System SafetyCore silent install=== | |||
{{Main|Android System SafetyCore}} | |||
On 22 January 2025, Google quietly rolled out Android System SafetyCore to all Android devices. The installation of the program neither informed consumers that it was installed, nor did it request consumers to install it onto their devices.<ref>{{Cite web |last=Baran |first=Guru |title=Google’s SafetyCore App Secretly Scans All Your Photos on Android Phones |url=https://cybersecuritynews.com/googles-safetycore-app-secretly-scans/ |website=Cyber Security News |date=27 Feb 2025 |access-date=8 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20250227210543/https://cybersecuritynews.com/googles-safetycore-app-secretly-scans/ |archive-date=27 Feb 2025}}</ref> | |||
=== | ===OEM Locked Bootloaders=== | ||
{{ | {{Main|Motorola}} | ||
In | |||
In North America, many Android devices like phones or tablets will not allow consumers to unlock and do what they want to modify the software. Therefore, it has been incredibly difficult and nearly impossible to root and install custom ROMs on the device unless an exploit has been found. Some OEMs like [[Samsung]] are now completely blocking [[bootloader unlocking]] on their phones regardless of region. | |||
===Android Cast restricted to Google-signed receivers=== | |||
In Android, streaming over network is referred as "Casting". In Android 4.4, {{Wplink|Miracast}} support was introduced. | |||
In Android 9, Miracast (an open standard) was fully replaced by the proprietary {{Wplink|Google Cast|Chromecast protocol}} (Google Cast). Google Cast includes signing key verification of both the Cast source and receiver device, meaning that since Android 9 it is no longer possible to cast high quality content to receivers which aren't signed by Google. This means that unlike AirPlay on Apple devices, there's no way to stream multi-channel Hi-Fi audio on Android unless the receiver has a valid vendor signature.<ref>{{Cite web |last=Weiske |first=Christian |title=Android/Lineage OS and Screen mirroring ("Cast") |url=https://p.cweiske.de/669 |website=p.cweiske.de |date=31 Aug 2025 |access-date=8 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20250831142415/https://p.cweiske.de/669 |archive-date=31 Aug 2025}}</ref> | |||
===Google delaying AOSP 16 QPR1 update without proper explanation=== | |||
''NOTE: This section needs to be re-written in past tense, the technical verbiage explained or linking to the relevant Wikipedia page using <nowiki>{{Wplink}}</nowiki>, and how it is applicable from a consumer rights standpoint (otherwise should be deleted). Also remember to check for spelling, punctuation, and grammar.'' | |||
Google is releasing Android 16 QPR1 update for Pixel devices on September 3, 2025, normally AOSP will get QPR1 update in 24-48 hours after Pixel devices. But until now, there still no QPR1 update for AOSP. Google later told Android Authority said they will release the source code "in the coming weeks." But they doesn't explain why they delaying QPR1 update for AOSP 16<ref>{{Cite web |last=Mishaal |first=Rahman |title=Android 16 QPR1’s source code is nowhere to be found, but Google swears it’s coming |url=https://www.androidauthority.com/android-16-qpr1-source-code-delay-3596650/ |website=Android Authority |date=10 Sep 2025 |access-date=18 Oct 2025 |url-status=live |archive-url=https://web.archive.org/web/20250911142548/https://www.androidauthority.com/android-16-qpr1-source-code-delay-3596650/ |archive-date=11 Sep 2025}}</ref> | |||
Update : Google is now releasing QPR1 update for AOSP 16 after 2 months delay<ref>{{Cite web |last=Mishaal |first=Rahman |title=The wait is over: Android 16 QPR1's source code is now available on AOSP |url=https://www.androidauthority.com/android-16-qpr1-source-code-available-3614853/ |website=Android Authority |date=12 Nov 2025 |access-date=12 Nov 2025 |url-status=live |archive-url=https://web.archive.org/web/20251112032612/https://www.androidauthority.com/android-16-qpr1-source-code-available-3614853/ |archive-date=12 Nov 2025}}</ref> | |||
==References== | ==References== | ||
{{Reflist}} | |||
[[Category: | |||
[[Category:{{PAGENAME}}]] | |||
[[Category:Google]] | [[Category:Google]] | ||
[[Category: | [[Category:Operating systems]] | ||