Could you please build in the feature again to reduce the bitrate from a stream.
Or to play already reduced streams from a station on shoutcast.
Example technobase.fm.
If you search on the official shoutcast website there are three streams.
If you search on xialive there is only one with the highest bitrate.
But on sometimes slowly mobile connections you could just play the slowest with 48kb.
I'm sorry for my English but I am from Germany.
I hope you understand it.
I know it was asked 3 years ago but I think it's not really the same

Many thanks

Lukas

Galaxy S4 SCH-I545, Version 4.4.2 -- is stuttering on track changes and station switching.  The data connection is solid, I'm thinking the album art is causing the problem (didn't have this problem on prior version of XIIA)  -- I don't care about album art and would prefer there was an "OFF" option

Asus ME173x tablet, Version 4.4.2 -- app shuts down intermittently several times a day (unfortunately xiia has to shut down error) and I didn't have this problem on prior version of XIIA

aac and aac+ streams not playing on motorola milestone 2

This update was mainly a maintenance update.

I really like XiiaLive. It has been quite reliable, and it uses noticeably less battery power than one of the other popular radio apps (that app also caused strange phone behaviour, like lock-ups). Nevertheless, XiiaLive still uses more battery power than I would like, and maybe more than it needs to. I can download 80MB of podcasts in 2 minutes, for no noticeable battery usage, and play back a 3 hour podcast for just a fraction of my phone's battery life. Using XiiaLive for 2 hours, involving a similar amount of data download (though admittedly higher bit-rate processing during playback) will use up almost all of my battery. It occurred to me that one difference between XiiaLive and a podcast download with separate playback, is that the podcast download is probably receiving full/large data packets, while XiiaLive is reading the data as fast as it comes in from a throttled stream. That means the same amount of data will arrive in many many small packets, resulting in a lot more radio activity accessing the Wi-Fi network. I don't know how hard it is to do this in an Android App (I know how I'd do it on a PC), but one thing you could try, in order to increase the packet sizes, and thus reduce radio activity and battery usage, is to add a delay before reading the input stream. Figure out what percentage of your buffer equates to a full Wi-Fi/TCPIP packet, then add the corresponding delay. For example, if 10% of the buffer equals a good packet size, then don't try to read more data from the input stream until the buffer drops to 90% full (either calculate the required sleep time based on buffer fullness, or have the playback function trigger the read event at the 90% mark). Again, I don't know how hard it is, or if it's even possible, to do this using Android software (it depends how much control the software gives you versus how much it does for you automatically), but I have my fingers crossed for you.

Has been trying to install for day and ahalf

I want to add the player to my website for desktop computers.