Fascinating and informative. Hats off to you, sir.
EDIT: Actually, after reading his post, I'm not sure I agree at all. He is saying that there was a bug in stagefright that caused lower-bandwidth AAC to sound bad, but when streaming over WiFi of 4G, the newer codec that uses more bandwidth was ok. How is that the fault of the streaming radio companies? And how is that still not a bug on behalf of Google for alienating users of the older codec (which, by the way, is hardly obsolete compared to, say mp3s).
This whole "moving forward means not having to support legacy codecs" sounds a little ridiculous to me. AAC is not legacy, and is still used in a lot of streaming media (heck, most of my encoded movies from previous phones have audio in lower quality AAC. I am NOT interested in having to re-encode all of them because of a known bug in Google's decoder!). Pandora refused to update their Windows Mobile 6.x software because WM was difficult to build AAC support for (I had a chat with one of their chief technology officers almost a year ago) and re-encoding their library for another format to be used by a single (and slowly dying) specific OS was just not cost effective. Meanwhile, Google actually has support for it, breaks it, and we all blame Pandora for not keeping up?
Feh. I don't want broken codecs in my OS! I want to know that I can play my streaming audio from whatever source, my encoded movies, etc, and not have to worry if it is compatible with "google's new way of doing it" (which he's not specific about in the article either- why does the new way break the old one?).
/end off topic rant
Meanwhile, it doesn't say anywhere in that article that the bug is fixed now. Is it? Or is everyone expected to re-encode their stuff now if there is a problem? Because if the latter, I'm not sure I'd want to keep stagefright in my ROM... benchmark scores be damned!