Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pulseaudio pulseaudio
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 863
    • Issues 863
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 49
    • Merge requests 49
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PulseAudio
  • pulseaudiopulseaudio
  • Merge requests
  • !522

Draft: bluetooth: assume software volume control until peer replies

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Igor Kovalenko requested to merge igor.v.kovalenko/pulseaudio:pr/bluetooth-assume-software-volume-for-headset-mic into master Mar 06, 2021
  • Overview 3
  • Commits 2
  • Pipelines 5
  • Changes 3

Support for remote audio volume control is optional for HSP and HFP profiles, and there is no feedback from peer for +VGM and +VGS.

In practice remote volume control is implemented for speaker and changing volume using +VGS reply works, while doing the same with +VGM for mic does not.

Assume software volume control for peer mic until peer sends AT+VGM= command which should mean peer supports remote volume control for mic as well.

This change is based on Rodrigo Araujo's work here https://lists.freedesktop.org/archives/pulseaudio-discuss/2017-September/028820.html

Note the new can_attenuate_source_volume API change for transport also works for A2DP profiles. For A2DP new callbacks are not defined which indicates A2DP transport endpoints cannot do volume attenuation which turns on software volume control.

Edited Mar 09, 2021 by Igor Kovalenko
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: pr/bluetooth-assume-software-volume-for-headset-mic