r/chromeos Samsung Galaxy Chromebook 18h ago

Troubleshooting Touchscreen issue goes away in guest mode, but not fixed after powerwash?

Multitouch is unreliable for me but I found out that while logged into guest mode it works perfectly. So I presumed something on my user configuration was messed up but after a powerwash there was no change.

Any guidance? I tried removing all extensions, all chrome flags, fiddling with every setting I can.

Can I powerwash and get into the OS without logging into any account so I can try the purest state of the OS with no preloaded configurations?

Edit: Never mind, the issue is present immediately after powerwash before even signing in, but guest mode works fine. I don't think there's anything I can do to fix it.

1 Upvotes

6 comments sorted by

1

u/_jis_ Acer Chromebook 516 GE 16GB (CBG516-1H) | Stable 17h ago

If you haven't tried it yet, there is still one more powerful option left, perform a restore using this tool: https://chromewebstore.google.com/detail/chromebook-recovery-utili/pocpnlppkickgojjlmhdmidojbmbodfm

1

u/Sqwv Samsung Galaxy Chromebook 16h ago

Thanks for the suggestion. I just tried that and the issue is still present. Before that I also tried switching to Beta and Dev channels.

I already submitted feedback, but does anyone know if there a better/more efficient way to report this issue to Google?

1

u/_jis_ Acer Chromebook 516 GE 16GB (CBG516-1H) | Stable 15h ago

1

u/Sqwv Samsung Galaxy Chromebook 14h ago

Thanks again but still no change.

1

u/_jis_ Acer Chromebook 516 GE 16GB (CBG516-1H) | Stable 14h ago edited 13h ago

2

u/Sqwv Samsung Galaxy Chromebook 13h ago

Samsung Galaxy Chromebook (XE930QCA-K01US). With one finger the touchscreen works fine, but when two, three, or more fingers are on the screen, about 50% of the time it causes it to stop responding to any touches until I remove all fingers from the screen then it starts working again. When I switch to guest mode it doesn't have any issues, even tracking up to 10 fingers.

It really doesn't seem like a hardware issue at all. I'll check the links for clues though.