Solved Can't pair bluetooth MadCatz C.T.R.L.R

[elchhome]

evtest brings for me something like:

Event: time 1471421830.222857, -------------- SYN_REPORT ------------
Event: time 1471421839.037076, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90008
Event: time 1471421839.037076, type 1 (EV_KEY), code 311 (BTN_TR), value 1
Event: time 1471421839.037076, -------------- SYN_REPORT ------------
Event: time 1471421839.222181, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90008
Event: time 1471421839.222181, type 1 (EV_KEY), code 311 (BTN_TR), value 0
Event: time 1471421839.222181, -------------- SYN_REPORT ------------
Event: time 1471421839.747441, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90007
Event: time 1471421839.747441, type 1 (EV_KEY), code 310 (BTN_TL), value 1
Event: time 1471421839.747441, -------------- SYN_REPORT ------------
Event: time 1471421839.935186, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90007
Event: time 1471421839.935186, type 1 (EV_KEY), code 310 (BTN_TL), value 0
Event: time 1471421839.935186, -------------- SYN_REPORT ------------
Event: time 1471421841.059117, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90008
Event: time 1471421841.059117, type 1 (EV_KEY), code 311 (BTN_TR), value 1
Event: time 1471421841.059117, -------------- SYN_REPORT ------------
Event: time 1471421841.184228, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90008
Event: time 1471421841.184228, type 1 (EV_KEY), code 311 (BTN_TR), value 0
Event: time 1471421841.184228, -------------- SYN_REPORT ------------
Event: time 1471421850.286365, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1471421850.286365, type 1 (EV_KEY), code 304 (BTN_SOUTH), value 1
Event: time 1471421850.286365, -------------- SYN_REPORT ------------
Event: time 1471421850.384091, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1471421850.384091, type 1 (EV_KEY), code 304 (BTN_SOUTH), value 0
Event: time 1471421850.384091, -------------- SYN_REPORT ------------
Event: time 1471421851.221895, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90002
Event: time 1471421851.221895, type 1 (EV_KEY), code 305 (BTN_EAST), value 1
Event: time 1471421851.221895, -------------- SYN_REPORT ------------
Event: time 1471421851.320732, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90002
Event: time 1471421851.320732, type 1 (EV_KEY), code 305 (BTN_EAST), value 0
Event: time 1471421851.320732, -------------- SYN_REPORT ------------

and the button names doesn't even change when changing between the three controller modes (android/mouse/windows)
So finally it comes down to a button name mapping issue

[acris]

This post is deleted!

[Substring]

@elchhome so it's paired, sends joypad events. If there are also mouse events sticked to it, it won't be recognized as a joypad but as a mouse. Need a udev rule. We need you to run /recalbox/scripts/recalbox-support.sh with your pad paired and upload the file somewhere. With this, we will know if your pad is seen as a mouse/keyboard or pad, and make what's necessary to have it recognised as a pad

[elchhome]

I hope you can download it:
h_t_t_p_s://drive.google.com/open?id=0BxMwQBosHAcbUUVWVkxoVkVnN2M

[elchhome]

@subs
Did you download the file and do you already have an idea how to fix that?

[Substring]

nope, didn't have the opportunity yet

[elchhome]

@subs
is there a file where I can add the button mapping by hand?

[Substring]

@elchhome sorry dude, I was out for the weekend. Gonna check your file today and report back.

[Substring]

@elchhome try those commands through SSH :

mount -o remount, rw /
echo 'SUBSYSTEM=="input", ATTRS{name}=="Mad Catz C.T.R.L.R", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1"' >> /etc/udev/rules.d/99-joysticks-exotics.rules
reboot && logout

Your pad is, as I expected, considered as a mouse/keyboard. Those commands above will force the joystick bit, and it should then work. Can you confirm ? If yes, we'll add your pad to 4.1 so that it's automatically detected as a pad

[elchhome]

@subs
Thanks a lot! This change makes the controller available to the system.
Good work!

[Substring]

@acris a reminder for you to include the udev rule in 4.1

[acris]

@subs it s done
https://github.com/recalbox/recalbox-buildroot/pull/461/commits/a00f6c3a6c226a2bcd54044fd0e477c10c61e2e0

[Substring]

@acris Nice !

[wden86]

Hi all,

I just got a raspberry pi3, installed recalbox 4.0 on it and tried to set up my gamepads.

No trouble with 8bitDo NES pro, nor with an USB generic gamepad.

I tried to set up my Mad Catz C.T.R.L.R with this topic's solution.

Adding a line in the joystick rule file didn't work at first because of device name.
Indeed, the sdptool command on the MAC address told me the device's name is not "Mad Catz C.T.R.L.R", but "HID Gamepad".

The CTRLR switch is set on the gamepad.

Regars,

Denis