Kai Krakow

So maybe xow should initialize the dongle in paring mode? You could try adding "ExecPost=kill -SIGUSR1 $MAINPID" to the system service to see if it helps. For a start, just...

Oh sorry, my fault: It's `ExecStartPost`... After this, check `systemctl status xow` to see if the ExecStartPost line was actually executed (it would show `Process: ... ExecStartPost=... (... status=0/success)`. It...

BTW: Maybe you could try if it breaks for you because of `Type=idle`... Try to compile and install https://github.com/medusalix/xow/pull/116

Yeah, with the pull request, you no longer enable the service, it will start when udev detects the dongle (you should be able to watch this using `journalctl -f`, then...

So I'm a bit out of ideas now. You could make it work by making xow start a systemd.timer which in turn triggers the signal then. But this is only...

> I tried with the sleep Yeah, look at the output: It didn't detect `;` as a command separator, so sleep thinks the `SIGUSR1` parameter belongs to it. It may...

BTW: You may want to use `sudo systemctl edit xow.service` to add the additional lines to a separate drop-in file so they don't get overridden on update. `systemctl cat xow.service`...

The hardware supports only rumble. It's the ff-memless driver in Linux which is able to emulate periodic feedback over rumble but that's only true for kernel drivers: ff-memless is a...

You shouldn't hide the product id... It identifies the model and is important for development. Besides that: xow shouldn't show the guide nor the share button in jstest. Both buttons...

> Playing though, for example, Dragon Quest XI S demo in Proton-GE, when the pad disconnected the game would not register it again unless restarted. FYI This may be a...