Consumer Rights Wiki

Deceptive language frequently used against consumers: Difference between revisions

← Older editNewer edit →
VisualWikitext
Lucros (talk | contribs)
2 edits
Fixed a few tone issues and added citations
Line 14: Line 14:
<blockquote>
<blockquote>
Google says you should think of the new requirements like checking IDs at the airport.
Google says you should think of the new requirements like checking IDs at the airport.
</blockquote>Google is implying to users that "because it's necessary and accepted there, it's just as necessary here too". This is an invalid comparison given that airplanes belong to their respective airlines while a smartphone belongs to the person who purchased it. It is more similar to Google installing an airport security station infront of home owners' doorsteps. Google takes ownership away from smartphone buyers by assuming the final authority on which software can run on Android devices.
</blockquote>Critics argued the comparison was misleading, noting that airlines own their aircraft, while consumers own their smartphones. <ref>{{Cite web |last=Sohn |first=Jiyoung |date=2026-03-23 |title=Ads Are Popping Up on the Fridge and It Isn’t Going Over Well |url=https://www.wsj.com/lifestyle/samsung-refrigerator-ads-lg-whirlpool-ge-10ea7bcc |url-status=live |archive-url=https://web.archive.org/web/20260326132248/https://www.wsj.com/lifestyle/samsung-refrigerator-ads-lg-whirlpool-ge-10ea7bcc |archive-date=2026-03-23 |access-date=2026-04-09 |website=The Wall Street Journal}}</ref>


===Storage access restrictions in Android===
===Storage access restrictions in Android===
Line 23: Line 23:
</blockquote>
</blockquote>


The only "security" storage access framework actually gives the user is that it prevents them from granting access to the root directory of the external storage (not to be confused with "root access" which gives the device owner superuser privileges).
In practice, Storage Access Framework's main restriction is preventing apps from accessing the root directory of external storage.


Storage Access Framework is no replacement for legacy storage access given its slowness from its large processing overhead. The performance loss may be concealed to some extent from the fast hardware smartphones have nowadays, but even then, it increases battery usage. In addition, it breached compatibility with all apps previously developed over the span of several years.<ref name="SAF">[https://www.xda-developers.com/android-q-storage-access-framework-scoped-storage/ The Storage Access Framework is the only way for apps to work with all your files in Android Q. And it's terrible.] - XDA developers ([https://web.archive.org/web/20260222042955/https://www.xda-developers.com/android-q-storage-access-framework-scoped-storage/ Archived])</ref><ref name=":0">{{Cite web |date=14 Apr 2017 |title=Horrible access storage framework performance |url=https://old.reddit.com/r/androiddev/comments/65dn8x/horrible_access_storage_framework_performance/ |archive-url=https://web.archive.org/web/20250823190730/https://old.reddit.com/r/androiddev/comments/65dn8x/horrible_access_storage_framework_performance/ |archive-date=23 Aug 2025 |website=[[Reddit]] - r/androiddev}}</ref>
Storage Access Framework is no replacement for legacy storage access given its slowness from its large processing overhead. The performance loss may be concealed to some extent from the fast hardware smartphones have nowadays, but even then, it increases battery usage. In addition, it breached compatibility with all apps previously developed over the span of several years.<ref name="SAF">[https://www.xda-developers.com/android-q-storage-access-framework-scoped-storage/ The Storage Access Framework is the only way for apps to work with all your files in Android Q. And it's terrible.] - XDA developers ([https://web.archive.org/web/20260222042955/https://www.xda-developers.com/android-q-storage-access-framework-scoped-storage/ Archived])</ref><ref name=":0">{{Cite web |date=14 Apr 2017 |title=Horrible access storage framework performance |url=https://old.reddit.com/r/androiddev/comments/65dn8x/horrible_access_storage_framework_performance/ |archive-url=https://web.archive.org/web/20250823190730/https://old.reddit.com/r/androiddev/comments/65dn8x/horrible_access_storage_framework_performance/ |archive-date=23 Aug 2025 |website=[[Reddit]] - r/androiddev}}</ref>


===Non-replaceable batteries since the Samsung Galaxy S6===
===Non-replaceable batteries since the Samsung Galaxy S6===
Justin Denison, Samsung's public relations person, said:<ref>[https://www.youtube.com/watch?v=U8mfEud8n4c Samsung Galaxy Unpacked 2015 - Livestream (Replay] ([https://preservetube.com/watch?v=U8mfEud8n4c Archived])</ref>
Justin Denison, Samsung's public relations person, said:<ref name=":1">[https://www.youtube.com/watch?v=U8mfEud8n4c Samsung Galaxy Unpacked 2015 - Livestream (Replay] ([https://preservetube.com/watch?v=U8mfEud8n4c Archived])</ref>


<blockquote>We refused to do this for some time. That's because we didn't want to have a built-in battery, until we were absolutely sure that users would feel confident about charging their phones. </blockquote>
<blockquote>We refused to do this for some time. That's because we didn't want to have a built-in battery, until we were absolutely sure that users would feel confident about charging their phones. </blockquote>
Line 34: Line 34:
The OnePlus Pad has a serialized battery, meaning the device detects repairs not approved by OnePlus, which can result in functionality being disabled. This is an anti-repair practice first seen on Apple iPhone 11.
The OnePlus Pad has a serialized battery, meaning the device detects repairs not approved by OnePlus, which can result in functionality being disabled. This is an anti-repair practice first seen on Apple iPhone 11.


However, OnePlus marketed this practice as "encrypting" the battery. Given that people associate "encryption" with something positive (for example end-to-end encryption on a messaging service), OnePlus attempted to "recycle" this word to glorify an anti-repair practice.<ref>{{Cite web |last=Rossmann |first=Louis |date=2023-02-08 |title=Oneplus' tablet uses an encrypted battery; how's that for repairability? |url=https://www.youtube.com/watch?v=UgtFSHCGNIk |access-date=2025-10-01 |website=YouTube |type=Video |url-status=live |archive-url=https://preservetube.com/watch?v=UgtFSHCGNIk |archive-date=16 Feb 2026}}</ref><ref>{{Cite news |last=Amadeo |first=Ron |date=2023-02-07 |title=OnePlus takes on the iPad with the OnePlus Pad |url=https://arstechnica.com/gadgets/2023/02/oneplus-takes-on-the-ipad-with-the-oneplus-pad/ |access-date=2025-10-01 |work=Ars Technica |url-status=live |archive-url=http://web.archive.org/web/20251118200050/https://arstechnica.com/gadgets/2023/02/oneplus-takes-on-the-ipad-with-the-oneplus-pad/ |archive-date=18 Nov 2025}}</ref>
OnePlus used the term "encryption" to describe this battery serialization. Critics noted that "encryption" carries positive associations unrelated to its use here, and that the term obscures the restriction's effect on independent repair.<ref>{{Cite web |last=Rossmann |first=Louis |date=2023-02-08 |title=Oneplus' tablet uses an encrypted battery; how's that for repairability? |url=https://www.youtube.com/watch?v=UgtFSHCGNIk |access-date=2025-10-01 |website=YouTube |type=Video |url-status=live |archive-url=https://preservetube.com/watch?v=UgtFSHCGNIk |archive-date=16 Feb 2026}}</ref><ref>{{Cite news |last=Amadeo |first=Ron |date=2023-02-07 |title=OnePlus takes on the iPad with the OnePlus Pad |url=https://arstechnica.com/gadgets/2023/02/oneplus-takes-on-the-ipad-with-the-oneplus-pad/ |access-date=2025-10-01 |work=Ars Technica |url-status=live |archive-url=http://web.archive.org/web/20251118200050/https://arstechnica.com/gadgets/2023/02/oneplus-takes-on-the-ipad-with-the-oneplus-pad/ |archive-date=18 Nov 2025}}</ref>


==="Web Environment Integrity API" by Google===
==="Web Environment Integrity API" by Google===
Google tried to implement [[Digital rights management|Digital Restrictions Management]] (DRM) on the Internet, giving it the name "Web Environment Integrity API".<ref>[https://www.youtube.com/watch?v=0i0Ho-x7s_U Google's trying to DRM the internet, and we have to make sure they fail] - Louis Rossmann ([https://www.brighteon.com/1f4125e9-f0cd-46a3-bf38-0ff22881c0f9 Brighteon mirror], [https://old.bitchute.com/video/Jl7ze8KjhWvK/ BitChute mirror]) ([https://preservetube.com/watch?v=0i0Ho-x7s_U Archived])</ref><ref>{{Cite web |last=Bruchon |first=Jody |date=2023-07-22 |title=Web Environment Integrity Must Be Stopped: Enslavement By "Remote Attestation" |url=https://www.jodybruchon.com/2023/07/22/web-environment-integrity-must-be-stopped-enslavement-by-remote-attestation/ |access-date=2025-10-01 |website=jodybruchon.com |url-status=live |archive-url=http://web.archive.org/web/20251201031758/https://www.jodybruchon.com/2023/07/22/web-environment-integrity-must-be-stopped-enslavement-by-remote-attestation/ |archive-date=1 Dec 2025}}</ref>
Google tried to implement [[Digital rights management|Digital Rights Management]] (DRM) on the Internet, giving it the name "Web Environment Integrity API".<ref>[https://www.youtube.com/watch?v=0i0Ho-x7s_U Google's trying to DRM the internet, and we have to make sure they fail] - Louis Rossmann ([https://www.brighteon.com/1f4125e9-f0cd-46a3-bf38-0ff22881c0f9 Brighteon mirror], [https://old.bitchute.com/video/Jl7ze8KjhWvK/ BitChute mirror]) ([https://preservetube.com/watch?v=0i0Ho-x7s_U Archived])</ref><ref>{{Cite web |last=Bruchon |first=Jody |date=2023-07-22 |title=Web Environment Integrity Must Be Stopped: Enslavement By "Remote Attestation" |url=https://www.jodybruchon.com/2023/07/22/web-environment-integrity-must-be-stopped-enslavement-by-remote-attestation/ |access-date=2025-10-01 |website=jodybruchon.com |url-status=live |archive-url=http://web.archive.org/web/20251201031758/https://www.jodybruchon.com/2023/07/22/web-environment-integrity-must-be-stopped-enslavement-by-remote-attestation/ |archive-date=1 Dec 2025}}</ref>


=="To enhance our services"==
=="To enhance our services"==
Line 50: Line 50:
</blockquote>
</blockquote>


Despite using benevolent-seeming phrases such as "enhance our service" and " offer additional content", the actual aim of the change was to place large and obtrusive adverts in users' homes.
Despite using benevolent-seeming phrases such as "enhance our service" and " offer additional content", the update introduced advertisements on the refrigerator's display.<ref name=":1" />


=="To streamline the experience"==
=="To streamline the experience"==
Line 68: Line 68:




So they brought it back with Android 5.0, however only through Google's Storage Access Framework, which comes with a large processing overhead, resulting in slower speeds, especially when handling a high number of files.<ref name="SAF" /><ref name=":0" />
Google restored write access in Android 5.0 through the Storage Access Framework. However, the framework introduces processing overhead that reduces speeds, particularly when handling large numbers of files.<ref name="SAF" /><ref name=":0" />


==References==
==References==
Retrieved from "https://consumerrights.wiki/w/Deceptive_language_frequently_used_against_consumers"