Affiliate links on Android Authority may earn us a commission. Learn more.
Google rounds the week out with Android 17 QPR 3 Beta 1
Oct 2, 2026 — 4:51 PM ET
- Android 17 QPR3 Beta 1 is now available for Pixel testers.
- Builds cover the Pixel 6a up through the Pixel 11 family.
- Google is fixing quite a few bugs with this first preview release.
With October now upon us, 2027 feels like it’s really starting to loom over us. We’re already looking out to next year for most of the big hardware launches on the horizon, and now software’s starting to catch up. Earlier this week, Google delivered its latest preview of the company’s big year-end Android update, with Android 17 QPR2 Beta 6.1. And with just hours left before the weekend, we’re getting our first taste of Android’s next major update beyond that.
Google just announced Android 17 QPR 3 Beta 1 for Pixel devices. Firmware is available for the Pixel 6a on up through the Pixel 11 series. Most devices will get build DP11.260918.006, while DP11.260918.005 is reserved for Pixel 11 family members.
So far, all we know to expect is the big list of bugfixes Google is sharing:
- Audio output device cannot be switched while playing audio from apps without active media controls. (Issue #259180936)
- Apps crash when attempting to start a foreground service from a Quick Settings tile. (Issue #299506164)
- Application icons in the app menu display with excessive spacing. (Issue #316288379, Issue #300758716)
- App previews fail to display in the recent apps screen. (Issue #515091621)
- NFC service crashes with DeadObjectException and stops detecting tags after the initial scan on Android 16. (Issue #456078994)
- Device freezes and becomes unresponsive when unlocking with the fingerprint sensor. (Issue #490719716, Issue #514867650, Issue #523022829)
- Device crashes when selecting the require eyes to be open option in Face Unlock settings. (Issue #466618368, Issue #522677686)
- MediaPlayer crashes when handling non-ASCII audio attribute tags. (Issue #552043106)
- Applications freeze and trigger an Application Not Responding (ANR) error when launched. (Issue #484969809, Issue #475406236)
- Camera feed is rotated 90 degrees when using video calling apps on an external display in desktop mode. (Issue #432390710)
- User interface issues when navigating back to the home screen from an app. (Issue #566639975)
- Unexpected dot displayed on the Mobile Data icon in Quick Settings. (Issue #551150806)
- Front camera fails to function while screen recording is active. (Issue #523313834)
- Calling apps crash with ForegroundServiceStartNotAllowedException when handling calls immediately after device reboot. (Issue #409069722)
- eSIM profile cannot be enabled and silently reverts to off in Settings. (Issue #541436675)
- Excessive battery drain during idle when Flip to Shh is enabled. (Issue #560036427)
- Settings app crashes when opening battery settings. (Issue #554603197)
- Audio playback stops on active LHDC v5 Bluetooth devices when a second connected device disconnects. (Issue #554992287)
- com.android.phone crash loop and complete loss of cellular service when the modem reports unexpected SIM slot indices. (Issue #554049220)
- Wi-Fi fails to automatically reconnect during background wakes when hardware PNO scans fail or are unsupported. (Issue #551970385)
If this sounds like a grand time to get started playing around with Android Betas, you can register your Pixel handset with Google’s Android Beta for Pixel program. As always, securely back up your data before getting involved with an effort like that.
On the flip side, if you’re looking to leave the testing track and go back to stable Android, this is also your chance — just unenroll your device from the program and do not install today’s QPR3 Beta. Then when QPR2 goes stable as a future drop, you should be able to install without needing to bother with a data wipe.
We’ll start loading this up on our own handsets, and let you know about any interesting QPR3 changes we manage to spot. On first pass, we’re already seeing a few.
For one, here are some text strings that appear to reveal work towards letting connected gamepads control Android’s cursor like a mouse:
<string name="gamepad_mouse_title">Gamepad mouse</string>
<string name="gamepad_mouse_summary">Use a connected gamepad to control the cursor</string>
<string name="gamepad_mouse_main_title">Use Gamepad mouse</string>
<string name="gamepad_mouse_footer_description">Gamepad mouse lets you control the cursor and perform actions using a connected gamepad or joystick.</string>We’re also spotting a whole lot of new strings connected to phone unlock support. If we were the gambling type, we might bet on this being related to Googlebook connectivity:
<string name="cdt_unlock_title">Phone</string>
<string name="cdt_unlock_intro_text">Use your phone to unlock this device.</string>
<string name="cdt_unlock_screen_title">Phone unlock</string>
<string name="cdt_unlock_summary">Manage Phone Unlock settings</string>
<string name="cdt_unlock_no_phones_found">No phones found.</string>
<string name="cdt_unlock_screen_purpose">Allows users to manage the settings of Phone Unlock. This includes enrolling and unenrolling a phone to unlock this device.</string>Why Googlebook? Well, these illustrations we spotted are certainly evocative:
And if we keep looking, there are just more and more strings seemingly related to this forthcoming support:
<string name="phone_unlock_all_set_description">You can now use your phone to unlock this device when you open your lid, move your mouse, or press a keyboard key on the lock screen.</string>
<string name="phone_unlock_all_set_title"><b>You’re all set!</b></string>
<string name="phone_unlock_association_list_purpose">The list of associated companion devices for phone unlock, formatted as associationId:displayName.</string>
<string name="phone_unlock_explanation_button_continue">Continue</string>
<string name="phone_unlock_explanation_button_more">More</string>
<string name="phone_unlock_explanation_button_not_now">Not now</string>
<string name="phone_unlock_explanation_how_it_works_item1">Your phone can unlock this device when it’s within reach and unlocked.</string>
<string name="phone_unlock_explanation_how_it_works_item2">When this device is unlocked, you’ll get notified on your phone. If it was unlocked when you didn’t intend to, tap the notification to lock the device again.</string>
<string name="phone_unlock_explanation_how_it_works_title">How it works</string>
<string name="phone_unlock_explanation_keep_in_mind_item">Using your phone to unlock this device may be less secure than a strong pattern, PIN, or password. In some cases, your phone may unlock this phone even if it’s out of reach.</string>
<string name="phone_unlock_explanation_keep_in_mind_title">Keep in mind</string>
<string name="phone_unlock_explanation_message">Phone Unlock is another convenient way to unlock this device when your phone is within reach</string>
<string name="phone_unlock_explanation_title"><b>Set up Phone Unlock</b></string>
<string name="phone_unlock_explanation_youre_in_control_item">You can remove your phone from Phone Unlock at any time in Settings</string>
<string name="phone_unlock_explanation_youre_in_control_title">You’re in control</string>
<string name="phone_unlock_screen_hardware_unsupported">Phone Unlock is not supported on this device.</string>
<string name="phone_unlock_screen_preconditions">The device must support the Phone Unlock feature.</string>
<string name="phone_unlock_settings_available_phones">Available phones</string>
<string name="phone_unlock_settings_button_confirm">Confirm</string>
<string name="phone_unlock_settings_title"><b>Choose your phone</b></string>We’ll keep at it, and share anything else we spot!
Thank you for being part of our community. Read our Comment Policy before posting.