Urgent.News

What's breaking now, across thousands of outlets.

Tech

Google Home speakers are quietly downloading hundreds of GBs of data

Check to make sure your device isn't sapping your usage

Google Home speakers are quietly downloading hundreds of GBs of data

Google Home smart speakers are quietly consuming hundreds of gigabytes of data in the background, potentially causing users to exceed their limited internet data plans and face unexpected overcharges. Most users will likely remain unaware of this issue, as it can only be detected by examining router settings and monitoring data usage.

Many users on Reddit have reported this problem, with some experiencing up to 200GB of data downloaded daily. The first post about this issue appeared about a week ago, followed by posts detailing 35GB and 200GB of daily data usage, respectively.

The root cause of this data consumption appears to be a stuck update that downloads multiple times a day. Certain models of Google Home speaker, including the , seem to be more susceptible to this issue than others. It is recommended that users check their internet logs to ensure they are not affected by this bug. In case of a problem, users can alleviate the issue by unplugging their Google Home speaker for a few days.

Google has acknowledged the issue and is working on a fix, providing relief to users experiencing excessive data consumption.

Written by urgent.news from Android Police's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Also reported by 1 other outlet

Read the original at androidpolice.com →

More in Tech

Running Pandoc in the Browser: WebAssembly, Web Workers, and a 58 MB Module

Every "convert my document" tool I've tried has the same shape: you pick a file, it uploads somewhere, a server does the work, you get a download link back. That's fine for public data.

  • Running Pandoc in browser uses WebAssembly, Web Workers, and 58 MB module
  • Pandoc preserves document semantics through typed abstract syntax tree conversion
  • Module loaded lazily, cached, and executed in Web Worker to maintain UI responsiveness

Beyond Deployment: What's Next for CrescoDB, Plus a Clearer Path to Getting Started

Beyond Deployment: What's Next for CrescoDB, Plus a Clearer Path to Getting Started Building a backend is only part of the work.

  • CrescoDB improving backend workflow and developer insights
  • Upcoming update adds production monitoring and operational visibility tools
  • Server monitoring expanded to include CPU, memory, disk usage, and container resources

Part 3: `tokenprice` ($0.001) vs the price-feed incumbents — measured, not marketed

Part 3 of the x402 benchmark series. Part 1 covered the method and our baseline across 7 endpoints. Part 2 (websearch vs Exa vs Tavily) is still in the queue — we're waiting on API keys to run that…

  • tokenprice endpoint charges $0.001 per call, cheaper than CoinGecko's $0.01
  • Median latency of 1.8 seconds for various queries, distinguishing address vs ticker queries
  • Free trial available via curl command, with pricing details on API pricing page

More from Tuesday 20 October →