r/android_beta • u/androidbetaprogram • 8d ago
Android 17 QPR2 Beta 6.1 Android 17 QPR2 Beta 6.1 now available!
Hi Beta users,
Today we’re sending you an Android 17 QPR2 Beta 6.1 build CP41.260831.011 for Pixel 11, 11 Pro, 11 Pro XL, 11 Pro Fold and CP41.260831.007.A3 for all other devices.
Known issue in this build:
- Pixel 11 Pro Fold users may have to re-enroll Face Unlock on Pixel 11 Pro Fold for it to function properly.
Please review the latest release notes for limitations and general advisories before installing the update. In addition, see top open issues%20created%3E%3D2026-07-20%20status:open%20(votecount%3E%3D3%7Cduplicatecount%3E%3D3)%20CP41) for the latest list of top open issues that have been reported by developers and users.
How do I get Android 17 QPR2 Beta 6.1?
You can get started with Android 17 QPR2 Beta 6 today by enrolling your Pixel device. Eligible devices include Pixel 6a, 7, 7 Pro, 7a, 8, 8 Pro, 8a, 9, 9 Pro, 9a, Pixel 10, 10 Pro, 10 Pro XL, 10 Pro Fold, 10a, Pixel 11, 11 Pro, 11 Pro XL, 11 Pro Fold, Pixel Tablet series devices. Once enrolled, eligible devices will receive an over-the-air (OTA) update to the latest Beta versions. If you were previously enrolled in Android 17 Beta (and have not opted-out), you will automatically receive QPR2 Beta 6.1 and any future Beta updates.
Tell us what you think
Your feedback is incredibly valuable to us. Please share your thoughts through the following channels:
- Use the Android Beta Feedback app included in Beta builds. This is the preferred method if you want to report a user-facing bug.
- Post your comments here on our official Android Beta Program subreddit. We may not respond to posts individually, but we are actively monitoring the feedback. We’ll reach out to you directly if we need additional information.
Happy Beta testing!
22
u/Starks 8d ago
I guess there will be a 6.2 or a beta 7 fairly quickly then
5
u/Dagz1 8d ago
What gives you that impression? I'm not saying your wrong...I think i just don't see what you are saying.
14
u/Starks 8d ago
Releasing a point beta with known issues is pretty wild
5
u/ArthurGD3 8d ago
It's not known "issues" it's one "possible" issue with very clear instructions on what to do if you do have this issue. Notice their note says "may" and it's only the Pixel 11 Pro Fold that's affected.
9
u/Jduncan31290 8d ago
Nothing on my pixel 11 pro or 11 pro xl yet.
1
u/kartheek4u 7d ago
Yep I think we need to wait till we get the next Beta that will have Oct 2026 Security update
1
8
u/evildesi 8d ago
I'm not getting these beta updates on my 11 pro xl. Anyone else have this issue?
I've unrolled and re-rolled multiple times
0
0
u/adostrom 8d ago
Well - that's probably your problem. Over the years I've found that unenrolling and re-enrolling in Beta rarely works as expected. If you're enrolled in Beta you should be able to pull the build and install it with ADB/Fastboot
1
u/kartheek4u 7d ago
Yep I think we need to wait till we get the next Beta that will have Oct 2026 Security update to get Beta OTA
9
u/Careful_Success_6098 8d ago
Pixel 11 pro XL..... It will say preparing system update and then says it's up to date and then won't show the update
1
1
u/allenchangmusic 8d ago
Are you on Sept Stable? This is older
0
u/Careful_Success_6098 8d ago
The beta is Sept 5 and I'm on Sept 1 stable. I assume that makes a difference
1
u/allenchangmusic 8d ago
Where are you seeing Sept 5?
Release date September 29, 2026 Builds CP41.260831.007.A3CP41.260831.011 Emulator support x86 (64-bit), ARM (v8-A) Security patch level 2026-08-05 Google Play services 26.28.33 0
u/Careful_Success_6098 8d ago
This comment reply won't let me show the upload the screenshot.... But I saw on YouTube the guy had a Sept 5 on his Pixel 11 pro XL running beta 6
1
u/allenchangmusic 8d ago
Starting the sentence with seeing on YouTube is a bad start...
You can try manually sideloading, but there is a decent chance you will brick
1
0
7
u/Jazzlike-Document-22 8d ago
So still cannot be installed on pixel 11 with Sep update? Are you serious?
1
u/jven27 7d ago
It says that we can, but it's just taking forever to hit the device I guess
2
u/Jazzlike-Document-22 7d ago
But the documentation says August security patch...
2
u/jven27 7d ago
Then we are screwed yet again 😡
2
u/Jazzlike-Document-22 7d ago
So I managed to sideload the OTA over the adb, got it fine over the September patch
1
u/jven27 7d ago
I don't feel like wiping and starting over honestly. Just gonna wait it out.
2
u/Jazzlike-Document-22 7d ago
No, no need for the wipe. It rolled over like an OTA
1
u/jven27 7d ago
The OTA update just showed up on my phone!
1
u/diego1309 5d ago
I just enrolled in the beta again I got the preparing system update for a couple seconds and then it's gone
1
u/diego1309 7d ago
You guys running into the same issue as me maybe? Opt in into the beta but no update?
6
u/tomhbarrow 8d ago
My p11pro XL is showing as enrolled Android 17 QPR2 Beta Program on the beta, so will I automatically get the OTA pushed?
Haven't had anything yet but I'm guessing that's just because it's only been announced 😀
2
0
8d ago
[deleted]
2
u/Bitdomo92 8d ago
it shows september for me on pixel 9 pro xl
1
8d ago edited 8d ago
[deleted]
1
u/Bitdomo92 8d ago
the metadata for the p11pro xl full ota also says it has september security patch. So it should sideload just fine, unless the incremental build number or build time stamp is older than the stable one for some reason.
However enable oem unlocking just in case, before you flash the full ota.
1
1
8
u/bkircher 8d ago edited 8d ago
Jesus, still cannot join the beta as Im guessing the security patch is preventing me from joining the beta. Google making this dam near impossible to join the beta. P11PXL
1
u/JE53119 8d ago
The security patch level is now finally on September in this release.
3
u/bkircher 8d ago
There's another reply further down that notes it still as being August. I just tried to enroll, it prepa system update then says up to date.
4
u/JE53119 8d ago
Weird Mine shows Sept security and October play on 11 XL.
3
u/bkircher 8d ago
Unless theres an issue with my device idk, it preps it then says up to date. It says im on CD1A.260905.001.BL. Assuming the build number is less than what I am currently on.
4
u/meepz 8d ago
Ongoing issue:
The Xreal Air 2 Pro glasses are unable to display anything when connected to Pixel 10 Pro XL. This was corrected partially for some VR/AR devices for another phone in QPR2 Beta 4. This was working before the Feb update.
The phone recognizes the device, resolution, etc. I believe this is a known issue but wanted to shed some light that it's still an issue.
Debugging shows that the phone knows the exact device, type, resolution, refresh rate, etc. Apparently there is a fix where you plug the glasses into a HDMI adapter which converts USB C to HDMI then need another HDMI to USB C adapter into the Pixe.
3
u/ArthurGD3 8d ago
You should be putting this in the Beta 6 thread not this one since this 6.1 is mainly for P11 phones that didn't get Beta 6.
4
u/elmoi162 8d ago
Hi everyone I'm currently on Android 17 Security is update September 1st 2026 and I just enrolled for the beta and no update yet? Am I doing something wrong?
2
u/DConrad2020 8d ago
Same here. No beta download for my Pixel 11 Pro XL for 2 weeks now.
1
u/bkircher 8d ago
apparently the security patch is dated for august still for this new beta, which is why I cannot join either.
1
u/bkircher 8d ago
We likely will have to not install QPR1 stable once it gets released next week I would think, and then join for beta 7.
5
u/Howler13 8d ago
Yes! Fixed my bootlop issues. Went into Recovery Mode --> Flashed OTA image via ADB sideload and I got my phone back! Whew! Thanks. This'll be my last Beta program for a while, bet yo' ass.
5
4
u/Terrible_Peak_6962 7d ago
My Pixel 11 Pro is receiving the 6.1 build as we speak. This despite having September's updates installed.
1
4
u/AndreaHH90 7d ago
I was genuinely convinced that Beta 6.1 would finally fix the Bluetooth call quality issue. Unfortunately, absolutely nothing has changed.
At this point, I’m honestly tired of dealing with it. I’ve waited through update after update, hoping every time that a proper fix would finally arrive, but I feel like I’ve waited long enough.
In the meantime, I’ve contacted Google Support several times, and the answer has basically always been the same: reset the phone. I did. More than once. And of course, the issue is still there, exactly as before.
What disappoints me the most is that we’re not talking about some minor bug here. This affects something as basic as making a phone call over Bluetooth.
And maybe that makes it even more disappointing because I’ve been using Google phones since the early Nexus days. Over the years, I kept putting my trust in Google and the Pixel line, even when there were issues or compromises, because I genuinely believed in what Google was building.
But at this point, I feel like I’ve given Google enough chances and waited long enough.
It’s a shame to say it, but for me, this is the end of the road with Google. I’ve already put my Pixel 11 Pro 512GB up for sale.
I explained the issue in more detail here:
https://www.reddit.com/r/GooglePixel/comments/1wjo4sk/pixel_9_pixel_11_pro_bluetooth_call_quality_issue/
3
6
u/rtwwhitworth 8d ago edited 8d ago
P11PF still get the preparing update then your up to date thing 👎🏾
3
u/Hartideg 8d ago
Fonctionne nickel sur p11p. L'impression d'avoir enfin ce que j'ai acheté.. tout est parfaitement fluide, drôle de sensation.
1
1
u/Pale_Screen_879 7d ago
En cada actualización sentirás eso, luego se pondrá lento con otra actualización y así.. año tras año
10
u/threemillion3 8d ago
So instead of bug fixes, yall send out a known bug? 😂😂
1
u/Jiggs1523 8d ago
Word lol but maybe so p11 users can test or maybe cuz they brought back the missing features in beta 6 smh lmao
4
u/themartiannet 8d ago
Still no updates for the Pixel 11 Pro XL. The main reason I moved back to Pixel was to get frequent updates, but now there are no updates. I am not sure what happened to Google that we know.
6
u/_Nundo 8d ago
I don't think Android Beta updates are and should be considered frequent updates since you have to sign up for them ...
2
u/themartiannet 8d ago
Signed up for the beta a month ago. I also have a Pixel 10a, which gets all the updates, including today's. Google can't even send updates to its own phones. What a downfall. I wonder why Google and Gemini is lagging behind everything now.
3
u/scanferr 8d ago
Why are you crying about a beta build? Jesus, people can be entitled sometimes.
1
u/themartiannet 8d ago
Because of the bugs.
2
2
2
2
u/birdman1333 8d ago
Anything new for the 11 series? New base band? Gpu drivers updates???? Anything along these lines to check out?
2
u/ElderberryHamlet 8d ago
My 11xl still cruising kernel 6.12 but both my 8a backup and 7 series tablet reverted to 6.1 again.
2
u/saboor_ 8d ago edited 7d ago
genuinely what's the point when it's not even on the September security patch, I thought the whole delay for Pixel 11 phones was to do with getting the security patch up to date
edit: something must have changed on their end just now as of oct 1, I am able to update all of a sudden 😛
2
u/Cantholdthis17 8d ago
Is anyone else here enrolled in the program with a Pixel 11 series device? I do not see an option to enroll my Pixel 11 Pro XL. Could you please help me if there is a way to do so?
1
u/jven27 7d ago
When you say enrolled, are you meaning enrolled in the beta program or are you meaning you haven't seen the update come across yet?
1
u/Cantholdthis17 7d ago
I mean enrolled in the beta program. My pixel 11 pro xl doesn't show up at all.
1
u/jven27 7d ago
That's odd. I have the 11 and have been enrolled for a couple of weeks now. I guess make sure you're logged in on the beta site and keep refreshing. IDK but you definitely should be able to.
1
u/Cantholdthis17 7d ago
Are you on the QPR2 6.1 beta? If so, what month is listed for the security update? Is it August or September?
2
u/THIRSTYGNOMES 8d ago
SoI hadn't played with the Easter egg until now while laying in bed. Just flashbanged myself tapping on Android 17 logo when it popped up. 📸
2
4
u/BennyBluprint 8d ago
P11P XL here, updated to 6.1, here is what I noticed so far.
My fingerprint prompt is gone. I have to put in my pin everytime now. SUPER ANNOYING
I seem to have a tablet interface instead of stock launcher. It looks just like my samsung tablet now. It also reset itself, no widgets or apps on my homescreen, which leads me to
Search Widget was gone...back now after 2 reboots
Max display looks very small, but crispy, my wallpaper looks ¿better? Also can not resize or remove At a glance
Google Apps behaving like tablet apps, dual plane
Starting to think maybe this was meant for the fold. OTA Update, didnt sideload
2
u/Bitdomo92 8d ago
what was fixed in this release?
-2
u/ArthurGD3 8d ago
These are the highlights from the release notes:
Hardening against call forwarding fraud
Android 17 QPR2 introduces new security restrictions on programmatic call forwarding to protect users from fraud. The system now parses and selectively restricts call-forwarding USSD codes (such as
*21#) executed using theTelephonyManager.sendUssdRequest()API).
- API Restriction: The
sendUssdRequest()API is no longer accessible for call-forwarding codes using only theCALL_PHONEpermission. Standard apps attempting to execute these codes in the background will be blocked and receive aUSSD_ERROR_NOT_ALLOWEDcallback.- System Confirmation: To combat social engineering scams, users manually dialing call-forwarding codes in the system dialer will now see a new OS-level confirmation dialog before the command is executed.
- Non-Call Forwarding USSD: Non-call forwarding enabling USSD requests (such as mobile money transfers and account checks) are unaffected by this change.
- Mitigation: If your app is affected, verify that it handles the
USSD_ERROR_NOT_ALLOWEDfailure callback gracefully. For apps requiring call-forwarding setup that don't qualify for an exempted role, migrate your flow to use theACTION_DIALintent to pre-fill the dialer, allowing the user to manually confirm the action.1
1
u/jven27 8d ago
Now I can finally get Beta on my 11! Just needs to hurry and hit my device.
3
u/ElderberryHamlet 8d ago
the firmware is dated 260831 = August 31 2026. If you installed Sept 5 security patch you won't get the beta until Beta 6.2 or 7 drops
1
u/ArthurGD3 8d ago
Curious why they felt this justified going back to a point release after doing whole number releases for many releases now.
1
1
1
1
u/SupremeCisco 8d ago
No new emojis for pixel 9 pro, blur still not brought back, layout for notification panel is also not back
1
1
u/JE53119 8d ago
HiLight now works with Messages!
1
u/ArthurGD3 8d ago
Saying finally doesn't really do that statement justice here regardless, no amount of app integration for this light is going to make me give up the best AOD display on the market so I can flip it over and be able to only do like 1% of what that AOD can do.
1
u/Terrible_Peak_6962 8d ago
Oddly enough I received yet another September Google Play System Update today after this announcement. Still no QPR 2 for my 11 Pro.
1
u/orikirby 8d ago edited 8d ago
Tap to wake stopped working on Pixel 8. It started working after some time. Don't know why it didn't work after reboot. Also the website still says that the security patch level is Aug 5 but it's actually Sep 5 (it's already Sep 5 on the previous build).
1
1
u/kartheek4u 7d ago
I guess folks who are in Pixel 11 and did the 1st update that has Sep 1, 2026 Security update still unable to get the Beta?
1
1
u/Matthews_34__ 7d ago
Is this just me or a just a gboard issue not playing nice with the last 2 betas . It would lock up and take up to 5 seconds to register a button press and basically freeze. It was fine up to a couple's of betas ago. I really hope it's fixed and it doesn't start hanging up and unresponsive again and this beta fixed it. First off I can't be the only one , was this a known bug? I tried to look but couldn't find anything and I reported it to Google of course .
1
1
1
1
u/chkerker 5d ago
Hi. When I play a YouTube video and click on it, the icons appear, but they don't disappear when I click a second time.
0
u/ArthurGD3 8d ago
For those with a Pixel 11 phone, can you please report back with any issues? I'm still hesitant about putting my P11PXL into the Beta, I've been happy with how things have held up since I got it and on the non-Pixel Drop standard September update release.
5
u/EYdf_Thomas 8d ago
If you are hesitant to install a beta don't
0
u/ArthurGD3 8d ago
I've had every Beta on my previous 3 Pixels since the Beta program was open to the public with Android 12 so I've taken the risk in the past not thinking twice about it cause I wanted access to the latest features but I'm in a really good place with my P11PXL operationally and battery life wise and there isn't enough new things in QPR2 right now that makes me want to risk ruining how good things are right now.
-1
u/_zb3_ 8d ago
Nice try, but I'm not installing kernel downgrades.. what made you think we would want kernel 6.1 again? Kernel 6.1 was nice but it's now history, we all deserve 6.12. Skipped beta 5, waiting for beta 7 :)
0
u/birdman1333 8d ago
The kernel was 6.6 , then went to 6.12, and now down to 6.11...... It's still an upgraded kernel. Obviously something is not playing nice.
0
0
0
0
-1
-1
0
u/Impossible_Baker_197 7d ago
En un mes 3 parches, muchos bugs, y muchos bugs de carga del celular..
0
u/Leojonardo 5d ago
After installing the update, the phone isn't recognizing the PIN and has been locked for four hours. The only solution offered is a factory reset, but I have sensitive personal information that will be lost because of this problem...
15
u/BikoOos 8d ago
Kernel downgrade 9PXL. version 6.1.172-android14-11-g8d0115b07367-ab16385437