Bluetooth speaker (apparently) initiates disconnection on idle

mickleby · April 16, 2023, 5:04pm

Hello Garuda users.

When I login after reboot the Bluetooth speaker connects automatically. However after about 2 minutes idle the speaker disconnects. I connect the speaker again, and it disconnects after 20 minutes idle thereafter. I figure this is designed behavior, and I'm hoping the design includes other options.

I can see this interaction between devices using btmon. For example, here is a disconnection finishing:

        Status: Success (0x00)
        Handle: 256 Address: 54:15:89:07:49:A4 (MCS Logic Inc.)
        Reason: Remote User Terminated Connection (0x13)
@ MGMT Event: Device Disconnected (0x000c) plen 8                                            {0x0001} [hci0] 1706.248898
        BR/EDR Address: 54:15:89:07:49:A4 (MCS Logic Inc.)
        Reason: Connection terminated by remote host (0x03)
< HCI Command: Write Scan Enable (0x03|0x001a) plen 1                                            #160 [hci0] 1706.272656
        Scan enable: Page Scan (0x02)
> HCI Event: Command Complete (0x0e) plen 4                                                      #161 [hci0] 1706.274528

It looks like a "request to disconnect" from the speaker. I should be able to respond in the negative, is that correct?

I think previously I had used an HDMI connection to the speaker to avoid this issue, although my recollection is hazy.

I've spent a few hours searching around but haven't found the info I need to even create a sufficient search.

-- mickleby

Complete disconnection dialog:

      L2CAP: Disconnection Response (0x07) ident 13 len 4
        Destination CID: 2546
        Source CID: 67
^[> ACL Data RX: Handle 256 flags 0x02 dlen 12                                                     #144 [hci0] 1706.065802
      L2CAP: Disconnection Request (0x06) ident 169 len 4
        Destination CID: 68
        Source CID: 2547
> ACL Data RX: Handle 256 flags 0x02 dlen 7                                                      #145 [hci0] 1706.065810
      Channel: 64 len 3 [PSM 25 mode Basic (0x00)] {chan 1}
      AVDTP: Close (0x08) Command (0x00) type 0x00 label 0 nosp 0
        ACP SEID: 7
< ACL Data TX: Handle 256 flags 0x00 dlen 12                                                     #146 [hci0] 1706.066010
      L2CAP: Disconnection Response (0x07) ident 169 len 4
        Destination CID: 68
        Source CID: 2547
< ACL Data TX: Handle 256 flags 0x00 dlen 6                                                      #147 [hci0] 1706.066380
      Channel: 2544 len 2 [PSM 25 mode Basic (0x00)] {chan 1}
      AVDTP: Close (0x08) Response Accept (0x02) type 0x00 label 0 nosp 0
> HCI Event: Number of Completed Packets (0x13) plen 5                                           #148 [hci0] 1706.069535
        Num handles: 1
        Handle: 256 Address: 54:15:89:07:49:A4 (MCS Logic Inc.)
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5                                           #149 [hci0] 1706.071491
        Num handles: 1
        Handle: 256 Address: 54:15:89:07:49:A4 (MCS Logic Inc.)
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 12                                                     #150 [hci0] 1706.074598
      L2CAP: Disconnection Request (0x06) ident 170 len 4
        Destination CID: 66
        Source CID: 2545
> ACL Data RX: Handle 256 flags 0x02 dlen 12                                                     #151 [hci0] 1706.074600
      L2CAP: Disconnection Request (0x06) ident 171 len 4
        Destination CID: 64
        Source CID: 2544
< ACL Data TX: Handle 256 flags 0x00 dlen 12                                                     #152 [hci0] 1706.074674
      L2CAP: Disconnection Response (0x07) ident 170 len 4
        Destination CID: 66
        Source CID: 2545
< ACL Data TX: Handle 256 flags 0x00 dlen 12                                                     #153 [hci0] 1706.074690
      L2CAP: Disconnection Response (0x07) ident 171 len 4
        Destination CID: 64
        Source CID: 2544
> HCI Event: Number of Completed Packets (0x13) plen 5                                           #154 [hci0] 1706.078487
        Num handles: 1
        Handle: 256 Address: 54:15:89:07:49:A4 (MCS Logic Inc.)
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5                                           #155 [hci0] 1706.080466
        Num handles: 1
        Handle: 256 Address: 54:15:89:07:49:A4 (MCS Logic Inc.)
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 12                                                     #156 [hci0] 1706.084618
      L2CAP: Disconnection Request (0x06) ident 172 len 4
        Destination CID: 65
        Source CID: 2543
< ACL Data TX: Handle 256 flags 0x00 dlen 12                                                     #157 [hci0] 1706.084659
      L2CAP: Disconnection Response (0x07) ident 172 len 4
        Destination CID: 65
        Source CID: 2543
> HCI Event: Number of Completed Packets (0x13) plen 5                                           #158 [hci0] 1706.088463
        Num handles: 1
        Handle: 256 Address: 54:15:89:07:49:A4 (MCS Logic Inc.)
        Count: 1
> HCI Event: Disconnect Complete (0x05) plen 4                                                   #159 [hci0] 1706.248681
        Status: Success (0x00)
        Handle: 256 Address: 54:15:89:07:49:A4 (MCS Logic Inc.)
        Reason: Remote User Terminated Connection (0x13)
@ MGMT Event: Device Disconnected (0x000c) plen 8                                            {0x0001} [hci0] 1706.248898
        BR/EDR Address: 54:15:89:07:49:A4 (MCS Logic Inc.)
        Reason: Connection terminated by remote host (0x03)
< HCI Command: Write Scan Enable (0x03|0x001a) plen 1                                            #160 [hci0] 1706.272656
        Scan enable: Page Scan (0x02)
> HCI Event: Command Complete (0x0e) plen 4                                                      #161 [hci0] 1706.274528

Inxi:

 ╰─λ sudo garuda-inxi
[sudo] password for mickleby:
System:
  Kernel: 6.2.11-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=7ce7773f-cf24-4ed4-92fd-61d4b91d7a28 rw rootflags=subvol=@
    quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    loglevel=3
  Desktop: Qtile v: 0.22.1 wm: LG3D dm: SDDM Distro: Garuda Linux
    base: Arch Linux
Machine:
  Type: Desktop System: AZW product: SEi v: N/A serial: N/A
  Mobo: AZW model: SEi serial: N/A UEFI: American Megatrends LLC.
    v: ALDER109 date: 12/01/2022
Battery:
  Device-1: hidpp_battery_0 model: Logitech Illuminated Living-Room Keyboard
    K830 serial: <filter> charge: 100% (should be ignored) rechargeable: yes
    status: discharging
CPU:
  Info: model: 12th Gen Intel Core i5-1235U socket: U3E1 bits: 64
    type: MST AMCP arch: Alder Lake level: v3 note: check built: 2021+
    process: Intel 7 (10nm ESF) family: 6 model-id: 0x9A (154) stepping: 4
    microcode: 0x429
  Topology: cpus: 1x cores: 10 mt: 2 tpc: 2 st: 8 threads: 12 smt: enabled
    cache: L1: 928 KiB desc: d-8x32 KiB, 2x48 KiB; i-2x32 KiB, 8x64 KiB
    L2: 6.5 MiB desc: 2x1.2 MiB, 2x2 MiB L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 2353 high: 2500 min/max: 400/4400:3300
    base/boost: 1188/4400 scaling: driver: intel_pstate governor: powersave
    volts: 0.7 V ext-clock: 100 MHz cores: 1: 2500 2: 2500 3: 740 4: 2500
    5: 2500 6: 2500 7: 2500 8: 2500 9: 2500 10: 2500 11: 2500 12: 2500
    bogomips: 59904
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel Alder Lake-UP3 GT2 [Iris Xe Graphics] driver: i915 v: kernel
    arch: Gen-12.2 process: Intel 10nm built: 2021-22+ ports: active: HDMI-A-1
    empty: HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:46a8 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.8 compositor: Picom v: git-c4107
    driver: X: loaded: modesetting alternate: fbdev,intel,vesa dri: iris
    gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1360x768 s-dpi: 96 s-size: 358x202mm (14.09x7.95")
    s-diag: 411mm (16.18")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 model: LG (GoldStar) TV
    serial: <filter> built: 2012 res: 1360x768 hz: 60 dpi: 216 gamma: 1.2
    size: 160x90mm (6.3x3.54") diag: 1836mm (72.3") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: OpenGL Message: Unable to show GL data. Required tool glxinfo
    missing.
Audio:
  Device-1: Intel Alder Lake PCH-P High Definition Audio driver: snd_hda_intel
    v: kernel alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3
    chip-ID: 8086:51c8 class-ID: 0403
  API: ALSA v: k6.2.11-zen1-1-zen status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.69 status: n/a (root, process) with:
    1: pipewire-pulse status: active 2: wireplumber status: active
    3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:51f0 class-ID: 0280
  IF: wlo1 state: down mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000
    bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 3-10:3 chip-ID: 8087:0026 class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
  Local Storage: total: 535.41 GiB used: 11.1 GiB (2.1%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Micron model: 2400 MTFDKBA512QFM
    size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: V3MA002 temp: 31.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 type: USB vendor: PNY model: USB 3.0 FD
    size: 58.47 GiB block-size: physical: 512 B logical: 512 B type: N/A
    serial: <filter> scheme: MBR
Partition:
  ID-1: / raw-size: 38.67 GiB size: 38.67 GiB (100.00%)
    used: 11.07 GiB (28.6%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p5
    maj-min: 259:5
  ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
    used: 34.7 MiB (36.2%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
    maj-min: 259:1
  ID-3: /home raw-size: 38.67 GiB size: 38.67 GiB (100.00%)
    used: 11.07 GiB (28.6%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p5
    maj-min: 259:5
  ID-4: /var/log raw-size: 38.67 GiB size: 38.67 GiB (100.00%)
    used: 11.07 GiB (28.6%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p5
    maj-min: 259:5
  ID-5: /var/tmp raw-size: 38.67 GiB size: 38.67 GiB (100.00%)
    used: 11.07 GiB (28.6%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p5
    maj-min: 259:5
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 15.39 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 30.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 303 Uptime: 14m wakeups: 8 Memory: 15.39 GiB
  used: 2.99 GiB (19.4%) Init: systemd v: 253 default: graphical
  tool: systemctl Compilers: gcc: 12.2.1 Packages: pm: pacman pkgs: 1187
  libs: 326 tools: pamac,paru Shell: garuda-inxi (sudo) default: Bash
  v: 5.1.16 running-in: alacritty inxi: 3.3.26
Garuda (2.6.16-1):
  System install date:     2023-04-11
  Last full system update: 2023-04-16
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       Yes
  Failed units:

 ╭─mickleby@mickleby in ~ via  v3.10.10 as 🧙 took 8s
 ╰─λ

BluishHumility · April 16, 2023, 5:34pm

This sounds like it's probably a feature of the speakers, not the OS. You could test that theory by pairing the speakers to something else (like a mobile phone) to see if you can reproduce the timeout/disconnection event.

What kind of speakers are they? If you can find the exact model that might be helpful.

mickleby · April 16, 2023, 5:39pm

Samsung Soundbar S5A-Series, model S50A.

I think that was the hint I needed:

How do I stop my Samsung sound bar from turning off automatically?

You can turn this feature off if you don’t like it. To disable the Auto Power Link feature, find the Auto Power button on your soundbar remote and press it once. Each time the button is pressed, your soundbar will alternate between Power Link On and Power Link Off.

[

Soundbar turns on automatically - Samsung

[image]
Samsung
https://www.samsung.com › support › TSG01110025
](Soundbar turns on automatically)

Search for: How do I stop my Samsung sound bar from turning off automatically?

system · April 18, 2023, 5:40pm

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.