[Katch]

Are we to assume that Herman's patched libstagefright.so is required for further testing and development of these builds on RK3066 SoCs? If so we could do with a link and explanation in the OP or we'll end up with a slew of problems stemming from users not having installed that file.

Indeed. Having a working libstagefright.so is only half the solution. The other half is getting it on the devices self.
I assume the level of post-sale support and updates differ greatly amongst the various device vendors, so It will be hard to have a one-size-fits-all.

As of now, I think the safe route is to keep blacklisting non-MOD16/32 vids, with the option of bypassing the blacklisting via advancedsettings.xml

---

Well, actually the one-size-fits-all solution would be that Rockchip renames the components in the corrected libstagefright.so, so that we can detect whether it's the fixed version or not, but that seems far-fetched.
A good one would maybe to somehow pass a version number in the metadata just after doing the OMXCodec::create...

I can't see the patched libstagefright.so making it into vendors ROMS & updates any time soon (if ever) - It is my understanding that OEMs are responsible for their own firmware and updates so they would need to pick up this fix and include it - I can't believe they are even aware of it.

So moving forward we need to assume that replacing the libstagefright.so is part of the installation process for RK3066 users unless they are using an aftermarket ROM that includes the fix - I will do what I can to disseminate the lib around the other RK3066 devs that I work with at Flashmyandroid and Slatedroid - but it will continue to be an issue for end users I feel...

Unfortunately I can see no easy way to distribute the patched lib as it requires Root and /system write access.

@Herman

Do Rockchip provide a base ROM to OEM vendors and will this patched libstagefright.so be included in future release through official channels?