Pixel 11 Joins Android 17 QPR2 Beta 6.1 After the Skip

Google released Android 17 QPR2 Beta 6.1 on September 29, five days after Beta 6, and the Pixel 11 family is on the list this time. Last week’s drop fixed phones that rebooted while scrolling, then never went to the Pixel 11, Pixel 11 Pro, Pixel 11 Pro XL, or Pixel 11 Pro Fold.

The new package lists no fresh bug fixes. It splits the fleet into two builds, warns Fold owners they may have to set Face Unlock up again, and turns on the rear LED glow Google already sold as a reason to buy a Pro.

The Pixel 11 Gap in Beta 6

Pixel 11 phones were not new to this beta track. They first joined Android 17 QPR2 at Beta 4 on September 1, after the August 28 images had already gone to older Pixels. Then Beta 6 arrived on September 24 as build CP41.260831.007, and the newest four models disappeared from the table.

Mishaal Rahman, Android’s community manager, posted that Beta 6 would be available for the Pixel 6a and later. Testers on Pixel 11 hardware still saw nothing. The.011 build that names those four phones showed up only with Beta 6.1.

That skip hurt because Beta 6 was the stability drop. Google’s own notes credit it with stopping crashes, reboots, and hangs while scrolling, plus a Pixel 9 Pro Fold reboot when third-party apps opened the camera viewfinder. Pixel 11 owners sat on Beta 5 (or stable) while that work shipped to everyone else.

THE QPR2 BETA CALENDAR

1. July 20, 2026: Beta 1 opens the QPR2 preview on Pixel.
2. August 28, 2026: Beta 4 hits older Pixels; Pixel 11 joins on September 1.
3. September 15, 2026: Beta 5 continues the run with the August 5 patch.
4. September 24, 2026: Beta 6 ships as CP41.260831.007 and omits Pixel 11.
5. September 29, 2026: Beta 6.1 adds Pixel 11 on CP41.260831.011.

Google already told buyers, at the August 12 Pixel 11 event, to expect more HiLight tricks later, including message alerts from favorite contacts. The phones reached stores on August 20. The text glow is landing in a beta 40 days after that, on a build that also had to reopen the door Pixel 11 lost in Beta 6.

Two Builds Now Cover 23 Pixels

Beta 6.1 is not one image with a decimal on the end. Google published QPR2 Beta 6.1 factory images under two numbers, and the split is the Pixel 11 line versus everybody else still in the program.

THE TWO SOFTWARE TRACKS

That is 23 Pixel models, plus the Android Emulator on x86 (64-bit) and ARM (v8-A). Pixel 6 and Pixel 6 Pro are out; they ended on Android 17 QPR1. Pixel 6a stays in.

Both tracks keep the same Google Play services build, 26.28.33, and the same security patch, August 5, 2026. Testers who already took September’s stable security update sit on a newer patch date than this beta, so some enrolled phones will not be offered the OTA until Google moves that date. The flash tool path is cinnamonbun-qpr2-beta6.1. Pixel 11 images use the cubs, grizzly, kodiak, and yogi names.

Fold Owners May Have to Re-Enroll Face Unlock

Google lists no bugs fixed in Beta 6.1. The notes instead flag one known Face Unlock issue on the foldable that starts at $1,899.

Pixel 11 Pro Fold users may have to re-enroll Face Unlock.

Android 17 QPR2 release notes, Google

That is the entire device-specific warning. Google does not say Face Unlock is broken, and it does not describe a patch. It tells Fold testers they may need to register a face again so the sensor works after the install.

Face Unlock has already been in this QPR’s notes. Beta 4 fixed low-light Face Unlock failures that skipped fingerprint and forced a PIN. The Fold line item in 6.1 is a setup step, not a listed repair, and it lands on the one Pixel 11 model whose hinge and cover-screen camera stack differ from the slabs.

Anyone flashing 6.1 on a Pro Fold should run Face Unlock again before treating the phone as a daily driver. The rest of the Pixel 11 series has no matching warning in the notes.

Messages Finally Wake the Rear LED

HiLight is the color LED ring around the flash on Pixel 11 Pro, Pixel 11 Pro XL, and Pixel 11 Pro Fold. The base Pixel 11 does not get it. Google’s August 13 product post framed HiLight on Pixel 11 Pro as a way to stay current with the phone face down, using color for favorite callers and glow patterns while Gemini listens, thinks, or answers.

At launch you got two jobs and five colors. Beta 6.1 adds the third job Google previewed in August: texts from people you have marked as favorites. After the update, Settings, then System, then HiLight shows a new line, “Messages from favorites: Glows when your favorite contacts send you messages,” under Speaking with Gemini and Calls. A Contacts sheet lets you toggle phone calls and messages on their own. A new text makes the ring blink twice. Google Messages is working in that build.

HILIGHT TRIGGERS IN 6.1

• Favorite calls: The ring lights in the color you assigned when a starred contact rings through Phone by Google or WhatsApp, with the phone face down.
• Gemini status: Separate glow patterns show listening, thinking, and responding.
• Favorite texts: The same favorites path now fires for messages, with a two-blink alert in this beta.

Launch software offered five hues. Contacts strings already named nine: blue, cyan, green, orange, pink, purple, teal, white, and yellow. The 6.1 settings walk testers described still centers on the new messages toggle, not a confirmed jump to that wider palette. WhatsApp already drives HiLight for calls; whether its chats trip the two-blink alert is still a check for testers, not a claim in Google’s notes.

What Beta 6 Fixed While Pixel 11 Waited

Beta 6, posted September 24, is the changelog Pixel 11 did not receive on time. Google listed six top fixes, several of them the kind of crash that ends a test day. Pixel 11 jumping to 6.1 inherits that work in one step, along with two feature cuts testers already noticed on older phones.

TOP FIXES IN BETA 6

• Status bar leak: Letterboxed content no longer bleeds through the status bar during app transitions (Issue 493438057).
• Blank screensaver: The screensaver no longer shows a blank screen while charging (Issues 516262713 and 526560397).
• Fold camera reboot: Pixel 9 Pro Fold no longer reboots when third-party apps open the camera viewfinder (Issues 555960820, 558564487, 554763027, 559421409).
• Locked apps in Recents: Locked apps can be dismissed with a swipe in Recents again (Issue 555579953).
• Biometric kernel crash: A kernel crash that rebooted phones when third-party apps asked for camera and mic together during biometric checks is fixed (Issue 557712189).
• Scroll crashes: An issue that caused crashes, reboots, or hangs while scrolling is fixed (Issue 559054323).

Rahman told testers that App Lock and notification-shade blur were pulled in Beta 6 to fix bugs underneath, and that both would return in a later drop. Pixel 11 owners who install 6.1 land in that stripped state. They also pick up the scroll and camera-stack fixes without having lived on the broken Beta 6 build for five days.

Call-Forwarding Scams Hit a System Dialog

The 6.1 notes restated a QPR2 security change that is easy to skip next to the Fold warning. Android 17 QPR2 now parses call-forwarding USSD codes such as *21# when an app fires them through TelephonyManager.sendUssdRequest(), and it blocks a quiet class of number hijacks.

THE NEW USSD RULES

• API lock: sendUssdRequest() can no longer run call-forwarding codes with only the CALL_PHONE permission. Background attempts get USSD_ERROR_NOT_ALLOWED.
• Confirm dialog: If you type a forwarding code in the system dialer, Android shows an OS-level confirm screen before the code runs.
• Other USSD: Mobile-money and account-check codes that do not enable forwarding stay as they were.
• App path: Apps that still need forwarding and do not hold an exempted role should send the user to ACTION_DIAL with the code filled in, then wait for a tap.

Google calls QPR2 a minor SDK release with no planned behavior changes for most apps. This USSD lock is the exception that will break silent forwarding tools. It is also the one 6.1 note that is not about Pixel 11 hardware.

Cinnamonbun Images Are Ready to Flash

Enrolled Pixels should see Beta 6.1 as an over-the-air update. Developers can sideload from the factory image page or use Android Flash Tool at the cinnamonbun-qpr2-beta6.1 preview. Flashing a factory image wipes the phone. Leaving the Android Beta program later is how you get back to the public build.

QPR2 is a quarterly Feature Drop. This preview is the run-up to the December Pixel drop, so 6.1 is late-cycle plumbing, not a new platform. Pixel 11 is on the train again, on its own.011 build, with a Fold Face Unlock setup step and a rear LED that finally blinks when a favorite texts.

If you are on a Pixel 11 Pro Fold, re-enroll Face Unlock after the reboot. If you already took September’s stable patch, wait for Google to move the beta’s August 5 date, or flash knowing you are stepping backward on security to join the test.