Google confirms Pixel 6a battery nerf due to overheating; AOSP changes to impact custom ROMs for Pixel phones

Google is making headlines for two distinct but significant developments affecting its Pixel smartphone lineup. For owners of the popular Pixel 6a, a looming software update will intentionally limit battery performance to address a serious overheating risk. In a separate move, Google has altered its approach to the Android Open Source Project (AOSP), a change that will create major hurdles for custom ROM developers who build alternative software for Pixel phones.

Pixel 6a batteries to be throttled for safety

The Google Pixel 6a, launched in 2022, was a massive hit for bringing Google’s flagship Tensor chip to a more affordable price point. Many people are still happily using the device today. However, recent events suggest it might be time for those users to pay close attention to their phone’s battery health.

Over the last several months, a worrying trend has emerged. As first reported by Android Authority, multiple Pixel 6a owners have shared disturbing accounts of their phones catastrophically overheating, with some even catching fire and melting their plastic chassis. These incidents, initially thought to be isolated, appear to point to a more fundamental problem.

Now, Google has officially confirmed these fears. In a statement to Android Authority, the company acknowledged the issue, stating, “A subset of Pixel 6a phones will require a mandatory software update to reduce the risk of potential battery overheating.”

This mandatory update will act as a fail-safe. Once a Pixel 6a’s battery has gone through 400 charge cycles, the software will automatically reduce the battery’s maximum capacity and slow down its charging speed. The goal is to put less stress on aging batteries and prevent them from reaching dangerous temperatures.

Code discovered in the latest Android 16 beta shows that users will receive a warning when their battery reaches 375 charge cycles, advising them to seek a replacement. This isn’t the first time Google has faced such an issue. The company had to take similar steps with the Pixel 4a, which also suffered from overheating batteries.

For Pixel 6a owners, the message is clear. Battery fires are incredibly dangerous. You can check your battery’s health in your phone’s settings. If you receive a warning or have owned your phone for a couple of years, it’s strongly recommended to either get the battery replaced or consider upgrading your device. Google says it will contact affected customers next month with more information.

Google deals a blow to custom ROM developers

While Google is trying to solve a hardware problem for some users, it’s creating a software headache for its most dedicated enthusiast community. The company just made a fundamental change to how it handles the Android Open Source Project, the very foundation of Android.

Historically, Google has made it easy for independent developers to build custom versions of Android, known as custom ROMs, for Pixel phones. They provided key files called “device trees” and driver binaries, which are essential for making the open-source software work properly with the Pixel’s specific hardware.

With the recent source code release for Android 16, developers quickly noticed these crucial files were missing. The move sparked concern that Google was walling off its ecosystem.

Seang Chau, Google’s VP of Android Platform, clarified on X that “AOSP is NOT going away.” He explained that Google is intentionally shifting its AOSP reference device away from Pixel phones. Instead, they will use a virtual device called “Cuttlefish,” which runs on PCs. The logic is to make AOSP a more neutral platform, independent of any specific consumer hardware.

While that sounds reasonable, the practical effect is a major blow to the custom ROM scene. Developers behind popular ROMs like LineageOS now face a much more difficult path. Nolen Johnson of the LineageOS project told Android Authority that the process will now be “painful.”

Without Google providing the device trees, developers will have to reverse-engineer them from older versions, essentially guessing what changes are needed to support new Android releases on Pixels. This brings Pixel phones down to the same level as devices from other manufacturers, removing a key advantage that made them a favorite among tinkerers and privacy advocates.

Pixels are still easy to unlock, but this change significantly increases the workload for the volunteer developers who keep the custom ROM scene alive, potentially impacting the quality and stability of future builds for Pixel devices.