Title pretty much sums it up. Upgraded controller firmware to newest version. Enabled Bluetooth and turned on via dual shock instructions but whenever I try to connect via any of the modes the blue light just flashes and there’s no indication that it’s connected. Everything else works great! If only I can get the controller working… It does work via USB but the cable is rather short. Thanks!
[QUOTE=Rion;34991]http://libretro.com/forums/showthread.php?t=3649
Have you tried this?[/QUOTE]
From my understanding this is for when the controller is connected but not all buttons work? Just the d pad? I’m unable to get it connected at all so I think there’s something I’m missing or not doing right to get the controller connected and paired. When I hold the start button or start+R is there anything I have to do in Lakka to get it connected and paired? Confirmed that it connects to my iPhone or MacBook and works fine… Just will not connect to Lakka? Thanks
Did you add the udev rules as mentioned ?
wget https://raw.githubusercontent.com/paalfe/mixedcontent/master/udev_rules.d/99-8bitdo-bluetooth-controllers.rules -O /etc/udev/rules.d/99-8bitdo-bluetooth-controllers.rules ;
1 Like
[QUOTE=gouchi;35020]Did you add the udev rules as mentioned ?
wget https://goo.gl/H2SViY -O /etc/udev/rules.d/99-8bitdo-bluetooth-controllers.rules ;
[/QUOTE]
I just did. Appears to not do anything at all. I have verified that the file is in the correct location.
I appreciate the help but I’m going to start over from the beginning in hopes that it helps. Running terminal through ssh from my macbook to the asus box.
I have Lakka installed on an Asus Chromebox, and am trying to get it working with the 8bitdo SNES bluetooth controller. I followed the directions for the dual shock 3 document to get the bluetooth enabled and running using the enable bluetooth, start bluetooth, and status bluetooth commands. added udev rules file in previous post Under bluetooth I can run the scan on command and see what I assume is the controllers MAC address. I tried following the pairing guide for the dual shock controller as well but after turning everything on from that point nothing in the guide happens as it’s explained so I’m unable to really get anywhere from it. I don’t get an authorize device request and connect <device_addr> does nothing even after repeating the code like the guide suggests.
So that’s where I’m at if anyone has any suggestions or can help that would be great!
added udev rules file in previous post
Try to reload udev or reboot, udev should automatically detects changes to rules files but we never know 
A friend of mine had a similar issue. It turned out he forgot to power up the bluetooth module after a reboot. After he added following in the local.rules, the problem was fixed. But you may have another problem. You should compare the mac adresses. If you start up with another button combo, for e.g. Start+R, the MAC Adress might have changed. And you schould also reset the controller if it was connected prior to another PC/Tablet/Phone. I am not 100% sure, resseting the controller is by pressing “Select” for about 3-5 Seconds.
nano /etc/udev/rules.d/10-local.rules
Set bluetooth power up
ACTION==“add”, KERNEL==“hci0”, RUN+="/usr/bin/hciconfig hci0 up"
[QUOTE=jayp76;35042]A friend of mine had a similar issue. It turned out he forgot to power up the bluetooth module after a reboot. After he added following in the local.rules, the problem was fixed. But you may have another problem. You should compare the mac adresses. If you start up with another button combo, for e.g. Start+R, the MAC Adress might have changed. And you schould also reset the controller if it was connected prior to another PC/Tablet/Phone. I am not 100% sure, resseting the controller is by pressing “Select” for about 3-5 Seconds.
nano /etc/udev/rules.d/10-local.rules
Set bluetooth power up
ACTION==“add”, KERNEL==“hci0”, RUN+="/usr/bin/hciconfig hci0 up"[/QUOTE]
I tried the above suggestion and that doesn’t seem to be the problem. Reloaded and rebooted the udev rules, no joy. Held select to “unpair” from other devices. The MAC address does change depending on which startup mode is used but I’m not sure on the relavence since it doesn’t matter which startup mode I use it still won’t connect to Lakka. Unlike when I plug it into usb it pops up and displays the controller type and port. Any other suggestions? I’ve read that people have gotten these to work so I’m sure it’s something I’m missing or not doing right. Does anyone have step by step instructions on how to get the 8bitdo controllers working via bluetooth from a completely new install? As always, thanks.
Ok I may have found something of use. when checking status of bluetooth I get the following:
systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2016-02-29 21:34:28 UTC; 10min ago Main PID: 498 (bluetoothd) Status: “Running” CGroup: /system.slice/bluetooth.service └─498 /usr/lib/bluetooth/bluetoothd
Feb 29 21:34:28 Lakka systemd[1]: Started Bluetooth service. Feb 29 21:34:28 Lakka bluetoothd[498]: Bluetooth daemon 5.27 Feb 29 21:34:28 Lakka bluetoothd[498]: Starting SDP server Feb 29 21:34:28 Lakka bluetoothd[498]: Failed to open RFKILL control device Feb 29 21:34:28 Lakka bluetoothd[498]: Bluetooth management interface 1.10 …ed Hint: Some lines were ellipsized, use -l to show in full.
"Failed to open RFKILL control device" does this mean it’s unable to locate the bluetooth on the asus?
:SOLVED:
I’m not sure what happened but at some point after doing the steps above I tried going back through the pairing process and using the “scan on” code to view the MAC address and was able to connect to it with the connect “XX:XX:XX:XX:XX:XX” X’s being the MAC address. Thanks to everyone’s help!
1 Like