Bluetooth not working after update - need info [obsolete]

[PhilE]

Try here: http://downloads.raspberrypi.org/raspbian/images/

[Steven Boelens]

I downloaded the Jessie image from march. With this completely fresh install the dmesg still mentions "mmc1: error -110 whilst initialising SDIO card". So I guess this isn't related to the last release.
Maybe my RPi is faulty indeed.

I will try this SD card in new RPi coming week.

Thanks for the help so far.

[gvandenbosch]

Hello,

I have a Raspberry PI 3 and am trying to get the internal Bluetooth to run.
However I am getting Connection timed out on several commands.

The bluetooth service is running:

Code: Select all

systemctl status bluetooth -l
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
   Active: active (running) since Tue 2016-11-22 02:41:35 UTC; 5min ago
     Docs: man:bluetoothd(8)
 Main PID: 558 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─558 /usr/lib/bluetooth/bluetoothd --noplugin=sap

I have disabled the SAP because it was giving an error.

The hciconfig displays device info but already gives the first timeout error.

Code: Select all

hci0:	Type: BR/EDR  Bus: UART
	BD Address: B8:27:EB:F1:64:C8  ACL MTU: 1021:8  SCO MTU: 64:1
	UP RUNNING 
	RX bytes:717 acl:0 sco:0 events:42 errors:0
	TX bytes:1546 acl:0 sco:0 commands:44 errors:0
	Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
	Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
	Link policy: RSWITCH SNIFF 
	Link mode: SLAVE ACCEPT 
Can't read local name on hci0: Connection timed out (110)

If I do a scan I also get a timeout:

Code: Select all

hcitool scan
Scanning ...
Inquiry failed: Connection timed out

Other thing I tried is to make the device discoverable, with bluetoothctl but this fails as well:

Code: Select all

discoverable on
Failed to set discoverable on: org.freedesktop.DBus.Error.NoReply

I have tried following things:
- sudo rpi-update
- sudo apt-get --reinstall install pi-bluetooth

Version details:

Code: Select all

cat /proc/version 
Linux version 4.4.33-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #927 SMP Sat Nov 19 18:15:38 GMT 2016

What could be going wrong?

[PhilE]

Your Pi might not have enough power to work correctly, which can cause the Bluetooth/WiFi chip to fail during or shortly after startup.

1) What does "vcgencmd get_throttled" return?

2) What power supply are you using?

3) What else is connected to your Pi?

In case undervoltage isn't the cause of the problem, which distribution are you running? Could you install a fresh Raspbian onto a spare card and see if it works using the Bluetooth GUI?

[Cowpoke]

Of recent, I am having issues with my RPi 3. Wireless connectivity is fine, however, my bluetooth connection doesn't work. As others have noted, the power-up screen shows failed at Configure Bluetooth Modems connected by UART.

I investigated and found that the system was trying to connect at /dev/serial1. That doesn't exist as a device or link. Per aoakley (and others') suggestions, I manually created the link. I run the following (with sudo):

Code: Select all

 ln -s /dev/ttyAMA0 /dev/serial1
 modprobe hci_uart
 /usr/bin/hciattach /dev/serial1 bcm43xx 921600 noflow -

Afterwards, when I query the status, via:

Code: Select all

sudo systemctl status hciuart.service -l

I still get an adverse response:

Code: Select all

* hciuart.service - Configure Bluetooth Modems connected by UART
   Loaded: loaded (/lib/systemd/system/hciuart.service; enabled)
   Active: failed (Result: exit-code) since Sun 2016-11-20 15:09:44 PST; 1 day 15h ago
  Process: 451 ExecStart=/usr/bin/hciattach /dev/serial1 bcm43xx 921600 noflow - (code=exited, status=1/FAILURE)

Nov 20 15:09:44 pico hciattach[451]: Can't open serial port: No such file or directory
Nov 20 15:09:44 pico hciattach[451]: Can't initialize device: No such file or directory
Nov 20 15:09:44 pico systemd[1]: hciuart.service: control process exited, code=exited status=1
Nov 20 15:09:44 pico systemd[1]: Failed to start Configure Bluetooth Modems connected by UART.
Nov 20 15:09:44 pico systemd[1]: Unit hciuart.service entered failed state.

I used to have teamviewer installed (I used it); I've removed it as a roll-back to base. No game though.

Anyone else have a similar experience? Anyone find a fix?

Ride on,
Cowpoke

[PhilE]

The /dev/serial<n> symlinks should be created by a udev rule (/etc/udev/rules.d/99-com.rules) that reads /proc/device-tree/aliases/uart<n> and serial<n> and matches them up. The firmware determines the uart<->serial mapping.

Which distribution are you running?

Do you have any dtoverlays or dtparams in config.txt?

What do you get from running this command?:

Code: Select all

sudo vcdbg log msg |& grep -v -E "(HDMI|gpioman)"

[Cowpoke]

Thx!

Reviewing my /etc/udev/rules.d directory, I realized that I unwittingly broke the bluetooth interface when I was configuring a different rule to mount an android device on my RPi. I had renamed 99-com.rules to 99-rules.com.old - which broke the bluetooth interface.

Reverting the file name fixed the problem.

Ride on,
Cowpoke

[gvandenbosch]

Your Pi might not have enough power to work correctly, which can cause the Bluetooth/WiFi chip to fail during or shortly after startup.

1) What does "vcgencmd get_throttled" return?

2) What power supply are you using?

3) What else is connected to your Pi?

In case undervoltage isn't the cause of the problem, which distribution are you running? Could you install a fresh Raspbian onto a spare card and see if it works using the Bluetooth GUI?

1) returns throttled=0x0

2) I have now replaced my power supply with 5V 2.5A but still same problem

3) Ethernet connected and internal Wifi chip is running a AccessPoint

I am running Raspbian Jessy.

Edit I have tried a clean Raspbian and that is working, what could be the issue in this case?

[Steven Boelens]

I tried the same SD card in a new RPi3 and this gave wlan and bluetooth right away. I retried my old RPi3 again with the same card, no wireless interfaces.
So I guess my old Pi is dead. This is my first Pi of about 10 that has deceased, I am sad now. Is a three day mourning period appropriate?

Should I give it a ceremonial burial or is someone from the foundation or the manufacturers interested in analyzing what actually broke so they can perhaps improve production?

[DougieLawson]

Should I give it a ceremonial burial or is someone from the foundation or the manufacturers interested in analyzing what actually broke so they can perhaps improve production?

Most die because of inappropiate abuse (with voltages over 3.3V and/or currents over 16mA) of the GPIO pins by the end user.

[another bob]

I'm working on getting this going with the latest volumio image.

Code: Select all

Linux volumio 4.4.9-v7+ #884 SMP Fri May 6 17:28:59 BST 2016 armv7l GNU/Linux

RPI 3 w/ touchscreen -
Installed pi-bluetooth, blues 5 and pulse audio 5 and did the fixes suggested earlier in this post. I've also done a forced reinstall of pulse. I've also tried this set up compiling pulse 6. Using this link as a guide http://youness.net/raspberry-pi/bluetoo ... spberry-pi

I've able to get my bluetooth speaker pair, trusted and connected. One time... many many re-images ago... I got a pulseaudio sink. I rebooted and have never been able to get my bluetooth "seen" as a sink in pulse.

Here's bluetoothctl with the connected and paired device... it pairs automatically and stays connected for around 3 mins because there's no audio...

Speaker info:

Code: Select all

[CHG] Device A0:E9:DB:5D:F3:66 Connected: yes
[CHG] Device A0:E9:DB:5D:F3:66 UUIDs:
	00001108-0000-1000-8000-00805f9b34fb
	0000110b-0000-1000-8000-00805f9b34fb
	0000110c-0000-1000-8000-00805f9b34fb
	0000110d-0000-1000-8000-00805f9b34fb
	0000110e-0000-1000-8000-00805f9b34fb
	0000111e-0000-1000-8000-00805f9b34fb

Code: Select all

[bluetooth]# info A0:E9:DB:5D:F3:66
Device A0:E9:DB:5D:F3:66
	Name: Marley Liberate BT
	Alias: Marley Liberate BT
	Class: 0x240404
	Icon: audio-card
	Paired: yes
	Trusted: yes
	Blocked: no
	Connected: yes
	LegacyPairing: no
	UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)

Controller info:

Code: Select all

[bluetooth]# list
Controller B8:27:EB:C2:71:B5 volumio [default]
[bluetooth]# show B8:27:EB:C2:71:B5
Controller B8:27:EB:C2:71:B5
	Name: volumio
	Alias: volumio
	Class: 0x0c0000
	Powered: yes
	Discoverable: no
	Pairable: yes
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v1D6Bp0246d0517
	Discovering: no

Here's the output from Pulse audio list-sinks

Code: Select all

volumio@volumio:~$ pacmd list-sinks
1 sink(s) available.
  * index: 0
	name: <alsa_output.0.analog-stereo>
	driver: <module-alsa-card.c>
	flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY FLAT_VOLUME DYNAMIC_LATENCY
	state: SUSPENDED
	suspend cause: IDLE 
	priority: 9009
	volume: front-left: 26241 /  40% / -23.85 dB,   front-right: 26241 /  40% / -23.85 dB
	        balance 0.00
	base volume: 56210 /  86% / -4.00 dB
	volume steps: 65537
	muted: no
	current latency: 0.00 ms
	max request: 0 KiB
	max rewind: 0 KiB
	monitor source: 0
	sample spec: s16le 2ch 44100Hz
	channel map: front-left,front-right
	             Stereo
	used by: 0
	linked by: 0
	configured latency: 0.00 ms; range is 0.50 .. 371.52 ms
	card: 0 <alsa_card.0>
	module: 6
	properties:
		alsa.resolution_bits = "16"
		device.api = "alsa"
		device.class = "sound"
		alsa.class = "generic"
		alsa.subclass = "generic-mix"
		alsa.name = "bcm2835 ALSA"
		alsa.id = "bcm2835 ALSA"
		alsa.subdevice = "0"
		alsa.subdevice_name = "subdevice #0"
		alsa.device = "0"
		alsa.card = "0"
		alsa.card_name = "bcm2835 ALSA"
		alsa.long_card_name = "bcm2835 ALSA"
		device.bus_path = "/devices/virtual/sound/card0"
		sysfs.path = "/devices/virtual/sound/card0"
		device.string = "hw:0"
		device.buffering.buffer_size = "65536"
		device.buffering.fragment_size = "65536"
		device.access_mode = "mmap+timer"
		device.profile.name = "analog-stereo"
		device.profile.description = "Analog Stereo"
		device.description = "bcm2835 ALSA Analog Stereo"
		alsa.mixer_name = "Broadcom Mixer"
		module-udev-detect.discovered = "1"
		device.icon_name = "audio-card"
	ports:
		analog-output: Analog Output (priority 9900, latency offset 0 usec, available: unknown)
			properties:
				
	active port: <analog-output>

This is the output from sudo systemctl status hciuart.service -l ● hciuart.service - Configure Bluetooth Modems connected by UART

Code: Select all

volumio@volumio:~$ sudo systemctl status hciuart.service -l ● hciuart.service - Configure Bluetooth Modems connected by UART
● hciuart.service - Configure Bluetooth Modems connected by UART
   Loaded: loaded (/lib/systemd/system/hciuart.service; enabled)
   Active: active (running) since Sat 2017-01-07 20:52:44 UTC; 26min ago
  Process: 486 ExecStart=/usr/bin/hciattach /dev/serial1 bcm43xx 921600 noflow - (code=exited, status=0/SUCCESS)
 Main PID: 672 (hciattach)
   CGroup: /system.slice/hciuart.service
           └─672 /usr/bin/hciattach /dev/serial1 bcm43xx 921600 noflow -

Jan 07 20:52:40 volumio systemd[1]: Starting Configure Bluetooth Modems connected by UART...
Jan 07 20:52:44 volumio hciattach[486]: bcm43xx_init
Jan 07 20:52:44 volumio hciattach[486]: Flash firmware /lib/firmware/BCM43430A1.hcd
Jan 07 20:52:44 volumio hciattach[486]: Set Controller UART speed to 921600 bit/s
Jan 07 20:52:44 volumio hciattach[486]: Device setup complete
Jan 07 20:52:44 volumio systemd[1]: Started Configure Bluetooth Modems connected by UART.

● \xe2\x97\x8f.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

● hciuart.service - Configure Bluetooth Modems connected by UART
   Loaded: loaded (/lib/systemd/system/hciuart.service; enabled)
   Active: active (running) since Sat 2017-01-07 20:52:44 UTC; 26min ago
  Process: 486 ExecStart=/usr/bin/hciattach /dev/serial1 bcm43xx 921600 noflow - (code=exited, status=0/SUCCESS)
 Main PID: 672 (hciattach)
   CGroup: /system.slice/hciuart.service
           └─672 /usr/bin/hciattach /dev/serial1 bcm43xx 921600 noflow -

Jan 07 20:52:40 volumio systemd[1]: Starting Configure Bluetooth Modems connected by UART...
Jan 07 20:52:44 volumio hciattach[486]: bcm43xx_init
Jan 07 20:52:44 volumio hciattach[486]: Flash firmware /lib/firmware/BCM43430A1.hcd
Jan 07 20:52:44 volumio hciattach[486]: Set Controller UART speed to 921600 bit/s
Jan 07 20:52:44 volumio hciattach[486]: Device setup complete
Jan 07 20:52:44 volumio systemd[1]: Started Configure Bluetooth Modems connected by UART.

● -.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

● Configure.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

● Bluetooth.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

● Modems.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

● connected.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

● by.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

● UART.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

I've done a force reinstall of pulse audio... any other suggestions? I'm guessing that this has a lot to do with the services that seem to be missing but I'm not sure why or what to do about that. I'm on a no sleep till this works mission... help!

[Douglas6]

Have you installed pulseaudio-module-bluetooth?

[Xarathos]

My issue didn't start after an update. I'm a new user and can't get a Bluetooth speaker to play music. I've read two different threads and tried every suggestion posted. I've also Googled and tried fixes that I've found there. No luck. The Bluetooth icon is pulsing. When I try to connect the speaker, Amplify BSP20, I get "connection failed - use the audio...". Pulseaudio gives me a "fatal error: unable to connect...". When I launch a browser and try to play music on Youtube the page won't load properly. It slows down. I run a few commands and found the following.

Code: Select all

pi@raspberrypi:~ $ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
   Active: active (running) since Tue 2017-01-31 12:55:24 EST; 18min ago
     Docs: man:bluetoothd(8)
 Main PID: 799 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─799 /usr/lib/bluetooth/bluetoothd

pi@raspberrypi:~ $ hciconfig -a
hci0:	Type: BR/EDR  Bus: UART
	BD Address: B8:27:EB:23:50:A7  ACL MTU: 1021:8  SCO MTU: 64:1
	UP RUNNING PSCAN ISCAN 
	RX bytes:1081 acl:0 sco:0 events:57 errors:0
	TX bytes:2606 acl:0 sco:0 commands:57 errors:0
	Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
	Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
	Link policy: RSWITCH SNIFF 
	Link mode: SLAVE ACCEPT 
	Name: 'raspberrypi'
	Class: 0x000000
	Service Classes: Unspecified
	Device Class: Miscellaneous, 
	HCI Version: 4.1 (0x7)  Revision: 0xb6
	LMP Version: 4.1 (0x7)  Subversion: 0x2209
	Manufacturer: Broadcom Corporation (15)


pi@raspberrypi:~ $ hcitool scan
Scanning ...
	BE:A1:87:5A:1D:BC	Amplify BSP20

pi@raspberrypi:~ $ vcgencmd get_throttled
throttled=0x0

[Xarathos]

I'm not seeing an issue. Any suggestions? I am considering trying a Bluetooth CSR V4.0 Dongle to see if that solves the issue.

[xiphocoleon]

My bluetooth hardware seems to be working properly, but I have not been able to send files between this Pi and another Pi, or between this Pi and laptop/desktop computers with bluetooth.

1) Did you install a clean image, or did you update?
This RPi came installed with Raspian/Linux 8 Jessie as far as I know.

2) Had you ever used the Bluetooth hardware on the image before you did the update?
No.

3) If you open a terminal and type "bluetoothctl", what messages come up?
[NEW] Controller B8:27:EB:78:07:99 mirror-pi [default]
[NEW] Device B8:27:EB:6C:D2:39 raspberrypi
[NEW] Device 00:1A:7D:DA:71:13 LASTCHANCEPC
[NEW] Device 00:11:67:D4:93:7E SB571


4) If you updated, and you have a spare SD card, please try downloading the clean image and installing it to see if the behaviour is different - can that image find the Bluetooth controller?
I am not able to do this right now.

5) On the image which doesn't work, try removing the Bluetooth plugin from the taskbar (right-click and choose "remove this plugin") and rebooting, and then try "bluetoothctl" in the terminal again - any difference?
N/A

[Douglas6]

Please post a new topic for this new issue.
[EDIT: I see that you have.]

[WRustyLane]

I cannot get my wireless bluetooth keyboard discovered on my Raspberry PI 3. Are there some keyboards that just won't work with a Raspberry PI 3? I got it from e-Bay and is a Chinese product. The model # is BK3001. I have tried everything in all the troubleshooting questions and replies. If this keyboard is incompatible then, what kind of bluetooth keyboard would you suggest? Keep in mind that I'm a retired Vietnam vet on a fixed income. The Raspberry PI 3 is now my main computer since my wife's laptop got an unrecoverable virus (worm) in it and it's crapped out. Thank you.

Rusty

[Richpi82]

Paired but not connecting - Connection Failed No usable services on this device

Anyone able to help with this guys. Bluetooth is pairing fine on Pi3 Model B but cannot connect to any phone.
When connecting the above error appears. I have tested this with a bluetooth enabled speaker but however no audio feed.
Trying to get bluetooth interaction via bluetooth to phone for college project but no joy so far.
Have made all the necessary updates and upgrades, etc but still no look?
Serial is registering the device in bluetooth mode fine.

Thanks

[Douglas6]

I'm confused as to what you are trying to do. Stream audio to a speaker? Stream audio from your phone? Something else?

A new posting would be a good idea. Your issue is not related to the topic of this thread.

[Richpi82]

Hi Douglas6,

I'm new this this Forum since last Friday, apologies for addressing this post under the wrong heading. Basically what I want to do is send (a) file even an image from my Smart Phone Galaxy S4 to my Pi3 via Bluetooth. They see each other fine on discovery and paired perfectly. However when I try connect from the Pi and click on "connect", the error "Connection Failed No usable services on this device" is prompted in the Pi interface.

Referring to the Bluetooth Speaker, I just this as an example, that the Pi is connecting to a device via bluetooth. The phone was tested from phone to phone to make sure it could send and receive files.

What do you make of it and I hope its more clearer. Also what heading should this post be going under?

[Douglas6]

Ah, file transfer. See if this post helps: viewtopic.php?p=963751#p963751

[Richpi82]

Douglas6 absolutely delighted great job, cheers!
The auto enable very handy, for a minute I was questioning why it seemed like there was no connection, but as I sent a file the Listener picked straight away, the connection icon turned green automatically and received the file.
No just need to figure out how to send a file from Pi back to phone.

[Douglas6]

No just need to figure out how to send a file from Pi back to phone.

See this post. The instructions for pairing are out of date, but the part about using ussp-push is still relevant. viewtopic.php?p=675983#p675983

[Richpi82]

Douglas6,

Thanks for addressing all my relevant questions. Sending from both sides now.

Richie

[Xarathos]

I'm still not able to get a speaker to connect. At present I'm using the same dongle that another user has working. When I try to connect this is the result.

Code: Select all

[[bluetooth]# connect BE:A1:87:5A:1D:BC
Attempting to connect to BE:A1:87:5A:1D:BC
[CHG] Device BE:A1:87:5A:1D:BC Connected: yes
Failed to connect: org.bluez.Error.Failed
[CHG] Device BE:A1:87:5A:1D:BC Connected: no
[CHG] Device BE:A1:87:5A:1D:BC Connected: yes
[CHG] Device BE:A1:87:5A:1D:BC Connected: no
/code]
Any ideas or suggestions will be appreciated.