Android 17 QPR1 landed on Pixels on September 15, and it brought a serious kernel problem along with it. Processes started dying, apps stalled, and the whole phone froze under memory pressure. GrapheneOS noticed the issue too, since it updated the firmware and drivers alongside the regular release — and now the open-source project has fixed it on its own.
The fix is live, and the team behind GrapheneOS is not exactly hiding its frustration with the company that ships Android. In fact, the announcement reads almost like a shrug: “We fixed it for our release today.” The full commit is linked in the post, and the team is already moving on to bigger projects.
What The Kernel Regression Actually Does
The regression affects the Pixel kernel driver tree. Under memory pressure, the phone starts killing processes and freezing entirely. The symptoms are familiar to anyone who has watched their phone grind to a halt: stuttering, lag, and outright freezes that make the device unusable.
GrapheneOS was hit by this too, since the project updates the firmware and drivers alongside the regular release. But the open-source team moved faster than Google did. The fix is already in place for its release, and the project is documenting the whole process in public.
Why Google Takes So Long To Ship Fixes
The short answer is that Google’s release engineering and testing process is broken. The company gets fixes done quickly in days, but the actual shipping process drags out for weeks. For major Android releases, including Android 17 QPR1, the public testing period is long, and it typically takes Google at least 4 to 6 weeks to ship fixes for even the most severe issues.
The result is a pattern that GrapheneOS describes bluntly: Google either cancels a release or ships a broken one. The Pixel 11 series got a bug fix release near the start of September 2026 with the 2026-09-01 patch level, but that update wasn’t Android 17 QPR1 and didn’t include the September 2026 Pixel firmware or driver security patches. GrapheneOS suggests the issue was spotted and the update pulled.
How GrapheneOS Fixed The Regression
The fix is simple in principle: the team patched the kernel itself. The commit linked in the announcement addresses the specific driver issue causing the memory pressure failures. GrapheneOS has published the code publicly, and the project is transparent about how it handles these kinds of problems.
The team’s description of the fix is direct: it’s so severe that it’s causing processes to be killed for stalls. It’s unclear when Google will ship a fix for the issue. December 2026 wouldn’t be a surprise.
The Secure Spawning Feature
The regression is bad enough on its own, but it also prompted GrapheneOS to look at how the project uses memory. The team found a way to eliminate most extra memory use from its secure spawning feature without any significant downsides.
Removing the extra memory overhead from that feature is a big win, and the team hopes to ship it before November 2026.
The Bigger Picture Of Slow Updates
The Android 17 QPR1 regression is just the latest example of a broader trend. Standard Android and Pixel updates have a severe issue with delays. It usually takes 2 to 3 months for Google to ship fixes for both severe regressions and security issues.
The pattern repeats:
- A major release goes through public testing.
- Severe issues emerge during that testing.
- Google either cancels the release or ships a broken version.
- Open-source projects like GrapheneOS pick up the slack.
The Pixel 11 series saw a bug fix release near the start of September 2026 with the 2026-09-01 patch level, but that update wasn’t Android 17 QPR1 and didn’t include the September 2026 Pixel firmware or driver security patches. GrapheneOS suggests the issue was spotted and the update pulled.
What GrapheneOS Is Doing About It
GrapheneOS is expanding its workload to include handling basic updates, testing, and quality control for the entire operating system. The project admits it’s having to take on work that used to belong to Google, but it’s confident it can manage it.
The team has rapidly growing resources and says it’ll handle the expanded workload. The fix for the Android 17 QPR1 regression is proof that the project can move fast when it wants to.
The Fix Is Live
The kernel fix is live in GrapheneOS’s release, and the team is working on the memory pressure improvements separately. The project is documenting everything openly, which means other developers can see the work.
For users of GrapheneOS, the takeaway is simple: the team is on top of things. The regression is fixed, and the memory work is coming soon. For everyone else, the wait for a Google fix continues.
The irony is that GrapheneOS is openly complaining about Google’s slow update process while proudly linking its own hotfix for the same problem. That’s exactly why this story has legs.
GrapheneOS has fixed the Android 17 QPR1 kernel performance regression, and it did so while Google’s own process remains broken. The project is doing the work that should be done elsewhere, and it’s doing it faster.
Source material: “GrapheneOS has fixed the Android 17 QPR1 kernel performance regression,” grapheneos.org.
Get the Notebook.
The day's best stories and every fresh verdict, in plain English, in your inbox by seven. One email a day, no more.