News for hackers. Stuff that matters.
Re:Crashing competing media players on Android by jpk on Friday April 18, 2014 @01:59PM (#7610366)
"Since your average Android application does not have sufficient permission to access /dev/* entries on your system, you must use a proxy called the mediaserver in order to communicate with HW codecs."

This is incorrect. Application access to hardware de/encoders isn't a matter of permissions. You can't get at them directly because the api isn't in the SDK/NDK. However, if you're willing to pull in headers from AOSP, and fool around with dlopen/dlsym you can develop and build against libstagefright.

Re:Crashing competing media players on Android by flx42_ on Friday April 18, 2014 @02:41PM (#7610593)
It depends on your SoC, but most of the time your application won't be able to access HW codecs and then you have no choice but using the mediaserver. I think that if you pull OMX functions from libstagefright you are actually using IOMX, it's the regular OMX IL API but using IPC with the mediaserver.
Re:Crashing competing media players on Android by lcedp on Friday April 18, 2014 @08:38PM (#7612052)
I think both author and you are correct. There is a misunderstanding in the 'permission' term. Author uses it generally and you specifically as in Android permission.