![\"Android](\"https:\/\/www.newsbeep.com\/ca\/wp-content\/uploads\/2025\/08\/Android_16_Easter_egg_hero_image_2.jpg\"\/ "\\"Android")
<\/p>\n<\/p>\n
Mishaal Rahman \/ Android Authority<\/p>\n
TL;DR<\/p>\n
Android 16 QPR1 Beta 3 arrived on July 17, and Google\u2019s now following that up with a Beta 3.1 release.
\nThe full changelog mentions a ton of fixes.
\nIf all goes to plan, Android 16 QPR1 should be ready to hit stable right on schedule, on September 3.<\/p>\n
When it comes to Google hardware, August has arrived to usher in the latest lineup, and at this point we\u2019re under a week away from the big Pixel 10 Made by Google<\/a> event. But for as exciting as that is, we\u2019re already looking forward to September, when it\u2019s Google\u2019s latest software that will be grabbing all our attention. That\u2019s when we\u2019re expecting Android 16 QPR1 to hit stable<\/a> and have its rollout. But ahead of that day arriving, we\u2019ve got what may be the final QPR1 beta to try out.<\/p>\n Don\u2019t want to miss the best from Android Authority?<\/p>\n It\u2019s been almost a month now since Android 16 QPR1 Beta 3<\/a> arrived, and while we spotted a handful of changes that were incoming, like the magnified keyboard that first debuted on Android Canary<\/a>, there weren\u2019t a ton of user-facing tweaks that were new \u2014 just like we\u2019d expect from a beta at this late stage, to be fair.<\/p>\n This afternoon, Google released Android 16 QPR1 Beta 3.1, a bug-fixing update on top of QPR1 Beta 3. The new build is labeled as BP31.250610.009 (.009.A1 for the Pixel Tablet), and just like previous releases, we\u2019re seeing it for Pixel 6 and later models.<\/p>\n According to the QPR1 release notes page, Beta 3.1 includes fixes for the following issues:<\/p>\n Device instability or reboots related to Wi-Fi by improving how the system processes network statistics. (Issue #433037402<\/a>,\u00a0Issue #432867183<\/a>,\u00a0Issue #433418936<\/a>,\u00a0Issue #432795362<\/a>,\u00a0Issue #432770117<\/a>,\u00a0Issue #432699126<\/a>,\u00a0Issue #435489862<\/a>,\u00a0Issue #435011484<\/a>)
\nThe Context Hub, a low-power sensor component, would crash due to excessive use of main memory, causing device instability; resolved by optimizing memory allocation and preventing memory leaks. (\u00a0Issue #420999948<\/a>,\u00a0Issue #426316038<\/a>)
\nThe home screen sometimes lost its bottom row of pinned apps and the search bar, making them inaccessible; this was fixed by adjusting how these elements reappear after screen transitions. (Issue #428088033<\/a>,\u00a0Issue #428405658<\/a>,\u00a0Issue #429817851<\/a>)
\nNotifications would overlap in the shade, hindering readability, by refining the notification display and dismissal animation logic. (Issue #421792538<\/a>,\u00a0Issue #422749237<\/a>,\u00a0Issue #420418750<\/a>,\u00a0Issue #428896474<\/a>)
\nAn issue that caused unexpected device restarts. (Issue #427676713<\/a>)
\nThe Quick Settings UI on unfolded foldable devices appeared clipped or misaligned due to incorrect padding caused by double-counting the camera cutout. (Issue #419184923<\/a>,\u00a0Issue #421879049<\/a>,\u00a0Issue #421810067<\/a>,\u00a0Issue #423172198<\/a>,\u00a0Issue #422560004<\/a>,\u00a0Issue #424116279<\/a>)
\nAn issue that caused devices to unexpectedly reboot. (Issue #408888279<\/a>,\u00a0Issue #409949346<\/a>,\u00a0Issue #409960197<\/a>,\u00a0Issue #410624610<\/a>,\u00a0Issue #407373090<\/a>,\u00a0Issue #430095518<\/a>)
\nThe status bar appearing in the Quick Settings shade was sometimes misaligned with the standard status bar, causing a visual inconsistency. (Issue #419573315<\/a>,\u00a0Issue #419134909<\/a>,\u00a0Issue #432794874<\/a>)
\nAddressed a system hang or crash, particularly during unlock, caused by the camera\u2019s Ambient Light Sensor (ALS) read getting stuck, by implementing a non-blocking method for sensor data retrieval. (Issue #421870862<\/a>,\u00a0Issue #420725698<\/a>)
\nThe media player on the lock screen would sometimes disappear or become unresponsive. (Issue #420517884<\/a>)
\nAn issue where the notification shade displayed a large, growing gap, obscuring notifications, by correcting how notification animations were clipped. (Issue #421366916<\/a>)
\nAn issue where the media player notification could appear clipped or disappear during device rotation, by improving how its display area is sized and updated in UI transitions. (Issue #433040374<\/a>)
\nVideo calls initiated from voice calls no longer experience muted audio; a system audio fix now correctly manages sound output during call type transitions. (Issue #434139133<\/a>,\u00a0Issue #427060263<\/a>,\u00a0Issue #438414975<\/a>)
\nAn issue where black translucent bars appeared at the top and bottom of the home screen after exiting full-screen apps by correcting how transient system bar states were cleared. (Issue #425407737<\/a>,\u00a0Issue #433929827<\/a>)
\nAn issue that caused the device to unexpectedly crash and restart during an OTA update.
\nAn issue causing occasional device restarts after system updates.
\nWidgets on the home screen sometimes failed to load due to looking for outdated app files.
\nTyping occasionally stopped working in apps because internal input system processes could race.
\nDevice crashes caused by the Context Hub running out of memory.
\nBluetooth crashes and instability caused by an \u201cUnimplemented Packet Type\u201d error have been resolved.
\n[RG5][BD1A.250219.006]Unable to handle kernel paging request, PC is at edgetpu_kci_release_vmbox, LR is at edgetpu_kci_release_vmbox
\nAn issue that could cause phone disconnections or system crashes during calls by resolving a memory corruption bug in audio data buffer handling related to audio playback speed changes.
\nA brief screen flicker happened when launching apps from the notification shade.
\nA system crash that could occur when using your device\u2019s media features, especially when connected to a computer for media transfer, by improving the internal handling of media connection resources.<\/p>\n