Android NDK C++ JNI (no implementation found for native...)

AndroidAndroid Ndk

Android Problem Overview


I'm trying to use the NDK with C++ and can't seem to get the method naming convention correct. my native method is as follows:

extern "C" {
JNIEXPORT void JNICALL Java_com_test_jnitest_SurfaceRenderer_drawFromJni
(JNIEnv* env, jclass c)
{
   //
}
}

with a header wrapped in extern "C" {} aslo.

Everything compiles fine, creates a .so file and copies to the libs folder under my project, but when I debug and run in Eclipse I keep getting a log cat message that of "no implementation found for native...". Is there something i'm missing as all the NDK examples are in C?

Thanks.

Android Solutions


Solution 1 - Android

There are a couple of things that can lead to "no implementation found". One is getting the function prototype name wrong, another is failing to load the .so at all. Are you sure that System.loadLibrary() is being called before the method is used?

If you don't have a JNI_OnLoad function defined, you may want to create one and have it spit out a log message just to verify that the lib is getting pulled in successfully.

You already dodged the most common problem -- forgetting to use extern "C" -- so it's either the above or some slight misspelling. What does the Java declaration look like?

Solution 2 - Android

An additional cause for this error: your undecorated native method name must not contain an underscore!

For example, I wanted to export a C function named AudioCapture_Ping(). Here is my export declaration in C:

JNI_EXPORT int Java_com_obsidian_mobilehashhost_MainActivity_AudioCapture_Ping(JNIEnv *pJniEnv, jobject object);  //Notice the underscore before Ping

Here was my Java class importing the function:

package com.obsidian.mobileaudiohashhost;
...
public class MainActivity extends Activity {
    private native int AudioCapture_Ping();  // FAILS
    ...

I could not get Android to dynamically link to my native method until I removed the underscore:

JNI_EXPORT int Java_com_obsidian_mobilehashhost_MainActivity_AudioCapturePing(JNIEnv *pJniEnv, jobject object); 

package com.obsidian.mobileaudiohashhost;
...
public class MainActivity extends Activity {
    private native int AudioCapturePing();  // THIS WORKS!
    ...

Solution 3 - Android

I had the same problem, but to me the error was in the file Android.mk. I had it:

LOCAL_SRC_FILES := A.cpp
LOCAL_SRC_FILES := B.cpp 

but should have this:

LOCAL_SRC_FILES := A.cpp
LOCAL_SRC_FILES += B.cpp 

note the detail += instead :=

I hope that helps.

Solution 4 - Android

Called extern "C" as provided in the automatically-generated Studio example, but forgot to wrap the entire rest of the file, including following functions, in {} brackets. Only the first function worked.

Solution 5 - Android

Solution 6 - Android

An additional reason: Use LOCAL_WHOLE_STATIC_LIBRARIES instead of LOCAL_STATIC_LIBRARIES in android.mk. This stops the library from optimizing out unused API calls because the NDK cannot detect the use of the native bindings from java code.

Solution 7 - Android

Use javah (part of Java SDK). Its the tool exactly for this (generates .h header from .class file).

Solution 8 - Android

If your package name includes _ character, you should write 1(one) after _ character as shown below:

MainActivity.java

package com.example.testcpp_2;

native-lib.cpp

JNICALL
Java_com_example_testcpp_12_MainActivity_stringFromJNI(

Solution 9 - Android

I try all above solutions, but no one can solved my build error(jni java.lang.UnsatisfiedLinkError: No implementation found for...), at last I found that I forget to add my verify.cpp source file to CMakeList.txt add_library segement(verify.cpp is auto generate by Ctrl + Enter short key, maybe other file name), hope my response can help some one.

my build environment: Gradle + CMake

Solution 10 - Android

I Faced the same problem, and in my case the reason was that I had underscore in package name "RFID_Test" I renamed the Package and it worked. Thanks user1222021

Solution 11 - Android

I faced the same problem twice. It happened, that the phone I tried to start the app from Android Studio used an API level that I haven't downloaded yet in Android Studio.

  1. Upgrade Android Studio to the latest version
  2. Download the necessary API from within Android Studio

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionPatrick KafkaView Question on Stackoverflow
Solution 1 - AndroidfaddenView Answer on Stackoverflow
Solution 2 - Androiduser1222021View Answer on Stackoverflow
Solution 3 - Androidademar111190View Answer on Stackoverflow
Solution 4 - AndroidDragonLordView Answer on Stackoverflow
Solution 5 - AndroidMeghaView Answer on Stackoverflow
Solution 6 - AndroidJohn TwiggView Answer on Stackoverflow
Solution 7 - AndroidMartinHView Answer on Stackoverflow
Solution 8 - AndroidoiyioView Answer on Stackoverflow
Solution 9 - Androiduser2420449View Answer on Stackoverflow
Solution 10 - AndroidFiras ShrourouView Answer on Stackoverflow
Solution 11 - AndroidYuliweeView Answer on Stackoverflow