[zxczxc]

Originally Posted by lucida

Try this. the first /dev/input/eventX is the OTG device(not kindle), then a list of button keycode and coordinates of point.

	kindle-evdev /dev/input/eventX btn1:x1,y1 btn2:x2,y2....

You can start by running

     kindle-evdev /dev/input/eventX  1:1,1

from ssh/kterml, check the output to get keycode.

Thanks for your help! Nice code!

Although why do this every minute?
lipc-set-prop com.lab126.powerd -i touchScreenSaverTimeout 1
Any reason why not every button press, like what would happen every real screen touch?

(In the spoiler are my mistakes, feel free to ignore, I this understand this stuff more now!)

Spoiler:

Ok I am trying to do this, I plugged in a usb keyboard (actually little presenter remote control, it just sends left+right/pageup/pagedown) - yet when I type 'kindle-evdev /dev/input/eventX 1:1,1' I see no output when I press buttons. You say the first eventX is my device, so that would be event0?

In /dev/mnt/ - withouth the usb inserted I see:
by-path, event0, event1, mice, uinput


When the usb is inserted I see:
by-id, by-path, event0, event1, event2, event3, event4, mice, mouse0, uinput


Any advice? I'm not great at unix stuff sorry, I'm happy to learn though.
Thanks

-edit. Ok, within 'by-id' I see 4 devices, this usb thing isn't only being recognized as a keyboard then... strange, it doesn't have any mouse functions but maybe the firmware etc inside it does, and the creators were a little lazy.
So, I try all devices I see:
./kindle-evdev /dev/input/by-id/usb-8ea3_Wireless_Receiver-event-if01 1:1,1
./kindle-evdev /dev/input/by-id/usb-8ea3_Wireless_Receiver-event-kbd 1:1,1
./kindle-evdev /dev/input/by-id/usb-8ea3_Wireless_Receiver-event-mouse 1:1,1
./kindle-evdev /dev/input/by-id/usb-8ea3_Wireless_Receiver-mouse 1:1,1

but when I press buttons on the device I get no output on the kindle...

I guess I misunderstood the aim of this program.

I thought I give it an input device as an argument, and it would output the codes of the buttons I press... but I'm not so sure... ha

I think I understand,...
./kindle-evdev /dev/input/by-id/example buttoncode1:X,Y

When I run it and leave it running in the background, it will tap the screen at X,Y, each time I press a button that has buttoncode1.

I will look what codes correspond to what keyboard keys.

After rmmod mousedev, the keys are being read properly now, no problems there, before it was intermittent at best.

My volume buttons are being recognized fine as codes 114-115 as they should.
But they are only recognized on event3, whilst all the other keys are being recognized on event2... ha.

- lucida, your mouseturn executable is just a altered version of kindle-evdev?
or something much different? I imagine it is very similar, but I can't see the source code of mouseturn, so I'm asking

Thanks for all the information in here everyone, soon it will start to get much colder and remote page turning will be appreciated even more! (hands under the blanket etc)