Touch event delayed or missing with weston 1.8.0 and qtwayland 5.4.2

Fri Dec 11 05:09:39 PST 2015

Hi Giulio,

Thanks for the suggestion. I was able to capture the wayland log from
weston and HMI as per your suggestion with good and bad scenarios. You
will see two times wayland log, I think this is due to I have
specified WAYLAND_DEBUG=1 for weston and hmi both.

Captured log for below five scenarios. 1st scenario is good and rest
is bad.. Attached here the logs for each scenario. If possible could
you point me out or suggest what might be going wrong?

Scenario 1: When the button is pressed, it is displayed as pressed,
when released, the view is updated without delay.
- This I think is good case and these call sequence should be there
each time and can be used as reference.
- Also looking at the timestamp it takes 110 ms from first touch_down
event to last callback_done notify. Which seems reasonable.

Scenario 2: When the button is pressed, it is displayed as pressed,
when released, the view is updated after some delay.
- Here all call sequence seems ok to me after referring touch id,
surface id and buffer id but can't make out any wrong calls.
- Also looking at the timestamp it takes 783 ms from first touch_down
event to last callback_done notify. Any idead what can cause this?

Scenario 3: When the button is pressed, it is not displayed as
pressed, observed delay in wayland log from weston and hmi
- Here no surface events, request observed and all touch events
immediately (down, frame and up). Any idea what can cause this?

Scenario 4: When the button is pressed, it is not displayed as
pressed, observed immediate all touch events log from weston and hmi
- here I think error is touch_down, touch_frame and touch_up comes
immediate without attach, damage, commit before touch_up.

Scenario 5: When the button is pressed, it is not displayed as
pressed, observed delay in wayland log from weston and hmi, second
touch to recover

@All, Waiting for comments/suggestions/inputs and thanking you all.

Thanks & Regards,
Vikas

On Sat, Nov 21, 2015 at 1:28 AM, Giulio Camuffo <giuliocamuffo at gmail.com> wrote:
> 2015-11-20 13:28 GMT+02:00 Vikas Patil <vikasmpatil at gmail.com>:
>> 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?
>
> You should export the environment variable WAYLAND_DEBUG=1 on the
> client side and check if the wl_touch events are coming correctly at
> the right time. If they are the bug is probably in the client,
> otherwise it's in the compositor.
>
>
> --
> Giulio
>
>>
>>
>> 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
>> _______________________________________________
>> wayland-devel mailing list
>> wayland-devel at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/wayland-devel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1_scenario.log
Type: application/octet-stream
Size: 5340 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/wayland-devel/attachments/20151211/d4c8279a/attachment-0005.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2_scenario.log
Type: application/octet-stream
Size: 5501 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/wayland-devel/attachments/20151211/d4c8279a/attachment-0006.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 3_scenario.log
Type: application/octet-stream
Size: 4012 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/wayland-devel/attachments/20151211/d4c8279a/attachment-0007.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 4_scenario.log
Type: application/octet-stream
Size: 4081 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/wayland-devel/attachments/20151211/d4c8279a/attachment-0008.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 5_scenario.log
Type: application/octet-stream
Size: 5477 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/wayland-devel/attachments/20151211/d4c8279a/attachment-0009.obj>