Touch event delayed or missing with weston 1.8.0 and qtwayland 5.4.2

[Vikas Patil]

I think when I feel delay in touch. Seeing following log from weston
(I added the prints) and evtest prints. I am testing this with button
on HMI. When the button is pressed, it is displayed as pressed, but
when released, the view is not updated immediately and it is still
displayed as pressed for sometime and after very little delay it shows
released.

Could anyone give some inputs?


weston log:

[13:13:40.144] -----> notify_touch: WL_TOUCH_DOWN
[13:13:40.144] -----> notify_touch: touch_grab_down
[13:13:40.144] -----> notify_touch_frame
[13:13:40.144] -----> notify_touch: touch_grab_frame
[13:13:40.198] -----> notify_touch: WL_TOUCH_MOTION
[13:13:40.198] -----> notify_touch: touch_grab_motion
[13:13:40.198] -----> notify_touch_frame
[13:13:40.198] -----> notify_touch: touch_grab_frame
[13:13:40.208] -----> notify_touch: WL_TOUCH_MOTION
[13:13:40.208] -----> notify_touch: touch_grab_motion
[13:13:40.208] -----> notify_touch_frame
[13:13:40.208] -----> notify_touch: touch_grab_frame
[13:13:40.262] -----> notify_touch: WL_TOUCH_MOTION
[13:13:40.262] -----> notify_touch: touch_grab_motion
[13:13:40.262] -----> notify_touch_frame
[13:13:40.262] -----> notify_touch: touch_grab_frame
[13:13:40.342] -----> notify_touch: WL_TOUCH_UP
[13:13:40.342] -----> notify_touch: touch_grab_up
[13:13:40.342] -----> notify_touch_frame
[13:13:40.342] -----> notify_touch: touch_grab_frame

evtest log:

Event: time 1444828420.143687, type 3 (EV_ABS), code 57
(ABS_MT_TRACKING_ID), value 82
Event: time 1444828420.143687, type 3 (EV_ABS), code 53
(ABS_MT_POSITION_X), value 78
Event: time 1444828420.143687, type 3 (EV_ABS), code 54
(ABS_MT_POSITION_Y), value 431
Event: time 1444828420.143687, type 3 (EV_ABS), code 58
(ABS_MT_PRESSURE), value 35
Event: time 1444828420.143687, -------------- EV_SYN ------------
Event: time 1444828420.198068, type 3 (EV_ABS), code 53
(ABS_MT_POSITION_X), value 74
Event: time 1444828420.198068, -------------- EV_SYN ------------
Event: time 1444828420.207220, type 3 (EV_ABS), code 53
(ABS_MT_POSITION_X), value 73
Event: time 1444828420.207220, type 3 (EV_ABS), code 54
(ABS_MT_POSITION_Y), value 429
Event: time 1444828420.207220, -------------- EV_SYN ------------
Event: time 1444828420.261657, type 3 (EV_ABS), code 53
(ABS_MT_POSITION_X), value 72
Event: time 1444828420.261657, type 3 (EV_ABS), code 58
(ABS_MT_PRESSURE), value 70
Event: time 1444828420.261657, type 3 (EV_ABS), code 48
(ABS_MT_TOUCH_MAJOR), value 4
Event: time 1444828420.261657, -------------- EV_SYN ------------
Event: time 1444828420.341950, type 3 (EV_ABS), code 57
(ABS_MT_TRACKING_ID), value -1
Event: time 1444828420.341950, -------------- EV_SYN ------------

Best Regards,
Vikash

On Thu, Nov 19, 2015 at 8:59 PM, Vikas Patil <vikasmpatil at gmail.com> wrote:
> Dear Community,
>
> I am using following components and seeing sometime touch doesn't
> respond (seems touch_up event delayed or some touch event missing).
> For example back button on screen takes time to go back to desired
> screen or I need to touch it again.
>
> linux 3.14.28
> weston 1.8.0 with ivi-shell
> qt 5.4.2.
> qtwayland 5.4.2 + patch to support touch
>
> I have checked with following two commands and it seems touch events
> are proper from kernel and libinput.
>
> #libinput-debug-events --device /dev/input/event0
> #evtest /dev/input/event0
>
> I am trying to understand what is happening but no luck yet. Has
> anyone observed the same and fixed it? Could you give some
> inputs/suggestions to understand and debug this?
>
> Thanking you for reading this.
>
> Thanks & Regards,
> Vikas