Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Level 1

41 points

IPad Pro screen unresponsive at times

Hi there,

since one or two weeks, my iPad Pro 10.5” in unspecific circumstances sputters in accepting touchscreen inputs, be it screen keybord or handwriting or sketching or whatever. In these cases

you need more than one stroke to shift screen,
you have to press a screen key more than once to get the respective charakter,
the line you’re sketching is broken in short strokes an dots (instead of a continous line),
defining a textblock by dragging the start or end node with you fingertip, stopps arbitrarily,
ecc. in any similar occasion.

These effects don’t depend on a specific app and appear also after a reset of the iPad. I noticed them the first time about 2 weeks ago (maybe little less) – certainly they didn’t exist before. I got my new iPad Pro 10.5“ in May, 2017.

Unfortunately, I did’t exactly catch the point of time that this effects started; in my opinion it’s not before the last iOS update. (I’m using the most recent one.)

Is there anybody why encountered similar problems?

Thanks in advance!

Message was edited by: Tastenolm

iPad Pro Wi-Fi, iOS 10.3.2, 10.5 "

Posted on Nov 17, 2017 11:53 AM

Best reply

Tastenolm Author

Level 1

41 points

Posted on Nov 18, 2017 12:07 PM

Hi jeremy_v!

I really appreciate your suggestions, and I did in fact a reset (as I wrote above).

But to setup my iPad from the scratch in my eyes is a rather generic one. I‘m really not going to follow it without any hypothesis or diagnosis regarding the underlying causes. Because doing so, would cost me a complete weekend. With minor prospects of success.

(Moreover, I‘m a bit allergical against this standard answer, since a couple of the guys at the Genius Bar at the Apple Shop suggested me, two months ago in an other case, to follow the same procedure, without the faintest attempt to examine my problem more deeply. They simply tried to fob me off.)

What I want to understand is: what could cause the described effects: Could it be due to an overload in network operations? May it be a hardware defect?