Tus comentarios

We are currently looking over some issues with AAC streaming on Android 2.3 and this issue is similar to the one seen on the LG phone.


Update:

Could you try the newest version of XiiaLive v2.1.7? I placed a couple minor fixes that could do the trick on your particular phone running Android 2.1.  Let me know! :)


Update 06/02/11:

Update v2.1.9 brings a lot of optimizations. Please checkout this new version. Also, try using the internal stream engine. That might work for streaming AAC content.

Update 2.1.8v will have a better reconnecting logic.  If there is no network connection it will wait until network connection is available and it will retry to connect as opposed currently just trying continuously...


Update 06/02/11:

Update v2.1.9 has improved this area.  Better reconnection logic has been added, which will only try to reconnect if there is a valid connection, otherwise it waits until a valid connection is available.  Also, unlimited retry option has been added, please note this option is only available on the paid version.

Unfortunately this is an issue in the Android Media Framework "AMF".  Now we are working on our own streamer independent to the AMF.  For now you can actually try using our internal streaming engine which is beta.  It might work on your phone and might not work on your phone...  Give it a try and let me know...
Thanks for the links.  Could you specify what is the issue? Is it that you can't see the bitrate on the app?
Well, when the switch happens if you loose the connection than it wont connect until the buffer is played completely.  So if you are having data dropouts I don't recommend really large buffer length.  Possibly keep pre-buffer at 15000.
Please provide the link of the station you are having issues with.  Also, what phone do you have and what version of Android is it running?

We are improving the favorite skip feature currently.  We will have the improved version out on the next update this month.


Update 06/01/11:

Update v2.1.9 should have this issue resolved. Please confirm if possible.

This is an issue for sure! I have investigated in the past and things got very complex. It is very difficult to predict what encoding to use since it's not easily identifiable. SHOUTcast has released new server tools that hopefully when all other radio providers update it will use the new standard UTF-8 encoding.

Meanwhile this is a good idea and I'll look into adding this option.


Update 05/05/11:

Found a better way to guess the encoding. It's not perfect but for most cases it should work.  The encoding selection is also planed.


Update 06/01/11:

Automatic character encoding has been added to v2.1.9.  Should work for most metadata.

We are investigating... Thanks for your feedback!

Update 02/21/11:
There is an option to disable XiiaLive from taking over the media controls under Settings "User experience" -> "media controls" to OFF. However there are a couple few details we need to resolve.


Update 06/01/11:

Update v2.1.9 has resolved this issue.