[Multiple bluetooth speakers, playback] Stuttering sound

[8765pu]

Constant stuttering sound, stuttering at maybe 10 times/second. More than one speaker with the same symptoms.

Speakers work in Windows 10 / macOS 10.14+ running on same hardware.

Same speakers work on Ubuntu Mate 18.04 32 bit running on different hardware.

Remote control commands work (play/pause button on speakers).

Initial pairing and connection requires from 2 to about 10 retries. All tested within 1 m distance.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.2-1ubuntu2.1
ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
Uname: Linux 5.8.0-33-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu50.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: username 3486 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 14 13:49:26 2020
InstallationDate: Installed on 2020-10-30 (45 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: Crossbeat
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [Crossbeat, playback] Underruns, dropouts or crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/10/2020
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 264.0.0.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-2E6FAB96566FE58C
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir5,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-2E6FAB96566FE58C
dmi.modalias: dmi:bvnAppleInc.:bvr264.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C:
dmi.product.family: MacBook Air
dmi.product.name: MacBookAir5,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

[Daniel van Vugt (vanvugt)]

1. This is probably an issue with the Bluetooth kernel driver. Please run:

   lspci -kv > lspci.txt
   lsusb > lsusb.txt

   and attach the resulting text files here.

2. Please ensure the latest driver is installed by running:

   sudo apt install bcmwl-kernel-source

   and then reboot.

3. Try closing Settings, in case you are experiencing bug 1797002.

[8765pu (8765pukxbhc876y-deactivatedaccount)]

Thanks for the suggestions. Closing the settings window makes the problem disappear. Good call.

Unlike the reporter in the linked bug I wouldn't exactly call that a "solution" (and certainly not "simple") since there is very little chance I would consider closing the settings window before confirming that the speaker works properly.

[8765pu (8765pukxbhc876y-deactivatedaccount)]

I will be deleting all attachments, unless you think any of them are strictly necessary?

[Daniel van Vugt (vanvugt)]

Bug 1797002 is still open. We don't consider it resolved so this is now a duplicate of that.

Yes you are free to delete any attachments from this bug that you wish. In future if you are concerned about the privacy of attachments you can mark your bugs as Private at the top-right of the page. Then only a very small team of bug reviewers will be able to see them.

[8765pu (8765pukxbhc876y-deactivatedaccount)]

Thank you for the suggestion. I tried what you suggested in another bug (for gnome-shell) and got the message "The bug will become invisible because there is no-one with permissions to see Private bugs" -- is that option really a solution? Sounds like reports become pointless if that option is activated.

[Daniel van Vugt (vanvugt)]

Hmm, maybe it depends on which project the bug is assigned to.

Certainly I and other people do see plenty of private bugs. But we can't prove that we see all private bugs.

[8765pu (8765pukxbhc876y-deactivatedaccount)]

I understand. I was assuming that gnome-shell was big enough to warrant at least one person who could view private reports, and that the message suggested a mistake.

Thanks for the info.