List
Visual SLAM Tool app on Epson Moverio Glasses BT-350
Posted Date: 2019-05-27 19:08     Edited Date: 2019-05-29 1:43     Writer: inactive



I'm using Visual SLAM Tool app on Epson Moverio Glasses BT-350 Android 5.1.1. When I'm trying to create map every time app back to the main menu

From Android Studio logs: 
05-27 19:04:49.927 2795-3385/? E/TinyAlsaStream: getFramesAvailable: Unable to get available frames
05-27 19:04:49.928 2795-3385/? E/TinyAlsaStream: getFramesAvailable: Unable to get available frames
05-27 19:04:49.928 2795-3385/? E/TinyAlsaStream: getFramesAvailable: Unable to get available frames
05-27 19:04:49.988 2795-3880/? E/BufferQueueProducer: [GraphicBufferSource] dequeueBuffer: BufferQueue has been abandoned
05-27 19:04:49.989 2297-2297/? E/SurfaceFlinger: [scrcpy] advanceFrame: no buffer, bailing out
05-27 19:04:49.989 2297-2297/? E/SurfaceFlinger: [scrcpy] failed pushing new frame to HWC: -12
05-27 19:04:50.014 2795-3441/? E/BufferQueueProducer: [GraphicBufferSource] cancelBuffer: BufferQueue has been abandoned
05-27 19:04:50.016 2795-3390/? E/wrs-omxil-core: OMX_GetHandle(): exit failure, OMX.Intel.hw_ve.h264 not found
05-27 19:04:50.046 5226-5226/? E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.maxst.visualslamtool, PID: 5226
    java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.maxst.visualslamtool-1/base.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]] couldn't find "libMaxstAR.so"
        at java.lang.Runtime.loadLibrary(Runtime.java:366)
        at java.lang.System.loadLibrary(System.java:988)
        at com.maxst.ar.MaxstARJNI.<clinit>(MaxstARJNI.java:11)
        at com.maxst.ar.MaxstAR.init(MaxstAR.java:24)
        at com.maxst.visualslamtool.ARActivity.onCreate(ARActivity.java:23)
        at com.maxst.visualslamtool.MapCreation.MapCreationActivity.onCreate(MapCreationActivity.kt:70)
        at android.app.Activity.performCreate(Activity.java:5994)
        at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1106)
        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2278)
        at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2387)
        at android.app.ActivityThread.access$800(ActivityThread.java:151)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1303)
        at android.os.Handler.dispatchMessage(Handler.java:102)
        at android.os.Looper.loop(Looper.java:135)
        at android.app.ActivityThread.main(ActivityThread.java:5258)
        at java.lang.reflect.Method.invoke(Native Method)
        at java.lang.reflect.Method.invoke(Method.java:372)
        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
05-27 19:04:50.068 2795-3390/? E/OMXNodeInstance: setParameter(5e:Intel.hw_ve.h264, OMX.google.android.index.enableAndroidNativeBuffers(0x6ff00003): Output:1 en=0) ERROR: UnsupportedIndex(0x8000101a)
05-27 19:04:50.241 2795-3872/? E/BufferQueueProducer: [GraphicBufferSource] setBufferCount: buffer owned by producer
05-27 19:04:50.241 2297-2297/? E/Surface: IGraphicBufferProducer::setBufferCount(5) returned Invalid argument
05-27 19:04:50.701 2795-4685/? E/BufferQueueProducer: [GraphicBufferSource] cancelBuffer: BufferQueue has been abandoned
05-27 19:04:50.710 2795-3441/? E/wrs-omxil-core: OMX_GetHandle(): exit failure, OMX.Intel.hw_ve.h264 not found
05-27 19:04:50.771 2795-3872/? E/OMXNodeInstance: setParameter(5f:Intel.hw_ve.h264, OMX.google.android.index.enableAndroidNativeBuffers(0x6ff00003): Output:1 en=0) ERROR: UnsupportedIndex(0x8000101a)
05-27 19:04:51.093 2795-3872/? E/BufferQueueProducer: [GraphicBufferSource] setBufferCount: buffer owned by producer
05-27 19:04:51.093 2297-2297/? E/Surface: IGraphicBufferProducer::setBufferCount(5) returned Invalid argument
 

Posted Date: 2019-05-29 1:43     Edited Date: 2019-05-29 1:43     Writer: inactive

Hi jileslak.
The 'BufferQueue has been abandoned' log also appears in our own Moverio. But you do not have to worry about it because your app is dead or not having any problems.

 

Leo

Maxst Support Team