Closed
Bug 1141330
Opened 9 years ago
Closed 9 years ago
[FM Radio] Starting the FM Radio app without headphones results in a broken tuner dial
Categories
(Firefox OS Graveyard :: Gaia::FMRadio, defect)
Tracking
(blocking-b2g:2.5+, b2g-v2.2 unaffected, b2g-master verified)
Tracking | Status | |
---|---|---|
b2g-v2.2 | --- | unaffected |
b2g-master | --- | verified |
People
(Reporter: Marty, Assigned: kgrandon)
References
()
Details
(Keywords: regression, Whiteboard: [3.0-Daily-Testing][systemsfe])
Attachments
(1 file)
26.82 KB,
text/plain
|
Details |
Description: If the FM Radio app is started without headphones, the visual tuner/dial will not be properly. The user can try to scroll the dial, but will only be able to move between 87.5 and 108.0 MHz, often resulting in a display of 'NaN MHz' Note: The '<' and '>' buttons will still function, allowing the user to scrub through radio stations. Repro Steps: 1) Update a Flame to 20150309010232 2) Launch the FM Radio app without headphones plugged in. 3) Once the app has launched, plug in headphones 4) Observe and interact with the tuner/dial. Actual: The visual tuner dial does not function properly Expected: The visual tuner dial works properly, allowing the user to move between all radio frequencies. Environmental Variables: Device: Flame 3.0 (319MB)(Full Flash) Build ID: 20150309010232 Gaia: fea83511df9ccba64259346bc02ebf2c417a12c2 Gecko: eab4a81e4457 Gonk: e7c90613521145db090dd24147afd5ceb5703190 Version: 39.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:39.0) Gecko/39.0 Firefox/39.0 Repro frequency: 5/5 See attached: video clip (URL), logcat
Reporter | ||
Comment 1•9 years ago
|
||
This issue does NOT occur on Flame 2.2. The visual tuner dial works properly, allowing the user to move between all radio frequencies. Environmental Variables: Device: Flame 2.2 (319MB)(Full Flash) Build ID: 20150309002506 Gaia: 166491b92278dc9e648f8d49ab02d9ca00d74421 Gecko: 91b7aa6a3243 Gonk: e7c90613521145db090dd24147afd5ceb5703190 Version: 37.0 (2.2) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Comment 2•9 years ago
|
||
[Blocking Requested - why for this release]: Functional regression of a core feature. Requesting a window.
blocking-b2g: --- → 3.0?
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Keywords: regressionwindow-wanted
Updated•9 years ago
|
QA Contact: ychung
Comment 3•9 years ago
|
||
b2g-inbound Regression Window: Last Working Environmental Variables: Device: Flame 3.0 BuildID: 20150302233447 Gaia: 4352d56f8c79a51eb44e43658472236a38d6f1d8 Gecko: 7620dbd7cf22 Version: 39.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:39.0) Gecko/39.0 Firefox/39.0 First Broken Environmental Variables: Device: Flame 3.0 BuildID: 20150302234850 Gaia: 620210e07a4634008a33fe62f817f508258bd2c3 Gecko: f112754e1858 Version: 39.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:39.0) Gecko/39.0 Firefox/39.0 Last Working Gaia First Broken Gecko: Issue does NOT reproduce Gaia: 4352d56f8c79a51eb44e43658472236a38d6f1d8 Gecko: f112754e1858 First Broken Gaia Last Working Gecko: Issue DOES reproduce Gaia: 620210e07a4634008a33fe62f817f508258bd2c3 Gecko: 7620dbd7cf22 https://github.com/mozilla-b2g/gaia/compare/4352d56f8c79a51eb44e43658472236a38d6f1d8...620210e07a4634008a33fe62f817f508258bd2c3 caused by bug 1069221
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: regressionwindow-wanted
QA Contact: ychung
Comment 4•9 years ago
|
||
Kevin, can you take a look at this please? Looks like this could have been caused by the landing for bug 1069221.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(kgrandon)
Assignee | ||
Comment 5•9 years ago
|
||
It seems like this is probably more likely a gecko regression, but I will try to take a look later this week.
Assignee | ||
Comment 6•9 years ago
|
||
Seems like the regression range was probably correct. I've gone ahead and backed out bug 1069221 for now as it was awaiting uplift, and better to not create a 2.2 blocker.
Assignee: nobody → kgrandon
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(kgrandon)
Resolution: --- → FIXED
Whiteboard: [3.0-Daily-Testing] → [3.0-Daily-Testing][systemsfe]
Updated•9 years ago
|
blocking-b2g: 3.0? → 3.0+
Updated•9 years ago
|
Target Milestone: --- → 2.2 S8 (20mar)
Comment 7•9 years ago
|
||
This issue is verified fixed on Flame Master. Result: The turner works properly when the user plugs in the headphone after starting FM Radio. Environmental Variables: Device: Flame 3.0 (KK, 319mb, full flash) Build ID: 20150430010201 Gaia: db8ea705c0fd1b1684807f5a8e837bb9a36a6f96 Gecko: 4b9b12c248dc Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b Version: 40.0a1 (Master) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0
Status: RESOLVED → VERIFIED
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Updated•9 years ago
|
Updated•9 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Updated•9 years ago
|
status-b2g-v2.5:
--- → verified
Updated•9 years ago
|
status-b2g-v2.5:
verified → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•