View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0012923 | MMA | Playback | public | 2015-10-26 21:01 | 2015-11-03 13:11 |
Reporter | rusty | Assigned To | |||
Priority | urgent | Severity | major | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Product Version | 1.1.3 | ||||
Target Version | 1.2.0 | Fixed in Version | 1.1.3 | ||
Summary | 0012923: No bluetooth autoplay on startup (regression 1.1.3) | ||||
Description | Users are indicating that 1.1.3 has a regression that in 1.1.2 turning on the vehicle would trigger MMA playback, but that this doesn't work in 1.1.3. I've seen similar behavior: when I start the car and initiate playback (with MMA not running), nothing happens but then after about 30 seconds, MMA will start to play. Could it be that MMA isn't responding in a timely fashion to bluetooth commands when it starts up, and that the commands time out? | ||||
Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?f=21&t=82774 | ||||
Tags | No tags attached. | ||||
Fixed in build | 494 | ||||
|
The delay must be on OS side, I think. When I was testing it on Kitkat and Lollipop, on both it works correctly, also when I restarted system. On other hand when I disconnect BT headset (on Kitkat device) and then connect again, initialization of playback fails. It was caused by "Power amp" player, which starts HeadsetService when BT is connected and it "stole" focus. It can be solved by enabling "Always respond to remote buttons" in Options. Let me know, whether issue still occurs when this option is enabled. Also next time please include android version on your device. |
|
On further testing the worst symptom I'm seeing is that playback is occasionally delayed, but MMA always seems to correctly respond to BT play commands. Waiting for further user feedback. |
|
I found several issues for devices with Android api >= Lollipop, so I believe that I have fixed this issue. Fixed in build 1.1.4.494 |