IME layouts (Gujarati Inscript, etc.) send no KeyDown from Deskflow

[anasvhora284]

XKB layouts (Russian, Gujarati Phonetic, etc.) work: Deskflow sends a KeyID and we inject Unicode or a physical shortcut.

IME layouts such as GNOME IBus Gujarati (Inscript) do not. The host IME consumes the key before Deskflow/libei. Input Leap skips keyid == 0 (NoSymbol), so the Android client never receives a KeyDown. Logcat from a 2026-08-26 device test showed ~35s on the phone with zero letter events, then Phonetic 0x61 (a) and Russian 0x444 (ф) plus Ctrl+A working.

This is not a client keymap gap. Input Leaf cannot invent keys the server never sent.

Workaround: use an XKB source (e.g. Indian → Gujarati / in(guj)), not IBus gu. Restart Deskflow after switching.

Possible later work (host/Deskflow): forward physical KeyButton even when the keysym is NoSymbol, or capture keys before the IME. Same class of failure for other IBus/fcitx Indic (and similar) layouts.

Tracked out of #5 / #22 so that PR can merge.

[anasvhora284]

Resolved in #44 (v1.4.2) via Shizuku / UHID physical keyboard emulation.

Reproduction Background:

When using an IME-based layout on the host computer (such as GNOME IBus Gujarati Inscript), the host IME intercepts and consumes the keystroke before Deskflow/libei can capture it. Deskflow receives keyid == 0 (NoSymbol) and never sends a KeyDown event across the network, making it impossible for the client to receive the key.

How It Is Resolved:

PR #44 attaches a real kernel UHID keyboard (HidKeyboard.kt) via Shizuku when entering the phone screen. Because Android identifies this as a genuine physical hardware keyboard:

1. Host Setup: Keep your host computer's keyboard on default standard English / QWERTY so Deskflow sends every physical key event without host IME interference.
2. Phone Setup: On your Android phone, go to Settings → System → Languages & input → Physical keyboard → Gboard and add the layout of your choice (e.g. Gujarati Inscript, Phonetic, Hindi, etc.).
3. Typing: When you type on your computer, the raw hardware scancodes are passed straight through to Android, and Gboard handles the IME layout mapping directly on the phone.

Tested and verified working for Gujarati, Russian, Chinese, and other layouts.