Hi Weston,
thanks for suggesting those debug tools. Here's my output
$ adb shell su -- getevent -lp /dev/input/event2
add device 1: /dev/input/event2
name: "gt80x"
events:
ABS (0003): ABS_HAT0X : value 0, min 0, max 0, fuzz 0, flat
0, resolution 0
ABS_HAT1X : value 0, min 0, max 0, fuzz 0, flat
0, resolution 0
ABS_HAT2Y : value 0, min 0, max 0, fuzz 0, flat
0, resolution 0
ABS_HAT3X : value 0, min 0, max 0, fuzz 0, flat
0, resolution 0
ABS_MT_TOUCH_MAJOR : value 0, min 0, max 255, fuzz 0,
flat 0, resolution 0
ABS_MT_WIDTH_MAJOR : value 0, min 0, max 255, fuzz 0,
flat 0, resolution 0
ABS_MT_POSITION_X : value 0, min 0, max 800, fuzz 0,
flat 0, resolution 0
ABS_MT_POSITION_Y : value 0, min 0, max 480, fuzz 0,
flat 0, resolution 0
input props:
<not available
And here's while touching onto the locker icon:
$ adb shell su -- getevent -lt /dev/input/event2
[ 471.347113] EV_ABS ABS_MT_POSITION_X 000002ae
[ 471.347143] EV_ABS ABS_MT_POSITION_Y 00000120
[ 471.347143] EV_ABS ABS_MT_TOUCH_MAJOR 0000001c
[ 471.347174] EV_ABS ABS_MT_WIDTH_MAJOR 0000001c
[ 471.347174] EV_SYN SYN_MT_REPORT 00000000
[ 471.362357] EV_SYN SYN_REPORT 00000000
[ 471.367784] EV_ABS ABS_MT_POSITION_X 000002ae
[ 471.368058] EV_ABS ABS_MT_POSITION_Y 00000120
[ 471.368271] EV_ABS ABS_MT_TOUCH_MAJOR 00000022
[ 471.368485] EV_ABS ABS_MT_WIDTH_MAJOR 00000022
[ 471.368698] EV_SYN SYN_MT_REPORT 00000000
[ 471.386808] EV_SYN SYN_REPORT 00000000
[ 471.394887] EV_ABS ABS_MT_POSITION_X 000002ae
[ 471.394918] EV_ABS ABS_MT_POSITION_Y 00000120
[ 471.394918] EV_ABS ABS_MT_TOUCH_MAJOR 00000023
[ 471.394918] EV_ABS ABS_MT_WIDTH_MAJOR 00000023
[ 471.394948] EV_SYN SYN_MT_REPORT 00000000
[ 471.394979] EV_SYN SYN_REPORT 00000000
...
I don't see anything wrong here. Is this correct? Indeed, 'PRESSURE' is
missing, but TOUCH_MAJOR should work as well. Indeed, as I said and shown
on video, I can see the touch circle shown on screen and moving under my
finger. Issue is that the locker window doesn't look like "receiving" those
events... I'm puzzled.
On Friday, 21 September 2012 08:25:07 UTC-7, Weston Weems wrote:
>
> Are you sure the driver is sending up the correct events? Fire up get
> event with:
> adb shell su -- getevent -lt /dev/input/event1
>
> make sure the commands that are comming in, are what your idc/keymap are
> expecting... more info on that here:
> http://source.android.com/tech/input/getevent.html
>
> Weston
>
> On Friday, September 21, 2012 5:39:41 AM UTC-7, ffxx68 wrote:
>>
>> Hi cnet,
>>
>> yes, that's what I've also done. Indeed looks like the kernel driver
>> isn't the main problem, I think...
>>
>> Here's what I've achieved so far. I've introduced the .idc file for the
>> touch device, so it gets recognized as an actual "touch" screen, not as a
>> "pointer" pad. Then I've set the "showTouches" to true in the
>> InputReader.cpp code, so to force showing of the touch position.
>>
>> I've posted a brief recording of results on YouTube:
>>
>> http://www.youtube.com/watch?v=XqebuAw5Jws&feature=youtu.be
>>
>> As you can see from video, the touch is properly received by the EventHub
>> module, but somehow it's not dispatched to the window, which is the locker
>> screen in this case...
>>
>> Also, I've enabled debug logging into InputReader.cpp and EventHub.cpp,
>> but I can see messages in the logcat only from the latter, which is another
>> mystery to me...
>>
>> On Thursday, September 20, 2012 11:52:55 AM UTC-7, cneth wrote:
>>>
>>> You need to add a .idc file for each TouchScreen that defines it's
>>> characteristics:
>>>
>>>
>>> http://source.android.com/tech/input/input-device-configuration-files.html
>>>
>>>
>>>
>>>
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
