{"id":101970,"date":"2025-07-29T11:49:12","date_gmt":"2025-07-29T11:49:12","guid":{"rendered":"https:\/\/www.europesays.com\/us\/101970\/"},"modified":"2025-07-29T11:49:12","modified_gmt":"2025-07-29T11:49:12","slug":"google-released-an-update-to-stop-pixel-6as-catching-fire-then-another-one-caught-fire","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/us\/101970\/","title":{"rendered":"Google released an update to stop Pixel 6as catching fire \u2014 then another one caught fire"},"content":{"rendered":"

Those of you who are still using a Pixel 6a<\/a> might want to be careful. Earlier this year, reports started surfacing about the phones catching fire, forcing Google to release an update designed to stop overheating. Unfortunately, that might not have been enough to solve the issue.<\/p>\n

Android Authority<\/a> spotted another instance of the Pixel 6a combusting while charging over on Reddit from u\/footymanageraddict<\/a>. Apparently, the phone caught fire while the user was sleeping on Saturday night (July 26) while plugged into a 45W Steam Deck<\/a> charger.<\/p>\n

The user claims they were woken by a “horrible smell and a loud noise,” at which point the fire had already started. They managed to throw the phone to the tile floor via the charging cord, but before that, it had been less than 40cm (15.7 inches) from their head on the nightstand.<\/p>\n

You may like<\/p>\n

Needless to say, being this close to the bed meant there was extra damage, including burnt sheets and damage to the surface of a nearby A\/C unit. The user also mentioned that their throat “hurt all day from the fumes [they] inhaled” \u2014 exacerbated by the fact that their door was shut and the time they spent trying to stop the fire spreading.<\/p>\n

As someone who has been woken up by a phone smoking and the panic that caused, I can’t imagine how much worse it must be to wake up and see a fire so close to your head.<\/p>\n

What’s going on with the Pixel 6a?<\/p>\n

\"Google<\/p>\n

(Image credit: Tom’s Guide)<\/p>\n

The worst part is that the phone apparently already had Google’s “Battery Performance Program” Update<\/a> installed. That update was supposed to stop batteries from overheating and avoid further instances of Pixel 6a phones going up in flames. If what this user says is true, that update may not be working exactly as intended.<\/p>\n

Google has also recommended getting a battery replacement for all affected devices. This is free and available via mail or as a walk-in appointment. Sadly, u\/footymanageraddict claims a walk-in replacement wasn’t available in their area.<\/p>\n

Get instant access to breaking news, the hottest reviews, great deals and helpful tips.<\/p>\n

They also claim that they didn’t take advantage of the mail-in replacement for reasons relating to time, uncertainty about the process and the fact that Google only “recommended” getting it done. So it sounds like they thought the update would be enough.<\/p>\n

While we don’t know if there were any other underlying problems with this phone, any Pixel 6a owners should proceed with caution. Get the battery replaced, even if it means mailing your phone away and stick to Google’s own charging advice \u2014 and use official chargers and cables wherever possible.<\/p>\n

If that’s not possible, don’t charge the phone while you’re sleeping or otherwise occupied. I’d also avoid using any kind of fast charging, since those extra speeds can lead to excess heat building up \u2014 which is the last thing you want with a potentially volatile phone.<\/p>\n

Follow Tom’s Guide on Google News<\/a> to get our up-to-date news, how-tos, and reviews in your feeds. Make sure to click the Follow button.<\/p>\n

More from Tom’s Guide<\/p>\n","protected":false},"excerpt":{"rendered":"Those of you who are still using a Pixel 6a might want to be careful. Earlier this year,…\n","protected":false},"author":3,"featured_media":101971,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17],"tags":[611,158,67,132,68],"class_list":{"0":"post-101970","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-mobile","8":"tag-mobile","9":"tag-technology","10":"tag-united-states","11":"tag-unitedstates","12":"tag-us"},"share_on_mastodon":{"url":"https:\/\/pubeurope.com\/@us\/114936372572408863","error":""},"_links":{"self":[{"href":"https:\/\/www.europesays.com\/us\/wp-json\/wp\/v2\/posts\/101970","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/us\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/us\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/us\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/us\/wp-json\/wp\/v2\/comments?post=101970"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/us\/wp-json\/wp\/v2\/posts\/101970\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/us\/wp-json\/wp\/v2\/media\/101971"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/us\/wp-json\/wp\/v2\/media?parent=101970"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/us\/wp-json\/wp\/v2\/categories?post=101970"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/us\/wp-json\/wp\/v2\/tags?post=101970"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}