FYI ony: from the command: less /proc/bus/input/devices
Product ID = a001 Vendor id=0eef Version 0210
name:="eGalax_eMPIA technology inc. PCAP Multitouch controller"
from the command: uname - r returns: 3.0.1-android-x86-asus-laptop+"
Specifically, here is the problem I see.... If you use a mouse in the
GUI to go to "apps->developer tools->pointer location" the touchscreen
works there. Touch, multi-touch and swipe all works.
At first I thought it was a driver issue, but the fact the touchpad
works in the developer "pointer location" tool seems to indicate the
driver is fine and the problem is more with interpreting the
touchscreen input from the driver into the Andriod GUI rather than the
touchscreen inputing into the driver. (from the CLI, the command
"getinput" function also shows it can read in the touch events from /
dev/inputs/event14)
I have not been able to fully understand the way the .IDC files and
the "handlers" entries work, but I noticed a "fake touchpad" and the
mouse entries that has an handler entry "mouse" or "mouse1". The
touchpad only has a handler of "event14 kbd"
Just my observations and wondering if anyone else has ever seen this
behavior
Thanks in advance,
Toby
I have the same issues with the touchscreen. I have copied the
qwerty.idc file to Vendor_0eef_Product_0001.idc but no results.
Pointer location in dev tools does not show any activity; the touchpad
on the keyboard works but pointer location shows no change in X and Y
axis, not even for the working touchpad.
Driver location: http://home.eeti.com.tw/web20/eGalaxTouchDriver/linuxDriver.htm
Many thanks for helping getting this touchscreen to work!
Mike