Hi, I'm using a new eGalax touchscreen on our own android version running 
on a beagleboard-xM.

I got the driver working and the screen is registered by android:

I/EventHub( 2098): Opening device: /dev/input/touchscreen0 
> V/EventHub( 2098): Getting keys...
> V/EventHub( 2098): Getting absolute controllers...
> V/EventHub( 2098): multi-touch controller detected...
> I/EventHub( 2098): New device: path=/dev/input/touchscreen0 
> name=eGalaxTouch Virtual Device for Multi id=0x20001 (of 0x2) index=2 fd=79 
> classes=0x14
> V/EventHub( 2098): Adding device /dev/input/touchscreen0 0x1ee6178 at 2, 
> id = 1, classes = 0x14
> I/EventHub( 2098): Opening device: /dev/input/event4 
> V/EventHub( 2098): Getting keys...
> V/EventHub( 2098): Getting absolute controllers...
> V/EventHub( 2098): multi-touch controller detected...
> I/EventHub( 2098): New device: path=/dev/input/event4 name=eGalaxTouch 
> Virtual Device for Multi id=0x10002 (of 0x3) index=3 fd=80 classes=0x14
> V/EventHub( 2098): Adding device /dev/input/event4 0x1ee6d40 at 3, id = 2, 
> classes = 0x14


...

V/EventHub( 2098): Reporting device opened: id=0x10002, 
> name=/dev/input/event4
> D/InputReader( 2098): Input event: device=0x10002 type=0x10000000 
> scancode=0 keycode=0 value=0
> I/InputReader( 2098): Device added: id=0x10002, name=eGalaxTouch Virtual 
> Device for Multi, sources=00001002
> V/EventHub( 2098): Reporting device opened: id=0x20001, 
> name=/dev/input/touchscreen0
> D/InputReader( 2098): Input event: device=0x20001 type=0x10000000 
> scancode=0 keycode=0 value=0
> I/InputReader( 2098): Device added: id=0x20001, name=eGalaxTouch Virtual 
> Device for Multi, sources=00001002


/proc/bus/input/devices contains these entries (which are correct according 
to the guide from EETI

I: Bus=0003 Vendor=0eef Product=7458 Version=0210
> N: Name="eGalax Inc. eGalaxTouch EXC7200-7458"
> P: Phys=usb-ehci-omap.0-2.3/input0
> S: 
> Sysfs=/devices/platform/ehci-omap.0/usb1/1-2/1-2.3/1-2.3:1.0/input/input2
> U: Uniq=
> H: Handlers=
> B: EV=1b
> B: KEY=421 0 30001 0 0 0 0 0 0 0 0
> B: ABS=100 3f
> B: MSC=10
> I: Bus=0006 Vendor=0eef Product=0020 Version=0001
> N: Name="eGalaxTouch Virtual Device for Multi"
> P: Phys=
> S: Sysfs=/devices/virtual/input/input5
> U: Uniq=
> H: Handlers=event4 
> B: EV=b
> B: KEY=400 0 0 0 0 0 0 0 0 0 0
> B: ABS=6608000 1000003
> I: Bus=0006 Vendor=0eef Product=0010 Version=0001
> N: Name="eGalaxTouch Virtual Device for Single"
> P: Phys=
> S: Sysfs=/devices/virtual/input/input6
> U: Uniq=
> H: Handlers=event5 
> B: EV=b
> B: KEY=30000 0 0 0 0 0 0 0 0
> B: ABS=3


I also created a basic idc file:

device.internal = 1
> touch.deviceType = touchScreen


When I touch the screen logcat outputs tons of these:

D/InputReader( 2098): Input event: device=0x10002 type=0x3 scancode=0 
> keycode=0 value=1629
> V/EventHub( 2098): /dev/input/touchscreen0 got: t0=150, t1=178436, type=3, 
> code=1, v=1798
> D/InputReader( 2098): Input event: device=0x10001 type=0x3 scancode=1 
> keycode=1 value=1798
> V/EventHub( 2098): /dev/input/event4 got: t0=150, t1=178436, type=3, 
> code=1, v=1798
> D/InputReader( 2098): Input event: device=0x10002 type=0x3 scancode=1 
> keycode=1 value=1798
> V/EventHub( 2098): /dev/input/touchscreen0 got: t0=150, t1=178741, type=0, 
> code=0, v=0
> D/InputReader( 2098): Input event: device=0x10001 type=0x0 scancode=0 
> keycode=0 value=0
> V/EventHub( 2098): /dev/input/event4 got: t0=150, t1=178741, type=0, 
> code=0, v=0
> D/InputReader( 2098): Input event: device=0x10002 type=0x0 scancode=0 
> keycode=0 value=0
> V/EventHub( 2098): /dev/input/touchscreen0 got: t0=150, t1=183868, type=3, 
> code=54, v=1797
> D/InputReader( 2098): Input event: device=0x10001 type=0x3 scancode=54 
> keycode=54 value=1797
> V/EventHub( 2098): /dev/input/event4 got: t0=150, t1=183868, type=3, 
> code=54, v=1797
> D/InputReader( 2098): Input event: device=0x10002 type=0x3 scancode=54 
> keycode=54 value=1797
> V/EventHub( 2098): /dev/input/touchscreen0 got: t0=150, t1=184448, type=3, 
> code=1, v=1797
> D/InputReader( 2098): Input event: device=0x10001 type=0x3 scancode=1 
> keycode=1 value=1797
> V/EventHub( 2098): /dev/input/event4 got: t0=150, t1=184448, type=3, 
> code=1, v=1797
> D/InputReader( 2098): Input event: device=0x10002 type=0x3 scancode=1 
> keycode=1 value=1797
> V/EventHub( 2098): /dev/input/touchscreen0 got: t0=150, t1=184753, type=0, 
> code=0, v=0
> D/InputReader( 2098): Input event: device=0x10001 type=0x0 scancode=0 
> keycode=0 value=0
> V/EventHub( 2098): /dev/input/event4 got: t0=150, t1=184753, type=0, 
> code=0, v=0
> D/InputReader( 2098): Input event: device=0x10002 type=0x0 scancode=0 
> keycode=0 value=0
> V/EventHub( 2098): /dev/input/touchscreen0 got: t0=150, t1=186370, type=3, 
> code=57, v=-1
> D/InputReader( 2098): Input event: device=0x10001 type=0x3 scancode=57 
> keycode=57 value=-1
> V/EventHub( 2098): /dev/input/event4 got: t0=150, t1=186370, type=3, 
> code=57, v=-1
> D/InputReader( 2098): Input event: device=0x10002 type=0x3 scancode=57 
> keycode=57 value=-1
> V/EventHub( 2098): /dev/input/touchscreen0 got: t0=150, t1=186767, type=3, 
> code=58, v=0
> D/InputReader( 2098): Input event: device=0x10001 type=0x3 scancode=58 
> keycode=58 value=0
> V/EventHub( 2098): /dev/input/event4 got: t0=150, t1=186767, type=3, 
> code=58, v=0
> D/InputReader( 2098): Input event: device=0x10002 type=0x3 scancode=58 
> keycode=58 value=0



Sometimes there are this messages in between:

V/EventHub( 2098): /dev/input/touchscreen0 got: t0=150, t1=187103, type=1, 
> code=330, v=0
> V/EventHub( 2098): iev.code=330 keyCode=0 flags=0x00000000 err=-19
> D/InputReader( 2098): Input event: device=0x10001 type=0x1 scancode=330 
> keycode=0 value=0
> V/EventHub( 2098): /dev/input/event4 got: t0=150, t1=187103, type=1, 
> code=330, v=0
> V/EventHub( 2098): iev.code=330 keyCode=0 flags=0x00000000 err=-19


This seems all fine to me (but I am no linux pro), so I wonder why Android 
is not responding to the touch inputs. The Pointer Location app from the 
dev tools also shows no reaction.
Does anybody have an idea whats wrong here?

-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

Reply via email to