How to fix Android 17 QPR1's Pixel animation bugs

If your Pixel has started doing strange things when you swipe back to the home screen, you’re not imagining it. Since Google rolled out Android 17 QPR1 as part of the September Pixel Drop, a chunk of Pixel owners have been reporting that apps slide the wrong way, get stuck mid-transition, or just feel laggier than before. This guide walks through what’s actually happening, the workarounds that exist right now, and the fixes for the other glitches riding along with this update.

What you need, and how long this takes

You need a Pixel phone (Pixel 6 or newer) running Android 17 QPR1, and about 10 minutes for the quick fixes below. None of this requires a factory reset or a PC.

Google began rolling out Android 17 QPR1 with the September 2026 security patch on September 15, 2026. The update for Pixel 6 through Pixel 10a carries build number CP3A.260905.009. If you’ve got a Pixel 11, note that Google shipped it separate maintenance builds that week instead, so it may not be on QPR1 at all yet.

The update isn’t small. Google’s own release notes list 20 bug fixes and 115 security fixes bundled into it, including fixes for gaming crashes, Wi-Fi and Bluetooth problems, and system crashes during app installs on Pixel 10-series devices. The animation glitch is a side effect that slipped through, not an intentional change.

Step 1: confirm you’re actually on the buggy build

Before chasing fixes, check what you’re running.

Open Settings.
Scroll down and tap About phone.
Tap Android version or look for Build number.

If you see CP3A.260905.009 or a later build dated September 2026 or after, you’re on QPR1 and these steps apply. If your build string starts with something else entirely on a Pixel 11, you’re likely still waiting on QPR1 to land.

Step 2: switch to three-button navigation

The animation bug is most visible with gesture navigation. On Reddit’s Pixel forum, one user described the problem on a Pixel 10 Pro XL: returning to the launcher from an app skips the usual downward animation and instead slides into the recent apps screen before sliding away to the right, and the app icon sometimes freezes on screen while Recents opens behind it. A Pixel 10a owner reported the same thing happening on the way back to the home screen, and traced it to apps launched from the app drawer rather than the home screen, often while the keyboard was open.

There’s no permanent fix yet, but switching navigation modes has worked for some people:

Open Settings.
Tap System (on some phones this is under Display or Display and touch).
Tap Navigation mode.
Select 3-button navigation.

This trades the gesture bar for on-screen back, home, and recents buttons, which sidesteps the broken swipe animation entirely. It’s not elegant, but it works until Google ships a proper patch.

Step 3: tone down the animations yourself

If you’d rather keep gestures, reducing animation speed system-wide can mask some of the stutter, even if it doesn’t fix the underlying bug.

Open Settings, tap About phone, then tap Build number seven times to unlock Developer options.
Go back to Settings and tap System, then Developer options.
Scroll to the Drawing section and find Window animation scale, Transition animation scale, and Animator duration scale.
Set each to 0.5x. You can turn them off completely, but that makes the whole interface feel abrupt.

These are the same three settings Android has used since API level 17 to control window, transition, and animator speed, and they default to 1x on every Pixel. Halving them won’t fix a broken animation sequence, but it shortens how long you’re stuck looking at it.

Step 4: clear the System UI cache

If apps are freezing mid-transition rather than just playing the wrong animation, a stuck cache is a reasonable suspect.

Open Settings, tap Apps, then See all apps.
Tap the three-dot menu and enable Show system.
Find and tap System UI.
Tap Storage & cache, then Clear cache.

Don’t clear data here, only cache. Clearing data on System UI can reset quick settings tiles and some launcher preferences. Restart the phone afterward.

Common Android 17 QPR1 problems and fixes

The animation bug isn’t travelling alone. Here’s what else has turned up since the update, and what to try for each.

Symptom	Who’s reporting it	What to try
Wrong slide animation returning to home or Recents	Mostly Pixel 10 series	Switch to 3-button navigation, or reduce animation scales
App icon frozen on screen during transition	Pixel 10 Pro XL, Pixel 10a	Launch apps from the home screen instead of the app drawer where possible
General lag, especially after heavy use	Pixel 9 and Pixel 10a owners, linked to 8GB RAM models under memory pressure	Close background apps, free up storage, restart the phone weekly
Notifications or Quick Settings toggles unresponsive	Spread across Pixel 6 through Pixel 10, including A-series phones	No confirmed fix yet; restart the device and avoid reinstalling apps as a workaround
Unlock animation stays on screen too long	Pixel 10 Pro	Restart the phone; report via Pixel Feedback if it persists

How widespread is this, actually

It’s hard to tell from Reddit threads alone how many of the millions of Pixel phones in circulation are affected. One outlet, Wirefly, ran an informal reader poll after the rollout and found a third of respondents hadn’t noticed anything new, while the rest were split across display glitches, unexpected UI behavior, connectivity failures, performance issues, and other problems.

Pixel owners reporting problems after Android 17 QPR1 (reader poll)

That’s not a scientific sample, it’s a self-selected group of people reading an article about Pixel bugs. But it does line up with what’s showing up across Reddit and other forums: a minority of very vocal, very annoyed users, and a majority who updated and noticed nothing different.

Step 5: report it and wait for the real fix

Google has acknowledged the problem. The official Pixel account on Reddit has reached out to people who posted about the animation bug to gather more detail, which suggests it’s gathering the data it needs for a patch rather than treating this as unreproducible noise.

If you’re hit by this, file a report through the Pixel Feedback app (Settings > search for Feedback, or long-press the power and volume-down buttons to trigger it mid-bug) so Google has your device model and steps to reproduce attached to the report. Screen recordings help more than screenshots here, since the bug is about motion, not a static state.

Realistically, a fix will land in a future monthly update or the next Feature Drop rather than an emergency patch. Google’s QPR cycle runs quarterly, with monthly security updates in between, so the earliest sensible target is the next scheduled Pixel update rather than anything out of band.

What this means for you

If the animation glitch is mildly annoying, the animation scale tweak in Developer options is the least disruptive fix and takes two minutes. If it’s actively getting in your way, especially the frozen app icon during Recents, switch to 3-button navigation until Google patches it; you can always switch back later with the same menu path. Hold off on a factory reset. None of the reports here point to a corrupted install, and wiping your phone won’t fix a bug that’s baked into the build itself. If you’re on a Pixel 9 or 10a and the complaint is lag rather than animations, check your free storage and background app count before blaming the update entirely, since those models are the ones flagged for memory pressure. And if you’re still deciding whether to install QPR1 at all, there’s no indication it’s being pulled, so updating is still the right call for the security fixes alone. Just expect the home screen transition to look a little off until the next patch.

How to fix Android 17 QPR1’s Pixel animation bugs