Hi Gaurav,

 

For media related libraries on celadon(libmfx_omx_core.so, libmfx_omx_components_hw.so, libmfxhw64.so, libva.so and i965_drv_video.so), please make sure OpenMax plugin is from https://github.com/projectceladon/mediasdk_release, mediasdk is from https://github.com/projectceladon/mediasdk, libva is from https://github.com/projectceladon/libva, and video driver is from https://github.com/projectceladon/media-driver, and they are built and installed correctly. If so, please check your android NDK version is available on Android P dessert. If it is other issue, we may not help with that…

 

Thanks,

 

Regards,

Tianmi

 

From: Gaurav Gupta [mailto:gaurav@trainingdata.io]
Sent: Thursday, May 23, 2019 3:35 PM
To: Sathish <satish.chevuru@gmail.com>
Cc: Chen, Tianmi <tianmi.chen@intel.com>; celadon@lists.01.org
Subject: Re: [01.org Celadon] UnsatisfiedLinkError: dlopen failed: cannot locate symbol "MFXClose" - Celadon PMR ww201913.xml Branch

 

Tianmi,

we have 2 problems:

1. our app's jni-shared-library is not able to load system libs from /vendor/lib/libmfxhw64.so (during runtime) 

    We have verified that our shared library was compiled against system shared library from OS-system folder

2. when we bundle the mediasdk shared libraries with our app, then dlopen fails for i965_drv_video.so

 

On Wed, May 22, 2019 at 10:01 PM Sathish <satish.chevuru@gmail.com> wrote:

Tianim,

 

     I built my "so" using  libmfxhw64, libva, libva-android.

 

     when i deploy the app that uses the "so", I get an error saying "libmfxhw64.so" not found, but where as, this is available in /vendor/lib64.

 

             E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: library "libmfxhw64.so" not found

                  

              celadon:/ # ls -lrt /vendor/lib64/ | grep mfx                                                                                                 

              -rw-r--r-- 1 root root   9359024 2008-12-31 18:30 libmfxhw64.so

 

   so I moved these "so" to app lib ( /data/app/com.tely.device.application.ng-vdrnqV3VvUEvNZBDZovteA==/lib/x86_64/ ) .

 

   then I get i965_drv_video.so dlopen failed error.

 

  All  "so"'s are available both in /vendor/lib64 and app lib ( /data/app/com.tely.device.application.ng-vdrnqV3VvUEvNZBDZovteA==/lib/x86_64/ )

 

Thanks,
Sathish

 

On Thu, May 23, 2019 at 9:11 AM Sathish <satish.chevuru@gmail.com> wrote:

Tianmi,

 

  The libraries (so) files are there in /vendor/lib64 , but the app is not able to load them , so I have moved them to app lib ( /data/app/com.tely.device.application.ng-vdrnqV3VvUEvNZBDZovteA==/lib/x86_64/ ).

 

|celadon:/vendor/lib64 # ls -lrt | grep va                                                                                                   

-rw-r--r-- 1 root root    158856 2008-12-31 18:30 libva.so
-rw-r--r-- 1 root root     10960 2008-12-31 18:30 libva-android.so
celadon:/vendor/lib64 # ls -lrt | grep 965                                                                                                    
-rw-r--r-- 1 root root  22067464 2008-12-31 18:30 i965_drv_video.so
celadon:/vendor/lib64 #

 

Thanks,

Sathish

 

On Thu, May 23, 2019 at 7:46 AM Chen, Tianmi <tianmi.chen@intel.com> wrote:

Hi Sathish,

 

Please make sure that libva you are using is from https://github.com/projectceladon/libva and media driver is from https://github.com/projectceladon/media-driver. So that libva.so and i965_drv_video.so can be installed correctly under /vendor/lib and /vendor/lib64/.

 

Thanks,

 

Regards,

Tianmi

 

From: Sathish [mailto:satish.chevuru@gmail.com]
Sent: Wednesday, May 22, 2019 2:48 AM
To: Chen, Tianmi <tianmi.chen@intel.com>
Cc: celadon@lists.01.org
Subject: Re: [01.org Celadon] UnsatisfiedLinkError: dlopen failed: cannot locate symbol "MFXClose" - Celadon PMR ww201913.xml Branch

 

Tianmi,

  

thank you. I was using the Intel-Media SDK and I moved to projectceladon Media SDK and able to move forward.

 

I am getting the below error though,  while loading the jni built with Media SDK.  

 

05-21 18:33:42.288 30819 30819 I libva   : VA-API version 1.2.0

05-21 18:33:42.288 30819 30819 I libva   : va_getDriverName() returns 0
05-21 18:33:42.288 30819 30819 I libva   : Trying to open /vendor/lib64//i965_drv_video.so
05-21 18:33:42.288 30819 30819 E linker  : library "/vendor/lib64//i965_drv_video.so" ("/vendor/lib64/i965_drv_video.so") needed or dlopened by "/data/app/com.tely.device.application.ng-vdrnqV3VvUEvNZBDZovteA==/lib/x86_64/libva.so" is not accessible for the namespace: [name="classloader-namespace", ld_library_paths="", default_library_paths="/data/app/com.tely.device.application.ng-vdrnqV3VvUEvNZBDZovteA==/lib/x86_64:/data/app/com.tely.device.application.ng-vdrnqV3VvUEvNZBDZovteA==/base.apk!/lib/x86_64", permitted_paths="/data:/mnt/expand:/data/data/com.tely.device.application.ng"]
05-21 18:33:42.288 30819 30819 E libva   : dlopen of /vendor/lib64//i965_drv_video.so failed: dlopen failed: library "/vendor/lib64//i965_drv_video.so" needed or dlopened by "/data/app/com.tely.device.application.ng-vdrnqV3VvUEvNZBDZovteA==/lib/x86_64/libva.so" is not accessible for the namespace "classloader-namespace"
05-21 18:33:42.288 30819 30819 I libva   : Trying to open /system/lib64/i965_drv_video.so
05-21 18:33:42.288 30819 30819 I libva   : va_openDriver() returns -1
05-21 18:33:42.289 30819 30819 F libc    : Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) in tid 30819 (.application.ng), pid 30819 (.application.ng)

 

For testing purpose , I moved the i965_drv_video.so to app lib path ( data/app/com.tely.device.application.ng-vdrnqV3VvUEvNZBDZovteA==/lib/x86_64/ ) , but still it is trying to load the  i965_drv_video.so from /vendor/lib64 which is not accessible to the app.

 

celadon:/data/app/com.tely.device.application.ng-vdrnqV3VvUEvNZBDZovteA==/lib/x86_64 # ls -lrt | grep  i965_drv_video.so
-rw-r--r-- 1 root   root   22067464 2019-05-21 18:33 i965_drv_video.so
celadon:/data/app/com.tely.device.application.ng-vdrnqV3VvUEvNZBDZovteA==/lib/x86_64 # 

 

Appreciate any inputs on this.

 

Thanks,
Sathish

 

On Mon, Apr 29, 2019 at 10:48 AM Chen, Tianmi <tianmi.chen@intel.com> wrote:

Hi Sathish,

The dlopen issue may be caused by the mismatch between msdk omx plugin and msdk os libraries. It is recommended to use mediasdk opensource from celadon code tree. Can we know where you get the msdk source code? Is it from https://github.com/projectceladon/MediaSDK or https://github.com/Intel-Media-SDK/MediaSDK ? There are some difference between them. If the second one is being used, there might be the mismatch issue.

Thanks,

Regards,
Tianmi

-----Original Message-----
From: Celadon [mailto:celadon-bounces@lists.01.org] On Behalf Of celadon-request@lists.01.org
Sent: Saturday, April 27, 2019 3:00 AM
To: celadon@lists.01.org
Subject: Celadon Digest, Vol 12, Issue 7

Send Celadon mailing list submissions to
        celadon@lists.01.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.01.org/mailman/listinfo/celadon
or, via email, send a message with subject or body 'help' to
        celadon-request@lists.01.org

You can reach the person managing the list at
        celadon-owner@lists.01.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of Celadon digest..."


Today's Topics:

   1. UnsatisfiedLinkError: dlopen failed: cannot locate symbol
      "MFXClose" - Celadon PMR ww201913.xml Branch (Sathish)


----------------------------------------------------------------------

Message: 1
Date: Fri, 26 Apr 2019 23:28:58 +0530
From: Sathish <satish.chevuru@gmail.com>
To: celadon@lists.01.org
Subject: [01.org Celadon] UnsatisfiedLinkError: dlopen failed: cannot
        locate symbol "MFXClose" - Celadon PMR ww201913.xml Branch
Message-ID:
        <CACzLWDL70AXKtt2fH+FBSj+mqXFTDtbPOg-nScQO1cbzL-N_sQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi,

 I am trying to use Intel Media SDK for video processing and I could not move further because of the below error.

The same was working with the celadon OMR1 older release. There the app was able to load the libraries from the /system/lib64 and /vendor/lib64.

But on PMR1 stable branch, I am seeing the below error. I bundling the dependant libraries inside app lib directory , but same behaviour.

Manifest branch: refs/tags/android-9.0.0_r18 Manifest merge branch: refs/heads/master Manifest groups: all,-notdefault
----------------------------

The command line program that uses the same Media SDK code is working fine, But when I use the code in a Application , I am not getting this error.

I moved all the libs from /system/lib64 and /vendor/lib64 to app library path , but still seeing this error.

Any suggestions/inputs is appreciated.

04-26 17:47:20.821 29559 29559 E AndroidRuntime: FATAL EXCEPTION: main
04-26 17:47:20.821 29559 29559 E AndroidRuntime: Process:
com.tely.device.application.ng, PID: 29559
04-26 17:47:20.821 29559 29559 E AndroidRuntime:
java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "MFXClose" referenced by "/data/app/com.tely.device.application.ng-E5zwZhHUurFlC_HEw_EmVA==/lib/x86_64/libmfx_omx_components_hw.so"...
04-26 17:47:20.821 29559 29559 E AndroidRuntime: at
java.lang.Runtime.loadLibrary0(Runtime.java:1016)
04-26 17:47:20.821 29559 29559 E AndroidRuntime: at
java.lang.System.loadLibrary(System.java:1669)
04-26 17:47:20.821 29559 29559 E AndroidRuntime: at
com.tely.media.core.JniLoader.loadJniLibraries(JniLoader.java:31)
04-26 17:47:20.821 29559 29559 E AndroidRuntime: at
com.tely.media.video.NewTelyCameraPreview.<clinit>(NewTelyCameraPreview.java:517)
04-26 17:47:20.821 29559 29559 E AndroidRuntime: at java.lang.Class.classForName(Native Method)
04-26 17:47:20.821 29559 29559 E AndroidRuntime: at
java.lang.Class.forName(Class.java:453)
04-26 17:47:20.821 29559 29559 E AndroidRuntime: at
java.lang.Class.forName(Class.java:378)
04-26 17:47:20.821 29559 29559 E AndroidRuntime: at
com.tely.device.application.ng.mediahal.TelyXLCameraPreview.Init(TelyXLCameraPreview.java:44)
04-26 17:47:20.821 29559 29559 E AndroidRuntime: at
com.tely.device.application.ng.mediahal.TelyXLCameraPreview.<init>(TelyXLCameraPreview.java:77)
04-26 17:47:20.821 29559 29559 E AndroidRuntime: at
com.tely.device.application.ng.mediahal.TelyCameraManager.getCamera(TelyCameraManager.java:43)
04-26 17:47:20.821 29559 29559 E AndroidRuntime: at
com.tely.device.application.ng.setup.frag.HomeFrag.createCameraXL(HomeFrag.java:1992)
04-26 17:47:20.821 29559 29559 E AndroidRuntime: at
com.tely.device.application.ng.setup.frag.HomeFrag$3.run(HomeFrag.java:1627)
04-26 17:47:20.821 29559 29559 E AndroidRuntime: at
android.os.Handler.handleCallback(Handler.java:873)
04-26 17:47:20.821 29559 29559 E AndroidRuntime: at
android.os.Handler.dispatchMessage(Handler.java:99)


Thanks,
Sathish
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.01.org/pipermail/celadon/attachments/20190426/a17cfab5/attachment-0001.html>

------------------------------

Subject: Digest Footer

Celadon mailing list
Celadon@lists.01.org
https://lists.01.org/mailman/listinfo/celadon


------------------------------

End of Celadon Digest, Vol 12, Issue 7
**************************************
--
Celadon mailing list
Celadon@lists.01.org
https://lists.01.org/mailman/listinfo/celadon

--
Celadon mailing list
Celadon@lists.01.org
https://lists.01.org/mailman/listinfo/celadon


 

--

Gaurav,

Co-founder, TrainingData.io

+1-917-386-3396

228 Webster Street,          Embassy Golf Links, 
Palo Alto,                            Domlur, Cinnabar Hills, 

CA, 94301                           Bangalore, KA 560071