The Beta Android 16 QPR1 update is a buckt fixing monster

Google gave us the Android 16 QPR1 beta 3 update a month ago and there was a handful of bugs to crush from the previous beta version. Today, Google has published the QPR1 3.1 update and the list of bugs has corrected stretching at 20+. As for what should be a small update, it seems quite important in terms of solved problems. It will be an update to enter your Pixel device as quickly as possible.

Android 16 QPR1 3.1 Pixel update: Google has abandoned this new Android 16 QPR1 3.1 Update like Build BP31.250610.009 for all phones, plus BP31.250610.009.A1 for the Pixel tablet. As with the previous versions, this new QPR1 update is available for pixels 6 and 6 pro, Pixel 6A, Pixel 7 and 7 Pro, Pixel 7A, Pixel Fold, Pixel Tablet, Pixel 8 and 8 Pro, Pixel 8A, Pixel 9, 9 Pro, 9 Pro XL, 9 Pro Fold and Pixel 9A. These are the devices still supported by Google, so it’s not a surprise.

The update is available immediately in the factory image and OTA file formats and should arrive live at any time (update: it’s live) for those of the Android Beta program. The live update weighs 65 MB on my pixel 9 pro.

Android 16 QPR1 3.1 Update bug corrections: As for the fixes, the full list has been included below and it is important. Google took care of several bugs that have caused unexpected restarts of the devices, Bluetooth accidents, several user interface problems of the status bar with quick -line parameters on the home screen, and much more. I strongly recommend that you read the list if you had problems on the previous beta QPR1 version.

Instability or restarting of the Wi-Fi device by improving how the system deals with network statistics. (Number n ° 433037402, number 432867183, number 433418936, number 432795362, number 432770117, number 432699126, number 435489862, number 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 ° 42099948, 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 n ° 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 422749237, number 420418750, number 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 421879049, number 421810067, number 423172198, number 422560004, number 424116279)
A problem that has restarted unexpected devices. (Number n ° 408888279, number 409949346, number 409960197, number 410624610, number 407373090, number 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 ° 4195733315, number 419134909, number 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 420725698)
The multimedia player on the lock screen sometimes disappeared or did not respond. (Number n ° 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 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 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.