14

I'm developing a camera app basically as part of a messaging app to attach images etc. The app needs to work for >= SDK 2.2 and:

I can't use the default Android Camera as much as I'd love to because:

  1. The nature of the app dictates that the image should not be saved to disk ever and some OEMs (Samsung) love to do this without giving you a choice.

  2. I can't call an intent that any other camera app can intercept because then that app could save the image.

My current problem is dealing with the fact that the Android camera apparently hates being in portrait orientation. Specifically, after some digging I'm monitoring the display and, on rotation, calling setDisplayOrientation(90). This works but the surfaceview dimensions need to be altered also and this must be done within supported dimensions or the parameter setting crashes the app.

I'm doing this with another SO snippet I found here (the getBestPreviewSize() method) but it has one glaring problem that I can't believe I haven't found anyone else having.

Part of the takePicture lifecycle involves calling the PostView picture callback. This is what shows the still image of the current paused SurfaceView image that will be returned via byteArray to the raw and/or jpeg callback. My problem is, this image is still skewed on a handful of seemingly random test devices! So the behavior is a user sees a dynamic camera image in perfect 4:3 aspect ratio until they take the picture and the image they are presented with is squished. Note that the byte array itself is correct and when I construct the Bitmap at the messaging end point it shows up fine but this is still a problem.

I can't see how I can alter the still image display at this point. Can anyone help me with this?

Community
  • 1
  • 1
Andrew G
  • 1,547
  • 1
  • 13
  • 27
  • Could you keep the previous postview picture callback and display that when a picture is actually taken? Could you at the end create a bitmap from the taken picture data and display that instead of the postview image data? I guess it comes down to whether the final image data is messed up or whether the surface view some how changes shape on you. – Douglas Jones Oct 14 '12 at 13:23

3 Answers3

6

Android camera system is a mess. And beind soldered to motherboard, camera chip is not going to like portait application - all the callbacks spill out data in camera orientation (buffer you receive is actually shared memory piece with native camera app) - if you like to display it while your application is in portait mode, you will have to flip this data over xy.

Instead of showing image on the surface view used by camera, I would overlay it with transparent ImageView and draw my bitmap there.

You may (hopefully) find some inspiration in out javaocr project where android deamon work in portrait mode and draw bitmaps over live preview. (please checkout from git, as it is being released now and I'm struggling with git and maven, see demos directory)

HitOdessit
  • 7,198
  • 4
  • 36
  • 59
Konstantin Pribluda
  • 12,329
  • 1
  • 30
  • 35
  • I ended up 'resolving' this last Friday by doing just that - constructing a Bitmap and displaying it. I was trying to avoid this since my app is already fairly heap intensive and we all know about Android's native Bitmap allocation issues pre-3.0. But I digress... Thanks for taking the time to post – Andrew G Oct 15 '12 at 14:30
  • Make sure you're setting your BitmapFactory options inSampleSize. It helps a TON with those memory issues. – samuelesque Oct 17 '12 at 17:36
3

I suspect your problem is at a couple different levels.

Sensor Mount

First, the camera sensor is mounted different on every device. Google has boiler plate code for getting that orientation and setting the correct rotational value to correct it here and it is good down to API 8.

AR Correction

The second issue is obviously that the preview frames aren't the same aspect ratio as the screen. You can use this post to solve that. The surfaceview dimensions have no relation to the best preview size, those values do not have to match - in fact, that your AR is messed up proves that they don't match.

Preview Frame Size != Picture Size

Finally, when you take a picture using takePicture, the size of the picture is completely independent of the size of your preview frame. Use the following to query and set the preview frame size: setPreviewSize() / getSupportedPreviewSizes()

Use the following to query and set the picture size (from takePicture()): getSupportedPictureSizes() / setPictureSize()

Some devices you may get lucky on and the defaults for pictures and preview frames will be the same. This is not the case on all devices.

Finally, if you want to display the taken picture, you may need to do AR correction on it as well if it's not the same size as your SurfaceView. Alternatively you could draw it to an ImageView and use ScaleType.CENTER_INSIDE to preserve the aspect ratio.

Community
  • 1
  • 1
Error 454
  • 7,255
  • 2
  • 33
  • 48
0

Check out this posting on how to switch the QR scanner to be portrait: http://code.google.com/p/zxing/issues/detail?id=178. I don't know if it relates to your swapping of the picture to be portrait but maybe it provides some guidance. Comment #11 seems to be the most helpful. (I am not endorsing that the QR app code be ripped off from Sean Owen).

thomas.cloud
  • 881
  • 13
  • 30