View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009814 | MMA | Playback | public | 2012-10-11 18:10 | 2012-12-11 15:35 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Target Version | 1.0.1 | Fixed in Version | 1.0.1 | ||
| Summary | 0009814: Clicking last-played track triggers crash --> triggers playback of wrong track | ||||
| Description | 1 Play a playlist, and press pause on 'Track x' 2 Click 'Back' to exit MM 3 Wait 10 minutes and or do some other activity on the phone 4 Run MM again --> Main menu appears, with 'Track x' in the MiniPlayer 5 Click the Artwork in the MiniPlayer OR press Play button in the miniplayer --> MM crashes This happens consistently on GB, but never on JB. I can't submit a debug log because of 0009813 . | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 55 | ||||
|
|
The crash seems to be fixed in build 43. However, now, upon clicking (at step 5) the track that's displayed in the miniplayer (the track that was last played/paused before mma was exited), the first track in the NP list appears, instead of the track that was displayed in the miniplayer. |
|
|
Fixed in build 45 |
|
|
Tested build 45 and this is mostly fixed, but there still remain a couple of issues: 1) Clicking the play button or the artwork in the miniplayer at step 5 results in a ~3 second delay before the playback begins or the NP>Art dialog opens. The action should be immediate. 2) Sometimes, if the user clicks the 'Previous' or 'Next' button at step 4, nothing happens. If the user subsequently presses play, then the first track in the NP list plays. |
|
|
3) If the user clicks the Play button in the miniplayer at step 5 while the MMA scanning indicator is on --> MM appears frozen for about 45 seconds before playback begins. |
|
|
Fixed 1) a 3) in build 48 |
|
|
Fixed in build 51 |
|
|
Tested build 51 1) fixed 2) still occurs--pressing Prev/Next in the widget has no effect 3) not tested |
|
|
Fixed in build 52. |
|
|
Issue 2 isn't fully fixed in build 52. Its a minor point but: - nothing occurs on the first press of the prev/next button in the widget--only the second press advances the track - the second press doesn't initiate playback--only the third press does |
|
|
Fixed in build 55. |
|
|
Verified 63 |
