[android-developers] Re: 1.6 vs setPictureSize

2009-10-26 Thread Greivin Lopez
Hi! I was having a similar issue on my application. Later I found that setPictureSize actually works well but the problem was in the setPreviewSize. When I called setParameters it was failing because the setPreviewSize, so the other parameters wasn't really being set. If you are calling

[android-developers] Re: 1.6 vs setPictureSize

2009-10-26 Thread enervatron
Greivin -- you are exactly right. Sigh. So the real problem here is that they have error checking in setParameters which is a void and throws no exceptions. Either follow Postel's rule as in 1.5, or throw errors. But what 1.6 is doing is a mess. On 10/26/09, Greivin Lopez greivin.lo...@gmail.com

[android-developers] Re: 1.6 vs setPictureSize

2009-10-25 Thread enervatron
Well the auto-scaling definitely worked in 1.5 and stopped working in 1.6. I'm not sure why they'd remove that feature as it requires a lot of hacking using BitmapFactory/Bitmap to get around the fact that you can't load a camera image into an app and manipulate it directly (it has to be

[android-developers] Re: 1.6 vs setPictureSize

2009-10-25 Thread blindfold
It works for me under Android 1.6 on ADP1, and I can save a 640 x 480 snapshot just fine, set using setPictureSize(). In my app the user can set the desired resolution (default 2048x1536). On Oct 24, 3:55 pm, enervat...@gmail.com wrote: Before 1.6:         Camera.Parameters parameters =

[android-developers] Re: 1.6 vs setPictureSize

2009-10-24 Thread gjs
Hi, I have a camera app which creates large 2048x, medium 1024x and small 512x images by setting the camera parameters and it is still working OK in 1.6 on G1. My guess is that 640 is not a binary integer multiple of 2048 ???, so maybe try 1024 and then rescale to 640. Does 5mp pictures ( eg