Kai Krakow
Kai Krakow
I could only imagine that `while (rumbleBuffer.get(rumble))` always returns false, or the wait condition never fires.
> Just to clarify you don't actually need to plugin the device for it to work Well, Linux uses the terms cold-plug (synthetic events played back on system boot for...
Chromium has a very strange implementation of the gamepad API where it looks at evdev devices to map the buttons and axes but actually reads the input values from the...
@mundifex Could you try if https://github.com/medusalix/xow/pull/156 solves the problem for you? If it does, one of the PRs should be merged that activate the xow service on udev event.
No it's not. It's better if the commit that fixes it has a "Closes" github tag.
> I noticed there are some button mismaps This is due to the share button which MS inserted at an odd location. xow probably needs to remap it to a...
> I noticed that on the boots that were failures, systemd total boot time was listed as 5secs longer than successful boots. I assumed this was from the service type...
Also, `Type=idle` adds a 5s timeout for the service when it will start regardless of the transaction queue. Since the service has no other dependencies, "idle" will queue it right...
Latest git version may fix it. Did you try?
Does "dongle button" means "connect button on the dongle" or "connect button on the controller"? Do you need to press just that one button, or both?