Your code will only return correct NV21 if there is no padding at all, and U and V plains overlap and actually represent interlaced VU values. This happens quite often for preview, but in such case you allocate extra w*h/4 bytes for your array (which presumably is not a problem). Maybe for captured image you … Read more
The 5X camera is not “reverse”; it does report the correct camera orientation in its parameters, so no special workarounds are needed, just make sure you’re setting the display orientation correctly: public static void setCameraDisplayOrientation(Activity activity, int cameraId, android.hardware.Camera camera) { android.hardware.Camera.CameraInfo info = new android.hardware.Camera.CameraInfo(); android.hardware.Camera.getCameraInfo(cameraId, info); int rotation = activity.getWindowManager().getDefaultDisplay() .getRotation(); int degrees … Read more
Even though the old camera API is marked as deprecated, it is still fully functional, and will remain so for quite a while (as nearly all camera-using applications on the Play Store use it currently). You’ll have to ignore Android Studio’s complaints about it being deprecated, but if you want to support Android versions earlier … Read more
Look at floor((float) uvPixelStride*(x)/2) which calculates your U,V row offset (uv_row_offset) from the Y x-coordinate. if uvPixelStride = 2, then as x increases: x = 0, uv_row_offset = 0 x = 1, uv_row_offset = 1 x = 2, uv_row_offset = 2 x = 3, uv_row_offset = 3 and this is incorrect. There’s no valid U/V … Read more