-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should bluez rpi version be a dependecy anymore? #15
Comments
It could probably be downgraded to the +rpt1 version, but there are other changes not in the Debian package. |
I've tested the latest versions of the bt support scripts with bluez from vanilla debian @XECDesign , the bluetooth is working fine. What is in bluez modded version to still be a dependency? (I could just to a diff between the two packages) |
@XECDesign RPi-Distro/firmware-nonfree#8 (comment) this comment, the user used bluez_5.50-1.2~deb10u1_armhf.deb from debian. When building the rpi image, having simply bluez-rpi in the packages list, will install it instead of bluez. Example usage: other distros are not rpios, can import them directly of using rpios repos, to use them, without having package conflicts. Maybe that isn't the usual case, but it can be useful too. |
I have never had any luck getting BT on RPi3B+ to do anything useful. I gave up trying abt 2 years ago, after applying numerous "snake-oil" fixes. I've just seen a post on RPi SE wherein the OP implied he fixed his issues by applying this recipe. It is a mystery to me how the OP "fixed" his problem (also with a RPi3B+) with this recipe, but since nothing else has worked, I tried it also :P Here's a synopsis: pi@raspberrypi3b:~ $ apt info firmware-brcm80211 | grep Version
Version: 1:20190114-1+rpt7
pi@raspberrypi3b:~ $ dpkg --status bluez | grep '^Version:'
Version: 5.50-1.2~deb10u1+rpt2
pi@raspberrypi3b:~ $ wget http://ftp.hk.debian.org/debian/pool/main/b/bluez/bluez_5.50-1.2~deb10u1_armhf.deb
...
Saving to: ‘bluez_5.50-1.2~deb10u1_armhf.deb’
pi@raspberrypi3b:~ $ sudo apt install ./bluez_5.50-1.2~deb10u1_armhf.deb
...
Note, selecting 'bluez' instead of './bluez_5.50-1.2~deb10u1_armhf.deb'
...
The following packages will be REMOVED:
pi-bluetooth
The following packages will be DOWNGRADED:
bluez
...
Do you want to continue? [Y/n] Y
...
Removing pi-bluetooth (0.1.14) ...
dpkg: warning: downgrading bluez from 5.50-1.2~deb10u1+rpt2 to 5.50-1.2~deb10u1
...
pi@raspberrypi3b:~ $ dpkg --status bluez | grep '^Version:'
Version: 5.50-1.2~deb10u1 In summary, it seems I've downgraded **FROM: ** Since making these changes, I've not tried to make any BT connections - my confidence is low that this will improve things. Can anyone offer any enlightenment, or is BT on Pi3B+ simply a hopeless cause? |
Dear @seamusdemora be happy now! This bugfix will through light to you solving the conflicts between wifi and bt on any Rpi model using CYW43455. Check it out here -> RPi-Distro/firmware-nonfree#8 |
@sebastianeferrer 👍 Thank you for the update - I've added a comment to the referenced RPi SE Q&A. I will take your advice and "be happy now" :) However... issues with Bluetooth on RPi go well beyond the WiFi-BT interference issue. To blether just a wee bit:
|
As learnt from here: #14 , bdaddr is in bluez rpi version of the package.
But with the new master commit not using it anymore, should the rpi version of bluez be maintained as a dependecy in the debian package, or bluez rpi version provides something more?
The text was updated successfully, but these errors were encountered: