Pixel owners report problems after installing January 2024 Google Play update

Original Article ↗ Hacker News Discussion ↗

Reports of Google Pixel phones becoming slow, unstable, or even unbootable after the January 2024 Google Play system update are raising concerns about Android reliability and Google’s quality assurance practices. Commenters note that while the issue doesn’t affect all devices, it has hit multiple Pixel generations and can leave users with few recovery options, potentially turning working phones into e‑waste. The incident fuels broader comparisons with iOS, interest in alternative Android ROMs like GrapheneOS and LineageOS, and calls for stronger accountability when over‑the‑air updates damage consumer hardware.

Scope and impact of the January 2024 Play system update

  • Update appears to affect some Pixels (5, 5a, 6/6a, 7/7a, 8/8 Pro), not all.
  • Reported failures: boot loops, devices entering low‑level Qualcomm EDL mode, storage errors, severe slowdowns, and random unresponsiveness.
  • Many commenters with various Pixels (including old 3/4a and new 7/8 series) report no issues, calling the headline overstated.
  • Staged rollout means many devices have not yet received the update; some users are delaying it.

Android/Pixel reliability experiences

  • Several long‑time Pixel/Nexus owners report years of instability: random reboots, alarms failing, camera or calls crashing, fingerprint problems, Bluetooth issues, and poor thermals/battery.
  • Others say Android (especially non‑Pixel brands like Sony, Moto, Samsung) has been stable for many years, suggesting problems may be Pixel‑specific or hardware‑related.
  • Pixel 5a “sudden death” and extended‑warranty disputes are cited as prior evidence of Pixel hardware/software fragility.

QA, culture, and update processes

  • Strong criticism of Google’s QA: perception that real‑world users are doing unpaid testing.
  • Claims that internal dogfooding exists but is ineffective due to organizational priorities and decayed engineering culture.
  • Comments that modern incentives reward shipping features, not avoiding regressions; QA staffing seen as out of fashion.
  • A/B update design was supposed to prevent bricks, yet devices still end up in EDL after failed OTAs.

Recovery, e‑waste, and liability

  • Technical discussion: Pixels in Qualcomm EDL could be revived via QPST/QFIL “firehose” images, but Google does not release them.
  • Some argue this unnecessarily creates e‑waste and harms users who can’t afford replacements.
  • Proposals: regulators should hold vendors liable for destructive updates, or require open‑sourcing if they refuse liability.
  • Others add that even if recovery is technically possible, it is far beyond typical users.

Alternatives and mitigation

  • Multiple users on GrapheneOS and LineageOS report no such issues and higher perceived reliability.
  • Advice to disable automatic system/app updates and defer Play system updates until issues are understood.
  • Some long‑time Android users, frustrated with Google’s handling, say they’ve switched or plan to switch to iPhones; others tout Samsung or cheap Android brands as more practical choices.