ImageView displays a Bitmap and Bitmaps don't carry any orientation data as LoadBitmap seems to ignore it. You probably need to rotate the Bitmap of the image according to the EXIF orientation data in the original jpg image file. You should be able to get this using this library
ImageView displays a Bitmap and Bitmaps don't carry any orientation data as LoadBitmap seems to ignore it. You probably need to rotate the Bitmap of the image according to the EXIF orientation data in the original jpg image file. You should be able to get this using this library
You would think that the first number would be x and the second y (or vice versa)? I mean ContnetChooser knows which way the picture is oriented. Where does it get its information?
The ContentChooser object allows the user to select a specific type of content using other installed applications.
For example the user can use the internal Gallery application to select an image.
ContentChooser doesn't know, it is the application you choose that does.
In my experience cameras always save the image in the same orientation relative to the camera. The camera software then uses the device rotation sensor to tag the orientation as landscape or portrait in the EXIF data of the image. This lets the image decoder software orient the image correctly for display.
In my experience cameras always save the image in the same orientation relative to the camera. The camera software then uses the device rotation sensor to tag the orientation as landscape or portrait in the EXIF data of the image. This lets the image decoder software orient the image correctly for display.
I'm just trying to understand here. If ContentChooser doesn't know then why are images always displayed correctly? Some have X>y and some have y>x but content chooser always displays them oriented correctly. And in a view that is sized correctly? This just doesn't make sense to me.