System.loadLibrary(…) couldn’t find native library in my case

by

To root cause (and maybe solve your issue in the same time), here is what you can do:

  1. Remove the jni folder and all the .mk files. You don’t need these nor the NDK if you aren’t compiling anything.

  2. Copy your libcalculate.so file inside <project>/libs/(armeabi|armeabi-v7a|x86|...) . When using Android Studio, it’s <project>/app/src/main/jniLibs/(armeabi|armeabi-v7a|x86|...), but I see you’re using eclipse.

  3. Build your APK and open it as a zip file, to check that your libcalculate.so file is inside lib/(armeabi|armeabi-v7a|x86|…).

  4. Remove and install your application

  5. Run dumpsys package packages | grep yourpackagename to get the nativeLibraryPath or legacyNativeLibraryDir of your application.

  6. Run ls on the nativeLibraryPath you had or on legacyNativeLibraryDir/armeabi, to check if your libcalculate.so is indeed there.

  7. If it’s there, check if it hasn’t been altered from your original libcalculate.so file: is it compiled against the right architecture, does it contain the expected symbols, are there any missing dependencies. You can analyze libcalculate.so using readelf.

In order to check step 5-7, you can use my application instead of command lines and readelf: Native Libs Monitor

PS: It’s easy to get confused on where .so files should be put or generated by default, here is a summary:

  • libs/CPU_ABI inside an eclipse project

  • jniLibs/CPU_ABI inside an Android Studio project

  • jni/CPU_ABI inside an AAR

  • lib/CPU_ABI inside the final APK

  • inside the app’s nativeLibraryPath on a <5.0 device, and inside the app’s legacyNativeLibraryDir/CPU_ARCH on a >=5.0 device.

Where CPU_ABI is any of: armeabi, armeabi-v7a, arm64-v8a, x86, x86_64, mips, mips64. Depending on which architectures you’re targeting and your libs have been compiled for.

Note also that libs aren’t mixed between CPU_ABI directories: you need the full set of what you’re using, a lib that is inside the armeabi folder will not be installed on a armeabi-v7a device if there are any libs inside the armeabi-v7a folder from the APK.

More Related Contents:

  1. Google Play and OpenSSL warning message
  2. How to build an executable for Android shell
  3. How to use addr2line in Android
  4. How To Get File In Assets From Android NDK
  5. What is the best way to save JNIEnv*
  6. How can I catch SIGSEGV (segmentation fault) and get a stack trace under JNI on Android?
  7. Android NDK: dlopen failed
  8. How to link a prebuilt shared Library to an Android NDK project?
  9. Calling native method twice of third party library in an Activity causes the Android application to close down
  10. Using FFmpeg with Android-NDK
  11. Android NDK C++ JNI (no implementation found for native…)
  12. how to use mkfifo using Android’s NDK
  13. Android – build separate APKs for different processor architectures
  14. NDK: how include *.so files in AndroidStudio
  15. Add pre-built .so files in project using Android Gradle plugin 0.7.3
  16. How to compile ffmpeg-2.2.2 on windows with cygwin and android ndk r9c
  17. How to play multiple video files simultaneously in one layout side by side in different view in Android
  18. Android: How to integrate a decoder to multimedia framework
  19. How to compile C into an executable binary file and run it in Android from Android Shell?
  20. Creating a product SDK: How do I add a native lib (.so) and a jar with the SDK I am creating?
  21. How to access resource with dynamic name in my case?
  22. How to Find memory leaks from native code in android
  23. NDK – problems after GNUSTL has been removed from the NDK (revision r18)
  24. After updating Android Studio to version 1.3.0 I am getting “NDK integration is deprecated in the current plugin” Error
  25. What is the Log API to call from an Android JNI program?
  26. WebP for Android [closed]
  27. Eclipse Juno ADT plugin NDK path removed?
  28. Javah Error android.app.Activity not found
  29. Error adding prebuilt apk with shared libraries to AOSP
  30. WARNING: ABIs [armeabi-v7a,armeabi] set by ‘android.injected.build.abi’ gradle flag contained ‘ARMEABI’ not targeted by this project

Leave a Comment