Closed Bug 1020647 Opened 8 years ago Closed 8 years ago
[B2G][Tarako][Music] Music lags behind display after skipping to next song
Description: Lag is seen when user taps the right or left arrow to skip to the next or previous song (comparing to my own personal device's music app in which the transition is instantaneous). The currently playing screen will transition to the next song's title, picture, and scrubber, while the previous song will continue playing for a moment before cutting off. It appears as though the lag is greater when the same steps are followed, but a bluetooth headset is in use. Repro Steps: 1) Update device to BuildID: 20140602014001 2) Pair a bluetooth headset with the device 3) Launch the music app 4) Tap 'shuffle all' 5) After the song has been playing for a few moments, the next arrow Actual: Lag observed between next song window loading and actually beginning to play. Expected: Song begins plays at the moment that it's information appears on the screen. Environmental Variables: Device: Tarako 1.3T BuildID: 20140602014001 Gaia: 335486c42498fa7a93c21e4d6121199728602ab8 Gecko: 55e4d83019e5 Version: 28.1 Firmware Version: SP6821a-Gonk-4.0-4-29 Notes: Repro frequency: 100% See attached: Logcat
Qawanted to check Buri v1.3.
The issue does not occur on the Buri 1.3 Environmental Variables: Device: Buri 1.3 Build ID: 20140603024001 Gaia: 2408c2238254776b0d3716753b7bf917883c9915 Gecko: 560138f48a17 Version: 28.0 (1.3) MOZ Firmware Version: v1.2device.cfg
We need a video of the bug here.
bug 1002897 landed : 2014-06-03 19:27:04 PDT ; this bug is using build 20140602014001 which doesn't have the fix. Testing on today's build doesn't show this issue. Resolving as WFM: Gaia 5611a68f5c039f62ae74b828feff1530ab066d3a Gecko https://hg.mozilla.org/releases/mozilla-b2g28_v1_3t/rev/7011129d1abd BuildID 20140612014001 Version 28.1 ro.build.version.incremental=eng.cltbld.20140612.045203 ro.build.date=Thu Jun 12 04:52:09 EDT 2014 tarako
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.