eGalax resistive touchscreen support in honeycomb?

167 views
Skip to first unread message

Missel Richana

unread,
Nov 26, 2011, 6:35:10 PM11/26/11
to Android-x86
I have an Acer Aspire One that works great with the 3.2-eeepc version
installed. Unfortunately I've lately installed a eGalax resistive
touchscreen that doesn't register anything. Is there any way to have
it working in honeycomb? The usual methods from 2.2 don't seem to be
working.
Message has been deleted

Joseph Hayhoe

unread,
Nov 27, 2011, 1:23:31 AM11/27/11
to Android-x86
Do you have working wifi and Hardware acceleration with the 3.2-eeepc
build as well?

Missel Richana

unread,
Nov 27, 2011, 7:28:01 AM11/27/11
to Android-x86
Both wifi and hardware acceleration worked out of the box and looks
and works amazing. Only had some troubles with screen rotation but
seem to be resolved by disabling auto screen rotation.
On the other hand still no luck with the touch screen.
In /proc/bus/input/devices there's no entry for the touchscreen
In /system/usr/idc there is no entry of type
Vendor_..._Product.idc, only querty.idc and querty2.idc
modprobe hid-multitouch has no effect

dmesg only shows
usb 2-1: new low speed USB device number 2 using uhci_hcd
on connection
usb 2-1: USB disconnect , device number 2
on disconnect

Joseph Hayhoe

unread,
Nov 27, 2011, 11:39:47 AM11/27/11
to Android-x86
devices:

: Bus=0003 Vendor=0eef Product=0001 Version=0210
N: Name="eGalax Inc. USB TouchController"
P: Phys=usb-0000:00:1d.7-5.1/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5.1/1-5.1:1.0/
input/input6
U: Uniq=
H: Handlers=mouse0 event6
B: PROP=0
B: EV=1b
B: KEY=401 0 0 0 0 0 0 0 0 0 0
B: ABS=3
B: MSC=10

I: Bus=0003 Vendor=0eef Product=0001 Version=0210
N: Name="eGalax Inc. USB TouchController"
P: Phys=usb-0000:00:1d.7-5.1/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5.1/1-5.1:1.0/
input/input7
U: Uniq=
H: Handlers=mouse1 event7
B: PROP=0
B: EV=1b
B: KEY=30000 0 0 0 0 0 0 0 0
B: ABS=3
B: MSC=10

I: Bus=0003 Vendor=0eef Product=0001 Version=0210
N: Name="eGalax Inc. USB TouchController"
P: Phys=usb-0000:00:1d.7-5.1/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5.1/1-5.1:1.0/
input/input8
U: Uniq=
H: Handlers=event8
B: PROP=0
B: EV=1

I: Bus=0003 Vendor=0eef Product=0001 Version=0210
N: Name="eGalax Inc. USB TouchController"
P: Phys=usb-0000:00:1d.7-5.1/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5.1/1-5.1:1.0/
input/input9
U: Uniq=
H: Handlers=event9
B: PROP=0
B: EV=1

dmesg:

<6>[ 2.838015] input: eGalax Inc. USB TouchController as /devices/
pci0000:00/0000:00:1d.7/usb1/1-5/1-5.1/1-5.1:1.0/input/input6
<6>[ 2.841013] input: eGalax Inc. USB TouchController as /devices/
pci0000:00/0000:00:1d.7/usb1/1-5/1-5.1/1-5.1:1.0/input/input7
<6>[ 2.843928] input: eGalax Inc. USB TouchController as /devices/
pci0000:00/0000:00:1d.7/usb1/1-5/1-5.1/1-5.1:1.0/input/input8
<6>[ 2.846088] input: eGalax Inc. USB TouchController as /devices/
pci0000:00/0000:00:1d.7/usb1/1-5/1-5.1/1-5.1:1.0/input/input9
<6>[ 2.847699] generic-usb 0003:0EEF:0001.0001: input: USB HID
v2.10 Pointer [eGalax Inc. USB TouchController] on usb-0000:00:1d.
7-5.1/input0

Tried the methods linked by tabletsx86 with no results on the
touchscreen. Anyone have any other tips?

Message has been deleted
Message has been deleted

Mike C

unread,
Nov 28, 2011, 11:34:37 AM11/28/11
to Android-x86
I have the Acer Aspire One 110, the first model AAO, with Taiwanese
(don't remember the brand) 8.9" touchscreen mod and it works super
with Android-x86 V1.6.
Reply all
Reply to author
Forward
0 new messages