After some feedback from users, just curious, if you get the new built in player successfully working ...what will happen when a text msg or email comes in on the Android App. Currently our Icecast Streaming Audio pauses. Most users only want music to stop for an actual Phone Call. But I know its happening because we are using/rigging (as per my older posts) the native player. -James

This is a good question. I haven't setup an Icecast server yet but it should not be related. I'm hoping to download the stream and cache x number of bytes to develop a buffer. Having a buffer of data to 'play' should allow the sound to continue to play when a call comes in or when it's moved to the background. Fingers crossed.

David, I was looking at the code: Doing some research. I think the current 'media player' needs to be an ongoing process / services. http://developer.android.com/guide/topics/fundamentals.html From that point we should be able to control what can and can't kill the music stream. I think it may be as simple as calling start services after intent.. Let me know if you dig anything up. Maybe a quick fix..

For sure, the newly updated player (existing code isn't really a player, just a URL to a file and phone decides what to do) should be a process capable of running outside of it's parent application. The Start Services method call would likely happen after the players Intent (screen) launches (like you said). When the app is brought back into the foreground, the Player controls should be available. Gone till tonight.

Buffering size is something that WE as the Icecast server owners would have to configure on the server side. If you look at the Streamfurious or yourmuze.fm these guys are writing apps that stream OUR streams into their OWN server and translate to a worthy format... expensive on their side, but it must be worth while in their opinion.... I understand streamfurious did it because of Androids inability to accept Icecast and Shoutcast natively... so they charged like $7 for their app.