Key Remapping on Wayland: What Still Works
On EM Mini Pad, five physical keys sit beside a knurled knob in a compact, weighty aluminium block supporting wired USB-C or Bluetooth. Under Wayland, its events can still be remapped, but the correct tool depends on where the rule should operate.
Why do old X11 remapping tools fail on Wayland?
Wayland clients do not share the broad global input access that many X11 utilities assumed. This isolation is part of the security model, but it means a tool designed to observe or inject keys through the X server cannot simply manage native Wayland applications.
XWayland compatibility does not turn every native window into an X11 client. A rule may appear to work in one legacy application and fail in the compositor or another program. Identify the input layer before blaming the pad.
Which tools work below the display server?
keyd uses Linux input facilities to create system-wide mappings that persist across Wayland, X11 and a text console. xremap also uses evdev and uinput, with builds and integration paths for several compositors. Both need permission to read input and create a virtual device.
Scope the configuration to the macropad rather than all keyboards. keyd monitor and xremap's device-list commands can provide identifiers. Start with an ordinary substitution, validate the configuration and keep another keyboard available for recovery.
Can device memory avoid the Wayland problem?
Yes, when the pad's documented firmware supports on-device remapping and storage. The hardware then emits the chosen key before Wayland receives it, so no desktop remapper is required for that layer. Application shortcuts still decide what the key means.
The EM Mini Pad listing does not confirm a particular firmware configurator or persistent keymap, so do not assume that route for this product. Use a Linux-side device rule unless its actual manual establishes supported on-device configuration.
What compositor-specific options remain?
Compositors provide their own global shortcuts for workspaces, focus, launching and media control. Hyprland, for example, documents current Lua binds and device filters, while other compositors use different configuration. These tools understand desktop concepts that a low-level remapper does not.
The EM Mini Pad is best divided into layers of responsibility: input substitution below Wayland, workspace actions in the compositor and editor commands in the application. Document those boundaries, test wired and Bluetooth names separately and avoid unsupported claims about firmware memory. Keep the original input event in your notes as well as the remapped output. After a compositor or kernel update, test the raw event first, the virtual device second and the application shortcut last. This sequence prevents a desktop failure from being mistaken for dead hardware.