On 1.5 and 1.6, there is no way to know supported preview sizes so
apps should not call setPreviewSize. Apps should call getPreviewSize
to know the current preview size. On 2.0, Apps should call
getSupportedPreviewSizes before setPreviewSize.
It's the same for setPictureFormat. On 1.5 and 1.6,
The camera drivers only support some preview sizes. In 2.0, you should
call getSupportedPreviewSizes to know the valid values and then call
setPreviewSize. In 1.6 and before, it's better just to call
getPreviewSize to know the preview size instead of changing it.
To achieve what you want, you
In 2.0, apps should call getSupportedPictureSizes to get valid picture
sizes and then setPictureSize.
http://developer.android.com/reference/android/hardware/Camera.Parameters.html#getSupportedPictureSizes()
On Nov 17, 12:28 am, Streets Of Boston flyingdutc...@gmail.com
wrote:
That's just in
This looks like a framework bug fixed in 2.0. This bug occurs more
often if preview callback is registered.
On Nov 9, 5:05 pm, merabi mera...@gmail.com wrote:
Hi.
im having a trouble getting Android'scamerato work.
i started CameraActivity Intent from MapActivity (when i startcamera
activity,
I don't know all the answers to your question. Here's what I know.
1. If your application only needs to show the preview and does not
need to process the preview frame, the app doesn't need to allocate
any buffer or register preview callback. The framework/driver will
draw the preview for your
5 matches
Mail list logo