XBOX One Controller not working in newest builds

Libretro Lakka
#1

I’ve just upgraded from ‘Lakka-Generic.i386-devel-20160206091726-r21311-geaf46ad’ to the latest nightly build (Lakka-Generic.i386-devel-20160403051253-r21394-g25646a6). Before the upgrade my XBOX One controller was working just fine, the white home button came on and everything was fine.

After the upgrade it no longer works, when I plug it in I get the message at the bottom left of the screen saying its been detected but the home button does not light up and none of the controls work.

From the log I get the following but nothing to indicate that something has gone wrong:

RetroArch [INFO] :: [udev]: Hotplug add: /dev/input/js0. RetroArch [INFO] :: [udev]: Hotplug add: /dev/input/event18. RetroArch [INFO] :: [udev]: Plugged pad: Microsoft X-Box One pad (045e:02d1) on port #0. RetroArch [INFO] :: Autodetect: 106 profiles found RetroArch [INFO] :: Autodetect: selected configuration: /tmp/joypads/udev/Microsoft_X-Box_One_pad.cfg RetroArch [INFO] :: [udev]: Pad #0 (/dev/input/event18) supports force feedback. RetroArch [INFO] :: [udev]: Pad #0 (/dev/input/event18) supports 16 force feedback effects.

Is anyone else having similar problems? I’ve just done a fresh install from scratch just in case I had config problems but that didn’t make any difference. I also tried reverting back a few versions, but no joy, it seems the problem starts with ‘Lakka-Generic.i386-devel-20160221190531-r21328-g13640c2’ for me.

My controller still works with the latest version of libreelec which should be close enough to openelec to make no difference at this point.

Reverting back to my old version of Lakka has got me back up and running but I’d obviously like to keep upto date with improvements.

For reference I am using the Generic i386 build on an ION 330.

Thanks

#2

Hi,

We have updated kernel to 4.4.2 for Generic (March 2nd). So it is maybe related to the xpad module ? Libreelec is using kernel 4.4.6 with this patch.

Can you try to check the log with journalctl ? And if you try to rebind, it doesn’t work ?

#3

Thanks for the response, I’ve just taken a look at journalctl, it doesn’t seem to be reporting a problem:

Apr 09 21:08:57 Lakka kernel: usbcore: registered new interface driver xpad … Apr 09 21:10:16 Lakka kernel: usb 3-1: USB disconnect, device number 2 Apr 09 21:10:18 Lakka kernel: usb 3-1: new full-speed USB device number 3 using uhci_hcd Apr 09 21:10:18 Lakka kernel: input: Microsoft X-Box One pad as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/input/input22

How do I rebind?

#4

Settings tab > Input > Input User 1 Binds > User 1 Bind All

#5

Hi, I’ve just given that a try, none of the button presses on the controller were detected at all. The logs didn’t give me anything extra while I was rebinding either:

journalctl: Apr 10 12:46:41 Lakka kernel: usb 3-1: new full-speed USB device number 2 using uhci_hcd Apr 10 12:46:41 Lakka kernel: input: Microsoft X-Box One pad as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/input/input21 Apr 10 12:47:26 Lakka kernel: usb 3-1: USB disconnect, device number 2

console: RetroArch [INFO] :: [udev]: Hotplug add: /dev/input/js0. RetroArch [INFO] :: [udev]: Hotplug add: /dev/input/event18. RetroArch [INFO] :: [udev]: Plugged pad: Microsoft X-Box One pad (045e:02d1) on port #0. RetroArch [INFO] :: Autodetect: 106 profiles found RetroArch [INFO] :: Autodetect: selected configuration: /tmp/joypads/udev/Microsoft_X-Box_One_pad.cfg RetroArch [INFO] :: [udev]: Pad #0 (/dev/input/event18) supports force feedback. RetroArch [INFO] :: [udev]: Pad #0 (/dev/input/event18) supports 16 force feedback effects. RetroArch [INFO] :: [KMS]: Missed 23 VBlank(s) (Frame: 1880, DRM frame: 5035). RetroArch [INFO] :: [udev]: Hotplug remove: /dev/input/js0. RetroArch [INFO] :: [udev]: Hotplug remove: /dev/input/event18.

is this something that will fix itself eventually when the latest code from openelec is merged?

#6

Yes it should fix it. Please follow this issue for update.

#7

Thanks, I’ll watch that issue. I had seen that issue before but assumed it was something different since my controller was working a little over month ago.

Thanks again.