It was easier than I expected, thanks @ferdnand

@mattrixk
I have the C120 Pro remote, which might not have the same id numbers.

I found this post that helped solve the same issue as yours, where it would register as player 1 and the other controls were 2+.
From the post: "The following code deactivates the joystick part."
https://ubuntuforums.org/showthread.php?t=2283297

Use this to find the usb interface/vendor/model id numbers:

udevadm info -q all -n /dev/input/js0 | grep -Ei '(ID_USB_INTERFACE_NUM|ID_VENDOR_ID|ID_MODEL_ID)'

Create rule using:

sudo nano /etc/udev/rules.d/99-persistent-joystick.rules

and add the following in (replacing bInterfaceNumber, idVendor and idProduct with yours):

SUBSYSTEM=="usb", ATTR{bInterfaceNumber}=="03", ATTRS{idVendor}=="0c45", ATTRS{idProduct}=="3451", RUN+="/bin/sh -c '/bin/echo -n %k >/sys${DEVPATH}/driver/unbind'"

Reboot, and you should see that js0 is no longer shown by using

ls -l /dev/input/

and that controller 1 shows up as controller 1 when activated.

This may not be the proper way to do things, but the best I've found so far using it with PS3 controllers. If there's a better way, I'd be open to hearing it.

Hope this helps.

I had the following error that occurs if you configure a PS3 controller before attempting to configure an 8bitdo gamepad:

Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 604, in msg_reply_handler reply_handler(*message.get_args_list(**get_args_opts)) File "/home/osmc/RetroPie-Setup/scriptmodules/supplementary/bluetooth/bluez-simple-agent", line 118, in pair_reply dev_connect(dev_path) File "/home/osmc/RetroPie-Setup/scriptmodules/supplementary/bluetooth/bluez-simple-agent", line 38, in dev_connect dev.Connect() File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in call return self._proxy_method(*args, **keywords) File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in call **keywords) File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.bluez.Error.NotAvailable: Operation currently not available

The solution is to remove the PS3 controller driver via the retropie_setup.sh script ([Manage packages] -> [driver]->[ps3controller]->[uninstall/remove]).

Afterward, manually remove all packages/dependencies related to it. Basically any package mentioned in the PS3 controller setup guide:

https://github.com/retropie/retropie-setup/wiki/Setting-up-a-PS3-controller

sudo apt-get --purge remove sixad
sudo apt-get --purge remove sixpair
sudo apt-get --purge remove bluetooth
sudo apt-get --purge remove blueman
sudo apt-get --purge remove bluez-hcidump
sudo apt-get --purge remove checkinstall
sudo apt-get --purge remove libusb-dev
sudo apt-get --purge remove libbluetooth-dev
sudo apt-get --purge remove joystick
sudo apt-get --purge remove pkg-config
sudo apt-get --purge remove python-gobject
sudo apt-get --purge remove bluez-utils
sudo apt-get --purge remove pi-bluetooth

Then,

sudo apt-get install pi-bluetooth

Then follow the normal 8bitdo setup guide:
https://github.com/retropie/retropie-setup/wiki/Setting-up-an-8bitdo-Bluetooth-controller

@deadpool There's this section in the retroarch.cfg

# The maximum rate at which content will be run when using fast forward. (E.g. 5.0 for 60 fps content => 300 fps cap). # RetroArch will go to sleep to ensure that the maximum rate will not be exceeded. # Do not rely on this cap to be perfectly accurate. # If this is set at 0, then fastforward ratio is unlimited (no FPS cap) fastforward_ratio = 0

I don't know if this is a very healthy setting to be using, or how much it even effectively speeds things up. There doesn't seem to be a way to get the really zippy frameskipping fastforward that you find with a lot of pc emulators. At least, I haven't come across it yet.

try this (worked for me):

worked for this configuration: RP3 model b, external bluetooth dongle, gasia fake ps3 controller (same as this post).

use ssh or get terminal access, cd /usr/sbin/
set appropiate permission to this command (one time setting): chmod 755 sixad-sixaxis
sudo reboot
have fun!