Ehm, the "jni/" directory contains the source for those files. Running "ndk-build" (from Android NDK) in top-level dir will recompile them.
Looking at the source the libraries contain AES code, libjpeg, libwebp and libyuv to handle image decoding, some image blur algorithms and video NV21-YUV conversion routines.
Nothing out of the ordinary for an Android app - offloading CPU intensive stuff to C/C++ where it's almost always noticably slower.
Can you please, PLEASE, check your facts before jumping the gun next time?
Comments
Ehm, the "jni/" directory contains the source for those files. Running "ndk-build" (from Android NDK) in top-level dir will recompile them.
Looking at the source the libraries contain AES code, libjpeg, libwebp and libyuv to handle image decoding, some image blur algorithms and video NV21-YUV conversion routines.
Nothing out of the ordinary for an Android app - offloading CPU intensive stuff to C/C++ where it's almost always noticably slower.
Can you please, PLEASE, check your facts before jumping the gun next time?
I retract my statement. This used to be the case, but appears to no longer be so.