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=13715We are waiting for further response from the Android Team.
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.
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).
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...
Service d'assistance aux clients par UserEcho