I'm trying to get a third party controller working.

So I've cloned the repo and built the dkms module and the controller is showing up as an interface under /dev/input/js0 - however I'm getting no input from the controller whatsoever.

Running the jstest utility brings up some info - but appears to be entirely unresponsive to any buttons pressed on the pad.

Looking at the source code, in particular xpad.c the controller should be support by vendorid and productid { 0x24c6, 0x543a, 'PowerA Xbox One wired controller', 0, XTYPE_XBOXONE },

Can anyone help?

Same Issue.

can you try again with latest master?

@paroj I did use the latest master 2 days ago. But unfortunately; I was upset by broken MS crap. SO I took them back and got 2 steam controllers today before I saw this comment. Sorry otherwise I would have pulled it down again and tested the changes.

the last 3 commits on Sep 3, 2016 improve xpad one support.
The issue probably is a new firmware on the controllers which needs the updated handling that was implemented in the last commits.

I'm encountering this same issue (the controller is recognized, but no input is detected.) I also have an earlier Power A Xbox One controller lying around which does work. I'm attaching the output of dmesg and lsusb for both.

Long story short, the two controllers have the same vendor and product ID (24c6 and 543a), but different names ('XBox ONE Pro Ex controller' works, while 'XBox ONE liquid metal controller' does not) and different endpoint addresses - {[1 out, 1 in]; [8 out, 7 in]; [3 out, 3 in]} for the working controller and {[2 out, 1 in]; [4 out, 3 in]; [6 out, 5 in]} for the non-working liquid metal controller.

I'm not familiar with the ins and outs of USB device management, but it looks as though xpad categorizes the controllers based solely on the product/vendor ID and miscategorizes the liquid metal controller. Is that accurate?

dmesg_liq_met.txt
dmesg_pro_ex.txt
lsusb_liq_met.txt
lsusb_pro_ex.txt

this is the part where the endpoints are picked: https://github.com/paroj/xpad/blob/master/xpad.c#L1566-L1582

maybe @cgutman can provide more hints.

can you try again with current master? A second init packet was added which fixed some other third party pads.

@paroj I think the endpoint selection code is definitely suboptimal but doesn't seem to have caused real problems yet (possibly by luck). The code depends on OUT endpoint being placed before the IN endpoint in the interface descriptor for all Xbox One controllers.

We know at least one controller that breaks this rule, that's the Titanfall 2 controller. Fortunately, because it uses endpoint addresses 0x81 and 0x01, the code works because the USB core masks off the 0x80 direction flag when processing the endpoint address anyway.

If a hypothetical controller had both:

• endpoint addresses that were not equal when masked by 0xF - like the Liquid Metal controller
• swapped order of IN and OUT endpoints - like the Titanfall 2 controller

Then it wouldn't work, but we don't know whether any such controller really exists. It's probably worth fixing anyway.

Thanks for looking at this! Using the current master gives the same results (i.e. the liquid metal pad is still unresponsive.)

@nderr Can you try with this xpad.c? http://pastebin.com/raw/Re8xby26

@cgutman Tried it - still no luck.

@nderr thanks for testing. Is this the controller model that isn't working? https://www.amazon.com/Official-Licnesed-Wired-Liquid-Metal-Controller/dp/B0179K5L98

@cgutman It's this one: https://www.amazon.com/POWER-WIRED-CONTROLLER-XBOX-ONE-GREEN/dp/B01KTKHVC0

Although, as noted above, the product string in a call to dmesg identifies it as a liquid metal controller.

Same problem with the same controller.

@nderr@Trevdish30 If either of you have a Windows machine accessible, please try getting us a packet capture of the official driver - https://franticrain.github.io/sniffing/index.html

I have no idea if this is right but this is what I got.

@Trevdish30 Can you try uploading it as a pcap file? I think uploading it as a txt file may have messed up the capture because Wireshark won't open it.

I tried doing it as well.
xone_liquid_metal.zip

It tells me the pcap file is empty when i try uploading it.

Please test the 'powera' branch of my repo. https://github.com/cgutman/xpad/tree/powera

@nderr@Trevdish30 I'm preparing a patch upstream to fix the PowerA gamepads. Can you try my 'for_upstream' branch? https://github.com/cgutman/xpad

If that works, may I add a 'Tested-By: Firstname Lastname Email address' from you for my submission upstream?

@cgutman just tried your powera branch and it works for me now on jstest and steam!

Sorry for the delay - I had no access to the pad until today. I've tested the for_upstream branch with jstest-gtk and everything appears to work perfectly!

@cgutman I can also confirm that your branch works with the PowerA gamepad, thanks so much for your work!

I am still getting no input on jstest or steam with the patch. could someone tell me what exactly what to do or how they go it to work so I know if I am just not doing it right or if it just doesn't work.

@Trevdish30 this is what I did, roughly, on two separate machines. I'm only 80% sure about this, it has been a few weeks. I based my instructions off of the README here: https://github.com/paroj/xpad/ and off my bash history :)

Edit: See #48 (comment) below for accurate instructions

@MDCore Thank you for your response but I am still not getting an input from the controller.