Pixel Lag After Android 17 QPR1? Fixes That Work

Updated 26 October 2026. Checked against Google's issue tracker, Pixel Phone Help, the Android Beta program pages, and reporting from Android Authority and 9to5Google.

Short answer: if your Pixel has been stuttering, freezing for a few seconds at a time or throwing "System UI isn't responding" since the September 2026 update, you're probably hitting a known bug in Android 17 QPR1. Google has fixed it, but so far only in Android 17 QPR2 Beta 7.1. Until the fix reaches the stable channel, keep at least 10% of your storage free, clear the Pixel Launcher cache, restart now and then, and look for apps eating memory. If the phone is close to unusable, the beta gets you the fix today, but read the catch in Step 9 first.

The bug has a fairly narrow trigger: it bites when the phone runs short on memory. That's why one person's Pixel 8 is crawling while another owner says theirs is fine, and why most of what helps comes down to keeping memory pressure low until a proper update arrives. Below is everything worth trying, cheapest first, plus a quick check of your alarms, since at least one owner found theirs switched off after the update.

Jump to:

• What's causing the lag
• Is it the QPR1 bug?
• Step 1: Check your build
• Step 2: Free up storage
• Step 3: Clear the Pixel Launcher cache
• Step 4: Restart more often
• Step 5: Find memory-hungry apps
• Step 6: Safe mode
• Step 7: Reset app preferences
• Step 8: Limit background processes
• Step 9: Get the fix through the beta
• Step 10: Factory reset (last resort)
• Check your alarms
• When the stable fix lands
• FAQ

What's causing Pixel lag after Android 17 QPR1?

Android 17 QPR1 reached Pixels on 15 September 2026 alongside the September Pixel Drop, as 9to5Google reported. Within days, the Pixel subreddits filled up with complaints: frame drops in the app drawer, apps taking ages to reopen, phones running warm, battery life falling off a cliff.

On 2 October the GrapheneOS team said it had found the cause: a regression in the Pixel kernel driver tree causing "stuttering, lag and outright freezes under memory pressure". Because the bug sits in Google's own drivers, it hits stock Pixels too. GrapheneOS patched its own build the same day. Android Authority noted that this fit its reader survey, where roughly one in five respondents reported new performance problems after QPR1 and 31% reported no new issues at all.

The public bug, issue 571186734, now has more than 150 comments. Most come from Pixel 8 owners, though people with Pixel 6, 7, 9 and 10 models chime in too. Several say the October update didn't help. One Pixel 8 owner posted logs showing zRAM swap almost used up and Android's low-memory killer closing processes just as apps froze. That matches Google's own wording for the fix: "severe UI stuttering and multi-second freezes under memory pressure from heavy page-reclaim thrashing and major page faults."

In plain terms, once RAM fills up the phone has to shuffle data in and out of memory, and since QPR1 it does that badly. Apps you switch back to reload from scratch, the keyboard pauses and then dumps three words at once, and now and then the whole screen stops responding.

Is it the QPR1 bug or something else?

Not every slow Pixel has this bug. Launcher glitches and post-update optimisation look similar and are easier to fix. Match what you're seeing:

Pixel 11 owners, take note: 9to5Google reports the Pixel 11 series is still on base Android 17 even after the October update. If yours lags, this bug probably isn't why.

Step 1: Check your build and install pending updates

Open Settings > About phone > Android version to see the version, security update date and build number. A build starting with CP3A means you're on QPR1. Google's update help page shows where each item lives.

Then go to Settings > System > Software updates and install anything waiting, including the Google Play system update. Pixels download updates in the background and only switch over on the next restart, so a notification that's been sitting there for days may just need you to tap Restart. While you're at it, open the Play Store, tap your profile icon, choose Manage apps & devices and update everything. None of this fixes the kernel bug, but an old app with a memory leak makes it a lot worse.

Google also says battery drain is normal right after an update while the phone finishes optimising. If you updated yesterday, give it a day.

Step 2: Free up storage

This sounds unrelated, but it keeps coming up. Google's slow Pixel guide warns your phone "can have issues when less than 10% of storage is available". On the issue tracker, one owner said freeing up space made the problem go away. Another freed 27 GB and still had it, so treat this as a help rather than a cure. It's just the easiest thing on the list.

Check Settings > Storage, then:

• Use Free up space in Google Photos to drop local copies of photos that are already backed up.
• Open Files by Google and clear old downloads, duplicates and big videos.
• Archive apps you rarely use. Your data stays put and the app comes back with a tap.
• Clean out chat media. WhatsApp has its own Manage storage screen under Settings > Storage and data.

Step 3: Clear the Pixel Launcher cache

If the stutter is mostly on the home screen, in the app drawer or in the recent apps view, start here. Google's own Pixel Community team keeps suggesting it in the r/pixel_phones QPR1 threads, and a Pixel 10 Pro owner whose app drawer dropped frames after updating said it fixed things.

1. Go to Settings > Apps > See all apps.
2. If Pixel Launcher isn't listed, tap the three-dot menu and choose Show system.
3. Open Pixel Launcher > Storage & cache and tap Clear cache.
4. Restart the phone.

Still choppy? Go back and tap Clear storage. That wipes your home screen layout, widgets and shortcuts, so screenshot it first. The Pixel 10 Pro owner needed this second step before scrolling was smooth. It won't touch the memory bug, but it clears up a lot of launcher-only lag that showed up alongside it.

Step 4: Restart more often than you normally would

Since the lag builds as memory fills, a restart wipes the slate clean. Until the fix lands, restarting once a day, or before you need the phone for something important, is a cheap way to stay ahead of it.

On a Pixel 6 or later, hold Power and Volume up for a few seconds and tap Restart. If the screen is frozen, Google's frozen Pixel guide says to hold the power button for about 60 seconds.

If your Pixel is also running hot and charging slowly, a few tips from my guide to a phone that's charging slowly apply here as well, like taking the case off and not gaming while it charges.

Step 5: Find the apps using the most memory

Because memory pressure sets the bug off, one bloated app can tip the whole phone over. On the GrapheneOS forum, one user found a photo-backup app sitting on about 4 GB of RAM. After a force stop it came back at around 600 MB.

To look for yourself, turn on Developer options by tapping Build number seven times in Settings > About phone. Then open Settings > System > Developer options > Memory and check memory used by apps. Settings > Battery > Battery usage is worth a glance too.

If something looks way out of line, open it under Settings > Apps and tap Force stop. Google suggests noting which apps you force stop, since a pattern points to the culprit. Don't force-close everything all day, though. Android caches apps so they reopen fast, and killing healthy ones usually costs more battery than it saves.

Step 6: Test in safe mode

Safe mode starts the phone with every downloaded app turned off. If the stutter goes away there, an app is involved. If it's just as bad, it's the system, and you can skip to Step 8. Samsung owners have a different use for it right now: safe mode is part of the workaround when a Galaxy gets stuck after the update, which I cover in my One UI 9 XML Access Denied fix.

Per Google's safe mode instructions, on a Pixel 6 or later hold Power and Volume up, then touch and hold Power off or Restart until the safe mode prompt shows, and tap OK. Airplane mode turns on automatically, and some home screen widgets get removed, so take that screenshot first.

Use the phone for a while, ideally as long as it used to take for the lag to show. If it behaves, restart normally and remove recent apps one at a time, restarting after each. Launchers, customisation tools and anything that draws over other apps are good suspects.

Step 7: Reset app preferences

Pixel Community moderators also suggested this in a QPR1 thread on r/pixel_phones. Go to Settings > System > Reset options > Reset app preferences. It restores disabled apps, notification limits, default apps, background data limits and permission choices to their defaults. No app data is deleted, but you'll have to pick your default browser and similar again.

It's a long shot for the memory bug, but it clears out odd settings that pile up over years of updates. The same screen has Reset Mobile Network Settings, which the Pixel team also mentioned. I explain what each reset does in my Wi-Fi Calling fix guide.

Step 8: Limit background processes as a stopgap

Try this if the phone is genuinely hard to use. One commenter on the issue tracker said capping background processes at four "instantly stopped the lagging". Fewer cached apps means less memory pressure, which is exactly what the bug feeds on.

1. Turn on Developer options as in Step 5.
2. Go to Settings > System > Developer options and scroll to the Apps section.
3. Tap Background process limit and pick At most 4 processes.

Know the trade-offs. Android's developer docs describe it as a testing option that caps how many processes run in the background. Apps will reload more often, and music, fitness or messaging apps may act up in the background, so make sure notifications still arrive. The same commenter said it wasn't a permanent fix, so check the setting after each restart. Set it back to Standard limit once the fix arrives.

Step 9: Get the fix early through the Android Beta

Google released the actual fix on 16 October in Android 17 QPR2 Beta 7.1, build CP41.260831.019 (9to5Google, Android Authority). On 21 October a Google employee confirmed on the tracker that the issue "has been resolved in the Beta 7.1 release".

To join, sign in at google.com/android/beta with the account on your phone, enroll your device and check Settings > System > Software updates. Google's QPR2 download page says enrolling usually doesn't need a wipe, but back up anyway. The beta covers the Pixel 6a and newer.

Here's the catch. Leave the beta before the stable release and your phone gets wiped. The clean way out is to wait for QPR2 stable, install it, then opt out before the next beta arrives. If you're happy to stay on the beta until then, it's a reasonable move. If you depend on banking apps, a work profile or anything fussy about pre-release software, think twice.

Step 10: Factory reset only as a last resort

"Just factory reset it" is the first reply many people get, and it's in Google's general slow-phone advice too. For this bug, though, a reset doesn't change the kernel code behind it. A fresh phone may feel quicker at first because fewer apps are running, but expect it to slide back as you reinstall everything.

If you've tried everything above and have problems even in safe mode that don't look like freezes under load, a reset may still be worth it. Back up, then use Settings > System > Reset options > Erase all data (factory reset). For the plain QPR1 bug, the update is the better bet.

Check your alarms after the update

This isn't widespread, but it's worth thirty seconds. In a busy r/GooglePixel thread about the September update, a Pixel 8a owner said the updated Clock app "turned off all my alarms so I was late for work." That's the only report of it I've found for this update, so it may be a one-off. Checking costs nothing:

• Open Clock and look at the Alarm tab. Make sure each recurring alarm is still switched on. Google's Clock help says that one switch turns all of an alarm's repeats on or off.
• Check the sound. If the ringtone is silent and vibration is off, Google says the alarm won't go off.
• Space out back-to-back alarms. Alarms set too close together can cancel the first one. Google suggests leaving 5 minutes between them.
• Check your modes. Under Settings > Modes, open any bedtime or Do Not Disturb mode and make sure alarms are allowed through.
• Update Clock from the Play Store if an update is waiting.

When will the fix reach stable Pixels?

Google hasn't given a date. Android Authority expects QPR2 stable "later this year", and 9to5Google has pointed to December. GrapheneOS said early on that December "wouldn't be a surprise". A backport to the November patch would be the best case, but there's no sign of one.

Pixel 6 and 6 Pro owners have a harder time. Their five years of updates, counted from the US launch in October 2021, are ending, and neither phone is on the QPR2 beta list. They may never get the fix. If that's you, Steps 2, 4 and 8 are your main tools.

When the update lands, check the notes for issue 571186734 or a mention of stuttering, install it, restart, and undo any Developer options changes. If you block ads with Private DNS, my Private DNS guide shows how to check it's still working after an update.

FAQ

Why is my Pixel so slow after the September 2026 update?

Most likely it's the Android 17 QPR1 kernel regression that causes stutter and freezes when memory runs low. Google tracks it as issue 571186734 and fixed it in QPR2 Beta 7.1. Launcher cache problems and low storage look similar, so try Steps 2 and 3 first.

Did the October 2026 Pixel update fix the lag?

No. The October patch fixed a keyboard bug, a VoIP ringtone problem and a photo orientation glitch. Plenty of owners on the tracker say the lag carried on after installing it.

Can I roll back to the version before QPR1?

Not from Settings. Pixels have no uninstall option for system updates, and installing an older build means wiping the phone. Joining the beta or waiting for the stable fix is more practical for most people.

Is it safe to join the Android 17 QPR2 beta to fix lag?

Mostly, but it's pre-release software. Joining usually doesn't wipe the phone. Leaving early does, unless you wait for QPR2 stable, install it, and opt out before the next beta. Back up before you enroll.

Does clearing Pixel Launcher storage delete anything?

It resets your home screen layout, widgets and shortcuts. Your apps, photos and messages aren't touched. Clearing the cache alone removes nothing you'd notice.

Still lagging?

Leave a comment with your Pixel model, the build number from Settings > About phone, how much storage is free, and which steps you've tried. Mention whether it lags in safe mode too, because that tells us whether it's the system or an app. If you can, add a bug report to issue 571186734. That helps Google far more than another "+1".