Package Details: pi-bluetooth 1.2_4-1

Git Clone URL: (read-only)
Package Base: pi-bluetooth
Description: Services, firmware and udev rules to get integrated bluetooth running in Raspberry Pi 3
Upstream URL: None
Licenses: Multiple
Submitter: Huulivoide
Maintainer: blm768
Last Packager: blm768
Votes: 25
Popularity: 0.777983
First Submitted: 2016-03-19 20:54
Last Updated: 2019-04-12 03:51

Latest Comments

1 2 3 4 5 Next › Last »

emmanuelux commented on 2019-10-13 00:20

after 2 weeks of use, i can say it is stable on PI 4 ... in waiting for a better support to avoid /sys/class/bluetooth/hc0 and /sys/class/bluetooth/hc1 created if we dont blacklist btsdio (or other module)

LordSocky commented on 2019-10-05 23:25

The raw package didn't work for me on my Raspberry Pi 4, but I can confirm the directions provided by emmanuelux work. I haven't encountered any of the mentioned stability problems, but I only have a singular bluetooth controller on it (8Bitdo SF30 Pro) and have only lightly tested it so far, so perhaps I just haven't given it enough chances to break.

If I encounter any problems, I'll add them to this comment later.

emmanuelux commented on 2019-09-29 21:11

I get it working on PI 4, without bluez-utils-compat

I use btattach in place of hciattach (deprecated) in brcm43438.service

I have changed this :

ExecStart=/usr/bin/hciattach -n /dev/ttyAMA0 bcm43xx 921600 noflow -

ExecStart=/usr/bin/btattach -B /dev/ttyAMA0 -P bcm -S 3000000

I use 3000000 for baurate as it is used for PI 3 according to gentoo wiki (I don't know the correct baud rate for PI 4), see there (link in PKGBUILD too) :

I use blueman as GUI config and bluetoothctl as command line config. It is OK after some tries and errors with xbox one controllers and bluetooth keyboard (not 100% stable, one kernel crash, but ok for now)

A second hci1 adapter is created with this driver (hci0 and hci1). To avoid this, we need to blacklist the module btsdio in /etc/modprobe.d/raspi-blacklist.conf (see :

blacklist btsdio

Neil commented on 2019-09-17 17:13

@blm768: Thanks for the reply. Not sure if a recent update has sorted things, but so far it seems reliable (or I've just got lucky!)

blm768 commented on 2019-09-13 06:08

@Neil: I haven't tested on Pi 4 hardware since I've just got a Pi 3 (which seems to be rather temperamental). I'll probably look at integrating the scripts from the official repo, though, which may help.

Neil commented on 2019-09-08 18:52

Has anyone tried this package on the Raspberry Pi 4? I've got it up and running, but sometimes the brcm43438 service fails to start due to the hciattach command timing out. Sometimes starting the service at the command line does the trick, but it other cases a few reboots are required to get it to start at boot.

keithspg commented on 2019-04-27 15:31

Still struggling here. I do not know how much of my problem is this and how much is with bluealsa. With a BT dongle I have no problems with bluealsa. I pair and connect and it does not seem to matter what phone I use. It seems to always connect and play. With the onboard modules, I get nothing but problems. The one I have had the most luck with is the B3+. It seems to play music with any phone I pair and seems to be robust. The B3 is a nightmare and the Zero I have had no luck getting any output at all recently (still working on figuring out why). On teh B3, I can pair and connect, eventually, and send audio, but it will disconnect and with certain devices (samsung Tab4), I get choppy audio. I get smooth audio with Moto Z2Play and HTC M9. On the B3+ all seem to work with smooth audio.

The B3+ works with ExecStart=/usr/bin/hciattach -n /dev/ttyAMA0 bcm43xx 3000000 flow -

The B3 I am using: ExecStart=/usr/bin/hciattach -n /dev/ttyAMA0 bcm43xx 921600 noflow -

The B3+ device is at hci1 (do not really know why) and the b3 device is hci0. On thh B3+, with the btattach command, I was able to blacklist a module and get the device to show up at hci0. That does not work with the hciattach command. I also tried the AUR alarm-bluetooth-raspberrypi and noted that the behavior on audio was identical to the btattach command (choppy audio with all paired devices), but the dmesg actually showed what was going on. With this command, the response is different in dmesg (no hci device is announced). On the B3+:

dmesg | grep hci

[ 4.298943] sdhci: Secure Digital Host Controller Interface driver [ 4.298945] sdhci: Copyright(c) Pierre Ossman [ 4.299395] sdhci-pltfm: SDHCI platform and OF driver helper

dmesg | grep Blue

[ 7.498883] Bluetooth: Core ver 2.22 [ 7.498933] Bluetooth: HCI device and connection manager initialized [ 7.498946] Bluetooth: HCI socket layer initialized [ 7.498952] Bluetooth: L2CAP socket layer initialized [ 7.498973] Bluetooth: SCO socket layer initialized [ 7.502178] Bluetooth: Generic Bluetooth SDIO driver ver 0.1 [ 8.814895] Bluetooth: HCI UART driver ver 2.3 [ 8.814916] Bluetooth: HCI UART protocol H4 registered [ 8.814924] Bluetooth: HCI UART protocol BCSP registered [ 8.814979] Bluetooth: HCI UART protocol LL registered [ 8.814982] Bluetooth: HCI UART protocol ATH3K registered [ 8.815007] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 8.815198] Bluetooth: HCI UART protocol Broadcom registered [ 9.012920] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 9.012928] Bluetooth: BNEP filters: protocol multicast [ 9.012944] Bluetooth: BNEP socket layer initialized

blm768 commented on 2019-04-24 03:12

I haven't done any testing on AArch64. However, based on the GitHub issue comments (, AArch64 support for some of the devices appears to be rather incomplete, and it looks like the Bluetooth controller may be one of those devices.

bipbip1981 commented on 2019-04-23 19:10

Hi, On my RPI3B with archlinux ARM AARCH64, i have two rfollowing results with dmesg and systemd

On my RPI3B with archlinux ARM armor, all it good

Bluetooth not work a this time with AARCH64? i do a mistake somewhere? i miss explain somewhere in documentation?

Thank a lot for helping

Sorry for my poor english

systemctl status brcm43438

  • brcm43438.service - Broadcom BCM43438 bluetooth HCI Loaded: loaded (/usr/lib/systemd/system/brcm43438.service; enabled; vendor preset: disabled) Active: inactive (dead) Condition: start condition failed at Tue 2019-04-23 21:00:23 CEST; 6s ago `- ConditionPathIsDirectory=/proc/device-tree/soc/gpio@7e200000/bt_pins was not met

Apr 23 20:53:41 raspberrypi systemd[1]: Condition check resulted in Broadcom BCM43438 bluetooth HCI being skipped.


[ 31.194545] Bluetooth: hci0: BCM: failed to write update baudrate (-110) [ 31.207605] Bluetooth: hci0: Failed to set baudrate [ 31.338676] Bluetooth: hci0: BCM: chip id 94 [ 31.351179] Bluetooth: hci0: BCM: features 0x2e [ 31.384607] Bluetooth: hci0: BCM43430A1 [ 31.394081] Bluetooth: hci0: BCM43430A1 (001.002.009) build 0000

blm768 commented on 2019-04-16 04:19

Based on my research, the 3B may require a different baud rate with control flow turned off. Does replacing the hciattach command with "/usr/bin/hciattach /dev/ttyAMA0 bcm43xx 921600 noflow -" work on your 3B?