Obsolete
Status Update
Comments
su...@gmail.com <su...@gmail.com> #2
attaching the snapshot of the configuration of arm64 emulator
su...@gmail.com <su...@gmail.com> #5
Hi,
We have narrowed down that renderScript usage in our project is causing the above issue.
If we remove renderScript usage from project it is installing on 64 bit devices.
To remove renderscript usage we have done following changes to project
1)Removed below tags form build.gradle
renderscriptTargetApi 19
renderscriptSupportModeEnabled true
2) Removed below renderscript related source files from src subfolders
Brightness.rs
ColorClamp.rs
Convolve.rs
When we compile the project with renderScript and with "ndk { abiFilters 'arm64-v8a' }" for 64 bit, we see that only 64 bit .so files are packed into apk even for renderscript generated native libraries.
How ever we are not sure why application is falling back to 32 bit on a 64 bit device.
Attaching the zip of appcode.
Any additional inputs on why inclusion of render script is causing the issue though we specify 64 bit ndk abi filters.
We have narrowed down that renderScript usage in our project is causing the above issue.
If we remove renderScript usage from project it is installing on 64 bit devices.
To remove renderscript usage we have done following changes to project
1)Removed below tags form build.gradle
renderscriptTargetApi 19
renderscriptSupportModeEnabled true
2) Removed below renderscript related source files from src subfolders
Brightness.rs
ColorClamp.rs
Convolve.rs
When we compile the project with renderScript and with "ndk { abiFilters 'arm64-v8a' }" for 64 bit, we see that only 64 bit .so files are packed into apk even for renderscript generated native libraries.
How ever we are not sure why application is falling back to 32 bit on a 64 bit device.
Attaching the zip of appcode.
Any additional inputs on why inclusion of render script is causing the issue though we specify 64 bit ndk abi filters.
mi...@google.com <mi...@google.com> #6
The problem is that renderscriptTargetApi 19 will generate .bc files in /res/raw/. And PackageManager will install apks with .bc files as 32bit applications.
The solution is simple:
renderscriptTargetApi 21
renderscriptSupportModeEnabled true
Your application should then work fine, since renderscriptTargetApi 21+ will not generate .bc files in /res/raw any more.
The solution is simple:
renderscriptTargetApi 21
renderscriptSupportModeEnabled true
Your application should then work fine, since renderscriptTargetApi 21+ will not generate .bc files in /res/raw any more.
su...@gmail.com <su...@gmail.com> #7
Hi,
The application is now getting installed on 64 bit devices, but causing another problem i.e., renderscript api's are failing, as there are no .bc files generated under raw folder.
It is searching for resources under raw folder throwing error:
W ResourceType: No package identifier when getting value for resource number 0x00000000
02-19 16:28:29.385 13649 13663 D KONYJNI : throwJSException(ENTER){
02-19 16:28:29.385 13649 13663 W System.err: android.content.res.Resources$NotFoundException: Resource ID #0x0
02-19 16:28:29.395 13649 13663 W System.err: at android.content.res.Resources.getValue(Resources.java:2558)
02-19 16:28:29.395 13649 13663 W System.err: at android.content.res.Resources.openRawResource(Resources.java:2472)
02-19 16:28:29.395 13649 13663 W System.err: at android.content.res.Resources.openRawResource(Resources.java:2448)
02-19 16:28:29.395 13649 13663 W System.err: at android.support.v8.renderscript.ScriptC.internalCreate(ScriptC.java:91)
02-19 16:28:29.395 13649 13663 W System.err: at android.support.v8.renderscript.ScriptC.<init>(ScriptC.java:59)
The application is now getting installed on 64 bit devices, but causing another problem i.e., renderscript api's are failing, as there are no .bc files generated under raw folder.
It is searching for resources under raw folder throwing error:
W ResourceType: No package identifier when getting value for resource number 0x00000000
02-19 16:28:29.385 13649 13663 D KONYJNI : throwJSException(ENTER){
02-19 16:28:29.385 13649 13663 W System.err: android.content.res.Resources$NotFoundException: Resource ID #0x0
02-19 16:28:29.395 13649 13663 W System.err: at android.content.res.Resources.getValue(Resources.java:2558)
02-19 16:28:29.395 13649 13663 W System.err: at android.content.res.Resources.openRawResource(Resources.java:2472)
02-19 16:28:29.395 13649 13663 W System.err: at android.content.res.Resources.openRawResource(Resources.java:2448)
02-19 16:28:29.395 13649 13663 W System.err: at android.support.v8.renderscript.ScriptC.internalCreate(ScriptC.java:91)
02-19 16:28:29.395 13649 13663 W System.err: at android.support.v8.renderscript.ScriptC.<init>(ScriptC.java:59)
sa...@google.com <sa...@google.com> #8
Thank you for your feedback. We assure you that we are doing our best to address the issue reported, however our product team has shifted work priority that doesn't include this issue. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with latest bug report here https://goo.gl/TbMiIO .
Description
I have built an application targeting only arm64-v8a devices. I have built the respective .so files and placed them under arm64-v8a folder under libs.
Now when I try to install the application on devices like nexus 6p, nexus 5x, samsung s6, one plus three(which are of arm64-v8a architecture), I am getting error INSTALL_FAILED_NO_MATCHING_ABIS though the abi's are available.
Now if I include armeabi-v7a libs as well, the application is working fine. It is picking armeabi-v7a libs on arm64 device despite having those libs.
The .so file is built against AArch64 which supports arm64-v8a architecture.
Same is the case with x86_64 as well.
We are not sure if this is some thing wrong with the way we built the application or it is an issue with ndk.
Any help would be appreciated.
I have attached the apk and application code is shared here
Thanks,
Surya Soma