-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Joystick intermittently stops working #134
Comments
Can you try the udev driver? This can be found in the add-on's settings or the Driver Settings button in System -> Input settings. Also let me know if you run into this issue. |
Thanks for the quick response, I tried the udev driver now and it is practically unusable for me. I do run into the issue you referenced. The controller is a) not auto detected when using the udev driver and b) I can when manually binding the controls not bind all the analog axis. I further tried debugging this problem now. It appears that its both a controller and a kodi issue in the end. The controller itself goes into a suspend mode after a while, meaning that it won't send its inputs to linux anymore. I might have to play around with bluetooth suspend settings to mitigate that. If you hard reset the controller then, by disconnecting and reconnecting immediately, it appears the kodi addon does not do well with that happening as it then produces those errors. If you leave it disconnected for a while ( a couple of seconds ) the errors don't seem to happen. |
I have a sixaxis I can test with. My plan is to finish the player manager, then address the remaining joystick drivers I plan to finish (udev, steamcontroller, xarcade, etc). |
still running into this issue with my steam controller:
|
This looks like an OS problem. Error 19 is Given that it's a wireless controller, the wireless connection is most likely the problem. Can you try connecting the controller via wire? It could also be a Linux problem. Can you try switching from the Linux Joystick API driver to the udev driver? Finally, if the issue persists, perhaps we can work around it with some reconnect logic. |
Thanks for the fast response will try that! |
Yeah udev works better it seems, the controller still dissapears but is found again:
|
Check It's good that udev reconnects. The Linux joystick driver should also reconnect, but I'd eed to get ahold of a faulty controller for testing. |
Yeah maybe its my raspberry pi5 it sucks with bluetooth controllers too and sucks with my steam deck controller :) |
I've been mired in RPi 5 problems for two weeks now. There's lots of development in side branches, and RPi 5 fixes are frequently being merged. I suggest updating all firmware and OS versions. If weak controller connectivity is still an issue, we can take this thread to the LibreELEC forum. |
So I'm quite happy in general how easy it is to set up a joystick right now. The main problem I'm facing is that it will sometimes without warning stop working in kodi leaving this in the log:
00:20:32.214 T:139691099584256 ERROR: AddOnLog: Joystick Support: ScanEvents: failed to read joystick "Wireless Controller" on /dev/input/js0 - 19 (No such device)
00:20:33.031 T:139691110160128 ERROR: Previous line repeats 49 times.
With varying amounts of repeats. This persists until I reconnect the joystick.
jstest or other utilities keep seeing the joystick just fine and work as expected. The device /dev/input/js0 in that case was also there and responding as it should.
Any clue how I can help to triage this?
Joystick was a Dualshock 4 paired over Bluetooth
The text was updated successfully, but these errors were encountered: