Bluetooth issues

Hi all,

I have problems with a bluetooth, specifically when I am listening music on my Bluetooth headphones.

I figured that when I am watching/listening Youtube,
sound stops for few seconds but on Youtube it is running normally.

Also while I am doing something , multitasking etc sound also stops for few sec , lags.

Is it normal for Linux ? I don't have such problems with my phone or Windows.

Thanks

No, read

We need more details :slight_smile:

1 Like

Ahh..I know that..will post more when I get home :wink:

1 Like

inxi -Fxxxza output

>     System:
>       Kernel: 5.9.14-99-tkg-bmq x86_64 bits: 64 compiler: gcc v: 10.2.0 
>       parameters: intel_pstate=passive 
>       BOOT_IMAGE=/@/boot/vmlinuz-linux-tkg-bmq 
>       root=UUID=11de5c08-b64e-4502-97f8-a61295848e7e rw [email protected] 
>       quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 
>       systemd.unified_cgroup_hierarchy=1 
>       resume=UUID=3b4f21d2-8f3a-4387-b37c-0102e3a4df99 loglevel=3 
>       Desktop: KDE Plasma 5.20.4 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 
>       dm: SDDM Distro: Garuda Linux 
>     Machine:
>       Type: Convertible System: HP product: HP ENVY x360 Convertible 13-ar0xxx 
>       v: N/A serial: <filter> Chassis: type: 31 serial: <filter> 
>       Mobo: HP model: 85DE v: 41.36 serial: <filter> UEFI: AMI v: F.19 
>       date: 12/26/2019 
>     Battery:
>       ID-1: BAT0 charge: 51.3 Wh condition: 51.3/51.3 Wh (100%) 
>       volts: 17.4/15.4 model: 333-2B-49-A KC04053XL type: Li-ion 
>       serial: <filter> status: Full 
>       Device-1: hid-0018:04F3:23B9.0004-battery model: ELAN2514:00 04F3:23B9 
>       serial: N/A charge: N/A status: N/A 
>     CPU:
>       Info: Quad Core model: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx 
>       bits: 64 type: MT MCP arch: Zen+ family: 17 (23) model-id: 18 (24) 
>       stepping: 1 microcode: 8108102 L2 cache: 2048 KiB 
>       flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
>       bogomips: 33568 
>       Speed: 1439 MHz min/max: 1400/2100 MHz boost: enabled Core speeds (MHz): 
>       1: 1224 2: 1833 3: 1250 4: 2175 5: 1597 6: 2070 7: 1226 8: 1231 
>       Vulnerabilities: Type: itlb_multihit status: Not affected 
>       Type: l1tf status: Not affected 
>       Type: mds status: Not affected 
>       Type: meltdown status: Not affected 
>       Type: spec_store_bypass 
>       mitigation: Speculative Store Bypass disabled via prctl and seccomp 
>       Type: spectre_v1 
>       mitigation: usercopy/swapgs barriers and __user pointer sanitization 
>       Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, 
>       STIBP: disabled, RSB filling 
>       Type: srbds status: Not affected 
>       Type: tsx_async_abort status: Not affected 
>     Graphics:
>       Device-1: AMD Picasso vendor: Hewlett-Packard driver: amdgpu v: kernel 
>       bus ID: 04:00.0 chip ID: 1002:15d8 
>       Device-2: Lite-On HP Wide Vision HD Camera type: USB driver: uvcvideo 
>       bus ID: 3-1:2 chip ID: 04ca:709d 
>       Display: x11 server: X.org 1.20.10 compositor: kwin_x11 
>       driver: amdgpu,ati unloaded: modesetting alternate: fbdev,vesa 
>       resolution: <missing: xdpyinfo> 
>       OpenGL: renderer: AMD Radeon Vega 8 Graphics (RAVEN DRM 3.39.0 
>       5.9.14-99-tkg-bmq LLVM 11.0.0) 
>       v: 4.6 Mesa 20.3.0 direct render: Yes 
>     Audio:
>       Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio 
>       vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 04:00.1 
>       chip ID: 1002:15de 
>       Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor 
>       vendor: Hewlett-Packard driver: N/A 
>       alternate: snd_pci_acp3x, snd_rn_pci_acp3x bus ID: 04:00.5 
>       chip ID: 1022:15e2 
>       Device-3: AMD Family 17h HD Audio vendor: Hewlett-Packard 
>       driver: snd_hda_intel v: kernel bus ID: 04:00.6 chip ID: 1022:15e3 
>       Sound Server: ALSA v: k5.9.14-99-tkg-bmq 
>     Network:
>       Device-1: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter 
>       vendor: Hewlett-Packard driver: rtw_8822be v: N/A modules: rtw88_8822be 
>       port: f000 bus ID: 02:00.0 chip ID: 10ec:b822 
>       IF: wlo1 state: up mac: <filter> 
>     Drives:
>       Local Storage: total: 476.94 GiB used: 17.89 GiB (3.8%) 
>       SMART Message: Unable to run smartctl. Root privileges required. 
>       ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKNW512G8H size: 476.94 GiB 
>       block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 
>       serial: <filter> rev: HPS0 scheme: GPT 
>     Partition:
>       ID-1: / raw size: 467.84 GiB size: 467.84 GiB (100.00%) 
>       used: 17.89 GiB (3.8%) fs: btrfs dev: /dev/nvme0n1p2 
>       ID-2: /home raw size: 467.84 GiB size: 467.84 GiB (100.00%) 
>       used: 17.89 GiB (3.8%) fs: btrfs dev: /dev/nvme0n1p2 
>       ID-3: /var/log raw size: 467.84 GiB size: 467.84 GiB (100.00%) 
>       used: 17.89 GiB (3.8%) fs: btrfs dev: /dev/nvme0n1p2 
>       ID-4: /var/tmp raw size: 467.84 GiB size: 467.84 GiB (100.00%) 
>       used: 17.89 GiB (3.8%) fs: btrfs dev: /dev/nvme0n1p2 
>     Swap:
>       Kernel: swappiness: 10 (default 60) cache pressure: 75 (default 100) 
>       ID-1: swap-1 type: partition size: 8.80 GiB used: 0 KiB (0.0%) 
>       priority: -2 dev: /dev/nvme0n1p3 
>       ID-2: swap-2 type: zram size: 734.5 MiB used: 0 KiB (0.0%) 
>       priority: 32767 dev: /dev/zram0 
>       ID-3: swap-3 type: zram size: 734.5 MiB used: 0 KiB (0.0%) 
>       priority: 32767 dev: /dev/zram1 
>       ID-4: swap-4 type: zram size: 734.5 MiB used: 0 KiB (0.0%) 
>       priority: 32767 dev: /dev/zram2 
>       ID-5: swap-5 type: zram size: 734.5 MiB used: 0 KiB (0.0%) 
>       priority: 32767 dev: /dev/zram3 
>       ID-6: swap-6 type: zram size: 734.5 MiB used: 0 KiB (0.0%) 
>       priority: 32767 dev: /dev/zram4 
>       ID-7: swap-7 type: zram size: 734.5 MiB used: 0 KiB (0.0%) 
>       priority: 32767 dev: /dev/zram5 
>       ID-8: swap-8 type: zram size: 734.5 MiB used: 0 KiB (0.0%) 
>       priority: 32767 dev: /dev/zram6 
>       ID-9: swap-9 type: zram size: 734.5 MiB used: 0 KiB (0.0%) 
>       priority: 32767 dev: /dev/zram7 
>     Sensors:
>       System Temperatures: cpu: 57.1 C mobo: 40.0 C gpu: amdgpu temp: 57.0 C 
>       Fan Speeds (RPM): N/A 
>     Info:
>       Processes: 286 Uptime: 5m wakeups: 46 Memory: 5.74 GiB 
>       used: 2.95 GiB (51.4%) Init: systemd v: 247 Compilers: gcc: 10.2.0 
>       clang: 11.0.0 Packages: pacman: 1289 lib: 429 Shell: fish v: 3.1.2 
>       running in: konsole inxi: 3.1.09 
1 Like

There is no other device in Network. I would expect a BT device here...
Have you checked Archwiki about BT headphones and BT?

2 Likes

upps.. I was faster than my wifi connection.. here it is

> Network:
>   Device-1: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter 
>   vendor: Hewlett-Packard driver: rtw_8822be v: N/A modules: rtw88_8822be 
>   port: f000 bus ID: 02:00.0 chip ID: 10ec:b822 
>   IF: wlo1 state: up mac: <filter> 

Some more info > https://bin.garudalinux.org/?1e65fb60bf21eb22#9BbiwGzJaDLxMfCnkTnqD6q591bp21ErWhcaGY2aLz53

And yes, I checked Archwiki, followed the thread.
I am not sure, but I noticed that when I connect my bluetooth headphones or even turn on bluetooth on my laptop, wifi network went crazy. From no bandwith traffic at all, to slower wifi.. weird

It maybe a bug.

1 Like

but I can connect them.. And listen ..but sometimes sound is laggy , like latency is borked

Because I believe you, I say it maybe a bug.
Have you read the linked report?

3 Likes

Yes :grinning:

So you understand it's not a distro bug.
Check for errors or other helpful info in journal

journalctl -b -p3 --no-hostname --no-pager
journalctl -b  --no-hostname --no-pager | grep -iwE "bt|bluetooth"
1 Like
╰─λ journalctl -b -p3 --no-hostname --no-pager
-- Journal begins at Fri 2020-12-11 20:53:46 CET, ends at Wed 2020-12-16 21:31:15 CET. --
pro 16 18:13:57 kernel: pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter.
pro 16 18:13:58 systemd-udevd[330]: nvme0: /etc/udev/rules.d/60-ioschedulers.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.7/0000:03:00.0/nvme/nvme0/queue/scheduler}, ignoring: No such file or directory
pro 16 18:13:58 kernel: lis3lv02d: unknown sensor type 0x0
pro 16 18:13:58 systemd-udevd[346]: nvme0n1p3: /etc/udev/rules.d/60-ioschedulers.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.7/0000:03:00.0/nvme/nvme0/nvme0n1/nvme0n1p3/queue/scheduler}, ignoring: No such file or directory
pro 16 18:13:58 systemd-udevd[357]: nvme0n1p1: /etc/udev/rules.d/60-ioschedulers.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.7/0000:03:00.0/nvme/nvme0/nvme0n1/nvme0n1p1/queue/scheduler}, ignoring: No such file or directory
pro 16 18:13:58 systemd-udevd[360]: nvme0n1p2: /etc/udev/rules.d/60-ioschedulers.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.7/0000:03:00.0/nvme/nvme0/nvme0n1/nvme0n1p2/queue/scheduler}, ignoring: No such file or directory
pro 16 18:13:58 kernel: snd_pci_acp3x 0000:04:00.5: Invalid ACP audio mode : 1
pro 16 18:13:58 kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xd7d09000-0xd7d09fff flags 0x200] vs d7d09000 4000
pro 16 18:13:58 kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xd7d0d000-0xd7d0dfff flags 0x200] vs d7d0d000 4000
pro 16 18:13:58 kernel: sp5100-tco sp5100-tco: Watchdog hardware is disabled
pro 16 18:13:58 systemd-udevd[350]: nvme0n1p1: /etc/udev/rules.d/60-ioschedulers.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.7/0000:03:00.0/nvme/nvme0/nvme0n1/nvme0n1p1/queue/scheduler}, ignoring: No such file or directory
pro 16 18:13:58 kernel: Error: Driver 'rtw_8822be' is already registered, aborting...
pro 16 18:13:58 kernel: kvm: disabled by bios
pro 16 18:13:58 kernel: kvm: disabled by bios
pro 16 18:13:58 systemd-tmpfiles[457]: Failed to write file "/sys/module/pcie_aspm/parameters/policy": Operation not permitted
pro 16 18:13:58 kernel: kvm: disabled by bios
pro 16 18:13:58 kernel: kvm: disabled by bios
pro 16 18:13:58 kernel: kvm: disabled by bios
pro 16 18:13:58 kernel: kvm: disabled by bios
pro 16 18:13:58 kernel: kvm: disabled by bios
pro 16 18:13:58 kernel: kvm: disabled by bios
pro 16 18:13:59 bluetoothd[480]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:16:94:41:F2:47: Protocol not available
pro 16 18:17:18 bluetoothd[480]: src/profile.c:record_cb() Unable to get Headset Voice gateway SDP record: Host is down
pro 16 20:44:36 kernel: Bluetooth: hci0: HCI reset during shutdown failed
pro 16 20:44:36 bluetoothd[480]: src/profile.c:ext_io_disconnected() Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
pro 16 21:29:57 kernel: debugfs: File 'force_bredr_smp' in directory 'hci0' already present!
pro 16 21:30:28 bluetoothd[480]: src/profile.c:ext_connect() Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
╭─marko at marko-hpenvyx360convertible13ar0xxx in ⌁
╰─λ journalctl -b  --no-hostname --no-pager | grep -iwE "bt|bluetooth"
pro 16 18:13:58 kernel: usb 3-2: Product: Bluetooth Radio 
pro 16 18:13:58 kernel: Bluetooth: Core ver 2.22
pro 16 18:13:58 kernel: Bluetooth: HCI device and connection manager initialized
pro 16 18:13:58 kernel: Bluetooth: HCI socket layer initialized
pro 16 18:13:58 kernel: Bluetooth: L2CAP socket layer initialized
pro 16 18:13:58 kernel: Bluetooth: SCO socket layer initialized
pro 16 18:13:58 kernel: Bluetooth: hci0: RTL: examining hci_ver=07 hci_rev=000b lmp_ver=07 lmp_subver=8822
pro 16 18:13:58 kernel: Bluetooth: hci0: RTL: rom_version status=0 version=2
pro 16 18:13:58 kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8822b_fw.bin
pro 16 18:13:58 kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8822b_config.bin
pro 16 18:13:58 kernel: Bluetooth: hci0: RTL: cfg_sz 14, total sz 20270
pro 16 18:13:58 systemd[1]: Started Bluetooth autoconnect service.
pro 16 18:13:58 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth-autoconnect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
pro 16 18:13:58 systemd[1]: Starting Bluetooth service...
pro 16 18:13:58 bluetoothd[480]: Bluetooth daemon 5.55
pro 16 18:13:58 systemd[1]: Started Bluetooth service.
pro 16 18:13:58 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
pro 16 18:13:58 systemd[1]: Reached target Bluetooth.
pro 16 18:13:58 kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
pro 16 18:13:58 kernel: Bluetooth: BNEP filters: protocol multicast
pro 16 18:13:58 kernel: Bluetooth: BNEP socket layer initialized
pro 16 18:13:58 bluetoothd[480]: Bluetooth management interface 1.18 initialized
pro 16 18:13:59 NetworkManager[483]: <info>  [1608138839.1075] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.26.4-1/libnm-device-plugin-bluetooth.so)
pro 16 18:13:59 kernel: Bluetooth: hci0: RTL: fw version 0xab6b705c
pro 16 18:13:59 bluetooth-autoconnect[479]: connecting to device /org/bluez/hci0/dev_00_16_94_41_F2_47
pro 16 18:13:59 bluetooth-autoconnect[479]: error connecting to device /org/bluez/hci0/dev_00_16_94_41_F2_47: Protocol not available
pro 16 18:17:12 systemd[2351]: Starting Bluetooth OBEX service...
pro 16 18:17:12 kded5[2671]: bluedevil: Bluetooth operational changed true
pro 16 18:17:12 systemd[2351]: Started Bluetooth OBEX service.
pro 16 18:17:12 kernel: Bluetooth: RFCOMM TTY layer initialized
pro 16 18:17:12 kernel: Bluetooth: RFCOMM socket layer initialized
pro 16 18:17:12 kernel: Bluetooth: RFCOMM ver 1.11
pro 16 18:17:12 systemd[2351]: Started Bluetooth autoconnect service for pulseaudio.
pro 16 18:17:13 bluetooth-autoconnect[2843]: connecting to device /org/bluez/hci0/dev_00_16_94_41_F2_47
pro 16 18:17:13 systemd[1]: Starting Bluetooth management mechanism...
pro 16 18:17:13 systemd[1]: Started Bluetooth management mechanism.
pro 16 18:17:18 bluetooth-autoconnect[2843]: error connecting to device /org/bluez/hci0/dev_00_16_94_41_F2_47: Host is down
pro 16 18:17:18 systemd[2351]: pulseaudio-bluetooth-autoconnect.service: Succeeded.
pro 16 20:28:18 systemd[2351]: Reached target Bluetooth.
pro 16 20:44:36 dbus-daemon[482]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.41" (uid=1000 pid=2767 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.1" (uid=0 pid=480 comm="/usr/lib/bluetooth/bluetoothd ")
pro 16 20:44:36 kernel: Bluetooth: hci0: HCI reset during shutdown failed
pro 16 21:29:57 systemd[1]: Starting Bluetooth management mechanism...
pro 16 21:29:57 systemd[1]: Started Bluetooth management mechanism.
pro 16 21:29:57 bluetooth-autoconnect[479]: connecting to device /org/bluez/hci0/dev_00_16_94_41_F2_47
pro 16 21:30:22 bluetooth-autoconnect[479]: error connecting to device /org/bluez/hci0/dev_00_16_94_41_F2_47: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

There are possible causes, like "host is down". Are you sure there is no issue with exhausted battery?

Or it might be a bug.

IDK, not searched.
Firewalld can block BT?

no, my bluetooth headphones are fully charged

In bluetooth headset wiki, there are several sections about possible issues and what you should do to troubleshoot properly.
Please do your best.
I cannot enter in your office area, yet, but I will try harder. :man_shrugging:

3 Likes