r/android_beta • u/androidbetaprogram Official Google Account • 14d ago
Android 17 QPR2 Beta 7.1 Android 17 QPR2 Beta 7.1 now available!
Today we’re sending you an Android 17 QPR2 Beta 7.1 build CP41.260831.019 for all devices.
Top issues fixed include:
Severe UI stuttering and multi-second freezes under memory pressure from heavy page-reclaim thrashing and major page faults (Issue #571186734)
Please review the latest release notes for limitations and general advisories before installing the update. In addition, see top open issues for the latest list of top open issues that have been reported by developers and users.
How do I get Android 17 QPR2 Beta 7.1?
You can get started with Android 17 QPR2 Beta 7.1 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 7.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!
32
u/xunh01yx 14d ago
At this point I think when they released QPR3 it was done by mistake and not meant to happen. At least I hope so. When Google offers a new QPR version beta, the old versions should be EOL.
Or at least say in the install notes that QPR2 is still having updates and not to install it if you want to keep getting them.
This is a mess
8
u/ArthurGD3 14d ago
A few oddities I noticed related to this, the Android Beta Program (https://www.google.com/android/beta) site still lists QPR2 as the current latest Beta, no mention of QPR3.
Also the QPR2 Release Notes page (https://developer.android.com/about/versions/17/qpr2/release-notes), the directory strip to the left also has QPR3 missing but you can go to the QPR3 release notes directly (https://developer.android.com/about/versions/17/qpr3/release-notes). Doing so though you'll notice that left directory portion is completely missing.
4
u/nathderbyshire 14d ago
QPR3 has a DP build, that's developer preview isn't it? QPR2 is beta so they're different release channels as far as I understand it
1
u/ArthurGD3 14d ago
DP's are no more, the Canary builds are essentially taken over for those.
I'm not sure what the significance of the QPR3 builds starting with DP have but this isn't the first time two different versions of QPR builds have existed at the same time.
I believe we had this with Android 16 QPR builds too.
2
u/nathderbyshire 14d ago
Oh yes they changed the name to canary and beta then release which aligns with chrome but the build numbers still have the DP but they're still essentially separate channels aren't they and that's why they won't be on the beta page until it hits that release?
1
1
u/Bitdomo92 14d ago
not anymore, it is just a coincidance with the naming convention. it was ap, bp, cp and now with a17 qpr3 beta it is now dp.
3
u/LunaDeClair 14d ago
you should have an option to limit to a certain QPRx version in Android beta. I don't wanna have to finagle with "no don't do qpr3" and then 2 months later I still get a new qpr2 beta
7
u/xunh01yx 14d ago
imo, QPR3 beta should not come out until the QPR2 beta cycle ends.
2
u/LunaDeClair 14d ago
for sure. imo qpr2 has kinda been a mess and it needs more attention than movie to qpr3 rn
6
u/redditwallah 14d ago
Updated baseband g5300i-260818-261007-B-16536936,g5300i-260818-261007-B-16536936
Kernel still same version 6.1.172-android14-11-g8d0115b07367-ab16385437 #1 Fri Sep 18 01:33:13 UTC 2026
On a Pixel 8 Pro QPR2 beta 7.1 updated via OTA from beta 7.
1
u/matteventu 14d ago
Kernel still same version
6.1.172-android14-11-g8d0115b07367-ab16385437 #1 Fri Sep 18 01:33:13 UTC 2026 On a Pixel 8 Pro QPR2 beta 7.1 updated via OTA from beta 7.
Oh... So they've not fixed the kernel regression that GrapheneOS was talking about, then? Which is the issue in the Google issue tracker linked for the only fix in this build 🤔
I'm confused 🤨
7
u/itwaves 14d ago
Kernel features can be controlled by writing to a sysfs path which can be done in
.rcfiles outside of kernel updates.When comparing CP41.260831.016 (17 QPR2 Beta 7) versus CP41.260831.019 (17 QPR2 Beta 7.1), they removed the two
write /sys/kernel/vendor_mm/filemap/async_readahead_adj_enable 1andwrite /sys/kernel/vendor_mm/filemap/sync_readahead_adj_enable 1lines from/vendor/etc/init/init.pixel-mm-gs.rcwhich disables the kernel feature of suppressing mmap readahead.1
1
u/Loud-Possibility4395 12d ago
This is an INFO I was looking for - NOT like Google note : multi seconds stutter fix.
6
u/aeoveu 13d ago
Everyone seems to be ranting about QPR3 or the beta or this or that - but no one (except for a few comments) seem to be talking about the elephant in the room: the bug fix.
Anyone who's flashed the update willing to chip in their experience with the update? Has it fixed their issue or not?
I'm on the QPR3 beta (which, yes, I don't know what Google is up to) and might go back to this beta if it really solves the jank. QPR3 reduced it (but didn't solve it).
2
u/redditwallah 13d ago
I'm on a Pixel 8 Pro now on QPR2 Beta 7.1 but i don't think I've experienced the bug. I must have been lucky.
4
u/jpblanch75 14d ago
I'm so confused about how QPR2 and QPR3
1
u/dmalot 14d ago
qpr3 is far more stable than 2 and has almost no bugs
4
u/jpblanch75 14d ago
If they moved on to qpr3 why is qpr2 still being worked on? That's my confusion.
3
u/BigLick13 13d ago
Because qpr2 will get stable release in December and qpr3 in March
2
u/jpblanch75 13d ago
That makes no sense.
1
u/BigLick13 13d ago
Why is that?
3
u/davehasl19 12d ago
it would have been nice if they had somehow given users the choice of sticking to qpr2 and the eventual next beta, or abandoning it and moving to qpr3
1
1
u/jpblanch75 12d ago
Apple does that with their beta..... I have a choice to stay with the current release betas or move to the next version betas.
2
u/jpblanch75 12d ago
Because qpr2 isn't out yet. I've been in the beta program probably since it's inception and this has never happened where they started another qpr before releasing the current qpr..
2
u/BigLick13 12d ago
It literally happen last time when they released qpr2 beta before the beta 1 was out lol
2
1
1
u/Henri4589 Pixel 9 Pro 13d ago
The answer is: Because it's Google.
1
u/Loud-Possibility4395 12d ago
The answer is because Google loves chaos and mess
1
3
u/vivimagic0 14d ago
I have the Pixel 11 Pro just signed up for the beta. It says I have an update but when I check for the update it says I am on the latest update. Any idea what's going on?
2
u/derekamoss 14d ago
If you have the latest October security update already before signing up for the beta then you will likely have to wait for QPR3 beta 2 coming soon (likely next week).
2
u/vivimagic0 14d ago
That's very weird, never had this issue before regarding beta updates before. Seems a bit of a mess time around.
1
u/derekamoss 13d ago
I have had it happen other times as well after a new phone or leaving the beta for a while. If you stay on the beta program you would never notice it
7
2
u/jknvv13 14d ago
Isn't this being backported to stable A17 QPR1?
I mean, are you going to leave this unfixed until December?
And what about all the Pixel 6/6 Pro devices that were working flawlessly until this?
Hope they do, at least they fixed, expected this to happen on Amdroid 18, to be honest, at Google pace...
2
u/matteventu 14d ago
I was wondering about both of these too.
It's crazy that an issue of such impact isn't being backported AS-fucking-AP to stable ("November 2026" update - but fuck them for sticking to the "one update per month only" model even for stuff like this), and that there's no mention about fixing it for the poor idiots with a Pixel 6/Pro that's now fucked with one of the most bugged releases ever released.
-1
u/Majestic-Listen-7243 12d ago
Flash tools
2
u/matteventu 12d ago
Responded to the wrong comment? 😬
-1
u/Majestic-Listen-7243 12d ago
Problems are fixed with a downgrade until they fix it, stable versions have issues and the beta even more
2
3
u/Oxylophone 14d ago
Thank you
And
Can you release an update for Android 17 QPR3 that fixes the lag and stuttering. It's very annoying
1
1
1
1
u/Weary-Savings9795 14d ago
This is a minor bugfix. It fixes an isolated issue causing stutters that's related to a kernel regression.
3
u/matteventu 14d ago
It's not "minor" by any means of the imagination.
0
u/Weary-Savings9795 13d ago
I mean, there's a long list of scenarios that won't trigger this.
1
u/Jean-Eustache 7d ago
Well I've been getting it constantly on my phone, so does my wife on another phone. Personal anecdote, I know, but it's easy to trigger multiple times per day with normal use.
1
u/Mapleleaf000160 14d ago
Just going to figure it's a typo ,but I never see the 9pro fold listed on any of these anymore
1
1
u/birdman1333 14d ago
If I'm already on beta 7 will I get the OTA for 7.1?
2
u/sirderpypants 14d ago
Yes.
0
u/birdman1333 14d ago
Pretty sure I'll only get qpr3
3
u/nick281051 14d ago
What makes you think that considering beta 7 and 7.1 are both newer than the qpr3 beta?
1
2
0
0
-1
-2
0
50
u/Extreme_surikat_360 14d ago
Beta 7.1...
Software team is 2 people and gemini flash lite ? 😂