三星SPen SDK演示立即崩溃

时间:2013-10-19 13:04:59

标签: android android-emulator samsung-mobile

我尝试使用Samsung SPen SDK(http://developer.samsung.com/android/technical-docs/S-Pen-SDK-2-3-Tutorial),但是只要我使用它,我的模拟器就会立即崩溃。 SDK-Demo也不能在模拟器上运行 - 它启动了,但是只要我从listview中选择一个演示,我就会直接强制关闭。

模拟器的数据:

  • 设备:Nexus 7
  • Android 4.3 Api等级18
  • Intel Atom(x86)
  • 内存:
    • Ram:1024
    • VM-Heap:32
  • 内部存储:200 MB
  • 使用主机GPU:true

对于简单的代码更改,我不想每次都需要获取设备。是否有“技巧”让它发挥作用?

提前致谢!

更新 按照此处的要求,在发生错误时跟踪logcat的堆栈跟踪

  

10-19 14:27:55.473:D / dalvikvm(2001):VFY:在0x0032处替换操作码0x6e

     

10-19 14:27:55.493:E / SDraw(2001):不支持在此设备上运行此引擎。 (品牌:generic_x86,制造商:未知)

     

10-19 14:27:55.563:E / CB :: BeautifyNative(2001):警告:无法加载libjni_secime natives

更新2: 当我使用模拟器库并尝试打开SPenGestureLibrary时,我得到以下stacktrace。我有“代码”:

public MainActivity extends ActivityWithSPenLayer

我在overriden方法中使用super.onCreateOptionsMenu(menu)

10-19 14:40:10.574: E/AndroidRuntime(2179): FATAL EXCEPTION: main
10-19 14:40:10.574: E/AndroidRuntime(2179): java.lang.UnsatisfiedLinkError: Couldn't load SPenGesture from loader dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.example.testappforgesturelibrary-1.apk"],nativeLibraryDirectories=[/data/app-lib/com.example.testappforgesturelibrary-1, /system/lib]]]: findLibrary returned null
10-19 14:40:10.574: E/AndroidRuntime(2179):     at java.lang.Runtime.loadLibrary(Runtime.java:355)
10-19 14:40:10.574: E/AndroidRuntime(2179):     at java.lang.System.loadLibrary(System.java:525)
10-19 14:40:10.574: E/AndroidRuntime(2179):     at com.samsung.spen.engine.gesture.SPenGestureEngineJni.<init>(SourceFile:7)
10-19 14:40:10.574: E/AndroidRuntime(2179):     at com.samsung.spen.engine.gesture.a.a(SourceFile:61)
10-19 14:40:10.574: E/AndroidRuntime(2179):     at com.samsung.spen.lib.gesture.SPenGestureLibrary.openSPenGestureEngine(SourceFile:122)
10-19 14:40:10.574: E/AndroidRuntime(2179):     at com.example.testappforgesturelibrary.MainActivity.onCreate(MainActivity.java:38)
10-19 14:40:10.574: E/AndroidRuntime(2179):     at android.app.Activity.performCreate(Activity.java:5133)
10-19 14:40:10.574: E/AndroidRuntime(2179):     at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1087)
10-19 14:40:10.574: E/AndroidRuntime(2179):     at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2175)
10-19 14:40:10.574: E/AndroidRuntime(2179):     at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2261)
10-19 14:40:10.574: E/AndroidRuntime(2179):     at android.app.ActivityThread.access$600(ActivityThread.java:141)
10-19 14:40:10.574: E/AndroidRuntime(2179):     at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1256)
10-19 14:40:10.574: E/AndroidRuntime(2179):     at android.os.Handler.dispatchMessage(Handler.java:99)
10-19 14:40:10.574: E/AndroidRuntime(2179):     at android.os.Looper.loop(Looper.java:137)
10-19 14:40:10.574: E/AndroidRuntime(2179):     at android.app.ActivityThread.main(ActivityThread.java:5103)
10-19 14:40:10.574: E/AndroidRuntime(2179):     at java.lang.reflect.Method.invokeNative(Native Method)
10-19 14:40:10.574: E/AndroidRuntime(2179):     at java.lang.reflect.Method.invoke(Method.java:525)
10-19 14:40:10.574: E/AndroidRuntime(2179):     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:737)
10-19 14:40:10.574: E/AndroidRuntime(2179):     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
10-19 14:40:10.574: E/AndroidRuntime(2179):     at dalvik.system.NativeStart.main(Native Method)

1 个答案:

答案 0 :(得分:1)