Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
P
pipewire
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 135
    • Issues 135
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 3
    • Merge Requests 3
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • PipeWire
  • pipewire
  • Issues
  • #545

Closed
Open
Opened Jan 06, 2021 by Sebastian A.@sebastian-aContributor

Bluetooth: Clicking Sounds in pavucontrol

Issue opened as discuessed here, I'll copy the conversation here for completeness.

@pvir I've tested v0.3.19 + the hfp backend native commits, and I have the following observations (Ubuntu 20.04):

  1. Works as expected: After switching profile to HSP/HFP, I can record sound via gnome-sound-recorder
  2. Not as expected: I hear clicking sounds in the headset, sco_source_cb() keeps loggin "read socket data 48" (even when I am not actively recording)
  3. Not as expected: dmesg shows "Bluetooth: hci0: SCO packet for unknown connection handle 0" (or handles 258/259/260/261)

Feedback re questions by @pvir: Q: Which Bluetooth adapter and model (check dmesg or lsusb)? dmesg: Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq lsusb: ID 8087:07dc Intel Corp. Headset: Soundcore Life P2

Q: Note that pavucontrol/gnome-control-center always record, since they display the microphone volume bar, perhaps you see that. Ah, makes sense, this is what triggers the "read socket data" log messages

Q: Are the clicks in the recorded audio, or appear in playback? The clicks are audible when pavucontrol is open (and records for purposes of the volume bar). No clicking when I close pavucontrol.

**Q: Try to play/record with pw-play and pw-record instead of g-s-r, does the problem still appear? ** No clicking when using pw-play and pw-record, also no clicking when using gnome-sound-recorder.

The SCO dmesg messages likely are harmless, they appear also for me.

Remark: After going through @pvir's question it's probably not the most pressing problem right now. I'll leave it here for completeness anyway.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: pipewire/pipewire#545