Skip to content

input: reconcile Android key mapping and seat modifier lifetime - #132

Draft
Leeestephen wants to merge 1 commit into
SuperTurtleDev:mainfrom
Leeestephen:fix/android-input-state
Draft

Leeestephen wants to merge 1 commit into
SuperTurtleDev:mainfrom
Leeestephen:fix/android-input-state

Conversation

@Leeestephen

Copy link
Copy Markdown
Collaborator

Summary

Expand zero-scancode Android-to-evdev mapping for ordinary injected keyboards.
Reconcile fresh MotionEvent modifier snapshots before presses while preserving
modifiers backed by real key-down events. Release pressed keys before the active
keyboard owner leaves or dies, retain lock state and ignore stale-owner leaves.

This addresses missing non-UHID keyboard input and stale Ctrl state causing
ordinary browser tab taps to act like multi-selection. Upstream's window-relative
coordinate handling from #129 is retained in the extracted branch.

Testing

The release host APK and arm64/API35 daemon build successfully against the
upstream-pinned Wayland source. Seventy-five Android key-mapping assertions pass.
An ASan/UBSan host harness executes the actual keyboard-leave and modifier
functions, covering balanced releases, stale-owner cleanup, absent resources,
lock retention and genuinely held modifiers.

The integrated predecessor passed physical typing, intentional Ctrl+tap and
ordinary tab-touch acceptance. A fresh end-to-end GUI/input pass for this exact
upstream-based extraction remains pending.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant