View Single Post
Old 12-09-2018, 04:05 PM   #293
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@baskerville: Hmm, not quite sure I understood the "image" question? That was the output from hexdump -x /dev/input/event1 after a single tap in the top-left corner (i.e., Nickel's hamburger menu), mainly so you'd have an idea of what ABS_MT_POSITION_X & ABS_MT_POSITION_Y looked like (0x35 & 0x36, respectively, third column from the right, actual coordinates in the next column).

Just for my sanity, I just checked through strace, and the ioctl pair (PUT_V/GET_F) do get fired, so that does indeed look like the device is messing with you . (I did not decode the content, though, but I'm assuming it's correct, since that works when getting back to the FM).

EDIT: And yes, when it works (f.g., going from 270 to 0, one after the other), everything matches your Glo HD example .

EDITē: Err, my bad, that holds for the fb, NOT the touch axis . My top-left corner touch example is at (61, 1026).

Last edited by NiLuJe; 12-09-2018 at 05:22 PM.
NiLuJe is offline   Reply With Quote