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 !

[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.

[Tech-User42]

I updated today in the latest 7.1 i got an issue with a wireless carplay which plug into a wired carplay adapter, in 6.7 it worked flawlessly but now it throw me an error from gstreamer, when i unplug the wireless adpater and the plug the iPhone it works ;)

00:00:00.362 [INFO] [wayland] unable to lock lockfile /run/user/1000/wayland-0.lock, maybe another compositor is running
00:00:00.363 [INFO] [backend/wayland/backend.c:450] Starting Wayland backend
00:00:00.389 [INFO] [../livi-compositor.c:1179] livi: new output -> screen 'main' at x=0 (1280x720)
00:00:00.440 [INFO] [../livi-compositor.c:1726] livi: control socket at /run/user/1000/livi-compositor.ctrl
00:00:00.444 [INFO] [../livi-compositor.c:1899] Running livi-compositor on WAYLAND_DISPLAY=wayland-1
[GstVideo] GStreamer 1.26.2
[ProjectionService] GStreamer codecs: h264(hw=true sw=true) h265(hw=true sw=true) vp9(hw=false sw=true) av1(hw=false sw=false)
[ProjectionService] hevc support: true
[1106:0612/164842.097748:ERROR:media/gpu/vaapi/vaapi_wrapper.cc:1658] vaInitialize failed: unknown libva error
[1106:0612/164842.116675:ERROR:ui/ozone/platform/wayland/gpu/wayland_surface_factory.cc:252] '--ozone-platform=wayland' is not compatible with Vulkan. Consider switching to '--ozone-platform=x11' or disabling Vulkan
00:00:04.779 [INFO] [../livi-compositor.c:1318] livi: app_id='dev.f-io.livi' title='LIVI' tag='' -> ui on screen 'main'
[TelemetrySocket] Server listening on port 4000
[USBService] Dongle was already connected on startup
[USBService] startup scan: 3 USB devices on bus: vid=0x1314 pid=0x1520 cls=0x0, vid=0x2109 pid=0x3431 cls=0x9, vid=0x781 pid=0x5567 cls=0x0
00:00:06.035 [INFO] [../livi-compositor.c:1414] livi: request_fullscreen=1 screen 'main' output 800x480
[kiosk] enter: screen=800x480 workArea=800x480 window=800x480
[USBService] Dongle disconnected
[USBService] attach vid=0x1314 pid=0x1520 cls=0x0 → dongle=true accessory=false phoneCandidate=false lastPhone=false
[USBService] Dongle connected
[DongleDriver] Link established
[Perf] AppStart→FirstFrame: 41441 ms
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
> Warning:          Could not resolve keysym XF86KbdInputAssistPrevgrou
> Warning:          Could not resolve keysym XF86KbdInputAssistNextgrou
Errors from xkbcomp are not fatal to the X server
[gst-host] ready, running main loop
[gst_video] codec=h264 decoder=v4l2h264dec | appsrc name=src is-live=true do-timestamp=true format=time min-latency=0 max-latency=0 caps=video/x-h264,stream-format=byte-stream ! h264parse ! queue max-size-buffers=0 max-size-bytes=0 max-size-time=2000000000 ! v4l2h264dec name=dec ! queue max-size-buffers=2 max-size-bytes=0 max-size-time=0 leaky=downstream ! waylandsink name=sink sync=false
[gst_video] ERROR from src: Internal data stream error. | ../libs/gst/base/gstbasesrc.c(3187): gst_base_src_loop (): /GstPipeline:pipeline0/GstAppSrc:src:
streaming stopped, reason not-negotiated (-4)

But app seams smoother too, maybe a deps/config problem on my RPI 4 ?
Do you have a "config type" (OS Version,Installed Packages) to recommend to try t? (anything not in the install script)

If you want i can open an issue regarding the gstreamer error

[f-io]

Sorry, I had to re-read your log. There is something odd (reason not-negotiated), because the dongle always sends the same bitstream and it is unclear why it fails to negotiate in this chain.

I double-checked with a CPC200 plus a wired-to-wireless adapter, and it worked on my test setup (Pi 5). As soon as I use a Pi 4 I can reproduce the error. I will need some time to investigate, this is kind of an edge case.

[f-io]

solved with v7.1.1