mdmlv
Posts: 1
Joined: Fri Feb 15, 2019 7:28 am

Re: STICKY: Bluetooth not working after update - need info

Fri Feb 15, 2019 8:36 am

I just downloaded and installed "2018-11-13-raspbian-stretch-full" on a new Pi 3 B+. I am getting an error: "GDBus.Error:org.bluez.Error. Resource temporarily unavailable. Try again later." Further attempts after rebooting produced the same result. The Bluetooth earphones are recognized by the Pi and the error occurs after I use the audio menu to select the the earphones and the connection attempt fails. I am trying to used the included VLC media player with the earphones. VLC media player works fine with the analog output jack driving headphones. It seems that a number of first-time-posters start off on this thread and I have joined their ranks. Any information would be appreciated, since "temporarily unavailable" and "try again later" do not seem to indicate that I am lacking a specific driver or package.

jokhchan
Posts: 9
Joined: Tue Dec 26, 2017 9:26 am
Location: Hong Kong

Re: STICKY: Bluetooth not working after update - need info

Wed Mar 13, 2019 12:36 pm

Yes, I got the same problem. Help please.

jokhchan
Posts: 9
Joined: Tue Dec 26, 2017 9:26 am
Location: Hong Kong

Re: STICKY: Bluetooth not working after update - need info

Wed Mar 13, 2019 1:04 pm

I found the Bluetooth on another Pi installed with older version of Raspbian works fine. Only the Pi installed with the latest version of Raspbian dose not work.

pmower
Posts: 1
Joined: Wed Mar 13, 2019 6:42 pm

Re: STICKY: Bluetooth not working after update - need info

Wed Mar 13, 2019 6:46 pm

I had this same issue and resolved it with the following due to the pulseaudio-module-bluetooth package not being installed.

sudo apt install pulseaudio-module-bluetooth
pulseaudio -k
pulseaudio --start

If the issue is not due to the missing package, the problem in this case is that PulseAudio is not catching up. A common solution to this problem is to restart PulseAudio. Note that it is perfectly fine to run bluetoothctl as root while PulseAudio runs as user. After restarting PulseAudio, retry to connect. It is not necessary to repeat the pairing.

jokhchan
Posts: 9
Joined: Tue Dec 26, 2017 9:26 am
Location: Hong Kong

Re: STICKY: Bluetooth not working after update - need info

Thu Mar 14, 2019 12:02 am

Tried as suggested above, but still not work.

jokhchan
Posts: 9
Joined: Tue Dec 26, 2017 9:26 am
Location: Hong Kong

Re: STICKY: Bluetooth not working after update - need info

Thu Mar 14, 2019 2:10 pm

Today, I re-install the latest version of Raspbian on my Pi 3B. After installation, I performed:

1. $ sudo apt-get update
2. $ sudo apt-get upgrade
3. copy some songs to the pi
4. pair a Bluetooth headphone
5. select the headphone from the volume control on top right hand of the panel
6. $ sudo apt install pulseaudio-module-Bluetooth
7. $ pulseaudio -k
8. $ pulseaudio --start
9. $ cvlc song.m4a

Now I can hear the song from the headphone on-and-off.

But everytime I reboot, I need to perform $ pulseaudio --start again.

Anyone please help me to fix the problem.

jokhchan
Posts: 9
Joined: Tue Dec 26, 2017 9:26 am
Location: Hong Kong

Re: STICKY: Bluetooth not working after update - need info

Thu Mar 14, 2019 2:51 pm

Funny thing happen, even I connect and select the Bluetooth headphone successfully, the sound still goes to the 3.5mm jack. The Bluetooth headphone has no more sound no matter what I did.

JPICentral
Posts: 52
Joined: Wed Jul 18, 2018 3:22 am
Location: Next to the Mojave Desert at 100+ Degree Fahrenheit

Re: STICKY: Bluetooth not working after update - need info

Sat May 18, 2019 11:00 pm

as requested, did bluetoothctl and it gave me the MAC and the Name of the expected bluetooth devices attached including the mouse with the problem (did not know how to copy and pste without mouse help). Did the -a option whose response was registered. This command seems to want more input though man only gives two options and no input on the commands expected. Could only delete the window. How is one supposed to use a command whose features are not included in man?

I did the update today 20190518. I have two back up sd cards with the update done on 20190504 -- I am not in the UK. When I get some down time I will switch to the 20190504 cause a Pi without a mouse is mighty difficult to use!

If I can be of any help just ask. I am traveling mouseless and internet access may present obstacles -- I will do whatever I can.

xtal256
Posts: 14
Joined: Sat Aug 26, 2017 8:34 am

Re: STICKY: Bluetooth not working after update - need info

Sun Jun 02, 2019 8:33 am

Hi,

Not sure if best to post here or start a new thread, but I'm also having bluetooth problems.


Basically, I bought a Pi 3 and used the image from an older Pi 2 (so there was no bluetooth on it). Now, although though the new Pi supports bluetooth, I'm having some trouble getting it working on my image ("Raspbian GNU/Linux 9 (stretch)", upgraded from jessie).

On startup, bluetooth is not enabled:

Code: Select all

$ service bluetooth status
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: inactive (dead)
     Docs: man:bluetoothd(8)

$ service hciuart status
● hciuart.service
   Loaded: masked (/dev/null; bad)
   Active: inactive (dead)
I can start the bluetooth service:

Code: Select all

$ sudo modprobe btusb
$ sudo systemctl start bluetooth
$ service bluetooth status
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2019-06-02 18:26:20 AEST; 15s ago
     Docs: man:bluetoothd(8)
 Main PID: 1958 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─1958 /usr/lib/bluetooth/bluetoothd

Jun 02 18:26:20 Raspberry-Pi systemd[1]: Starting Bluetooth service...
Jun 02 18:26:20 Raspberry-Pi bluetoothd[1958]: Bluetooth daemon 5.43
Jun 02 18:26:20 Raspberry-Pi systemd[1]: Started Bluetooth service.
Jun 02 18:26:20 Raspberry-Pi bluetoothd[1958]: Starting SDP server
Jun 02 18:26:20 Raspberry-Pi bluetoothd[1958]: Bluetooth management interface 1.14 initialized
But when I try to start hciuart it says:

Code: Select all

Failed to start hciuart.service: Unit hciuart.service is masked.
And bluetoothctl says "No default controller available" when I try to do anything with it.


I have read many other posts by people who have problems with bluetooth, and they all seem slightly different to mine. I might find answers somewhere in this 7 page thread, but I'd much appreciate it if someone could point me in the right direction.

thanks

User avatar
Douglas6
Posts: 4739
Joined: Sat Mar 16, 2013 5:34 am
Location: Chicago, IL

Re: STICKY: Bluetooth not working after update - need info

Sun Jun 02, 2019 1:47 pm

Yes, you should have started a new thread. This one yearns to be locked.

You can try unmasking the hciuart service:

Code: Select all

sudo systemctl unmask hciuart 
Or you could try uninstalling bluetooth and pi-bluetooth and re-installing. But the best bet is to flash a new version of Raspbian Stretch.

xtal256
Posts: 14
Joined: Sat Aug 26, 2017 8:34 am

Re: STICKY: Bluetooth not working after update - need info

Tue Jun 04, 2019 1:07 am

Thanks.

I did that, and it said "Removed /etc/systemd/system/hciuart.service". Now the service cannot be found.

How do I re-install this service?

jokhchan
Posts: 9
Joined: Tue Dec 26, 2017 9:26 am
Location: Hong Kong

Re: STICKY: Bluetooth not working after update - need info

Fri Jul 19, 2019 11:39 am

After a few months try and fail, I think I need to give up. Before that, I try to go through some replies/advises one more time from this forum, luckily I found the information from the following link, I tell myself I'll try it with my last effort, if it fail, I'll totally give up on this topic and use audio cable to connect my Bluetooth dongle.

I refer to the following link to solve the problem
http://youness.net/raspberry-pi/how-to- ... berry-pi-3

In order to eliminate those I've done before to solve the problem, I install the OS (NOOBS_v3_2_0) from scratch and do the followings after installation:

1. $ sudo apt-get update
2. $ sudo apt-get upgrade
3. $ sudo apt-get autoremove
4. $ sudo reboot

5. Copy some songs to the pi

6. $ sudo apt-get install pulseaudio pulseaudio-module-bluetooth
7. $ dpkg -l pulseaudio pulseaudio-module-bluetooth

8. Connect the bluetooth speaker

9. $ sudo killall bluealsa
10. $ pulseaudio --start

11 Play songs with the bluetooth speaker, it works fine.

12. I've try to reboot the pi and play the Bluetooth speaker for a few times, it still works fine. I think I've solved the problem.

Although I can use my Bluetooth speaker now, but I still not understand what is the reason, please tell me why it happen if you know. Thanks.

xjust
Posts: 1
Joined: Tue Aug 06, 2019 3:37 pm

Re: STICKY: Bluetooth not working after update - need info

Tue Aug 06, 2019 3:42 pm

hello
bluetooth should work on raspberry pi 4 default installation of raspbian buster ?
i think i might have a defective board if so..

● hciuart.service loaded failed failed Configure Bluetooth Modems connected by UART

tristone
Posts: 4
Joined: Sat Aug 03, 2019 1:26 pm

Re: STICKY: Bluetooth not working after update - need info

Sat Aug 17, 2019 6:52 pm

Hi.

Yes it works out of the box. I had the same issue and spent countless hours trying to make it work.

Then I got replacement board and it started to wok in about a minute

superpowter77
Posts: 19
Joined: Thu Aug 22, 2019 2:38 pm

Re: STICKY: Bluetooth not working after update - need info

Thu Aug 22, 2019 3:19 pm

jokhchan wrote:
Thu Mar 14, 2019 2:51 pm
Funny thing happen, even I connect and select the Bluetooth headphone successfully, the sound still goes to the 3.5mm jack. The Bluetooth headphone has no more sound no matter what I did.
Same here. It was working fine with supplied raspbian stretch. After update, I get exactly the same issue.
Have to select my JBL bluetooth speakers from the speakers icon(right click) instead HDMI or analog set by default if I turn off my machine. Have to do this every time after reboot. Pulse audio volume control for some unknown reason keeps defaulting to 3.5mm jack after rebooot and no longer shows bluetooth speaker or headphone.

superpowter77
Posts: 19
Joined: Thu Aug 22, 2019 2:38 pm

Re: STICKY: Bluetooth not working after update - need info

Wed Sep 11, 2019 12:54 am

Wifi/BT module still buggy on Rpi 4 using latest Raspbian Buster. I have had issues with both, Wifi connetions at 5Ghz and some random and annoying BT audio hiccups. I have been tweaking and changing parameters for days. Finally gave up and uninstalled Rpi 4b's Wifi/BT module and purchased some expensive BT audio dongles with Aptx low latency that actually cost more than a Rpi 4 board and some other more affordable which are dedicated USB BT audio dongles, no data. First thing I notice, a high fidelity option was shown which wasn't there before. So far, All my BT Headphones are working: Audio-Technica m50xBT, Sennheiser HD 4.50, Audio-Technica ATH-AR3BTBK and Plantronics Back beat Pro 2(Aptx LL Codec). My JBL BT speakers as Extreme 2, Charge 3 and Flip 4 Not yet. Audio reproduction is better, crystal clear audio quality. No Hiss, No occasional pop up sounds or random disconnections when I reboot or system go to sleeping mode. I am seeing the light now, still gotta find out why JBL BT speakers are not reproducing any sound despite being recognized by new BT dongles.

User avatar
Douglas6
Posts: 4739
Joined: Sat Mar 16, 2013 5:34 am
Location: Chicago, IL

Re: STICKY: Bluetooth not working after update - need info

Wed Sep 11, 2019 1:07 am

Your post would be much more helpful and informative if you mentioned what you "have been tweaking and changing parameters for days". Also what you mean by "Rpi 4b's Wifi/BT module". "Sleeping mode" I'll just ignore for now.

superpowter77
Posts: 19
Joined: Thu Aug 22, 2019 2:38 pm

Re: STICKY: Bluetooth not working after update - need info

Wed Sep 11, 2019 12:53 pm

Finally, was able to have all my BT audio devices working as intended. For those who opt going into the USB BT dongle route, after testing several dongles cheap and expensive ones I recommend the Plugable USB-BT4LE which is fairly cheap and can be easily found at amazon stores(US and Canada).BTW, they are the only ones that actually advertise full compatibility with all Raspberry Pi boards and all Raspian and Ubuntu Mate OS versions, they have also top notch customer service who reply really fast to your inquiries. It works pretty much right out of the box and has none of the issues I had with internal Cypress CYW43455 chip(Rpi 4b). For the record, I have no affiliation to them. Risking sounding Biased here, I just love whatever gets the job done without too much sweating. Bluetooth audio topic is a close chapter to me now. Cheers.

rob_fer
Posts: 5
Joined: Sat Jul 20, 2019 6:39 am

Re: STICKY: Bluetooth not working after update - need info

Tue Sep 17, 2019 11:09 am

Hi all,
I've gone through the whole thread, I did apply recomendations but I'm still having a problem with my bluetooth.
It looks like it doesn't see the controller. the service starts and agent is registered but when I run "scan on" command I permanently get "No such device" error.
My goal is to use the integrated bluetooth LE module of my raspberry Pi3 b+ to listen without any pairing.

When I run a script that should listen for Bleutooth incoming data I got :
[email protected]:~ $ sudo python3 /usr/local/sbin/collect_data.py
Traceback (most recent call last):
File "/usr/local/sbin/collect_data.py", line 117, in <module>
scanner.scan(5)
File "/usr/local/lib/python3.7/dist-packages/bluepy/btle.py", line 852, in scan
self.start(passive=passive)
File "/usr/local/lib/python3.7/dist-packages/bluepy/btle.py", line 790, in start
self._mgmtCmd("le on")
File "/usr/local/lib/python3.7/dist-packages/bluepy/btle.py", line 312, in _mgmtCmd
raise BTLEManagementError("Failed to execute management command '%s'" % (cmd), rsp)
bluepy.btle.BTLEManagementError: Failed to execute management command 'le on' (code: 17, error: Invalid Index)


Any help will be much appreciated. see beloow some outputs.

[email protected]:~ $ systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: inactive (dead)
Docs: man:bluetoothd(8)

sept. 17 00:24:03 raspberrypi systemd[1]: Condition check resulted in Bluetooth service being skipped.



[email protected]:~ $ sudo systemctl status hciuart.service
● hciuart.service - Configure Bluetooth Modems connected by UART
Loaded: loaded (/lib/systemd/system/hciuart.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2019-09-17 00:24:17 CEST; 1min 13s ago
Process: 314 ExecStart=/usr/bin/btuart (code=exited, status=1/FAILURE)

sept. 17 00:23:38 raspberrypi systemd[1]: Starting Configure Bluetooth Modems connected by UART...
sept. 17 00:24:17 raspberrypi btuart[314]: Initialization timed out.
sept. 17 00:24:17 raspberrypi btuart[314]: bcm43xx_init
sept. 17 00:24:17 raspberrypi systemd[1]: hciuart.service: Control process exited, code=exited, status=1/FAILURE
sept. 17 00:24:17 raspberrypi systemd[1]: hciuart.service: Failed with result 'exit-code'.
sept. 17 00:24:17 raspberrypi systemd[1]: Failed to start Configure Bluetooth Modems connected by UART.



[email protected]:~ $ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: inactive (dead)
Docs: man:bluetoothd(8)

sept. 17 00:24:03 raspberrypi systemd[1]: Condition check resulted in Bluetooth service being skipped.



[email protected]:~ $ sudo hciconfig -a

[email protected]:~ $ sudo systemctl start bluetooth

[email protected]:~ $ systemctl status bluetooth
bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2019-09-17 00:29:32 CEST; 2s ago
Docs: man:bluetoothd(8)
Main PID: 1414 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 2077)
Memory: 1.3M
CGroup: /system.slice/bluetooth.service
└─1414 /usr/libexec/bluetooth/bluetoothd

sept. 17 00:29:32 raspberrypi systemd[1]: Starting Bluetooth service...
sept. 17 00:29:32 raspberrypi bluetoothd[1414]: Bluetooth daemon 5.50
sept. 17 00:29:32 raspberrypi systemd[1]: Started Bluetooth service.
sept. 17 00:29:32 raspberrypi bluetoothd[1414]: Starting SDP server
sept. 17 00:29:32 raspberrypi bluetoothd[1414]:
Bluetooth management interface 1.14 initialized



[email protected]:~ $ sudo bluetoothctl
Agent registered
[bluetooth]# scan on
No default controller available
[bluetooth]#




[email protected]:~ $ sudo apt-get --reinstall install pi-bluetooth
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 0 non mis à jour.
Il est nécessaire de prendre 0 o/4 696 o dans les archives.
Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
(Lecture de la base de données... 149824 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de .../pi-bluetooth_0.1.11_all.deb ...
Dépaquetage de pi-bluetooth (0.1.11) sur (0.1.11) ...
Paramétrage de pi-bluetooth (0.1.11) ...
Job for hciuart.service failed because the control process exited with error code.
See "systemctl status hciuart.service" and "journalctl -xe" for details.



[email protected]:~ $ journalctl -xe
-- Subject: Le démarrage du système est terminé
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Tous les services nécessaires au démarrage du système ont été lancés.
-- Notez que cela ne signifie pas que le système est maintenant au repos,
-- car des services peuvent encore être en train de terminer leur démarrage.
--
-- Le chargement du noyau a nécessité 1645040 microsecondes.
--
-- Le chargement du « RAM disk » initial a nécessité INITRD_USEC microsecondes.
--
-- Le chargement de l'espace utilisateur a nécessité 36045146 microsecondes.
sept. 17 10:55:33 raspberrypi dbus-daemon[504]: [session uid=1000 pid=504] Activating via systemd: service name='org.gtk.vfs.Metadata'
sept. 17 10:55:33 raspberrypi systemd[481]: Starting Virtual filesystem metadata service...
-- Subject: L'unité (unit) UNIT a commencé à démarrer
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- L'unité (unit) UNIT a commencé à démarrer.
sept. 17 10:55:33 raspberrypi dbus-daemon[504]: [session uid=1000 pid=504] Successfully activated service 'org.gtk.vfs.Metadata'
sept. 17 10:55:33 raspberrypi systemd[481]: Started Virtual filesystem metadata service.
-- Subject: L'unité (unit) UNIT a terminé son démarrage
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- L'unité (unit) UNIT a terminé son démarrage, avec le résultat done.
sept. 17 10:56:22 raspberrypi sudo[814]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/systemctl status hciuart.servic
sept. 17 10:56:22 raspberrypi sudo[814]: pam_unix(sudo:session): session opened for user root by (uid=0)
sept. 17 10:56:22 raspberrypi sudo[814]: pam_unix(sudo:session): session closed for user root






[email protected]:~ $ sudo shutdown -r now

[email protected]:~ $ systemctl status hciuart.service
● hciuart.service - Configure Bluetooth Modems connected by UART
Loaded: loaded (/lib/systemd/system/hciuart.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2019-09-17 10:54:23 CEST; 43s ago
Process: 315 ExecStart=/usr/bin/btuart (code=exited, status=1/FAILURE)

sept. 17 10:53:53 raspberrypi systemd[1]: Starting Configure Bluetooth Modems connected by UART...
sept. 17 10:54:23 raspberrypi btuart[315]: Initialization timed out.
sept. 17 10:54:23 raspberrypi btuart[315]: bcm43xx_init
sept. 17 10:54:23 raspberrypi systemd[1]: hciuart.service: Control process exited, code=exited, status=1/FAILURE
sept. 17 10:54:23 raspberrypi systemd[1]: hciuart.service: Failed with result 'exit-code'.
sept. 17 10:54:32 raspberrypi systemd[1]:
Failed to start Configure Bluetooth Modems connected by UART.



[email protected]:~ $ hcitool scan
Device is not available: No such device

User avatar
Douglas6
Posts: 4739
Joined: Sat Mar 16, 2013 5:34 am
Location: Chicago, IL

Re: STICKY: Bluetooth not working after update - need info

Tue Sep 17, 2019 11:37 am

If the hciuart service is failing, nothing Bluetooth related is going to work. Depending on your operating system, you might try installing pi-bluetooth: 'sudo apt install pi-bluetooth'. Otherwise, I would image a new SD card with the latest Buster Raspbian. If hciuart is still failing, you could have a hardware problem.

rob_fer
Posts: 5
Joined: Sat Jul 20, 2019 6:39 am

Re: STICKY: Bluetooth not working after update - need info

Tue Sep 17, 2019 12:00 pm

THanks a lot for your fast response.

I am running Raspbian GNU/Linux 10 (Buster)

rob_fer
Posts: 5
Joined: Sat Jul 20, 2019 6:39 am

Re: STICKY: Bluetooth not working after update - need info

Wed Sep 18, 2019 7:25 am

Hi,
just one more question. Is there any Hardware (firmware) parameter that has to be set?
I mean should some setting be configured with raspi-config?
Thanks in advance for your help.

Return to “Troubleshooting”