Although the Google Play Store version of OpenCV Manager hasn't been updated since OpenCV 3.0.0, I see new builds in the apk folder of the OpenCV Android 3.2.0 release (from http://opencv.org/downloads.html). Choose the APK that matches your Android device's architecture, and sideload it using ADB. For example, if you are using an armeabi-v7a device, run this in the command prompt:
adb install OpenCV_3.2.0_Manager_3.20_armeabi-v7a.apk
[Edit 1] Of course, if you're concerned about easily distributing your app to other people, you shouldn't depend on a version of OpenCV Manager that has to be sideloaded. However, if your app is just for your use or internal organizational use, this might be fine.
[Edit 2] I've opened an issue at https://github.com/opencv/opencv/issues/8120 to request that the latest builds be published to Google Play Store.
Thanks Joseph! I followed the 4th step of the instructions from: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ (http://www.howtogeek.com/125769/how-t...) to add the desirable architecture (armeabi-v7a version in my case) via my command prompt. It worked like a charm :)
the opencv manager app has not been updated since opencv3.0.0.
please try with static initialization in the meantime.
Thanks for the quick reply @berak. I've tried the static initialization for OpenCV 3.2.0 but at the third step, I'm not sure which target architecture that I should be copying over. OpenCV library 3.2.0 has a bunch of .so files, one for: arm64-v8a armeabi armeabi-v7a mips mips64 x86 and x86_64. Do I just copy over all of these? In my project's libs folder, I only see .jar files.
To maximize compatibility, yes, copy all of the libs subfolders. Thus, your project's libs folder will have subfolders arm64-v8a, armeabi, armeabi-v7a, mips, mips64, x86, and x86_64.
Asked: 2017-02-01 05:14:49 -0600
Seen: 2,348 times
Last updated: Feb 02 '17
