Enhance readablity by making objects that could live longer than it's activity their own name

When dealing with AsyncTasks or Task<V, Callable<V>> never create it anonimously:

new AsyncTask<Void, Void, Float>() {
    //...
};

as it may cause the programmer to easily forget that all variables used and an instance of this are strongly referenced for the life of the anonymous object. That could cause unforeseen leaks.

A mitigation is having each object be instantiated from a subclass:

new MakeThingTask(...);

This is more explicit in its "aquisition" of strong references to the parameters passed.

Start by searching the Android project for anonymous AsyncTask and Task<V, Callable> usages. Determine which objects need named subclasses to make their strong references explicit, and consider the work complete when the affected usages follow that pattern without introducing the described leak risk.