Edgar Cervantes / Android Authority
Tl;
- Android 16 Beta 3 became available to Pixel users to test last Thursday.
- Now Google has already got an update ready, as Beta 3.1 is starting to expire.
- This release fixes a handful of errors, including one that caused the screen to dampen during media playback.
When it comes to Google’s work of preparing Android 16 For the stable release, we are really starting to get to the end of the road. This year’s development has gone on an accelerated schedule, and last week we got what we thought would be our last beta in front of platform stability, with the release of Android 16 beta 3. It turns out that Googles get a little more mileage out of these beta yet, as it releases a new point release update.
Just as we saw Android 16 Beta 2.1 Country late last month with some bug fixes that just couldn’t wait for beta 3, today Google announce that Android 16 Beta 3.1 is deployed to testers with multiple bug fixes. Google shares the following improvements:
- Solved a problem that caused the system setting app to crash repeatedly at the launch if the system language was set to a language other than English. (Issue #403303683)
- Solved a problem that caused the brightness of the screen to swing between an app-specified brightness setting and the automatic, system-specific or user-specific brightness settings. (Issue no. 392522561)
- Corrected a performance problem that caused excessive battery drain from high CPU load.
- Directed a performance problem that sometimes caused memory leaks in the system server.
Whoever immediately captures our eyes there is the second, which we recently reported on a wave of user complaints about Unexpected screen that dimmer with apps like Netflix Following the release of Google’s march update for pixels. Apparently there is a problem with Android 16, also because it reports that Google links to describe the same behavior. In the future, at least beta 3.1 will sip it in the bud.
Anyone already testing Android 16 Beta 3 on their Pixel phones will get a 3.1 as an OTA update, so there are really no actions needed on your part beyond being on the lookout for that update alert.