Touchpad issues

[drufusb]

Edited:
Issue was fixed using the firmware and instructions form https://forum.pine64.org/showthread.php?tid=8407

-Many thanks to all those who helped.



Hi all, first I want to say I love the build quality of the Pinebook Pro, the key travel is great. In fact I am writing this post using the hardware right now   . I do occasionally do get missed key presses as I have seen by other posts, and am very grateful for the work being put into updating the firmware.

My only current major issue is the touchpad, it is almost non-working. Sometimes it thinks I have it pressed when I don't, even when no fingers are touching it, it will click a on-screen button every few seconds with no hands touching it. Other times it will not register clicks or my fingers moving across the surface of the touch area.

I have tried disabling and re-enabling all of the options under Touchpad in the Mouse Preferences, but nothing has improved its ability to function correctly.

For now the only way I have been able to get around this was to plug in an external mouse, which makes navigating GUIs doable.

Is there some way that maybe the touchpad is not calibrated correctly, or a way to calibrate it?

Thank you to all the people that have worked on this project, I have showed it to others I know and one day hope to make this (Pinebook Pro) my personal daily driver.

p.s. I have also seen posts about fingers slightly touching the touchpad when resting palms for typing causing keypress issues and I have specifically tried to touch type keys with nothing touching the touchpad and was still getting very delayed inupt from the keys.

[evilbunny]

My only current major issue is the touchpad, it is almost non-working. Sometimes it thinks I have it pressed when I don't, even when no fingers are touching it, it will click a on-screen button every few seconds with no hands touching it. Other times it will not register clicks or my fingers moving across the surface of the touch area.

https://forum.pine64.org/showthread.php?tid=8325

[odinson]

Out of curiosity, does this occur when using it flat on a surface like a desk or table, or is it in your lap at an angle? I was in a situation where I was using my PBP for hours in a car today, and at certain angles in my lap, the trackpad had issues with the "top click"* getting stuck. It appears to happen because of the case flexing a certain way at certain angles that keeps the trackpad from fully returning to the fully unpressed position. I had to level it out and sometimes gently apply a counter pressure to the case to get it unstuck.


*by "top click", I'm referring to the first of two clicks possible when pressing down on the trackpad.

[drufusb]

Thank you evilbunny, I have been following that thread pretty closely and am looking forward to the update.

I did notice that the lower left corner of the touchpad can get stuck down/pressed, due to sticky material on the back side of the touchpad. When I checked by removing the back cover as per the wiki Accessing the Internals, I also did notice that its ability to detect touch events was worse when the laptop was on my lap vs a table or desk. But I am still getting random "clicks" when nothing is touching the touchpad, and I have made sure that it is not stuck in the pressed position.

I have also noticed that if I do press and hold the touchpad "click" down, I am better able to move the mouse around the screen and more touch events are registered, but that also causes all contents on the screen to be selected. When I release pressure from the touchpad and it "un-clicks", the mouse often quits responding to any light touches for moving the mouse around and no longer registers events for movement of mouse on the desktop.

When running evtest to look at the usb input device events, with no "clicks" pressed (that I can tell) on the touchpad, the output from the tool is:

Code:

Event: time 1574030305.037629, -------------- SYN_REPORT ------------
Event: time 1574030305.045662, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 740
Event: time 1574030305.045662, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 246
Event: time 1574030305.045662, -------------- SYN_REPORT ------------
Event: time 1574030305.053567, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 736
Event: time 1574030305.053567, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 248
Event: time 1574030305.053567, -------------- SYN_REPORT ------------
Event: time 1574030305.061649, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 733
Event: time 1574030305.061649, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 249
Event: time 1574030305.061649, -------------- SYN_REPORT ------------
Event: time 1574030305.069547, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 731
Event: time 1574030305.069547, -------------- SYN_REPORT ------------
Event: time 1574030305.077545, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 729
Event: time 1574030305.077545, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 248
Event: time 1574030305.077545, -------------- SYN_REPORT ------------
Event: time 1574030305.085541, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 727
Event: time 1574030305.085541, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 247
Event: time 1574030305.085541, -------------- SYN_REPORT ------------
Event: time 1574030305.093548, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 725
Event: time 1574030305.093548, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 245
Event: time 1574030305.093548, -------------- SYN_REPORT ------------
Event: time 1574030305.101544, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 724
Event: time 1574030305.101544, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 243
Event: time 1574030305.101544, -------------- SYN_REPORT ------------
Event: time 1574030305.109539, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 723
Event: time 1574030305.109539, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 240
Event: time 1574030305.109539, -------------- SYN_REPORT ------------
Event: time 1574030305.117537, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 237
Event: time 1574030305.117537, -------------- SYN_REPORT ------------
Event: time 1574030305.125545, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 234
Event: time 1574030305.125545, -------------- SYN_REPORT ------------
Event: time 1574030305.133548, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 724
Event: time 1574030305.133548, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 230
Event: time 1574030305.133548, -------------- SYN_REPORT ------------
Event: time 1574030305.181593, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
Event: time 1574030305.181593, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1574030305.181593, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 0
Event: time 1574030305.181593, -------------- SYN_REPORT ------------

At the end of the log it shows DOUBLETAP, but all I did was remove a single finger from touching the touchpad, I did not touch it with more then a single finger and I removed it without pressing.
Thank you all for your help in trying to figure this out, any help is greatly appreciated. I would like to not have to have an external mouse plugged in if possible, it makes it way less "take on the go" friendly.

[evilbunny]

Thank you all for your help in trying to figure this out, any help is greatly appreciated. I would like to not have to have an external mouse plugged in if possible, it makes it way less "take on the go" friendly.

You may have to wait for firmware updates.
(I prefer a mouse over a touchpad, so I don't think I can help much/at all)

[drufusb]

To all helping, I have run the firmware updates from https://forum.pine64.org/showthread.php?tid=8407 and the touchpad and keyboard are working much better now!!

All my major issues have been resolved now with the built-in input devices.

Thank you all for helping try and figure this out, seams to have been related to the factory firmware.