is there a BitmapFactory resolution to fix "Bitmap too Large to be uploaded into a texture"?

Question

on some devices, it seems the images in Bitmap form are too big for the ImageView which is going to house them.

Images will be obtained by the camera and the web. They will be shown 1 at a time in an activity which allows you to move the image, zoom, etc to look at defects.

It seems that when using images from the camera, we get "Bitmap too large to be uploaded into a texture."

I didnt want to hardcode a scale, but i was thinking to take whatever image, and through the Bitmap Factory, produce an image which will fit in the Imageview. I would then take that image now that it isnt tooo large, and pinch zoom it through relating a matrix to the ImageView.

Answer 1

I was looking around stackoverflow about how this can be resolved. I have come to the following conclusions:

1. It is based on an invidicual devices GL_MAX_TEXTURE_SIZE as per: "Bitmap too large to be uploaded into a texture" and jptsetung's answer and the underlying comments which also point to HW accelerated activity - how to get OpenGL texture size limit? which has Romain Guy give a solid understanding.
2. You need to understand what sort data your device can handle.

3. When you do the following code, using 2 will quarter the size of the image.

   BitmapFactory.Options ops = new BitmapFactory.Options();
   opts.inSampleSize = 2;
   

   this understanding comes from the notion that it will half the width and height, and therefore quarter the size.

4. If you do not want to hardcode it, like i did. You can use GL_MAX_TEXTURE_SIZE to help determine what it is.

As a final note, what i did is that i took the imageview with the bitmap, and assigned it a MATRIX and then scaled the matric by

Matrix m = new Matrix();
m.postScale(scaleX,scaleY);

which allows you to get sample of the image to make it smaller, and then scale it up so that it maintains the same size. inSampleSize is the size of both scaleX and scaleY to make it scaled up.

Possible issue: Pixelation. depending on the size of the image, it wont be too bad, but you are going to see some of that.

This is to solve the constraints of the device. I would check to see how big the images width and height is, and if it is > GL_MAX_TEXTURE_SIZE, it will do some math and make it under the balue.

and i believe the next standard things would be:

1. ...

2. Profit!