Android MediaPlayer bug when using reset() and release() calls

The bug I'm seeing is on the calls to reset() and release() never returning thus leaving my application in an indefinitely stopping state. It doesn't matter if I call stop() before reset() or release() the hang can a开发者_StackOverflowlways be reproduced.

Anyone experienced any similar issues with the MediaPlayer locking up? Any tips? I'm working on a multi-threaded application.

The DDMS reports the following when looking at the threads that are holding:

CLASS | METHOD | FILE | LINE | NATIVE

android.media.MediaPlayer _release MediaPlayer.java -2 true

android.media.MediaPlayer release MediaPlayer.java 1049 false

You may have stumbled across this bug: http://code.google.com/p/android/issues/detail?id=959. It has sat for some time, I wouldn't expect it to be addressed any time soon, unfortunately.

If you are developing for API level 16 or above, I strongly suggest you toss the crappy MediaPlayer and use Exoplayer from Google.

I did and never looked back. Since I also support API level 15, I have an abstraction to use the standard MediaPlayer when in that API and Exoplayer when in 16 (or 17 can't remember now).

It's not perfect, but it's a lot better and I've seen much much better buffering.

I also face this issue in android 2.2, when calling MediaRecorder.release();

Sometime it didn't response, my program flow just stuck on it. it cause my UI freeze, and bring ANR later....

BTW, my customer says that they didn't face it when using android 2.3.3

This: http://code.google.com/p/android/issues/detail?id=959#makechanges

And this: http://code.google.com/p/android/issues/detail?id=5047#makechanges

If you're simply trying to start the song/sound from the beginning, you can write a reset function, that simply does:

mediaplayer.seekTo(0);

I changed my stop(); to: pause, then seekTo.