Posts made by elchhome

The wiki mentioned two methods:

/recalbox/scripts/bluetooth/test-device list
8C:CD:E8:73:F4:87 Nintendo RVL-CNT-01-UC
/recalbox/scripts/bluetooth/simple-agent hci0 "8C:CD:E8:73:F4:87"
Agent registered
Creating device failed: org.bluez.Error.AlreadyExists: Already Exists

[bluetooth]# pair 8C:CD:E8:73:F4:87
Attempting to pair with 8C:CD:E8:73:F4:87
Failed to pair: org.bluez.Error.AlreadyExists
[bluetooth]# connect 8C:CD:E8:73:F4:87
Attempting to connect to 8C:CD:E8:73:F4:87
[CHG] Device 8C:CD:E8:73:F4:87 Connected: yes
Connection successful
[CHG] Device 8C:CD:E8:73:F4:87 ServicesResolved: yes
[Nintendo RVL-CNT-01-UC]# trust 8C:CD:E8:73:F4:87
Changing 8C:CD:E8:73:F4:87 trust succeeded

-> now the controller is connected

After reboot it can't connect again.
No progress...

Hello Recalbox Team,

I've just done a fresh installation of Recalbox 6.1.1 on my Raspberry Pi 3 B+.
In Emulationstation I was able to pair the original Wii U Pro Controller successfully with the internal Bluetooth controller.
After every reboot the pairing is lost, but the button mapping is still there.
Pairing the controller again solves the problem until next reboot. That's really exhausting...
Can you please help me saving the configuration that it survived reboots?

The bonus question is:
I have the Retroflag NESPI+ case.
In the past I've used the safe shutdown script from:
https://github.com/RetroFlag/retroflag-picase
Should I use this again or is there already something included with the new Recalbox release?

Thanks in advance,
Andi

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

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

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

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

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

You're completely right. I tried anothe dongle and now I have exactly the same behavior as you described.
The interesting thing is, that the additional buttons like fastforward/fastbackward/pause and the digital arrow keys are then received as keyboard strokes and not as gamepad buttons.

btw. my controller firmware is on latest level v1.2.5 that can be downloaded from madcatz.com

mmh. In order to get even an emulated mouse function running the device has to be paired.
I think the gamepad should be exactly the same as yours, but I tried all three modes and it doesn't pair.
The home button keeps blinking read and blue and nothing is working although the GUI said "ok".

# hcitool cc 00:15:9E:C0:78:19; hcitool auth 00:15:9E:C0:78:19
Can't create connection: Input/output error
HCI authentication request failed: Input/output error

# sdptool browse 00:15:9E:C0:78:19
Browsing 00:15:9E:C0:78:19 ...
Service Name: Mad Catz C.T.R.L.R
Service Description: HID Gamepad
Service Provider: Mad Catz
Service RecHandle: 0x10000
Service Class ID List:
  "Human Interface Device" (0x1124)
Protocol Descriptor List:
  "L2CAP" (0x0100)
    PSM: 17
  "HIDP" (0x0011)
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "Human Interface Device" (0x1124)
    Version: 0x0100

How would I authenticate?

no, I don't need a key if I pair it with my phone/Android

Hi folks,

when I try to pair the bluetooth MadCatz C.T.R.L.R gamepad I'll get the error:

# hcitool scan
Scanning ...
        00:15:9E:C0:78:19       Mad Catz C.T.R.L.R
# hidd --connect 00:15:9E:C0:78:19
Can't create HID control channel: Connection refused
# tail -4 /var/log/messages
Aug 16 11:28:43 RECALBOX daemon.err bluetoothd[305]: No agent available for request type 0
Aug 16 11:28:43 RECALBOX daemon.err bluetoothd[305]: btd_event_request_pin: Operation not permitted
Aug 16 11:28:44 RECALBOX daemon.err bluetoothd[305]: No agent available for request type 0
Aug 16 11:28:44 RECALBOX daemon.err bluetoothd[305]: btd_event_request_pin: Operation not permitted

any idea?