Google: Difference between revisions
SinexTitan (talk | contribs) →Controversies: bypass redirect |
m Style changes according to Wiki Style Guide |
||
| Line 35: | 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==== | ||
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==== | ||
{{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 51: | 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=== | ||
{{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 68: | Line 68: | ||
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. | 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 | 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> | ||