You are not logged in.

#51 2021-03-22 21:20:01

ArthurBorsboom
Member
Registered: 2014-05-20
Posts: 51

Re: Random bluetooth speaker disconnects

I am experiencing the same disconnects, which was not the case before.

- Intel AX200 160MHz, REV=0x340
- Kernel: 5.11.8
- Firmware: 20210315.3568f96-1

Is anybody aware of a bug report upstream?

Offline

#52 2021-03-24 11:53:28

alxndr13
Member
Registered: 2016-09-22
Posts: 9

Re: Random bluetooth speaker disconnects

ArthurBorsboom wrote:

I am experiencing the same disconnects, which was not the case before.

- Intel AX200 160MHz, REV=0x340
- Kernel: 5.11.8
- Firmware: 20210315.3568f96-1

Is anybody aware of a bug report upstream?

Maybe 4johnny is, otherwise no. I just gave up and purchased a simple bt usb dongle until this issue is fixed. I need a reliable connection for work and i cannot afford to have random disconnect during the workday. If there's anything i can provide though, let me know.

Offline

#53 2021-03-25 13:01:21

adrin
Member
Registered: 2017-08-05
Posts: 11

Re: Random bluetooth speaker disconnects

- AX200
- WH-1000XM3
- 20210315.3568f96-1 firmware
- bluez 5.56-2
- kernel: Linux 5.11.8-arch1-1 #1 SMP PREEMPT

and got a disconnect in less than half an hour.

Edit1: I downgraded the firmware, but not the kernel, and still got a disconnect, here's the log: https://pastebin.com/ZH9YU5Ev

Edit2: I downgraded the kernel as well, but still got a disconnect
kernel: Linux 5.9.14-arch1-1 #1 SMP PREEMPT
bluez 5.56-2
linux-firmware: 20201120.bc9cd0b-1

here's the log: https://pastebin.com/qTGpb9B9

Edit3: also downgraded bluez, still got a disconnect:
kernel: Linux 5.9.14-arch1-1 #1 SMP PREEMPT
bluez, bluez-libs: 5.55-3
linux-firmware: 20201120.bc9cd0b-1

and here's the log: https://pastebin.com/izWC2p4A

Last edited by adrin (2021-03-29 09:22:49)

Offline

#54 2021-03-25 13:42:44

speedyx
Member
From: Italy
Registered: 2008-09-05
Posts: 85

Re: Random bluetooth speaker disconnects

The same here:
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: 2000
  bus-ID: 52:00.0 chip-ID: 8086:2723 class-ID: 0280

Kernel 5.11.8
core/linux-firmware 20210315.3568f96-1
extra/bluez 5.56-2
extra/pipewire 1:0.3.24-1


Twitter: @speedytux The Freedom Technologies Are Available... And Work!
I love archlinux: the last STABLE kernel release + the last STABLE gnome release + the last STABLE apps releases. The upstream developers decide what is STABLE.
Philipe Müller, Manjaro: "Always remember how you started with Linux and what your beginner questions were!"

Offline

#55 2021-03-25 16:20:53

Fireminster
Member
Registered: 2020-07-12
Posts: 13

Re: Random bluetooth speaker disconnects

I suffer the same problem but cannot contribute because I am not on Arch anymore but I just want to say thank you to @4johnny!! The whole internet is cheering your efforts to get this sorted out. I know a lot of people on other distros who are having these same problems and do not know where or how to address it.

Offline

#56 2021-03-26 05:46:02

djorr5
Member
Registered: 2021-03-26
Posts: 2

Re: Random bluetooth speaker disconnects

Not sure if it has been mentioned before but I have this issue but only when I use A2DP profile. If I use HSP/HFP I don't get the intermittent disconnects.

Offline

#57 2021-03-26 13:04:18

davidbepo
Member
Registered: 2021-03-22
Posts: 8

Re: Random bluetooth speaker disconnects

disconnect also happens on prev firmware: linux-firmware-20200817.7a30af1-1
going to test linux-firmware-20200519.8ba6fa6-1 now and will report back

Offline

#58 2021-03-26 13:31:51

davidbepo
Member
Registered: 2021-03-22
Posts: 8

Re: Random bluetooth speaker disconnects

linux-firmware-20200519.8ba6fa6-1 still shows the same issue, im starting to think this isnt a firmware issue...

Offline

#59 2021-03-29 09:32:42

adrin
Member
Registered: 2017-08-05
Posts: 11

Re: Random bluetooth speaker disconnects

@4johnny, has there been an update? I've uploaded 3 different log files here (https://bbs.archlinux.org/viewtopic.php … 3#p1964083) not sure if they're helpful.

Offline

#60 2021-03-31 08:41:52

djorr5
Member
Registered: 2021-03-26
Posts: 2

Re: Random bluetooth speaker disconnects

I get the feeling that this is falling by the wayside?

Offline

#61 2021-03-31 11:47:41

flortsch
Member
From: Linz, Austria
Registered: 2015-07-21
Posts: 38
Website

Re: Random bluetooth speaker disconnects

Downgrade to linux-firmware 20201120.bc9cd0b-1 solved the problem for my environment.

- Lenovo Thinkpad T14s with Intel Corporation Wi-Fi 6 AX200 (rev 1a) AX200
- Bose QC35 ii 4.8.1
- bluez 5.56-2
- linux 5.11.11.arch1-1

Offline

#62 2021-04-02 17:21:29

4johnny
Member
Registered: 2021-03-05
Posts: 12

Re: Random bluetooth speaker disconnects

Sorry that I haven't responded in quite some time, it appears I stopped receiving notifications for this thread.

After sending the requested logs (sent on 2021-03-17), I haven't received any response until now. There has also been no new driver available since the 2021-03-15 release.

I'm still running firmware version 20201120  without issues though.

Offline

#63 2021-04-03 04:31:37

Damino
Member
Registered: 2021-02-18
Posts: 8

Re: Random bluetooth speaker disconnects

My issue was resolved after BlueZ 5.56, but with the recent update of 5.57, I disconnect constantly. Even my Bluetooth mouse gets killed off. This time, they can't reconnect.
Firmware 20210315

Offline

#64 2021-04-04 09:32:54

flavius-as
Member
Registered: 2021-04-04
Posts: 2

Re: Random bluetooth speaker disconnects

I get this with Bose NC 700:

Apr 04 11:25:13 evolution obexd[862]: disconnected: Transport got disconnected
Apr 04 11:25:13 evolution bluetoothd[494]: src/profile.c:ext_io_disconnected() Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
Apr 04 11:25:13 evolution bluetoothd[494]: src/profile.c:ext_io_disconnected() Unable to get io data for Phone Book Access: getpeername: Transport endpoint is not connected (107)
Apr 04 11:25:13 evolution acpid[492]: input device has been disconnected, fd 22
Apr 04 11:25:13 evolution dbus-daemon[495]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.33" (uid=1000 pid=833 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.3" (uid=0 pid=494 comm="/usr/lib/bluetooth/bluetoothd ")
Apr 04 11:25:17 evolution bluetoothd[494]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 60:AB:D2:27:30:AA: Host is down (112)
Apr 04 11:25:18 evolution obexd[862]: CONNECT(0x0), <unknown>(0xff)
Apr 04 11:25:18 evolution obexd[862]: CONNECT(0x0), <unknown>(0x0)
Apr 04 11:25:18 evolution obexd[862]: SETPATH(0x5), <unknown>(0xff)
Apr 04 11:25:18 evolution obexd[862]: stat(/home/flav/phonebook/): No such file or directory (2)
Apr 04 11:25:18 evolution obexd[862]: SETPATH(0x5), Not Found(0x44)
Apr 04 11:25:19 evolution bluetoothd[494]: plugins/policy.c:reconnect_timeout() Reconnecting services failed: Operation already in progress (114)
Apr 04 11:25:19 evolution bluetoothd[494]: /org/bluez/hci0/dev_60_AB_D2_27_30_AA/fd9: fd(41) ready
Apr 04 11:25:19 evolution rtkit-daemon[837]: Supervising 11 threads of 8 processes of 1 users.
Apr 04 11:25:19 evolution rtkit-daemon[837]: Successfully made thread 195229 of process 833 owned by '1000' RT at priority 5.
Apr 04 11:25:19 evolution rtkit-daemon[837]: Supervising 12 threads of 8 processes of 1 users.
Apr 04 11:25:21 evolution kernel: input: Bose NC 700 HP (AVRCP) as /devices/virtual/input/input44
Apr 04 11:25:21 evolution systemd-logind[498]: Watching system buttons on /dev/input/event20 (Bose NC 700 HP (AVRCP))

How to debug this issue further?

It happens during playback with A2DP, and it comes back online after 10 seconds

Last edited by flavius-as (2021-04-04 09:34:28)

Offline

#65 2021-04-04 12:47:26

flavius-as
Member
Registered: 2021-04-04
Posts: 2

Re: Random bluetooth speaker disconnects

Got one more line at the beginning of the log, see first line:

Apr 04 14:44:51 evolution bluetoothd[494]: profiles/audio/avdtp.c:cancel_request() Suspend: Connection timed out (110)
Apr 04 14:44:52 evolution obexd[862]: disconnected: Transport got disconnected

after disabling some plugins in blueman-applet

Offline

#66 2021-04-07 14:04:14

wowsuchcode
Member
Registered: 2019-05-16
Posts: 9

Re: Random bluetooth speaker disconnects

Apr 07 15:46:11 hostname rtkit-daemon[1186]: Supervising 1 threads of 1 processes of 1 users.
Apr 07 15:46:11 hostname rtkit-daemon[1186]: Successfully made thread 567981 of process 1179 owned by '1000' RT at priority 9.
Apr 07 15:46:11 hostname rtkit-daemon[1186]: Supervising 0 threads of 0 processes of 0 users.
Apr 07 15:46:11 hostname bluetoothd[444]: /org/bluez/hci0/dev_MAC_ADDRESS/fd11: fd(28) ready
Apr 07 15:46:09 hostname systemd-logind[366]: Watching system buttons on /dev/input/event20 (WH-1000XM3 (AVRCP))
Apr 07 15:46:09 hostname kernel: input: WH-1000XM3 (AVRCP) as /devices/virtual/input/input41
Apr 07 15:46:08 hostname bluetoothd[444]: src/profile.c:record_cb() Unable to get Headset Voice gateway SDP record: Host is down
Apr 07 15:46:07 hostname bluetoothd[444]: src/profile.c:ext_io_disconnected() Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)

Same issue here. Pulseaudio 14.2 and Kernel 5.11.11-arch1-1
THinkpad T15 and WH-1000XM3

Offline

#67 2021-04-07 18:53:34

Fireminster
Member
Registered: 2020-07-12
Posts: 13

Re: Random bluetooth speaker disconnects

FYI I would be careful with downgrading too far back in bluetooth/firmware land because of this: https://google.github.io/security-resea … iteup.html

Maybe mitigations for that could also have been the reason why newer firmware/bluetooth driver combos broke?

Offline

#68 2021-04-08 16:27:44

davidgp.com
Member
Registered: 2021-04-08
Posts: 2

Re: Random bluetooth speaker disconnects

Hi,

Same problem here. So, this has been my testing so far:

Laptop: Asus G14
Wireless/BT Card: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
Kernel: 5.11.11-arch1-1
Pulseaudio: 14.2-3
pulseaudio-modules-bt: 1.4_14.2-8
Headset: Sony WH-1000XM3

With Linux firmware version: 20210315.3568f96-1 and bluez versions: 5.6-1, 5.7-1 or 5.8-1 I have the same problem as everybody else here, dropouts from time to time.

As other people here in this thread, I have installed bluez 5.56-2 and linux firmware 20201120.bc9cd0b-1 and this gave me the most stable connection. At least for several hours (around 4) no dropouts in the connection.

Other changes that I did, at the beginning the dropouts were like every 20 minutes, this got around an hour between dropouts after I followed the recommendations for Intel Wireless cards and power management: https://wiki.archlinux.org/index.php/Po … _(iwlwifi) :

# cat /etc/modprobe.d/iwlwifi.conf
options iwlwifi power_save=1
options iwlmvm power_scheme=3

Well, not 100% sure that those power management options are related or not, but at least, it is no longer as crazy as it was at the beginning with dropouts every 20 minutes. No other change that came to mind that could have do that.

P.D.: Not related with this problem, but in case it is useful for somebody, using LDAC codec or aptX HD codec with the Sony WH-1000XM3 with the headphones created lots of noise in the sound. The firmware version of my Headphones was 2.0.0, I checked with the phone Sony app there was a new version 4.x.x (too lazy to pair now the headset with the phone), and those codecs are no longer a problem, no noise in the transmission, although I have to say my ears or Spotify streams are not enough to see if there is much improvement between aptX vs aptX HD or LDAC.

Offline

#69 2021-04-11 15:15:01

Antonio05200
Member
Registered: 2020-05-14
Posts: 9

Re: Random bluetooth speaker disconnects

Hi,
Same problem with AX201

Offline

#70 2021-04-13 11:12:28

nikarh
Member
Registered: 2021-02-25
Posts: 1

Re: Random bluetooth speaker disconnects

Have experienced the same issues with AX200, My current solution is using older linux-firmware and LTS kernel. Haven't experienced disconnects for the past month or so. Upgrading firmware or switching back to the regular kernel returns the problem for me.

No disconnects with the following

linux-firmware 20201218.646f159-1
linux-lts 5.10.29-1

Offline

#71 2021-04-13 13:42:18

VLegacy
Member
Registered: 2005-01-29
Posts: 42

Re: Random bluetooth speaker disconnects

@nikarh Interesting, I have the AX200 in my laptop and downgrading linux-firmware was enough for me--no need for the LTS kernel.

linux-firmware 20201218.646f159-1
linux 5.11.13.arch1-1

Offline

#72 2021-04-13 20:52:06

mokkurkalve
Member
From: Bergen, Norway
Registered: 2009-08-29
Posts: 42

Re: Random bluetooth speaker disconnects

AX201 here. Downgrading to  linux-firmware 20201218.646f159-1 fixes the issue for me. The newer firmware packages gives regular disconnects. Version of kernel or bluez or anything else doesn't matter here, only the linux-firmware package.


"ONLY THOSE WHO ATTEMPT THE IMPOSSIBLE WILL ACHIEVE THE ABSURD"
- Oceania Association of Autonomous Astronauts

Offline

#73 2021-04-18 16:26:52

mikkl
Member
Registered: 2021-04-18
Posts: 3

Re: Random bluetooth speaker disconnects

Same issue here on Gentoo linux kernel 5.11 series with both AX200 and AX201 BT chips when playing a2dp audio. The issue occurs randomly from every 5 minutes to once a few hours. In any case, there's something wrong with the firmware and I hope this gets fixed. All people using these devices seem to be affected. When using the linux-firmware-20201218 (gentoo package) it seems to work now for several hours without disconnect. However there was one case with a disconnect (without reconnect a few seconds later) when I had to reboot the BT receiver but this may be another problem or not related to the intel BT. However, there are some pitfalls when downgrading linux-firmware package version which may be the reason why it doesn't work for some people.

1. After installing downgraded package you have to completely power off the device. A simple reboot won't work because the firmware won't be lost during a reboot and the driver seems to detect a running firmware and then skips uploading firmware to the device. During cold boot from power-off state you should be able to see kernel messages like these:

dmesg | grep "Bluetooth: hci"
[    3.988237] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[    3.992223] Bluetooth: hci0: Device revision is 1
[    3.994527] Bluetooth: hci0: Secure boot is enabled
[    3.996760] Bluetooth: hci0: OTP lock is enabled
[    3.998963] Bluetooth: hci0: API lock is enabled
[    4.001108] Bluetooth: hci0: Debug lock is disabled
[    4.003213] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    4.005297] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[    5.817024] Bluetooth: hci0: Waiting for firmware download to complete
[    5.819493] Bluetooth: hci0: Firmware loaded in 1790766 usecs
[    5.821932] Bluetooth: hci0: Waiting for device to boot
[    5.840950] Bluetooth: hci0: Device booted in 18585 usecs
[    5.843383] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
[    5.851012] Bluetooth: hci0: Applying Intel DDC parameters completed
[    5.861992] Bluetooth: hci0: Firmware revision 0.0 build 121 week 7 2021

The last line is the firmware that gets uploaded and in this case is the one from latest linux-drivers-20210315 package. The one from linux-drivers-20201218 package should look like this:

[    5.274381] Bluetooth: hci0: Firmware revision 0.0 build 127 week 48 2020

2. The firmware may be baked into the kernel so although you downgrade your linux-firmware files a kernel would have to be rebuilt with the downgraded firmware files installed. If it works for you with an older kernel it may be because it has baked in an older version of the firmware files. In any case you should be able to see the firmware version during boot as shown above.

Offline

#74 2021-04-19 18:21:16

jyxent
Member
Registered: 2013-04-24
Posts: 1

Re: Random bluetooth speaker disconnects

mikkl wrote:

1. After installing downgraded package you have to completely power off the device. A simple reboot won't work because the firmware won't be lost during a reboot and the driver seems to detect a running firmware and then skips uploading firmware to the device. During cold boot from power-off state you should be able to see kernel messages like these:

Thanks.  After turning off my computer and then the power supply, I now have the downgraded firmware running.

Is this also the case for upgrades?  It seems like it might be.  Looking at my system logs, I installed the 20120208 linux-firmware package on Feb 11, and my AX200 didn't run the firmware from that update until Mar 11.  This happened to be the date I upgraded my RAM, so my computer was completely powered off.

Also, it looks like there is an update for AX201 firmware that was added today, if anyone wanted to try:

https://git.kernel.org/pub/scm/linux/ke … 740d204180

Offline

#75 2021-04-20 18:02:50

mikkl
Member
Registered: 2021-04-18
Posts: 3

Re: Random bluetooth speaker disconnects

jyxent wrote:

Is this also the case for upgrades?  It seems like it might be.  Looking at my system logs, I installed the 20120208 linux-firmware package on Feb 11, and my AX200 didn't run the firmware    from that update until Mar 11.  This happened to be the date I upgraded my RAM, so my computer was completely powered off.

Yes, upgrade or downgrade doesn't matter. I even noticed on my NUC with AX201 I had to unplug the AC cord after shutting down or it wouldn't work because of standby-circuitry still power to the BT chip or some left over charge in the power supply, I don't know.

jyxent wrote:

Also, it looks like there is an update for AX201 firmware that was added today, if anyone wanted to try:

https://git.kernel.org/pub/scm/linux/ke … 740d204180

I tried it and it makes itself noticeable by follwing line:

[    3.645000] Bluetooth: hci0: Firmware revision 0.0 build 7 week 13 2021

I've been running it the whole day now with no disconnects so I would say it's looking good. Hopefully they did not fix this by chance so this may come up again and AX200 and other chips will get fixed, too.

Offline

Board footer

Powered by FluxBB