Bluetooth no longer working after fresh install

[charleszimm]

Hello everyone,

This has been stumping me for a few days. First the formalities:

Pi Model or other hardware: Pi 3
Power Supply used: Official Power Supply
RetroPie Version Used: 4.4.8
Built From: 4.4 SD Image from retropie.org.uk
USB Devices connected: Logitech USB keyboard, external hard drive
Controller used: 8bitdo SN30 Pro
Error messages received: See below!
Log found in /dev/shm/runcommand.log (if relevant): Nothing there
How to replicate the problem: Not 100% sure because I've never run into this before.

I rebuilt my main RetroPie system to upgrade it to Stretch. I've build way more RetroPie systems using the official images for family and friends, but this is the first time I've run into this.

Everything is built, I've restored all of my content, and then I go to sync my 8bitdo SN30 Pro controller. I go into the RetroPie Setup script, Configuration/Tools, and then Bluetooth. I click on Register and Search and it sits. And when I say it sits, it SITS. No moving. So I break out of it and then go into Display Registered and Connected Bluetooth Devices. It finds anything that has Bluetooth active in my house, including the SN30 Pro.

I removed all of the devices minus the SN30 Pro and tell the Bluetooth menu to connect now to all registers devices. IT WORKED! I bring up EmulationStation but notice some weird lag but I was able to get the controller to work. I put the controller to sleep, go play with my dog, and then come back to the Pi to play some games.

Controller doesn't sync. Just scrolling lights.

I check the usual places, like the bluetooth.service status. I see this:

Feb 18 20:40:58 theaterretropie bluetoothd[571]: connect error: Invalid exchange (52)
Feb 18 20:41:09 theaterretropie bluetoothd[571]: Can't get HIDP connection info
Feb 18 20:41:09 theaterretropie bluetoothd[571]: connect error: Invalid exchange (52)
Feb 18 20:41:20 theaterretropie bluetoothd[571]: Can't get HIDP connection info
Feb 18 20:41:20 theaterretropie bluetoothd[571]: connect error: Invalid exchange (52)
Feb 18 20:41:31 theaterretropie bluetoothd[571]: Can't get HIDP connection info
Feb 18 20:41:31 theaterretropie bluetoothd[571]: connect error: Invalid exchange (52)
Feb 18 20:41:42 theaterretropie bluetoothd[571]: Can't get HIDP connection info
Feb 18 20:41:42 theaterretropie bluetoothd[571]: connect error: Invalid exchange (52)
Feb 18 20:41:53 theaterretropie bluetoothd[571]: Can't get HIDP connection info

Weird.

I check hciuart, and it's running fine.

Feb 18 20:30:34 theaterretropie systemd[1]: Starting Configure Bluetooth Modems connected by UART...
Feb 18 20:30:38 theaterretropie btuart[1367]: bcm43xx_init
Feb 18 20:30:38 theaterretropie btuart[1367]: Flash firmware /lib/firmware/brcm/BCM43430A1.hcd
Feb 18 20:30:38 theaterretropie btuart[1367]: Set BDADDR UART: xx:xx:xx:xx:xx:xx (I changed this)
Feb 18 20:30:38 theaterretropie btuart[1367]: Set Controller UART speed to 921600 bit/s
Feb 18 20:30:38 theaterretropie btuart[1367]: Device setup complete
Feb 18 20:30:38 theaterretropie systemd[1]: Started Configure Bluetooth Modems connected by UART.

I then go into bluetoothctl to just see what is going on. Something really cool started happening (I'll leave this MAC address in because it happens too frequently)

pi@theaterretropie:~ $ bluetoothctl
[NEW] Controller B8:27:EB:81:C7:4C theaterretropie [default]
[NEW] Device 98:B6:E9:42:4B:35 Pro Controller
[CHG] Device 98:B6:E9:42:4B:35 Connected: yes
[CHG] Device 98:B6:E9:42:4B:35 Connected: no
[CHG] Device 98:B6:E9:42:4B:35 Connected: yes
[CHG] Device 98:B6:E9:42:4B:35 Connected: no
[CHG] Device 98:B6:E9:42:4B:35 Connected: yes
[CHG] Device 98:B6:E9:42:4B:35 Connected: no

And it just repeats. I tried reinstalled bluetooth and pi-bluetooth to no gains. The SN30 Pro just cycles its lights.

Very weird, right? I responded on a thread on Reddit and it seems like this is happening to others. I don't want to abandon this image and revery back to a Jessie version but I might just because I want to use my device again.

Am I alone in this?

[snoogans]

I can confirm I am having this same issue. I built a RetroPie system for a friend this weekend and ran into the same issue.

Pi Model or other hardware: Pi 3B+
Power Supply used: Official Power Supply
Built From: 4.4 SD Image from retropie.org.uk
USB Devices connected: keyboard
Controller used: 8bitdo SF30 Pro

After the initial installation I ran the updates to both the RetroPie script and the system updates. Installed a few emulators and Steven Selph's scraper. When I went to add the controller it just hangs on searching. In an effort to troubleshoot I checked my build, which I also ran the updates on, and it hangs on searching too.

To troubleshoot I took another SD card, loaded the same image, and then tested BT after every change. It was fine through everything, including running system updates outside of ES, updating packages (core, main and optional) and updating the raspi-config tool. As soon as I updated the RetroPie setup script it would break BT.

The only thing I could find with similar issues had PS3 controllers installed. This was a fresh install from the official image so I was stumped. I believe it's something with the RetroPie script.

I didn't get as far as actually adding the controller through connect all registered and connected devices but it did find all the BT devices.

[BuZz]

I don't have this particular controller, so this may not be very useful. You have latest firmware and powered on in the right mode before registering?

[snoogans]

Yes. But, I don't believe the controller is the issue. It hangs on searching and never gets to the list of devices to register. I let it search for about 15 minutes just to see if it would get past it. Obviously, it doesn't.

[BuZz]

@snoogans would be better to start new topic. Different controller. I have your controller btw and it works on latest. Get 4.1 firmware though.

[snoogans]

I can do that, but my it works in my build too. But, it was already registered before the updates. Try and add a new device and if it makes it past searching I will start a new thread.

[BuZz]

@snoogans I re-added my fc30 pro last week after updating them. There was a bug with Bluetooth gui returning to main menu after scanning. That's fixed now though so make sure you have retropie 4.4.8

[BuZz]

Sorry to tag you @psyke83 - anything related to PS3 changes you can think of that might affect this? You are more familiar with the stack than me.

[psyke83]

@charleszimm said in Bluetooth no longer working after fresh install:

98:B6:E9:42:4B:35

Can you paste the output of info 98:B6:E9:42:4B:35 in bluetoothctl?

If it says "Trusted: no", try manually trusting via trust 98:B6:E9:42:4B:35 as well, and then check the info again to see if trust is enabled (and let us know whether that makes the controller start working).

[snoogans]

I just verified that I have the latest firmware for the controller, 1.29, and the Retropie setup script is 4.4.8. It hangs on searching.

[BuZz]

@snoogans the latest firmware is 4.1 for fc30 pro. Their support site is a bit confusing though.

[BuZz]

@snoogans try disabling PS3 driver first btw. If that's enabled.

[charleszimm]

@psyke83 Wasn't trusted but behaving the same way:

[bluetooth]# info 98:B6:E9:42:4B:35
Device 98:B6:E9:42:4B:35
Name: Pro Controller
Alias: Pro Controller
Class: 0x002508
Icon: input-gaming
Paired: yes
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: usb:v057Ep2009d0001
[bluetooth]# trust 98:B6:E9:42:4B:35
[CHG] Device 98:B6:E9:42:4B:35 Trusted: yes
Changing 98:B6:E9:42:4B:35 trust succeeded
[CHG] Device 98:B6:E9:42:4B:35 Connected: yes
[CHG] Device 98:B6:E9:42:4B:35 Connected: no
[CHG] Device 98:B6:E9:42:4B:35 Connected: yes
[CHG] Device 98:B6:E9:42:4B:35 Connected: no

[psyke83]

@charleszimm

I'd first like to know why the "Register" option is getting stuck in a loop; I suspect that it's caused by bluetoothctl constantly reporting your device "Connected: xxx" non-stop.

Try to remove the offending device (either via the menu option or manually in bluetoothctl), then let me know if the "Register and Connect" option works (or at least progresses to the list of devices after 20 seconds without having to be interrupted).

[charleszimm]

@psyke83 okay I’ll give that a shot. Don’t be alarmed if I don’t get back to you for a few hours since my calendar is pretty full today. Thanks for your help!

[charleszimm]

@psyke83 Okay finally got to it. Sorry for the delay.

When I went to remove the controller through bluetoothctl, this happened:

[bluetooth]# devices
Device 98:B6:E9:42:4B:35 Pro Controller
[bluetooth]# remove 98:B6:E9:42:4B:35
[DEL] Device 98:B6:E9:42:4B:35 Pro Controller
Device has been removed
[DEL] Controller B8:27:EB:81:C7:4C theaterretropie [default]
Waiting to connect to bluetoothd...

I check the bluetooth.service status and crashy crash crash.

pi@theaterretropie:~ $ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: failed (Result: signal) since Wed 2019-02-20 08:01:45 EST; 1min 32s ago
Docs: man:bluetoothd(8)
Main PID: 571 (code=killed, signal=SEGV)
Status: "Running"

Feb 20 08:01:10 theaterretropie bluetoothd[571]: Can't get HIDP connection info
Feb 20 08:01:15 theaterretropie bluetoothd[571]: connect error: Host is down (112)
Feb 20 08:01:21 theaterretropie bluetoothd[571]: Can't get HIDP connection info
Feb 20 08:01:27 theaterretropie bluetoothd[571]: connect error: Host is down (112)
Feb 20 08:01:32 theaterretropie bluetoothd[571]: Can't get HIDP connection info
Feb 20 08:01:38 theaterretropie bluetoothd[571]: connect error: Host is down (112)
Feb 20 08:01:43 theaterretropie bluetoothd[571]: Can't get HIDP connection info
Feb 20 08:01:45 theaterretropie systemd[1]: bluetooth.service: Main process exited, code=killed, status=11/SEGV
Feb 20 08:01:45 theaterretropie systemd[1]: bluetooth.service: Unit entered failed state.
Feb 20 08:01:45 theaterretropie systemd[1]: bluetooth.service: Failed with result 'signal'.

I restart bluetooth.service and no errors:

pi@theaterretropie:~ $ sudo systemctl start bluetooth.service
pi@theaterretropie:~ $ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2019-02-20 08:03:30 EST; 5s ago
Docs: man:bluetoothd(8)
Main PID: 29848 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
└─29848 /usr/lib/bluetooth/bluetoothd

Feb 20 08:03:30 theaterretropie bluetoothd[29848]: Starting SDP server
Feb 20 08:03:30 theaterretropie bluetoothd[29848]: Bluetooth management interface 1.14 initialized
Feb 20 08:03:30 theaterretropie bluetoothd[29848]: Failed to obtain handles for "Service Changed" characteristic
Feb 20 08:03:30 theaterretropie bluetoothd[29848]: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Feb 20 08:03:30 theaterretropie bluetoothd[29848]: avrcp-controller: Protocol not supported (93)
Feb 20 08:03:30 theaterretropie bluetoothd[29848]: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
Feb 20 08:03:30 theaterretropie bluetoothd[29848]: audio-avrcp-target: Protocol not supported (93)
Feb 20 08:03:30 theaterretropie bluetoothd[29848]: Sap driver initialization failed.
Feb 20 08:03:30 theaterretropie bluetoothd[29848]: sap-server: Operation not permitted (1)
Feb 20 08:03:30 theaterretropie bluetoothd[29848]: Failed to set privacy: Rejected (0x0b)

Some of those things don't look good but I continue forward. I go back into bluetoothctl and start the scan (I won't post all of the MAC address that it finds since it obviously finds everything that has Bluetooth enabled in the house, but just the SN30 Pro)

[bluetooth]# devices
[bluetooth]# scan on
[NEW] Device 98:B6:E9:42:4B:35 Pro Controller
[bluetooth]# connect 98:B6:E9:42:4B:35
Attempting to connect to 98:B6:E9:42:4B:35
[CHG] Device 98:B6:E9:42:4B:35 Connected: yes
[CHG] Device 98:B6:E9:42:4B:35 Connected: no
Failed to connect: org.bluez.Error.Failed
[bluetooth]# info 98:B6:E9:42:4B:35
Device 98:B6:E9:42:4B:35
Name: Pro Controller
Alias: Pro Controller
Class: 0x002508
Icon: input-gaming
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
RSSI: -77
[bluetooth]# trust 98:B6:E9:42:4B:35
[CHG] Device 98:B6:E9:42:4B:35 Trusted: yes
Changing 98:B6:E9:42:4B:35 trust succeeded
[bluetooth]# info 98:B6:E9:42:4B:35
Device 98:B6:E9:42:4B:35
Name: Pro Controller
Alias: Pro Controller
Class: 0x002508
Icon: input-gaming
Paired: no
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no

At this point I try to turn the controller back on.

[bluetooth]# connect 98:B6:E9:42:4B:35
Attempting to connect to 98:B6:E9:42:4B:35
[CHG] Device 98:B6:E9:42:4B:35 Connected: yes
[CHG] Device 98:B6:E9:42:4B:35 Modalias: usb:v057Ep2009d0001
[CHG] Device 98:B6:E9:42:4B:35 UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[CHG] Device 98:B6:E9:42:4B:35 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 98:B6:E9:42:4B:35 ServicesResolved: yes
[CHG] Device 98:B6:E9:42:4B:35 Paired: yes
Connection successful

Success!

So for entertainment sake, I turn off the controller.

[Pro Controller]# info 98:B6:E9:42:4B:35
Device 98:B6:E9:42:4B:35
Name: Pro Controller
Alias: Pro Controller
Class: 0x002508
Icon: input-gaming
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: usb:v057Ep2009d0001

It still showed connected which was weird. So I turned the controller back on and bluetoothctl updated with this:

[CHG] Device 98:B6:E9:42:4B:35 ServicesResolved: no
[CHG] Device 98:B6:E9:42:4B:35 Connected: no
[CHG] Device 98:B6:E9:42:4B:35 Connected: yes

I look up at the TV and the controller is working. I decided to reboot the Pi to see if the controller automatically syncs. It does!

pi@theaterretropie:~ $ bluetoothctl
[NEW] Controller B8:27:EB:81:C7:4C theaterretropie [default]
[NEW] Device 98:B6:E9:42:4B:35 Pro Controller
[CHG] Device 98:B6:E9:42:4B:35 Connected: yes

So I'm not sure what this tells us. I started digging through the bluetooth.sh script under scriptmodules/supplementary directory to see if anything strikes me that could be causing it to get stuck between bluez, hcitool, and bluetoothctl.

I did notice something weird though. If I go into RetroArch, it doesn't detect the controller as a "RetroPad" like it use to. Instead it is treating the controller as a keyboard but that might be a different topic for a different post.

[psyke83]

@charleszimm,

Despite your success, some of your output is still concerning, and we still need to establish whether there's a potential problem in the Bluetooth script that needs addressing.

A potential fix for the infinite hang has just been merged (https://github.com/RetroPie/RetroPie-Setup/pull/2625). Can you try updating your script to ensure you have this change, and then remove & re-register your device, but this time only using the Bluetooth script?

[charleszimm]

@psyke83 said in Bluetooth no longer working after fresh install:

https://github.com/RetroPie/RetroPie-Setup/pull/2625

Totally agree with the output concerns. I felt the same way which was why I started digging around the setup script. Give me a few minutes to update the script and remove the device from the bluetoothctl registration.

[charleszimm]

@psyke83 Update:

Got the latest script and confirmed the commit times matched with the Github post.

I no longer hang on "Searching..." so that's all good. It picked up the SN30 Pro, I got the prompt for the input mode, but then I get:

"An error occurred connecting to the bluetooth device (Creating device failed: org.bluez.Error.AuthenticationFailed: Authentication Failed)"

It shows as a registered device but so does every Bluetooth device in the house. The daemon.log shows:

Feb 20 09:29:00 theaterretropie bluetoothd[545]: Refusing input device connect: No such file or directory (2)
Feb 20 09:29:00 theaterretropie bluetoothd[545]: Refusing connection from 98:B6:E9:42:4B:35: unknown device
Feb 20 09:29:06 theaterretropie bluetoothd[545]: 98:B6:E9:42:4B:35: error updating services: Host is down (112)
Feb 20 09:31:43 theaterretropie bluetoothd[545]: Refusing input device connect: No such file or directory (2)
Feb 20 09:31:43 theaterretropie bluetoothd[545]: Refusing connection from 98:B6:E9:42:4B:35: unknown device
Feb 20 09:31:48 theaterretropie bluetoothd[545]: Refusing input device connect: No such file or directory (2)
Feb 20 09:31:48 theaterretropie bluetoothd[545]: Refusing connection from 98:B6:E9:42:4B:35: unknown device

Bluetoothctl shows the device. I try to start the controller up after the sync through the Setup Script and I no longer get stuck in the Connected yes/no loop, but I got automatically disconnected:

pi@theaterretropie:~ $ bluetoothctl
[NEW] Controller B8:27:EB:81:C7:4C theaterretropie [default]
[NEW] Device 98:B6:E9:42:4B:35 Pro Controller
[CHG] Device 98:B6:E9:42:4B:35 Connected: yes
[CHG] Device 98:B6:E9:42:4B:35 Connected: no

I checked info and it does show pair but not trusted. I decided to try to trust it but same connected yes/no:

[bluetooth]# info 98:B6:E9:42:4B:35
Device 98:B6:E9:42:4B:35
Name: Pro Controller
Alias: Pro Controller
Class: 0x002508
Icon: input-gaming
Paired: yes
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
[bluetooth]# trust 98:B6:E9:42:4B:35
[CHG] Device 98:B6:E9:42:4B:35 Trusted: yes
Changing 98:B6:E9:42:4B:35 trust succeeded
[CHG] Device 98:B6:E9:42:4B:35 Connected: yes
[CHG] Device 98:B6:E9:42:4B:35 Connected: no

[BuZz]

@charleszimm just to confirm, you're running latest firmware on controller and have powered on in the correct mode? Apologies if.you have already answered these. Gets confusing with multiple user issues on one thread :-)