What's the difference between a regular Android APK and one included as part of a device's system image?

We have a manufacturer that wants to pre-install our application on their Android device. We sent them the APK and even though it installs fine when used by a user, it appears to not get installed correctly when included in the manufacturer's build image. FYI, our application uses the JNI layer and some libraries built with NDK. The exception we're seeing seems to indicate that the class loader c开发者_StackOverflow中文版annot find the library and is unable to load it. They have verified that the library files are indeed present in the APK.

Since we dont make devices, its unclear why they are seeing this exception and what needs to be done differently when including a package as part of the Android build image.

Any Android folks here care to comment?

I have worked with pre-installed Android apps, that also uses library files, in my case jar files. I am assuming that you have added the appropriate lines to AndroidManifest.xml like <uses-library android:name..... I am also assuming that you have provided instruction on how to install your library files on handset, with instructions like adb push ... on the command prompt. If you havent, do provide them the instructions.

Another issue may be permissions, we had to get the library jar AND the permissions xml file installed, that may be the issue.

Also ensure that you are using the correct version of Android for testing. And if everything fails, ask them to send one of the handsets that is not working to you and you can then compare with the one in office and debug this. Good Luck, as all this can be pretty frustrating.

Besides moving the apk file into /system/app, you should ask the manufacturer to move the native libraries created by NDK (.so files) to /system/lib or the path specified by LD_LIBRARY_PATH.

Please refer to https://groups.google.com/d/topic/android-porting/r_Ao7_PWgKQ for more details.