\nThe post How Many Pixels Have to Catch Fire Before Google Does Something? appeared first on Android Headlines.
\n
![](\"https:\/\/plus.maciejpiasecki.info\/wp-content\/uploads\/2025\/08\/Pixel-6a-Photo-8.png\"){kind=tracking}
\nSource: ndroidheadlines.com <\/p>\n","protected":false},"excerpt":{"rendered":"
The Pixel 6a comes with a SIM ejector tool, a quick switch adapter, a USB-C to USB-C cable, and of course, the phone. But with recent battery issues, maybe Google should consider bundling a fire extinguisher with future iterations of its Pixel A-series models.<\/p>\n
Because over the past year, at least five Pixel 6a units have caught fire. And we\u2019re not talking about \u201cfire\u201d in the colloquial \u201cthis phone is fiyah\u201d kind of way. We\u2019re talking battery-swelling, chassis-melting, display-popping literal flames. One user woke up to the smell of smoke. Another had to toss their flaming phone into the toilet.<\/p>\n
To be clear, these Pixel A-series battery issues aren\u2019t isolated accidents. They come on the heels of Google issuing software updates that deliberately nerf the battery performance of both the Pixel 4a and 6a, supposedly to avoid overheating. But yet here we are. Melted phones and no official recall in sight. Just a quiet Battery Performance Program that we\u2019re not sure actually works.<\/p>\n
Which makes you wonder: are corners being cut somewhere, and are users paying the price? And is this Google\u2019s Samsung Galaxy Note 7 moment?<\/p>\n
The Pixel A-Series Proposition: Great Value, Until It Isn\u2019t<\/p>\n
Google\u2019s Nexus phones were all about clean software, no gimmicks, and fair pricing. That spirit carried over briefly into the early Pixel years, before prices started climbing to match Apple and Samsung. Suddenly, \u201cpure Android\u201d came with a premium. Call it the Google tax.<\/p>\n
The A-series was supposed to be the answer to that. Budget-friendly, stripped-down, and smart. You didn\u2019t get the latest hardware, but you got the Pixel experience, such as timely updates, great software, and the same camera magic. It was the sensible choice, especially in today\u2019s economy.<\/p>\n
But now the batteries are swelling, melting, and catching fire. And that value proposition? It\u2019s starting to look more like a liability.<\/p>\n
To hit those budget-friendly price points, Google clearly had to make compromises. And maybe, just maybe, those corner-cutting decisions are finally catching up. The Pixel 4a and 6a are now both on battery-throttling life support.<\/p>\n
Worse, this isn\u2019t just an A-series problem. Even the flagship Pixels have been riddled with hardware issues: screens showing pink lines, fingerprint sensors that barely register, phones that overheat under light use, camera bars literally popping off the Pixel 9. Let\u2019s not forget, software issues that have not been addressed for half a year. <\/p>\n
These are not isolated incidents. It\u2019s starting to feel like a pattern of inconsistency and poor quality control.<\/p>\n
From Battery Throttling to Battery Fires<\/p>\n
The Pixel A-series battery issues didn\u2019t start with the 6a. It started with the 4a. Earlier this year, Google quietly pushed a software update that throttled battery performance, citing overheating concerns. Charging got slower, and battery life went into the toilet. The fix was a limited battery swap program or $50\u2013$100 in Google Store credit. More on that later, but it wasn\u2019t exactly generous.<\/p>\n
In Australia, the situation escalated. The ACCC issued an official recall, warning that the Pixel 4a\u2019s overheating battery could cause fires or burns.<\/p>\n
Then the Pixel 6a caught fire, literally. At least five cases have surfaced so far, including one phone that already had the safety update. Another unit melted into a user\u2019s clothes while charging overnight.<\/p>\n
Google\u2019s response came in the form of a software patch called the \u201cBattery Performance Program.\u201d After 400 charge cycles, it slows down charging and caps battery use to reduce risk. But it doesn\u2019t always work. And even when it does, it leaves users with a crippled device. In some places, replacement batteries aren\u2019t even available.<\/p>\n
So users are stuck with a choice: live with a phone that is a shell of its former self, or buy a new one. Either way, Google escapes liability, and users are left holding the fire hazard.<\/p>\n
No Recall, Just Risk Management<\/p>\n
So far, five Pixel 6a units have caught fire, with one of them catching fire after receiving Google\u2019s so-called \u201cBattery Performance Program\u201d update. The fix was supposed to prevent exactly this. It didn\u2019t. And yet, there\u2019s still no recall, no formal investigation, and not even a warning page pinned to Google\u2019s own support site.<\/p>\n
Instead, Google quietly pushed out a software update that throttles battery capacity after 400 charge cycles and called it a day. The ACCC echoed this, telling users that as long as they update their devices, they\u2019re fine, and that \u201cConsumers do not need to return their devices.\u201d But \u201cfine\u201d doesn\u2019t describe phones that melt, explode, or burn through clothing.<\/p>\n
Google is lucky no one\u2019s been injured. Yet. But are they really going to wait for that headline before taking action? Are they going to wait until someone shows up in the ER with third-degree burns? Do they really want to have that scrolling across the news ticker in the evenings?<\/p>\n
Unlike Samsung, Google doesn\u2019t have the luxury of a dozen different smartphone lines. There\u2019s no \u201cPixel Lite\u201d brand to sacrifice. If one Pixel burns a hole in someone\u2019s pocket, literally, it scorches the entire brand. Samsung ultimately killed off its Note series, but it still had the Galaxy S-series to fall back on. It also has its budget-friendly Galaxy A-series that drives most of its revenue.<\/p>\n
This is when Google needs to get proactive. Issue a recall. Make it right. Because if they don\u2019t, they\u2019re not just risking battery fires,\u00a0 they\u2019re risking the reputation of every Pixel to come. At this point, I wouldn\u2019t feel comfortable recommending a Pixel phone to anyone.<\/p>\n
Loyalty, Punished<\/p>\n
Google\u2019s idea of \u201ccompensation\u201d for these battery issues is a choice: $50 in cash, or $100 in store credit toward a new Pixel. On paper, it looks fair. But in practice? Less so.<\/p>\n
The cash can be used freely. The $100 voucher, on the other hand, cannot be stacked with sales, according to a customer posting on Google\u2019s support forums. Try to use it during a discount, and the voucher gets absorbed into the sale price. This essentially makes it worthless. You pay what everyone else pays, and your \u201ccompensation\u201d evaporates.<\/p>\n
So if you chose the voucher thinking it was the better deal, you\u2019re punished for wanting to stay loyal to Google. That\u2019s exactly what happened to the original poster, who detailed how they planned to keep their phone for another year or two, but were forced to replace it early due to Google\u2019s software update throttling the battery. They chose the voucher in good faith. However, little did they know it would trap them into paying full price for a phone that anyone else could get cheaper.<\/p>\n
When they asked Google Support for help, they got copy-pasted policy replies that completely ignored the issue.<\/p>\n
That\u2019s just bad business ethics. Google broke these phones and then tried to spin a bait-and-switch as compensation. What happened to \u201cYou break it, you fix it\u201d? The message is clear: Google thinks it\u2019s indispensable to the point where brand loyalty can kiss its colorful behind.<\/p>\n
Maybe it\u2019s time we start taking our money elsewhere.<\/p>\n
Conclusion: Google Needs to Wake Up<\/p>\n
Google can\u2019t keep treating the Pixel A-series battery issues like they\u2019re just another support ticket. Throttling the Pixel 6a\u2019s battery might lower the odds of it bursting into flames, but it doesn\u2019t change the fact that it ever could in the first place. That alone should\u2019ve triggered a recall. Instead, we got silence, store credit, and half-hearted firmware updates.<\/p>\n
And it\u2019s happening while Google pours money into its custom Tensor chips, ramps up Pixel availability worldwide, and tries to convince us it\u2019s serious about hardware. But you can\u2019t ask people to buy into the Pixel brand when your response to literal fire hazards is a $100 Play Store voucher.<\/p>\n
That\u2019s not how you treat customers who are willing to spend their hard-earned money on your product.<\/p>\n
Most people who bought a Pixel A-series phone just wanted a reliable, affordable device. They didn\u2019t sign up for hidden battery throttling or the risk of waking up to smoke. If Google wants to compete with Apple and Samsung, it needs to grow up and take responsibility. That means real transparency, actual fixes, and an apology that isn\u2019t buried in a firmware changelog.<\/p>\n
Because right now, it\u2019s not just batteries that are catching on fire, it\u2019s everything the Pixel brand was supposed to stand for.
\nThe post How Many Pixels Have to Catch Fire Before Google Does Something? appeared first on Android Headlines.
\n
\nSource: ndroidheadlines.com
<\/p>\n","protected":false},"excerpt":{"rendered":"
The Pixel 6a comes with a SIM ejector tool, a quick switch adapter, a USB-C to USB-C cable, and of […]<\/p>\n","protected":false},"author":80,"featured_media":17470,"comment_status":"false","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-17469","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-bez-kategorii"],"_links":{"self":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts\/17469","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/users\/80"}],"replies":[{"embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/comments?post=17469"}],"version-history":[{"count":1,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts\/17469\/revisions"}],"predecessor-version":[{"id":17471,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts\/17469\/revisions\/17471"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/media\/17470"}],"wp:attachment":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/media?parent=17469"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/categories?post=17469"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/tags?post=17469"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}