Both of the above issues were fixed in build 140. If you're still experiencing a failure to terminate in 140+, please let us know.

Thanks.

-Rusty

I hit a similar issue today. I'd played an album in the car. A few hours later, I picked up the device to sync the plays; when I woke it up, the Now Playing showed a Pause button rather than Play (as if it were playing) but the progress bar showed 0:00 and was not advancing; and no sound. I switched to Home and tried to stop, but nothing happened.

So I force-closed in Task Manager. When I restarted, I got the prompt telling me my 30-day limit had expired. (Sure would be nice if that could get reset with every new version.) Maybe the expiration caused something to get stuck?

Anyway, time to go rebuild the sync list again. And, I'm going to lose two days worth of sync. Bother.

It could be related to the failed wifi sync. I will keep that in mind going forward since I did notice it this morning while testing wifi sync failure scenarios.

bkenobi69,
Most likely the problem isn't related specifically to the stop button--it's an example of a certain case that is causing MM to fail to terminate (either via the Stop button, or via the timer when playback has stopped and MM isn't in the foreground).

We're aware of the following cases that cause this failure to terminate:
http://www.ventismedia.com/mantis/view.php?id=10935
http://www.ventismedia.com/mantis/view.php?id=10451

If you figure out what specifically triggers the problem in your case, please let us know.

Thanks.

-Rusty

There was some improvements in 136 over 133 please let us know if issue recur.

Just for kicks, I force closed MMA from the app manager. When I relaunched MMA, it does allow me to close with notification stop button. It appears this was either a one time event or at least something that doesn't happen every time. Hopefully the debug log sent earlier will provide some insight.

This is a regression from 133 for me. Debug log uploaded.

Droid4 ICS 4.0.4
MMA 136