@nethlem: The Xbox 360 adapter only works for Xbox 360 controllers and the Xbox One adapter only works for Xbox One controllers. Newer Xbox One controllers also support Bluetooth connections, although only for one controller per PC and with impulse trigger support disabled. I would recommend buying any Xbox One controller and an adapter.

Here's the result of running system_profiler -detailLevel full on Mac OS X. Good to know that it doesn't support 360.

Is the scope of this project locked down to 360 controllers? Or is it ok to have Xbox One specific functionality? XBOX ACC: Product ID: 0x02e6 Vendor ID: 0x045e (Microsoft Corporation) Version: 1.00 Serial Number: 310241 Speed: Up to 480 Mb/sec Manufacturer: Microsoft Inc.

Location ID: 0x14200000 / 7 Current Available (mA): 1000 Current Required (mA): 500 Extra Operating Current (mA): 0```. My thought was to use a beagle (USB packet sniffer) on a windows PC and record USB traffic to the dongle 1st sans the controller and then with.

Sent from my iPad On Nov 1, 2015, at 3:34 PM, Nat Brown wrote: i haven't yet been able to get through the XBox One dongle's initial handshake to talk through as works with XBox One wired. Anybody else have ideas/leads?

- ditto, happy to send you a dongle and/or controller if you don't have yet: natbro-at-gmail-dot-com. — Reply to this email directly or view it on GitHub. FranticRain has already got the 360 dongle working on OS X. We need to do the same for the Xbox One. (I'll assume that's what you meant). Sent from my iPad On Nov 1, 2015, at 4:48 PM, Drew Mills wrote: You really don't even need the beagle. You can just do it with Wireshark and USBPcap, but a beagle would probably work best.

If you're interested in the Wireshark method, you can check it out here. These are instructions for sniffing the Xbox One controller itself. Once you figure out the packets, its basically just an exercise in figuring out what means what and then you're good to go.

Software for mac to read ntfs. Or if you don't want to figure it all out, just send me the info and I'll try and piece it together for you. I can't guarantee it'll work though. I've never looked at the 360 wireless adapter code before.

— Reply to this email directly or view it on GitHub. Ahem, I did the original wireless 360 dongle support;P I just used the Windows driver + some USB snooper app (no idea what it was at this point, but its icon may have been Snoopy).

This didn't give me any functionality the Windows driver didn't have though (and I did use a Beagle for some things, such as to deduce wired ChatPad support). Some people with more XBox 360s to lose than me used a Beagle on the wireless dongle inside the real console to work out the off command (and perhaps Wireless chatpad support, I think someone sent the required magic code to me to make that work) as the 360 basically just contains the same thing that the dongle does to speak to the controllers. To get XBone wireless support working nicely may also require someone to disassemble (and perhaps permanently modify - assuming the same dongle is in there and USB) a real console and Beagle it, too. I got my controller sending button press messages with the wireless dongle. Before you start celebrating there are a few issues that are still pending: • looks like it works only for me. Probably some codes were device specific. Don't know yet how to figure it out (3rd party scans don't help).