I'm bumping this because a fundamental component of the Android system
is broken, there have been numerous reports and not a single person
from the Android dev team have spoken about this after weeks. Please
reply soon! There are hundreds of broken apps on the market.

R

On Jun 18, 4:45 pm, Rich <[email protected]> wrote:
> Same thing here - you're not the only one. The newMediaPlayeris
> absolute garbage, trying to decipher the error codes is like reading
> tea leaves (And they told us this was going to be 
> fixed:http://www.mail-archive.com/[email protected]/msg20...
> - they just made it worse!) Further discussion here:
>
> http://groups.google.com/group/android-developers/browse_thread/threa...
>
> http://groups.google.com/group/android-developers/browse_thread/threa...
>
> and
>
> http://forum.rhapsody.com/rhapsody/topics/app_force_closes_in_froyo_w...
>
> No proposed workarounds, not a peep from any Google employees.
>
> Very disappointing response so far. Fortunately 2.2 isn't deployed on
> any retail devices, but it sure sucks if you've only got a Nexus on
> 2.2
>
> Let me know if you come up with some solution,
> Rich
>
> On Jun 2, 5:29 pm, RC <[email protected]> wrote:
>
> > I'm having a problem withMediaPlayerplaying a stream. It goes along
> > fine and then I get the following.
>
> > I/AwesomePlayer(   59): prefetcher is done preparing
> > E/MediaPlayer( 6358): error (1, -2147483648)
> > E/MediaPlayer( 6358): Error (1,-2147483648)
> > W/TimedEventQueue(   59): Event 2 was not found in the queue, already
> > cancelled?
> > V/TuneWiki( 6358): Client closed connection!
> > V/TuneWiki( 6358): java.net.SocketException: Connection reset by peer
> > V/TuneWiki( 6358):     at
> > org.apache.harmony.luni.platform.OSNetworkSystem.writeSocketImpl(Native
> > Method)
>
> > This is only happening in the newFroYo(Android 2.2) release where
> > the media player was changed.
>
> > All streaming works up to Android 2.1, and with Android 2.2 we get
> > squelches, pops, and other bad noise and then the connection
> > terminates.
>
> > I have looked at one possibility being the change from HTTP/1.0 to
> > HTTP/1.1 requests. I'm not sure if Stagefright can be told to make
> > HTTP/1.0 connections but it appears to work for a couple seconds and
> > then everything falls apart and the media player quits.
>
> > Anyone have thoughts about what has changed and what might be needed
> > to work with the new media player properly?

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to