Odroid XU 4 8bitdo controllers add problem

mitu

Looks like a XU4 specific problem. Check if you can delete manually the BT pairings

sudo bluetoothctl
# list
# remove <CONTROLLER:MAC>
# exit

where you replace <CONTROLLER:MAC> with the entry shown by list for your controllers.

For problem 1, can you please be more specific what kind of 8Bitdo controllers you have ? Please also add the info requested in https://retropie.org.uk/forum/topic/3/read-this-first.

ray3d

Yes I remove and from bluetooth and when I try to pair again I have the error “An error occurred connecting to the bluetooth device (Creating device failed: .org.bluez. Error. AlreadyExists: Already Exists)” in security mode just one step before finishing the pairing. The first installation left rests somewhere but who mows here to delete everything.

For problem 1: I have these controllers:

http://www.8bitdo.com/n30pro-2/

In this problem 1 the first problem I presented is that initially the right shoulder, and right trigger buttons were not detected. I pressed them and emulation station didn’t do anything. With the other buttons were detected perfectly just that two buttons no.

mitu

@ray3d Please also add the info requested in https://retropie.org.uk/forum/topic/3/read-this-first.

ray3d

I’m using the controllers 8bit3do N30 pro 2. I’m using the retropie installed following the instructions described here:

https://retropie.org.uk/docs/Odroid-XU3-XU4/

I have the Odroid XU 4 with “ameriDroid USB Bluetooth Module 2” bluetooth dongle. I’m using an USB keyboard and lao I have enabled SSH. I have excellent power supply with 3A.

That is the information I have if my system.

I made what you said:

sudo bluetoothctl
# list
# remove <CONTROLLER:MAC>
# exit

There are no devices just the:

Controller 00:1A:7D:DA:71:13 odroid [default]

Nothing else. The there are rest left over somewhere. Any idea where to delete? Because I continue receiving the same error when I try to pair for second time:

An error occurred connecting to the bluetooth device (Creating device failed: .org.bluez. Error. AlreadyExists: Already Exists)

For the problem 1: Why the righ shoulder and trigger buttons were not detected to map?

mitu

@ray3d said in Odroid XU 4 8bitdo controllers add problem:

For the problem 1: Why the righ shoulder and trigger buttons were not detected to map?

Are the buttons detected by running jstest /dev/input/js0 from a command line and pressing them ?

ray3d

Ok I will try that what you say in case are detected there what means or if not what can be done?

Actually I cannot test because as you see I can’ t pair for the error “Already Exists” before described.

mitu

@ray3d said in Odroid XU 4 8bitdo controllers add problem:

Actually I cannot test because as you see I can’ t pair for the error “Already Exists” before described.

Hm, I might be wrong on the bluetoothctl command - try the advice in https://askubuntu.com/questions/822249/unpair to list any device paired.

ray3d

Finally I’m here but I yes with your command:

jstest /dev/input/js0

But the gamepad not work. It work just some buttons all the shoulders and triggers works, the rest of the control not works. Also sometimes that shoulders and triggers buttons stop working also. This is like erratic.

mitu

@ray3d said in Odroid XU 4 8bitdo controllers add problem:

This is like erratic

Maybe the bluetooth connection is having problems - are you using an USB dongle for the bluetooth connection ?

ray3d

Thank you @mitu for all help. I almost finish my image from other posts you helped me to solve. In the case of the game pads I write a solution worked for me, just in case someone is lost and can be useful. This is the solution:

Finally I could make work two 8bitdo SN30 Pro 2 game pads. I used the firmware V1.2 and worked pretty with this same technique. However, I wanted to try with the latest V1.3 firmware to see what happens and I could make work. Fighting with the retro arena setup and also retropie setup both versions in the bluetooth script, it just worked for me the first time and after the first time is impossible, at least for me, to pair again by the horrible error Already exists bluez.org. Something is stored in the cache or somewhere after the first pairing but I could not find information in any place. Most of posts run from a real solution and they mention “my solution was begin with a fresh image and problem solved”. I made that but if you have a mistake, like in my case, is an endless loop over and over again and no solution. Then this is what I did:

First I made a copy, to have safe the original file “/etc/dbus-1/system.d/bluetooth.conf”. Then I replaced that file with this:

https://pastebin.com/LufCYWy9

Then I made this procedure to pair:

1.-sudo service bluetooth restart

2.-agent on

3-power on

4.-scan on

5.-scan off

6.-pair “mac address of the gamepad”

7.-connect “mac address of the gamepad”

At this is step it will pair although and is possible it can says cannot connect. No matter this is not a thing to be afraid. If it doesn’t connect or says fail to connect in specific: Turn OFF if it is ON the game pad. Turn ON again normally the game pad and type again step 7 (connect with the mac address command).

It can says a couple (2 or 3) times is not possible connect but no matter it will do. Simply is turn OFF the game pad and ON again and give the “connect” command again. Once say successfully connected is give this command:

8.-trust “mac address of the gamepad”

9.-Return the original file “/etc/dbus-1/system.d/bluetooth.conf”, deleting the one of pastebin above described. Just in case. I used the pastebin temporary just to pair, after pair there is no sense to keep it.

If in the step 6 of pairing says already exists bluez.org or simply never connected in step 7 then is type first to see the devices paired:

devices

After that is check if i there the game pad. If it’s there then is give now:

remove “mac address of the gamepad”

One is successfully removed is back to step 5.

Once is paired, and connected, because It will pair for sure, also will be detected ALL the buttons by emulation station. I have two gamepads and both were detected including after reboot and latest firmware. I tested this like 10 times to be sure, including making tests downgrading and upgrading firmware in the game pads and always worked at the end. I write this just in case someone has a problem as me and want time and loss time beginning from fresh image and is wanted to save time.