Google · touchscreen

Google Pixel Tablet screen or touch input is not working correctly

Google Pixel Tablet screen or touch input is not working correctly: one app/region, moisture, protector/case, charger interference and display hardware should be separated. Scoped to GA04750/GA04751 series.

A Pixel Tablet with a touch fault should follow Google's touch article, written for Pixel phones but generic Android: take off any case or screen protector, remove gloves and stickers, clean the screen, update and try gesture navigation, and note that a fault in one app is for that app's developer. The tablet's 10.95-inch panel is large, so test all four corners as well as the middle, and try it both docked and undocked. Google's FAQ says the tablet works with third-party USI 2.0 styluses, so an unfamiliar stylus can also cause odd input. A cracked panel is a repair: iFixit lists the screen at $200 as a part.

Differential

Likely causes of “Google Pixel Tablet screen or touch input is not working correctly”, and how to tell them apart

  1. 1

    A case or screen protector in the way

    What separates it Touch is patchy near the edges of the screen while the middle of the display responds normally

    How to confirm Google says to try removing the case or protector and test

  2. 2

    Gloves, stickers or a dirty screen

    What separates it Touch is missed or misfires, with taps registering in the wrong place on the screen

    How to confirm Remove gloves and stickers and clean the screen

  3. 3

    A stylus or accessory

    What separates it There is odd input while a third party stylus is nearby because of a stylus or accessory

    How to confirm Google's FAQ lists USI 2.0 styluses as supported; test without one

  4. 4

    A software fault

    What separates it Touch fails or behaves oddly right after an app was updated on the phone

    How to confirm Restart, check for updates and try Safe mode

  5. 5

    A cracked or damaged panel

    What separates it Dead patches or lines on the display do not clear after a restart or a screen clean

    How to confirm Have the screen replaced; iFixit lists $200 as a part

Before you touch a setting

Record this first — changing settings destroys the evidence

  • Pixel Tablet, the Android version and whether the fault is in one app or everywhere
  • Whether it is one area, an edge or the whole screen
  • Whether a case, protector, stylus or sticker is on
  • Whether the screen is cracked or has been wet

Try in this order

0 of 6 completed
  1. Check the screen

    Reversible

    Remove the case, protector, gloves and stickers, and clean the screen with a soft dry cloth, then test touch again.

  2. Check for updates

    Reversible

    Open Settings, System, Software updates and install anything waiting, then open the Play Store and update your apps too.

  3. Test all four corners

    Reversible

    Test all four corners, by drawing across the whole screen to find where the fault is.

  4. Try Safe mode

    Reversible

    If touch works in Safe mode, a downloaded app is the cause, so remove recent apps one at a time and test after each.

  5. Undock and retest

    Reversible

    Undock and retest, by testing both docked and undocked to rule out the dock or a case.

  6. Book a repair

    Reversible

    Book a repair, and if it persists, a repairer can replace the screen, and then test again to see whether it helped.

Model-specific

What is true of this model and not of its siblings

Screen
A 10.95-inch panel with a front-facing 8 MP camera, Tensor G2 and 8 GB of RAM, per Wikipedia and iFixit's screen listing.
Care rules
Google's FAQ: not water resistant, not dustproof, and liquid damage voids the warranty. The Pixel Tablet Case does not need to be removed to dock.
Tools and supplies
A dry towel or soft cloth, clear tape for a cracked screen and a flashlight to see cracks. Do not use a blade or heat on the panel.
Repair cost
iFixit parts per 9to5Google: screen $200 (with the front camera), battery $59.99, USB-C port $24.99. A repairer's labor is extra.

Stop boundary

When this stops being a self-service repair

  • !If touch is faulty after removing accessories, a restart and Safe mode, contact Google or a repairer
  • !If the screen is cracked or has lines, do not delay a repair
  • !If the fault is in one app only, contact the app developer, as Google advises

Evidence ledger

Sources behind this answer

Exact questions

Common questions

Does a screen protector need to be USI-compatible?+

Google's FAQ mentions a Made for Google screen protector among accessories. Whatever you use, remove it as a test if touch is patchy, as Google's touch article advises.

Does screen brightness affect touch?+

No. Brightness changes what you see, not how touch is read. If the screen is too dim to see, raise brightness before testing touch.

What if touch works on the lock screen but not in an app?+

That points to the app. Google's touch article says a fault in one app is for the app's developer; update or reinstall the app and test again.

Could the tablet's size make my grip trigger touches?+

A hand resting near the edge can trigger touches on a large screen. Google's guides give no figure, so test with the tablet on a table.

Should I try a different charger for touch faults?+

If touch fails only while charging, try a different cable and adapter; a poor charger can cause noisy input on some devices. Google's charging article recommends 15W USB Power Delivery.

Can I keep my screen protector on?+

Google says to try removing it and warns you may not be able to put it on again. Test with it off to see whether it is the cause.

Does the tablet support a stylus?+

Google's FAQ says it is compatible with third-party USI 2.0-compliant styluses and Bluetooth keyboards.

Is the screen water resistant?+

No. Google's FAQ says the Pixel Tablet is not water resistant or dustproof, and liquid damage voids the warranty.

Can I use the tablet while waiting for repair?+

If the screen is cracked, tape it and avoid pressure. Back up first in case touch fails completely.

Does the dock affect touch?+

Testing docked and undocked simply rules it out.

Wrong device or version?

Match the path before repeating the steps.

Match another device