Issues with AAC+ streams on Android 2.3
Antwoorden
Now, the only issue is that, after less than 5 minutes, it will say "completed", like it was a finite stream... and the stopping and buffering is much worse now (on par with Radio Time
However, tunein radio and antplayer work fine (both uses independent streaming engine), so if xiialive can use independent streaming engine it will work.
Tested on the device I have:
nexus one, NS, X10 are not included.
G2x: OK
Galaxy Tab: OK
MyTouch 4: choppy
Optimus Virgin: choppy
It appears if the device has decent 3D performance, it doesn't have problem. I guess this engine requires good FPU (floating point unit) which affects 3D performance.
If you read my result, you may understand why it's off by default.
Some phones/tablets with good 3D rendering in quadrant seem to be running well. However, it's choppy with aac+ on some low end machines even MyTouch 4.
Nexus one and NS are not tested because they're upgraded to 2.3.4 so custom streaming engine is not required, so does X10i which runs on 2.1 that the platform doesn't have aac+ streaming problem.
Other streaming formats don't need customer streaming engine (you don't have to enable it if you don't have aac+ stream, or your platform is either 2.1 or 2.3.4 or higher).
I just found the latest 2.2.1 on market and now it can play streaming aac+ without internal streaming engine enabled!!!
I tested it on Galaxy Tab and G2x and both work 100% with aac+ streams (wfuv 64k aac stream) without internal streaming engine.
Yea, we know... if you have Facebook, like "DroidLive"... I've been using it for a couple of days...
Also, if you are running Android versions 2.3, 2.3.1, 2.3.2, or 2.3.3, your AAC+ streaming will still not work, and you'll have to use the internal encoder for AAC/AAC+ streaming. 2.3.4 fixes the audio framework issue, but it's still nice to have an internal coder, because the code (should?) be cleaner, and can be optimized more easily than the Android OS will be...
Also, the screen resolution isn't working right on this device, it has a qHD screen. XiiaLive takes up only 2/3 of it.
Hopefully the next release will support more screen resolution (960x540, 1024x600)
When I switched back to internal decoder, the sound was excellent as it should be. Not sure what the issue is, it's also frustrating because apparently even on 4G, it's not able to maintain a 40kbps stream for more than 15 seconds without rebuffering. Not sure if it's the network being horrible or something else...
After investigating the issue it appears that this is an issue with Android. AAC streams are played over RTSP and currently Android 2.3 seems to have broken RTSP functionality. Please see the following link:
http://code.google.com/p/android/issues/detail?id=13715
We are waiting for further response from the Android Team.
Update 05/05/11:
Seems like the AAC issue with Android 2.3 have been resolved on the next upcoming update 2.3.4. Thanks to everyone that confirmed this.
Customer support service by UserEcho
After investigating the issue it appears that this is an issue with Android. AAC streams are played over RTSP and currently Android 2.3 seems to have broken RTSP functionality. Please see the following link:
http://code.google.com/p/android/issues/detail?id=13715
We are waiting for further response from the Android Team.
Update 05/05/11:
Seems like the AAC issue with Android 2.3 have been resolved on the next upcoming update 2.3.4. Thanks to everyone that confirmed this.