09-10-2020, 12:37 PM
(This post was last modified: 09-10-2020, 04:49 PM by quipacorn.
Edit Reason: updated
)
Hi all,
Received my pinetab today and noticed on first boot the top row of the onscreen keyboard was unresponsive and I was unable to enter most things for the setup. Once I got to the desktop I verified that there is a strip that runs the full width that doesn't respond to any touch input. The plastic screen protector also came with a bunch of scratches and fingerprints, removing it did help touch sensitivity somewhat on the rest of the screen but that strip was still dead. On top of that, the keyboard case only a few keys work. I verified with an external keyboard that it can receive those inputs.
I'm leaning towards a hardware problem (which is a bummer given how long the wait was) but wanted to check to see if anyone else encountered similar and if there's an easy solution. Thanks.
Edit 1: Tested multiple operating systems, problem persists. Screen rotations don't change where the bad strip is. Gotta be a hardware issue, went ahead and submitted a ticket. Am sad.
Edit 2: Attached image to show what I'm talking about. Drawn horizontal lines with gimp roughly covering the possible y-axis points when in landscape mode. Turns out, there's actually two dead strips. When trying to draw in between those two white spots on the bottom input just goes above or below. Sometimes it would cross over due to momentum and gimp approximating things but it's impossible for anything to register inside those bounds
Received my pinetab today and noticed on first boot the top row of the onscreen keyboard was unresponsive and I was unable to enter most things for the setup. Once I got to the desktop I verified that there is a strip that runs the full width that doesn't respond to any touch input. The plastic screen protector also came with a bunch of scratches and fingerprints, removing it did help touch sensitivity somewhat on the rest of the screen but that strip was still dead. On top of that, the keyboard case only a few keys work. I verified with an external keyboard that it can receive those inputs.
I'm leaning towards a hardware problem (which is a bummer given how long the wait was) but wanted to check to see if anyone else encountered similar and if there's an easy solution. Thanks.
Edit 1: Tested multiple operating systems, problem persists. Screen rotations don't change where the bad strip is. Gotta be a hardware issue, went ahead and submitted a ticket. Am sad.
Edit 2: Attached image to show what I'm talking about. Drawn horizontal lines with gimp roughly covering the possible y-axis points when in landscape mode. Turns out, there's actually two dead strips. When trying to draw in between those two white spots on the bottom input just goes above or below. Sometimes it would cross over due to momentum and gimp approximating things but it's impossible for anything to register inside those bounds