View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011416 | MMA | Playback | public | 2013-10-25 15:01 | 2014-12-17 19:55 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.0.4 | ||||
| Target Version | 1.1.0 | Fixed in Version | 1.1.0 | ||
| Summary | 0011416: Bluetooth: some devices fail to initiate playback / MediaMonkey isn't the active media app | ||||
| Description | On some bluetooth devices (two users reported this on a Toyota car, and I observed it on a Clarion radio), if the car is started up while MMA is running, pressing the radio's play/pause button has no effect. The workaround is to press 'Play' in MMA, and from that point on, Play/Pause button on the radio works. Note: user indicates that MMA screen should be off to replicate, but my experience is that even if the screen is on, this failure occurs. Also, when testing the same device (GS3) using the Samsung Music Player, this problem doesn't occur. | ||||
| Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?f=21&t=73831 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 358 | ||||
| related to | 0010874 | closed | martin | MMA shouldn't automatically terminate if an audio device is connected |
| related to | 0011687 | closed | martin | Lock screen don't resume playback after MM has terminated |
| related to | 0011969 | resolved | martin | 'Always respond to remote buttons' doesn't work |
| related to | 0012441 | closed | martin | Controls for Lock Screen Player disappear |
|
|
I'm Able to replicate on my LG headunit and on friends pioneer headunit. Looks like the problem lies in point that after pairing headunit do not know to whoom it should send command and as soon as it gets player status/audio it starts to work. I have found that If MMA is playing at the moment of BT connection Player commands work. Also Prev/Next should be tested too. |
|
|
Fixed in build 178. |
|
|
Verified on a satechi device. |
|
|
As reported at http://www.mediamonkey.com/forum/viewtopic.php?f=21&t=73831&p=374995#p377189 , this issue doesn't seem to be fully resolved on some devices. User submitted a debug log for a case where MMA seekbar began moving, but there was no audio. EDIT: a second user indicated that he experienced the same problem as well (comment appears in the forum, following the above comment). |
|
|
Should be fixed in build 190. |
|
|
Apparently this is still occurring for some users: http://www.mediamonkey.com/forum/viewtopic.php?f=21&t=73831&start=15#p379861 |
|
|
Initialization of playback fails when screen is locked sometimes. It should be fixed in build 215. |
|
|
new Option "Remote controls" in build 218. This option must be enabled to control by remote devices such as Headset or Bluetooth. |
|
|
improved in build 228. |
|
|
Verified no regressions in 228. |
|
|
Regression from build 228: "Remote Controls" - all button commands were received twice on GB and ICS (maybe device specific issue) -> fixed in build 230. |
|
|
I'm replicating a similar problem with 1.1.0.341 using a Hyundai car radio. If I initiate playback with MMA, then the vehicle Back/Next/Play/Pause buttons work as expected. However, if I turn on the car and press Play/Pause, then Google Music usually starts playing tracks! Note: 'Always respond to remote buttons' is enabled. |
|
|
Another report of this issue at: http://www.mediamonkey.com/forum/viewtopic.php?f=21&t=78608 (debug log included) Note: I've been able to replicate consistently using a Samsung tablet or a Nexus 5: 1 Reboot the tablet and pair with a bluetooth headset (with controls) 2 Run Samsung player / Google Player, click a single track to play it and wait for it to stop 3 Back out of the Samsung Player 4 Go to the MediaMonkey for Android Widget and click Play to play the current track 5 Open the notifications bar and press 'Stop' 6 Press Play on the Bluetooth controller --> The Samsung/Google Player starts playing!! This is almost certainly the same problem that users are also experiencing with their Bluetooth Headunits in their vehicles. |
|
|
0011416:0041372 - fixed in build 1.1.0.0356 0011416:0041083 - please verify whether this fix also helped in this case. |
|
|
Tested build 356 with a Nexus 5, and the issue occurs as previously. Debug log X9OLHJFTQQ In fact, the bug is even worse than previously described: 1 Reboot the tablet and pair with a bluetooth headset (with controls) 2 Run Samsung player / Google Player, click a single track to play it and wait for it to stop 3 Back out of the Samsung Player 4 Go to the MediaMonkey for Android Widget and click Play to play the current track 5 Skip this step [Open the notifications bar and press 'Stop'] 6 Press Play on the Bluetooth controller --> The Samsung/Google Player starts playing concurrently with MMA!! i.e. even when MMA playback via the widget is ongoing, the bluetooth controller controls the other media app which is inactive. Note: '[x] Always respond to remote buttons' was enabled for this test. |
|
|
Our registration of remote button receiver always failed on lower layer when MMA was never in foreground before. So playback from widget caused these BT issues. Now it should be fixed and working much better. Fixed in build 1.1.0.0357 |
|
|
Build 357 behaves in the same manner as previous builds exactly as described at 0011416:0041465 btw, there's another very annoying manifestation of this bug or a related one: 1 Play TrackA in MMA 2 Press Power 2x to get to the lock screen 3 Pause using the lockscreen --> Playback pauses 4 Wait 5 minutes 5 Press the power button --> Track A displays in the Lock Screen player, but the player controls disappear so the user can no longer control playback In contrast, with Google Music, the playback controls don't disappear. |
|
|
It was caused by beta build, which has different package name. Fixed in build 1.1.0.0358 |
|
|
Verified 358--the original issue is fixed. The issue raised at 0011416:0041473 is still open though. Opening a separate bug for that. |
