Pinebook Pro Revised Keyboard Firmware

[linusfargo]

I'm still diggin into the touchpad interfacing, but I think I've had some luck in making it a bit more usable with the current firmware by adjusting the MinSpeed of the driver:

Code:

synclient MinSpeed=0.25

This seems to make it a little more natural to grab window corners (for me).

This is an awesome bit of kit. Absolutely improves corner grabbing. Do you now if this setting will be saved on reboot? If not, is there a config file to modify, or do I just add it to a start up script? Honestly thanks again for this find.

[Solra Bizna]

synclient changes aren't persistent, you'll have to run the command every time you log in. (Also, synclient is only effective under X11, not Wayland.)

[jackhumbert]

I'm still diggin into the touchpad interfacing, but I think I've had some luck in making it a bit more usable with the current firmware by adjusting the MinSpeed of the driver:

Code:

synclient MinSpeed=0.25

This seems to make it a little more natural to grab window corners (for me).

This is an awesome bit of kit. Absolutely improves corner grabbing. Do you now if this setting will be saved on reboot? If not, is there a config file to modify, or do I just add it to a start up script? Honestly thanks again for this find.

synclient changes aren't persistent, you'll have to run the command every time you log in. (Also, synclient is only effective under X11, not Wayland.)

I'm not sure if it's the recommended way, but adding this to /etc/X11/xorg.conf worked for me (in X11):

Code:

    Section "InputClass"
        Identifier "touchpad catchall"
        Driver "synaptics"
        MatchIsTouchpad "on"
        MatchDevicePath "/dev/input/event*"

        Option "MinSpeed" "0.25"
    EndSection

I don't have any experience with Wayland - if someone is able to configure this with Wayland, please share!

[xmixahlx]

I am on sway/wayland/mesa-git and don't have any issues with the trackpad at all. honestly it has been difficult understanding exactly what the issues are experienced by others.

using revised keyboard update and added input block to sway config for touchpad have been my changes.

the only annoyance I have is avoiding use of tty3 due to F3 acting wonky with the revised keyboard firmware.

[Arwen]

...

I'm not sure if it's the recommended way, but adding this to /etc/X11/xorg.conf worked for me (in X11):

Code:

Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"

Option "MinSpeed" "0.25"
EndSection

I don't have any experience with Wayland - if someone is able to configure this with Wayland, please share!

Perfect. I've added both this and the "synclient MinSpeed=0.25" to the Wiki;

Wiki - Pinebook Pro - X-Windows trackpad tuning

As usual, feel free to correct, improve or comment, (good or politely bad).

[tllim]

@jackhumbert -  I have updated ANSI keyboard before (with oem files). Can I just run last step of your instructions - ./updater flash-kb-revised ansi ?

Yeap! `sudo` should be needed I think.

If you have any bug reports or suggestions for other features, feel free to open an issue/PR in the repo, or discuss things here!

I'd be happy to test out a dvorak mapping, or even generate one if needed -- I recently built a keyboard, and having hardware dvorak is really nice.

The documentation says the .asm files aren't -- does that apply to the .a51 files?

Having a comprehensive way of remapping keys would be awesome, particularly if it could be as easy as Soarer's converter for simple mods, but with the ability to do more ornate mappings (Fn-key, maybe even layers) as well.

I've started converting these assembly-ish files into c code and keymaps that can actually be compiled with sdcc: https://github.com/jackhumbert/pinebook-...c/keymaps/ - hopefully the format I have here makes sense. This branch isn't thoroughly tested yet, so please be careful when thinking about flashing from `c_source` (`master` is stable). I've only created ANSI versions for now since that's all I'm able to personally test at this time. Theoretically we can create an ISO mapping using the ANSI .hex file as a base (as opposed to the ISO one), but I'm not sure if there's any other differences yet.

it'd be nice to have the updater able to flash arbitrary .hex files instead of needing to rename and recompile each time. Ideally we can have a bunch of keymaps in here for people to flash/try out based on what they want.

Please PM your address, phone number and email address (for shipping purpose). I will ask shipping team to dispatch an ISO PBP to you. Thanks on the awesome task. On the trackpad info, I will try to get more info from trackpad vendor.

[jackhumbert]

Please PM your address, phone number and email address (for shipping purpose). I will ask shipping team to dispatch an ISO PBP to you. Thanks on the awesome task. On the trackpad info, I will try to get more info from trackpad vendor.

That would be awesome! Just shot you an email I think I have a lot of the trackpad interface (within the keyboard firmware) figured out - I don't know how much is customisable outside the trackpad itself, but maybe configuring it at the OS level will be sufficient.

[Solra Bizna]

Please PM your address, phone number and email address (for shipping purpose). I will ask shipping team to dispatch an ISO PBP to you. Thanks on the awesome task. On the trackpad info, I will try to get more info from trackpad vendor.

!!!!

Glad I've hitched my cart to the Pine64 horse... that is just not the sort of thing that happens in a proprietary ecosystem. Now I can look forward to custom keymaps on my ISO PBP too...!

I think I have a lot of the trackpad interface (within the keyboard firmware) figured out - I don't know how much is customisable outside the trackpad itself, but maybe configuring it at the OS level will be sufficient.

I know my problem [probably] won't be solved through synclient alone. MinSpeed=0.25 does help slightly, but the temporal displacement is still a major pain. I looked at the other options and didn't see anything relevant. I'm almost totally sure that mine is a problem only with a few specific units. If it were possible, I'd purchase another trackpad to see if replacing the hardware makes my problem go away.

[ssfrfr@]

it'd be nice to have the updater able to flash arbitrary .hex files instead of needing to rename and recompile each time. Ideally we can have a bunch of keymaps in here for people to flash/try out based on what they want.

I modified colmak_ansi.c into dvorak_ansi.c, and it works fine so far.

How would you like contributions submitted?

(Oh, we can attach files.  Attached.)

[jackhumbert]

I modified colmak_ansi.c into dvorak_ansi.c, and it works fine so far.

How would you like contributions submitted?

(Oh, we can attach files.  Attached.)

Nice! I'm not sure how familiar you are with Github, but you can create a fork and pull request to the repo: https://github.com/jackhumbert/pinebook-...rc/keymaps - if you make once you add it, you can add the .hex file to the repo too.