Android 17 Is Breaking Touchscreens on Pixel Phones — Here's Everything You Need to Know
Google's latest major operating system update, Android 17, has officially begun rolling out to Pixel devices — and while a new OS release is usually cause for excitement, early adopters are discovering a deeply frustrating problem lurking beneath the surface. A widespread touchscreen bug is causing significant disruption across the Pixel lineup, with users reporting everything from ignored taps to completely reversed scrolling behavior. If your Pixel has been acting strangely since updating, you are far from alone.
What Exactly Is the Android 17 Touchscreen Bug?
At its core, the issue comes down to the phone misinterpreting — or entirely ignoring — touch inputs. Users who have upgraded to Android 17 are reporting several distinct symptoms that make day-to-day use a genuine challenge.
- Ignored taps: The phone simply fails to register a tap on the screen, forcing users to press multiple times to get a response.
- Dead zones: Certain areas of the display become completely unresponsive, regardless of how firmly or frequently they are touched.
- Reversed scrolling: Perhaps the most disorienting symptom, swiping upward — the universal gesture for scrolling down through content — causes the page to jump back to the very top instead.
These aren't subtle quirks. Reversed scrolling and unresponsive screen zones strike at the most fundamental interaction a smartphone user has with their device. Unlike a connectivity bug that can be sidestepped by switching from Wi-Fi to mobile data, a broken touchscreen has no easy workaround — your thumb is your only input method, and when that stops working reliably, the entire phone becomes difficult to use.
Reports of this behavior surfaced quickly on Reddit after the Android 17 stable rollout began, and were subsequently picked up and confirmed by Android Authority. The fact that multiple independent users across different devices and regions described the same symptoms makes it clear this is a systemic software issue, not an isolated hardware fault.
Which Pixel Devices Are Affected?
One of the most concerning aspects of this bug is how broadly it has spread across Google's own hardware lineup. Based on reports filed in Google's official IssueTracker and corroborated by Reddit threads, the Android 17 touchscreen bug is not limited to a single device generation.
The following Pixel series have all been reported as affected:
- Pixel 10 series
- Pixel 9 series
- Pixel 8 series
- Pixel 7 series
This means the bug spans Google's most current flagship devices all the way back to the Pixel 7, which remains widely used. It also doesn't appear to be app-specific. Users describe experiencing the reversed inputs and unresponsive zones throughout the system UI — on the home screen, in the app drawer, inside native Google apps, and within third-party applications alike. The problem lives at the OS level, not within any individual app.
Is This the Only Android 17 Bug?
Unfortunately, no. The touchscreen problem is the most disruptive issue to emerge from the Android 17 rollout so far, but it is not the only one. Early adopters have also documented a 5G connectivity glitch that causes some devices to lose or struggle to maintain a 5G signal, as well as a work-profile bug that causes home screen widgets to disappear entirely for users who rely on Android's work profile feature for separating personal and professional apps.
It is worth noting that some degree of instability following a major OS upgrade is not unusual. Android 17 represents a significant leap, and large-scale rollouts invariably surface edge cases that internal testing did not fully catch. What makes the touchscreen issue stand out, however, is its severity. A widget disappearing or a 5G signal dropping is inconvenient. A touchscreen that fights against you every time you try to scroll or tap makes the phone nearly impossible to use normally.
What Is Google Doing About It?
Google is aware of the issue. The problem has been officially logged in Google's IssueTracker, which is the company's public bug-reporting platform where engineers track and address reported problems. The official PixelCommunity account on Reddit has also weighed in, acknowledging the complaints and offering an initial suggested fix.
Google's recommended troubleshooting step is to clear the Pixel Launcher cache. Here is how to do it:
- Open Settings on your Pixel device.
- Tap Apps, then select See all apps.
- Scroll down and tap on Pixel Launcher.
- Tap Storage & cache.
- Tap Clear cache.
The results from this fix have been mixed at best. Some users report that clearing the Pixel Launcher cache temporarily relieves the symptoms or reduces their frequency, while others say their touchscreen behavior remains just as erratic as before. This suggests that while the cache workaround may help in some configurations, it is not a reliable or permanent solution for everyone affected.
What Should You Do Right Now?
If your Pixel device is experiencing touchscreen issues after updating to Android 17, the cache-clearing method described above is worth attempting as a first step, even if the results are not guaranteed. Beyond that, filing a report directly through Google's IssueTracker helps the engineering team understand the full scope of the problem and can accelerate the development of a proper patch.
You can also watch the official PixelCommunity subreddit and Google's IssueTracker page for updates. Google has a reasonable track record of pushing targeted bug-fix updates relatively quickly when a high-visibility issue gains traction — and a broken touchscreen affecting four full device generations is about as high-visibility as bugs get.
The Bottom Line
Android 17 is off to a bumpy start for Pixel owners. The touchscreen bug — with its dead zones, unresponsive taps, and reversed scrolling — is one of the more severe launch issues to accompany a major Android update in recent memory, precisely because it undermines the most basic way people interact with their phones. Google is aware and has offered an initial workaround, but a comprehensive software fix has not yet arrived. For now, patience and the cache-clearing step are the best tools available, and a proper patch will hopefully follow soon.