In the end, I connected a mouse to play Arkanoid in lr-mame2003, and it worked from the off. Xbox 360 controller just too baggy and too huge a deadzone to make it playable. Thanks for advice though.

I'm at my wits' end here. I've tried blacklisting the device to prevent it being grabbed by usbhidby creating /etc/modprobe.d/blacklist.conf and adding to it : blacklist usbhid No dice. I've tried creating: /etc/udev/rules.d/99-disable-usb-hid.rules and adding to it: SUBSYSTEMS=="usb", DRIVERS=="usbhid", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="028e", ACTION=="add", ATTR{authorized}="0" No dice. Before that, tried adding an /etc/udev/rules.d/ ruleset with: SUBSYSTEM=="usb",ATTRS{idVendor}=="045e", ATTRS{idProduct}=="028e", MODE="666", GROUP+="plugdev" No dice. The end result is always the same, reboot after reboot. I've tried looking at other conf files in /etc/udev/rules.d/to see that there are no conflicts. I have two identical controllers at my disposal I've tried plugging them in one at a time. Adding to that, I've tried this with FOUR identical controllers, all of which work 100% plug'n'play in Windows 7. The controller's analog LED light lights up for a few seconds and then shuts off. Here's what lsusb -v -s 001:009 shows : pi@retropie:~ $ lsusb -v -s 001:009 Bus 001 Device 009: ID 045e:028e Microsoft Corp. Xbox360 Controller Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize0 64 idVendor 0x045e Microsoft Corp. idProduct 0x028e Xbox360 Controller bcdDevice 1.10 iManufacturer 1 iProduct 2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 48 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 93 bInterfaceProtocol 1 iInterface 0 ** UNRECOGNIZED: 10 21 10 01 01 24 81 14 03 00 03 13 02 00 03 00 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0020 1x 32 bytes bInterval 4 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0020 1x 32 bytes bInterval 8 pi@retropie:~ $ All help appreciated. This is especially infuriating as I already got this thing to work once with one controller, tried to get it working with two controllers of the same kind, and it all went to hell. * one huge sigh * Am I completely on a wrong track here if I'm thinking that perhaps the device ID should be added into the boot config file or somewhere alike as separately blacklisted or as an USB HID exception? Or, does the actual problem run deeper somewhere on the Raspbian/Linux kernel level? That's what a lot of my attempts to search further into the USB HID device issues w/ Linux altogether would suggest. One plausible culprit might also be that since the controller ( http://piranha-gamer.com/product/piranha-pc-ps2-ps3-controller/ ) is listed as a "PC/PS2/PS3" controller, it might auto-select its operating mode accordingly between PC and PS mode upon being plugged to an USB port. Then again, that doesn't explain how it has worked earlier from time to time (or, should I say, from RetroPie update to RetroPie update) without any problems whatsoever.

Found driver, installed it, connected pad. All good. Thanks @mitu

@MajorDangerNine lr-vice has a virtual keyboard and you can control the mouse with your controller. Lr-bluemsx works. Msx does have some games that require some keyboard keys. Linapple works but there might be some games that require a keyboard press. Not sure though. After setting up controls you can play a ton of games in dosbox without a controller. Thats the extent of my computer gaming systems.

@theretroprince said in Xbox One Blue Tooth Joy-Pad Connection Problem: @lip9571 The udev rules are an option that you can automatically set in RetroPie-setup. They just write a line of configuration to your bluetooth rules. It is not enabled by default. As long as you haven't enabled them, you don't need to concern yourself with them. If you have enabled it, you can disable it within the Bluetooth setup in RetroPie-Setup. Thanks for the reply. I got it all working in the end all I need to do was re bind the buttons for Bluetooth in retro arch and it worked perfect

@Clyde yes, i purcheased on ebay ;-)

Usually, controllers supporting several devices have a switch between the connection modes they support (PS3, X-Input, DirectInput, Switch, Android, etc.), but it seems your controller tries to guess which device is connected to and starts in a certain mode. You can force a certain driver to handle the gamepad - see https://unix.stackexchange.com/questions/12005/how-to-use-linux-kernel-driver-bind-unbind-interface-for-usb-hid-devices - but that still might not work if the controller 'thinks' it's using a certain connection mode.

@jamesnj if you want a solution for both, you could use the Virtual Gamepad option within RetroPie. You would use your phone connected to the RetroPie IP address and it gives you an onscreen joypad. That may also work within Kodi if you re-enable the joystick support and setup the gamepad within the Input settings.

@eldrethor yes i didnt think of it... 2003 mame are ok yes.

Well, I don't have an IPAC, but maybe some forum members can chime in with their experience, but IMHO shouldn't be an issue as long as all controllers are detected by the system.

@jfrmilner Thanks for the kind praise. My answer about multiplayer games is going to come from the arcade game options, as my build obviously has that emphasis. There is another thread here somewhere that lists all of the 4-player games (4-player MAME lists can also be found online). But I have far far less than a full ROMset loaded on my system--I load games as I learn about them. That said, it is hard to beat a good game of 4-player Gauntlet and Gauntlet 2. Try Xenophobe. Then, there are the fighter games like X-men, or the Simpsons and TMNT. Battletoads has 3 player capability, Rampage is fun. Then there is a handful of sports titles. Stone Ball is super fun! NBA Jam, and a few racing games like Super Sprint. My build looks like a 4-player cabinet, but remember, many classic arcade games have the CRT oriented vertically, so for those, even though they are not 4-player games, I play them from the vertical sides of the cabinet (players 3 and 4) to get the best, full-screen experience.

@salvaliebana install joystick selection. Go into retropie menu. If you see joystick selection then it is already installed and go to paragraph 2. If it is not read paragraph 1. In the retropie menu, go into runcommand. In there install joystick selection. Exit. Restart your pi. Go into retropie menu, then into joystick selection. In option number 1 you can select which joystick is each player.

@alistaircg which folder are you running the roms from? /roms/mame-libretro?

wow @edmaul69, thank you very much. i didn't think about it. i switched joypad from analog to standart in Little Big Adventure and its working now ;) legend of mana works as well you are great, cheers

@mrdally204 Config file overrides for RetroArch are explained here and are probably more inline with what you're looking for. It includes an example for per-ROM configuration.

@Neo-Rio Thats the thing - my joypad works fine in ES, but even after setting them up in Vice itself they still don't work. Guess i could always just 'start again' - any idea what Vice-specific files i need to delete to clear the config?

@chubsta get the SNES30 and you'll get what you want. ;)

@PetroRie Thanks - I do have a PS4 so will give that a go later. Cant get much cheaper than "already have"!