AnsweredAssumed Answered

Help with android Capsense

Question asked by Kobus Goosen on Jul 19, 2014
Latest reply on Aug 29, 2016 by Ashokkumar G P

I'm trying to get a 7" touchscreen working in android with an IMX6 (technexion edm). The touch IC is from pixcir, and a driver exists for it in newer kernels, but not the 3.0.X used for android. I copied the driver into my kernel and got it to work by sligthy modifying the module interface parts. Andoird now sees the input device, and seems to understand the input from it.

see my original post: Wandboard Discussion Forums • View topic - Help with i2c PCAP panel


There's one problem, when I move my finger over the display it moves a relative cursor, like moving with a mouse (except when I use a mouse the cursor, a circle, turns into a mouse pointer). The touches aren't registered at their absolute position on display.


I originally thought this might be due to the particular input events the driver registers, but this doesn't seem to be the case. I tried removing everything except ABS_MT_POSITION_X and ABS_MT_POSITION_Y, I also tried copying exactly what was done in the egalaxy and driver, where they register and report



ABS_MT_TRACKING_ID     (I left this out as my driver doesnt )




This does nothing except that when I run cat /proc/bus/input/devices it is reported as both an event device and a mouse...


I can confirm that the events being generated are in absolute coordinates. When I run getevent -lt /dev/input/event1 I get absolute x and y points that to go to roughly 0,0 in the top left corner, and roughly 1024,600 in the bottom left, which tells me that it probably doesnt need to be calibrated.


Does anyone know why the android system would not interpret these as absolute coordinates? the inly thing I can think is that its expecting a calibration file because the build I'm using originally worked with a resisitive display. However my andoird build does not appear to include tslib.


Any help would be appreciated.