[d0dger]

Hi,

I´m not sure if this is an OE issue or Kodi... but maybe someone is able to point me to the right direction:

I´m using:
Asrock Beebox
Microsoft XBox 360 Wireless Controller
Fresh OE 6.0.0 Final Install

The Gamepad is identified properly I can use the Controller for Navigation using the d-pad (lower left) BUT: every input is executed twice. E.g. when I press left, it jumps two items to the left.
No matter how fast or slow I press the key, even if I try to hold it down (thought the "key up" might get recognized as second input) it doesnt matter.

A single press looks like:

19:47:19 T:140347836434304 DEBUG: Joystick 0 hat 1 value 8
19:47:19 T:140347836434304 DEBUG: Joystick 0 button 12 Down
19:47:19 T:140347836434304 DEBUG: Joystick 0 hat 1 hat centered
19:47:19 T:140347836434304 DEBUG: Joystick 0 button 12 Up


But I´m unsure how the keymap-configuration with "hat" etc. works in detail, therefore I´m afraid to fiddle on my own....

I also tried to disable mouse/keyboard support etc., but without any success

So, what I´m doing wrong ? Here are my full logs:
dmesg: sprunge.us/DLXK
kodi.log: sprunge.us/dRGe

I hope someone has an advice what to try...

[iskonje]

I can't help you but i'm in the same situation with my OE 6.0 on my Asrock ION 330 and wireless xbox controller.

I think the issue came out with kodi 15.x ... the strange thing is that in retroarch and in games dpad is responding well.

Still searching for a solution !

[d0dger]

Currently I´m running the EGL-Build from http://forum.kodi.tv/showthread.php?tid=231955 on my Asrock Beebox. But even with Jarvis the problem remains, the xbox 360 wireless always double-triggers the input from d-pad

No one an idea how to tackle this problem ?

[d0dger]

So, might this be a candidate for a bug tracker entry ?
Or has anyone running this setup without problems and we are just doing something wrong ?

[chamonix]

I also have this problem on my Intel NUC6i5SYH and Xbox 360 Wireless Controller.

Because it is relatively new hardware (Feb 2016) the current stable OpenELEC builds don't work with the GPU so I've been using these builds:

OpenELEC-Generic.x86_64-6.0.198-Intel_EGL.img
OpenELEC-Generic.x86_64-7.0-Milhouse-20160214232831-#0214-ga9bb95e

The debug.log shows the following messages after a single press D-pad right button, but the focus moves two places on the GUI. This happens for all D-pad buttons on any menu:

14:59:47 2411.561523 T:140520364824640 DEBUG: Joystick 0 hat 1 value 2
14:59:47 2411.561523 T:140520364824640 DEBUG: Joystick 0 button 13 Down
14:59:47 2411.630371 T:140520364824640 DEBUG: Joystick 0 hat 1 hat centered
14:59:47 2411.630371 T:140520364824640 DEBUG: Joystick 0 button 13 Up

I thought maybe Kodi was registering a 'hat' and 'button' from the same button press and carrying out two actions, but I'm not sure. I've tried commenting out the hat definition in the global section of my copy in /storage/.kodi/userdata/keymaps/joystick.Microsoft.Xbox.360.Controller.xml but it made no difference.

I'm using the same controller on Windows with Jarvis and there is no problem there.

[Matt Devo]

submitted an issue to capture this: https://github.com/OpenELEC/OpenELEC.tv/issues/4746

[chamonix]

I did some additional testing using the same hardware with Ubuntu 15.10 and Kodi version 15.1 from the repository, and the Xbox 360 controller worked fine.

Here is an excerpt from the debug.log for the same D-pad actions.

16:23:45 T:140683275598016 NOTICE: Enabled Joystick: Xbox 360 Wireless Receiver
16:23:45 T:140683275598016 NOTICE: Details: Total Axis: 6 Total Hats: 0 Total Buttons: 15

16:23:47 T:140683275598016 DEBUG: Joystick 0 button 13 Down
16:23:47 T:140683275598016 DEBUG: Joystick 0 button 13 Up
16:23:47 T:140683275598016 DEBUG: Joystick 0 button 13 Down
16:23:47 T:140683275598016 DEBUG: Joystick 0 button 13 Up
16:23:48 T:140683275598016 DEBUG: Joystick 0 button 13 Down
16:23:48 T:140683275598016 DEBUG: Joystick 0 button 13 Up

Going back to OpenELEC-Generic.x86_64-7.0-Milhouse-20160214232831-#0214-ga9bb95e, this is how it sees the Xbox 360 controller:

16:38:19 5.696664 T:140316764162112 NOTICE: Enabled Joystick: Xbox 360 Wireless Receiver
16:38:19 5.696685 T:140316764162112 NOTICE: Details: Total Axis: 6 Total Hats: 1 Total Buttons: 15

It sees 1 Hat whereas Ubuntu 15.10/Kodi 15.1 sees no hat.
This may help explain why Kodi on OpenELEC is doing two actions for each D-pad press - a button action and a hat action.

I presume Kodi is picking up the controller device from the Linux kernel, but I don't know why it would be seeing it differently. Perhaps someone can chip in with some ideas, as I've kind of reached the limit of my knowledge in this area.

[chamonix]

Milhouse put out a new release yesterday (#0221) which resolves the issue. It uses a new version of libinput and kernel 4.4.2.

There are some new errors in the debug.log but the controller is working correctly now. The formatting of events in the log has changed too.

18:03:34 6.930527 T:139898636937280 ERROR: Window Translator: Can't find window joystickfamily
18:03:34 6.930565 T:139898636937280 ERROR: Previous line repeats 1 times.
18:03:34 6.930570 T:139898636937280 ERROR: Joystick Translator: Can't find button button
18:03:34 6.930619 T:139898636937280 ERROR: Previous line repeats 14 times.
18:03:34 6.930623 T:139898636937280 ERROR: Joystick Translator: Can't find button axis
18:03:34 6.930635 T:139898636937280 ERROR: Previous line repeats 9 times.
18:03:34 6.930637 T:139898636937280 ERROR: Joystick Translator: Can't find button hat
18:03:34 6.930686 T:139898636937280 ERROR: Previous line repeats 3 times.
... repeated

18:03:46 17.078581 T:139898040841984 NOTICE: Register - new joystick device registered on addon->peripheral.joystick/0: Xbox 360 Wireless Receiver
18:04:35 66.005585 T:139898636937280 NOTICE: Log level changed to "LOG_LEVEL_DEBUG_FREEMEM"
18:04:35 66.005684 T:139898636937280 NOTICE: Enabled debug logging due to GUI setting. Level 2.
18:04:35 66.006180 T:139898636937280 DEBUG: ------ Window Init () ------
18:04:35 66.175232 T:139898032449280 DEBUG: Button [ 0 ] on Xbox 360 Wireless Receiver released
18:04:35 66.175346 T:139898032449280 DEBUG: Feature [ a ] on game.controller.default released
18:04:36 67.210419 T:139898040841984 INFO: AddOnLog: Joystick Support: CJoystickInterfaceLinux::Initialize: opening joystick /dev/input/js0
18:04:36 67.308281 T:139898032449280 DEBUG: Button [ 11 ] on Xbox 360 Wireless Receiver pressed
18:04:36 67.308395 T:139898032449280 DEBUG: Feature [ left ] on game.controller.default pressed
18:04:36 67.308510 T:139898032449280 DEBUG: Joystick button event handled
18:04:36 67.408279 T:139898032449280 DEBUG: Button [ 11 ] on Xbox 360 Wireless Receiver released
18:04:36 67.408379 T:139898032449280 DEBUG: Feature [ left ] on game.controller.default released
18:04:37 68.708374 T:139898032449280 DEBUG: Button [ 13 ] on Xbox 360 Wireless Receiver pressed
18:04:37 68.708496 T:139898032449280 DEBUG: Feature [ up ] on game.controller.default pressed
18:04:37 68.708565 T:139898032449280 DEBUG: Joystick button event handled

[Matt Devo]

Milhouse put out a new release yesterday (#0221) which resolves the issue. It uses a new version of libinput and kernel 4.4.2.

while Milhouse's build does appear to be fixed, it's not libinput and the 4.4.2 kernel alone that are responsible, as both of those have been merged into OpenELEC's master branch (which will eventually become the Kodi 16.0 / OE-7 release) and that still has the duplicate issue.

[davidaq]

Did anyone ever find a fix for this that didn't involve using a development build (which don't seem to play nicely with various skins)?

I've noticed if you hold down any button you can then use the d-pad as normal.

But short of mapping a button to do nothing and then physically taping it down on the controller, I've not been able to find a fix.

really frustrating problem, especially considering this used to work in older version of openelec.

[ntoenis]

Not to beat a dead horse and bring this old thread back, but has one ever found a solution for this bug? I too am still experiencing this issue.

[gooie]

I need to keep beating the horse.
The erratic xbox 350 wireless controller on Windows 10 with Kodi 18.1 persists.
Most dramatic issue is D-Pad and A buttons still double tapping through menu so you can never reach the place you need.

I've also looked through forums & not found solution.
It's started for me after rebuilding my Alienware Alpha after Hivemind support withdrawl.
 - Reinstalled latest Win 10
 - reinstalled latest Xbox 360 Wireless Controller & Receiver drivers
 - have also tried installing latest Kodi 18.2
 - Have checked Kodi Add-on/Peripheral lib/Joystick support enabled
 - Have tried all combinations of Kodi System/Input - Peripherals-Driver settings-Configure Controllers
 - Have tried all combinations of enabling Win 10 device drivers incl. HID devices & Xbox 360 devices
 - Have tried disabling legacy Alpha mouse driver
........ problem still persists

Losing hair rapidly now..... any assistance appreciated... even if just confirming that no solution to this problem was ever found.
If so, what work around has kept you using Kodi?
thanks guys, Gooie

[asavah]

I need to keep beating the horse.
The erratic xbox 350 wireless controller on Windows 10 with Kodi 18.1 persists.

You're beating a wrong horse.
Do you realize that this is an old OE (which is linux) thread?
Since your problem is on windows I'd suggest you make a new topic on windows subforum and provide a link to a proper debug log reproducing the problem.