DeeJanuzandClaude Opus 5.5 57617d4a14 ft-powerd: ask SteamVR every 100 ms, not on every input event ...

The loop polled the input devices with a 100 ms timeout and then, on every wake, did
SteamVR's part: PollNextEvent, the headset's activity level and every device's pose, all
IPC calls to vrserver. Input wakes it at once so the displays come on with the first
key or motion, but a moving mouse sends hundreds of events a second, so moving the mouse
meant hundreds of rounds of IPC a second instead of 10.

Every wake still drains the input devices and the control socket and counts input as
use straight away; SteamVR's part, and the backlight read that goes with it, now run
only when 100 ms have passed since the last time, and poll sleeps until then. Built in
the dev container (power/build.sh, no warnings); not run, since the live ft-powerd holds
@ft_powerd.

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

2026-10-03 09:19:49 -06:00

..

build.sh

Turn the displays off while the headset isn't used, and keep it awake on a charger

2026-09-29 09:34:34 -06:00

frametop-power.service

Turn the displays off while the headset isn't used, and keep it awake on a charger

2026-09-29 09:34:34 -06:00

ft-powerd.cpp

ft-powerd: ask SteamVR every 100 ms, not on every input event

2026-10-03 09:19:49 -06:00

run.sh

Installers: ask for sudo in the terminal, and cope with SteamVR off

2026-10-01 15:04:49 -06:00