Closed
Bug 1116839
Opened 9 years ago
Closed 9 years ago
[Music]Moving/Scrubbing the timeline scrubber to the end of the track of the song resets it to the beginning of the song with a corrupted time-code and freezes the song playback.
Categories
(Firefox OS Graveyard :: Gaia::Music, defect)
Tracking
(b2g-v2.0 unaffected, b2g-v2.1 unaffected, b2g-v2.2 affected)
RESOLVED
DUPLICATE
of bug 1095382
Tracking | Status | |
---|---|---|
b2g-v2.0 | --- | unaffected |
b2g-v2.1 | --- | unaffected |
b2g-v2.2 | --- | affected |
People
(Reporter: jmitchell, Unassigned)
References
Details
(Keywords: regression, Whiteboard: [2.2-Daily-Testing])
Attachments
(2 files)
Description: When playing music and moving the scrubber to the end of the timeline the scrubber resets back to the beginning but changes the start timecode to 0-1:0-1 instead of 00:00 and causes the song to Freeze; hitting pause and play will change the icon respectively but the song will not play and the scrubber will not move. Recovery Steps: To recover from this bug you must tap the track forward or back buttons as the play/pause buttons will have broken functionality. Repro Steps: 1) Update a Flame to 20141231010205 2) Launch the Music app 3) Play a song 4) Scrub the timeline scrubber to the end of the song Actual: The scrubber resets to 00:00, but the timecode becomes corrupt and the track freezes Expected: (Based on 2.0 and 2.1 functionality) If playing a single track the scrubber will reset to 00:00 and the track will play again If playing a series of tracks the next song will begin (same functionality as hitting 'next track') Environmental Variables: Device: Flame Master (Nightly, Full-flashed) Build ID: 20141231010205 Gaia: 26d479f0fccb7174e06255121e4e938c1b280d67 Gecko: 88037f94b7d7 Gonk: a814b2e2dfdda7140cb3a357617dc4fbb1435e76 Version: 37.0a1 (Master) Firmware Version: v188-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0 Repro frequency: 5/5 See attached: Screenshot, Logcat ----------------------------------------------------------------- This issue DOES occur in 2.2 with V18D base This issue does NOT occur in 2.1, and 2.0 Device: Flame 2.1 (Nightly, Full-flashed) Build ID: 20141223001203 Gaia: 17c7ad2e4919a994f0844239b483116090412dee Gecko: 39dfb662c82a Gonk: a814b2e2dfdda7140cb3a357617dc4fbb1435e76 Version: 34.0 (2.1) Firmware Version: v188-1 Device: Flame 2.0 (Nightly, Full-flashed) Build ID: 20141223000202 Gaia: ce83ea7b8e3fa2d1c3fd771fc22b654c18b3c381 Gecko: 4dd6d9b58f42 Gonk: a814b2e2dfdda7140cb3a357617dc4fbb1435e76 Version: 32.0 (2.0) Firmware Version: v188-1
Reporter | ||
Comment 1•9 years ago
|
||
Flags: needinfo?(pbylenga)
Comment 2•9 years ago
|
||
Functional Regression in a core feature. Requesting a window.
Updated•9 years ago
|
QA Contact: jmercado
Comment 3•9 years ago
|
||
A regression window cannot be found for this issue. It occurs on all KitKat based builds for 2.2 but does not occur on the same builds for 2.2 JB. Flame KK 2.2 Environmental Variables: Device: Flame 2.2 BuildID: 20140904171737 Gaia: de59e0c3614dd0061881fe284e9f2d74fa0d1d5d Gecko: 8703c1895505 Version: 35.0a1 (2.2) Firmware Version: v18D User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0 Flame JB 2.2 Environmental Variables: Device: Flame 2.2 BuildID: 20141003070740 Gaia: a8a6eed2ba9d66239aac789b9ee4900f911c73cb Gecko: 388e101e75c8 Version: 35.0a1 (2.2) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
Updated•9 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Comment 4•9 years ago
|
||
Marking duplicate based on comment in 1095382
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Updated•9 years ago
|
blocking-b2g: 2.2? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•