Uw opmerkingen
I don't want to roll back to Android 2.3.4 because it's battery hungry.
Well, it looks like I'll have to live with it :)
I just flashed Cyanogen 217 nightly based on Android 2.3.7 and then Cyanogen 207 nightly based on Android 2.3.5 (wich I use now). I believe that the app needs to be optimised for this Android versions, because on aacPlus streams sometimes the sound clicks. It's not a matter of CPU because I overclocked @ 700 MHz and the issue still persists. The sound quality is incredible, nothing compared to Android 2.2 wich really sucked, but this issue needs attention. It also may be useful to know that on Cyanogen 7.1 RC1 based on Android 2.3.4 there are no issues with aacPlus streams even if the CPU is overcloked or not.
After rooting and using conservative mode on CPU, when I play aacPlus streams with XiiaLive minimized and the screen off, the playback is flawless with ZERO issues. I believe the issue is fixed. The only thing left for Wildfire users is to root and install a custom ROM, or live with it :)
Thanks for everything guys.
P.S. On CyanogenMod 7.03 aacPlus streams don't work, but I believe it's an issue regarding Android 2.3.3 media framework.
Well, I can hear the improvement. The playback is at about 99% of what it should be. It's flawless, very few glitches at some points but almost not noticeable. The only moment it stutters is when I turn off the screen for about one second, but I can live with that :) I've been running XiiaLive minimised for some while now. I haven't tryed to turn off the screen with XiiaLive maximized, but since I get good performance when minimized I will only use it that way.
Also, I've noticed some improvement when the network fails and XiiaLive tryes to reconnect. It reconnects faster than v2.2.2.
Good work. Keep it up. If there's room for more improvements for the aac+ streams, make them.
I'm looking forward to purchase the PRO version when the final release is ready.
AOR stopped working with aacPlus streams on HTC Wildfire since the last update (2010). I believe they dropped the support for it. The version before the one in Android Market worked really fine with Wildfire. I will try to find a apk with that version and email it to you. I deleted it from my SD card some while ago when I discovered XiiaLive :)
I just remembered that the playback of aacPlus streams with xiialive minimised, is similar to the old AOR software (before the last update it used to work on Wildfire.. the development has been discontinued). When AOR was used maximized, it never had this issue. It also displayed metadata (if that helps).
In conclusion, I believe something is happening with Xiialive right after turning off the screen when the app is maximized.
The best way to avoid this issue is to keep the player minimised before turning off the display. Another thing I have done is to install AND SET UP PROPERLY Advanced Task Killer Free. I ignored all the important software needed by android and placed a widget of the program on the main screen. The steps I take are the following:
1. I start XiiaLive, go to favourites and play a station.
2. I touch the screen for preventing it to turn off untill the stream plays for about 10 secs after the buffer.
3. I minimise the app and press the Advanced Task Killer widget to kill everything else that runs in the background. This does not affect the playback of XiiaLive.
4. After all these steps, I turn off the screen and the playback is 99% flawless.
If I don't minimise the app, this issue occurs as described in this topic. I believe it has something to do with retrieving the metadata. I've noticed it especially when a song ends and another one starts playing... that's when it stutters more often. It seems that even if the display is off, when the app is maximised, it uses lot of CPU. Even the battery life is better since I run XiiaLive minimised before turning off the screen.
How about the internal streaming engine? Any hope to make it work flawless on this phone in order to fix this issue for good?
Customer support service by UserEcho
BTW Jona, you should do something with the interface of the app. On my tablet the interface is really buggy and messed up.