MobileRead Forums - View Single Post

cienanos · 03-20-2017, 09:58 PM

Hi, I'm having an issue with the digitizer on my N96ML and I wanted to see if it had affected anyone else.

Very often when I start up my reader, I'll find that it is not responsive to the stylus, and what's more, the reader will act as if the stylus is tapping on a point in the lower left corner of the screen. This will usually trigger the "Library" app to open. It's basically making the reader unusable because I can't rely on it to read something when I want to.

I have installed firmware 1.8.1, and it seems like it started after I did this, but not immediately after, so I'm not sure if it's responsible.

Assuming this is a hardware issue, do I have any chance of getting this fixed? I bought it new in the US from a wholesale seller on eBay -- it came with the warranty documentation, but from reading other posts it seems like that might be useless.

Is there anything I can do to resolve this issue?

Update: wiping data/cache didn't do anything

03-20-2017, 09:58 PM	#1
cienanos Junior Member Posts: 5 Karma: 10 Join Date: Mar 2017 Device: Boox N96ML	Issue with N96ML digitizer Hi, I'm having an issue with the digitizer on my N96ML and I wanted to see if it had affected anyone else. Very often when I start up my reader, I'll find that it is not responsive to the stylus, and what's more, the reader will act as if the stylus is tapping on a point in the lower left corner of the screen. This will usually trigger the "Library" app to open. It's basically making the reader unusable because I can't rely on it to read something when I want to. I have installed firmware 1.8.1, and it seems like it started after I did this, but not immediately after, so I'm not sure if it's responsible. Assuming this is a hardware issue, do I have any chance of getting this fixed? I bought it new in the US from a wholesale seller on eBay -- it came with the warranty documentation, but from reading other posts it seems like that might be useless. Is there anything I can do to resolve this issue? Update: wiping data/cache didn't do anything Last edited by cienanos; 03-20-2017 at 10:08 PM.