First track cuts off after starting Bluetooth [#12730]

[mcow]

For several weeks, keeping up with the various MMA builds, I've started noticing a consistent symptom with Bluetooth playback in my car.
I'm not sure if this is something MediaMonkey can fix, but it seems different than the other problems I've had with BT.

I start the car and wait until the bluetooth connection is established. (The tablet beeps for this.) I turn on the car stereo, which is already set to the BT connection; after a moment to negotiate the connection, the expected track starts up and plays for some short period of time, maybe four or five seconds, and then stops. The head unit display blinks "Pause".

The scrub bar in MMA is advancing at this time. I haven't let it run for the length of a song to see what happens next; instead, I press the "back" button (on the steering wheel) and MMA immediately resets to the beginning of the track and starts playing; and this generally proceeds with no incident.

I caught it this evening, grabbed a log as soon as I could after it stopped playback: 35VL6R017F
i didn't have a wireless connection until later, but I assume those are queued up (?)


It's pretty consistent. I don't have to turn on the screen, but it happens if the screen is on, too.

Usually, after turning off the stereo, I explicitly press the MMA notification's Stop button so the track I just cut off restarts when I get back in the car. Other times, I forget to do this, but I get the same behavior whether the track is starting from the middle or the beginning.

I think if there isn't anything queued up, the next track I start does not have this problem.

[rusty]

Hi mcow,

We've fixed some possibly related issues (see: http://www.ventismedia.com/mantis/view.php?id=12614 ) but couldn't locate your debug log.

Can you test build 400+ and confirm whether the issue is resolved? If not, please let us know and post another log ID.

Thanks.

-Rusty

[mcow]

I get the same symptoms with build 400.
I tried to catch it in a log: B65OJANKO1

[rusty]

Hi mcow,

We don't seem to have received the log. Can you retry?

Thanks.

-Rusty

[mcow]

Do I need to be connected to wi-fi when I click submit? If it takes me a while to get to a signal, is the useful information overwritten?

[rusty]

You need to have a network connection to submit the log (at least until we fix this).

Thanks.

-Rusty

[rusty]

Is this still occurring with build 411 ?

-Rusty

[mcow]

Is this still occurring with build 411 ?

Yes it is, but I haven't managed to capture a log yet.

[rusty]

So it's an intermittent issue?

Thanks.

-Rusty

[mcow]

No, it's not intermittent. I'm just getting tired of trying to get it fixed. Because of the necessity for a wifi link at the time of capturing the log. The problem occurs when I'm about to take off in my car, not when I get home; when I get home, I'm thinking of doing things other than debug MediaMonkey.

In fact, in many ways, the current situation is the best it's been because I very seldom am in a state where I can't get the music playing at all, any more. I used to have to turn the car off and back on in order to play music, or switch to a CD.

[mcow]

Is this still occurring with build 411 ?

I saw that you'd implemented delayed logs, so I tried sending logs today, with 416. I assume they are sent automatically, so these should have gotten thru:

US6P5AMSG5: This captures what I think is the first part of the problem: When I turn on the car, the Bluetooth connection is established. If I leave the stereo off, when the BT connection is made, MMA starts to "play"; it shouldn't start until the head unit sends the Play command.
So when this happened, I woke up the tablet, pressed Pause, and sent a log.

JP0XLUP9RY: This captures subsequent behavior: Turn the stereo on. No sound at all; head unit display is blank, then blinks "Pause." Look at MMA: it has stopped playing. I sent a log at this point.

[martin.bohac]

Thanks for your debug logs.
Tracked at:
http://www.ventismedia.com/mantis/view.php?id=12730

Both described cases are fixed in next build 417.

Martin

[mcow]

Thank you, Martin. The Bluetooth interaction appears to be a lot more sensible. However, the problem I originally opened this thread for still persists.

I captured a new log, 5DVCSBCDQ1.
When I got to work, I let a track complete, then turned off the head unit as the next one began. MMA stopped, correctly. I pressed the stop button in the MMA notification, to reset the track to 0:00.

Then tonight, leaving work, I started playback with the head unit after the BT connection was established. It played audibly for about 5 seconds, then cut out. The MMA scrub-bar kept moving. I turned off the head unit, and the scrub-bar stopped. Then I submitted the log.

I noticed, on returning to MMA after logging, that the scrub-bar had reset to 0:00. I turned the head unit on again, and it started playback and continued; no problems followed.

[mcow]

I wanted to say that 1.0.2 has been behaving generally better with Bluetooth in the car. Since getting the Nexus 5X, I haven't been using the old Galaxy Tab, but even before getting that phone I noticed better behavior. In particular, the problem this topic was about has not been occurring.

I also have noticed that with the phone, the head unit displays the elapsed track time (but not the track title), something that didn't occur with the Tab. I've sometimes been using Google's music program to stream while driving, and get the same display; I think the head unit just doesn't support title display.

The phone also established the BT connection quite a bit faster than the Tab did, but that's not too surprising.