
Google Releases Android 15 QPR2 Beta 2 With Critical Bug Fixes | Image Source: www.androidpolice.com
Mountain View, California, December 21, 2024 – Google released Android 15 QPR2 Beta 2, marking a critical step to solve several system and hardware issues before the next important Pixel Feature Drop, scheduled for March 2025. The update comes as a rather surprising move during the holiday season, but it highlights Google’s commitment to fine-tuning the Android 15 experience before the focal transition to the expected Android 16.
According to Android Police, the Android 15 QPR2 Beta 2 has the construction number BP11.241121.010 and is available for all eligible Pixel devices ranging from the Pixel 6 series to the latest models. Although the update is not full of functions, it provides a series of highly needed bug fixes that point to system performance, Bluetooth reliability and development tools. Google said the update focuses on the delivery of the “next round of refinements” after the release of QPR2 Beta 1.
Corrections to key errors and improvements
Android 15 QPR2 Beta 2 update introduces solutions to several persistent failures, many of which have frustrated developers and end users. Google highlighted the following issues that were addressed:
A remarkable solution solves a problem where the COMO preference option in Developer Options could not be viewed, a major concern for the performance of test graphics and debugging problems. This fixation was classified in edition 379196574.
In addition, Google addressed a problem that prevented certain glucose sensor devices from being properly connected, classified as number 378816128. This failure had caused discomfort to users who depended on external health surveillance devices, particularly diabetics who depended on continuous glucose reading.
Another important improvement is delays during calls. Users reported significant delays in selecting call options, which were identified in numbers 379266329 and 378854091. The solutions guarantee smoother call management experiences on all devices.
Bluetooth improvements and security corrections
Several corrections in this update center around Bluetooth functionality, in particular involving Low Energy (LE) Audio. LE Audio is an essential feature for users who need energy efficient connections with compatible Bluetooth devices. Google solved an error causing inconsistent behavior by changing between ASHA (Audio Streaming for Hearing Aids) and LE Audio, ensuring that audio playback stops perfectly during transitions.
In addition, the update resolves the L2CAP connection problems that occurred after restarting. This was caused by incorrect safety-level savings during Bluetooth coupling, leading to failing security controls in restarting. The Google solution now ensures a reliable connection without leaks or data failures. In addition, a failure that allowed LE links to remain unencrypted in reconnection with connected devices, potentially exposing user data sensitive to attackers, has been corrected, greatly improving Bluetooth security.
Google also addressed failures caused by Bluetooth Hardware Abstraction Layer (HAL) when downloading LE Audio hardware was disabled. Previously experienced Bluetooth intermittent failure users, and this update ensures a stable Bluetooth experience for all compatible devices.
Improvements in load optimization
One of the most exciting solutions concerns the new charging option “Limit to 80%” introduced in the December Drop. Before this update, the setting cannot be changed, frustrating users seeking to optimize the health of the battery. The option now works as expected, providing a significant benefit to heavy users who maintain their energy-related phones for long periods of time. Once activated, the function also activates passive charging, reducing battery wear and ensuring a long battery life for Pixel devices.
According to Android Police, this improvement is particularly remarkable for users who trust their devices for long work sessions or games. The passing charge avoids the battery, providing energy directly to the device, thus reducing heat generation and battery degradation.
Pixel Specific Fixes
Google also addressed a critical issue that affects Pixel Fold. Users indicated that devices would sometimes stop responding when they were developed, which would create significant user problems. This number, followed by number 379387626, was resolved in the latest beta version, ensuring stable performance for Pixel Fold users.
As folding devices gain popularity, implementing such usage errors remains a top priority for Google to maintain user satisfaction and confidence in their hardware alignment. Resolution ensures smoother performance, especially during multitasking and media consumption on deployed screens.
How to access the update
For Pixel users wishing to try the last beta, Google did the process directly. Depending on the update announcement, users can save their devices in the Beta Android program and browse in Settings → System → Software updates → System Update → Consult for the update. The update is now live, with download sizes ranging from 300MB to 500MB, depending on the device model.
For advanced users who prefer manual installation, Google also provides factory images and OTA files, which can be flashed or loaded with ADB. This method provides more control over the installation process, although it requires technical experience and caution to avoid the device brick.
Google’s quick release of QPR2 Beta 2 reflects the company’s condensed update schedule. With Android 16 on the horizon and expected to enter public beta by January 2025, the stable release of Android 15 QPR2 is probably imminent. According to the Android font, there are minimal indications of new updates in 2024, making this version a likely conclusion for the year.
The Google approach now changes to refine Android 16, but users can still anticipate the Mars Pixel Feature Drop, which will probably bring additional improvements and features. For now, the Android 15 QPR2 Beta 2 provides a smoother and safer experience for Pixel users, tackling persistent errors while improving basic features.