Android 16 QPR1 is almost finished, while Beta 3.1 arrives

Regarding Google Hardware, August has arrived to inaugurate the latest range, and at this stage, we are less than a week from the Big Pixel 10 produced by Google Event. But for as exciting as that, we are already looking forward to September, when the last Google software that will attract our full attention. It is then that we expect Android 16 QPR1 stable and its deployment. But before the arrival of this day, we have what could be the last beta QPR1 to try.

It has been almost a month now that Android 16 QPR1 Beta 3 has arrived, and although we have spotted a handful of changes that were incoming, like the enlarged keyboard which made its debut on Android Canary, there was not a ton of settings for users who were new – just as we would touch a beta at this late stage, to be fair.

This afternoon, Google published Android 16 QPR1 BETA 3.1, an update to fix BOGUES in addition to QPR1 BETA 3. The new version is labeled as BP31.250610.009 (.009.A1 for the pixel tablet), and just like the previous versions, we see it for the Pixel 6 and later models.

According to the Publication Notes QPR1 page, BETA 3.1 includes fixes for the following problems:

• Instability or restarting of the Wi-Fi device by improving how the system deals with network statistics. (Number n ° 433037402,, Number n ° 432867183,, Number 433418936,, Number n ° 432795362,, Number n ° 432770117,, Number 432699126,, Number n ° 435489862,, Number n ° 435011484))
• The HUB Context, a low -power sensor component, would block due to the excessive use of the main memory, causing instability of the device; Solved by optimizing memory allowance and preventing memory leaks. ( Number n ° 420999948,, Number 426316038))
• The home screen has sometimes lost its lower row of pinned applications and the search bar, which makes them inaccessible; This was corrected by adjusting how these elements reappear after the screen transitions. (Number 428088033,, Number 428405658,, Number 429817851))
• The notifications would overlap in the shade, hampering readability, by refining the display of the notification and the logic of dismissal animation. (Number n ° 421792538,, Number n ° 422749237,, Number 420418750,, Number n ° 428896474))
• A problem that caused unexpected restarts of the devices. (Number n ° 427676713))
• The quick user interface on unfolded foldable devices appeared coupe or poorly aligned due to incorrect padding caused by the double counting of the camera cutting. (Number n ° 419184923,, Number n ° 421879049,, Number n ° 421810067,, Number 423172198,, Number n ° 422560004,, Number n ° 424116279))
• A problem that has restarted unexpected devices. (Number No. 408888279,, Number No. 409949346,, Number n ° 409960197,, Number 410624610,, Number No. 407373090,, Number n ° 430095518))
• The status bar appearing in the shade of the quick parameters has sometimes been ill -aligned with the standard status bar, causing visual inconsistency. (Number n ° 419573315,, Number n ° 419134909,, Number n ° 432794874))
• Addressed a clash or a crash of the system, especially during unlocking, caused by reading the ambient light sensor of the camera (SLA) is stuck, implementing a non -blocking method for the recovery of sensor data. (Number n ° 421870862,, Number No. 420725698))
• The multimedia player on the lock screen sometimes disappeared or did not respond. (Number 420517884))
• A problem in which the notification shade displayed a large growing gap, obscuring notifications, correcting how notification animations were cut. (Number n ° 421366916))
• A problem where the notification of the multimedia player can appear cut or disappear during the rotation of the device, by improving the way in which its display area is dimensioned and updated in user interface transitions. (Number n ° 433040374))
• Video calls initiated from vocal calls no longer know silent audio; An audio system corrective now manages the sound output during transitions of the call type. (Number n ° 434139133,, Number 427060263,, Number n ° 438414975))
• A problem where the black translucent bars appeared at the top and bottom of the home screen after leaving the apps in full screen by correcting how the transitional system states were erased. (Number n ° 425407737,, Number n ° 433929827))
• A problem that caused the unexpected device and restart and restart during an OTA update.
• A problem causing occasional restarts of the devices after the system updates.
• Widgets on the home screen were not responsible for taking care due to the search for obsolete application files.
• Entering from time to time has ceased to operate in applications because the processes of the internal input system could run.
• The accidents of the aircraft are caused by the context center which moves away from memory.
• Bluetooth accidents and the instability caused by an “type of unrescited package” were resolved.
• [RG5][BD1A.250219.006]Unable to manage the pagination request of the nucleus, PC is at Edgetpu_kci_release_vmbox, LR is at Edgetpu_kci_release_vmbox
• A problem that could cause telephone disconnections or system accidents during calls by solving a memory corruption bug in audio data tampon management linked to audio reading speed changes.
• A brief screen sparkle occurred when launching applications from the notification shade.
• A system crash that could occur when using the multimedia features of your device, especially when connected to a computer transfer, by improving the internal management of multimedia connection resources.

Users registered in Android beta for the Pixel program Should simply sit at this stage and wait for their updates to arrive via the OTA notification. Since this is only a punctual version, do not expect to see new features in this version.

This article was updated at 5:37 p.m. to add the official version notes for Android 16 QPR1 BETA 3.1.