With stylus, pointerup event arrives ~100ms late |
|||||||||||
Issue descriptionChrome Version: 67.0.3383.0 OS Version: 10539.0.0 Repro steps: 1) Open http://output.jsbin.com/jasugoz 2) Try dragging and lifting the stylus just a little off the screen 3) Try dragging and lifting the stylus quickly off the screen Expected: both up events should arrive ~2.5ms after the last move event Actual: lifting just a little sends an up event in 2.5ms, while lifting more causes it to arrive 60-100ms later
,
Apr 16 2018
,
Apr 16 2018
Repro at a lower level, logs from evtest: LIFT SLOW: Event: time 1523904719.576722, type 3 (EV_ABS), code 0 (ABS_X), value 18746 Event: time 1523904719.576722, type 3 (EV_ABS), code 1 (ABS_Y), value 8397 Event: time 1523904719.576722, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 331 Event: time 1523904719.576722, type 3 (EV_ABS), code 40 (ABS_MISC), value 14326 Event: time 1523904719.576722, -------------- SYN_REPORT ------------ Event: time 1523904719.584353, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042 Event: time 1523904719.584353, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 Event: time 1523904719.584353, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 0 Event: time 1523904719.584353, -------------- SYN_REPORT ------------ LIFT FAST: Event: time 1523904599.676123, type 3 (EV_ABS), code 0 (ABS_X), value 15590 Event: time 1523904599.676123, type 3 (EV_ABS), code 1 (ABS_Y), value 7095 Event: time 1523904599.676123, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 1767 Event: time 1523904599.676123, type 3 (EV_ABS), code 40 (ABS_MISC), value 62542 Event: time 1523904599.676123, -------------- SYN_REPORT ------------ Event: time 1523904599.742178, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042 Event: time 1523904599.742178, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 Event: time 1523904599.742178, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 0 Event: time 1523904599.742178, type 3 (EV_ABS), code 26 (ABS_TILT_X), value 8 Event: time 1523904599.742178, type 3 (EV_ABS), code 27 (ABS_TILT_Y), value 13
,
Apr 16 2018
parekhp@, This seems to be a fw or hardware issue. Are you aware of any hardware protocol limitations? Should we include wacom?
,
Apr 16 2018
This looks more like a FW issue could you please add Hadi to this.
,
Apr 16 2018
+ hadih@
,
Apr 16 2018
Hey Hadi - Can you please help drive this with Wacom. It seems when pen goes out of of range really quickly, FW might be waiting for few frames to see if it did not go out of sync, and hence it might be reporting pen up event late.
,
Apr 16 2018
surething. will start thread with Wacom.
,
Apr 17 2018
Here is Wacom response. Could you please give the attached FW a try and let me know if delay is improved? "Hello Hadi, For the Windows OS, the latest package of FW needs to have some delay time to avoid cursor blinking when pen hovering. We removed this delay for you to test. We’ve tested it in our side by FAE, we can see it has been improved."
,
Apr 17 2018
,
Apr 18 2018
Thanks, hadih@, the fw attached has name of *A70*, while we care about A70. The bug is reported on A50. Shall we get the fw update for A50 first?
,
Apr 20 2018
A50 FW is attached.
,
Apr 26 2018
Update: for A50 Wacom improved FW and we are measuring 17ms ~ 23 ms.Full evaluation of stylus is scheduled to be done by Monday in touch lab using stylus robot.
,
May 12 2018
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/overlays/overlay-eve-private/+/6bb0e23dfc5019688a9c9c4c89028ca22462852e commit 6bb0e23dfc5019688a9c9c4c89028ca22462852e Author: Jingkui Wang <jkwang@google.com> Date: Sat May 12 06:22:13 2018
,
Jun 10 2018
Issue #851314 might be related.
,
Jun 10 2018
This issue is chrome os fw change rather than chrome change. It should not influence chrome on other platforms. |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by jkwang@google.com
, Apr 16 2018