Google has started testing the next major quarterly release for its Pixel phones. Android 17 QPR3 Beta 1 arrived on October 2, 2026, bringing a relatively small package of bug fixes, interface changes, and a couple of unreleased features that hint at what Google may be developing for future Pixel devices.
This isn’t a feature-packed Android update. Instead, Google is using the first QPR3 beta to address several annoying problems affecting Pixel users, including fingerprint unlock freezes, eSIM profiles unexpectedly disabling themselves, cellular connectivity crashes, Bluetooth audio problems, and battery drain.
There are also a few visual changes, including a new Notes Quick Settings tile for the Pixel 11 lineup and updated status bar icons. Meanwhile, code discovered inside the beta points to potential features for using a game controller as a mouse and unlocking another device with a nearby phone.
Here’s everything you need to know about Android 17 QPR3 Beta 1, including the supported Pixel phones, all 20 documented fixes, the new features, and whether you should install the beta.

Android 17 QPR3 Beta 1: Quick Overview
Android 17 QPR3 is still a long way from its final release, so Beta 1 should be viewed as an early testing build rather than a finished update.
According to Google’s official release notes, Android 17 QPR3 Beta 1 was released on October 2, 2026.
Here are the key details:
- Release date: October 2, 2026
- Build number: DP11.260918.005 for Pixel 11 devices
- Build number: DP11.260918.006 for other supported Pixel phones
- Android API level: 37
- Security patch: August 5, 2026
- Google Play services: 26.32.34
- Beta size: Around 597MB when updating from QPR2 Beta on a Pixel 11 Pro
- Expected stable release: March 2027
Google hasn’t officially confirmed the March 2027 date, so treat that timeframe as an expectation rather than a guaranteed release date.
One important detail is that QPR releases aren’t designed to introduce API changes that affect application compatibility. Android 17 therefore remains at API level 37, meaning developers don’t need to make major app changes specifically for QPR3.
Which Pixel Phones Are Compatible With Android 17 QPR3 Beta 1?
Google is making Android 17 QPR3 Beta 1 available across a wide range of Pixel hardware.
The supported devices include:
Pixel 6a and Pixel 7 Series
- Pixel 6a
- Pixel 7
- Pixel 7 Pro
- Pixel 7a
Pixel Fold and Pixel Tablet
- Pixel Fold
- Pixel Tablet
Pixel 8 Series
- Pixel 8
- Pixel 8 Pro
- Pixel 8a
Pixel 9 Series
- Pixel 9
- Pixel 9 Pro
- Pixel 9 Pro XL
- Pixel 9 Pro Fold
- Pixel 9a
Pixel 10 Series
- Pixel 10
- Pixel 10 Pro
- Pixel 10 Pro XL
- Pixel 10 Pro Fold
- Pixel 10a
Pixel 11 Series
- Pixel 11
- Pixel 11 Pro
- Pixel 11 Pro XL
- Pixel 11 Pro Fold
What About the Pixel 6 and Pixel 6 Pro?
The Pixel 6 and Pixel 6 Pro aren’t eligible for Android 17 QPR3 Beta 1.
That’s expected rather than an error with Google’s beta program. Both phones reached the end of their major Android update support in October 2026, making Android 17 QPR1 their final major operating system update.
The Pixel 6a is different because it launched later and has a longer support period.
If you’re still using a Pixel 6 or Pixel 6 Pro, you shouldn’t expect QPR3 to arrive on your device.
Android 17 QPR3 Beta 1 Fixes 20 Pixel Problems
The most important part of QPR3 Beta 1 isn’t the new interface. It’s the large collection of bug fixes included in the build.
Google has documented 20 fixes in its release notes. Several address problems that could affect essential phone functions such as unlocking, mobile connectivity, Wi-Fi, NFC, and Bluetooth.
Here’s a closer look at the most important changes.
Fingerprint Unlock Could Freeze the Phone
One of the more significant fixes addresses a problem where a Pixel could become unresponsive after attempting to unlock it with the fingerprint sensor.
Google references multiple reports related to this problem, suggesting it wasn’t an isolated occurrence.
For anyone who relies on fingerprint authentication throughout the day, this should be a welcome fix.
Face Unlock Could Crash When Eye Detection Was Enabled
Another biometric issue affected Face Unlock.
Enabling the option that requires your eyes to be open could cause the device to crash under certain circumstances.
Android 17 QPR3 Beta 1 addresses the problem.
eSIM Profiles Could Turn Themselves Off
QPR3 also fixes an especially frustrating eSIM problem.
Some users could enable an eSIM profile only for Android to disable it again without providing an obvious error message.
That’s more than a minor inconvenience because an unexpectedly disabled eSIM can leave you without cellular connectivity.
Cellular Service Could Disappear After a Modem Problem
Google has also addressed a crash involving the Android phone process.
Under certain conditions, unexpected SIM slot information reported by the modem could cause com.android.phone to repeatedly crash. That could ultimately result in the loss of cellular service.
This is one of the fixes that matters most for people using their Pixel as their primary phone.
Pixel Wi-Fi Could Fail to Reconnect While the Screen Was Off
Android uses a low-power Wi-Fi scanning mechanism called Preferred Network Offload (PNO) to look for known networks while the display is turned off.
A problem with these background scans could prevent a Pixel from reconnecting to Wi-Fi correctly.
The result could be surprisingly easy to miss: you arrive home, unlock your phone, and discover that it has remained on cellular data instead of reconnecting to your home Wi-Fi.
QPR3 Beta 1 addresses this behavior.
NFC Could Stop Working After the First Scan
Another fix targets the NFC service.
A DeadObjectException could cause NFC to stop responding after the first tag interaction. Once the service crashed, subsequent NFC scans wouldn’t work properly.
Interestingly, Google identifies this as an Android 16 issue, showing that some bugs can persist across major Android releases before finally being fixed.
Bluetooth Audio Gets Several Fixes
Android 17 QPR3 Beta 1 also contains multiple Bluetooth and audio fixes.
Audio Output Could Get Stuck
Users could encounter situations where Android wouldn’t allow them to switch audio output while an application without built-in media controls was playing sound.
LHDC v5 Audio Could Stop
A Bluetooth audio device using LHDC v5 could stop playing audio when another connected Bluetooth device disconnected.
MediaPlayer Could Crash on Certain Song Metadata
MediaPlayer could also crash when processing audio files containing non-ASCII metadata.
That includes music with titles, artist names, or other information written using scripts such as Japanese, Arabic, Hindi, and other non-Latin alphabets.
Android 17 QPR3 Addresses Battery Drain
Google has included two battery-related fixes.
The first concerns Flip to Shh, Pixel’s feature that automatically activates Do Not Disturb when you place the phone face down.
With the feature enabled, some devices could consume more battery than expected while sitting idle.
The second fix addresses a crash that could occur when opening the Battery section inside Android Settings.
More Android 17 QPR3 Beta 1 Fixes
The remaining fixes cover a variety of camera, display, system UI, and application problems.
Google has addressed issues where:
- The front-facing camera could stop working while screen recording was active.
- Video calls displayed through an external monitor in desktop mode could appear rotated by 90 degrees.
- App icons in the application menu could have excessive spacing.
- The Recents screen could fail to display application previews.
- A small unwanted dot could appear on the Mobile Data icon in Quick Settings.
- Returning to the home screen from an application could cause visual interface glitches.
- Applications could freeze during startup with an ANR, or “Application Not Responding,” error.
- Applications could crash when launching a foreground service from a Quick Settings tile.
- Calling applications could crash when handling a call immediately after the phone rebooted.
Overall, the fixes are much more practical than the visible changes in this beta.
Android 17 QPR3 Beta 1 Also Includes Small Pixel UI Changes

Don’t expect a dramatic redesign with QPR3 Beta 1. Google is keeping the visual changes relatively subtle.
Pixel 11 Gets a New Notes Quick Settings Tile
Pixel 11 devices receive a new Notes tile in Quick Settings.
It provides a shortcut for opening the Notes application without first navigating through the app drawer.
For now, Google appears to be limiting the feature to the Pixel 11 family.
Android’s Status Bar Icons Have Been Tweaked
Google has also made several small changes to status bar icons.
The VPN indicator is more prominent, while the Bluetooth and Airplane Mode icons have been enlarged.
The silent-mode icon has also been adjusted so that its appearance better matches the design used by the Android volume panel.
These aren’t major changes, but they’re the kind of small interface refinements that tend to accumulate throughout quarterly Pixel updates.
Pixel 10 Gets the Gemini Intelligence Boot Animation
One of the more interesting changes affects the Pixel 10 lineup.
Google is bringing the Gemini Intelligence boot animation to Pixel 10 devices. The animation was previously associated with the newer Pixel 11 generation.
This doesn’t necessarily mean every Pixel 11 AI feature is coming to Pixel 10.
Google’s AI features can depend on the hardware available in each generation, so a new boot animation shouldn’t be interpreted as confirmation that every Gemini Intelligence capability will become available on older Pixels.
Proactive Assistance Moves in Settings
Android 17 QPR3 Beta 1 also changes the placement of Proactive Assistance inside system Settings.
It now appears above Magic Cue.
The change is relatively small, but it suggests Google is continuing to integrate its AI-powered assistance features more deeply into the Pixel software experience.
Two Hidden Android 17 QPR3 Features Could Be More Interesting
The most intriguing discoveries aren’t actually enabled in Beta 1.
Android researchers have found code references pointing toward two features that Google appears to be experimenting with.
Neither is currently functional, so don’t install the beta expecting to use them.
Gamepad Mouse Support
One hidden feature could allow a connected game controller to act as a mouse.
Instead of simply controlling games, a compatible controller could potentially be used to move a pointer around the Android interface.
That could become particularly useful as Google continues expanding Android’s desktop-style capabilities.
However, the feature is still unfinished and could change significantly before QPR3 reaches stable release.
Phone Unlock Could Connect Android Devices
Another discovery is a feature referred to internally as Phone Unlock.
The concept is relatively straightforward: an unlocked phone located nearby could potentially be used to unlock another compatible device.
The idea resembles Apple’s ecosystem-based device unlocking, where a trusted nearby device can help authenticate another device.
Google’s code reportedly warns that this method could be less secure than using a PIN or password.
Again, this feature isn’t active in QPR3 Beta 1. Google could modify it, delay it, or remove it completely before the final release.
Should You Install Android 17 QPR3 Beta 1?
For most Pixel owners, I wouldn’t recommend installing Android 17 QPR3 Beta 1 yet.
The fixes are useful, but there is an important trade-off.
The Security Patch Is Older Than the Stable Release
QPR3 Beta 1 ships with the August 5, 2026 security patch.
That’s a problem because stable Pixel devices have already moved to the September 2026 security update.
The September release included security fixes for vulnerabilities including CVE-2026-58704, a modem-related vulnerability that Google indicated could be subject to limited, targeted exploitation.
In other words, installing this beta can actually put your phone on an older security patch than the stable software currently available.
For a daily driver, that’s difficult to justify unless you specifically need one of QPR3’s fixes.
Leaving the Android 17 QPR3 Beta Can Wipe Your Phone
There’s another important consideration: reverting to stable Android.
If you install QPR3 Beta 1 and later decide you want to return to the stable Android release, the downgrade process normally requires a factory reset.
That means your locally stored data can be erased.
Before installing any Pixel beta, make sure your photos, messages, files, authentication data, and other important information are backed up.
Who Should Install QPR3 Beta 1?
The beta makes the most sense for:
- Android developers testing applications.
- Pixel enthusiasts who enjoy testing early software.
- People with a secondary Pixel device.
- Users experiencing one of the specific bugs fixed by QPR3.
- Anyone comfortable troubleshooting beta software and potentially resetting their phone.
For everyone else, waiting for the stable release is the safer choice.
How to Install Android 17 QPR3 Beta 1
If you decide to test the beta, enrolling through Google’s Android Beta program is the simplest option.
Step 1: Back Up Your Pixel
Before installing any beta software, create a complete backup of important data.
Step 2: Join the Android Beta Program
Visit Google’s Android Beta for Pixel website and enroll your compatible Pixel.
Step 3: Check for the Update
On your Pixel, open:
Settings β System β Software updates β System update
Then check for available updates.
The QPR3 beta should appear if your device is eligible and properly enrolled.
Developers and experienced Android users can also install the software using an OTA package or flash a factory image with Google’s Android Flash Tool.
How to Leave the Android 17 Beta Program
If you decide the beta isn’t for you, you can return to Google’s beta program page and select Opt out for your Pixel.
However, there’s an important catch.
The downgrade update can erase your phone.
If you want to avoid a factory reset, the safer strategy is to remain enrolled until the stable version of QPR3 becomes available. Once your phone receives the stable QPR3 release, you can install it and then leave the beta program without downgrading.
Android 17 QPR3 Beta 1: Should You Wait?
Android 17 QPR3 Beta 1 is best described as a maintenance-focused Pixel update rather than a major feature release.
The new Notes Quick Settings tile, status bar changes, and Gemini Intelligence boot animation are nice additions, but they’re not reasons by themselves to install unfinished software.
The more meaningful improvements are hidden in the bug fixes.
Google is addressing problems involving fingerprint authentication, Face Unlock, eSIM profiles, cellular connectivity, Wi-Fi reconnection, NFC, Bluetooth audio, battery drain, cameras, and application crashes. For users affected by one of those bugs, QPR3 Beta 1 could be a significant improvement.
For everyone else, however, waiting is the smarter move.
The beta currently carries an older security patch than stable Pixel software, and returning from the beta can require wiping the device. Unless you’re testing Android, using a spare Pixel, or specifically need one of these fixes, there’s little reason to take that risk this early.
With QPR3 expected to remain in development for several months, Google has plenty of time to add additional improvements before the final Android 17 QPR3 release.
Add Tech2Geek as a preferred source on Google to see more of our latest tech articles.
Support Tech2Geek β€οΈ
Did this guide help you? If Tech2Geek saves you time or helps you solve a problem,
consider buying me a coffee. β
Your support helps keep Tech2Geek independent and free.

Comments