- Some Pixel 6A phones overheated while loading
- Google says it will solve the problem with a software update
- The update will limit the capacity of the battery and the loading speed
You may have spotted several reports of Google Pixel 6A phones to set fire and burn in recent weeks, and Google now takes measures to stop any future incident by limiting the battery capacity and the loading speed of the 2022 handsets.
In a statement to Android Authority, a Google spokesperson said that a “subset” of Pixel 6A phones will soon receive a “compulsory” software update, reducing battery capacity and load performance once 400 cycles have been achieved.
This should “reduce the risk of potential drums overheating” according to Google, although it leaves you a phone that takes care of more slowly and does not last as long between charges – not ideal for a handset that has only been released for three years.
Google indicates that users with assigned phones will be contacted next month with details on what they have to do. Meanwhile, the Android team Authority has spotted a warning concerning a potential battery overheating problem on the 6a pixel in the last Android 16 Beta.
Keep an eye on your phone
It is difficult to assess how common this problem is, but Android Authority has already recorded two distinct incidents, and there are images as proof. It is frightening to think that your phone could suddenly ignite while it was left in charge.
Since Google only mentions a “subset” of Pixel 6A phones, it is possible that only certain handsets are affected. We may not see this update takes place for each 6a pixel, but for the moment, it is not clear anyway.
If you have a Google Pixel 6a, it’s a good idea to keep it an eye while it loads: search for any type of deformation and check that the handset is not too hot to the touch. The very short battery life can also indicate a battery health problem.
Swelling and overheating can potentially arrive at any lithium -ion battery, if it is physically damaged or sort of dysfunctions, but it is a problem that continues to occur with Pixel phones – more recently with the Google Pixel 7A.
