Closed Bug 1222185 Opened 10 years ago Closed 8 years ago

music app audio playback gets interrupted

Categories

(Firefox OS Graveyard :: Gaia::System::Audio Mgmt, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jovan.gerodetti, Unassigned)

Details

(Keywords: foxfood, Whiteboard: [bzlite])

User-Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0 When unlocking the device, switching to an other app or receiving a new notification while the screen is of, many times the audio playback just stops. Also the control "widgets" in the notification tray and on the lockscreen disapear. As soon as I return back to the music app the audio playback continues.
QA Whiteboard: [foxfood-triage]
Component: Gaia::Feedback → Gaia::Music
This isn't a music bug. It's arguably an audio channel issue, or more likely, whatever component is in charge of that mind-boggingly annoying text-to-speech whenever you switch apps.
Component: Gaia::Music → AudioChannel
Not sure if this is happening on 2.5 or not, but this needs to block. Ideally, the solution is to get rid of the text-to-speech because I hate it.
Status: UNCONFIRMED → NEW
blocking-b2g: --- → 2.6?
Ever confirmed: true
I don't hear any text to speech, but I experiencing this issue on 2.5.
[Blocking Requested - why for this release]: This is happening in 2.5 according to comment 3 (hopefully these are the same issue in 2.5 and 2.6). It's also extremely bad, since it effectively makes the music app unusable.
blocking-b2g: 2.6? → 2.5?
Component: AudioChannel → Gaia::VoiceControl
Component: Gaia::VoiceControl → AudioChannel
Hi, Evan, It seems related with the audio competing policy. Could you help to take a look?
Component: AudioChannel → Gaia::System::Audio Mgmt
Flags: needinfo?(evan)
Hi Jovan, I cannot reproduce the issue in this build[1]. Music app can continue to play when unlocking the device, switching to an other app or receiving a new notification. But screen unlock sound will stop music, we're fixing it in Bug 1214908. Could you provide clear STR to help me reproduce the bug? Thanks. [1]: Build ID 20151111150236 Gaia Revision 86c5b466fc8c096a66aacf158859a6a1c8c7c850 Gaia Date 2015-11-12 09:48:01 Gecko Revision https://hg.mozilla.org/mozilla-central/rev/84a7cf29f4f14c9b359db2f7f19c0abd6a8e178e Gecko Version 45.0a1 Device Name flame Firmware(Release) 4.4.2 Firmware(Incremental) 65 Firmware Date Mon Dec 15 18:51:29 CST 2014 Bootloader L1TC000118D0
Flags: needinfo?(evan)
Flags: needinfo?(titannanomail)
blocking-b2g: 2.5? → ---
Hi Evan, I still have a outdated build [1]. After you mentioned the issue with the unlocking sound, I tried to reproduce the issue again. As far as I see, the problem only occurs if the app I'm switching to also tired to play some kind of audio. The problem with receiving a notification I think was caused by Bug 1222059. 1. I had Telegram Messenger in the foreground. 2. I locked my device. 3. I received a new message and the application triggered a new notification. 4. The notification instantly turned on the screen, due to Bug 1222059 the app thought it's in the foreground and also played a sound. 5. Music app playback got interrupted. [1] Serial: f30eccae (State: device) Build ID 20151109004552 Gaia Revision cf646c52bb947af28329b0a100df91d1b1f2a907 Gaia Date 2015-11-09 02:55:50 Gecko Revision https://hg.mozilla.org/releases/mozilla-b2g44_v2_5/rev/4eafef5b80f8985c94c4a067f130d37513e1a581 Gecko Version 44.0a2 Device Name flame Firmware(Release) 4.4.2 Firmware(Incremental) eng.cltbld.20150527.043015 Firmware Date Wed May 27 04:30:24 EDT 2015 Bootloader L1TC000118D0
Flags: needinfo?(titannanomail)
(In reply to Jovan Gerodetti from comment #7) > Hi Evan, > > I still have a outdated build [1]. > After you mentioned the issue with the unlocking sound, I tried to reproduce > the issue again. > As far as I see, the problem only occurs if the app I'm switching to also > tired to play some kind of audio. > Hi Jovan, I follow the below steps to reproduce the bug. But I use pre-installed Messages app, not Telegram Messenger. > The problem with receiving a notification I think was caused by Bug 1222059. > 1. I had Telegram Messenger in the foreground. > 2. I locked my device. > 3. I received a new message and the application triggered a new > notification. > 4. The notification instantly turned on the screen, due to Bug 1222059 the > app thought it's in the foreground and also played a sound. > 5. Music app playback got interrupted. In the step 5, we will turn the Music app playback's volume down and then turn it's volume as normal. That is not interruption. That is fade-in and fade-out effect we defined in the spec[1]. So this is not a bug. It's a feature. [1]: https://bug1068219.bmoattachments.org/attachment.cgi?id=8579177#12 > > > [1] > Serial: f30eccae (State: device) > Build ID 20151109004552 > Gaia Revision cf646c52bb947af28329b0a100df91d1b1f2a907 > Gaia Date 2015-11-09 02:55:50 > Gecko Revision > https://hg.mozilla.org/releases/mozilla-b2g44_v2_5/rev/ > 4eafef5b80f8985c94c4a067f130d37513e1a581 > Gecko Version 44.0a2 > Device Name flame > Firmware(Release) 4.4.2 > Firmware(Incremental) eng.cltbld.20150527.043015 > Firmware Date Wed May 27 04:30:24 EDT 2015 > Bootloader L1TC000118D0
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.