rpi4 buster bluetooth and wlan conflict

[akicker]

With the update from 27.3. (updating bluetooth, ... to bluetooth (5.50-1.2~deb10u1)) raspbian buster on rpi4 bluetooth and wlan did work well (the first time on my rpi4) !!! 👍
Unfortunately updates from 30.3. to bluetooth (5.50-1.2~deb10u1+rpt1) and 11 other updates bluetooth and wlan conflicts again (BT off --> wlan ok, BT on --> very low wlan rx-rate). 👎
current using buster kernel 4.19.97 - Some more info see image below, wlan and BT improoved when (5.50-1.2~deb10u1) is in use !!!

[pelwell]

Cypress have been notified.

[akicker]

Meanwhile i decided to use a workaround to hold blue* at 5.50-1.2~deb10u1 and run all other updates --> wlan is still working excellent 👍

• sudo apt update -y
• sudo apt-mark hold bluez
• sudo apt-mark hold bluetooth
• sudo apt-mark hold bluez-obexd
• sudo apt-mark hold libbluetooth-dev
• sudo apt-mark hold libbluetooth3
• sudo apt full-upgrade

[JsBergbau]

Just a warning for all that want to hold " 5.50-1.2~deb10u1"
On Pi Zero W it reduces the bluetooth range dramatically. Any findings about that on PI4?

[akicker]

My personal experience (hold only on rpi4 !!!):

RPI	Model	Rev	OS	kernel	BCM	blue*	Wlan+BT
3	B	1.2	buster	4.19.97	43430/1	5.50-1.2~deb10u1+rpt1	OK
3	B Plus	1.3	stretch	4.19.66	4345/6	5.43-2+rpt2+deb9u2	OK
4	B	1.1	buster	4.19.97	4345/6	5.43-...	NOT OK
4	B	1.1	buster	4.19.97	4345/6	5.50-1.2~deb10u1	OK
4	B	1.1	buster	4.19.97	4345/6	5.50-1.2~deb10u1+rpt1	NOT OK

[pelwell]

I think there's an element of randomness in these results. I'm reasonably convinced that the most recent version of the 43455 firmware doesn't always play nicely with Bluetooth, but the results aren't consistent - I get laggy response from a BT keyboard with occasional connection loss on one boot, and great performance while streaming video over WiFi on the next.
N.B. The WiFi firmware is part of the firmware-80211 package. You can downgrade it with:

$ wget http://archive.raspberrypi.org/debian/pool/main/f/firmware-nonfree/firmware-brcm80211_20190114-1+rpt3_all.deb
$ sudo dpkg -i ./firmware-brcm80211_20190114-1+rpt3_all.deb

(The ./ is necessary) Yes - rpt3 misses out rpt4, but that was later reverted.

Returning to the latest version is just sudo apt install firmware-brcm80211.

[XECDesign]

@pelwell It looks like there are reports of the bluez package being a factor, not just the firmware.

The changes we make are the 'Add avdtp_set_priority' and hciattach patches. Any chance they could be related?

[pelwell]

hciattach either downloads the firmware patch or it doesn't - it doesn't make any changes to it, so I don't believe it could be making a difference during normal use of Bluetooth. If the pure upstream version works as well then we could switch to using that.

The priority setting code is possibly a factor, since it alters the scheduling between the BT and WiFi, designed to give preference to Bluetooth audio streaming.

[pelwell]

To diagnose the issue I've been rebuilding BlueZ 5.50 with and without the downstream patches, but it's been behaving itself - so I started again.

A clean installation of the latest Buster image, fully upgraded, is streaming HD video while sending audio to a headset, while two keyboards are connected. So far there have been no hiccups.

Hmmm...

[akicker]

My experience downgrading the firmware to rpt3: Pi3-improoved Pi4-worsened:

RPI	Rev	OS	kernel	BCM	blue*	brcm…	Status
3B	1.2	buster	4.19.97	43430/1	5.50-1.2~deb10u1+rpt1	+rpt5	OK
3B	1.2	buster	4.19.97	43430/1	5.50-1.2~deb10u1+rpt1	+rpt3	Improved
3Bplus	1.3	stretch	4.19.66	4345/6	5.43-2+rpt2+deb9u2	+rpt4	OK
4B	1.1	buster	4.19.97	4345/6	5-43-...	+rpt5	NOT OK
4B	1.1	buster	4.19.97	4345/6	5.50-1.2~deb10u1	+rpt5	OK
4B	1.1	buster	4.19.97	4345/6	5.50-1.2~deb10u1	+rpt3	Worsened
4B	1.1	buster	4.19.97	4345/6	5.50-1.2~deb10u1+rpt1	+rpt5	NOT OK
4B	1.1	buster	4.19.97	4345/6	5.50-1.2~deb10u1+rpt1	+rpt3	Worsened

[djibux]

It seems I have the issue on a 3b+ with a fresh Raspbian install. I have a bluetooth keyboard (Logitech K480) that I can pair properly, but it's unusable when the WiFi is active. I tried downgrading packages to 5.43-2+rpt2+deb9u2 but the issue remains.

[akicker]

If your OS is buster try 5.50-1.2~deb10u1 (3B+ and 4 use the same WL/BT-chip)

[zorazor]

With a downgrade to "5.50-1.2~deb10u1" my RPI4 can't connect to keyboard/mouse.

Edit:
I upgraded to "5.50-1.2~deb10u1+rpt1" again and disabled WIFI. At least for now I can use my BT mouse/keyboard but without WIFI.

Crossing my fingers for an update. Thank you.

[pelwell]

Connecting to a 2.4G AP I see the problem more reliably now. Cypress have also been able to reproduce the issue.

[zorazor]

Thank you for the workaround hint.
I disabled 2.4Ghz WIFI on my AP and enabled 5Ghz.
The Pi4 with bluetooth devices, bluez 5.50-1.2~deb10u1+rpt1 and brcm80211 rpt5 is working now.

But I noticed that the Pi4 has a limited ability to connect.
On a 5Ghz ac WIFI it connects only with:
"n/ 40 MHz, WPA2, 1 x 1, 11k, 11v"

[ghost]

Hi,

I am sorry my bad English, I have a pi 4, I am having an issue, I have a speaker jbl go, jbl charge 3 and handsfree Huawei Am61, My devices work when I power off Wifi on the pi 4, but I power on wifi my devices star connect and desconnect by ifselt that happens when I am not listening to music, My pi 4 is full upgrade, can you help me with a solution for this problem.

Regards,

John

[rtheil]

I'm having this same issue with a cheap bluetooth keyboard (https://www.amazon.com/gp/product/B00X5P8BJO) and with Apple bluetooth keyboard. Fresh install of Raspbian buster image on rpi4 (dated 2/13/20). Keyboard works perfectly. Updates are run and keyboard stops working. Connectivity is perfect. Keyboard always connects to Pi and shows as connected.

I do not have ability to switch between 2.4GHz and 5GHz on wifi as they are configured together on same SSID and many devices in the house still require 2.4GHz. However, I did disable wifi and the keyboards work perfectly. Problem is, next to my SSID it shows "5G" while connected.

[pelwell]

Cypress have responded with an easy patch to the "NVRAM" configuration file. I've pushed the updated file to this repo and we'll get a Raspbian package out as soon as possible, but the easiest way to fix it for yourself in the meantime is to run this command:

$ echo btc_params50=0x972c | sudo tee -a /lib/firmware/brcm/brcmfmac43455-sdio.txt

You can confirm that the patch has been applied successfully with:

pi@raspberrypi:~$ md5sum /lib/firmware/brcm/brcmfmac43455-sdio.txt
0ed2738fb42c392c60e34dedb74d0510  /lib/firmware/brcm/brcmfmac43455-sdio.txt

Now reboot, and you should find it all works much better.

[XECDesign]

Should I push out a new package with that one line added, or is there more to it than that?

[pelwell]

Yes please, there is nothing more to it than that.

[macmpi]

I see current RPi-Distro firmware file is at 7.45.202 rather than latest 7.45.206

Is that supposed to work with latest firmware files from Cypress:
File: firmware/brcmfmac43455-sdio.bin
Version: 7.45.206

[pelwell]

As I mentioned in the message associated with the commit, Cypress say this extra parameter is required for firmwares starting with 7.45.177. By using a default Cypress build you are missing out on some Pi-specific settings (and support from us), but adding this parameter might make a difference.

[XECDesign]

Thanks Phil, it should be live within an hour.

[pelwell]

Awesome.

[pelwell]

firmware-brcm80211 1:20190114-1+rpt6 is now live. Thanks, @XECDesign.

[djibux]

I can confirm it fixes the issue for me. Thanks. Le 17 avril 2020 18:23:18 GMT+02:00, Phil Elwell <[email protected]> a écrit :

…

firmware-brcm80211 1:20190114-1+rpt6 is now live. Thanks, @XECDesign. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #8 (comment)

-- djib

[rtheil]

I can also confirm that this issue is fixed after running updates. Thank you!

[akicker]

With the brcm80211 fw-update to +rpt6:
pi3 buster, latest blue* (+rpt1) --> OK 👍
pi4 buster, old blue* (5.50-1.2~deb10u1) --> OK 👍
*pi4 buster, after unholding and updating blue (5.50-1.2~deb10u1+rpt1) --> Wlan again slowing down dramatically when BT is on 👎 **
same problem on pi3plus buster - latest stable updates

[akicker]

First of all hold upgrading bluetooth - see my second post from Mar 31.
and full-upgrade should do the rest (upgrade it to rpt6) :-)

[marquesn]

Hello @akicker

I've placed the packages on hold as per your post on 31st March.

I followed this with a full upgrade. However, the command apt show bluez-obexd still shows that I'm still using rpt1:

apt show bluez-obexd
Package: bluez-obexd
Version: 5.50-1.2~deb10u1+rpt1
Priority: optional
Section: admin
Source: bluez
Maintainer: Debian Bluetooth Maintainers <[email protected]>
Installed-Size: 473 kB
Depends: libc6 (>= 2.28), libdbus-1-3 (>= 1.9.14), libglib2.0-0 (>= 2.35.9), libical3 (>= 3.0.0)
Conflicts: obexd-client, obexd-server
Replaces: obexd-client, obexd-server
Homepage: http://www.bluez.org
Download-Size: 180 kB
APT-Sources: http://archive.raspberrypi.org/debian buster/main armhf Packages

[akicker]

@marquesn dont worry
try to show the installed version
dpkg --status bluez-obexd | grep '^Version:'
--> Version: 5.50-1.2~deb10u1

[Swap-File]

I have a pair of Pi4s talking to each other via 5ghz wifi, one is running hostAPD. I also have bluetooth traffic (tethering to share internet, not music or a keyboard) on the Pi running hostAPD.

Previously, I was running firmware-brcm80211 20190114-1+rpt4 and bluez 5.50-1+rpt1 and it worked well.

I recently ran apt update & upgrade and noticed my wifi performance became very inconsistent. My synced rate would go up and down wildly, and my connection would often drop entirely.

I tried rebuilding my cards from scratch with the new Raspberry Pi OS (32-bit) Lite image, and had the same problem.

I went back to my old image, and eventually found if I held back bluez, everything would keep working OK. Around that time I found this git issue.

bluez 5.50-1+rpt1 with firmware-brcm80211 20190114-1+rpt6 is working well for me.

bluez 5.50-1.2~deb10u1 with firmware-brcm80211 20190114-1+rpt6 also seems OK.

bluez 5.50-1.2~deb10u1+rpt1 with firmware-brcm80211 20190114-1+rpt6 (what you get if you run an apt update & upgrade) does not work.

Note: I did not heavily test bluetooth range, other than making sure I could connect and it was usable for tethering.

[akicker]

After some tests on my pi4 kernel 4.19.118 using firmware-brcm80211 20190114-1+rpt7
bluez 5.50-1.2~deb10u1+rpt1 still does not work 👎
My solution: sudo apt-mark hold bluez - update all others
using bluez 5.50-1.2~deb10u1 works fine 👍

[DenisBY]

Just a side note. If I boot into Ubuntu 20.20 bluetooth works just fine. During scan I see all my devices and even devices of my neighbors. If I boot into 'buster' I can see only my MI Band 4 when I'm sitting close to Raspberry.

In buster I have:

# strings /lib/firmware/brcm/brcmfmac43455-sdio.bin | grep Version
43455c0-roml/43455_sdio-pno-aoe-pktfilter-pktctx-lpc-pwropt-43455_ftrs-wfds-mfp-dfsradar-wowlpf-idsup-idauth-noclminc-clm_min-obss-obssdump-swdiv Version: 7.45.202 (r724630 CY) CRC: 4b9a9ceb Date: Mon 2020-03-02 23:32:43 PST Ucode Ver: 1043.2139 FWID 01-72f6ece2
...
Unpacking firmware-brcm80211 (1:20190114-1+rpt5) over (1:20190114-1+rpt5)
...

[akicker]

The latest bluez update rpt2 is better than rpt1 BUT
bluez 5.50-1.2~deb10u1+rpt2 still slows down wlan 👎
using bluez 5.50-1.2~deb10u1 still works fine 👍

[rob-meiner]

Dear colleagues,

Is there a definitive fix to the bluetooth disconnect problem? I've read through all the forum entries I can find now and tried a lot of the suggestions with no success. It seems like different things sort-of work for different people. I have a raspberry pi 4b with 4G RAM, running Buster, headless. I'm using a 2.4 Ghz WLAN.

Here's a link to the description of the problem I posted on the raspberrypi/firmware page

pi@antonio:~ $ dpkg --status bluez-obexd | grep '^Version:'
Version: 5.50-1.2~deb10u1+rpt2

I would really appreciate some insights into this issue. After reading through a large number of posts on a variety of fora, without finding a solution, I' starting to think this is a hardware design issue. This seems like a big deal, since headless users can't really get the value of the bt radio.

Is the fastest way to get this to work to just buy a 5Ghz modem?

-Mark

[rob-meiner]

Just to add a bit more information to this. It appears that I am getting a firmware loading error.

pi@antonio:~ $ dmesg | grep brcmfmac
[    4.785330] brcmfmac: F1 signature read @0x18000000=0x15264345
[    4.796418] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    4.796839] usbcore: registered new interface driver brcmfmac
[    4.818617] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt failed with error -2
[    5.046562] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    5.067193] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: May 20 2020 00:36:51 version manifest (de496ab CY) FWID 01-12aa6092
[    7.204682] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[    8.355542] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
pi@antonio:~ $ md5sum /lib/firmware/brcm/brcmfmac43455-sdio.bin
0a45a7a828e49e20fee2fe0438149523  /lib/firmware/brcm/brcmfmac43455-sdio.bin

I have tried updating the firmware per @pelwell in this post: raspberrypi/firmware#1403 (comment)

After making this firmware change, I can pair with BT devices and trust them, but I cannot connect to them. When I first pair with some devices, they connect for about a second, then disconnect. When I try to reconnect to them, it always looks like this. The devices work fine connecting to one another. It's unsurprising that this doesn't work, since there is obviously a firmware loading problem, but I'm surprised that it works this far... (I addedd all the x's to the MAC addresses)

pi@antonio:~ $ sudo bluetoothctl
Agent registered
[bluetooth]# pairable on
Changing pairable on succeeded
[bluetooth]# discoverable on
Changing discoverable on succeeded
[bluetooth]# devices
Device 00:0C:XX:XX:XX:XX Bose Mini SoundLink
Device 2C:41:XX:XX:XX:XX LE-Bose SoundWear
[NEW] Device DC:66:XX:XX:XX:XX Galaxy A3 (2016)
[CHG] Device DC:66:XX:XX:XX:XX Modalias: bluetooth:v0075p0100d0200
[CHG] Device DC:66:XX:XX:XX:XX UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Device DC:66:XX:XX:XX:XX UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Device DC:66:XX:XX:XX:XX UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device DC:66:XX:XX:XX:XX UUIDs: 00001112-0000-1000-8000-00805f9b34fb
[CHG] Device DC:66:XX:XX:XX:XX UUIDs: 00001115-0000-1000-8000-00805f9b34fb
[CHG] Device DC:66:XX:XX:XX:XX UUIDs: 00001116-0000-1000-8000-00805f9b34fb
[CHG] Device DC:66:XX:XX:XX:XX UUIDs: 0000111f-0000-1000-8000-00805f9b34fb
[CHG] Device DC:66:XX:XX:XX:XX UUIDs: 0000112d-0000-1000-8000-00805f9b34fb
[CHG] Device DC:66:XX:XX:XX:XX UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Device DC:66:XX:XX:XX:XX UUIDs: 00001132-0000-1000-8000-00805f9b34fb
[CHG] Device DC:66:XX:XX:XX:XX UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device DC:66:XX:XX:XX:XX UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device DC:66:XX:XX:XX:XX UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device DC:66:XX:XX:XX:XX ServicesResolved: yes
[CHG] Device DC:66:XX:XX:XX:XX Paired: yes
[CHG] Device DC:66:XX:XX:XX:XX ServicesResolved: no
[CHG] Device DC:66:XX:XX:XX:XX Connected: no
[bluetooth]# devices
Device 00:0C:XX:XX:XX:XX Bose Mini SoundLink
Device 2C:41:XX:XX:XX:XX LE-Bose SoundWear
Device DC:66:XX:XX:XX:XX Galaxy A3 (2016)
[bluetooth]# trust DC:66:XX:XX:XX:XX
[CHG] Device DC:66:XX:XX:XX:XX Trusted: yes
Changing DC:66:XX:XX:XX:XX trust succeeded
[bluetooth]# connect DC:66:XX:XX:XX:XX
Attempting to connect to DC:66:XX:XX:XX:XX
Failed to connect: org.bluez.Error.Failed

Please let me know if you have any ideas how to resolve this.
Thanks, Mark

[thamht4190]

For one who don't want to read all comments:
I got this problem on my Pi4B. I got the firmware +rpt7, so I suppose the fix (on +rpt6) is already there. If your firmware version is less than +rpt6, you should update it.

pi@raspberrypi:~ $ apt info firmware-brcm80211 | grep Version
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Version: 1:20190114-1+rpt7

I checked bluez version:

pi@raspberrypi:~ $ dpkg --status bluez \| grep '^Version:'
Version: 5.50-1.2~deb10u1+rpt1

From the comment on this ticket, I understand that bluez version 5.50-1.2~deb10u1 can work, so I download it from here, then install it (bluez will be downgraded automatically):

pi@raspberrypi:~ $ wget http://ftp.hk.debian.org/debian/pool/main/b/bluez/bluez_5.50-1.2~deb10u1_armhf.deb
pi@raspberrypi:~ $ sudo apt install ./bluez_5.50-1.2~deb10u1_armhf.deb

And now, bluetooth and wifi can work together on my Pi.

[stuckinger]

Thanks for this post! It kind of helped me, but only partly.
I want to share my experience because I got an improvement, someone else might be interested in.
Even though I end up using an extra usb wifi - read below why...

The Hardware:

model name      : ARMv7 Processor rev 4 (v7l)
BogoMIPS        : 51.20
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xd03
CPU revision    : 4`

Hardware        : BCM2835
Revision        : a02082
Model           : Raspberry Pi 3 Model B Rev 1.2

I do not have an exact setup from before when it was not working, but I was on stretch and on blue*-version 5.50 something I guess and kernel 4.19 something.
I had scratches in my audio in general, not only bluetooth.
Network via WIFI onboard and Bluetooth via onboard.
The main problem was, when trying to read/write Bluetooth LE Devices it mostly did not work:

Error: connect error: Function not implemented (38)
[E0:E5:CF:D6:AF:49][LE]> Bluetooth connection timed out

After reading this thread I updated to buster, so now my versions are:

~# uname -a
Linux  5.4.51-v7+ #1333 SMP Mon Aug 10 16:45:19 BST 2020 armv7l GNU/Linux

~# dpkg -l |grep -i blue
ii  bluej                                 4.2.1                                     all          A simple but powerful Java IDE.
ii  blueman                               2.0.8-1+b2                                armhf        Graphical bluetooth manager
ii  bluetooth                             5.50-1.2~deb10u1+rpt2                     all          Bluetooth support (metapackage)
ii  bluez                                 5.50-1.2~deb10u1+rpt2                     armhf        Bluetooth tools and daemons
ii  bluez-alsa:armhf                      4.99-2+deb7u1                             armhf        Bluetooth ALSA support
ii  bluez-audio                           4.99-2+deb7u1                             all          Transitional package
ii  bluez-firmware                        1.2-4+rpt5                                all          Firmware for Bluetooth devices
ii  bluez-gstreamer                       4.99-2+deb7u1                             armhf        Bluetooth GStreamer support
ii  bluez-hcidump                         5.50-1.2~deb10u1+rpt2                     armhf        Analyses Bluetooth HCI packets
ii  bluez-obexd                           5.50-1.2~deb10u1+rpt2                     armhf        bluez obex daemon
ii  bluez-tools                           2.0~20170911.0.7cb788c-2                  armhf        Set of tools to manage Bluetooth devices for linux
ii  bluez-utils                           4.99-2+deb7u1                             all          Transitional package
ii  libbluetooth3:armhf                   5.50-1.2~deb10u1+rpt2                     armhf        Library to use the BlueZ Linux Bluetooth stack
ii  pi-bluetooth                          0.1.15                                    all          Raspberry Pi 3 bluetooth
ii  pulseaudio-module-bluetooth           12.2-4+deb10u1                            armhf        Bluetooth module for PulseAudio sound server

~# dpkg -l |grep -i firmware
ii  bluez-firmware                        1.2-4+rpt5                                all          Firmware for Bluetooth devices
ii  firmware-atheros                      1:20190114-1+rpt8                         all          Binary firmware for Atheros wireless cards
ii  firmware-brcm80211                    1:20190114-1+rpt8                         all          Binary firmware for Broadcom/Cypress 802.11 wireless cards
ii  firmware-libertas                     1:20190114-1+rpt8                         all          Binary firmware for Marvell wireless cards
ii  firmware-misc-nonfree                 1:20190114-1+rpt8                         all          Binary firmware for various drivers in the Linux kernel
ii  firmware-ralink                       1:20190114-1+rpt8                         all          Binary firmware for Ralink wireless cards (dummmy package)
ii  firmware-realtek                      1:20190114-1+rpt8                         all          Binary firmware for Realtek wired/wifi/BT adapters
ii  rpi-update                            20200409                                  all          Raspberry Pi firmware updating tool

In first place I was really happy because even though my pi was still connected via internal WIFI I could control my bluetooth devices!
I even found out that the sound was way better than before - I haven't tested bluetooth yet, only audio plug.
But then I realized that there are still some conflicts because while streaming audio - I have an mpd running that is streaming from network - every time I connect to a bluetooth-device the music stopped. I guess it comes from buffer underrun, maybe the wifi connection drops for some seconds. Something I did not realize while being on ssh.

So while not using it as a radio station I guess this setup would work fine, but constant WIFI network AND Bluetooth still conflicts.

My workaround: Using USB WIFI.
Sound = OK
Bluetooth = OK
WIFI = OK

Still sad since the hardware is already onboard and should be working...

[sebastianeferrer]

Hi everyone! great news! we finally have an official bugfix for CYW43455.

$ apt changelog bluez-firmware | head

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Get:1 store: bluez-firmware 1.2-4+rpt8 Changelog
bluez-firmware (1.2-4+rpt8) buster; urgency=medium

  [ Phil Elwell ]
  * Second Spectra fix for CYW43455 (CVE-2020-10370)
    - Original firmware name: BCM4345C0_003.001.025.0174.0342.hcd

 -- Serge Schneider <[email protected]>  Thu, 28 Jan 2021 14:57:44 +0000

Just run:

$ sudo apt update && sudo apt upgrade bluez-firmware

then it should work again.

May be a deeper review on different implementations should be done, but first signs from me are good. My problem of interference between bt and wifi working on 2.4GHz was fixed

[akicker]

Great, that's working, did remove my hold on bluez (sudo apt-mark unhold bluez) updated all and everything is OK again :-)

[pelwell]

I'm going to close this issue then.

[rabe-]

I'm still having that problem on my Pi4 with the K380
It works fine on my Pi3 with the same SD card.

I did try a fresh pairing of course. Many times over.

[pelwell]

That's strange - I'm using one now and it works fine. Which distribution are you using?

[lesinigo]

I'm having the same problem:

• Raspberry Pi Zero W rev1.1
• fresh Raspbian buster + apt-get update; apt-get dist-upgrade
• kernel 5.10.17+ #1403, bluez 5.50-1.2~deb10u1+rpt2, bluez-firmware 1.2-4+rpt8

After weeks without any problem using wifi only, I turned on bluetooth, paired a BT GPS and suddenly got connectivity issues over WiFi (2.4GHz). Disabling bluetooth gave me a perfectly working wifi again.

These are from my dmesg:

[   17.552652] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   17.941396] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   18.363915] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[   18.376905] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[   18.377393] usbcore: registered new interface driver brcmfmac
[   18.412091] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.raspberrypi,model-zero-w.txt failed with error -2
[   18.652728] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[   18.652945] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[   18.654148] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 22 2019 01:59:28 version 7.45.98.94 (r723000 CY) FWID 01-3b33decd
[   27.978848] uart-pl011 20201000.serial: no DMA platform data
[   29.175921] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[   31.900322] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   32.531216] Bluetooth: Core ver 2.22
[   32.531389] NET: Registered protocol family 31
[   32.531405] Bluetooth: HCI device and connection manager initialized
[   32.531440] Bluetooth: HCI socket layer initialized
[   32.531462] Bluetooth: L2CAP socket layer initialized
[   32.531510] Bluetooth: SCO socket layer initialized
[   32.554015] Bluetooth: HCI UART driver ver 2.3
[   32.554045] Bluetooth: HCI UART protocol H4 registered
[   32.554212] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   32.554500] Bluetooth: HCI UART protocol Broadcom registered
[   33.914212] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   33.914238] Bluetooth: BNEP filters: protocol multicast
[   33.914272] Bluetooth: BNEP socket layer initialized