We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

About the implementation in your patch:

I think cloning of the array object is not needed. You could just use three local float variables. onSensorChanged() is called very often and this would prevent some creation and garbage collection overhead for a tiny performance improvement.

Also I think swapping through a temporary variable is not needed. You could just assign the values from the input array (maybe modified) into three local "output" variables and use these as parameters for the JNI call.

e.g.:

// ...

float x, y, z;

// ...

case Surface.ROTATION_90:
    x = -event.values[1];
    y = event.values[0];
    z = event.values[2];
    break;

// ...

default:
    x = event.values[0];
    y = event.values[1];
    z = event.values[2];
    break;
}

SDLActivity.onNativeAccel(x / SensorManager.GRAVITY_EARTH,
                          y / SensorManager.GRAVITY_EARTH,
                          z / SensorManager.GRAVITY_EARTH);

Created attachment 1370 [details]
Coordinate remapping of the accelerometer data according to screen orientation

Good point, I was initially using SensorManager.remapCoordinateSystem() (but overkill for our need), hence the clone. Here's a new patch where I kept the new variables to a minimum. No need to get Z out as it won't change (it just needs to be adjusted once, see bug 2156)

Created attachment 1371 [details]
Coordinate remapping of the accelerometer data according to screen orientation

Had forgotten to remove yet another variable. This time it should be as lean a possible.

Good patch, thanks!
http://hg.libsdl.org/SDL/rev/e2188abb7c10