Android - Revision history

Sojourna: /* Consumer impact summary */

2026-04-09T04:08:39Z

Consumer impact summary

← Older revision		Revision as of 04:08, 9 April 2026
Line 16:		Line 16:

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

Sojourna: Clean-up; pass on style; removed Accio citation - it is AI; added note for last Incident sub-section.

2026-04-09T04:08:19Z

Clean-up; pass on style; removed Accio citation - it is AI; added note for last Incident sub-section.

Show changes

89.240.169.46 at 19:21, 8 April 2026

2026-04-08T19:21:48Z

← Older revision		Revision as of 19:21, 8 April 2026
Line 11:		Line 11:
	\|Website= https://android.com/		\|Website= https://android.com/
	}}		}}
	[[wikipedia:Android_(operating_system)\|'''Android''']] is an operating system which started in 2003, ~~got~~ acquired by '''[[Google]]''' in 2005<ref>{{Cite web \|last=Elgin \|first=Ben \|date=2005-08-17 \|title=Google Buys Android for Its Mobile Arsenal \|url=http://www.businessweek.com/technology/content/aug2005/tc20050817_0949_tc024.htm \|url-status=dead \|archive-url=https://web.archive.org/web/20110227182929/http://www.businessweek.com/technology/content/aug2005/tc20050817_0949_tc024.htm \|archive-date=2011-02-27 \|access-date=2025-07-12 \|website=Bloomberg Businessweek}}</ref>, and made its first official release (Android 1.0) in 2008.<ref>{{Cite web \|date=2008-09-23 \|title=Announcing the Android 1.0 SDK, release 1 \|url=https://android-developers.googleblog.com/2008/09/announcing-android-10-sdk-release-1.html \|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\|access-date=2025-07-12 \|website=Android Developers Blog}}</ref> It is based on a modified version of the 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 \|date=2025 \|title=Why Android? \|url=https://www.android.com/why-android/ \|url-status=live \|archive-url=http://web.archive.org/web/20260221233734/https://www.android.com/why-android/ \|archive-date=21 Feb 2026\|access-date=2025-07-12 \|website=Android}}</ref>		[[wikipedia:Android_(operating_system)\|'''Android''']] is an operating system which started in 2003, was acquired by '''[[Google]]''' in 2005<ref>{{Cite web \|last=Elgin \|first=Ben \|date=2005-08-17 \|title=Google Buys Android for Its Mobile Arsenal \|url=http://www.businessweek.com/technology/content/aug2005/tc20050817_0949_tc024.htm \|url-status=dead \|archive-url=https://web.archive.org/web/20110227182929/http://www.businessweek.com/technology/content/aug2005/tc20050817_0949_tc024.htm \|archive-date=2011-02-27 \|access-date=2025-07-12 \|website=Bloomberg Businessweek}}</ref>, and made its first official release (Android 1.0) in 2008.<ref>{{Cite web \|date=2008-09-23 \|title=Announcing the Android 1.0 SDK, release 1 \|url=https://android-developers.googleblog.com/2008/09/announcing-android-10-sdk-release-1.html \|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\|access-date=2025-07-12 \|website=Android Developers Blog}}</ref> It is based on a modified version of the [[wikipedia:Linux_kernel\|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 \|date=2025 \|title=Why Android? \|url=https://www.android.com/why-android/ \|url-status=live \|archive-url=http://web.archive.org/web/20260221233734/https://www.android.com/why-android/ \|archive-date=21 Feb 2026\|access-date=2025-07-12 \|website=Android}}</ref>

	The original "philosophy and goals" page of Android stated that it 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 \|title=Philosophy and Goals \|url=http://source.android.com/about/philosophy.html \|url-status=dead \|archive-url=https://web.archive.org/web/20120111091238/http://source.android.com/about/philosophy.html \|archive-date=11 Jan 2012 \|website=Android Open Source Project}}</ref> This founding principle was abandoned with the [[Android Developer Verification]] plan announced in 2025 that is scheduled to come in effect in September of 2026.		The original "philosophy and goals" page of Android stated that it 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 \|title=Philosophy and Goals \|url=http://source.android.com/about/philosophy.html \|url-status=dead \|archive-url=https://web.archive.org/web/20120111091238/http://source.android.com/about/philosophy.html \|archive-date=11 Jan 2012 \|website=Android Open Source Project}}</ref> This founding principle was abandoned with the [[Android Developer Verification]] plan announced in 2025 that is scheduled to come in effect in September of 2026.

2001:4BC9:B009:90BE:2205:B7FF:FE00:E700: /* References */ 14: fix name

2026-03-30T20:46:06Z

References: 14: fix name

← Older revision		Revision as of 20:46, 30 March 2026
Line 30:		Line 30:

	===Apps cannot run writable files===		===Apps cannot run writable files===
	Apps targeting Android 10 aren't allowed to execute files from their "home" folder, as this is enforced by the system.<ref>{{Cite web \|title=Behavior changes: apps targeting API 29+ \|url=https://developer.android.com/about/versions/10/behavior-changes-10#execute-permission \|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=2026-02-09 \|access-date=2026-03-02 \|website=Android Developers}}</ref> While "targeting" any version is an opt-in choice, the [[wikipedia:Google_Play\|Google Play Store]] policy forbids apps that target old Android versions.<ref>https://developer.android.com/google/play/requirements/target-sdk</ref><ref>[https://support.google.com/googleplay/android-developer/answer/16561298?hl=en https://support.google.com/googleplay/android-developer/answer/16561298]</ref><ref>https://support.google.com/googleplay/android-developer/answer/11926878</ref> This negatively impacts apps such as [[wikipedia:Termux\|Termux]],<ref>{{Cite web \|first=~~n0n3m4~~ \|date=2019-03-18 \|title=No more exec from data folder on targetAPI >= Android Q \|url=https://github.com/termux/termux-app/issues/1072 \|access-date=2026-03-02 \|website=GitHub}}</ref> which must be "[[Sideloading\|sideloaded]]" so that the policy is not applicable, otherwise they must find a way to bypass it (risks legal issues).<ref>{{Cite web \|last=Kang \|first=Jinoh \|date=2021-07-03 \|title=Revisit the Android W^X problem \|url=https://github.com/termux/termux-app/issues/2155 \|access-date=2026-03-02 \|website=GitHub}}</ref>		Apps targeting Android 10 aren't allowed to execute files from their "home" folder, as this is enforced by the system.<ref>{{Cite web \|title=Behavior changes: apps targeting API 29+ \|url=https://developer.android.com/about/versions/10/behavior-changes-10#execute-permission \|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=2026-02-09 \|access-date=2026-03-02 \|website=Android Developers}}</ref> While "targeting" any version is an opt-in choice, the [[wikipedia:Google_Play\|Google Play Store]] policy forbids apps that target old Android versions.<ref>https://developer.android.com/google/play/requirements/target-sdk</ref><ref>[https://support.google.com/googleplay/android-developer/answer/16561298?hl=en https://support.google.com/googleplay/android-developer/answer/16561298]</ref><ref>https://support.google.com/googleplay/android-developer/answer/11926878</ref> This negatively impacts apps such as [[wikipedia:Termux\|Termux]],<ref>{{Cite web \|last=n0n3m4 \|first= \|date=2019-03-18 \|title=No more exec from data folder on targetAPI >= Android Q \|url=https://github.com/termux/termux-app/issues/1072 \|access-date=2026-03-02 \|website=GitHub}}</ref> which must be "[[Sideloading\|sideloaded]]" so that the policy is not applicable, otherwise they must find a way to bypass it (risks legal issues).<ref>{{Cite web \|last=Kang \|first=Jinoh \|date=2021-07-03 \|title=Revisit the Android W^X problem \|url=https://github.com/termux/termux-app/issues/2155 \|access-date=2026-03-02 \|website=GitHub}}</ref>

	===Blocking sideloading of unverified Android apps (2026-2027)===		===Blocking sideloading of unverified Android apps (2026-2027)===

Rudxain: link Termux

2026-03-02T07:52:37Z

link Termux

← Older revision		Revision as of 07:52, 2 March 2026
Line 30:		Line 30:

	===Apps cannot run writable files===		===Apps cannot run writable files===
	Apps targeting Android 10 aren't allowed to execute files from their "home" folder, as this is enforced by the system.<ref>{{Cite web \|title=Behavior changes: apps targeting API 29+ \|url=https://developer.android.com/about/versions/10/behavior-changes-10#execute-permission \|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=2026-02-09 \|access-date=2026-03-02 \|website=Android Developers}}</ref> While "targeting" any version is an opt-in choice, the [[wikipedia:Google_Play\|Google Play Store]] policy forbids apps that target old Android versions.<ref>https://developer.android.com/google/play/requirements/target-sdk</ref><ref>[https://support.google.com/googleplay/android-developer/answer/16561298?hl=en https://support.google.com/googleplay/android-developer/answer/16561298]</ref><ref>https://support.google.com/googleplay/android-developer/answer/11926878</ref> This negatively impacts apps such as Termux,<ref>{{Cite web \|first=n0n3m4 \|date=2019-03-18 \|title=No more exec from data folder on targetAPI >= Android Q \|url=https://github.com/termux/termux-app/issues/1072 \|access-date=2026-03-02 \|website=GitHub}}</ref> which must be "[[Sideloading\|sideloaded]]" so that the policy is not applicable, otherwise they must find a way to bypass it (risks legal issues).<ref>{{Cite web \|last=Kang \|first=Jinoh \|date=2021-07-03 \|title=Revisit the Android W^X problem \|url=https://github.com/termux/termux-app/issues/2155 \|access-date=2026-03-02 \|website=GitHub}}</ref>		Apps targeting Android 10 aren't allowed to execute files from their "home" folder, as this is enforced by the system.<ref>{{Cite web \|title=Behavior changes: apps targeting API 29+ \|url=https://developer.android.com/about/versions/10/behavior-changes-10#execute-permission \|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=2026-02-09 \|access-date=2026-03-02 \|website=Android Developers}}</ref> While "targeting" any version is an opt-in choice, the [[wikipedia:Google_Play\|Google Play Store]] policy forbids apps that target old Android versions.<ref>https://developer.android.com/google/play/requirements/target-sdk</ref><ref>[https://support.google.com/googleplay/android-developer/answer/16561298?hl=en https://support.google.com/googleplay/android-developer/answer/16561298]</ref><ref>https://support.google.com/googleplay/android-developer/answer/11926878</ref> This negatively impacts apps such as [[wikipedia:Termux\|Termux]],<ref>{{Cite web \|first=n0n3m4 \|date=2019-03-18 \|title=No more exec from data folder on targetAPI >= Android Q \|url=https://github.com/termux/termux-app/issues/1072 \|access-date=2026-03-02 \|website=GitHub}}</ref> which must be "[[Sideloading\|sideloaded]]" so that the policy is not applicable, otherwise they must find a way to bypass it (risks legal issues).<ref>{{Cite web \|last=Kang \|first=Jinoh \|date=2021-07-03 \|title=Revisit the Android W^X problem \|url=https://github.com/termux/termux-app/issues/2155 \|access-date=2026-03-02 \|website=GitHub}}</ref>

	===Blocking sideloading of unverified Android apps (2026-2027)===		===Blocking sideloading of unverified Android apps (2026-2027)===

Rudxain: add "Apps cannot run writable files" section

2026-03-02T07:42:59Z

add "Apps cannot run writable files" section

← Older revision		Revision as of 07:42, 2 March 2026
Line 28:		Line 28:
	==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]].		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 aren't allowed to execute files from their "home" folder, as this is enforced by the system.<ref>{{Cite web \|title=Behavior changes: apps targeting API 29+ \|url=https://developer.android.com/about/versions/10/behavior-changes-10#execute-permission \|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=2026-02-09 \|access-date=2026-03-02 \|website=Android Developers}}</ref> While "targeting" any version is an opt-in choice, the [[wikipedia:Google_Play\|Google Play Store]] policy forbids apps that target old Android versions.<ref>https://developer.android.com/google/play/requirements/target-sdk</ref><ref>[https://support.google.com/googleplay/android-developer/answer/16561298?hl=en https://support.google.com/googleplay/android-developer/answer/16561298]</ref><ref>https://support.google.com/googleplay/android-developer/answer/11926878</ref> This negatively impacts apps such as Termux,<ref>{{Cite web \|first=n0n3m4 \|date=2019-03-18 \|title=No more exec from data folder on targetAPI >= Android Q \|url=https://github.com/termux/termux-app/issues/1072 \|access-date=2026-03-02 \|website=GitHub}}</ref> which must be "[[Sideloading\|sideloaded]]" so that the policy is not applicable, otherwise they must find a way to bypass it (risks legal issues).<ref>{{Cite web \|last=Kang \|first=Jinoh \|date=2021-07-03 \|title=Revisit the Android W^X problem \|url=https://github.com/termux/termux-app/issues/2155 \|access-date=2026-03-02 \|website=GitHub}}</ref>

	===Blocking sideloading of unverified Android apps (2026-2027)===		===Blocking sideloading of unverified Android apps (2026-2027)===
	{{Main\|Google blocking sideloading of unverified Android apps}}		{{Main\|Google blocking sideloading of unverified Android apps}}
	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<ref>{{Cite web \|last=Whitwam \|first=Ryan \|date=26 Aug 2025 \|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/ \|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 \|access-date=26 Aug 2025 \|website=ArsTechnica}}</ref><ref>{{Cite web \|date=26 Aug 2025 \|title=Google's plan to end sideloading on Android \|url=https://xdaforums.com/t/googles-plan-to-end-sideloading-on-android.4756353/ \|url-status=live \|archive-url=https://web.archive.org/web/20250826161809/https://xdaforums.com/t/googles-plan-to-end-sideloading-on-android.4756353/ \|archive-date=26 Aug 2025 \|access-date=26 Aug 2025 \|website=XdaForums}}</ref>. The policy is aimed to be enforced worldwide in 2027. Devices without Google Mobile Service (GMS) or running a third-party ROM will be unaffected. However it's hard for users to bypass/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 \|date=3 Apr 2022 \|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/ \|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 \|access-date=26 Aug 2025 \|website=XdaForums}}</ref>.		Starting September 2026, unmodified Android devices in Brazil, Indonesia, Singapore and Thailand will no longer be allowed to install applications outside of the Play Store unless the developer has verified their identity with Google<ref>{{Cite web \|last=Whitwam \|first=Ryan \|date=26 Aug 2025 \|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/ \|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 \|access-date=26 Aug 2025 \|website=ArsTechnica}}</ref><ref>{{Cite web \|date=26 Aug 2025 \|title=Google's plan to end sideloading on Android \|url=https://xdaforums.com/t/googles-plan-to-end-sideloading-on-android.4756353/ \|url-status=live \|archive-url=https://web.archive.org/web/20250826161809/https://xdaforums.com/t/googles-plan-to-end-sideloading-on-android.4756353/ \|archive-date=26 Aug 2025 \|access-date=26 Aug 2025 \|website=XdaForums}}</ref>. The policy is aimed to be enforced worldwide in 2027. Devices without Google Mobile Service (GMS) or running a third-party ROM will be unaffected. However it's hard for users to bypass/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 \|date=3 Apr 2022 \|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/ \|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 \|access-date=26 Aug 2025 \|website=XdaForums}}</ref>.

	===Data collection===		===Data collection===
Line 54:		Line 57:

	Update : Google is now releasing QPR1 update for AOSP 16 after 2 months delay<ref>{{Cite web \|last=Mishaal \|first=Rahman \|date=12 Nov 2025 \|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/ \|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 \|access-date=12 Nov 2025 \|website=Android Authority}}</ref>		Update : Google is now releasing QPR1 update for AOSP 16 after 2 months delay<ref>{{Cite web \|last=Mishaal \|first=Rahman \|date=12 Nov 2025 \|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/ \|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 \|access-date=12 Nov 2025 \|website=Android Authority}}</ref>


	==References==		==References==
	<references />		<references />
	[[Category:{{PAGENAME}}]]		[[Category:{{PAGENAME}}]]

Rudxain: minor reword, link Chromecast to G-Cast

2026-03-02T06:57:11Z

minor reword, link Chromecast to G-Cast

← Older revision		Revision as of 06:57, 2 March 2026
Line 48:		Line 48:
	In Android, streaming over network is referred as "Casting". In Android 4.4, [[wikipedia:Miracast\|Miracast]] support was introduced.		In Android, streaming over network is referred as "Casting". In Android 4.4, [[wikipedia:Miracast\|Miracast]] support was introduced.

	In Android 9, Miracast (an open standard) was fully replaced ~~with~~ proprietary Chromecast-protocol. ~~Chromecast protocol~~ 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 multichannel Hi-Fi audio on Android unless the receiver has a valid vendor signature.<ref>{{Cite web \|last=Weiske \|first=Christian \|date=2025-08-31 \|title=Android/Lineage OS and Screen mirroring ("Cast") \|url=https://p.cweiske.de/669 \|url-status=live \|archive-url=https://web.archive.org/web/20250831142415/https://p.cweiske.de/669 \|archive-date=2025-08-31 \|access-date=2025-08-31}}</ref>		In Android 9, Miracast (an open standard) was fully replaced by the proprietary [[wikipedia: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 multichannel Hi-Fi audio on Android unless the receiver has a valid vendor signature.<ref>{{Cite web \|last=Weiske \|first=Christian \|date=2025-08-31 \|title=Android/Lineage OS and Screen mirroring ("Cast") \|url=https://p.cweiske.de/669 \|url-status=live \|archive-url=https://web.archive.org/web/20250831142415/https://p.cweiske.de/669 \|archive-date=2025-08-31 \|access-date=2025-08-31}}</ref>

	==='''Google delaying AOSP 16 QPR1 update without proper explanation'''===		==='''Google delaying AOSP 16 QPR1 update without proper explanation'''===

Rudxain: fix hyphen in heading; replace Miracast explanation by link. BTW, my prev edit also fixed a typo

2026-03-02T06:50:48Z

fix hyphen in heading; replace Miracast explanation by link. BTW, my prev edit also fixed a typo

← Older revision		Revision as of 06:50, 2 March 2026
Line 45:		Line 45:
	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.		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===		===Android Cast restricted to Google-signed receivers===
	In Android, streaming over network is referred as "Casting". In Android 4.4 Miracast support was introduced~~. Miracast is an open standard by the Wi-Fi-alliance which makes it possible to stream screen contents as well as high-quality multichannel audio over wireless networks~~.		In Android, streaming over network is referred as "Casting". In Android 4.4, [[wikipedia:Miracast\|Miracast]] support was introduced.

	In Android 9, Miracast was fully replaced with proprietary Chromecast-protocol. Chromecast protocol 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 multichannel Hi-Fi audio on Android unless the receiver has a valid vendor signature.<ref>{{Cite web \|last=Weiske \|first=Christian \|date=2025-08-31 \|title=Android/Lineage OS and Screen mirroring ("Cast") \|url=https://p.cweiske.de/669 \|url-status=live \|archive-url=https://web.archive.org/web/20250831142415/https://p.cweiske.de/669 \|archive-date=2025-08-31 \|access-date=2025-08-31}}</ref>		In Android 9, Miracast (an open standard) was fully replaced with proprietary Chromecast-protocol. Chromecast protocol 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 multichannel Hi-Fi audio on Android unless the receiver has a valid vendor signature.<ref>{{Cite web \|last=Weiske \|first=Christian \|date=2025-08-31 \|title=Android/Lineage OS and Screen mirroring ("Cast") \|url=https://p.cweiske.de/669 \|url-status=live \|archive-url=https://web.archive.org/web/20250831142415/https://p.cweiske.de/669 \|archive-date=2025-08-31 \|access-date=2025-08-31}}</ref>

	==='''Google delaying AOSP 16 QPR1 update without proper explanation'''===		==='''Google delaying AOSP 16 QPR1 update without proper explanation'''===

Rudxain: fix hyphens

2026-03-02T06:43:58Z

fix hyphens

← Older revision		Revision as of 06:43, 2 March 2026
Line 46:		Line 46:

	===Android Cast restricted to Google -signed receivers===		===Android Cast restricted to Google -signed receivers===
	In Android, streaming over network is referred as "Casting". In Android 4.4 Miracast support was introduced. Miracast is an open standard by the Wi-Fi -alliance which makes it possible to stream screen contents as well as high quality multichannel audio over wireless networks.		In Android, streaming over network is referred as "Casting". In Android 4.4 Miracast support was introduced. Miracast is an open standard by the Wi-Fi-alliance which makes it possible to stream screen contents as well as high-quality multichannel audio over wireless networks.

	In Android 9, Miracast was fully replaced with ~~proprietrary~~ Chromecast -protocol. Chromecast protocol 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 multichannel Hi-Fi audio on Android unless the receiver has a valid vendor signature.<ref>{{Cite web \|last=Weiske \|first=Christian \|date=2025-08-31 \|title=Android/Lineage OS and Screen mirroring ("Cast") \|url=https://p.cweiske.de/669 \|url-status=live \|archive-url=https://web.archive.org/web/20250831142415/https://p.cweiske.de/669 \|archive-date=2025-08-31 \|access-date=2025-08-31}}</ref>		In Android 9, Miracast was fully replaced with proprietary Chromecast-protocol. Chromecast protocol 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 multichannel Hi-Fi audio on Android unless the receiver has a valid vendor signature.<ref>{{Cite web \|last=Weiske \|first=Christian \|date=2025-08-31 \|title=Android/Lineage OS and Screen mirroring ("Cast") \|url=https://p.cweiske.de/669 \|url-status=live \|archive-url=https://web.archive.org/web/20250831142415/https://p.cweiske.de/669 \|archive-date=2025-08-31 \|access-date=2025-08-31}}</ref>

	==='''Google delaying AOSP 16 QPR1 update without proper explanation'''===		==='''Google delaying AOSP 16 QPR1 update without proper explanation'''===

Rudxain: link "root" to Jailbreak

2026-03-02T06:38:36Z

link "root" to Jailbreak

← Older revision		Revision as of 06:38, 2 March 2026
Line 31:		Line 31:
	===Blocking sideloading of unverified Android apps (2026-2027)===		===Blocking sideloading of unverified Android apps (2026-2027)===
	{{Main\|Google blocking sideloading of unverified Android apps}}		{{Main\|Google blocking sideloading of unverified Android apps}}
	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<ref>{{Cite web \|last=Whitwam \|first=Ryan \|date=26 Aug 2025 \|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/ \|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 \|access-date=26 Aug 2025 \|website=ArsTechnica}}</ref><ref>{{Cite web \|date=26 Aug 2025 \|title=Google's plan to end sideloading on Android \|url=https://xdaforums.com/t/googles-plan-to-end-sideloading-on-android.4756353/ \|url-status=live \|archive-url=https://web.archive.org/web/20250826161809/https://xdaforums.com/t/googles-plan-to-end-sideloading-on-android.4756353/ \|archive-date=26 Aug 2025 \|access-date=26 Aug 2025 \|website=XdaForums}}</ref>. The policy is aimed to be enforced worldwide in 2027. Devices without Google Mobile Service (GMS) or running a third-party ROM will be unaffected. However it's hard for users to bypass/spoof [[Google Play Integrity API\|Google Play Integrity]] to hide their ROM or root status to use utility apps such as most of banking apps<ref>{{Cite web \|date=3 Apr 2022 \|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/ \|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 \|access-date=26 Aug 2025 \|website=XdaForums}}</ref>.		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<ref>{{Cite web \|last=Whitwam \|first=Ryan \|date=26 Aug 2025 \|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/ \|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 \|access-date=26 Aug 2025 \|website=ArsTechnica}}</ref><ref>{{Cite web \|date=26 Aug 2025 \|title=Google's plan to end sideloading on Android \|url=https://xdaforums.com/t/googles-plan-to-end-sideloading-on-android.4756353/ \|url-status=live \|archive-url=https://web.archive.org/web/20250826161809/https://xdaforums.com/t/googles-plan-to-end-sideloading-on-android.4756353/ \|archive-date=26 Aug 2025 \|access-date=26 Aug 2025 \|website=XdaForums}}</ref>. The policy is aimed to be enforced worldwide in 2027. Devices without Google Mobile Service (GMS) or running a third-party ROM will be unaffected. However it's hard for users to bypass/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 \|date=3 Apr 2022 \|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/ \|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 \|access-date=26 Aug 2025 \|website=XdaForums}}</ref>.

	===Data collection===		===Data collection===