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: 23
Popularity: 0.775142
First Submitted: 2016-03-19 20:54
Last Updated: 2019-04-12 03:51

Latest Comments

1 2 3 4 Next › Last »

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?


keithspg commented on 2019-04-15 02:23

Just tried this on a Pi3b+ and it works if I set the bluealsa device as hci1. The problem is that this is the default device and it shows up on hci1. How do I get the default device to be hci0.

From btmgmt, it shows this: [mgmt]# info Index list with 1 item hci1: Primary controller addr 43:45:C0:00:1F:AC version 8 manufacturer 15 class 0x040000 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr hs le advertising secure-conn debug-keys privacy static-addr current settings: powered connectable bondable ssp br/edr le secure-conn name gusrune short name

it does not list an hci0, but when it enumerates on the B3+, it shows up as hci1. All this on a PiB3+

On another pi, a regular B3 (not a plus) I have Bluealsa set up identically installed the same versions of pi-bluetooth, etc. WHen I run brcm43438, the device shows up as hci0

[mgmt]# info Index list with 1 item hci0: Primary controller addr B8:27:EB:D7:82:70 version 7 manufacturer 15 class 0x040000 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr hs le advertising secure-conn debug-keys privacy static-addr current settings: powered connectable discoverable bondable ssp br/edr le secure-conn name gretarune short name

after trying numerous times and finally getting it to pair and connect, when it plays, the timing is way off (fast) and it cuts in and out. This is only on the B3. B3+ is fine with playback. I have not yet tried on a Zero. Any ideas?

keithspg commented on 2019-04-14 19:26

I just tried this latest version. Uninstalled my hack and installed this one. Only had opportunity to try it on a Pi3 so far, but no joy. I can pair, but bluealsa cannot find the 'adapter'

bluealsa[2255]: /usr/bin/bluealsa: Adapter not available: /org/bluez/hci0/dev_BC_FF_EB_39_E0_5E

rebooted 2x. no help

blm768 commented on 2019-04-12 03:57

I've pushed a new version of the package that seems to work properly on my Pi; for whatever reason, the old hciattach utility seems to be more stable on this hardware. Using that, the updated *-sdio.txt files don't seem to be necessary, at least according to my tests. Thanks, @keithspg; your research was super useful.

keithspg commented on 2019-04-10 14:27

@blm768 Thanks for looking into this. I made a PKGBUILD and .install file for my use to get the files in the correct places. Apparently hciattach needs the HCD files in /etc/firmware for it to work. A link to my files is here: I have been working on getting this set up so my Pi is a BT enabled speaker (a2dp-sink) with bluez-alsa. I have success with a B3+ and a B3. It would also be helpful if we could understand why the a2db device will work only on hci1 on a B3+ and it shows up at hci0 (where I expect it) on a B3. I have not yet been able to get the Zero going yet.

blm768 commented on 2019-04-10 05:12

@keithspg Well, the utilities in bluez-utils-compat are considered deprecated, but if they work, they work. I'm able to reproduce the choppy audio issue on my own device. Seems like changing the btattach parameters to what should be equivalent to the old hciattach command (/usr/bin/btattach -B /dev/ttyAMA0 -P bcm -S 921600 -N) doesn't fix the issue, either. I might have to experiment with the compat package again.

keithspg commented on 2019-04-10 01:54

I finally got this working. I hope someone here can help tell me if I am doing it right. This list had all the 'choppy audio' comments in it. I was able to get this working using pieces of an older commit from this AUR. Plus I grabbed the edits to the txt files as well. The nvram txt files:

keithspg commented on 2019-04-09 17:05

In addition to the hcd files, the txt files have been modified. I manually edited mine and still cannot get a a2dp stream to play on either the Zero or B3. I continually get buffer under runs. With a btusb device it works correctly every time. Is the command in the .service file the most appropriate for streaming? All I get is choppy playback with onboard bt. Also with the B+, I needed to blacklist "btsdio" to get the BT device to be at hci0 which is quite helpful for pairing and such.

blm768 commented on 2019-02-13 05:56

@suthernfriend good catch. I totally spaced that last time.

suthernfriend commented on 2019-02-12 14:24

as @grimler noted. the hcd file checksums are out of date. in order to keep this from happening @blm768 should either

  • SKIP the checksum checks on the files downloaded from github or
  • specify the commit in the raw.githubuser[...].com url instead of the branch

while i'd prefer the second (otherwise the package should be named pi-bluetooth-git according to arch package guidelines)