Issue #800 has been open since 2008.
It's unbelievable that three years later, one still cannot determine
the state of the MediaPlayer.
I hate to kvetch, but Android makes me kvetch more that just about any platform.
Regards
P. V. Nasby
On Sat, Nov 27, 2010 at 7:38 AM, Jason
I know this thread is old, but why not call stop() and that's it.
After you can call start(). Or just call reset() and when you need to
prepare again just setDataSource() and prepareAsync().
-Jona
On Jun 15, 7:30 am, Petroleum Nasby pnasby1...@gmail.com wrote:
Issue #800 has been open since
Sometimes when you call stop(), you can't immediately call prepare(),
even though the state diagram says you can. The state diagram varies
from reality, and the current programming model forces the developer
to assume what the state is based on the APIs that were called, and
when any variance from
Thanks for the advice. I had already modeled the state transitions
using the listeners, however I suspect there is (was) a problem with
the rules I had implemented in this regard.
Because the call to prepareAsync returns immediately, I think a
subsequent call to prepareAsync was coming in and
Do you have an error listener registered? Does it give you more
information?
According to the state diagram, stop() is not available in all states.
Perhaps you're calling stop() in an invalid state, causing the player
to transition to the Error state, at which point prepareAsync would
fail:
Whoa.. what's with the double post??
On Nov 23, 8:16 pm, Jason Polites jason.poli...@gmail.com wrote:
Hi folks,
Some time ago I posted an issue relating to an IllegalStateException
in the Media Player (http://groups.google.com/group/android-developers/
6 matches
Mail list logo
