Pooja Reporter
	Description • 10 years ago

Audio leaks to Speaker when doing device switch from BT to Speaker and when disconnect the BT

Steps To Reproduce:
--------------------
 1. Copy clips to DUT SD card 
 2. Pair a BT headset to DUT
 3. Start playing a clip 
 4. Disconnect the BT headset. Audio should be routing through speaker
 5. observe the issue that Audio leaking to Speaker

Excepted Result:
Audio should not leak to any device when DS operations doing

Actual Result:
Audio is leaking to Speaker when doing device switch from BT

Target QRD 8x26 V2.0 KK

	Pooja Reporter
	Comment 1 • 10 years ago

[Blocking Requested - why for this release]:

	Mike Habicher [:mikeh] (high bugzilla latency)
	Comment 2 • 10 years ago

Pooja, can you please clarify what you mean by "audio is leaking to speaker"? What do you mean by leaking? From your STR, it sounds like the music is supposed to be coming from the speaker.

Squib, can you take a quick look at this and determine if this is an app or a system issue?

	Jason Smith [:jsmith]
	Comment 3 • 10 years ago

Marking qawanted to see what behavior we see on the Flame 2.0 device

	Jim Porter (:squib)
	Comment 4 • 10 years ago

Sorry, I'm not even sure what the bug is here. From the description, it sounds like we're doing exactly what we should be doing.

	Mike Habicher [:mikeh] (high bugzilla latency)
	Comment 5 • 10 years ago

Dominic, I just noticed you're working on bug 1038162 -- can you take a quick look at this one as well? Hopefully we can get clarification on the symptoms soon.

	bhavana bajaj [:bajaj]
	Comment 6 • 10 years ago

Still waiting for more clarification here from CAF before making blocking call here, after which we can try to see if this reproduces on Flame which is 8x10

	bhargavg1
	Comment 7 • 10 years ago

(In reply to bhavana bajaj [:bajaj] from comment #6)
> Still waiting for more clarification here from CAF before making blocking
> call here, after which we can try to see if this reproduces on Flame which
> is 8x10

While doing A2DP streaming if disconnection is initiated from the BT headset side, the audio on the phone would pause. Before the actual pause happens see that there is a slight leak (you can hear the audio being played) for a 1 sec or less on the device speaker.

Let me know if you need any further info

	No-Jun Park [:njpark]
	Comment 8 • 10 years ago

Reproduced by doing the following:
Go to Settings, pair a bluetooth speaker
Go to music app, start playing a music file
Go back to settings -> bluetooth, long tap the currently connected device, and select disconnect

The music will briefly play (1/2 seconds) right after disconnecting from the BT device

It was reproduced in following configuration:
Flame V2.0 KK (v165) with 319MB of RAM
Gaia      a51633e29a7826b6bf07cb1c5ad81b3217b9820a
Gecko     8f121f8fa5fa1a3e82967f91e2afe337465fc593
BuildID   20140826105138
Version   32.0
ro.build.version.incremental=18
ro.build.date=Thu Aug 14 19:29:46 CST 2014

	Mike Habicher [:mikeh] (high bugzilla latency)
	Comment 9 • 10 years ago

Based on comment 8, I think this is a paper-cut, not a blocker. Especially since only selecting Disconnect in Settings causes the problem. Turning Bluetooth off does not.

	Jason Smith [:jsmith]
	Comment 10 • 10 years ago

(In reply to No-Jun Park [:njpark] from comment #8)
> Reproduced by doing the following:
> Go to Settings, pair a bluetooth speaker
> Go to music app, start playing a music file
> Go back to settings -> bluetooth, long tap the currently connected device,
> and select disconnect
> 
> The music will briefly play (1/2 seconds) right after disconnecting from the
> BT device
> 
> It was reproduced in following configuration:
> Flame V2.0 KK (v165) with 319MB of RAM
> Gaia      a51633e29a7826b6bf07cb1c5ad81b3217b9820a
> Gecko     8f121f8fa5fa1a3e82967f91e2afe337465fc593
> BuildID   20140826105138
> Version   32.0
> ro.build.version.incremental=18
> ro.build.date=Thu Aug 14 19:29:46 CST 2014

We probably should also branch check here to see if this happens on 1.4.

	bhavana bajaj [:bajaj]
	Comment 11 • 10 years ago

Given comment #8, comment #9, pooja if this is what you are observing in your testing as well, I think this is a paper cut but not a release blocking issue.

	bhargavg1
	Comment 12 • 10 years ago

(In reply to bhavana bajaj [:bajaj] from comment #11)
> Given comment #8, comment #9, pooja if this is what you are observing in
> your testing as well, I think this is a paper cut but not a release blocking
> issue.

Agreed that we see a leak for only fraction of sec, can we look as to why we see the leak.

	Chris Kreinbring [:CKreinbring]
	Comment 13 • 10 years ago

The bug repros on Flame 2.0, Flame 1.4 and Open C 2.0
Actual result: When the Bluetooth audio device is disconnected while a song is playing, the music can be heard from the device speaker for a split second.

Flame 2.0
BuildID: 20140827071131
Gaia: d72f8ad53448aed577c01ff6e11d958463f261e7
Gecko: 6f28fbf3ec07
Platform Version: 32.0
Firmware Version: V123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Flame 1.4
BuildID: 20140827090228
Gaia: 05653cb12d324649687dad3eeb2ea373a2ad84d4
Gecko: baf01c5965ef
Platform Version: 30.0
Firmware Version: V123
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

Open C 2.0
BuildID: 20140827071131
Gaia: d72f8ad53448aed577c01ff6e11d958463f261e7
Gecko: 6f28fbf3ec07
Platform Version: 32.0
Firmware Version: P821A10v1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

--------------------------------------------------------------------------------------------------------

The bug does not repro on Flame 2.1
Actual result: When the Bluetooth audio device is disconnected while a song is playing, nothing is heard when the device is disconnected.

BuildID: 20140827080726
Gaia: 6e804a42ab90f4251c7fe8c68731dc1c6abd8006
Gecko: 85135c5c6ba8
Platform Version: 34.0a1
Firmware Version: V123
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

	Pooja Reporter
	Comment 14 • 10 years ago

(In reply to bhavana bajaj [:bajaj] from comment #11)
> Given comment #8, comment #9, pooja if this is what you are observing in
> your testing as well, I think this is a paper cut but not a release blocking
> issue.

Yes, Agree Bhavana that Audio doesn't leak if we Turn BT off instead of disconnecting the connected headset.

But Is Audio leak is later case is permissible?

	bhavana bajaj [:bajaj]
	Comment 15 • 10 years ago

(In reply to Pooja from comment #14)
> (In reply to bhavana bajaj [:bajaj] from comment #11)
> > Given comment #8, comment #9, pooja if this is what you are observing in
> > your testing as well, I think this is a paper cut but not a release blocking
> > issue.
> 
> Yes, Agree Bhavana that Audio doesn't leak if we Turn BT off instead of
> disconnecting the connected headset.
> 
> But Is Audio leak is later case is permissible?

yep, but QA testing shows this happens for a fraction of a second only which is too minor to block a release on and keeping in mind we are not seeing this in 2.1

	bhargavg1
	Comment 16 • 10 years ago

(In reply to bhavana bajaj [:bajaj] from comment #15)
> (In reply to Pooja from comment #14)
> > (In reply to bhavana bajaj [:bajaj] from comment #11)
> > > Given comment #8, comment #9, pooja if this is what you are observing in
> > > your testing as well, I think this is a paper cut but not a release blocking
> > > issue.
> > 
> > Yes, Agree Bhavana that Audio doesn't leak if we Turn BT off instead of
> > disconnecting the connected headset.
> > 
> > But Is Audio leak is later case is permissible?
> 
> yep, but QA testing shows this happens for a fraction of a second only which
> is too minor to block a release on and keeping in mind we are not seeing
> this in 2.1

Hope we dont break again in v2.1

	Inder
	Comment 17 • 10 years ago

Bhargav -- can you please check if this is an issue on 2.1 as well? Based on Moz QA feedback it looks like it's not reproducible on 2.1.

	Hema Koka [:hema]
	Comment 18 • 10 years ago

This probably belongs to Bluetooth or Audiochannel component. 

Bhargav's needinfo was cancelled and linked to general bluetooth issues with 2.1, not clear if you are able to reproduce this particular issue on 2.1 (it is not reproducible on flame 2.1 based on moz qa testing). Please confirm.

Thanks
Hema

	bhargavg1
	Comment 19 • 10 years ago

(In reply to Hema Koka [:hema] from comment #18
> 
> Bhargav's needinfo was cancelled and linked to general bluetooth issues with
> 2.1, not clear if you are able to reproduce this particular issue on 2.1 (it
> is not reproducible on flame 2.1 based on moz qa testing). Please confirm.
> 
> Thanks
> Hema

Currently BT testing is blocked and is tracked by Bug 1066235

	Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)
	Comment 20 • 10 years ago

Keep me for further clarification

	Star Cheng [:scheng]
	Comment 21 • 10 years ago

It can not duplicate STR in Music app. And I can duplicate it in Video App. Video app should pause while disconnecting BT headset.

	Star Cheng [:scheng]
	Comment 22 • 10 years ago

(In reply to Star Cheng [:scheng] from comment #21)
> It can not duplicate STR in Music app. And I can duplicate it in Video App.
> Video app should pause while disconnecting BT headset.

Need info to John. 

Hi, John

Do you have any suggestion about the behavior : to pause the video while disconnecting BT headset?

	John Hu [:johnhu][:johu][:醬糊小弟]
	Comment 23 • 10 years ago

We don't pause the video while disconnecting BT and we don't listen the event of BT connection. The current implementation only listens wired headset change[1].

And why 2.1 doesn't be affected? We don't implement it in the past. So, it should be affected in v2.1.

As per offline discussion with Dominic Kuo, this issue can leverage the existing shared/js/media/remote_controls.js and implement "pause" command to support that.

I am fully loaded currently. I may not have any capacity to implement it, now.

[1] https://github.com/mozilla-b2g/gaia/blob/99bb2326e4282721ac4c1fe82cd3e55c7ed49ceb/apps/video/js/video.js#L171-L175

	bhargavg1
	Comment 24 • 10 years ago

(In reply to Hema Koka [:hema] from comment #18)
> This probably belongs to Bluetooth or Audiochannel component. 
> 
> Bhargav's needinfo was cancelled and linked to general bluetooth issues with
> 2.1, not clear if you are able to reproduce this particular issue on 2.1 (it
> is not reproducible on flame 2.1 based on moz qa testing). Please confirm.
> 
> Thanks
> Hema

Dont see the issue on v2.1