4

I'm trying to delete some native libraries from my application because I don't use them anymore, but after I install the apk in my phone I can see that the native libraries are still there. As I've seen, android does copy/update native libraries correctly just by replacing the file in my libs/ directory, but apparently it doesn't delete them when they're not in the apk anymore. How do I know the libraries are still there? Well first of all the application's size remains the same and I'm deleting some really big libraries, and second, if I leave the System.load(...) statement the app is still able to load the library.

The only solution that I've found for this has been to uninstall the app and make a fresh install, but that's not an obvious solution for a user updating the app from google play, and yes this problem affects severely my app functionality.

I've checked and apparently I can delete the files by my self, say during a service creation, but I don't want to mess with the installation this way.

Do you know if there's a way to tell Android that it needs to delete all the native libraries and copy them again?

Thanks, Mike

[EDIT]

I've just found that GB updates the libraries correctly, it deletes the now-missing as it should, but neither ICS nor JB do, those two leave the old .so files even when they're not in the apk anymore.

I tried deleting the .so files manually from /data/data/mypackage/lib but it won't let me.

Any ideas?

mike.adc
  • 191
  • 3
  • 11
  • You can also do a clear data on the app, but that will wipe out all data stored in the app's private directory. But how are the existence of these old libraries causing a problem- if they aren't called they just sit there. – Gabe Sechan May 08 '13 at 20:58
  • It sounds like you may have a broken version of Android on this device. Do you get the same behavior on an emulator? For one thing, application code is not supposed to have permission to modify the contents of its lib/ folder, so if you can that by itself indicates something very non-standard. I'd be curious what happens if you create an upgrade apk with a zero-length .so file having the same name as the one you want to wipe out. Also, you may want to use the `run-as your.package.name` command from within the `adb shell` and then `ls -l lib` and see what is actually installed there. – Chris Stratton May 08 '13 at 21:04
  • The problem is that the classes loading those libraries aren't mine, so I can't prevent them to be loaded from java. – mike.adc May 08 '13 at 21:04
  • If code in your app is trying to load them, removing them will probably cause runtime exceptions. You'll need to remove the code which depends on them, or make stub libraries with fake versions of each native method which do nothing, each in an appropriate manner. Or globally catch these exceptions and somehow recover. – Chris Stratton May 08 '13 at 21:06
  • actually @ChrisStratton, I haven't tried to delete the libraries by code, I just read that it was possible but I don't want to use that option. I also tried to replace the .so file with an empty file with the same name and the app crashes with a "fatal signal 7" error, which can't be catch in java as it isn't an exception. – mike.adc May 08 '13 at 21:11
  • No, I can safely remove them because those libraries are optional, if they're not found the functionality is simply disabled, and those are functionalities that I don't need. – mike.adc May 08 '13 at 21:13

2 Answers2

4

Ok, so I gave up on android to do this and I had to do it myself. I took some tips from here: http://www.moodstocks.com/2012/03/20/ice-cream-sandwich-why-native-code-support-sucks/.

Here's what I did:

  1. Make three zip files with the contents of the folders libs/armeabi, libs/armeabi-v7a and libs/x86 and named them libs_armeabi.zip, libs_armeabi_v7a.zip and libs_x86.zip respecively.

  2. Move the zip files to the res/raw folder.

  3. Delete the files under the three libs folders and re-create them with touch (in a -nix system), remember that ICS and JB don't delete the old files in the lib folder, so just deleting the files would cause the app to keep those files which are quite large.

  4. Verify the processor architecture programmatically with these two methods:

    public static boolean isArmv7() {
    try {
        return Build.VERSION.SDK_INT >= 4 && Build.class.getField("CPU_ABI").get(null).toString().startsWith("armeabi-v7");
    } catch (Throwable e) {}

    return false;
}

public static boolean isX86() {
    try {
        return Build.VERSION.SDK_INT >= 4 && Build.class.getField("CPU_ABI").get(null).toString().startsWith("x86");
    } catch (Throwable e) {}

    return false;
}

  5. Depending on the processor architecture unzip one of the three files programmatically to any folder you want, I'm using /data/data/myPackage/app_libs (using context.getDir("libs",Context.MODE_PRIVATE); returns that path).

Probably there would be more logic involved here, something like extracting the libs_armeabi.zip file, and then extract the files from either libs_armeabi_v7a.zip or libs_x86.zip or none of them, overwriting the files that have the same name (I'm just wandering here because I haven't actually tried that), fortunately for me my libs on the three files were already renamed and are exclusive on each zip file, so I just need to extract one of the three files.

  1. Replace the System.loadLibrary method calls to System.load which supports loading the libraries using its full path, and add the full path for each library.

This method comes with added benefits:

  • As the libraries are zipped the apk size will be reduced, making the application in the google play store smaller.

  • Being the libraries stored inside the raw resources android won't copy them automatically, allowing you to copy them wherever you want and load them using a full path.

  • You can decide to copy the libraries to the sd card if you want, I wouldn't recommend that but now you're able to do it, for example when the phone doesn't have enough space.

Hope this helps!

mike.adc
  • 191
  • 3
  • 11
0

All files in native lib directory has owner is System. So in your app, you can not delete these file without root permission.

Move your lib directory to res/raw, then manually copy them to internal data is a good choice.

Ken
  • 1,303
  • 13
  • 15