How can I use BitmapRegionDecoder code in android 2.2.2 (Froyo)?

Question

I was reading an answer to a different question on SO, in which @RomainGuy commented that one could (please correct me if I'm paraphrasing incorrectly) back-port code from later versions of android to earlier versions. Specifically, I am interested in back-porting code for BitmapRegionDecoder from Android version 2.3.3 (Gingerbread) to version 2.2.2 (Froyo).

I would have rather asked the question more generally as what is the best practice / what should be avoided when back-porting code from newer versions of Android to older versions, but stackoverflow hinted that my question might be closed as being too subjective.

Maybe if there is enough interest in the topic, this question could be "morphed" into a more general one..possibly a community wiki?

In any case, I would appreciate any insight into how this is done..whether specific to my use case, or more general advice. Do calls to native methods from within the java class complicate the matter (necessarily involving the NDK)?

If it is indeed possible (and reasonable) to cherry-pick and back-port code in this way, I think many would find it very useful to know how.

Answer 1

As @hackbod mentioned BitmapRegionDecoder is based on external skia library. Yet it's may be a benefit.

Let's examine original source:

• BitmapRegionDecoder.java. Mostly defines wrappers around native methods:

  private static native Bitmap nativeDecodeRegion(int lbm,     int start_x, int start_y, int width, int height,     BitmapFactory.Options options); private static native int nativeGetWidth(int lbm); private static native int nativeGetHeight(int lbm); private static native void nativeClean(int lbm); // ...multiply nativeNewInstance overloads follow 

  Class doesn't use any new Java APIs we'd need to backport.

• BitmapRegionDecoder.cpp. Header files it includes consist of ones which are present in Froyo except these two:

  • AutoDecodeCancel.h. The only line it's used in:

    AutoDecoderCancel   adc(options, decoder); 

    This class handles SkDecoder instances lifecycle. It's a small piece of code and may be well back-ported.

  • SkBitmapRegionDecoder.h

    As filename states this is a core component. In fact, all previous were a kind of wrappers around it. The good news is that we may not need to back-port it as it should be possible to take a whole skia library from the Gingerbeard and compile it under Froyo as it is external and doesn't contain any new dependencies.

P.S. I didn't actually dive deep in the code so please correct me if there's anything I overlooked.

Update:

Source code we need is located in following repositories on branches froyo-release and gingerbread-mr4-release:

• External skia library repository
  • Header files are in include/core and include/images
• Android framework base
  • Java code: graphics/java/android/graphics/BitmapRegionDecoder.java
  • Native code: core/jni/android/graphics/...

Answer 2

You can back-port some code, if it can exist on top of the SDK you are porting it to.

You can't back-port anything. For example, you couldn't back-port a kernel feature. :)

In this case, there is no easy solution to back-porting it. The implementation of this sits on top of Skia and the jpeg decoder, which are both native code. You will need to do your own implementation of that code. You could try copy/pasting the code from the platform, gluing it in with your code with JNI, but this will be a significant amount of work and leave you with native code you need to continue to maintain.

Sorry there is no easy solution for this.