New issue
Advanced search Search tips

Issue 599104 link

Starred by 2 users

Issue metadata

Status: Archived
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature

Blocking:
issue 596745
issue 610271



Sign in to add a comment

AVRCP: support absolute volume on bluetooth headset

Project Member Reported by hychao@chromium.org, Mar 30 2016

Issue description

For bluetooth headset/speaker without volume button:
 - Stick to existing solution: Chrome OS host adjust volume by software

For bluetooth headset/speaker with volume button:
 - Bluetooth headset itself will adjust volume
 - when user press volume button on headset, the adjusted volume will be reflected on Chrome OS host (volume bar appear on UI)


 
Blocking: 610271

Comment 2 by hychao@chromium.org, May 26 2016

Labels: -M-52 M-53
Originally I expect this require changes in both CRAS and BlueZ so I created separate  issue 605035  to track CRAS part.
The CRAS changes have been merged today, and it turns out we need no additional BlueZ changes to make things work. The absolute volume should work in M53 now.
Still occasionally I see AVRCP connection drop, will do more tests and use this issue to track the rest of the work.
Project Member

Comment 3 by sheriffbot@chromium.org, Jul 14 2016

Labels: -M-53 M-54 MovedFrom-53
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by hychao@chromium.org, Nov 29 2016

Status: Fixed (was: Started)
Cc: -jleong@chromium.org
Status: Assigned (was: Fixed)
To clarify, the volume buttons are supposed to adjust the /system/ volume?  Currently, we hear the volume adjusting but the system volume remains at the same level.

Comment 6 by hychao@chromium.org, Dec 26 2016

May I know which headset did you test with?

Some headsets not supporting AVRCP still have volume button to adjust the gain, but they won't sync volume back to host system.
Status: Archived (was: Assigned)

Comment 8 by ketakid@google.com, Mar 18 2017

Labels: Pri-3
Status: Available (was: Archived)
Activating. Please assign to the right owner and the appropriate priority.
Project Member

Comment 9 by sheriffbot@chromium.org, Apr 13 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Archived (was: Untriaged)
Archiving this. please file separate bug for AVRCP problem on specific headset.

Sign in to add a comment