Ok, I think I've figured out what is going on. When I plug the device in, it thinks there is both a keyboard and a mouse active. It's putting the mouse on event2, the volume buttons (brightness) on event3, and the keyboard (up/down/tab/enter) on event4. According to the KindleLazy doc it only reads event2 and event3.
I'm not sure why it's putting a keyboard on both event3 and event4. I tried changing the symlinks to redirect the things to event2/3 but that didn't work. Probably wouldn't last anyway between starts/stops.
Code:
[root@kindle by-path]# ls -la
drwxr-xr-x 2 root root 160 Apr 1 00:27 .
drwxr-xr-x 4 root root 240 Apr 1 00:27 ..
root 9 Apr 1 00:27 platform-fsl-ehci.0-usb-0:1:1.0-event-mouse -> ../event2
root 9 Apr 1 00:27 platform-fsl-ehci.0-usb-0:1:1.0-mouse -> ../mouse0
root 9 Apr 1 00:27 platform-fsl-ehci.0-usb-0:1:1.1-event-kbd -> ../event3
root 9 Apr 1 00:27 platform-fsl-ehci.0-usb-0:1:1.2-event-kbd -> ../event4
root 9 Jan 7 2000 platform-imx-i2c.0-platform-max77696-onkey.0-event -> ../event0
root 9 Apr 1 00:00 platform-imx-i2c.1-event -> ../event1
It looks like changing line 291 in kindlelazy.cpp from
Code:
eventfd2 = open("/dev/input/event2", O_RDONLY);
to
Code:
eventfd2 = open("/dev/input/event4", O_RDONLY);
would fix my issue?
Any ideas on why my device is using event3 and event4 for the keyboard and others are not? I assume others use event2 and event3.