Android 16: July update has two Pixel fixes and a needed update for the 6a

Contents

Google has announced that it will be rolling out the July update for its Pixel smartphones and tablets in stages. As usual, the rollout of the fixes for Android 16 will take place over the course of a week. Almost all supported Pixel devices – from Pixel 6a to 9 Pro XL – will receive the new firmware with the build number BP2A.250705.008. Surprisingly, the update does not contain any security patches.

No update for Pixel 6 and 6 Pro – but the 6a

Google is also leaving the Pixel 6 and 6 Pro models empty-handed this month, while the Pixel 6a is receiving the announced mandatory battery update. This provides “important battery management functions” for the budget model, which reduces the battery capacity and charging power on affected devices when the battery has reached 400 charging cycles.

In mid-June, Google announced battery problems with the Pixel 6a and announced a mandatory software update to reduce possible overheating problems. The manufacturer later said that it would be released on July 8. The update is intended to reduce the risk of potential battery overheating in affected devices.

Small updates for Pixel devices

As can be seen from the changelog, the July Pixel update only has two improvements on board: Firstly, Google has optimized the visual user experience in apps such as Android Auto and should now be smoother.

Secondly, Google's Android team has worked on improving Wi-Fi stability. It is said that the connection quality has been improved under certain conditions. Unfortunately, the manufacturer is not more specific.

Android 16: Google fixes lockscreen bug

In addition to the monthly update, Google is delivering a bug fix, according to Android Authority, that should wake Pixel smartphones with Android 16 from standby more quickly. It is one of several known Android 16 bugs.

However, the bug will not be fixed via the July patch, but apparently via a Play Services update that will be automatically installed in the background. Users do not need to do anything, but it could take a few days or weeks before it is distributed across the board.

(afl)