View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013327 | MMA | Playback | public | 2016-06-02 16:49 | 2016-06-07 17:25 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | sometimes |
| Status | resolved | Resolution | fixed | ||
| Product Version | 1.2.0 | ||||
| Target Version | 1.2.0 | Fixed in Version | 1.2.0 | ||
| Summary | 0013327: Bluetooth: Metadata fails to update on bluetooth reconnection | ||||
| Description | As reported at http://www.mediamonkey.com/forum/viewtopic.php?f=21&t=85035&p=423801#p423801 , metadata fails to update on bluetooth playback in some cases. | ||||
| Steps To Reproduce | 1.) Enter the car (car radio switches on) and start to play music via MMA. 2.) Leave the car and by this step the car's radio got switched off. MMA is still running in the background. 3.) Enter the car 2 minutes later and the car radio switches back on. 4.) Start to play music via MMA and switch to the next track ---> Metadata from step 1) continues to display! 5) Switch the car radio off and turn it again on, --> Metadata updates to the currently playing track. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 600 | ||||
|
|
I was able to replicate a variant of this issue: 1.) Enter the car and start to play music via MMA over bluetooth (song Easy Lover). 2.) Leave the car and by this step the car's radio got switched off. MMA is still running in the background. 3.) Enter the car 2 minutes later and the car radio switches back on. 4.) Start to play music via MMA (Easy Lover) and switch to the next track ---> Metadata for Easy Lover briefly re-appears and then switches to the next track (Echoes) I suspect that the brief re-appearance of the initial metadata is what, on some devices, causes the initial metadata to continue to display. Log ID: HFAYPS43HQ Description: incorrect metadata |
|
|
I can't reproduce your issue with SBH50, but the original issue is possible to replicate only on pre Lollipop devices (and only on devices using Metachanged Intent). User responded, he was not able to reproduce the issue with build 600, so I mark this issue as resolved in build 1.2.0.600. |
