It was the kind of morning nobody wants. A Reddit user, going by u/footymanageraddict, awoke on July 26 to a “horrible smell and a loud noise.” They found their Google Pixel 6a engulfed in flames, screen melted, case deformed, and charging atop a nightstand just 40cm from their head. Sheets caught fire, nearby AC vents bore scorch marks, and the user spent the rest of the day nursing a sore throat from inhaling toxic fumes.

What makes this incident especially galling is that Google had already issued a mandatory “Battery Performance Program” update precisely to prevent overheating—and fires—on the Pixel 6a. Rolled out in early July on Android 16, the firmware limits battery capacity and charging speed once a device hits 400 full charge cycles. Google even sweetened the deal by offering free battery replacements for eligible units. Yet here we are: a fifth Pixel 6a catching fire this month alone, suggesting software alone isn’t enough to plug the leak.

This latest blaze isn’t an isolated freak accident. Since December 2024, owners in North America, Europe, and Australia have documented at least five Pixel 6a fires—some dramatic enough that cleanup crews needed hazmat suits. In one early case, a user managed to halt a device ablaze by submerging it in water; in another, a phone “exploded into flames” on a café table. Reports consistently mention third‑party chargers—often rated 45W or higher—though Google representatives have stopped short of blaming accessories.

Android Authority’s Hadlee Simons calls the recurrence “very concerning” and notes that updates so far have failed to fully stem the tide of incidents. The Reddit community, meanwhile, is awash in dark humor and panic: threads brim with users asking whether charging at 15W even works, or if they should just swap to airplane mode and hope for the best.

Google’s response to date has been part-software patch, part-consumer relations play. The July 8 firmware update carries built‑in throttling for “impacted devices”—those with certain serial numbers or manufacturing windows—yet the feature remains dormant until the battery accrues 400 cycles; few devices in early 2023 batches have reached that threshold. Meanwhile, the company launched a “battery replacement program,” but it’s only available via mail‑in in most markets, leaving customers in countries with limited service centers (like Australia) in limbo.

In Australia, the situation escalated on July 25, when the Australian Competition and Consumer Commission (ACCC) published an official recall notice. The regulator warned that “an overheating battery could pose a risk of fire and/or burns,” and confirmed that “incidents have occurred resulting in serious burn injuries.” The notice clarifies that devices with model number G1AZG are impacted, urges consumers to verify firmware installation, and assures them they need not surrender their phones—though Google may offer “appeasement” remedies.

What should you do?

1. Check your update status. On Pixel 6a, go to Settings → About → Android version. Make sure you’re on the July 2025 security patch or later, which includes the throttling firmware.
2. Avoid high‑wattage chargers. If you’re using a 45W Steam Deck charger—or any charger above Google’s recommended 18W—consider switching to the stock 18W adapter for now. Third‑party chargers may push current faster than the battery can safely handle, especially on aging cells.
3. Monitor charge cycles. You can find your battery’s charge cycle count by using Android’s adb tool (adb shell dumpsys battery), or with third‑party apps. If you’re above 300–350 cycles, beware: that’s nearing the 400‑cycle throttle point.
4. Request a battery replacement. If you’re in a region with mail‑in service only, contact Google Support immediately to start the mailed‑in replacement process. For those in Australia, the ACCC recall page (published July 25, 2025) explains how to check eligibility and arrange repair without cost.

Casual users may wonder why Google didn’t simply recall and swap batteries outright. The answer likely lies in supply‑chain costs, retrofit complexity, and reputational risk. But when your budget flagship laptop-in‑pocket ignites beside your pillow, half‑measures feel dangerously inadequate.

This saga highlights a growing tension in consumer tech: the race to pack ever‑more battery life (and speedy charging) into pocket‑sized slabs of aluminum clashes with the slow march of battery chemistry improvements. Until manufacturers and regulators demand more robust safety certifications—think aerospace‑grade testing for everyday gadgets—consumers will remain guinea pigs for incremental software “mitigations” that arrive too little, too late.

So, yeah: thank Google—for reminding us that we shouldn’t sleep next to our chargers. And perhaps, if enough phones catch fire, they’ll finally swap more batteries, expand walk‑in repair options, or, dare we hope, issue a full recall before another morning alarm goes off to the crackle of burning plastic.