Bluetooth headset suddenly stops playback (until power is turned off and on again)"

Bug #2018305 reported by fringetos.Kim
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pulseaudio (Ubuntu)
New
Undecided
Unassigned

Bug Description

When watching videos using video players (SM Player, VLC, etc.) and repeatedly using the space key to toggle play/pause, the sound output to the Bluetooth headset stops working after a short while. When the Bluetooth headset's power is turned off, the sound that was not working immediately starts coming out of the built-in speaker. It's as if the sound data that was trapped in a queue suddenly pours out when the blockage is cleared. The same symptom occurs not only in video players, but also in other learning programs and places where keyboard or mouse clicks are repeated. Whenever the sound gets blocked, I have to repeatedly turn the Bluetooth headset off and on again. This issue occurs very frequently. I have tested 4 different Bluetooth headsets (Samsung Level U2, Samsung Galaxy Buds Pro, JBL TUNE660NC, LG HBS830), and so far, I have confirmed that the same issue occurs with all the headsets.Turning off the Bluetooth headset's power or running the '$ pulseaudio -k' command allows the previously frozen video to resume and the blocked sound to play through the built-in speaker. When I turn the Bluetooth headset's power back on, it reconnects, and the sound starts playing through the headset.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: fts 2436 F.... pulseaudio
 /dev/snd/controlC1: fts 2436 F.... pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue May 2 22:43:12 2023
InstallationDate: Installed on 2022-07-09 (297 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: Bluetooth sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/20/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P03AJK.039.210920.SH
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NT850XCR-HD7AB
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGLFREEDOS-C00-R000-S0000+1.0.0000
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03AJK.039.210920.SH:bd09/20/2021:br5.17:svnSAMSUNGELECTRONICSCO.,LTD.:pn850XCJ:pvrP03AJK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT850XCR-HD7AB:rvrSGLFREEDOS-C00-R000-S0000+1.0.0000:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PAJK:
dmi.product.family: Odyssey Series
dmi.product.name: 850XCJ
dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAJK
dmi.product.version: P03AJK
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
fringetos.Kim (fringetos) wrote :
affects: ubuntu → alsa-driver (Ubuntu)
Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

bluetooth audio isn't handled by alsa, but by pulseaudio directly.

affects: alsa-driver (Ubuntu) → pulseaudio (Ubuntu)
Revision history for this message
fringetos.Kim (fringetos) wrote (last edit ):

I have tested 4 different Bluetooth headsets (Samsung Level U2, Samsung Galaxy Buds Pro, JBL TUNE660NC, LG HBS830), and so far, I have confirmed that the same issue occurs with all the headsets. Turning off the Bluetooth headset's power or running the '$ pulseaudio -k' command allows the previously frozen video to resume and the blocked sound to play through the built-in speaker. When I turn the Bluetooth headset's power back on, it reconnects, and the sound starts playing through the headset.

description: updated
description: updated
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.