Hey, Some users of my app report that after installing the OpenCV Manager and running my app they encounter a messagebox with error:
"OpenCV was not initialized correctly. Application will be shut down."
Also when they run the OpenCVManager app there's a the problem visible:
path: /data/app/org.opencv.engine-1/lib/arm64
2.4 - null
3.0 - libopencv_java3.so
So 2.4 doesn't get installed somehow and that's the problem probably? Cause on my device I got both 2.4 and 3.0 pointing to some libs. My project is using OpenCV 3.00 package. This is my android.mk file:
LOCAL_PATH := $(call my-dir)
include $(CLEAR_VARS)
include C:/OpenCV4Android/OpenCV-android-sdk/sdk/native/jni/OpenCV.mk
LOCAL_MODULE := myNativeLib
LOCAL_SRC_FILES := myNativeLib.cpp
LOCAL_LDLIBS += -llog -ldl
include $(BUILD_SHARED_LIBRARY)
Maybe I lack sth here? But since I'm using the async initialisation I guess I don't have to add anything here...
This occurs on devices Meizu MX5 and LG G4 for example. I haven't found this reported as a bug but this issue is similar to http://answers.opencv.org/question/71799/opencv-manager-on-samsung-galaxy-edge/
Is there maybe some reliable work-around to fix the issue? I don't quite understand the solution in the above link. Does it mean I should statically link a concrete OpenCV version? Won't it cause more bad than good? If there's no solution I quess I should submit a bug. Anyway, I would be really very grateful for your time and support!