Pixel phones on stable Android 17 were still stuttering on Sunday. The fix is in a beta
Issue 571186734 describes a kernel regression, in mmap read-ahead, that landed with the September QPR1 update. A google.com reply on 21 October said it was resolved in Beta 7.1. The tracker now reads Fixed. Comments dated 8 November say stock phones are not. XDA’s Sunday story says the stable channel is still waiting, and its photo shows Android 17 QPR2 Beta 7.1, build CP41.260831.019.
Short2 minEasy
Eli Navarro2 min read
- Pixel
- Android 17
- GrapheneOS
Photo: XDA DevelopersSource page
People on stock Pixel phones were still describing a September stutter on Sunday, on a bug Google has already marked fixed in a beta. Issue 571186734, opened on 8 October, says Android 17 QPR1 introduced a regression in the Pixel kernel’s mmap read-ahead behavior. Under memory pressure the report lists UI stutter, multi-second freezes, slow app switching and “System UI not responding” errors. The report says GrapheneOS found the change and, in release 2026100200, restored the previous Android 17 read-ahead behavior, the one in the CP2A builds. A reply from a google.com account on 21 October says: “this issue has been resolved in the Beta 7.1 release.” The issue page’s status now reads Fixed. Comments on the same thread, dated 8 November, say the phones in their hands are not.
Chandraveer Mathur’s XDA story, published at 7:01 p.m. Eastern on Sunday, says the stable-channel fix is still awaited. The introduction names the patched beta as “QPR 3 Beta 3.” Later in the same piece, and on the phone in the story’s photograph, the build is Android 17 QPR2 Beta 7.1, CP41.260831.019. That is the build number on the install screen in the photo, and it is the build Mathur cites from a Reddit thread on Beta 7.1. He writes that there is no date for when that fix reaches the stable channel. A comment posted on the story on 8 November says the Battery Health Assistance toggle Mathur discusses is not present on a Pixel 11 Pro.
The reports are not one model. Posts on the tracker name the Pixel 7, 8, 8 Pro, 9, 9a, 10 and 10 Pro XL. Mathur writes that Pixel 10 owners seem the hardest hit, and that the Pixel 11 series appears to have been spared because Google delayed QPR1 for those phones. That delay is what users on the thread say, not a reason Google has posted on the issue. One Pixel 6 Pro owner asked for a backport, writing that the phone received the September update and is not eligible for the QPR2 beta that contains the fix. A Pixel 10 Pro XL owner, on the October security patch, wrote that freezes were still there after that update. Google has not, on the issue, given those stable builds a ship date.
Mathur is explicit that a setting cannot repair a kernel regression. What he passes on from users is a stopgap: turn off Battery Health Assistance, if the phone has it, and cap background processes so the phone is less likely to hit the memory pressure that triggers the fault. He writes that shortening animations only hides the symptom. The permanent change he describes is the one already in the beta, and in GrapheneOS’s October release, and not, as of his Sunday story, on the stable track the comments are still complaining about.