Touchpad notchy on new 2021 pinebook pro
#8
(05-30-2021, 04:04 PM)BCB Wrote: You couldn't just move a little, you would move and nothing would happen, then it would finally move and jump past your target.  So the setting in question is found in manjaro by going to  start button>system settings>input devices>touchpad then to the pointer motion tab.  The setting in question is the noise cancellation, I think by default it was set to 8 for vertical and horizontal.  Not sure of the specifics, but basically you could select 8 units of movement before the cursor would move, causing great frustration.  I changed both settings to 0, which made a vast improvement.  I also slowed down the cursor having minimum speed at about 75% of the way to the first notch, maximum speed 25% past the second notch, and and acceleration 25% past the first notch.  Change the settings, click apply at the bottom right and breathe a sigh of relief.

I was so happy to read that you found a solution for the touchpad issues, but...

I've tried applying your recommended settings, but I'm unfortunately still having the original issue: dreaded touchpad delay upon initial finger movement. Undecided  Actually, Xfce doesn't provide the settings you've described, so I've introduced the following additional configuration to the X synaptics driver:

Code:
Option "HorizHysteresis" "0"
Option "VertHysteresis"  "0"

Sadly, the initial touchpad delay remains with these settings in place, i.e. they made no noticeable effects on my first-batch ISO PineBook Pro. Undecided  I've also tried "1" and "10" as the values for these two parameters, still with no noticeable effects.

I've verified that the correct settings were applied, using the xinput utility, and yes, the value of the "Synaptics Noise Cancellation" property was already correctly set to "0, 0", as displayed by xinput.  Anyway, I've tried re-applying the settings using the xinput utility:

Code:
xinput set-prop "HAILUCK CO.,LTD USB KEYBOARD Touchpad" "Synaptics Noise Cancellation" 0 0

Sadly, this also made no noticeable effects, but that was already expected. Undecided  As a note, the default value of this property was "8, 8", as displayed by xinput.

Going further down the rabbit hole, I've monitored the touchpad events using the evtest utility, outside of X.  As a result, no synaptics driver settings were in effect while monitoring the touchpad events, which makes it possible to determine the real nature of the initial touchpad delay.

Below are the excerpts from a few outputs generated by executing the following command on tty1 (complete outputs are attached to this post):

Code:
evtest --grab /dev/input/event2

Execution #1 – an excerpt that shows the events generated by sliding my finger horizontally across the touchpad, in which is visible that the touchpad introduced a delay that lasted 1622833404.821716 - 1622833404.789698 = 32 ms:

Code:
Event: time 1622833404.781717, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 78
Event: time 1622833404.781717, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 713
Event: time 1622833404.781717, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 519
Event: time 1622833404.781717, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1622833404.781717, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1622833404.781717, type 3 (EV_ABS), code 0 (ABS_X), value 713
Event: time 1622833404.781717, type 3 (EV_ABS), code 1 (ABS_Y), value 519
Event: time 1622833404.781717, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833404.781717, -------------- SYN_REPORT ------------
Event: time 1622833404.789698, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 714
Event: time 1622833404.789698, type 3 (EV_ABS), code 0 (ABS_X), value 714
Event: time 1622833404.789698, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833404.789698, -------------- SYN_REPORT ------------
Event: time 1622833404.797687, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833404.797687, -------------- SYN_REPORT ------------
Event: time 1622833404.805688, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833404.805688, -------------- SYN_REPORT ------------
Event: time 1622833404.813700, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833404.813700, -------------- SYN_REPORT ------------
Event: time 1622833404.821716, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 717
Event: time 1622833404.821716, type 3 (EV_ABS), code 0 (ABS_X), value 717
Event: time 1622833404.821716, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833404.821716, -------------- SYN_REPORT ------------
Event: time 1622833404.829711, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 723
Event: time 1622833404.829711, type 3 (EV_ABS), code 0 (ABS_X), value 723
Event: time 1622833404.829711, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833404.829711, -------------- SYN_REPORT ------------
Event: time 1622833404.837707, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 732
Event: time 1622833404.837707, type 3 (EV_ABS), code 0 (ABS_X), value 732
Event: time 1622833404.837707, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833404.837707, -------------- SYN_REPORT ------------

Execution #2 – an excerpt for the same finger movement as in the first example, which shows a delay of 1622833505.165592 - 1622833505.053691 = 112 ms:

Code:
Event: time 1622833505.045724, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 80
Event: time 1622833505.045724, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 556
Event: time 1622833505.045724, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 466
Event: time 1622833505.045724, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1622833505.045724, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1622833505.045724, type 3 (EV_ABS), code 0 (ABS_X), value 556
Event: time 1622833505.045724, type 3 (EV_ABS), code 1 (ABS_Y), value 466
Event: time 1622833505.045724, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833505.045724, -------------- SYN_REPORT ------------
Event: time 1622833505.053691, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833505.053691, -------------- SYN_REPORT ------------
Event: time 1622833505.061687, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833505.061687, -------------- SYN_REPORT ------------
Event: time 1622833505.069693, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833505.069693, -------------- SYN_REPORT ------------
Event: time 1622833505.077693, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833505.077693, -------------- SYN_REPORT ------------
Event: time 1622833505.085691, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833505.085691, -------------- SYN_REPORT ------------
Event: time 1622833505.093693, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833505.093693, -------------- SYN_REPORT ------------
Event: time 1622833505.101689, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833505.101689, -------------- SYN_REPORT ------------
Event: time 1622833505.109689, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833505.109689, -------------- SYN_REPORT ------------
Event: time 1622833505.117701, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833505.117701, -------------- SYN_REPORT ------------
Event: time 1622833505.125702, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833505.125702, -------------- SYN_REPORT ------------
Event: time 1622833505.133671, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833505.133671, -------------- SYN_REPORT ------------
Event: time 1622833505.141702, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833505.141702, -------------- SYN_REPORT ------------
Event: time 1622833505.149570, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833505.149570, -------------- SYN_REPORT ------------
Event: time 1622833505.157537, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833505.157537, -------------- SYN_REPORT ------------
Event: time 1622833505.165592, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 557
Event: time 1622833505.165592, type 3 (EV_ABS), code 0 (ABS_X), value 557
Event: time 1622833505.165592, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833505.165592, -------------- SYN_REPORT ------------
Event: time 1622833505.173605, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 559
Event: time 1622833505.173605, type 3 (EV_ABS), code 0 (ABS_X), value 559
Event: time 1622833505.173605, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833505.173605, -------------- SYN_REPORT ------------
Event: time 1622833505.181606, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 562
Event: time 1622833505.181606, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 465
Event: time 1622833505.181606, type 3 (EV_ABS), code 0 (ABS_X), value 562
Event: time 1622833505.181606, type 3 (EV_ABS), code 1 (ABS_Y), value 465
Event: time 1622833505.181606, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833505.181606, -------------- SYN_REPORT ------------
Event: time 1622833505.189696, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 566
Event: time 1622833505.189696, type 3 (EV_ABS), code 0 (ABS_X), value 566
Event: time 1622833505.189696, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833505.189696, -------------- SYN_REPORT ------------

Execution #3 – an excerpt for the same finger movement as in the first example, which shows a delay of 1622833543.341713 - 1622833543.125568 = 216 ms (obviously, I got better at triggering the delay with no visible mouse pointer):

Code:
Event: time 1622833543.117729, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 82
Event: time 1622833543.117729, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 485
Event: time 1622833543.117729, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 457
Event: time 1622833543.117729, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1622833543.117729, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1622833543.117729, type 3 (EV_ABS), code 0 (ABS_X), value 485
Event: time 1622833543.117729, type 3 (EV_ABS), code 1 (ABS_Y), value 457
Event: time 1622833543.117729, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.117729, -------------- SYN_REPORT ------------
Event: time 1622833543.125568, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.125568, -------------- SYN_REPORT ------------
Event: time 1622833543.133688, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.133688, -------------- SYN_REPORT ------------
Event: time 1622833543.141537, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.141537, -------------- SYN_REPORT ------------
Event: time 1622833543.149584, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.149584, -------------- SYN_REPORT ------------
Event: time 1622833543.157620, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.157620, -------------- SYN_REPORT ------------
Event: time 1622833543.165520, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.165520, -------------- SYN_REPORT ------------
Event: time 1622833543.173561, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.173561, -------------- SYN_REPORT ------------
Event: time 1622833543.181702, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.181702, -------------- SYN_REPORT ------------
Event: time 1622833543.189701, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.189701, -------------- SYN_REPORT ------------
Event: time 1622833543.197789, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.197789, -------------- SYN_REPORT ------------
Event: time 1622833543.205704, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.205704, -------------- SYN_REPORT ------------
Event: time 1622833543.213703, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.213703, -------------- SYN_REPORT ------------
Event: time 1622833543.221726, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.221726, -------------- SYN_REPORT ------------
Event: time 1622833543.229702, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.229702, -------------- SYN_REPORT ------------
Event: time 1622833543.237703, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.237703, -------------- SYN_REPORT ------------
Event: time 1622833543.245707, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.245707, -------------- SYN_REPORT ------------
Event: time 1622833543.253703, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.253703, -------------- SYN_REPORT ------------
Event: time 1622833543.261704, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.261704, -------------- SYN_REPORT ------------
Event: time 1622833543.269702, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.269702, -------------- SYN_REPORT ------------
Event: time 1622833543.277599, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.277599, -------------- SYN_REPORT ------------
Event: time 1622833543.285702, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.285702, -------------- SYN_REPORT ------------
Event: time 1622833543.293703, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.293703, -------------- SYN_REPORT ------------
Event: time 1622833543.301702, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.301702, -------------- SYN_REPORT ------------
Event: time 1622833543.309703, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.309703, -------------- SYN_REPORT ------------
Event: time 1622833543.317598, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.317598, -------------- SYN_REPORT ------------
Event: time 1622833543.325894, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.325894, -------------- SYN_REPORT ------------
Event: time 1622833543.333702, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.333702, -------------- SYN_REPORT ------------
Event: time 1622833543.341713, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 486
Event: time 1622833543.341713, type 3 (EV_ABS), code 0 (ABS_X), value 486
Event: time 1622833543.341713, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.341713, -------------- SYN_REPORT ------------
Event: time 1622833543.349698, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 488
Event: time 1622833543.349698, type 3 (EV_ABS), code 0 (ABS_X), value 488
Event: time 1622833543.349698, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.349698, -------------- SYN_REPORT ------------
Event: time 1622833543.357707, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 491
Event: time 1622833543.357707, type 3 (EV_ABS), code 0 (ABS_X), value 491
Event: time 1622833543.357707, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.357707, -------------- SYN_REPORT ------------
Event: time 1622833543.365692, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 495
Event: time 1622833543.365692, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 456
Event: time 1622833543.365692, type 3 (EV_ABS), code 0 (ABS_X), value 495
Event: time 1622833543.365692, type 3 (EV_ABS), code 1 (ABS_Y), value 456
Event: time 1622833543.365692, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1622833543.365692, -------------- SYN_REPORT ------------

Based on these three excerpts, it should be safe to conclude that the trackpad firmware has a bug that introduces a delay upon the initial finger movement, as decribed below.  As a note, this conclusion isn't new, more than a few forum members have already concluded the same.

Thus, I have to ask you this: are you absolutely positive that you no longer have the initial touchpad delay?  It manifests as having no pointer movement when you touch the touchpad with your finger and start sliding the finger across the touchpad, horizontally for example.  Then, continuing the sliding motion, the pointer eventually starts moving, but the short initial finger movement is lost, so to speak.  That's the dreaded delay.


Attached Files
.txt   evtest-out-1.txt (Size: 22.27 KB / Downloads: 252)
.txt   evtest-out-2.txt (Size: 32.28 KB / Downloads: 259)
.txt   evtest-out-3.txt (Size: 34.79 KB / Downloads: 245)
  Reply


Messages In This Thread
RE: Touchpad notchy on new 2021 pinebook pro - by dsimic - 06-04-2021, 01:49 PM

Possibly Related Threads…
Thread Author Replies Views Last Post
  Pinebook Pro on Debian 12 Power Issue u974615 1 234 03-13-2024, 10:46 AM
Last Post: u974615
  Pinebook Pro Source for Trackpad Flex / Ribbon Cable rankharris 1 180 02-17-2024, 07:06 PM
Last Post: tllim
  HDMI or VGA From Pinebook Pro via Pinebook Pro Docking Deck? segaloco 0 152 02-13-2024, 10:43 PM
Last Post: segaloco
  Pinebook Pro charging issues tomekdev 1 527 01-05-2024, 08:40 PM
Last Post: tomekdev
  Replacement battery for PineBook Pro DrYak 3 958 11-07-2023, 10:09 AM
Last Post: DrYak
  Pinebook Pro Revised Keyboard Firmware jackhumbert 73 127,134 09-13-2023, 03:43 AM
Last Post: k3dAR
  PineBook Pro dead ottahe 9 5,716 01-18-2023, 07:41 PM
Last Post: ottahe
  Pinebook Pro malfunctioned hardware samtux 10 4,144 12-27-2022, 03:31 PM
Last Post: samtux
  Touchpad Issues - August 2022 Run SteveCaruso 5 2,804 12-14-2022, 11:00 PM
Last Post: doug
  PineBook Pro revision 2.2: Wishlist for the hardware issue fixes dsimic 115 131,843 11-30-2022, 04:28 PM
Last Post: KC9UDX

Forum Jump:


Users browsing this thread: 1 Guest(s)