About the SetFrameRate at Android Camera Input MIO

by ever » Tue, 14 Apr 2009 03:47:39 GMT


Sponsored Links
 Hi,
SetFrameRate at Camera Input MIO does not negotiate with the camera
driver for the preview framerate, it just postpone the Camera Input
MIO to receive video frame from buffer queue when recording is
started.
The preview framerate could be different from what we ask for
recording (encoding), doesnt this condition cause any problem? Ex.
Camera client sends preview frame to buffer for Camera Input MIO at 30
fps, but the app asks recording at 20 fps.
--~--~---------~--~----~------------~-------~--~----~



About the SetFrameRate at Android Camera Input MIO

by Han Chao » Tue, 14 Apr 2009 05:03:25 GMT


 Preview FrameRate and Recording are different conception.
Somethimg Recording FrameRate can't reach the setting , it may do as
much as possible.

Camera Input MIO should be the preview FrameRate.
--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


About the SetFrameRate at Android Camera Input MIO

by Han Chao » Tue, 14 Apr 2009 05:04:29 GMT


 We have discussed it .
Some setting of preview and recording may be separated.
--~--~---------~--~----~------------~-------~--~----~



About the SetFrameRate at Android Camera Input MIO

by ever » Tue, 14 Apr 2009 05:22:48 GMT


 Hi Han Chao,
could you tell me more detail about the framerate between preview,
mio, encoder and composer node.
thanks a lot.



--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. How ACTION_CHOOSER picks choices for ACTION_SET_WALLPAPER

In Launcher application,  ACTION_CHOOSER intent is used to show
possible choices for setting wallpaper from.  I could not find
ACTION_SET_WALLPAPER in any AndroidManifest.xml.   What ACTION does it
use to identify the possible choices (gallery,  wallpaper)?  Is this
PICK_ACTION?

Thanks,  Layeeq

--~--~---------~--~----~------------~-------~--~----~

2. Can I use generic/ramdisk.img for my target board?

it depends on the File system configuration of your board.

ramdisk.img is the root FS with ramdisk format.  system.img and data.img
will be mounted under /system, /data by default.

Of course, images will be built by the cross-compilers attached the Android
package. ABI will ensure the system call and Android middlewares. but to
enable Android on your target, the android special features like binder,
power, etc. must be ported to the target.

Good Luck!





--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

3. Market statistics for apps targeting The Netherlands are not correct

4. How Toggle Button paints the toggle indicator?

5. show me the bluetooth??

6. How does the TabActivity successfully "switch" activities?

7. Sensor readings on demand