Lakka and Stadia Controller (Bluetooth Mode) do not work together #1824
Comments
mtoensing
changed the title
|
I dont have a stadia controller unfortunately |
|
Hi, what do you mean mit send? I can send you controller if you like. |
|
https://discord.gg/libretro-184109094070779904 |
|
@gouchi |
|
@mtoensing were you able to pair the controller via bluetooth? Maybe pairing via RetroArch UI will not work, so please try using command line. After you pair the controller, you might need to manually map controls to actions. |
|
I know I could do that. But since there are now millions of Stadia controllers in the wild I would appreciate that this works automatically in Lakka. |
|
That is the reason why I kindly ask you to pair it first - to know if there is support in the linux kernel already (meaning only the joypad mapping is necessary) or a kernel driver/module needs to be added. |
|
I got it to connect correctly: After pairing this is the info I get: After that the controller sometimes appears on the bluetooth screen of RetroArch with a generic bluetooth icon, but it is not available on the input mapping screen options. I'm running lakka stable (4.3) on raspberry pi 3. On my Debian Stable box the controller is connected and setup with the graphical standard process without problem (well, mostly, some random disconnections). |
|
Thanks, if the device is recognized correctly as gamepad/joystick, you should be able to test the inputs via command line, e.g. Now that it is paired with your RPi, it should connect after reboot without the need of the command line. Do you get a brief message that a gamepad was detected in RetroArch? For example something in the meaning that no valid configuration was found? It is possible that it is not recognized as gamepad, but other type HID device (keyboard/mouse/...) - in such case there will be no such message. Also can you paste kernel log ( |
|
Hello. I don't have any /dev/input/js0 (custom udev rules needed?). And so I cannot map actions as there is no device index available. Yes, it reconnects (but with Paired: no); and no there is no message at the start or when switching off and on again the controller. dmesg is rather cryptic: BTMon output at controller switch on and connect: |
|
Hi, I have the same problem and came here to ask for the same thing. I can help too. I noticed from this thread some errors or at least things that don't apply to my machine. The stadia bluetooth enabled controller does connect to lakka via bluetooth both via ssh and gui. Plus, the stadia controller works flawlessly on retroarch for windows. It even shows up the correct controller's name. |
|
Is it also an issue using dev builds from Lakka 5.x branch ? Thank you. |
|
No, it doesn't work even there. Same problem: gets connected but not recognized as a controller |
|
Do you still have that problem? I figured out, that it helps to restart bluetooth with a startup script. i added sleep 10, otherwise it won't work |
|
Hi, Is it still not working using latest dev builds ? Thank you. |
|
@gouchi I have the same issue, I just tried installing the latest dev build (Lakka-RPi4.aarch64-devbuild-v5.x-20240125-9297f90.img.gz) and same issue there. Anything I can do to assist or provide more details? EDIT: running btmon I do see live events but it does not show up in /dev/input
BTMON output when starting already paired stadia controller What sticks out is "= bluetoothd: src/service.c:service_accept() input-hog profile accept failed for F6:8B:AB:35:A8:F3 11.695629"
|
|
I stumbled upon this https://codeberg.org/fabiscafe/game-devices-udev |
|
Still did not work =/ When u run the control reload and trigger UI showed that my PS3 controller disconnected (but still works) so that seems to have done something. Is there a command to debug what udev sees? |
|
when enabling debug output as in https://superuser.com/questions/677106/how-can-i-check-if-a-udev-rule-fired (top response) I get when boting paired device: |
you could try something like |
|
This is what I get when booting the device (already paired) and when turning it off.. But from previous logs and some googling on simiar errors sonds like there might be an issue with bluez? It seems to me the device is connecting and disconnecting properly but something fails on my machine during this and its only partially setup? |
|
Also I see all these Maybe we are supposed to show some dialog? (I remember my macbook did this everytime I connected wth it) |
|
After I ran |
|
dmesg |
|
I removed the udev rules, rebooted. Device was paired but non functional, then I did hciconfig hci0 down and up, and controller connects again, so I suspect there is really some sort of dance we are supposed to do with it that does not work automatically |
|
PS, none of the buttons seem to be mapped as |
|
Managed to figure out how to remap controller and get meny key working =) However I guess we should figure out how to get that security request fixed properly. |
|
Toggling bluetooth off and on via UI has the same effect. So currently to get it working on Lakka you need to pair it, then Services > Bluetooth Off and then On again and it should tell you a Stadia controller was connected I suspect it might be an issue with the current bluetooth agent, maybe its booted too early? |
|
Regarding binding there seems to be one already https://github.com/libretro/retroarch-joypad-autoconfig/blob/master/udev/Google%20LLC%20Stadia%20Controller%20rev.%20A.cfg But it gives a different name when connected over bluetooth maybe that is why it does not map it out of box ( had to rename it to whatever mine as called for Mupen64 on my mac...) My generated config has these rows vs EDIT: Might also be they changed the device name when you flashed it to permanent BT mode and the existing bindings worked with pre-flashed controller over cable |
Please make Stadia Controllers compatible with Lakka.
The text was updated successfully, but these errors were encountered: