@matchaman Ah, I misunderstood the concurrently part. I don't think it's possible from within the emulator, but maybe something external to combine the 2 inputs into 1 virtual gamepad (like xboxdrv ).

@demonscythe hey, i have 2 m30 controllers and work great with raspberry pi. how are you setting up your controls in emulationstation, and which games are you playing. I had this issue Ok by default sega genesis will be funny like X will be A and A will be B and B will be C, but lets start with emulation station, i mapped my keys with b is a and a is b. For example When mapping set B on controller as A and switch them X is y and Y is X Z is L shoulder and C is R shoulder L trigger is top L and R is top right. Also make sure you are pairing with Switch mode. Start+Y then press pair and reboot your raspberry pi. Hope this helps

Oh I missed it! Thanks so much!

The USB is rather OK, has been from the start. Only issue is that the home hotkey doesn't work. But I bought this for BT, and as I have no experience, I thought it really is 8Bitdo. I was fooled by the ebay sellers having 8Bitdo in the topic. I only yesterday found out it is not 8Bitdo :(

@mitu I had already tried de/re-registering the controller multiple times to no avail. But I'm going to run that firmware downgrade mentioned in the sticky, and if it fixes things I'll post in the sticky about my experience so that people will know if it affects WiiU controllers too.

Thank you @mitu , but the problem is still present. Ich will put my experience to the other topic.

@Efriim well thec64 mini doesnt even have a boot folder or 99.9% of linux in it. They made that thing absolutely bare bones as possible. I did discover that the ppsspp emulator on the pi uses a gamecontrollerdb.txt. I added theMayflash adapter to the gamescontrollerdb.txt and then tested in the emulator and the hats work fine. So i am not sure what the c64 mini’s problem is. I do however have a raphnet chip for wii classic controllers that i can solder up the wires to tomorrow to see if that one is working.

@mitu thanks.

@AssPunchMan said in PS3 Shanwan Controller lossed on every update: Its possible fix this? update without loss the PS3Controller pairs. The upgrade that broke the PS3 controllers - the Linux kernel - also broke other Bluetooth controllers and it's not under the project's control. It's a badly timed bug, but that's not something that happens regularly. If you wish to not be bitten by such situations, then only upgrade the packages you need (for bugfixes or new features) and skip the OS and driver upgrades.

@Felixoid said in Cannot configure 8BitDo M30 controller shoulder buttons: @psyke83 Hello. I've built a binary from the master, but the shoulders still don't work on the M30 pad. Could you tell if they already should work? It should work on the latest dev branch, yes. Is your controller definitely using axes 2 & 5 for triggers (considering differences in firmware/pairing mode)? Note that the axis filtering is done only when defining the trigger buttons, so if you're doing non-standard mapping to buttons other than the triggers, it won't work.

@cyperghost thanks will check that link out! I switched everything round, loaded up a random playstation game (2002 Fifa World Cup) and hit various hotkey combos (save state, load state, retroarch menu, exit emulator) a few times. All seemed to work without issue. The main test will be a longer play with testing throughout so will see how it goes.

Thanks but I appear to have found the problem. It seems that udev was blocking the new controller. Creating a new udev rule seem to have corrected the issue. For anyone else having this problem, first identify the name of your controller. There are several ways you can do this but the simplest it probably to just look through the system logs. With the controller connected (either via bluetooth of hardwire) cat the messages log. sudo cat /var/log/messages You'll need to look through the messages for the right device name but if you just plugged in the controller or connected it via bluetooth it should be near the bottom. It may even be the last entry in the log. Apr 20 16:31:13 retropie kernel: [ 8.528199] hid-generic 0005:1949:0402.0001: input,hidraw0: BLUETOOTH HID v1.1b Keyboard [Gamepad] on 00:1b:dc:0f:9d:ae Then create a new udev rule in the approprate location. sudo nano /etc/udev/rules.d/99-bluetooth.rules SUBSYSTEM=="input", ATTRS{name}=="Gamepad", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1" Once done simple restart the system and it should now work in EmulationStation. I hope this is helpful for someone! If nothing else I'm sure I'll be back here one day trying to figure out what I need to do again. :-P

@solisae Emulationstation does not initiate any connection, it's the OS (Linux) underneath that handles the connection. Try removing the bluetooth device (the controller) from the configuration screen and then re-pair and connect it again. Leave everything else on default and finish the configuration, then see if the behavior remains.

Rewrite: For people without a usb keyboard. On any android you can use an app like ConnectBot to SSH into your pi using RNDIS USB ethernet. Activate SSH on the Raspberry Pi navigate to raspi-config >> Interfacing Options >> SSH or (untested) create an empty file named ssh in the boot directory of the raspberry sdcard Install the apps on your android ConnectBot (or preferred ssh client) LanDroid (optional) F-Droid (optional - Free Open Source Software for Android) Activate the RNDIS USB ethernet use your phone charger to connect the Android device to the raspberry pi USB. android settings >> network & internet >> Mobile Hotspot/Tethering >> USB tethering or if you're phone provider has this service blocked for android 2.3 - 4.4 Use an app like Notification Bar will sometimes allow you to enable tether using the widget. Or install an unbranded rom like cyanogen-mod. for android ?5.0 - 8.0 android settings >> system >> about phone >> x7 build number (click on the build number 7 times) with "developer mode" enabled android settings >> developer options >> "select usb configuration" - RNDIS (USB Ethernet) (This is a good way to turn your phone into a wifi adapter if your router allows internet connection sharing) Aquire the IP address of the Pi using arp navigate to "show IP" on the raspberry pi or using ConnectBot app; add a host; change protocol to "local"; or use local terminal emulator type cat /proc/net/arp or ip neighbor into android terminal look for the ip-address 192.168.42.* or open the app LanDroid, and select the ARP & ND Cache or on windows use commandline arp -a look for a dynamic address that is not listed in ipconfig Open a SSH to the Raspberry Pi Use ConnectBot to add a ssh host filling out the username "pi"(default) and host "ip.address"(from the arp cache) other apps can be used and configured including sftp, I use the apps Total Commander and SFtp plugin for Total Commander or on windows windows 10 has ssh built in, simply type ssh ip.address or use one of these programs PuTTY(ssh) BitVise SSH client with ftp (easy to advanced) KiTTY (PuTTY with more features, easy) WinSCP (scp, sftp, ftp, advanced) FileZilla (sftp & ftp) And many more inlcuding Terminus, Super Putty and the amazing though complex Cygwin Android RNDIS creates IP addresses from the range 192.168.42.[1-255] these are generated randomly and will change when you reconnect the tether. When I figure out how to assign a static ip or save the dhcp or create some sort of order I will share. And if anyone know how to do this then please do. Alternatively to setting up ethernet, import the wpa passkey (wifi passkey) create a wifikeyfile.txt with the contents ssid="NETWORK_NAME" psk="NETWORK_PASSWORD" save it to the main folder of the microsd with retropie installed using a microsd reader. Reinsert the micro sd with RetroPie installed and power on the Raspberry Pi. Navigate Emulationstation using your controller to WiFi and Import wifi credentials from /boot/wifikeyfile.txt So it is possible with any android phone with a usb charging cable to tether and access configurations. or if you have a ethernet cable for your computer. I'm happy to help. Feel free to practice and take notes. It is difficult to find memories like this from while travelling. @trekdrop ~Bon voyage.

Hi folks I wanted to give an update. I had a little bit of success with the following: I went to /etc/udev/rules.d and opened up the three files that were in it 99-bluetooth.rules 99-com.rules 99-input.rules the first, "99-bluetooth.rules" is the udev rule that was created by the Bluetooth Configuration menu. SUBSYSTEM=="input", ATTRS{name}=="Pro Controller", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1" The MODE value here is "0666". However, when I opened up the other two files "99-com.rules" and "99-input.rules", I saw that they had MODE values of "0660". On a hunch I changed the values so that all three files had MODE="0666". And it worked - kind of. After making these changes and going through the setup process for a new controller, I was able to pair even after rebooting the pi or shutting down and turning it back on later. However, I was only able to pair: AFTER the pi had completely booted up and had arrived on the WELCOME no game pads detected screen Only on the second pairing attempt. The first attempt to pair would always fail. This worked for me about 10 times before the controller went back to not pairing at all. I'm wondering maybe if there are files besides the three that I mentioned that need to be altered in order to get this working consistently. If anyone has any ideas I'd really appreciate it!

@lmjiang1 Hi. I've been trying to get my M30 pad working with my Pi running Retropie, and it connects ok via Bluetooth, but my problem is that the controller won't recognise the R or C buttons when configuring it in Emulation Station. Do all your buttons work ok?