How do you know stagefright is broken with h264? Prove it
Could that not be due to the broken eAAC + AAC portions of stagefright?
Apparently they produce lower quality results which I assume is due to the codec not operating fully thus faster.
Anyway IF 264 is broken on stagefright somone better tell google
The only mentions are the green bar appearing on youtube videos which some people have claimed is due to the heap size (considering an incorrect hep size can distort the camera viewfinder and other videos Im inclined to believe this).
I have used a rom for a while with stagefright fully enabled and a large heap size and I have NEVER had an issue. (Based on softbank, compiled kernel from ZTE-BLADE git repo, stock google apps with beebplayer and the Gingerbread theme, launcher and keyb)
Can not be proven, as the Android system is smart enough, knows that there are two codecs, and if one's broken, it uses the other.
Stagefright is broken on MSM7x27 series CPUs, and even if there's no Google Code report (afaik, the official Google repo does not support MSM7x27 out-of-the-box and was never planned to do so), it is simply BROKEN. Accept it.
Also why tell google when they've already fixed it?
Also, you may prove yourself it is broken - try to play any HQ youtube video (what is streamed in MP4 container using H.264 encoder and AAC sound), it will fail to play the video (and no, it isn't a problem with the CPU not being capable of playing HQ, it is simply the failing Stagefright player).
You, sir, are heavily trolling. Accept what competent people say, the people who discovered the bug. They know what they are talking about, and believe me if they were wrong they would accept it. But, so far only you are the exception of this bug, and as you haven't wrote your ROM and phone version, we don't even know how you achieved it. So take back, and try to be more polite.