I have an iPhone 6 Plus. Approximately 24 hours after updating to IOS 10.0.2, the screen stopped responding to the point that the device was unusable. I experienced:
- could not double-click and swipe away running apps
- could not double-click and select/switch to a running app
- could not tap and start any app
- could not type actions/content into any app (play voicemail, select different tabs, enter text, etc).
...obviously no longer a "touch-screen device" when it got to that point. I restarted the device many times (press and hold Home + Lock buttons), was able to use Touch ID to unlock, and on some occasions able to get screen response back for only a few strokes/taps. After that it would become unresponsive and I had to restart again. After restarting many, many times...I was no longer able to do ANYthing via screen contact. As a matter of fact, when I was prompted to enter my PIN manually (as required after restart) -> I touched a number on the number pad and saw a different number flash briefly...six numbers typed in correctly accompanied by six incorrect numbers flashing = "incorrect PIN". After trying that and verifying the same behavior occurred a couple more times, it became obvious that I would be locking my account or wiping the device inadvertently if I persisted trying to enter my PIN to unlock the device. I left the device idle for about 2 hours, then connected to USB/PC and opened iTunes which recognized the device ("need to enter a PIN" message in iTunes). I then tried entering my PIN again and it worked. I immediately backed up my iPhone and retired it for the evening. This morning the device worked normally like nothing had ever happened!! I used the device all day with no indication of any issues. This evening around 6PM EST: same issue again, frequent periods of no screen response. I am convinced this is an IOS 10.0.2 issue. I [normally] use the device heavily all day/night...every day (I work on a 24x7 Operations team for a multi-national and use all manner of communication/scheduling/apps/etc on this thing). I am now waiting for 10.0.3 (or whatever > 10.0.2)...hypothetically containing the fix for this...