Running android native code is causing java.lang.UnsatisfiedLinkError

Question

I have an android app with native code where I use openCV library. When running the app in phone everything is working well but when I try to run it on tablet(Lenovo yoga 2 pro) I am encountering this error:

01-03 11:53:13.007: E/AndroidRuntime(25632): FATAL EXCEPTION: main
01-03 11:53:13.007: E/AndroidRuntime(25632): Process: <appname>, PID: 25632
01-03 11:53:13.007: E/AndroidRuntime(25632): java.lang.UnsatisfiedLinkError: dlopen failed: "/data/app-lib/<appname>/libnative_module.so" has unexpected e_machine: 40
01-03 11:53:13.007: E/AndroidRuntime(25632):    at java.lang.Runtime.loadLibrary(Runtime.java:364)
01-03 11:53:13.007: E/AndroidRuntime(25632):    at java.lang.System.loadLibrary(System.java:526)
01-03 11:53:13.007: E/AndroidRuntime(25632):    at <appname>.SplashActivity$1.onManagerConnected(SplashActivity.java:35)
01-03 11:53:13.007: E/AndroidRuntime(25632):    at org.opencv.android.AsyncServiceHelper$1.onServiceConnected(AsyncServiceHelper.java:318)
01-03 11:53:13.007: E/AndroidRuntime(25632):    at android.app.LoadedApk$ServiceDispatcher.doConnected(LoadedApk.java:1127)
01-03 11:53:13.007: E/AndroidRuntime(25632):    at android.app.LoadedApk$ServiceDispatcher$RunConnection.run(LoadedApk.java:1144)
01-03 11:53:13.007: E/AndroidRuntime(25632):    at android.os.Handler.handleCallback(Handler.java:733)
01-03 11:53:13.007: E/AndroidRuntime(25632):    at android.os.Handler.dispatchMessage(Handler.java:95)
01-03 11:53:13.007: E/AndroidRuntime(25632):    at android.os.Looper.loop(Looper.java:149)
01-03 11:53:13.007: E/AndroidRuntime(25632):    at android.app.ActivityThread.main(ActivityThread.java:5283)
01-03 11:53:13.007: E/AndroidRuntime(25632):    at java.lang.reflect.Method.invokeNative(Native Method)
01-03 11:53:13.007: E/AndroidRuntime(25632):    at java.lang.reflect.Method.invoke(Method.java:515)
01-03 11:53:13.007: E/AndroidRuntime(25632):    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:825)
01-03 11:53:13.007: E/AndroidRuntime(25632):    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:641)
01-03 11:53:13.007: E/AndroidRuntime(25632):    at dalvik.system.NativeStart.main(Native Method)

this is on the line 45 in SplashActivity:

System.loadLibrary("native_module");

Can someone help me to solve this error? or What am I doing wrong?

See sco.com/developers/gabi/2000-07-17/ch4.eheader.html: e_machine=40 means EM_ARM. — Alex Cohn
– Alex Cohn, Commented Jan 3, 2015 at 19:10

Community · Accepted Answer · 2017-05-23 12:25:47Z

4

Your tablet is based on Intel Atom CPU. You must build your native_module for APP_ABI=x86. Note that you also need the compatible version of OpenCV.

Update: in this particular case, the app was built for both x86 and ARM. But the app installer chose the wrong subfolder, maybe because the filenames listed in libs/x86 and libs/armeabi did not exactly match. The reliable and efficient approach for apps that have non-trivial native component is to upload separate APKs to PlayStore.

edited May 23, 2017 at 12:25

CommunityBot

11 silver badge

answered Jan 3, 2015 at 15:54

Alex Cohn

57.4k11 gold badges127 silver badges332 bronze badges

Sign up to request clarification or add additional context in comments.

13 Comments

mark Over a year ago

I thought the same thing and I checked the APP_ABI but it is set like this: APP_ABI := armeabi armeabi-v7a x86 mips so it should be ok. How do you mean the compatible version of OpenCV? because when I downloaded the openCV for android there was no option for choosing the processor type

Alex Cohn Over a year ago

Do you use shared or static version of OpenCV?

mark Over a year ago

In my project I have directory libs where are subfolders with .so and .a libraries for different processor types(these subfolders are from downloaded opencv project for android, in folder structure sdk/native/libs). And then I have linked opencv android project in eclipse(sdk/java).

Alex Cohn Over a year ago

You can verify the contents of the libs/ folder of your Eclipse project. In C/C++ perspective, you can see "binaries" tab, and it will list the so files that you have, marked for architecture (x86/arm/whatever). But you should also check which files are actually installed on the device.

mark Over a year ago

How can I check which files are installed on device? But to run the app I had to download opencv manager app and this app is working(does not crash) so it is bit weird.

|

Geraldo Neto · Accepted Answer · 2016-01-08 07:37:34Z

0

I have an Asus Zenfone 5 (which uses the x86 ABI) and I was having the same problem. Apparently the problem was with the OpenCV 2.x versions. Start using the OpenCV 3.x version and the problem is going to be solved.

The OpenCV 3.x version has more ABI options, such as:

arm64v8a
arm
armv7a
mips
mips64
x86
x86-64

You can find the 3.x version here.

Hope it helped!

answered Jan 8, 2016 at 7:37

Geraldo Neto

4,1401 gold badge36 silver badges37 bronze badges

Collectives™ on Stack Overflow

Running android native code is causing java.lang.UnsatisfiedLinkError

2 Answers 2

13 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

13 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related