Unexpected restarts and failed connections are among the problems Google is tackling in its latest Pixel beta.
Google released Android 17 QPR3 Beta 2 on Oct. 20, listing 21 fixes covering stability, calling, Bluetooth, apps, and battery drain. The update gives Pixel testers a new build to evaluate, but it remains prerelease software.
For people using a Pixel for work, the immediate question is whether to update an existing beta device or keep a primary work phone on stable Android.
What Google says Beta 2 fixes
Google’s official release notes identify build DP11.261002.005 with the Oct. 5 security patch level.
Google says the update fixes intermittent crashes and restarts, shutdowns during WhatsApp video calls, and an unresponsive black screen after calls end. It also addresses Bluetooth pairing timeouts and excess idle battery use linked to motion sensors remaining active after Face Unlock or camera use.
Several connectivity fixes are carrier-specific: cellular data, MMS, and hotspot connections on Dish Network; VoLTE, VoNR, and Wi-Fi calling on IT&E; and Wi-Fi calling on OXIO.
Other changes address screen recording after rotation, Airbnb messaging connections, and the Terminal app’s Linux virtual machine. These are Google’s reported fixes, rather than independently verified results across all affected devices.
QPR stands for Quarterly Platform Release. These updates build on Android between major releases, a distinction covered in this Android guide to versions and updates.
Which Pixel devices can receive it?
Google’s QPR3 installation guide lists the Pixel 6a, Pixel 7 through Pixel 11 families, the original Pixel Fold, and Pixel Tablet. The Pixel 6 and Pixel 6 Pro are absent from that list.
Eligible users can enroll through Android Beta for Pixel to receive over-the-air updates. Google recommends backing up data before enrolling, even though joining usually does not require a full reset.
This release’s Pixel eligibility should not be read as a rollout schedule for other Android manufacturers. As with the initial Android 17 rollout, Samsung and other brands have their own release paths.
What to know before joining or leaving the beta
Google’s beta program guidance warns that prerelease builds can contain defects that affect normal device operation.
Returning to stable Android generally requires wiping locally stored data. There is a limited exception: after installing the stable release corresponding to the version they are testing, users can opt out without wiping their data during a limited window, provided they have not installed the next beta update.
That makes enrollment a bigger commitment than installing a routine patch. Pixel owners seeking regular fixes should also distinguish this preview from the October Pixel security and stability update.
What's hot at TechRepublic
- Blackpoint Cyber vs. Arctic Wolf: Which MDR Solution is Right for You?
- Why AWS Sellers Choose Deepgram Over Other Voice AI Tools
- SS&C Intralinks DealCentre AI vs. Datasite: Which platform is built for the future of dealmaking?
- SS&C Intralinks FundCentre AI vs. Juniper Square: Which platform better supports modern private markets fund managers?
- Verito vs. Rightworks: Which IT Provider Is Best for Your Firm?
Test the workday before trusting the fix
For existing beta testers, this release offers specific problems to retest. Start with the failure you previously encountered, then check the surrounding workflow: place and receive calls, switch between Wi-Fi and mobile data, reconnect Bluetooth accessories, and use the hotspot if your job depends on it.
For IT teams, the recommendation is to keep that evaluation on spare or designated test devices. Check work-profile access, VPN connections, authentication prompts, and essential business apps under the conditions employees actually use them. A successful installation alone does not show that a phone is ready for a full working day.
Record the device model, carrier, build number, and steps behind any recurring problem. Carrier-specific fixes make that context particularly useful when comparing results or reporting a defect.
For readers on stable Android, a familiar symptom in the changelog is not enough reason to enroll a primary work phone. First confirm whether the problem occurs on your current build and whether a stable update addresses it. Before joining, make sure you can restore your data and access essential accounts if returning to stable requires a reset.
The practical test is whether the update restores the workflows you rely on without creating another obstacle. Use those results, rather than the length of the fix list, to decide what happens next.
Read more: Beyond reliability fixes, Google’s quarterly Android updates also introduce security changes, including call-forwarding scam protections.