Dynamic Touch Keyboard & System Optimization

[Tech-User42]

Hi,
Im trying to create a "perfect" infotainment system with the help of LIVI (Boot optimization, Auto Start Stop, etc...) and im trying to get a dynamic virtual keyboard, same behavior as Android or IOS when we click a filed it bring on the Keyboard.

I have tried so far onboard and matchbox-keyboard, and none works as intended 😅.

Im running LIVI on a RPI4 running RPI OS Lite with a lot of service packages disabled/deleted to optimize the boot process.

If anyone have an idea of how to achieve that it would be great !

P.S What a great piece of software 😉

[f-io]

Hi @Tech-User42,

the virtual keyboard is on the to-do list, but not high-prio, as you barely need any input after the initial setup.

If you're on a Pi 4, I'm sure you're going to love the new HW acceleration feature: https://github.com/f-io/LIVI/actions/runs/27076761737. That said, it's now a totally different way of displaying LIVI on Linux, so I'm not sure it'll work with your setup out of the box.

Bonne route !

[Tech-User42]

Hi,
Iv tried the hardware acceleration feature and its a game changer, without this the CarPlay is very laggy with a lag of ~1s on each input, with the HA option enabled its usable without the feeling of a GPS in 2005 😄.
For the Keyboard i agree its not a top priority, i be happy to help, i never coded electron/type script apps i could be a great experience !

[f-io]

How did you run it? Because the build I linked above is missing the correct assets, I didn’t realize that I’d patched them locally but forgotten to run the CI job that applies those changes to the repository assets used to build the self-contained images. 😅

It is already working on a pi (full desktop), now I need to fix the pi light version.

[Tech-User42]

I just run the install script pi-lite and enabled the hardware acceleration option in the settings page and it just worked ;)

[f-io]

Ah, that is not hardware acceleration. The installer will install the latest release, not 7.0.0.

This hardware acceleration flag only enables hardware acceleration on Linux (x86) and macOS. It has no effect on a Raspberry Pi (ARM Linux) due to a limitation of Google's Chrome engine. This flag does also not exist in v7.0.0, because the system will auto detect and choose HW if available.

However, version 7.0.0 no longer uses Chrome for video rendering. The video pipeline is now based entirely on GStreamer, which can utilize the Raspberry Pi's GPU. We also no longer use Chrome for display rendering, as we now use our custom nested window manager and rely on Chrome only for the UI overlay.