Kenny
im sorry i have to ask you this but im facing the same problem you guys do, 
or did but i am not an android programmer.
tough i was involved with programming many years ago i am very rusted and 
not literated in android or linux, just as user.
but i need to solve the same problem you did managed to solve.
can u give me a step by step tutorial or at least where to read one about 
your sollution?
i really appreciate this
regards
rodo

El miércoles, 18 de abril de 2012 11:52:47 UTC-3, Kenny Wickstrom escribió:
>
> 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: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to