Google patches Pixel crashes and connectivity faults in Android 17 Beta 2
The latest preview build for Google Pixel phones resolves twenty-one issues, including random reboots, black screens and failed network connections on specific carriers.
Key points
- Android 17 QPR3 Beta 2 addresses twenty-one distinct bugs affecting Pixel devices.
- Fixes target critical stability issues such as unexpected shutdowns and display failures.
- Network connectivity problems on Dish Network and IT&E carriers are resolved in this build.
Google has released the second beta version of Android 17 QPR3 for Pixel devices, addressing a wide range of stability and connectivity defects. This update is part of the preview programme leading up to the scheduled March 2027 stable release. The build focuses on resolving issues that cause devices to crash, reboot or become unresponsive during everyday use, according to reports from 9to5Google.
The update resolves twenty-one specific issues identified during testing. Major fixes include corrections for devices that intermittently crash or reboot without user action. It also addresses a problem where the screen turns black and becomes unresponsive after ending a phone call. Additionally, the build fixes an issue causing unexpected shutdowns during WhatsApp video calls, as detailed by 9to5Google.
What we know
Connectivity and user interface bugs form a large portion of the fixes. The update resolves failures in cellular data, MMS and hotspot services on Dish Network. It also restores VoLTE, VoNR and Wi-Fi calling availability on the IT&E network. Wi-Fi Aware errors that prevented data path establishment are also corrected.
Visual and interaction glitches are addressed across multiple system areas. The lock screen no longer causes stuttering animations when in-progress notifications overlap with other elements. System UI, fonts and apps are corrected to render at the proper scale, fixing a bug that made them appear abnormally small. The media output dialog now respects the monochrome system theme when external audio devices are connected.
Peripheral and app-specific issues are also resolved. Bluetooth pairing timeouts are fixed, and paired watches no longer continue ringing after a call is answered on the phone. The Terminal app can now launch the Linux development environment virtual machine correctly. Airbnb messaging connectivity issues and screen recording freezes after rotation are also addressed in this build.
Defender's checklist
- Verify that the device receives the Beta 2 update via the system settings menu.
- Check carrier-specific network settings to ensure VoLTE and Wi-Fi calling are enabled.
- Monitor battery usage statistics to confirm that idle drain from motion sensors has ceased.
- Test external audio devices to ensure the media output dialog displays correctly.
The background in plain language
Beta releases are pre-release software versions intended for testing before a final public launch. They allow manufacturers to identify and fix bugs in real-world usage scenarios. Users who install these builds help developers spot issues that automated testing might miss. However, beta software is not considered stable and may contain unresolved defects. Organisations typically avoid deploying beta software to production devices due to the risk of instability. Instead, they wait for the stable release, which has undergone rigorous quality assurance. This process ensures that critical functions like connectivity and security are reliable before widespread adoption.
Background: Virtual machines
Virtual machines emulate full hardware and run separate operating systems, providing strong isolation. Containers share the host kernel and package only application code, offering faster startup. Choose virtual machines for strict security or mixed operating systems. Choose containers for rapid deployment and resource efficiency in consistent environments.
What to do and how to stay safe: Google
- Backup important data before installing any beta software update to prevent potential loss.
- Monitor device performance closely after updating to identify any new or persisting issues.
- Report any encountered bugs through the official feedback channels provided by the vendor.
- Wait for the stable release before deploying updates to critical business devices.
General security guidance from the TechWire Beat newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
Which devices are affected by these fixes?
The fixes apply to Google Pixel devices running the Android 17 QPR3 Beta 2 preview build.
When is the stable version of Android 17 QPR3 expected?
The stable release is scheduled for March 2027, according to the preview timeline.
Does this update fix security vulnerabilities?
The source material lists bug fixes for stability and connectivity but does not mention specific security vulnerability patches.
