adb disable-verity

adb reboot

It might boot to recovery mode, then you need choose reset factory

adb remount

Then, push the file and change anything.

 

From: Sathish [mailto:satish.chevuru@gmail.com]
Sent: Wednesday, July 24, 2019 11:50 AM
To: Zhang, Yanmin <yanmin.zhang@intel.com>
Cc: celadon@lists.01.org; Chen, Tianmi <tianmi.chen@intel.com>; Cao, Jenny Q <jenny.q.cao@intel.com>; Lin, Johnson <johnson.lin@intel.com>
Subject: Re: [01.org Celadon] "not accessible for the namespace" error while loading an "so" file

 

Yanmin,

 

I tried this and it says "/vendor/etc" as a read only file system and failed to copy the file.

 

sathish@ubuntuIA:~/TelyCode_IA/logs/stability/july22$ adb push public.libraries.txt /vendor/etc

adb: error: failed to copy 'public.libraries.txt' to '/vendor/etc/public.libraries.txt': remote couldn't create file: Read-only file system
public.libraries.txt: 0 files pushed. 0.0 MB/s (51 bytes in 0.004s)

 

celadon:/vendor/etc # touch test.txt
touch: 'test.txt': Read-only file system
1|celadon:/vendor/etc # 

 

I earlier bundled all the dependant libraries in the application lib, based on the suggestion from android help link you mentioned above.

 

Thanks,

Sathish

 

 

 

On Tue, Jul 23, 2019 at 12:49 PM Zhang, Yanmin <yanmin.zhang@intel.com> wrote:

Sathish,

 

Since Android N, apk need call official API. All access to private libraries will be blocked.

https://developer.android.com/about/versions/nougat/android-7.0-changes

 

You can work around it by:

1)      Add the shared object file names into a config file:

ymzhang@ymzhang:~/android/data/logs/KBL$ cat public.libraries.txt

i965_drv_video.so

libva.so

libdrm.so

libgmm_umd.so

ymzhang@ymzhang:~/android/data/logs/KBL$ adb push public.libraries.txt /vendor/etc/

 

2)      After booting, run: adb shell setenforce 0

 

You app can start to a red window on my KBL.

 

Yanmin

 

From: Celadon [mailto:celadon-bounces@lists.01.org] On Behalf Of Zhang, Yanmin
Sent: Wednesday, July 17, 2019 8:44 AM
To: Sathish <satish.chevuru@gmail.com>; celadon@lists.01.org
Cc: Chen, Tianmi <tianmi.chen@intel.com>; Xiao, Jin <jin.xiao@intel.com>
Subject: Re: [01.org Celadon] "not accessible for the namespace" error while loading an "so" file

 

+Jin, Tianmi.

 

I remember you raised the similar issue 2 months ago. It seems not resolved.

 

From: Celadon [mailto:celadon-bounces@lists.01.org] On Behalf Of Sathish
Sent: Wednesday, July 17, 2019 1:50 AM
To: celadon@lists.01.org
Subject: [01.org Celadon] "not accessible for the namespace" error while loading an "so" file

 

Hi,

 

 I am getting the below error while deploying an application no NUC7i7BNH with celadon PMR.

 

The library is available in the given path, but unable to load the library and reporting not accessible for the namespace error.

 

 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-AHAaUmOTFd5Uvd1ECUGs6A==/lib/x86_64/libva.so" is not accessible for the namespace "classloader-namespace"

 

E libva   : dlopen of /system/lib64/i965_drv_video.so failed: dlopen failed: library "/system/lib64/i965_drv_video.so" needed or dlopened by "/data/app/com.tely.device.application.ng-AHAaUmOTFd5Uvd1ECUGs6A==/lib/x86_64/libva.so" is not accessible for the namespace "classloader-namespace"

 

Appreciate your inputs on this.

 

Thanks,

Sathish