DeeJanuzandClaude Opus 5.5 705b434cf3 Take over the volume keys so they can't crash gamescope ...

gamescope sends volume up and down to Steam by moving keyboard focus to
Steam for the key and back. When nothing had focus, it moves focus back to
null and wlroots aborts, which ends the whole VR session. One press of the
headset's volume button did that while working in the Frametop desktop.

The input relay now handles volume keys from every device that has them,
the headset's buttons included, and steps the default output with wpctl
(5%, repeating while held). SteamVR, which passes keys on to gamescope,
never sees a volume key: devices with a keymap (gpio-keys, USB and
Bluetooth keyboards) get only their volume entries remapped to unused
codes, so the headset's click button keeps working, and pmic_resin, which
has only volume down, is grabbed. The keymaps go back when the relay
stops, and --no-grab leaves the volume keys alone.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-09-27 09:10:28 -06:00

..

frametop-input-relay.service

Fix installed service and launcher paths; wait for the pointer helper

2026-09-26 16:21:22 -06:00

input-relay.py

Take over the volume keys so they can't crash gamescope

2026-09-27 09:10:28 -06:00