Hi, Did you ever have success with the T231H and MK802 Android sticks?
On Thursday, July 19, 2012 9:59:07 PM UTC+1, rock99rock wrote: > > Were you able to get this completely working? I'm actually trying to get > support for the Acer T231H on the MK802 Android stick. I really have no > idea where to start, but it looks like you have the method that I will need > to use in order to accomplish this task. Any assistance in pointing me in > the right direction, and driver files you may have, etc I will be very > thankful. > > Thanks! > > On Thursday, April 19, 2012 1:01:58 PM UTC-5, Jiří Hamáček wrote: >> >> I did everything but touchscreen wasn't there. >> When compiling kernel, hid-quanta.o was created and final size of >> compressed kernel image was different from the previous (with another >> config options). >> I tried compile the driver as module (hid-quanta.ko) adb push it to >> device and insmod it.... and it works :) I have wrong resolution and touch >> is anywhere but my finger, but finaly it's working. >> I don't know why it didn't use that driver from the kernel. Now, I have >> to put insmod in init.rc, I suppose. >> >> Anyway, thank you so much for your help. Now I have your other steps to >> do. >> >> Thank you >> Jiri >> >> Dne čtvrtek, 19. dubna 2012 6:02:11 UTC+2 Kenny Wickstrom napsal(a): >>> >>> Are you getting any response when you touch the touchscreen? What if >>> you enable "Pointer Location" in Settings -> Developer Options? >>> >>> The messages you see in dmesg don't necessarily mean your driver is >>> included in the kernel, just that you connected a USB device. The last 2 >>> lines when connected to your laptop show the touchscreen is ready for use. >>> Have you confirmed the driver got compiled into the kernel (review the >>> make output, look for hid-quanta.o in out/target/product/...)? For me, I >>> only needed to set the CONFIG_HID_QUANTA=y (not any others) and rebuild the >>> kernel. At this point, I was able to see the device with getevent (see >>> below). My interactions via the touchscreen were incorrect when this was >>> the only change, >>> >>> Download "wireless adb" from the market (play store). This will allow >>> you to use ADB wirelessly (I'm guess the panda supports wireless). If you >>> can do adb while having the monitor attached, you can do "adb shell >>> getevent -p -l" (last param is lowercase L). This will show the devices >>> attached, you should see one for the Acer. The output below shows the >>> actual touchscreen from my Motorola Xoom (with ICS). >>> >>> >>> add device 2: /dev/input/event6 >>> name: "qtouch-touchscreen" >>> events: >>> ABS (0003): ABS_MT_TOUCH_MAJOR : value 0, min 0, max 15, fuzz 2, >>> flat 0, resolution 0 >>> ABS_MT_ORIENTATION : value 0, min 0, max 255, fuzz 0, >>> flat 0, resolution 0 >>> ABS_MT_POSITION_X : value 0, min 10, max 2569, fuzz >>> 0, flat 0, resolution 0 >>> ABS_MT_POSITION_Y : value 0, min 15, max 1614, fuzz >>> 0, flat 0, resolution 0 >>> ABS_MT_TRACKING_ID : value 0, min 0, max 10, fuzz 1, >>> flat 0, resolution 0 >>> ABS_MT_PRESSURE : value 0, min 0, max 255, fuzz 2, >>> flat 0, resolution 0 >>> input props: >>> <none> >>> >>> >>> You should see something similar for the panda's touchscreen and also >>> the Acer's quanta touchscreen (assuming it is attached). >>> >>> Good luck, >>> Kenny >>> >>> On Wednesday, April 18, 2012 3:18:13 PM UTC-5, Jiří Hamáček wrote: >>>> >>>> Thank you very much for your response, i am really hopeless. >>>> >>>> I tried so many combinations of kernel config options, but no result. >>>> In Froyo I just compile kernel with added CONFIG_HID_QUANTA=y and it >>>> worked. >>>> I thought that kernel should create input for the touchscreen if there >>>> is right driver present - I mean that it is the first place where i have >>>> something wrong, because it doesn't create any input. >>>> In dmesg it found only one squirk - maybe it is the problem. >>>> >>>> This is my current (not working) HID configs panda_defconfig file >>>> CONFIG_HID_QUANTA=y >>>> CONFIG_HID=y >>>> CONFIG_USB_HID=y >>>> CONFIG_HID_MULTITOUCH=y >>>> CONFIG_HID_SUPPORT=y >>>> CONFIG_HIDRAW=y >>>> CONFIG_HID_PID=y >>>> CONFIG_USB_HIDDEV=y >>>> >>>> Do you have any idea what could be wrong? >>>> Which version of ICS you were working on? >>>> >>>> Thank you >>>> Jiri >>>> >>>> Dne středa, 18. dubna 2012 16:52:47 UTC+2 Kenny Wickstrom napsal(a): >>>>> >>>>> I did manage to get this touchscreen working (at least mostly) on a >>>>> yet to be release Motorola device. I don't have all of the information >>>>> at >>>>> my fingertips, but I'll highlight some of the changes that I made. >>>>> >>>>> - Enabled the driver (CONFIG_HID_QUANTA=y) to be built into the >>>>> kernel. >>>>> - Needed to create an IDC (input device configuration) file named >>>>> Vendor_0408_Product_3001.idc and put it in /system/usr/idc (I think). >>>>> - it contains the following line: touch.deviceType = touchScreen >>>>> - touch.deviceType = touchScreen /* Needed to make >>>>> screen like touch device instead of pointer */ >>>>> - device.internal = 1 /* Needed this so the surface size >>>>> would match the phone's touch surface size */ >>>>> - More info: >>>>> http://source.android.com/tech/input/touch-devices.html >>>>> - In an early build, I needed to add to events >>>>> (ABS_MT_TOUCH_AMPLITUDE and ABS_MT_TOUCH_AREA) to the driver since it >>>>> appeared like the system was looking for these events. I've heard >>>>> that >>>>> these are no longer needed in the most recent builds. >>>>> >>>>> With the above changes, I could interact with the touchscreen. >>>>> However, the touch accuracy was way off. The accuracy seemed to be >>>>> related to the scaling it tried to do. I tried some settings in the IDC >>>>> file, but they got ignored down in the framework. In the end, I modified >>>>> a >>>>> file called InputReader.cpp where the scaling factors were calculated and >>>>> just hard-coded the correct values if the device name was "QUANTA...", >>>>> not >>>>> very elegant, but it worked for my purposes. >>>>> >>>>> Hopefully this helps some. Let me know if you need more info on any >>>>> of the above. >>>>> Kenny >>>>> >>>>> >>>>> On Friday, April 13, 2012 6:20:32 AM UTC-5, Jiří Hamáček wrote: >>>>>> >>>>>> I didn't know about CONFIG_HID_MULTITOUCH, but it doesn't work. >>>>>> Please could you send me your kernel config file, because I think I am >>>>>> missing something, or HID configs only. >>>>>> >>>>>> Thank you >>>>>> Jiri >>>>>> >>>>>> >>>>>> >>>>>> Dne středa, 11. dubna 2012 21:47:33 UTC+2 Hedwin napsal(a): >>>>>>> >>>>>>> Did you try HID_MULTITOUCH? >>>>>>> >>>>>>> On Mon, Apr 9, 2012 at 3:51 PM, Jiří Hamáček wrote: >>>>>>> >>>>>>>> Please, any idea? >>>>>>>> >>>>>>>> >>>>>>>> Dne úterý, 3. dubna 2012 11:26:15 UTC+2 Jiří Hamáček napsal(a): >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> I'm trying to get the touchscreen (idVendor=0408, idProduct=3001, >>>>>>>>> USB) to work with ICS and pandaboard, but no success >>>>>>>>> In Froyo and Gingerbread everything worked with quanta driver (i >>>>>>>>> tested it with android-x86 platform). >>>>>>>>> >>>>>>>>> *My hardware:* >>>>>>>>> >>>>>>>>> Pandaboard ES rev. B1 >>>>>>>>> LCD Acer t231h with usb touchscreen 0408:3001 >>>>>>>>> >>>>>>>>> >>>>>>>>> I've done this: >>>>>>>>> >>>>>>>>> *Compile kernel with:* >>>>>>>>> >>>>>>>>> #Acer T231H >>>>>>>>> CONFIG_HID_QUANTA=y >>>>>>>>> CONFIG_HID=y >>>>>>>>> CONFIG_USB_HID=y >>>>>>>>> >>>>>>>>> >>>>>>>>> *When I turn on debug in HID:* >>>>>>>>> >>>>>>>>> echo 1 > /sys/module/hid/parameters/**debug >>>>>>>>> >>>>>>>>> >>>>>>>>> *Dmesg in Android ICS on pandaboard after connect the touchscreen: >>>>>>>>> * >>>>>>>>> >>>>>>>>> [ 131.272521] usb 1-1.3: new full speed USB device number 6 using >>>>>>>>> ehci-omap >>>>>>>>> [ 131.449798] usb 1-1.3: New USB device found, idVendor=0408, >>>>>>>>> idProduct=3001 >>>>>>>>> [ 131.458068] usb 1-1.3: New USB device strings: Mfr=1, >>>>>>>>> Product=2, SerialNumber=0 >>>>>>>>> [ 131.466491] usb 1-1.3: Product: T231H >>>>>>>>> [ 131.470733] usb 1-1.3: Manufacturer: Acer >>>>>>>>> [ 131.498504] drivers/hid/usbhid/hid-core.c: HID probe called for >>>>>>>>> ifnum 0 >>>>>>>>> [ 131.506561] drivers/hid/usbhid/hid-quirks.**c: Found squirk >>>>>>>>> 0x8 for USB HID vendor 0x408 prod 0x3001 >>>>>>>>> >>>>>>>>> >>>>>>>>> *Dmesg after connecting the touchscreen to my laptop:* (Opensuse >>>>>>>>> 12.1 32bit, also tested in Ubuntu 12.04 64bit) >>>>>>>>> >>>>>>>>> [27014.108072] usb 6-1: new full speed USB device number 3 using >>>>>>>>> uhci_hcd >>>>>>>>> [27014.458336] usb 6-1: New USB device found, idVendor=0408, >>>>>>>>> idProduct=3001 >>>>>>>>> [27014.458346] usb 6-1: New USB device strings: Mfr=1, Product=2, >>>>>>>>> SerialNumber=0 >>>>>>>>> [27014.458353] usb 6-1: Product: T231H >>>>>>>>> [27014.458358] usb 6-1: Manufacturer: Acer >>>>>>>>> [27014.461420] /home/abuild/rpmbuild/BUILD/** >>>>>>>>> kernel-default-3.1.9/linux-3.**1/drivers/hid/usbhid/hid-core.**c: >>>>>>>>> HID probe called for ifnum 0 >>>>>>>>> [27014.461435] /home/abuild/rpmbuild/BUILD/** >>>>>>>>> kernel-default-3.1.9/linux-3.**1/drivers/hid/usbhid/hid-**quirks.c: >>>>>>>>> Found squirk 0x8 for USB HID vendor 0x408 prod 0x3001 >>>>>>>>> [27014.461555] /home/abuild/rpmbuild/BUILD/** >>>>>>>>> kernel-default-3.1.9/linux-3.**1/drivers/hid/usbhid/hid-**quirks.c: >>>>>>>>> Found squirk 0x8 for USB HID vendor 0x408 prod 0x3001 >>>>>>>>> [27014.509960] input: Acer T231H as /devices/pci0000:00/0000:00:** >>>>>>>>> 1d.1/usb6/6-1/6-1:1.0/input/**input11 >>>>>>>>> [27014.510376] quanta-touch 0003:0408:3001.0003: input,hidraw1: >>>>>>>>> USB HID v1.10 Device [Acer T231H] on usb-0000:00:1d.1-1/input0 >>>>>>>>> >>>>>>>>> >>>>>>>>> I tried to get it worked for several days with no success. >>>>>>>>> Any help is appreceated >>>>>>>>> Thank you >>>>>>>>> >>>>>>>>> Jiri >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
