Is it possible to dynamically load a library at runtime from an Android application?

Sorry, I'm late and the question has already an accepted answer, but yes, you can download and execute external libraries. Here is the way I did:

I was wondering whether this was feasible so I wrote the following class:

package org.shlublu.android.sandbox;import android.util.Log;public class MyClass {    public MyClass() {        Log.d(MyClass.class.getName(), "MyClass: constructor called.");    }    public void doSomething() {        Log.d(MyClass.class.getName(), "MyClass: doSomething() called.");    }}

And I packaged it in a DEX file that I saved on my device's SD card as /sdcard/shlublu.jar.

Then I wrote the "stupid program" below, after having removed MyClass from my Eclipse project and cleaned it:

public class Main extends Activity {    @SuppressWarnings("unchecked")    @Override    protected void onCreate(Bundle savedInstanceState) {        super.onCreate(savedInstanceState);        setContentView(R.layout.main);        try {            final String libPath = Environment.getExternalStorageDirectory() + "/shlublu.jar";            final File tmpDir = getDir("dex", 0);            final DexClassLoader classloader = new DexClassLoader(libPath, tmpDir.getAbsolutePath(), null, this.getClass().getClassLoader());            final Class<Object> classToLoad = (Class<Object>) classloader.loadClass("org.shlublu.android.sandbox.MyClass");            final Object myInstance  = classToLoad.newInstance();            final Method doSomething = classToLoad.getMethod("doSomething");            doSomething.invoke(myInstance);        } catch (Exception e) {            e.printStackTrace();        }    }}

It basically loads the class MyClass that way:

• create a DexClassLoader

• use it to extract the class MyClass from "/sdcard/shlublu.jar"

• and store this class to the application's "dex" private directory (internal storage of the phone).

Then, it creates an instance of MyClass and invokes doSomething() on the created instance.

And it works... I see the traces defined in MyClass in my LogCat:

I've tried on both an emulator 2.1 and on my physical HTC cellphone (which is running Android 2.2 and which is NOT rooted).

This means you can create external DEX files for the application to download and execute them. Here it was made the hard way (ugly Object casts, Method.invoke() ugly calls...), but it must be possible to play with Interfaces to make something cleaner.

Wow. I'm the first surprised. I was expecting a SecurityException.

Some facts to help investigating more:

• My DEX shlublu.jar was signed, but not my app
• My app was executed from Eclipse / USB connection. So this is an unsigned APK compiled in DEBUG mode

Shlublu's anwser is really nice. Some small things though that would help a beginner:

• for library file "MyClass" make a separate Android Application project which has the MyClass file as only file in the src folder (other stuff, like project.properties, manifest, res, etc. should also be there)

• in library project manifest make sure you have:<application android:icon="@drawable/icon" android:label="@string/app_name"> <activity android:name=".NotExecutable" android:label="@string/app_name"> </activity></application>(".NotExecutable" is not a reserved word. It is just that I had to put something here)

• For making the .dex file, just run the library project as android application (for the compiling) and locate .apk file from the bin folder of the project.

• Copy the .apk file to your phone and rename it as shlublu.jar file (an APK is actually a specialization of a jar, though)

Other steps are the same as described by Shlublu.

• Big thanks to Shlublu for cooperation.

Technically should work but what about Google rules? From: play.google.com/intl/en-GB/about/developer-content-policy-pr‌​int

An app distributed via Google Play may not modify, replace or update itself using any method other than Google Play’s update mechanism. Likewise, an app may not download executable code (e.g. dex, JAR, .so files) from a source other than Google Play. This restriction does not apply to code that runs in a virtual machine and has limited access to Android APIs (such as JavaScript in a WebView or browser).