Not able to run the sample Android project

[LabN36]

hi i followed each step to run the eegeo android sample but every try was unsuccessful please find the below screen shot about the error, please guide me how can i remove and run this project successfully.

[murdoch-david]

Hi Rishabh Agrawal,

Thanks for letting us know.

Could you confirm the following:

• Which version of Eclipse you are using?
• What operating system and version is your setup running on?
• Which version of the Android SDK Tools are you using?

Regards,

David

[LabN36]

Eclipse: Version: Kepler Service Release 2
OS: Windows 7
Android SDK: Android Development Toolkit Version: 23.0.7.2120684

Hear are the steps that i follow from scratch to give 4th chance to run this project please guide what I'm doing wrong

Step1: Cloning the project eegeo-sdk-sample

Step2: Cd into directory and running update.platform.sh -p android command

after running this command i think some build files and generated in System or something

Step3: Adding NDK SetUp r10e

Step4: Importing project in Eclipse

Step5: after that I was adding 'Add Native Support' in the project

as soon as i clicks Finish Button my eclipse Hanged and nothing is Happening after that, earlier when i was importing this project in the same way i've not faced this problem by don't know what going wrong

please see this image too for android Depandancy reference

I was trying to run this project multiple times but every single attempt was unsuccessful please guide.

[murdoch-david]

Hi Rishabh Agrawal,

Thanks for the additional information. Can you confirm if you have run through the following troubleshooting guide?

https://github.com/eegeo/eegeo-sdk-samples/tree/master/android#eclipse-hangs-adding-native-support

Regards,

David

[LabN36]

Hi,
Thanks for pointing out the troubleshooting guide now I'm not facing any problem but when I'm running this application i got this error log

07-11 20:08:56.391: I/System.out(18764): waiting for debugger to settle...
07-11 20:08:56.591: I/System.out(18764): waiting for debugger to settle...
07-11 20:08:56.791: I/System.out(18764): debugger has settled (1307)
07-11 20:08:57.072: W/dalvikvm(18764): Exception Ljava/lang/UnsatisfiedLinkError; thrown while initializing Lcom/eegeo/mobilesdkharness/BackgroundThreadActivity;
07-11 20:08:57.072: W/dalvikvm(18764): Class init failed in newInstance call (Lcom/eegeo/mobilesdkharness/BackgroundThreadActivity;)
07-11 20:08:57.072: W/dalvikvm(18764): threadid=1: thread exiting with uncaught exception (group=0x4163e3a8)
07-11 20:08:57.142: E/AndroidRuntime(18764): FATAL EXCEPTION: main
07-11 20:08:57.142: E/AndroidRuntime(18764): java.lang.ExceptionInInitializerError
07-11 20:08:57.142: E/AndroidRuntime(18764): at java.lang.Class.newInstanceImpl(Native Method)
07-11 20:08:57.142: E/AndroidRuntime(18764): at java.lang.Class.newInstance(Class.java:1319)
07-11 20:08:57.142: E/AndroidRuntime(18764): at android.app.Instrumentation.newActivity(Instrumentation.java:1069)
07-11 20:08:57.142: E/AndroidRuntime(18764): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2262)
07-11 20:08:57.142: E/AndroidRuntime(18764): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2391)
07-11 20:08:57.142: E/AndroidRuntime(18764): at android.app.ActivityThread.access$600(ActivityThread.java:151)
07-11 20:08:57.142: E/AndroidRuntime(18764): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1335)
07-11 20:08:57.142: E/AndroidRuntime(18764): at android.os.Handler.dispatchMessage(Handler.java:99)
07-11 20:08:57.142: E/AndroidRuntime(18764): at android.os.Looper.loop(Looper.java:155)
07-11 20:08:57.142: E/AndroidRuntime(18764): at android.app.ActivityThread.main(ActivityThread.java:5520)
07-11 20:08:57.142: E/AndroidRuntime(18764): at java.lang.reflect.Method.invokeNative(Native Method)
07-11 20:08:57.142: E/AndroidRuntime(18764): at java.lang.reflect.Method.invoke(Method.java:511)
07-11 20:08:57.142: E/AndroidRuntime(18764): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1058)
07-11 20:08:57.142: E/AndroidRuntime(18764): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:825)
07-11 20:08:57.142: E/AndroidRuntime(18764): at dalvik.system.NativeStart.main(Native Method)
07-11 20:08:57.142: E/AndroidRuntime(18764): Caused by: java.lang.UnsatisfiedLinkError: Couldn't load eegeo-sdk-samples: findLibrary returned null
07-11 20:08:57.142: E/AndroidRuntime(18764): at java.lang.Runtime.loadLibrary(Runtime.java:365)
07-11 20:08:57.142: E/AndroidRuntime(18764): at java.lang.System.loadLibrary(System.java:535)
07-11 20:08:57.142: E/AndroidRuntime(18764): at com.eegeo.mobilesdkharness.BackgroundThreadActivity.(BackgroundThreadActivity.java:23)
07-11 20:08:57.142: E/AndroidRuntime(18764): ... 15 more

[ian-hutchinson]

Hi Rishabh Agrawal,

Sorry that you're still having trouble setting up the SDK Samples for Android.

It looks to me like the compiled native C++ code is missing from your APK - the runtime exception is thrown because the application can't find the eegeo-sdk-samples shared library within the APK.

Usually, this happens when the C++ code fails to compile, though typically I'd expect to see some output in the build log.

Are you able to confirm that:
a) After following the workaround to fix the hang in Eclipse you've reverted the changes to Android.mk and saved the file prior to building? Eclipse doesn't automatically save files by default, so it's possible that you might be building with an empty makefile. This would explain why there'd be no C++ build errors.

b) If your makefile has been saved, can you confirm that you see output in the console when performing a full clean build of your app? You should see output denoting which C++ files are being compiled (See screenshot below). If there are legitimate failures with the C++, you should see them here. If you don't see the C++ files being compiled here then it's possible that something is wrong with the makefile - perhaps that it's not picking up the source files for some reason.

Best,
Ian