Closed Bug 862571 Opened 12 years ago Closed 11 years ago

[B2G][Inari][FMRadio]There is a 3-4 second static delay when stopping the radio

Categories

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

ARM
Gonk (Firefox OS)
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME
1.4 S6 (25apr)

People

(Reporter: sparsons, Unassigned)

Details

(Keywords: perf, Whiteboard: [c=effect p= s=2014.04.25 u=] inarirun1 leorun1 )

Description: After pressing the stop button on the radio, there's a bit of delay with some radio fuzz before the station turns off. Repro Steps: 1) Updated to Inari Build ID: 20130415230202 2) Launch FM Radio app, with headphones in. 3) Choose any station to listen to. 4) Press the stop button. Actual: There is a 3-4 second delay where instead of stopping, static can be heard. Expected: Pressing the stop button should stop all audio from the radio. Environmental Variables: Kernel Date: Feb 21 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/04de87e63992 Gaia: cc0e498eca683258a926768388b5f39dd1c642a2 Notes: Repro frequency: 3/3 Test Suite Name: FMRadio UCID: #1931 Link to failed test case:https://moztrap.mozilla.org/runtests/run/1105/env/316/?pagenumber=1&pagesize=20&sortfield=order&sortdirection=asc&filter-id=1931&filter-suite=123 Q Analysts Test Team Priority: Pri3
Whiteboard: inarirun1 → inarirun1 leorun1
I believe this might be closely related to bug 819080. Note sure it is a duplicate yet.
Keywords: perf
Whiteboard: inarirun1 leorun1 → inarirun1 leorun1 [c= p= s= u=][perf-reviewed]
Whiteboard: inarirun1 leorun1 [c= p= s= u=][perf-reviewed] → inarirun1 leorun1 [c= p= s= u=]
Sarah, Do you want to verify if this is fix since there is similar bug that has been fixed already.
Problem no longer seen running 1.5 on Geeksphone Keon Git commit 2014.04.16 00:08:26 034050e5.
Status: NEW → RESOLVED
Closed: 11 years ago
Priority: -- → P2
Resolution: --- → WORKSFORME
Whiteboard: inarirun1 leorun1 [c= p= s= u=] → [c=effect p= s=2014.04.25 u=] inarirun1 leorun1
Target Milestone: --- → 1.4 S6 (25apr)
You need to log in before you can comment on or make changes to this bug.