Retropie 3.8 Bluetooth Configure Issue

GJ007

@Floob said in Retropie 3.8 Bluetooth Configure Issue:

@Ransom That fix has been committed already.
Try updating your RetroPie Setup script and trying again now.

will do this evening!
I will report back

GJ007

just tried an update of te setup script; and after that bluetooth seems to freeze up. could be of messing around to much yesterday; will try a fresh install with only updating the setup script in a minute

edit; fresh install with only an updated setup script seems to work. not seeing my nes30 pro controller, so i'm trying an package update.

GJ007

not much luck. BT seems to be working... but a lot of retrying before i even see the nes30 pro... and when i try to connect;

File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 604, in msg_reply_handler
reply_handler(*message.get_args_list(**get_args_opts))
File "/home/pi/RetroPie-Setup/scriptmodules/supplementary/bluetooth/bluez-simple-agent", line 118, in pair_reply
dev_connect(dev_path)
File "/home/pi/RetroPie-Setup/scriptmodules/supplementary/bluetooth/bluez-simple-agent", line 38, in dev_connect
dev.Connect()
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in call
return self._proxy_method(*args, **keywords)
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in call
**keywords)
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.bluez.Error.NotAvailable: Operation currently not available

GJ007

okay, got 1 controller working! and auto updating; very easy setup thanks to the new script.
but i had to retry retry retry to get an bluetooth connection ... could be interference our something like that...

Ransom

No bueno. Unfortunately this hasn't fixed the issue on my end. I've updated everything I can think of, but still no access to the bluetooth configuration settings, only the menu and the flashing cursor in the bottom left.

In the thread I linked to in my original post, someone mentions,

"Your problem is “sixad” which is needed to get the PS3 controller working. For all it$ money the PS3 controller is probably not stadard BT compliant (why would it need special software then). Unfortunately you have to choose between the PS3 controller or other BT devices."

Any possibility this is the issue? I'd hate to think I can't use my PS3 controller on bluetooth if I want to use another.

GJ007

no idea about the PS3 conroller.

i have the both NES30PRO connected and automatic connecting on poweron (thanks to the easy settings in the new script).
but I had to retry for 10~20 times before I could even discover the controllers...

Floob

I've put a brief guide for this here:

riddix

got exactly the same issue as ransom. i want to use ps3 controllers and my 2 ouya controllers, but im not able to use the bluetooth config scrip and even the bluetoothctl command inst working my pi just freezes when i use it.

i think the ps3 controller driver overrides the default bluetooth driver like it does on windows so you cannot use it to connect other devices than ps3 controllers. dont know if this is true but a fix/workaround would be awesome

Ransom

@Floob I know you have videos on how to pair both PS3 controller and as posted above, FC30 Pro controllers. Have you ever had success pairing both on a Pi3? As riddix pointed out and in the link I posted in my original post, there's a belief that the PS3 bluetooth driver is overriding the Pi's, and I'm curious if anyone has had success pairing both controllers as the same time.

riddix

on windows the 3dr part ds3 driver actually overrides the microsoft bluetooth one so it seems plausible thtat this is the case here too, wich would explain why we have both the same issue. Btw i got a fresh 3.8.1 image!

Floob

The manual implies there will be a conflict:
http://qtsixa.sourceforge.net/manual.pdf

Here is a fork that supports a non-official PS3 device, maybe it could help here.
https://github.com/ryonlabaw/qtsixa

Although the process does seem to have a conflict generally with the standard bluetooth drivers.
I'm afraid I dont have a PS3 controller to hand so I can try this out.

BuZz

you cant use ps3controllers and the built in bluetooth stack at the same time currently. Known limitation of the ps3 pairing software.

riddix

so any idea how to work around that? am i able to use a extra bluetooth dongle to pair my extra controllers ?

a quick link to a guid would be very helpful cause i dont find anything that helped me

anyways thx Floob and BuZz <3

Byrn

@BuZz said in Retropie 3.8 Bluetooth Configure Issue:

you cant use ps3controllers and the built in bluetooth stack at the same time currently. Known limitation of the ps3 pairing software.

Ahh there we go, been scratching my head for a week trying to figure out why I couldn't pair both my ps3 controller and then a bluetooth keyboard at the same time (didn't help that the bluetooth script had a bug at the same time haha). Same question as riddix, one dongle for the ps3 controller and another for all other bluetooth needs?

BuZz

no. That wont work either currently. The ps3controller software is set to disable the internal bluetooth stack.

Byrn

Ahh well. My thinking is if it gets the controller to work with the Pi then it can do what it pleases really. Will have to try a standard wireless keyboard until that changes, and I hope it does because I aim to get bluetooth headphones as well. Thanks!

BuZz

The solution is to pair the ps3 controller without sixpair and instead use bluez. However although I can do this on my Ubuntu desktop machine, I couldn't do it reliably on the RPI (I think I did a couple of times, but it wasn't something I could automate). Probably some bugs in the Bluez stack which we will have to revisit in a newer Raspbian. If you can get the ps3controller to manually pair using bluetoothctl (google for some howtos), then you can use other bluetooth devices also.

Ransom

Thanks for all the great responses everyone. This is the only thread where I've seen a definitive answer to this issue.

The question I have now, is there a way to effectively uninstall the PS3 driver, and get control of the bluetooth stack back? I had used the "sudo apt-get --purge remove sixad", which disabled the PS3 controller, but the issue of me not being able to open the bluetooth configuration menus persisted, so I'm not sure it worked.

Starting to feel like I may have to reinstall the whole thing, but hoping to avoid that.

EDIT: Seems like this thread may have some relevant info on getting a PS3 controller to pair natively with the bluetooth, rather than rely on sixad. Haven't done any testing myself, as I'll need to be able to get access to the configuration first, but seems like there may be potential in using other drivers. https://retropie.org.uk/forum/topic/42/shanwan-ps3-controller-pi3-retropie-3-6-bluetooth-setup/123

BuZz

there is an remove option in retropie-setup for it - if bluetooth is still not starting you can try chmod 755 /usr/sbin/bluetoothd

Ransom

Just an update, using the chmod 755 /usr/sbin/bluetoothd command worked (needed to sudo it) to allow me to regain control of the bluetooth configuration settings. I then set about setting up my 8bitdo controller, using @Floob 's video. However, something has gone wrong in the meantime.

I started to have a lot of success from the video, getting so far as to run sudo bluetoothctl so see my controller, and use that to select that controller in the setup menu. So far so good.

At this point, the controller still wasn't working in BT mode, so I opted to manually set up the sudo nano /etc/udev/rules.d/10-local.rules, but here's where things go weird.

From this point, I can no longer run sudo bluetoothctl successfully, as it just seems to stall. I read this is due to the bluetooth daemon not running, so I ran "systemctl status bluetooth" and it's telling me

"● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
   Active: failed (Result: exit-code) since Mon 2016-06-20 02:18:36 UTC; 7min ago
     Docs: man:bluetoothd(8)
  Process: 2872 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, status=203/EXEC)
 Main PID: 2872 (code=exited, status=203/EXEC)"

If I run sudo systemctl start bluetooth, I get

"Job for bluetooth.service failed. See 'systemctl status bluetooth.service' and 'journalctl -xn' for details."

Lastly, if I go back into my bluetooth configuration menu and choose display and register connected devices I get a long error that reads in part:

"Traceback (most recent call last):                       │  
              │   File                                                   │  
              │ "/home/pi/RetroPie-Setup/scriptmodules/supplementary/blu │  
              │ etooth/bluez-test-device", line 44, in <module>          │  
              │     adapter = bluezutils.find_adapter(options.dev_id)    │  
              │   File                                                   │  
              │ "/home/pi/RetroPie-Setup/scriptmodules/supplementary/blu │  
              │ etooth/bluezutils.py", line 14, in find_adapter          │  
              │     return                                               │  
              │ find_adapter_in_objects(get_managed_objects(), pattern)  │  
              │   File                                                   │  
              │ "/home/pi/RetroPie-Setup/scriptmodules/supplementary/blu │  
              │ etooth/bluezutils.py", line 9, in get_managed_objects    │  
              │     manager = dbus.Interface(bus.get_object("org.bluez"

Sorry, I know this is a long message and I'm not sure how to format the code, but have I somehow mucked things up? Any help appreciated.