Closed Bug 952003 Opened 11 years ago Closed 7 years ago

Resuming speaker mode in background fm radio app after an incoming call was received & denied isn't immediate

Categories

(Firefox OS Graveyard :: Gaia::FMRadio, defect, P3)

ARM
Gonk (Firefox OS)
defect

Tracking

(b2g-v2.0 affected)

RESOLVED WONTFIX
Tracking Status
b2g-v2.0 --- affected

People

(Reporter: jsmith, Unassigned)

References

Details

(Keywords: perf, Whiteboard: [c= u= p= s=], [2.0-flame-test-run-3])

Build - 12/18/2013 Leo 1.4 STR 1. Insert headphones into your device 2. Open the FM Radio & start playing a station with sound & enable speaker mode 3. Put FM Radio in background 4. Call the phone with speaker mode active 5. When the incoming call appears, deny the call Expected Speaker mode in the FM Radio should resume playback of the FM Radio. Actual Nothing happens for a few seconds. Then, FM Radio will resume playback of the sound.
Blocks: 854753
Whiteboard: [ft:multimedia-platform]
Note - it takes about 5 seconds to resume, which is bit too long.
blocking-b2g: --- → 1.3?
Keywords: perf
Hi Pin, Is this the resume time of turn on FMRadio?
Flags: needinfo?(pzhang)
Apparently this reproduces outside of speaker mode.
No longer blocks: 854753
blocking-b2g: 1.3? → ---
Component: DOM: Device Interfaces → Gaia::FMRadio
Product: Core → Firefox OS
Whiteboard: [ft:multimedia-platform]
Version: 29 Branch → unspecified
(In reply to Randy Lin [:rlin] from comment #2) > Hi Pin, > Is this the resume time of turn on FMRadio? I don't think FM radio could be paused/resumed, only could be turned on and off. Everytime the FM radio is turned on will take about 3-4 seconds. Is "turning off the playing-in-background FM radio when a call is coming and turning it back on when the incoming call is denied" a feature be designed? If not, I'm afraid it's a bug we need to find out.
Flags: needinfo?(pzhang)
(In reply to Pin Zhang [:pzhang] from comment #4) > (In reply to Randy Lin [:rlin] from comment #2) > > Hi Pin, > > Is this the resume time of turn on FMRadio? > > I don't think FM radio could be paused/resumed, only could be turned on and > off. Everytime the FM radio is turned on will take about 3-4 seconds. Is > "turning off the playing-in-background FM radio when a call is coming and > turning it back on when the incoming call is denied" a feature be designed? > If not, I'm afraid it's a bug we need to find out. Why can't we pause & resume specifically? Is this a limitation in the design of the FM Radio API?
(In reply to Jason Smith [:jsmith] from comment #5) > (In reply to Pin Zhang [:pzhang] from comment #4) > > (In reply to Randy Lin [:rlin] from comment #2) > > > Hi Pin, > > > Is this the resume time of turn on FMRadio? > > > > I don't think FM radio could be paused/resumed, only could be turned on and > > off. Everytime the FM radio is turned on will take about 3-4 seconds. Is > > "turning off the playing-in-background FM radio when a call is coming and > > turning it back on when the incoming call is denied" a feature be designed? > > If not, I'm afraid it's a bug we need to find out. > > Why can't we pause & resume specifically? Is this a limitation in the design > of the FM Radio API? Adding pause and resume to WebFM API is now one of the improvements proposal, please check bug 942727.
The audio competing between FMRadio and Telephony should be performed by just changing routing path from Device_FM_OUT to others so as I know FMRadio shouldn't have a power on/off transition.
Here's a link to general performance requirements, since "5 seconds is too long" is not really a useful requirement. https://wiki.mozilla.org/B2G/Performance/UserStories
Depends on: 942727
Priority: -- → P3
Whiteboard: [c= u= p= s=]
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Whiteboard: [c= u= p= s=] → [c= u= p= s=], [2.0-flame-test-run-3]
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.