rpi4 buster bluetooth and wlan conflict

akicker commented 4 years ago

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) !!! :+1: 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). :-1: 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 commented 4 years ago

Cypress have been notified.

akicker commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

@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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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

zorazor commented 4 years ago

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 commented 4 years ago

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

zorazor commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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

pelwell commented 4 years ago

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

macmpi commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

Thanks Phil, it should be live within an hour.

pelwell commented 4 years ago

Awesome.

pelwell commented 4 years ago

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

djibux commented 4 years ago

I can confirm it fixes the issue for me.

Thanks.

Le 17 avril 2020 18:23:18 GMT+02:00, Phil Elwell notifications@github.com 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: https://github.com/RPi-Distro/firmware-nonfree/issues/8#issuecomment-615339218

-- djib

rtheil commented 4 years ago

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

akicker commented 4 years ago

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

ghost commented 4 years ago

Hi, I'm sorry my bad English, me too can confirm that this issue is fixed after update to firmware-brcm80211 1:20190114-1+rpt6, thank you so much

pelwell commented 4 years ago

@akicker There is going to be some contention in the 2.4G band - there are limits to what you can achieve with a shared antenna. Use a 5G WLAN for best performance. The difference between the deb10u1 and deb10u1+rpt1 is the code that gives bluetooth priority when streaming audio. If you aren't streaming audio then it shouldn't make a difference.

akicker commented 4 years ago

@pelwell OK, thank you for this Info! I am using BT and 2.4G-Wlan (my router doesnt support 5G), knowing that BT uses the same frequency range. I dont use audio streaming, but my PI4 scans for BLE-devices, used as presence detection. So I will stick with my well working solution - hiding blue*-updates ;-) PS: my live system runs on pi3b+ stretch - never made such trobles ;-)

macmpi commented 4 years ago

@pelwell After careful comparison of new release with upstream NVRAM files (mostly an alphabetic reordering & different filenames), it turns-out that:

brcmfmac43455-sdio.txt has btc_mode=1 parameter twice (typo), and differs from upstream brcmfmac43455-sdio.raspberrypi,4-model-b.txt by newly introduced btc_params50=0x972c (and NVRAMRev number) (note: expectingly upstream brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt has same difference, plus boardflags3difference as actual boards are more instantiated upstream)
brcmfmac43430-sdio.txt is a copycat of upstream brcmfmac43430-sdio.raspberrypi,3-model-b.txt. (upstream is astonishingly missing brcmfmac43430-sdio.raspberrypi,model-zero-w.txt, which would need a symlink or copy of 3-model-b)

Except for this new Pi4/Pi3b+ btc_params50 (which I hope will show-up upstream soon?), I guess Pi Foundation prefers keeping by-feature ordering, rather than lining-up to upstream?

marquesn commented 4 years ago

Hello everyone, I've also been having issues with bluetooth connectivity dropping when WiFi is enabled. I have Raspbian 9 stretch with Bluez 5.50 and hardware BCM2835, revision a020d3.

As @pelwell mentioned, this update should do the trick, but how exactly do I perform the update? I've already tried it with "sudo apt update" and "sudo apt upgrade", but the issues persist. Do I have to upgrade the distro to Buster? Or is there another way to apply the update?

Thanks!

pelwell commented 4 years ago

What do the following two commands report?:

$ apt info firmware-brcm80211 | grep Version
$ strings /lib/firmware/brcm/brcmfmac43455-sdio.bin | grep Version

If you've already updated and upgraded and these aren't showing:

Version: 1:20190114-1+rpt6
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

then you'll have to either switch to Buster or (and this is much safer and easier) just overwrite the firmware directly:

$ wget https://github.com/RPi-Distro/firmware-nonfree/raw/master/brcm/brcmfmac43455-sdio.bin
$ wget https://github.com/RPi-Distro/firmware-nonfree/raw/master/brcm/brcmfmac43455-sdio.txt
$ wget https://github.com/RPi-Distro/firmware-nonfree/raw/master/brcm/brcmfmac43455-sdio.clm_blob
$ sudo cp brcmfmac43455-sdio.* /lib/firmware/brcm

marquesn commented 4 years ago

@pelwell

Many thanks for the prompt reply!

Running: apt info firmware-brcm80211 | grep Version results in the following: WARNING: apt does not have a stable CLI interface. Use with caution in scripts. E: Invalid operation info
Running: strings /lib/firmware/brcm/brcmfmac43455-sdio.bin | grep Version Results in: 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.154 (r684107 CY) CRC: b1f79383 Date: Tue 2018-02-27 03:18:17 PST Ucode Ver: 1043.2105 FWID 01-4fbe0b04

So based on these results, should I just overwrite the firmware directly with the links that you suggested?

Thanks again!

Edit: For the strings command, it seems I'm returned with a different version to the one posted above.

pelwell commented 4 years ago

should I just overwrite the firmware directly with the links that you suggested?

I think so - my "apt fu" in strong enough to do it any other way, and it should be a safe operation.

marquesn commented 4 years ago

@pelwell

I've downloaded the files and copied them over to the /lib/firmware/brcm path. I'll also add that I did not replace or delete any other files that were already in /lib/firmware/brcm.

I've also rebooted the RPi3 b+ but the issue still persists, with bluetooth connections being disrupted constantly if WiFi is turned on (they work with WiFi off).

I ran the strings command again, and this time it returned the same result as yours: 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

Although the apt info firmware-brcm80211 | grep Version still returns the same "invalid operation info" error.

Should I attempt the buster upgrade instead?

Thanks!

Edit: just noticed I didn't mention that this is ocurring on a RPi 3 b+ in my initial post. Not sure if this makes a difference with the procedure, but thought it might be useful to know anyways. My apologies.

pelwell commented 4 years ago

You can confirm the running version with:

$ dmesg | grep brcmfmac
[    3.922582] brcmfmac: F1 signature read @0x18000000=0x15264345
[    3.938684] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    3.939297] usbcore: registered new interface driver brcmfmac
[    4.259656] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    4.275308] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar  2 2020 23:30:41 version 7.45.202 (r724630 CY) FWID 01-72f6ece2
[    6.135038] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
$ tail -1 /lib/firmware/brcm/brcmfmac43455-sdio.txt
btc_params50=0x972c

If you see the right versions there and it hasn't improved matters then I don't think updating to Buster will make much of a difference, but if you have a spare SD card then you could try a clean install and upgrade (allow the wizard to do the update) of the latest Buster image and quickly try WiFi and Bluetooth.

just noticed I didn't mention that this is ocurring on a RPi 3 b+ in my initial post.

Yes you did - revision a020d3 ;-)

marquesn commented 4 years ago

@pelwell

Thanks! I've ran those commands and they return the exact same results from the dmesg command, as well as the tail.

I guess I'll try out your suggestion with the buster upgrade and will post the results on here when I do.

Thanks again!

marquesn commented 4 years ago

Hello @pelwell

I've done a fresh Buster install on the RPI 3 b+ and downloaded the new firmware files.

Bluetooth devices are still disconnecting when the WiFi is turned on. However this time the results of the dmesg grep command have detected some errors to do with scans? :

dmesg | grep brcmfmac
[    5.220747] brcmfmac: F1 signature read @0x18000000=0x15264345
[    5.234739] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    5.236739] usbcore: registered new interface driver brcmfmac
[    5.509316] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    5.544262] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar  2 2020 23:30:41 version 7.45.202 (r724630 CY) FWID 01-72f6ece2
[    8.120634] brcmfmac: power management disabled
[  315.591376] brcmfmac: brcmf_run_escan: error (-52)
[  315.591392] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
[  442.856107] brcmfmac: power management disabled

The tail command:

tail -1 /lib/firmware/brcm/brcmfmac43455-sdio.txt
btc_params50=0x972c

Not quite sure what else I could do for now, so I'll continue searching online. Please let me know if you think of something else, and I will post on here if I find a solution.

Many Thanks!

akicker commented 4 years ago

Hi, made some tests with my 3b+ Here the working configs:

RPI	OS	kernel	blue*	firmware-brcm80211
3Bplus	stretch	4.19.66	5.43-2+rpt2+deb9u2	+rpt4
3Bplus	buster	4.19.97	5.50-1.2~deb10u1	+rpt6

marquesn commented 4 years ago

Hello @akicker

My Bluez version is 5.50-1.2~deb10u1, but the firmware version is reported to be +rpt1. How do I go about upgrading it to rpt6?

Thanks!

akicker commented 4 years ago

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 commented 4 years ago

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 <team+pkg-bluetooth@tracker.debian.org>
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 commented 4 years ago

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

Swap-File commented 4 years ago

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 commented 4 years ago

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 :-1: My solution: sudo apt-mark hold bluez - update all others using bluez 5.50-1.2\~deb10u1 works fine :+1:

DenisBY commented 4 years ago

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 commented 4 years ago

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

rob-meiner commented 4 years ago

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 commented 4 years ago

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: https://github.com/raspberrypi/firmware/issues/1403#issuecomment-638701200

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

RPi-Distro / firmware-nonfree

rpi4 buster bluetooth and wlan conflict #8