Bananabot (talk | contribs)
Added archive URLs for 46 citation(s) using CRWCitationBot
Rudxain (talk | contribs)
"Phone number requirement for new accounts" incident
 
(12 intermediate revisions by 8 users not shown)
Line 5: Line 5:
|ParentCompany=Alphabet Inc.
|ParentCompany=Alphabet Inc.
|Type=Subsidiary
|Type=Subsidiary
|Description=Google LLC, founded in 1998 by Larry Page and Sergey Brin, is one of the most influential technology companies in the world. Originally developed as a search engine to organize and index the growing amount of information on the internet, Google has since expanded into a wide range of services and products, becoming a central player in digital advertising, software, hardware, and cloud computing.
|Description=Google is one of the most influential technology companies in the world originally known for developing the most widely used search engine.
|Website=https://www.google.com/
|Website=https://www.google.com/
}}
}}
'''[[wikipedia:Google|Google LLC]]''', founded in 1998 by Larry Page and Sergey Brin, is one of the most influential technology companies in the world.<ref>{{Cite web |title=Largest tech companies by market cap |url=https://companiesmarketcap.com/tech/largest-tech-companies-by-market-cap/ |url-status=live |website=companiesmarketcap.com |archive-url=http://web.archive.org/web/20260222070659/https://companiesmarketcap.com/tech/largest-tech-companies-by-market-cap/ |archive-date=22 Feb 2026}}</ref> Originally developed as a search engine to organize and index the growing amount of information on the internet, Google has since expanded into a wide range of services and products, becoming a central player in digital advertising, software, hardware, and cloud computing.<ref>{{Cite web |date= |title=Google Products |url=https://about.google/products/ |access-date=10 Mar 2025 |archive-url=http://web.archive.org/web/20260128182647/https://about.google/products/ |archive-date=28 Jan 2026}}</ref>
'''[[wikipedia:Google|Google LLC]]''', founded in 1998 by Larry Page and Sergey Brin, is one of the most influential technology companies in the world.<ref>{{Cite web |title=Largest tech companies by market cap |url=https://companiesmarketcap.com/tech/largest-tech-companies-by-market-cap/ |url-status=live |website=companiesmarketcap.com |archive-url=http://web.archive.org/web/20260222070659/https://companiesmarketcap.com/tech/largest-tech-companies-by-market-cap/ |archive-date=22 Feb 2026}}</ref> Originally developed as a search engine to organize and index the growing amount of information on the internet, Google has since expanded into a wide range of services and products, becoming a central player in digital advertising, software, hardware, and cloud computing.<ref>{{Cite web |date= |title=Google Products |url=https://about.google/products/ |access-date=10 Mar 2025 |archive-url=http://web.archive.org/web/20260128182647/https://about.google/products/ |archive-date=28 Jan 2026}}</ref>


Line 21: Line 22:


====Google Play Music shutdown====
====Google Play Music shutdown====
[[wikipedia:Google_Play_Music|Google Play Music]] was a service that allowed users to purchase music, listen via streaming, and download to the local device; alternatively users could pay for a subscription to listen to all music available through streaming. It was publicly launched on the 16th November 2011 and later shutdown in December 2020.<ref>{{Cite web |date=4 Aug 2020 |title=Google Play Music, Music Play Store & Music Manager are going away – everything you need to know |url=https://support.google.com/youtubemusic/thread/62843644/google-play-music-music-play-store-music-manager-are-going-away-%E2%80%93-everything-you-need-to-know?hl=en |url-status=live |access-date=5 Apr 2025 |website=[[Google]] |archive-url=http://web.archive.org/web/20251004223929/https://support.google.com/youtubemusic/thread/62843644/google-play-music-music-play-store-music-manager-are-going-away-%E2%80%93-everything-you-need-to-know?hl=en |archive-date=4 Oct 2025}}</ref><ref>{{Cite web |last=Amadeo |first=Ron |date=28 Oct 2020 |title=RIP Google Play Music, 2011 – 2020 |url=https://arstechnica.com/gadgets/2020/10/rip-google-play-music-2011-2020/ |url-status=live |access-date=5 Apr 2025 |website=ArsTechnica |archive-url=http://web.archive.org/web/20251214224205/https://arstechnica.com/gadgets/2020/10/rip-google-play-music-2011-2020/ |archive-date=14 Dec 2025}}</ref> Google Play Music further allowed users to upload their own songs to listen on all their devices, with a limit of up to 50,000 files.<ref>{{Cite web |last=Hoffman |first=Chris |date=11 Jan 2017 |title=How to Upload Your Music Library to Google Play Music |url=https://www.howtogeek.com/288231/how-to-upload-your-music-library-to-google-play-music/ |url-status=live |access-date=5 Apr 2025 |website=How-To-Geek}}</ref> Users were able to purchase songs individually or buy whole albums that they could then download and listen to, or stream through the internet.<ref>{{Cite web |date=15 Jan 2020 |title=How To Buy Music From Google Play (Now YouTube Music) |url=https://www.technobezz.com/buy-music-google-play |url-status=live |access-date=5 Apr 2025 |website=Technobezz |archive-url=http://web.archive.org/web/20250805235415/https://www.technobezz.com/buy-music-google-play |archive-date=5 Aug 2025}}</ref>
[[wikipedia:Google_Play_Music|Google Play Music]] was a service that allowed users to purchase music, listen via streaming, and download to the local device; alternatively users could pay for a subscription to listen to all music available through streaming. It was publicly launched on the 16th November 2011 and later shutdown in December 2020.<ref>{{Cite web |date=4 Aug 2020 |title=Google Play Music, Music Play Store & Music Manager are going away – everything you need to know |url=https://support.google.com/youtubemusic/thread/62843644/google-play-music-music-play-store-music-manager-are-going-away-%E2%80%93-everything-you-need-to-know?hl=en |url-status=live |access-date=5 Apr 2025 |website=[[Google]] |archive-url=http://web.archive.org/web/20251004223929/https://support.google.com/youtubemusic/thread/62843644/google-play-music-music-play-store-music-manager-are-going-away-%E2%80%93-everything-you-need-to-know?hl=en |archive-date=4 Oct 2025}}</ref><ref>{{Cite web |last=Amadeo |first=Ron |date=28 Oct 2020 |title=RIP Google Play Music, 2011 – 2020 |url=https://arstechnica.com/gadgets/2020/10/rip-google-play-music-2011-2020/ |url-status=live |access-date=5 Apr 2025 |website=ArsTechnica |archive-url=http://web.archive.org/web/20251214224205/https://arstechnica.com/gadgets/2020/10/rip-google-play-music-2011-2020/ |archive-date=14 Dec 2025}}</ref> Google Play Music further allowed users to upload their own songs to listen on all their devices, with a limit of up to 50,000 files.<ref>{{Cite web |last=Hoffman |first=Chris |date=11 Jan 2017 |title=How to Upload Your Music Library to Google Play Music |url=https://www.howtogeek.com/288231/how-to-upload-your-music-library-to-google-play-music/ |url-status=live |access-date=5 Apr 2025 |website=How-To-Geek |archive-url=http://web.archive.org/web/20251004223929/https://www.howtogeek.com/288231/how-to-upload-your-music-library-to-google-play-music/ |archive-date=4 Oct 2025}}</ref> Users were able to purchase songs individually or buy whole albums that they could then download and listen to, or stream through the internet.<ref>{{Cite web |date=15 Jan 2020 |title=How To Buy Music From Google Play (Now YouTube Music) |url=https://www.technobezz.com/buy-music-google-play |url-status=live |access-date=5 Apr 2025 |website=Technobezz |archive-url=http://web.archive.org/web/20250805235415/https://www.technobezz.com/buy-music-google-play |archive-date=5 Aug 2025}}</ref>


In October 2020, Google announced that they would be shutting down Google Play Music, with it being fully shut down by December.<ref>{{Cite web |last=Li |first=Abner |date=3 Dec 2020 |title=Google fully shuts down Play Music around the world |url=https://9to5google.com/2020/12/03/google-play-music-dead/ |url-status=live |access-date=5 Apr 2025 |website=9To5Google |archive-url=http://web.archive.org/web/20250708163846/https://9to5google.com/2020/12/03/google-play-music-dead/ |archive-date=8 Jul 2025}}</ref> This went ahead with a warning to their users to begin migrating to [[wikipedia:YouTube_Music|YouTube Music]], and that they would be losing access to their purchased songs. Google recommended users should download their purchased songs before the service would shut down.<ref>{{Cite web |date=4 Aug 2020 |title=YouTube Music will replace Google Play Music by end of 2020 |url=https://blog.youtube/news-and-events/youtube-music-will-replace-google-play-music-end-2020/ |url-status=live |access-date=5 Apr 2025 |website=YouTube Official Blog |archive-url=http://web.archive.org/web/20260201140126/https://blog.youtube/news-and-events/youtube-music-will-replace-google-play-music-end-2020/ |archive-date=1 Feb 2026}}</ref>
In October 2020, Google announced that they would be shutting down Google Play Music, with it being fully shut down by December.<ref>{{Cite web |last=Li |first=Abner |date=3 Dec 2020 |title=Google fully shuts down Play Music around the world |url=https://9to5google.com/2020/12/03/google-play-music-dead/ |url-status=live |access-date=5 Apr 2025 |website=9To5Google |archive-url=http://web.archive.org/web/20250708163846/https://9to5google.com/2020/12/03/google-play-music-dead/ |archive-date=8 Jul 2025}}</ref> This went ahead with a warning to their users to begin migrating to [[wikipedia:YouTube_Music|YouTube Music]], and that they would be losing access to their purchased songs. Google recommended users should download their purchased songs before the service would shut down.<ref>{{Cite web |date=4 Aug 2020 |title=YouTube Music will replace Google Play Music by end of 2020 |url=https://blog.youtube/news-and-events/youtube-music-will-replace-google-play-music-end-2020/ |url-status=live |access-date=5 Apr 2025 |website=YouTube Official Blog |archive-url=http://web.archive.org/web/20260201140126/https://blog.youtube/news-and-events/youtube-music-will-replace-google-play-music-end-2020/ |archive-date=1 Feb 2026}}</ref>
Line 34: Line 35:
Google Stadia controllers were limited to Wi-Fi connectivity, however upon shut down they started offering an update to allow them to connect through Bluetooth, the update service website was scheduled to shut down on the 31st December 2025.<ref>{{Cite web |last=Devine |first=Richard |date=17 Jan 2023 |title=Bluetooth support for Google Stadia Controller arrives — Here's how to enable it and play PC games |url=https://www.windowscentral.com/gaming/pc-gaming/bluetooth-support-for-google-stadia-controller-arrives-heres-how-to-enable-it-and-play-pc-games |url-status=live |access-date=5 Apr 2025 |website=Windows Central |archive-url=http://web.archive.org/web/20251109164004/https://www.windowscentral.com/gaming/pc-gaming/bluetooth-support-for-google-stadia-controller-arrives-heres-how-to-enable-it-and-play-pc-games |archive-date=9 Nov 2025}}</ref>
Google Stadia controllers were limited to Wi-Fi connectivity, however upon shut down they started offering an update to allow them to connect through Bluetooth, the update service website was scheduled to shut down on the 31st December 2025.<ref>{{Cite web |last=Devine |first=Richard |date=17 Jan 2023 |title=Bluetooth support for Google Stadia Controller arrives — Here's how to enable it and play PC games |url=https://www.windowscentral.com/gaming/pc-gaming/bluetooth-support-for-google-stadia-controller-arrives-heres-how-to-enable-it-and-play-pc-games |url-status=live |access-date=5 Apr 2025 |website=Windows Central |archive-url=http://web.archive.org/web/20251109164004/https://www.windowscentral.com/gaming/pc-gaming/bluetooth-support-for-google-stadia-controller-arrives-heres-how-to-enable-it-and-play-pc-games |archive-date=9 Nov 2025}}</ref>


===='''Manifest V2 shutdown'''====
====Manifest V2 shutdown====
On July 24, 2025, Google permanently disabled all Manifest V2 extensions for Chrome 138 users as well as making Chromium (a browser that many other browsers use as their base) switch to Manifest V3, and disabled the ability to turn them back on.<ref>{{Cite web |date=2021-09-23 |title=Manifest V2 support timeline |url=https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline |archive-url=https://web.archive.org/web/20250808191702/https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline |archive-date=2025-08-08 |access-date=2025-08-12}}</ref>
On July 24, 2025, Google permanently disabled all Manifest V2 extensions for Chrome 138 users as well as making Chromium (a browser that many other browsers use as their base) switch to Manifest V3, and disabled the ability to turn them back on.<ref>{{Cite web |date=2021-09-23 |title=Manifest V2 support timeline |url=https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline |archive-url=https://web.archive.org/web/20250808191702/https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline |archive-date=2025-08-08 |access-date=2025-08-12}}</ref>


Manifest V3 disabled the <code>webRequestBlocking</code> permission in the <code>webRequest</code> API<ref>{{Cite web |date=2023-03-09 |title=Replace blocking web request listeners {{!}} Chrome Extensions {{!}} Chrome for Developers |url=https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |url-status=live |archive-url=https://web.archive.org/web/20250614074559/https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |archive-date=2025-06-14 |access-date=2025-08-12 |website=Chrome for Developers}}</ref>, preventing many ad content blockers (such as uBlock Origin) from working.<ref>{{Cite web |date=2024-09-26 |title=Understanding Manifest V3 and the Future of uBlock Origin |url=https://ublockorigin.com/ |url-status=live |archive-url=https://web.archive.org/web/20250812114916/https://ublockorigin.com/ |archive-date=2025-08-12 |access-date=2025-08-12 |website=uBlock Origin - Free, open-source ad content blocker}}</ref> Google cites performance reasons <ref>{{Cite web |date=2023-03-09 |title=Replace blocking web request listeners {{!}} Chrome Extensions {{!}} Chrome for Developers |url=https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |url-status=live |archive-url=https://web.archive.org/web/20250614074559/https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |archive-date=2025-06-14 |access-date=2025-08-12 |website=Chrome for Developers |quote="In Manifest V2, blocking web requests could significantly degrade both the performance of extensions and the performance of pages they work with."}}</ref>, but this is dubious; restricting content blockers prevents users from impeding their tracking and surveillance, meaning they can create a larger profit from the data gained. This is likely the ulterior motive, although unproven.
Manifest V3 disabled the <code>webRequestBlocking</code> permission in the <code>webRequest</code> API<ref>{{Cite web |date=2023-03-09 |title=Replace blocking web request listeners {{!}} Chrome Extensions {{!}} Chrome for Developers |url=https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |url-status=live |archive-url=https://web.archive.org/web/20250614074559/https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |archive-date=2025-06-14 |access-date=2025-08-12 |website=Chrome for Developers}}</ref>, preventing many ad content blockers (such as uBlock Origin) from working.<ref>{{Cite web |date=2024-09-26 |title=Understanding Manifest V3 and the Future of uBlock Origin |url=https://ublockorigin.com/ |url-status=live |archive-url=https://web.archive.org/web/20250812114916/https://ublockorigin.com/ |archive-date=2025-08-12 |access-date=2025-08-12 |website=uBlock Origin - Free, open-source ad content blocker}}</ref> Google cites performance reasons <ref>{{Cite web |date=2023-03-09 |title=Replace blocking web request listeners {{!}} Chrome Extensions {{!}} Chrome for Developers |url=https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |url-status=live |archive-url=https://web.archive.org/web/20250614074559/https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |archive-date=2025-06-14 |access-date=2025-08-12 |website=Chrome for Developers |quote="In Manifest V2, blocking web requests could significantly degrade both the performance of extensions and the performance of pages they work with."}}</ref>, but this is dubious; restricting content blockers prevents users from impeding their tracking and surveillance, meaning they can create a larger profit from the data gained. This is likely the ulterior motive, although unproven.


===='''Google Jamboard shutdown'''====
====Google Jamboard shutdown====
{{Main|Google Jamboard}}
{{Main|Google Jamboard}}
In September 2023, Google revealed plans to retire its Jamboard service, as the product would be transitioned to a view-only format by October 1, 2024, and completely shut down by December 31, 2024. As a result, users had little time to transfer their data before the final transition and no refunds were ever issued to hardware buyers.
In September 2023, Google revealed plans to retire its Jamboard service, as the product would be transitioned to a view-only format by October 1, 2024, and completely shut down by December 31, 2024. As a result, users had little time to transfer their data before the final transition and no refunds were ever issued to hardware buyers.
Line 50: Line 51:
On June 20th, 2023, Google disabled 3rd party list support for Google Assistant<ref>{{Cite web |access-date=2025-09-16 |title=Where are my old lists? |url=https://support.google.com/assistant/answer/9415862#zippy=%2Cwhere-are-my-old-lists |archive-url=https://web.archive.org/web/20250427212604/https://support.google.com/assistant/answer/9415862#zippy=%2Cwhere-are-my-old-lists |archive-date=2025-04-27}}</ref>. This feature allowed lists through 3rd party services such as AnyList or Todoist to be managed via Google Assistant. The only list provider available through Google Assistant after this change was Google Keep<ref>{{Cite web |last=Mathur |first=Chandraveer |website=Android Police |date=2023-05-31 |title=Google Assistant is killing support for notes and lists integration with third-party apps |url=https://www.androidpolice.com/google-assistant-ending-support-third-party-notes-lists/ |archive-url=http://web.archive.org/web/20251218051543/https://www.androidpolice.com/google-assistant-ending-support-third-party-notes-lists/ |archive-date=18 Dec 2025}}</ref>.
On June 20th, 2023, Google disabled 3rd party list support for Google Assistant<ref>{{Cite web |access-date=2025-09-16 |title=Where are my old lists? |url=https://support.google.com/assistant/answer/9415862#zippy=%2Cwhere-are-my-old-lists |archive-url=https://web.archive.org/web/20250427212604/https://support.google.com/assistant/answer/9415862#zippy=%2Cwhere-are-my-old-lists |archive-date=2025-04-27}}</ref>. This feature allowed lists through 3rd party services such as AnyList or Todoist to be managed via Google Assistant. The only list provider available through Google Assistant after this change was Google Keep<ref>{{Cite web |last=Mathur |first=Chandraveer |website=Android Police |date=2023-05-31 |title=Google Assistant is killing support for notes and lists integration with third-party apps |url=https://www.androidpolice.com/google-assistant-ending-support-third-party-notes-lists/ |archive-url=http://web.archive.org/web/20251218051543/https://www.androidpolice.com/google-assistant-ending-support-third-party-notes-lists/ |archive-date=18 Dec 2025}}</ref>.


==='''Pixel 4a battery reduction update'''===
===Pixel 4a battery reduction update===
{{Main|Pixel 4a Battery Performance Program}}
{{Main|Pixel 4a Battery Performance Program}}
On January 6, 2025, Google issued a software update to the Pixel 4a that significantly decreased battery capacity on "Impacted Devices". Not all units were affected. It's speculated that the affected units have defective batteries and may pose a safety risk if the update is not applied, but Google never disclosed the reason(s) that the update was deemed necessary. Google removed all factory images for previous versions of the system software from their website, making it difficult to revert the update.
On January 6, 2025, Google issued a software update to the Pixel 4a that significantly decreased battery capacity on "Impacted Devices". Not all units were affected. It's speculated that the affected units have defective batteries and may pose a safety risk if the update is not applied, but Google never disclosed the reason(s) that the update was deemed necessary. Google removed all factory images for previous versions of the system software from their website, making it difficult to revert the update.
Line 62: Line 63:
Devices without [[Google Mobile Services]] or running custom ROMs are exempt.<ref name=":22">{{Cite web |last=Anderson |first=Tim |date=2025-08-26 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |archive-url=https://web.archive.org/web/20250829170329/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |archive-date=2025-08-29 |access-date=2025-08-26 |website=The Register}}</ref> Critics argue this restricts user freedom, impacts independent developers, and may enable Google to block apps it disapproves of, such as ad-blockers, raising concerns about privacy and control over personal devices.<ref name=":2">{{Cite web |last=Anderson |first=Tim |date=26 Aug 2025 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |access-date=26 Aug 2025 |website=The Register |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}</ref><ref name=":3">{{Cite web |first= |date=26 Aug 2025 |title=Google will block sideloading of unverified Android apps starting next year |url=https://www.bleepingcomputer.com/forums/t/810335/google-will-block-sideloading-of-unverified-android-apps-starting-next-year |url-status=live |access-date=26 Aug 2025 |website=BleepingComputer |archive-url=http://web.archive.org/web/20250829215120/https://www.bleepingcomputer.com/forums/t/810335/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |archive-date=29 Aug 2025}}</ref>
Devices without [[Google Mobile Services]] or running custom ROMs are exempt.<ref name=":22">{{Cite web |last=Anderson |first=Tim |date=2025-08-26 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |archive-url=https://web.archive.org/web/20250829170329/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |archive-date=2025-08-29 |access-date=2025-08-26 |website=The Register}}</ref> Critics argue this restricts user freedom, impacts independent developers, and may enable Google to block apps it disapproves of, such as ad-blockers, raising concerns about privacy and control over personal devices.<ref name=":2">{{Cite web |last=Anderson |first=Tim |date=26 Aug 2025 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |access-date=26 Aug 2025 |website=The Register |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}</ref><ref name=":3">{{Cite web |first= |date=26 Aug 2025 |title=Google will block sideloading of unverified Android apps starting next year |url=https://www.bleepingcomputer.com/forums/t/810335/google-will-block-sideloading-of-unverified-android-apps-starting-next-year |url-status=live |access-date=26 Aug 2025 |website=BleepingComputer |archive-url=http://web.archive.org/web/20250829215120/https://www.bleepingcomputer.com/forums/t/810335/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |archive-date=29 Aug 2025}}</ref>


===Not providing a solution for Pixel devices bricked due to switching slots, flashing certain ROMs, downgrading the OS, or installing the June 2025 update===
===Banning domain-blockers from Play Store===
Numerous Google Pixel phones have gotten bricked as a result of different use cases, such as accidentally switched slots, flashing custom ROMs or downgrading the bootloader version of the device after an Anti-Rollback (ARB) increment, accidentally or otherwise<ref>{{Cite web |last=Simons |first=Hadlee |date=2025-08-26 |title=Some Pixels are bricked and Google apparently won't help revive them |url=https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |url-status=live |access-date=2025-09-11 |website=Android Authority |archive-url=http://web.archive.org/web/20260108045933/https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |archive-date=8 Jan 2026}}</ref>. The device enters an emergency download state called Pixel ROM Recovery, which is a Google modification of Samsung's EUB mode on Exynos chipsets. In this mode, it refuses to enter Android recovery or Fastboot, making it near impossible to restore the operating system on the device. The only way to fix it is to use Pixel ROM Recovery to boot a special, Google-signed recovery bootloader into RAM and flash a working version of Android from there.
Since 2013, Google has taken down all apps on G-Play that can block connections to arbitrary [[wikipedia:Domain_Name_System|domain-names]] via [https://developer.android.com/develop/connectivity/vpn the official VPN API], most of those apps being marketed as ad-blockers.<ref>https://www.zdnet.com/article/google-kicks-ad-blocker-apps-off-play-store/</ref> This forced apps such as AdGuard and NetGuard to distribute their ad-blocking features elsewhere.<ref>https://adguard.com/en/blog/adguard-google-play-removal.html</ref><ref>https://github.com/M66B/NetGuard/blob/7308869411ff87649bf3a46a9c7c08f1e5353801/ADBLOCKING.md?plain=1#L6</ref><ref>https://github.com/M66B/NetGuard/blob/7308869411ff87649bf3a46a9c7c08f1e5353801/ADBLOCKING.md?plain=1#L106</ref>
 
Google cites their own Developer Distribution Agreement (terms of service for devs), claiming that those apps are "disruptive", as if to imply hacking or cracking. Many people claim that's an invalid excuse, and that the ulterior motive was to increase ad-revenue.
 
===Pixel devices bricked due to confusing reasons===
Numerous Google Pixel phones have gotten bricked as a result of different use cases, such as accidentally switched slots, flashing custom ROMs or downgrading the bootloader version of the device after an Anti-Rollback (ARB) increment (accidentally or otherwise), or installing the June 2025 update.<ref>{{Cite web |last=Simons |first=Hadlee |date=2025-08-26 |title=Some Pixels are bricked and Google apparently won't help revive them |url=https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |url-status=live |archive-url=http://web.archive.org/web/20260108045933/https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |archive-date=8 Jan 2026 |access-date=2025-09-11 |website=Android Authority}}</ref> The device enters an emergency download state called Pixel ROM Recovery, which is a Google modification of Samsung's EUB mode on Exynos chipsets. In this mode, it refuses to enter Android recovery or Fastboot, making it near impossible to restore the operating system on the device. The only way to fix it is to use Pixel ROM Recovery to boot a special, Google-signed recovery bootloader into RAM and flash a working version of Android from there.


This recovery bootloader is just a regular bootloader as it appears in Google factory images, but with a special "USB boot" bit flag set to 1. <ref>{{Cite web |date=2025-08-11 |title=Pixel devices getting bricked / stuck in Pixel ROM Recovery after flashing AOSP-based builds with Android 15 QPR2 (BP1A.250305.019) |url=https://issuetracker.google.com/issues/402455330#comment19 |archive-url=http://web.archive.org/web/20260205112358/https://issuetracker.google.com/issues/402455330 |archive-date=5 Feb 2026}}</ref>
This recovery bootloader is just a regular bootloader as it appears in Google factory images, but with a special "USB boot" bit flag set to 1. <ref>{{Cite web |date=2025-08-11 |title=Pixel devices getting bricked / stuck in Pixel ROM Recovery after flashing AOSP-based builds with Android 15 QPR2 (BP1A.250305.019) |url=https://issuetracker.google.com/issues/402455330#comment19 |archive-url=http://web.archive.org/web/20260205112358/https://issuetracker.google.com/issues/402455330 |archive-date=5 Feb 2026}}</ref>
Line 69: Line 75:
However, this recovery bootloader is inaccessible to the public, and is not possible to recreate it without Google's private keys. This makes it impossible to repair a device in this state, other than to do a technically challenging repair involving desoldering the UFS chip to repopulate its contents or by replacing the motherboard altogether. Google stores and service centers outside of the US do not offer support for the device if it is out of warranty, even though the issue is completely fixable by software.
However, this recovery bootloader is inaccessible to the public, and is not possible to recreate it without Google's private keys. This makes it impossible to repair a device in this state, other than to do a technically challenging repair involving desoldering the UFS chip to repopulate its contents or by replacing the motherboard altogether. Google stores and service centers outside of the US do not offer support for the device if it is out of warranty, even though the issue is completely fixable by software.


Numerous developers have worked on trying to find a solution to this issue, and have succeeded to varying extents. However, devices bricked due to the ARB trigger remain impossible to fix. Google has not provided any recovery images to resolve this issue, despite there being a sizable post on their bug tracker.<ref name=":4">{{Cite web |date=2025-08-10 |title=Pixel recovery bootloaders lack security reasoning for guarding |url=https://issuetracker.google.com/issues/437705274 |url-status=live |access-date=2025-09-11 |website=Google IssueTracker}}</ref><ref>{{Cite web |date=2025-03-12 |title=Pixel devices getting bricked / stuck in Pixel ROM Recovery after flashing AOSP-based builds with Android 15 QPR2 (BP1A.250305.019) |url=https://issuetracker.google.com/issues/402455330 |url-status=live |access-date=2025-09-11 |website=Google IssueTracker}}</ref> despite the fact that Google providing the recovery images for the repair will not compromise security, as explained by one of the developers in their report.<ref name=":4" />
Numerous developers have worked on trying to find a solution to this issue, and have succeeded to varying extents. However, devices bricked due to the ARB trigger remain impossible to fix. Google has not provided any recovery images to resolve this issue, despite there being a sizable post on their bug tracker.<ref name=":4">{{Cite web |date=2025-08-10 |title=Pixel recovery bootloaders lack security reasoning for guarding |url=https://issuetracker.google.com/issues/437705274 |url-status=live |access-date=2025-09-11 |website=Google IssueTracker |archive-url=http://web.archive.org/web/20251004223929/https://issuetracker.google.com/issues/437705274 |archive-date=4 Oct 2025}}</ref><ref>{{Cite web |date=2025-03-12 |title=Pixel devices getting bricked / stuck in Pixel ROM Recovery after flashing AOSP-based builds with Android 15 QPR2 (BP1A.250305.019) |url=https://issuetracker.google.com/issues/402455330 |url-status=live |access-date=2025-09-11 |website=Google IssueTracker |archive-url=http://web.archive.org/web/20260205112358/https://issuetracker.google.com/issues/402455330 |archive-date=5 Feb 2026}}</ref> despite the fact that Google providing the recovery images for the repair will not compromise security, as explained by one of the developers in their report.<ref name=":4" />
 
=== Phone number requirement for new accounts ===
Since 2020, Google has increasingly forced users to verify phone-numbers via SMS during account registration,<ref>https://support.google.com/accounts/thread/34403939/cannot-create-a-new-google-account-it-is-requiring-a-phone-number-forced-phone-verification</ref><ref>https://reddit.com/r/degoogle/comments/oanh2p/does_google_now_require_a_phone_number_to_make/</ref> to "confirm you're not a bot"{{Citation needed}}. They have a system that immediately detects reuse of numbers, so no accounts can have the same associated number.{{Citation needed}} This, paired with [[YouTube#Forced sign-in|YouTube's sign-in requirement]], makes it impossible for users to share a single "guest" account, as is typically the case for families sharing a smart TV.


==Controversies==
==Controversies==
Line 105: Line 114:


===Ban on third-party tech support ads===
===Ban on third-party tech support ads===
Google prohibits tech support ads on their platform if they are not authorised by the manufacturer.<ref>{{Cite web |last=Graff |first=David |date=31 Aug 2018 |title=Restricting ads in third-party tech support services |url=https://blog.google/products/ads/restricting-ads-third-party-tech-support-services/ |website=Google}}</ref>
Google prohibits tech support ads on their platform if they are not authorised by the manufacturer.<ref>{{Cite web |last=Graff |first=David |date=31 Aug 2018 |title=Restricting ads in third-party tech support services |url=https://blog.google/products/ads/restricting-ads-third-party-tech-support-services/ |website=Google |archive-url=http://web.archive.org/web/20251112170608/https://blog.google/products/ads/restricting-ads-third-party-tech-support-services/ |archive-date=12 Nov 2025}}</ref>


=== The chargeback incident ===
===The chargeback incident===
In November 2022, a Google customer accidentally purchased two Google Pixel smartphones instead of one, directly from Google (no third-party reseller), and tried to return one package to Google for a refund, but the shipping was unsuccessful.
In November 2022, a Google customer accidentally purchased two Google Pixel smartphones instead of one, directly from Google (no third-party reseller), and tried to return one package to Google for a refund, but the shipping was unsuccessful.


Line 114: Line 123:
==Anti-consumer legal cases==
==Anti-consumer legal cases==


===Rodriguez v. Google LLC (5/21/21 - Present)===
===Privacy Violations===
Google's Web & App Activity setting had the ability to be paused. Reportedly, despite this setting being paused by consumers, Google would continue to collect consumer data regardless of consent.<ref>{{Cite web |title=Rodriguez v. Google LLC |url=https://www.googlewebappactivitylawsuit.com/Home/FAQ#faq1 |url-status=live |access-date=5 Apr 2025}}</ref> This case is currently ongoing and has yet to receive a judgment.<ref>[https://www.googlewebappactivitylawsuit.com/Home/Documents Important Documents] ([http://web.archive.org/web/20250911091039/https://googlewebappactivitylawsuit.com/Home/Documents Archived])</ref>
 
====Rodriguez v. Google LLC (21 May 2021 - 3 Sep 2025)====
Google's "Web & App Activity" (WAA) setting had the ability to be paused. Reportedly, despite this setting being paused by consumers, Google would continue to collect consumer data regardless of consent.<ref>{{Cite web |title=Rodriguez v. Google LLC |url=https://www.googlewebappactivitylawsuit.com/Home/FAQ#faq1 |url-status=live |access-date=5 Apr 2025 |archive-url=http://web.archive.org/web/20251011171640/https://googlewebappactivitylawsuit.com/Home/FAQ |archive-date=11 Oct 2025}}</ref> This case is currently ongoing and has yet to receive a judgment.<ref>[https://www.googlewebappactivitylawsuit.com/Home/Documents Important Documents] ([http://web.archive.org/web/20250911091039/https://googlewebappactivitylawsuit.com/Home/Documents Archived])</ref> Google collected mobile device data for eight years from users who opted out of tracking under the WAA.<ref name=":5">{{Cite web |last=Staab |first=Theresa |date=18 Sep 2025 |title=Someone is Always Watching: Implications of Google's WAA Privacy Case |url=https://lawreview.syr.edu/someone-is-always-watching-implications-of-googles-waa-privacy-case/ |access-date=26 Mar 2026 |website=Syracuse Law Review}}</ref> The dates of use/activity in question were between July 1, 2016 and September 23, 2024.<ref>{{Cite web |date=23 Oct 2024 |title=FAQs: Google Web App Activity lawsuit |url=https://help.wfu.edu/support/solutions/articles/13000825158-faqs-google-web-app-activity-lawsuit |url-status=live |access-date=26 Mar 2026 |website=Wake Forest University}}</ref> On September 3, 2025, the San Francisco Federal Court jury held Google liable two of three claims of privacy invasion. Google was charged $425 million for invasion of privacy, but not for punitive damages since the jury found that Google did not act with malicious intent.<ref name=":5" />
 
===Anti-competitive Behavior===


===Epic Games, Inc. v. Google Inc. (8/13/20 - 5/31/25)===
====Epic Games, Inc. v. Google Inc. (13 Aug 2020 - 31 May 2025)====
Google takes a 30% share of all revenue made through all sales made on the Play Store, which is a comparable figure to other digital storefronts such as the [[Apple App Store]] and [[Steam]].<ref>{{Cite web |last=Marks |first=Tom |date=7 Oct 2019 |title=Report: Steam's 30% Cut Is Actually the Industry Standard |url=https://www.ign.com/articles/2019/10/07/report-steams-30-cut-is-actually-the-industry-standard |url-status=live |website=ign.com |archive-url=http://web.archive.org/web/20251211034837/https://www.ign.com/articles/2019/10/07/report-steams-30-cut-is-actually-the-industry-standard |archive-date=11 Dec 2025}}</ref> On 13th August 2020, [[Epic Games]] CEO Tim Sweeney updated both iOS and Android versions of ''Fortnite'' to redirect users to Epic Games' storefront to purchase in-game currency ("V-Bucks") alongside the respective first-party storefront, with incentives including cheaper prices if buying from Epic Games directly. This violated the Terms of Service of both Apple and Google's storefronts, and ''Fortnite'' was removed from both app stores the same day.
Google takes a 30% share of all revenue made through all sales made on the Play Store, which is a comparable figure to other digital storefronts such as the [[Apple App Store]] and [[Steam]].<ref>{{Cite web |last=Marks |first=Tom |date=7 Oct 2019 |title=Report: Steam's 30% Cut Is Actually the Industry Standard |url=https://www.ign.com/articles/2019/10/07/report-steams-30-cut-is-actually-the-industry-standard |url-status=live |website=ign.com |archive-url=http://web.archive.org/web/20251211034837/https://www.ign.com/articles/2019/10/07/report-steams-30-cut-is-actually-the-industry-standard |archive-date=11 Dec 2025}}</ref> On 13th August 2020, [[Epic Games]] CEO Tim Sweeney updated both iOS and Android versions of ''Fortnite'' to redirect users to Epic Games' storefront to purchase in-game currency ("V-Bucks") alongside the respective first-party storefront, with incentives including cheaper prices if buying from Epic Games directly. This violated the Terms of Service of both Apple and Google's storefronts, and ''Fortnite'' was removed from both app stores the same day.


Epic Games would use this motion to file federal lawsuits against both Google and Apple, citing that these practices meant that the companies were engaging in anti-competitive behavior. Google lost in the lawsuit, but attempted to appeal the decision, in which they lost again.<ref>{{Cite news |last=Hollister |first=Sean |date=31 July 2025 |title=Epic just won its Google lawsuit again, and Android may never be the same |url=https://www.theverge.com/news/716856/epic-v-google-win-in-appeals-court |access-date=21 August 2025 |work=The Verge |archive-url=http://web.archive.org/web/20260111151936/https://www.theverge.com/news/716856/epic-v-google-win-in-appeals-court |archive-date=11 Jan 2026}}</ref>
Epic Games would use this motion to file federal lawsuits against both Google and Apple, citing that these practices meant that the companies were engaging in anti-competitive behavior. Google lost in the lawsuit, but attempted to appeal the decision, in which they lost again.<ref>{{Cite news |last=Hollister |first=Sean |date=31 July 2025 |title=Epic just won its Google lawsuit again, and Android may never be the same |url=https://www.theverge.com/news/716856/epic-v-google-win-in-appeals-court |access-date=21 August 2025 |work=The Verge |archive-url=http://web.archive.org/web/20260111151936/https://www.theverge.com/news/716856/epic-v-google-win-in-appeals-court |archive-date=11 Jan 2026}}</ref>
===Social Media Addiction Bellwether Trials===
====Los Angeles Superior Court, JCCP 5255 (2026)====
Starting in January of 2026, [[Meta]] (Facebook and [[Instagram]]) and [[Google]] ([[YouTube]]) faced legal claims of their platforms being intentionally addictive and harmful to children. [[ByteDance]] ([[TikTok]]) and Snap ([[Snapchat]]) were named initially, but settled for undisclosed terms before the trial began. A 19-year-old girl, referred to by the initials "KGM" or Kaley, and two other plaintiffs were selected for bellwether trials—test cases tried as part of an MDL.<ref>{{Cite web |last=Huamani |first=Kaitlyn |last2=Ortutay |first2=Barbara |date=9 Feb 2026 |title=Landmark trial accusing tech giants of harming children with addictive social media begins |url=https://www.pbs.org/newshour/nation/landmark-trial-accusing-tech-giants-of-harming-children-with-addictive-social-media-begins |url-status=live |access-date=25 Mar 2026 |website=PBS News}}</ref>  On March 25, 2026, the California jury concluded in KGM's case that [[Meta]] and Google were guilty of negligent for their apps—[[Instagram]], Facebook, and [[YouTube]]—being deliberately built to be addictive, which the companies' executives knew this and failed to protect their youngest users.<ref>{{Cite web |last=Allyn |first=Bobby |date=25 Mar 2026 |title=Jury finds Meta and Google negligent in social media harms trial |url=https://www.npr.org/2026/03/25/nx-s1-5746125/meta-youtube-social-media-trial-verdict |url-status=live |access-date=26 Mar 2026 |website=npr}}</ref> [[Meta]] was charged to pay $4.2 million for compensatory and punitive damages, and charged Google $1.8 million.<ref>{{Cite web |last=Kang |first=Cecilia |last2=Mac |first2=Ryan |last3=Tan |first3=Eli |date=25 Mar 2026 |title=Meta and YouTube Found Negligent in Landmark Social Media Addiction Case |url=https://www.nytimes.com/2026/03/25/technology/social-media-trial-verdict.html |url-status=live |access-date=26 Mar 2026 |website=The New York Times}}</ref>


==See also==
==See also==
Line 130: Line 148:


*[[Advertising overload]]
*[[Advertising overload]]
*[[Google follows Samsung, asserts the right to steal your phone during a repair]]
*[[Google asserts the right to seize phones during repairs]]
*[[Google Nest Protect forced to use Google app]]
*[[Google Nest Protect forced to use Google app]]
*[[Google Nest thermostat smart features disabled]]
*[[Google Nest thermostat smart features disabled]]
*[[Google Pixel Watches do not come with repair options]]
*[[Google Pixel Watches do not come with repair options]]
==External links==
*"[https://www.jwz.org/xscreensaver/google.html XScreenSaver: Google Store Privacy Policy]". Google pretending to care about privacy by forcing a fully-local (no internet) minimal-permission screen-saver app to specify a privacy-policy. That blog-post contains many sources on Google's anti-consumer practices


==References==
==References==
<references />
<references />
[[Category:Google]]
[[Category:Google]]