Pixel 9 Pro XL is not registering corner taps sometimes

The Pixel 9 Pro XL is one of the four Pixel 9 phones that Google unveiled last month. Now that the company has started shipping units in batches, some initial Pixel 9 Pro XL users have complained that the device is not registering taps, especially at the bottom-left corner of the screen.

The Pixel 9 Pro XL is reportedly plagued by unresponsive/inconsistent corner taps

Yesterday, some folks over at 9to5Google reported spotting multiple Reddit posts with complaints about the Pixel 9 Pro XL. Per the report, some users noticed an unusual pattern of some units not registering taps on the corner of the screen. Notably, the issue has precisely plagued the bottom-left corner of the smartphone’s screen.

Many users are reportedly facing this issue when trying to close Gboard. The button to close Gboard at the bottom-left corner of the screen is consistently troubling users. As you may know, the system button has a wide touch target. Therefore, tapping around it should close Gboard. However, it doesn’t seem to be the case for some users as they need to touch the icon directly.

9to5Google noticed the same issue with two of its Pixel 9 Pro XL units. Additionally, a Redditor even complained that taps work very occasionally, after trying 30 times or so. Unfortunately, the corner taps issue is not limited to just one or two units of the “Pro XL” model. In fact, the issue is widespread and troubling many users.

Users speculate the issue is the result of some software bug

While the exact cause of the issue is unknown, it is very likely a software issue. Some Reddit users have also pointed out the same and blamed the palm rejection feature for it. While rebooting the Pixel 9 Pro XL reportedly fixes the corner taps issue temporarily; there’s no permanent solution as of yet.

Worth noting that while investigating the issue, we came across a comment on one of the posts by the official Reddit account run by the Pixel Product Support team. So, it is safe to assume that Google is well aware of this issue and might be working on it. Therefore, we recommend you wait until the company pushes an update to resolve this issue.