1. Title : Playing music in Bluetooth model, answer to an incoming phone and then hand up after a while,the music pause after the phone. 2. Precondition : Have music files/songs in device, Set the device into Bluetooth mode 3. Tester's Action : Launch music app ->select any song and play->when we get a incoming call->answer to the call and music paused->hand up the call->the music pauses to play . 4.Expected Result:the music continue to play after the call

Code analysis as follows: Connect to Bluetooth Headset and play a song in the phone 1 when the call comes in: Case'mozinterruptbegin': This.playStatus = INTERRUPT_BEGIN; Trigger the mozinterruptbegin event, modify the value of playStatus. 2.After we press the pick up button: Enter the pause function, and modify the value of this._statusBeforeSCO: This._statusBeforeSCO = PlayerView.playStatus; At this time this._statusBeforeSCO==mozinterruptbegin. 3.The hang up button is pressed: Enter the playpause function: If (this._statusBeforeSCO = = = PLAYSTATUS_PLAYING) PlayerView.play (); Else PlayerView.pause (); According to the code execution in process of 2,(this._statusBeforeSCO = = = PLAYSTATUS_PLAYING) returns false,then it go to PlayerView.pause (), the music pauses.

I think Dominic should be familiar with this.

Adding qawanted to see if we can reproduce and check for regression

Which device was this reproduced with?

Able to repro on Buri 1.4 mozilla RIL Build ID: 20140520000201 Gecko: https://hg.mozilla.org/releases/mozilla-b2g30_v1_4/rev/95be84248033 Gaia: 17b102ee8d9a724b62285547cc5f1c5d30bfb01c Platform Version: 30.0 Firmware Version: V1.2-device.cfg

The same as bug 1002897.

If the patch in bug 1002897 is work in 1.4?

(In reply to James Zhang from comment #6) > The same as bug 1002897. No it definitely is not. That's for low end devices only. Pretty sure there's a bug already on file for this, but I can't find it right now. IIRC, I don't think this was a regression to my understanding, but the 1.3 testing will confirm this or not.

(In reply to Jason Smith [:jsmith] from comment #8) > (In reply to James Zhang from comment #6) > > The same as bug 1002897. > > No it definitely is not. That's for low end devices only. > > Pretty sure there's a bug already on file for this, but I can't find it > right now. IIRC, I don't think this was a regression to my understanding, > but the 1.3 testing will confirm this or not. dear Jason: Would you please provide some clues for the already on file bug?

As I said, I know it's on file, but I can't find it at the moment.

(In reply to Jason Smith [:jsmith] from comment #10) > As I said, I know it's on file, but I can't find it at the moment. this one? https://bugzilla.mozilla.org/show_bug.cgi?id=1006413 (I have also seen variations of this issue in different bugs)

Yeah that's definitely one of them.

Root cause found and will fix in bug 1006413.