1083293 - DUT volume is not changing while changing the BT volume on BT headset device

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Bluetooth, defect)

Description

[bhargavg1]

teps to Reproduce:
-------------------
1. Copy clips to sdcard
2. Start playback by launching the music app
3. Pair and connect BT headset, playback routing to BT headset when BT connected
4. Verify DUT volume While playback is on BT
5. Now change the BT headset volume and verify the DUT volume
5. DUT volume doesn't change accordingly

Expected result: DUT volume should change according to BT headset volume 

Actual Result: DUT volume is not changing while changing the BT volume on BT headset device

Note: The same issue verified and reproduced with Plantronics and SONY MW600 BT headsets as well

BT Headset Used: Sony DR-BTN200

Comment 1

[bhargavg1]

[Blocking Requested - why for this release]:

Comment 2

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

Please provide snoop log. Thanks.

Comment 3

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

(In reply to bhargavg1 from comment #0)
> teps to Reproduce:
> -------------------
> 1. Copy clips to sdcard
> 2. Start playback by launching the music app
> 3. Pair and connect BT headset, playback routing to BT headset when BT
> connected
> 4. Verify DUT volume While playback is on BT
> 5. Now change the BT headset volume and verify the DUT volume
> 5. DUT volume doesn't change accordingly
> 
> Expected result: DUT volume should change according to BT headset volume 
> 
> Actual Result: DUT volume is not changing while changing the BT volume on BT
> headset device
> 
> Note: The same issue verified and reproduced with Plantronics and SONY MW600
> BT headsets as well
> 
> BT Headset Used: Sony DR-BTN200

Hi,
What's the expected behavior here?
I assume you expected the volume of music (normal mode, PCM volume) get changed, or in-call (BT SCO) volume?

Comment 4

[howie [:howie]]

Hi bhargav, can you provide the reason why you nominate this as a blocker? thanks

Comment 5

[vasanth]

Attachment: btsnoop_hci_enabled.log

While collecting snoop logs,
1. BT headset is paired with DUT.
2. Did some play, pause operations in Music app
3. Then changed volume by pressing BT headset vol up/down buttons
4. We can notice that volume is changed in BT headset but it is not updating device's volume level.

Comment 6

[Andrew Overholt [:overholt]]

Blocking 2.1 FC and CC = 2.1+.

Comment 7

[bhavana bajaj [:bajaj]]

shawn, does comment #5 help or you need more info here?

Comment 8

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

(In reply to vasanth from comment #5)
> Created attachment 8505996 [details]
> btsnoop_hci_enabled.log
> 
> While collecting snoop logs,
> 1. BT headset is paired with DUT.
> 2. Did some play, pause operations in Music app
> 3. Then changed volume by pressing BT headset vol up/down buttons
> 4. We can notice that volume is changed in BT headset but it is not updating
> device's volume level.
Although this bug marked as 2.1+, I still want to clarify a few things here.
There two ways to sync volume:
1. HFP profile AT command "+VGS", this changes "BT SCO volume, which is in-call bluetooth volume"
2. AVRCP 1.4 Volume sync (absolute volume feature), this does not support on v2.1.

From the log, I did not see any "+VGS command" or AVRCP 1.4 absolute volume sync.
The log shows the accessory supports AVRCP 1.3 only.

There are many headsets only support their local volume change but not AVRCP absolute volume.
Can you help to cross reference using other Android phones with the same Bluetooth headset?

Comment 9

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

Note: We're still clarifying this bug is related to headset design or function failure. We need more input for various headsets design.

Comment 10

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

(In reply to Shawn Huang [:shawnjohnjr] from comment #8)
> (In reply to vasanth from comment #5)
> Although this bug marked as 2.1+, I still want to clarify a few things here.
> There two ways to sync volume:
> 1. HFP profile AT command "+VGS", this changes "BT SCO volume, which is
> in-call bluetooth volume"
I can confirm '+VGS (Gain of Speaker)' works, BT SCO volume will be changed.
> 2. AVRCP 1.4 Volume sync (absolute volume feature), this does not support on
> v2.1.
I doubt many Bluetooth headsets actually support this, and I don't intend to add this feature for v2.1.
Given this fact, I really don't think this is a blocker. Let's wait for feedback Comment 8.

Comment 11

[vasanth]

(In reply to Shawn Huang [:shawnjohnjr] from comment #8)
> Can you help to cross reference using other Android phones with the same
> Bluetooth headset?

Hi Shawn,
That specific headset doesn't update volume in Android as well whereas some other headsets do.
We tried volume change only during audio playback so its *not* related to BT SCO volume.

As you mentioned, AVRCP 1.4 Volume sync is not supported yet in v2.1,
not sure we should continue to look into this?

Comment 12

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

(In reply to vasanth from comment #11)
> (In reply to Shawn Huang [:shawnjohnjr] from comment #8)
> > Can you help to cross reference using other Android phones with the same
> > Bluetooth headset?
> 
> Hi Shawn,
> That specific headset doesn't update volume in Android as well whereas some
> other headsets do.
> We tried volume change only during audio playback so its *not* related to BT
> SCO volume.
It depends on how bluetooth headsets design, some headsets send +VGS even during audio playback.
> As you mentioned, AVRCP 1.4 Volume sync is not supported yet in v2.1,
> not sure we should continue to look into this?
I don't think we need to continue to look into this. And the headsets you tested may not support AVRCP 1.4 absolute volume feature. Can we close it?

Comment 13

[vasanth]

(In reply to Shawn Huang [:shawnjohnjr] from comment #12)
> It depends on how bluetooth headsets design, some headsets send +VGS even
> during audio playback.
Got it. Thanks!

> I don't think we need to continue to look into this. And the headsets you
> tested may not support AVRCP 1.4 absolute volume feature. Can we close it?
Sure.