Closed Bug 993271 Opened 12 years ago Closed 8 years ago

Music is not resumed while playing video

Categories

(Firefox OS Graveyard :: AudioChannel, defect)

defect
Not set
normal

Tracking

(b2g-v2.1 affected, b2g-v2.2 affected)

RESOLVED WONTFIX
Tracking Status
b2g-v2.1 --- affected
b2g-v2.2 --- affected

People

(Reporter: ranjith253, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.154 Safari/537.36 Steps to reproduce: Gaia Version : V1.4 1. Open music app 2. play music & pause music 3. Go to homescreen 4. Enter video app & play video 5. while playing video, activate notification bar. ( we can see BGM music bar. ) 6. play music Actual results: Music is not played and BGM music bar is disappeared. Expected results: BGM music bar is should stay in notification tray & music has to be played .
There is a ux related discussion in bug 973156 and I think if we want to fix this,we also need ux to decide what's the expected behaviour here. And the issue is because the audio competing policy, please see that section in https://wiki.mozilla.org/WebAPI/AudioChannels - [2] If there is any other content channel starting to play in foreground or background then current content channel in playing will be muted or paused. Both video and music are content channels.
See Also: → 973156
Hi Dominic, As you mentioned, as per the audio competing policy we can play two audio tracks simultaneously *only* if all are coming from the FG app. We feel that this restriction is causing the problem here. As per the discussion, we have analyzed this issue and thought about fixes/workarounds for this. 1. Gaia only change (as a *workaround*): Try using audio-channel-changed events in system app to monitor channel changing and to hide the music widget whenever 'content' channel is used by other applications. This may not be possible as the channel change event is triggered before any media events like play or pause. 2. Gecko change: Send mozinterruptbegin (or any new event only for this case) during paused state also. 3. Audio competing policy change: allow same priority channels to play even they are from FG or BG application. please let us know your thoughts. setting ni? to dominic, for his points.
Flags: needinfo?(dkuo)
I think for the current state I would suggest we go option 1. Option 2 and 3 needs gecko changes, which might cause any regression we didn't expect, and as you know, there are known issues on the audio channel, we hope to have a gaia audio channel service(bug 961967) that manages the audio channel things, especially on the competing problems, so option 1 is the good candidate if we want this fixed soon.
Flags: needinfo?(dkuo)
This issue can be reproduced on Flame 2.2&3.0,and there is another problem,when I tap the play button on utility tray during video is playing,the music will play for about 2 seconds. After then,music stop playing and music controler disappear from utility tray. [Testing Steps]: 1.Launch Music 2.Play a song->then tap pause to pause the song 3.Press Home 4.Tap Video and play 5.Drag down notification bar 6.Tap Play button [Actual Result]: 6.The music play for 1~2s,after then the music controler disappear. [Reproduction build]: Flame 2.2: Affected Build ID 20150402002500 Gaia Revision 1ceca464053dee4a8bf10ea5abeef724d68c2ff2 Gaia Date 2015-04-01 09:49:30 Gecko Revision https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/427b4da96714 Gecko Version 37.0 Device Name flame Firmware(Release) 4.4.2 Flame 3.0: Affected Build ID 20150402160202 Gaia Revision 62042ffcc8c6cca0f51ad23f5c2b979fc153b5a7 Gaia Date 2015-04-02 16:01:42 Gecko Revision https://hg.mozilla.org/mozilla-central/rev/513265a4cbc2 Gecko Version 40.0a1 Device Name flame Firmware(Release) 4.4.2 [6.Reproduction Frequency]: Always Recurrence,5/5
This is an Audio Channel issue (and maybe a Music Controls issue). Adjusting component.
Component: Gaia::Music → AudioChannel
Firefox OS is not being worked on
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.