This is a known issue that'll be fixed once this PR is merged; when merged, you'll need to use emulationstation-dev until the patch is also applied to the stable branch.

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

Thanks @mitu, I actually just got it working! @darthzabuza have you watched this video by Herb Fargus - It solved my issue. I put the controller into Switch mode (four lights cycling across one at a time) when initially pairing. The whole procedure worked with my M30 even though the video was made for the SF30 Pro. Hope this helps.

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.

@mitu said in Speeding up retropie boot up on a Pi zero and turning off BT & WiFi..: @MachLid One thing you can do to speed up the boot is to disable file shares (Samba services). From what I've noticed, this is one of the services that takes up a lot of time (proportional to the total boot time) to start up. I've looked up in the RetroPie-Setup script and you only have the options to remove Samba completely (not disable it), so you'd have to use the command line to disable the services manually. sudo systemctl disable smbd sudo systemctl disable nmbd More ideas and help!! thank you very much, and I'm also going to try this as well. I have no problem killing anything unnecessary on it in order to speed up booting into the game selection menu. What I'm hoping to do with this Pi Zero is simply and only use it for mostly Atari 2600 stuff and maybe some popular arcade games from pre 1990's or earlier (if it'll handle it). I grew up with a Atari 2600 and lots of this stuff thru out the 1980s,, and thought it'd be neat to have something very little and compact (and even battery powered) and be able to quickly power on, and play some of the true classics. Not sure what I'm doing yet for a compact and portable housing or anything like that yet,, I just wanted to square away the working parts first. Thanks again.

@mitu Oooops, sorry about that. Will do! Thanks

@rodrigoleao said in [SOLVED] 8bitdo and dualschock 3 at same time: Is it happen with your setup too? I'm using the default bluetooth of raspberry pi 3. Yes it happens a bit for me too sometimes. I have both, a Raspberry PI 3B and 3B+, and as @mitu says the bluetooth of the plus is way better (but not perfect) than the normal one. Also make sure that the battery of the 8bitdo controller is charged, I found out that when it's about to get flat, it has a lot of latency/delays in response. Good you sorted out your problem!

Excellent, thanks for the quick reply. I won't be able to do it tonight, but will get onto it tomorrow. Cheers

@ByteThis Diffferent type of Bluetooth module, I believe. Could be wrong...

No worries. I just wanted to help the community out!

Anyone! I’m really desperate to fix this.