WTware RDP client

Please try this:

http://wtware.com/testing/202412231241/ ... ry.img.zip

In Raspberry Pi Imager CHOOSE OS -> Use custom -> Choose downloaded zip file.

In terminal config file "bluetooth=wait" instead of "bluetooth=on"

"I can make workaround: tell wtware to wait until user scans something. Stop booting at black screen with "please scan one code or press Esc to boot without scanner" text and wait for input from scanner. After we see input device connected, we can run Chromium with Bluetooth HID. Will it work for you?"

That would be good if you could farm that

WTware is too limited. We cut off many standard linux features to be small. Related to this topic: there is no udev in wtware. We only statically configure input devices detected on boot for Chromium. Input devices connected after boot (even USB mouse) will not work in Chromium (but work in wtware RDP client).

I can make workaround: tell wtware to wait until user scans something. Stop booting at black screen with "please scan one code or press Esc to boot without scanner" text and wait for input from scanner. After we see input device connected, we can run Chromium with Bluetooth HID. Will it work for you?

Will Bluetooth be implemented in Chrome mode in the next versions?

Sorry, we can't use bluetooth HID in Chrome. Bluetooth HID works only in WTware RDP client.

I have sent you the log file to support@wtware.com

Logging manual:

http://wtware.com/logs.html

There is no "delete everything important and leave only single line". Log should be full, from boot to first wrong behavior. Send it to support@wtware.com if there is something personal.

We want to use a Bluetooth Scanner HID in Chrome mode. The connection is established, unfortunately he doesn't write anything in the input field. Here is the log.

[EVDEV] Unknown key 374 (0x00000176) from 'Barcode ScannerHID', '/dev/input/event8'