Closed Bug 975230 Opened 12 years ago Closed 12 years ago

[Sora][FM][settings]FM would not pause while actived sound settings

Categories

(Firefox OS Graveyard :: Gaia::Settings, defect, P1)

defect

Tracking

(blocking-b2g:1.3+)

RESOLVED DUPLICATE of bug 958470
blocking-b2g 1.3+

People

(Reporter: sync-1, Unassigned)

References

Details

(Keywords: regression)

Firefox OS v1.3 Mozilla build ID: 20140208004002 DEFECT DESCRIPTION: FM would not pause while actived sound settings REPRODUCING PROCEDURES: 1.Insert headset; 2.Launch FM and select one channel to play; 3.Listening FM in background; 4.Settings->sound,listen ringer or alert ringtone.Ringtone and FM can play simultaneously;->KO EXPECTED BEHAVIOUR: When activated sound settings,FM should pause; ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: REPRODUCING RATE:5/5 For FT PR, Please list reference mobile's behavior:
Does this reproduce on 1.1 Buri?
Component: Gaia::FMRadio → AudioChannel
Flags: needinfo?(sync-1)
(In reply to Jason Smith [:jsmith] from comment #1) > Does this reproduce on 1.1 Buri? Yes. On 1.1 Buri when activated sound settings,FM have mute.
(In reply to Ray REN from comment #2) > (In reply to Jason Smith [:jsmith] from comment #1) > > Does this reproduce on 1.1 Buri? > > Yes. On 1.1 Buri when activated sound settings,FM have mute. Wait - do you mean that this works fine on 1.1 then?
(In reply to Jason Smith [:jsmith] from comment #3) > (In reply to Ray REN from comment #2) > > (In reply to Jason Smith [:jsmith] from comment #1) > > > Does this reproduce on 1.1 Buri? > > > > Yes. On 1.1 Buri when activated sound settings,FM have mute. > > Wait - do you mean that this works fine on 1.1 then? Yes, it works fine on 1.1
Bug 958470 should also fix this.
Depends on: 958470
Flags: needinfo?(sync-1)
Keywords: regression
(In reply to Dominic Kuo [:dkuo] from comment #5) > Bug 958470 should also fix this. I think this bug should be fixed independently of that bug - keep that bug's focus on the Ringtones app specifically.
No longer depends on: 958470
The fact that this is happening in multiple places makes me think that we're fundamentally not doing audio channels correctly.
blocking-b2g: --- → 1.3?
(In reply to Jason Smith [:jsmith] from comment #6) > (In reply to Dominic Kuo [:dkuo] from comment #5) > > Bug 958470 should also fix this. > > I think this bug should be fixed independently of that bug - keep that bug's > focus on the Ringtones app specifically. Before 1.2, that's 1.1, the capability of setting the ringtone was a sub-module of the settings app, and because the audio channel type was correctly set at that time, 1.1 didn't has this issue. In 1.2, djf had implemented a new app called "ringtones" in bug 905856 to support setting forward lock content as the ringtone, from 1.2 we started to pick the ringtone from the ringtones app. The ringtone's logic in settings app was removed and added to the new ringtones app, the audio channel type was probably the missing part we forgot to move then caused this issue, so that's why I filed bug 958470 and tried to fix it.
QA Wanted to confirm this in the latest 1.3 build.
blocking-b2g: 1.3? → ---
In response to Comment 10 Jason Smith [:jsmith] 2014-02-24 20:46:40 PST QA Wanted to confirm this in the latest 1.3 build. Confirmed this issue occurs on the latest 1.3 build with below Environmental Variables. I am able to play and hear FM Radio, go to Settings and select a ringtone or alert, and hear both FM Radio and the ringtone/alert at the same time. Environmental Variables: Device: Buri 1.3 MOZ BuildID: 20140225004004 Gaia: 6e883bde818d4d53aef7b5b075b4b34267918360 Gecko: e597280f9300 Version: 28.0 Base Image: v1.2-device.cfg
Keywords: qawanted
QA Contact: mclemmons
blocking-b2g: --- → 1.3?
The issue started reproducing on the 9/20/2013 1.3 build. On this build I am able to play and hear FM Radio, go to Settings and select a ringtone or alert, and hear both FM Radio and the ringtone/alert at the same time. The following regression window was found: Last Working Environmental Variables: Device: Buri 1.3 MOZ BuildID: 20130919040201 Gaia: 0dedb5b3789afc638a0c7c67652937fcb30e77d2 Gecko: 803189f35921 Version: 27.0a1 Base Image: v1.2-device.cfg First Broken Environmental Variables: Device: Buri 1.3 MOZ BuildID: 20130920040201 Gaia: 78a3e2509b979bd226f01f557bdf229fd3faa42e Gecko: 59beb1868522 Version: 27.0a1 Base Image: v1.2-device.cfg
This is missing a last gaia working/first gecko busted & vice versa analysis.
Keywords: qawanted
blocking-b2g: 1.3? → 1.3+
(In reply to Jason Smith [:jsmith] from comment #13) > This is missing a last gaia working/first gecko busted & vice versa analysis. Regression Window Last Working Environmental Variables: Device: Buri 1.3 MOZ BuildID: 20130919040201 Gaia: 0dedb5b3789afc638a0c7c67652937fcb30e77d2 Gecko: 803189f35921 Version: 27.0a1 Base Image: v1.2-device.cfg First Broken Environmental Variables: Device: Buri 1.3 MOZ BuildID: 20130920040201 Gaia: 78a3e2509b979bd226f01f557bdf229fd3faa42e Gecko: 59beb1868522 Version: 27.0a1 Base Image: v1.2-device.cfg First Broken Gaia/Last Working Gecko - issue reproduces Gaia: 78a3e2509b979bd226f01f557bdf229fd3faa42e Gecko: 803189f35921 Last Working Gaia/First Broken Gecko: - issue does not reproduce Gaia: 0dedb5b3789afc638a0c7c67652937fcb30e77d2 Gecko: 59beb1868522 push log: https://github.com/mozilla-b2g/gaia/compare/0dedb5b3789afc638a0c7c67652937fcb30e77d2 ...78a3e2509b979bd226f01f557bdf229fd3faa42e
The only patch that seems plausible in the regression range is bug 905856, given that I see modifications in that patch in sound.js file. David - Any ideas?
Blocks: 905856
Component: AudioChannel → Gaia::Settings
Flags: needinfo?(dflanagan)
Jason, My idea is to listen to Dominic (comment #9), since he is the only one on this bug who knows what they are talking about. Look at step 4 of the STR: this bug is about ringtones. Dominic is fixing a bug about ringtones. Dominic and Jim have a plan to fix this that got pushed off to 1.5. A 1.3+ bug is just what we need to get it fixed sooner. Changing the component back to AudioChannel, and setting needinfo for Dominic and Jim to find out if either of them can get on this ASAP.
Component: Gaia::Settings → AudioChannel
Flags: needinfo?(squibblyflabbetydoo)
Flags: needinfo?(dkuo)
Flags: needinfo?(dflanagan)
David: We'll probably just need to do the same sort of thing for this as you did for music and setringtone (just kill me now). Maybe we can get around this by making the ringtone app play on a higher-priority channel, but I have a vague recollection that that doesn't actually save us. Dominic probably knows more about this. Either way, I can implement this once I know what I'm implementing. :)
Flags: needinfo?(squibblyflabbetydoo)
Clearly I read these bugs in the wrong order. Bug 958470 has much more useful info, and we should probably just dupe these. (Aside: maybe duping an issue before we're sure that one actually fixes the other is frowned upon because it makes tracking harder, but this is a perfect example of why we should do it anyway: it's really hard to track which bug is the one we should be discussing technical details in.)
This is not a gecko bug - comment 14 already provides hard evidence that this is triggered in Gaia, not Gecko. There's also no evidence in the push log of anything in the System app triggering this. Back over to the Settings.
Component: AudioChannel → Gaia::Settings
(In reply to Jim Porter (:squib) from comment #19) > Clearly I read these bugs in the wrong order. Bug 958470 has much more > useful info, and we should probably just dupe these. We really should keep this bug open separate from bug 958470 - bug 958470 is focusing on a Web Audio solution to the problem, which is too risky to take into 1.3. We need a safe fix here for 1.3.
I'll dupe this per discussion with Jim & + the dupe.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Flags: needinfo?(dkuo)
You need to log in before you can comment on or make changes to this bug.