Home > Mobile >  Arm64 - v8a version of native lib, actually deployed to where go to?
Arm64 - v8a version of native lib, actually deployed to where go to?

Time:10-11

An android APP project, contain arm64 - v8a version of the original lib. In making the APK, do have arm64 - v8a under the lib folder.

Problem is, the apk installation to a 64 - bit arm CPU on mobile phones, generate to the lib folder is, which the specific path?


Experiments made excluding arm64 - lib v8a version, only armeabi lib apk, after installed to the same cell phone, you can see,
Is under the "\ data \ data \ pkgname, generate the lib folder.

Version and contains arm64 - v8a lib apk, installed in the mobile phone, but not in "\ data \ data \ pkgname", generate lib folder!!!!!!

The arm64 - v8a version of the original lib, where have deployed on earth?

Thank you.

CodePudding user response:

Did you solve this problem? I also encountered the same problem

CodePudding user response:

reference 1st floor fan_wenqing response:
did you solve this problem? I met the same problem also

Not clear.
My APP development, get around this problem for a while.

CodePudding user response:

Is in the/data/app/application name/lib/arm64 under
But after installed on a mobile phone application result is behind the original name of the application of a pile of strange suffix
Can use the command line, the adb shell PM path see add a suffix after name
And then CD to/data/app/lib/application of the suffix name, you can see a arm64 folder
  • Related