Has anyone switched to the userspace keyboard driver on Manjaro ARM?

[undata]

Okay, here is what finally worked for me.  I started with MajaroArm with all updates.  I also installed from the software app (Phosh) pinephone-keyboard-git and pinephone-toolkit-git, which may have helped.  I did not have to do any building of the userland driver, so an update may have already provided it, or maybe one of the git files I mentioned. Whatever, it already existed at the proper location when I started this.



Here are all of the exact steps I took:

1. Create systemd file

  a. Navigate  to /etc/systemd/system

  b. sudo nano keeb2.service (use whatever name you like before the ".service")

  c.In file, type:

 

  [Unit]
  Description=PinePhone keyboard userspace daemon
 
  [Service]
  Type=simple
  ExecStart=/usr/bin/ppkb-i2c-inputd
 
  [Install]
  WantedBy=multi-user.target
 
 
d. Save and exit Nano

 
2. Enable service for next boot

  a. Run: sudo systemctl enable keeb2.service


3. Set up boot.txt file to disable kb151

  a. cd /boot

  b. sudo nano boot.txt

  c. Type kb151.disable_input at the end of setenev bootargs line (there should be one space between last parameter in the line and this addition).

  d. save and close.


4. Create the new boot.scr from the boot.txt file to apply disabling kb151 at next boot.

  a. Run: /usr/bin/pp-uboot-mkscr

 

5. Reboot

This worked for me with MajaroArm. I have F1-F10 working with the pine key, and Fn-num keys actually type what is printed on the lower part of the keys.

I potched this together from different sources, (the link in the first post and the very helpful comments in this thread) and a lot of exploring to see where files were actually located and if I had them.  Many thanks to @Megamemnon and @neil_swan80, as well as another not on this forum.  And, of course, thanks to the ManjaroArm devs.

Hope this helps someone else.

It didn't work for me. No offense, but you started out saying "I did not have to do any building of the userland driver, so an update may have already provided it, or maybe one of the git files I mentioned." You followed that by saying "Here are all of the exact steps I took:" How is it possible that those were ALL of the exact steps as listed, if you weren't sure whether previous steps had any impact?

Okay. Well, nearly a year later, as you probably can tell if you read the whole thread, it kept breaking, so not all that surprising it didn't work for you. I gave up.  I no longer have a Pinephone  or keyboard case, so it's all kind of moot.  Lol.

You're right. Still, I have solved this frustrating problem. Using only gsettings. I will share my work, if anybody cares about the details. I just bought the keyboard in 2023. Had I known the problem I wouldn't have bought it. But after a lot of extremely tedious work, here it is (link to photographic evidence):
https://drive.google.com/file/d/12wBDZ9M...sp=sharing