Hello Team,
I'm working on multi-touch within Android 2.2

I need to support following use cases:
1. Report Pen activities
2. Report Multi-touch activities

I prefer to have very clear documentation that describes Android
protocol works, but not very short description that actually don't
work well.
I need to be able to manage ABS_MT_TRACKING_ID, since my track id
changes a lot, because of support for complicated motions on sensor.
The HW I'm working has very precise data about each finger.

FOLLOWING ARE RESULTS OF MY TEST:

For a Pen I found that in order to adjust Events with Android, I must
to report Pen as single touch
EV_ABS, ABS_PRESSURE
EV_ABS, ABS_X
EV_ABS, ABS_Y
EV_KEY, BTN_TOUCH
SYNCH_DATA

If I use multi-touch queue, both BTN_TOUCH and ABS_PRESSURE ignored

For Multi-Touch issue is much more complicated:
There is simple protocol for that

EV_ABS, ABS_MT_POSITION_X
EV_ABS, ABS_MT_POSITION_Y
EV_ABS, ABS_MT_TOUCH_MAJOR
MT_SYNCH

EV_ABS, ABS_MT_POSITION_X
EV_ABS, ABS_MT_POSITION_Y
EV_ABS, ABS_MT_TOUCH_MAJOR
MT_SYNCH
SYNCH_DATA

The problem is that you need to add BTN_TOUCH info
so what I do before sending ABS information I send
EV_KEY, BTN_TOUCH, number of fingers
EV_KEY, BTN_1
EV_KEY, BTN_2
....

In this case Android responds to events.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to