Ask Your Question

target33's profile - activity

2018-01-01 19:56:01 -0500 received badge  Popular Question (source)
2017-01-29 13:48:35 -0500 received badge  Taxonomist
2014-06-01 04:36:51 -0500 commented answer OpenCV build options, big difference in speed after android library linking

Hi, thanks for the answer. Are those NVIDIA optimization also acting on non-Tegra SoC? Because currently I'm developing on a Galaxy S2 device and as far as I know, it doesn't have a Tegra SoC..

2014-05-31 09:08:14 -0500 received badge  Student (source)
2014-05-31 08:49:11 -0500 asked a question OpenCV build options, big difference in speed after android library linking

Hi, Until now I used OpenCV4Android coupled with the opencv manager to experiment with ORB features performance on android devices. Now I need to modify an opencv function (for testing) so I switched to OpenCVLoader.initDebug() interface (instead of OpenCVLoader.initAsync()), by linking "" inside android project libs. Everything works fine as expected (currently I've done no changes to opencv source yet).

The only problem regards speed. No matter which options I use to compile opencv from trunk, if I link from my opencv build, I get almost half the framerate from my feature detector android program. To be sure it wasn't my fault, I extracted "" from apk file inside OpenCV4Android SDK (exactly, I extracted it from OpenCV_2.4.9_Manager_2.18_armv7a-neon.apk which is mainly a zip file) and linked it to my android program (no changes made, only linking with extracted Doing this I get full speed back. It seems that the build options of the openCV manager optimize the code same way..

The question is: which options have been used to build opencv manager? Or better, the libraries used during Manager compilation? Currently, the options used to build OpenCV_2.4.9_Manager_2.18_armv7a-neon.apk? I tried any option available (I think), especially the NEON ones, with no improvement. Also, if I link obtained from "OpenCV-2.4.9-android-sdk\sdk\native\libs\armeabi-v7a\" I get the same issue, so this means that opencv manager has been compiled with different options.

As additional note, if I install opencv manager from play store, it says my device uses armeabi-v7a with NEON.

These are the options I tried so far compiling "" from latest repository (I'm using Ubuntu):


I need to know with options have been used to compile the library used in opencv manager. I don't need to recompile the manager, only to recompile the same way.



P.S. maybe has intel IPP been installed and used inside library building? This is the only thing I didn't try yet...

2014-02-14 07:37:05 -0500 received badge  Supporter (source)