Google Chromebook: Difference between revisions
Bythmusters (talk | contribs) m Added Cargo template in place of Infobox |
Added archive URLs for 1 citation(s) using CRWCitationBot |
||
| Line 18: | Line 18: | ||
There have been reports of Google's ScreenAI being enabled on Chromebooks via the Google Chrome web browser by default.'''<ref name="CBrick">{{Cite web |last=Isaac |first=Rob |date=24 Mar 2025 |title=Today Google bricked my Chromebook by force-installing a hidden extension |url=https://news.ycombinator.com/item?id=43514087 |url-status=live |archive-url=https://web.archive.org/web/20250331115019/https://news.ycombinator.com/item?id=43514087 |archive-date=31 Mar 2025 |via=Hacker News, originally posted on Mastodon}}</ref>'''<ref name=":0">{{Cite web |last=Gerard |first=David |date=29 Mar 2025 |title=Google ScreenAI: make your Chromebook melt down |url=https://pivot-to-ai.com/2025/03/29/google-screenai-make-your-chromebook-melt-down/ |url-status=live |archive-url=https://web.archive.org/web/20250329233052/https://pivot-to-ai.com/2025/03/29/google-screenai-make-your-chromebook-melt-down/ |archive-date=29 Mar 2025 |access-date=21 Jun 2025 |website=Pivot to AI}}</ref> The accessibility tool was put into the [[wikipedia:Chromium_(web_browser)|Chromium]] project, which provides the foundation for the Google Chrome web browser and many other web browsers; potentially affecting the majority of web browsers that are used.<ref name=":0" /> | There have been reports of Google's ScreenAI being enabled on Chromebooks via the Google Chrome web browser by default.'''<ref name="CBrick">{{Cite web |last=Isaac |first=Rob |date=24 Mar 2025 |title=Today Google bricked my Chromebook by force-installing a hidden extension |url=https://news.ycombinator.com/item?id=43514087 |url-status=live |archive-url=https://web.archive.org/web/20250331115019/https://news.ycombinator.com/item?id=43514087 |archive-date=31 Mar 2025 |via=Hacker News, originally posted on Mastodon}}</ref>'''<ref name=":0">{{Cite web |last=Gerard |first=David |date=29 Mar 2025 |title=Google ScreenAI: make your Chromebook melt down |url=https://pivot-to-ai.com/2025/03/29/google-screenai-make-your-chromebook-melt-down/ |url-status=live |archive-url=https://web.archive.org/web/20250329233052/https://pivot-to-ai.com/2025/03/29/google-screenai-make-your-chromebook-melt-down/ |archive-date=29 Mar 2025 |access-date=21 Jun 2025 |website=Pivot to AI}}</ref> The accessibility tool was put into the [[wikipedia:Chromium_(web_browser)|Chromium]] project, which provides the foundation for the Google Chrome web browser and many other web browsers; potentially affecting the majority of web browsers that are used.<ref name=":0" /> | ||
Rob Isaac's complaint is that the machine has become "too hot to touch" and that the extra load has made it essentially unusable, significantly reducing the battery life.<ref name="CBrick" /> Chromebook users confirm these complaints on their own machines, and have posted their complaints on the Chromebook help forums.<ref name=":0" /> Other concerns are that the software is invasive, similar to [[Microsoft#Recall|Microsoft's Recall]] feature, and that the software itself is not transparent, as the source code for ScreenAI is not available to the public.<ref>{{Cite web |date=6 May 2024 |title=Development and Deployment of ScreenAI |url=https://github.com/chromium/chromium/blob/main/services/screen_ai/README.md#development-and-deployment |access-date=21 Jun 2025 |website=GitHub}}</ref> | Rob Isaac's complaint is that the machine has become "too hot to touch" and that the extra load has made it essentially unusable, significantly reducing the battery life.<ref name="CBrick" /> Chromebook users confirm these complaints on their own machines, and have posted their complaints on the Chromebook help forums.<ref name=":0" /> Other concerns are that the software is invasive, similar to [[Microsoft#Recall|Microsoft's Recall]] feature, and that the software itself is not transparent, as the source code for ScreenAI is not available to the public.<ref>{{Cite web |date=6 May 2024 |title=Development and Deployment of ScreenAI |url=https://github.com/chromium/chromium/blob/main/services/screen_ai/README.md#development-and-deployment |access-date=21 Jun 2025 |website=GitHub |archive-url=http://web.archive.org/web/20251023201813/https://github.com/chromium/chromium/blob/main/services/screen_ai/README.md |archive-date=23 Oct 2025}}</ref> | ||
==Products== | ==Products== | ||
Revision as of 05:19, 23 February 2026
⚠️ Article status notice: This article has been marked as incomplete
This article needs additional work for its sourcing and verifiability to meet the wiki's Content Guidelines and be in line with our Mission Statement for comprehensive coverage of consumer protection issues.
This notice will be removed once sufficient documentation has been added to establish the systemic nature of these issues. Once you believe the article is ready to have its notice removed, please visit the Moderator's noticeboard, or the discord and post to the #appeals channel.
Learn more ▼
| Basic Information | |
|---|---|
| Release Year | 2011 |
| Product Type | Hardware, Laptops |
| In Production | Yes |
| Official Website | Google Chromebook |
Consumer impact summary
Incidents
This is a list of all consumer protection incidents related to this product line. Any incidents not mentioned here can be found in the Google Chromebook category.
Automatic installation of Google's ScreenAI extension (2025)
There have been reports of Google's ScreenAI being enabled on Chromebooks via the Google Chrome web browser by default.[1][2] The accessibility tool was put into the Chromium project, which provides the foundation for the Google Chrome web browser and many other web browsers; potentially affecting the majority of web browsers that are used.[2]
Rob Isaac's complaint is that the machine has become "too hot to touch" and that the extra load has made it essentially unusable, significantly reducing the battery life.[1] Chromebook users confirm these complaints on their own machines, and have posted their complaints on the Chromebook help forums.[2] Other concerns are that the software is invasive, similar to Microsoft's Recall feature, and that the software itself is not transparent, as the source code for ScreenAI is not available to the public.[3]
Products
See also
References
- ↑ 1.0 1.1 Isaac, Rob (24 Mar 2025). "Today Google bricked my Chromebook by force-installing a hidden extension". Archived from the original on 31 Mar 2025 – via Hacker News, originally posted on Mastodon.
- ↑ 2.0 2.1 2.2 Gerard, David (29 Mar 2025). "Google ScreenAI: make your Chromebook melt down". Pivot to AI. Archived from the original on 29 Mar 2025. Retrieved 21 Jun 2025.
- ↑ "Development and Deployment of ScreenAI". GitHub. 6 May 2024. Archived from the original on 23 Oct 2025. Retrieved 21 Jun 2025.