Trackpad firmware update
That is strange, because the way that I know that the firmware is persistent is that the name of the device also changed from "HAILUCK ... Ltd." to "Pinebook Pro Touchpad" or similar. This is across different operating systems, too.
  Reply
(09-06-2020, 09:27 AM)via Wrote: I've been using the firmware update from jackhumbert, and it vastly improves my touchpad experience, but it doesn't seem to persist a reboot. Has anyone else experienced this?

I'm using debian from the pinebook pro installer.  Its not like the firmware somehow is getting reverted, because if I modify the updater to purely enter boot mode and then do a reset (skipping the actual firmware flashing), the touchpad is suddenly usable and great again.  As far as I can tell, nothing is different when Xorg detects the device the second time -- the logs indicate the same parameters with respect to acceleration, the only thing that changes is the ID (event11 instead of event7 in my case), probably because its rediscovered.

I'm tempted to just trigger this on my xsession.

That is very strange. What bad touchpad behavior are you seeing? Does it appear immediately on reboot? Does the reset permanently improve the behavior until another reboot?

The issue I occasionally experience which is fixed by a reset or reboot I suspect to be an issue inherent to the touchpad firmware. I have noticed that sometimes the touchpad will get itself in a "bad state" where it gets overly sensitive and constantly thinks there's touch events even when I'm not touching it.
  Reply
Just by the nature that firmware is persistent to the hardware, and the operating system software is independent of the of the firmware, perhaps you have a settings problem within the operating system...
( Just my observation)
      LINUX = CHOICES
         **BCnAZ**
               Idea
   Donate to $upport
your favorite OS Team
  Reply
Is this update required for PBP shipping mid Oct 2020?
  Reply
I tried running the updater from https://github.com/jackhumbert/pinebook-...d-updater/ on ANSI PBP shipped 10/2020.  After first step finished, key mapping was wrong and trackpad did not work.  Step 2 results in :

>>> Trying to open VID:0603 PID:1020...
>>> Device not found
>>> Failed to open in boot mode


Tried rebooting and redoing step 1 many many times, but now step 1 gives the same fail.  

Any ideas how to recover?

Full log:
Running STEP-2...

[*]Flashing touchpad firmware...
[*]Opening in touchpad mode
>>> Trying to open VID:258a PID:001f...
>>> Kernel Driver Active
>>> Writing offset:0 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:1024 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:2048 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:3072 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:4096 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:5120 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:6144 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:7168 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:8192 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:9216 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:10240 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:11264 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:12288 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:13312 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:14336 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:15360 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:16384 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:17408 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:18432 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:19456 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:20480 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:21504 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:22528 length:1024...
>>> Verifying '1k-data'...
>>> Writing offset:23552 length:1024...
>>> Verifying '1k-data'...
[*]Verifying 'end-program'...
[*]Verifying 'checksum'...
[*]Verifying 'program'...
[*]Finished succesfully!
>>> release interface
[*]Flashing ANSI keyboard firmware...
>>> Fix hex file
[*]Opening in user mode...
>>> Trying to open VID:258a PID:001e...
>>> Device not found
>>> Trying to open VID:258a PID:001f...
[*]Sending command to switch to boot mode...
[*]Command send
>>> release interface
[*]Opening in boot mode
>>> Trying to open VID:0603 PID:1020...
>>> Device not found
>>> Trying to open VID:0603 PID:1020...
>>> Device not found
>>> Trying to open VID:0603 PID:1020...
>>> Device not found
>>> Trying to open VID:0603 PID:1020...
>>> Device not found
>>> Trying to open VID:0603 PID:1020...
>>> Device not found
>>> Trying to open VID:0603 PID:1020...
>>> Device not found
>>> Trying to open VID:0603 PID:1020...
>>> Device not found
>>> Trying to open VID:0603 PID:1020...
>>> Device not found
>>> Trying to open VID:0603 PID:1020...
>>> Device not found
>>> Trying to open VID:0603 PID:1020...
>>> Device not found
>>> Trying to open VID:0603 PID:1020...
>>> Device not found
>>> Trying to open VID:0603 PID:1020...
>>> Device not found
>>> Trying to open VID:0603 PID:1020...
>>> Device not found
>>> Trying to open VID:0603 PID:1020...
>>> Device not found
>>> Trying to open VID:0603 PID:1020...
>>> Device not found
>>> Trying to open VID:0603 PID:1020...
>>> Device not found
>>> Trying to open VID:0603 PID:1020...
>>> Device not found
>>> Trying to open VID:0603 PID:1020...
>>> Device not found
>>> Trying to open VID:0603 PID:1020...
>>> Device not found
>>> Trying to open VID:0603 PID:1020...
>>> Device not found
>>> Failed to open in boot mode



USBVIEW report:
USB KEYBOARD
Manufacturer: HAILUCK CO.,LTD
Speed: 1.5Mb/s (low)
Bus:  3
Address:  26
USB Version:  1.10
Device Class: 00(>ifc )
Device Subclass: 00
Device Protocol: 00
Maximum Default Endpoint Size: 8
Number of Configurations: 1
Vendor Id: 258a
Product Id: 001f
Revision Number:  1.00

Config Number: 1
Number of Interfaces: 2
Attributes: a0
MaxPower Needed: 100mA

Interface Number: 0
Name: usbhid
Alternate Number: 0
Class: 03(HID  )
Sub Class: 01
Protocol: 01
Number of Endpoints: 1

Endpoint Address: 81
Direction: in
Attribute: 3
Type: Int.
Max Packet Size: 8
Interval: 10ms

Interface Number: 1
Name: usbhid
Alternate Number: 0
Class: 03(HID  )
Sub Class: 00
Protocol: 00
Number of Endpoints: 1

Endpoint Address: 82
Direction: in
Attribute: 3
Type: Int.
Max Packet Size: 8
Interval: 10ms
  Reply
There is improvement with the drift on the touch pad, but it's till there after this update.
  Reply
I FINALLY fixed by putting my pbp kb in boot mode with a python script.
  Reply
That could take place for a lot of reasons:
Hardware fail:
The controller board of your trackpad could be damaged; for instance, A static discharge from your frame on your PC can do that. Normally you need to update the complete trackpad module to fix this.
Cable disconnect or connector trouble:
Your trackpad is usually linked to an important board the use of a flat cable. When you have recently opened your computer or you've got dropped it or any form of liquid surpassed internal your pc, then there are desirable chances that the cable is the reason. To repair, a certified technician otherwise you (along with your obligation) ought to open the PC and see if the cable is loose, connector pins are bloodless soldered.
Flat cable pressure lost problem:
Also observe that flat cables can be without difficulty unfastened their connection sincerely because there is not sufficient strain on them. For the duration of time, the rubber fabric at the back of the cable gets more difficult and can't position sufficient pressure, fixing its miles very absolutely, add a piece of paper at the back of it to feature stress. The very sign of this is when your trackpad starts running when you bump on it.
Bodily pressure from inside:
This could be especially true if you are the usage of apple laptops. Battery swelling is not unusual trouble for those laptops and might not note its miles happening at first. Look at the frame and you will see it is slightly reshaped. You need to open your computer and update the battery as soon as possible before its harm is greater.
Software program issue:
You can delete the device driving force of the trackpad with the aid of coincidence. Go to your device supervisor and make certain that the trackpad device is there or attempt to reinstall it to look if it makes any distinction.
  Reply
That could take place for a lot of reasons:

Hardware fail:
The controller board of your trackpad could be damaged; for instance, A static discharge from your frame on your PC can do that. Normally you need to update the complete trackpad module to fix this.
Cable disconnect or connector trouble:
Your trackpad is usually linked to an important board the use of a flat cable. when you have recently opened your computer or you've got dropped it or any form of liquid surpassed internal your pc, then there are desirable chances that the cable is the reason. To repair, a certified technician otherwise you (along with your obligation) ought to open the PC and see if the cable is loose, connector pins are bloodless soldered.
Flat cable pressure lost problem:
Also observe that flat cables can be without difficulty unfastened their connection sincerely because there is not sufficient strain on them. For the duration of time, the rubber fabric at the back of the cable gets more difficult and can't position sufficient pressure, fixing its miles very absolutely, add a piece of paper at the back of it to feature stress. The very sign of this is when your trackpad starts running when you bump on it.
Bodily pressure from inside:
This could be especially true if you are the usage of apple laptops. Battery swelling is not unusual trouble for those laptops and might not note its miles happening at first. Look at the frame and you will see it is slightly reshaped. You need to open your computer and update the battery as soon as possible before its harm is greater.
Software program issue:
You can delete the device driving force of the trackpad with the aid of coincidence. Go to your device supervisor and make certain that the trackpad device is there or attempt to reinstall it to look if it makes any distinction
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Lifting Trackpad p3pp3r 7 2,381 03-23-2021, 05:48 PM
Last Post: Timpanogos Slim
  No keyboard & trackpad leads to no display. RMA from the US. Free parts in Seattle BitterPine 4 1,487 12-30-2020, 06:14 AM
Last Post: BetteHoward
  Safe to Update? BluBombr64 6 1,030 12-18-2020, 11:59 AM
Last Post: BluBombr64
Bug [Fixed] Issue with mesa-git (Manjaro ARM Stable Update 2020-09-22)) JasonG-FR 20 5,361 12-12-2020, 05:09 AM
Last Post: mogwai
  For sale: Pinebook Pro from the first batch, with the 128 Gb update Linux-Rob 8 3,114 10-07-2020, 12:03 PM
Last Post: Linux-Rob
  Proper way to use mrfixit update bastafari 13 3,181 09-29-2020, 09:45 PM
Last Post: wdt
  Do I need the touchpad update? Paulie420 3 1,292 09-22-2020, 06:40 PM
Last Post: Paulie420
  brick after firmware update on emms sashka_amur 4 1,301 09-22-2020, 02:24 AM
Last Post: sashka_amur
  Does this plastic trackpad cover come off? Paulie420 7 1,894 09-17-2020, 02:29 AM
Last Post: KC9UDX
  Mouse drfting when using the trackpad jcarty 1 738 09-15-2020, 03:21 PM
Last Post: ab1jx

Forum Jump:


Users browsing this thread: 2 Guest(s)