MediaMonkey forum

I opened Ticket #7487 "Playback crash/reset when pause and resume while MMA is in the background" a week and a half ago, and have been adding new crash logs to it several times with no acknowledgement from Support. Am I going to get it looked at? At this point, I'm considering looking for a replacement.

Hi Gordol,

Sorry for not getting back to you

I'll follow up with the dev team.

-Rusty

fyi, we _are_ looking into it. I've renamed the subject to better reflect what the issue is (the issue isn't caused by MMA crashing ).

For other readers: the issue is that if playback has been paused (via widget, android auto, or by disconnecting BT) and resumed at a later point in time via the Widget or Notification Player, then MMA sometimes restarts playback from the beginning of the track.

-Rusty

It has also (now? with the current version build 1208) done this with MMA stopped and restarted from the app's program window. If the logs I sent show any of it, this should show in the most recent one.

Tracked as https://www.ventismedia.com/mantis/view.php?id=21211

This should be resolved in build 1213 (available if you've subscribed to beta test builds). Can you confirm?

Thanks!

-Rusty

I am in the beta, and waiting for the new version to be available to me.

rusty wrote: ↑Fri Sep 20, 2024 8:15 am This should be resolved in build 1213 (available if you've subscribed to beta test builds). Can you confirm?

Around midnight I got an update  Google Play says it's build 1212, About says 1213.

Problem still exists.

Via Android Auto, I had hit the Pause button on my car's display and then a few moments later when I hit Play, the track restarted.  As I was driving, unable to capture a log.

Thanks for letting us know about the 'About' message--I've updated it to 1213.

Re. the bug, if you can replicate it again with 1213, please share a log and let us know here or via the ticket.

Thanks!

-Rusty

ZCAAWVK2PV

Playback paused when disconnecting from Android Auto, restarted from the beginning of the track when resumed a little later on the phone.

rusty wrote: ↑Sun Sep 22, 2024 4:06 pm Thanks for letting us know about the 'About' message--I've updated it to 1213.

Re. the bug, if you can replicate it again with 1213, please share a log and let us know here or via the ticket.

Several more logs with 1213 have been uploaded and log IDs in the support ticket.

Thanks! We've just submitted build 1214, which should fix this, to the Play store for approval (it normally takes a day or two to get approved).

Please let us know as we haven't been able to replicate the issue. Thanks!

-Rusty

1214 has fixed this for me.