My company is assessing various hardware video decoding and rendering path on Android. We come up with below solutions: 1. The perfect solution: comply to OpenMAX IL standards and write OMX components including OMX core and other components. The only modification made to Android would be placing component name @OMXCodec.cpp. Our components would be loaded through vendor plugin method. Unfortunately it's a rather heavy load. And we don't need OMX rather than for android, so it's a little bit of waste. 2. A slightly dirty modification: write decoders and renderer based on mediasource and awesomerenderer just like Android software decoders and render did. This requires a few modifications done to Awesomeplayer. And it's a lighter work. 3. Replace Awesomeplayer: not necessarily remove it, but add another player. This will lead the path further away, but it would be much easier consider we already have a full solution for linux. The only problem worries us though, is the Compatibility Test will be affected with the last solution? Though a quick search, I see compatibility tests are written in Java. Our solution won't change the APIs, so to my guess, compatibility won't be compromised, though I need confirmations.
-- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
