@notthesame I can't believe that worked, you are a godsend. I'd also like to add a few details:

After pressing Start and Y, the LEDs start to rotate from left to right. After that, you hold pair for 2 seconds, the LEDs go off for a second, and then they start to rotate again.

At this point you need to go through the Bluetooth pairing process again (and if your controller is already paired, you should un-pair it before you re-pair it) but you do NOT need to set up the udev rule. All you need to do is reboot and configure the input like normal.

I think this should be added to the documentation.

Oh I missed it! Thanks so much!

Has anyone had any more success for these? They really do look like nice controllers and I hate for them to collect dust :-/

@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.

Had a similar problem with an old Ipega GamePad. Pair with BlueTooth with some re-connect issues, but worked with jstest and evtest.

Adding the udev rule helped with emulationstation, but only the left joystick works in RetroArch.

Running RetroPie 4.5.1 with updates. Any suggestions?

@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.

@lmjiang1 hello i had this same issue with xu4 retroarena, m30 after reboot i get no pair, m30 would pair but couldnt do anything in game or ES, i updated m30, no luck.
Xu4 has only 3 ports i had a hdd connected, wifi usb, bt dongle all my usb connects gone so i thought maybe i need to connect to 3.0 usb, i bought 2 bt and same issue happen.
I then added a multi usb but it would do the same thing, i had some try m30 with thoses 20 dollar usb bt by with like super mario block design and i thought i need one of thoses, same thing happen, no pairing all what i have type above.

So i gave it about 2 months and asked again and tried again, once i had turned on the xu4 after months it paired right up like nothing had happened, so i played.
I had help and we tired to pair with switch mode and android but no luck i was fed up dude.

The guys at retroarena dont know what it is, i been waiting for about 1 month in a half but i havent bothered anymore.

But the m30 works fine with all other machines, just might be the xu4 cos someone else tired and did the same thing, might be your pi2 is the samething.
Works fine on my pi3b+ i used thme and pair just fine.

So my solution at the end since i got xu4 for saturn and just more power i put it away and ordered a pi4 and works super awesome!
I installed yabause on desktop and played dracula x.

Im sorry that it acts the way it does and i hope someone can help.

@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?

So @ExarKunIv , just update emulationstation and it now magically works?? Sweet! And no, you were not alone! I actually thought my controller was defective because it was doing this same thing over several very different builds.

Alright, I've tried Ubuntu MATE 18.04 beta 1 extensively and the problem does not occur on Ubuntu at all. Must be a Raspbian issue. Definitely not my hardware. I hate to dig up a month old topic, but it is what it is. A Raspbian issue.