Closed Bug 935086 Opened 11 years ago Closed 6 years ago

[B2G][FM Radio] Favoriting a station while FM radio is stopped causes the user to move back to 87.5

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v1.2 affected, b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected, b2g-master affected)

RESOLVED WONTFIX
Tracking Status
b2g-v1.2 --- affected
b2g-v2.0 --- affected
b2g-v2.1 --- affected
b2g-v2.2 --- affected
b2g-master --- affected

People

(Reporter: dwatson, Unassigned)

References

Details

(Whiteboard: [polish][priority])

Attachments

(1 file)

Repro Steps:
1. Updated Buri to Build ID: 20131105004003
2. Open the FM radio app
3. Plug in headphones
4. Navigate to a frequency
5. Press the stop button
6. Press the Star icon to favorite the station

Actual Results:
The user is moved back to 87.5.

Expected Results:
The user will stay at the frequency that was favorited until the user changed the station.

Environmental Variables
Device: Buri v1.2 COM RIL
Build ID: 20131105004003
Gecko: http://hg.mozilla.org/releases/mozilla-b2g26_v1_2/rev/3ba912717904
Gaia: be4ea00a50236b10eb0a03232a28ffd0048e0cb8
Platform Version: 26.0
RIL Version: 01.01.00.019.281 
Base Build: 20131015
Does this reproduce on 1.1?
Keywords: qawanted
This doesn't happen using the 1.1 device shipped in Brazil.
Keywords: qawanted
OS: Windows 7 → Gonk (Firefox OS)
Hardware: x86_64 → ARM
Sorry, I misread the steps. If you press the stop button using the 1.1 device it does the same thing as described in this bug.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
This issue reproduces on Flame 2.1, 2.2 and 3.0

Station is favorited but the user is taken back to the far left station

Environmental Variables:
Device: Flame 3.0 (319mb)(Kitkat)(Full Flash)
Build ID: 20150402063750
Gaia: f37be8b44cb7c3a147b9615ab76743b760f08eeb
Gecko: 35046df9df1f
Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b
Version: 40.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0


Environmental Variables:
Device: Flame 2.2 (319mb)(Kitkat)(Full Flash)
Build ID: 20150331002503
Gaia: cc11248ab69f13e89416c8e6bb2e184187e72088
Gecko: 90a26917ee8f
Gonk: ebad7da532429a6f5efadc00bf6ad8a41288a429
Version: 37.0 (2.2)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0


Environmental Variables:
Device: Flame 2.1 (319mb)(Kitkat)(Full Flash)
Build ID: 20150330001204
Gaia: 6f39e4e876152de1dcdcc0e7656197f22f105e4b
Gecko: 275ad18f587b
Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b
Version: 34.0 (2.1)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
QA Whiteboard: [QAnalyst-Triage+][lead-review+] → [QAnalyst-Triage?][lead-review+]
Flags: needinfo?(pbylenga)
NI on component owner for nomination decision.
QA Whiteboard: [QAnalyst-Triage?][lead-review+] → [QAnalyst-Triage+][lead-review+]
Flags: needinfo?(pbylenga) → needinfo?(npark)
Although it's not a blocker material, I feel that this should be simple to fix, and it is a type of polish bug that's been around for too long so it should be higher up in the queue.  Hema, do you know who should I ping for FM radio fix?
Flags: needinfo?(npark) → needinfo?(hkoka)
Justin,

Not a blocker. When you get a chance please fix this polish issue.

Thanks
Hema
Flags: needinfo?(hkoka) → needinfo?(jdarcangelo)
Whiteboard: [polish][priority]
Bulk-clearing old NI? requests. If this still needs my attention, please re-flag me. Thanks.
Flags: needinfo?(jdarcangelo)
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: