It doesn't seem difficult to deal with dynamic changes in preview. The application will make a request through setParameters() and this may result in a change in the preview heap.
It's too late to get this change into Cupcake, but we should be able to work on this in the next release. On Jan 26, 11:16 am, steve2641 <steve2...@gmail.com> wrote: > Dave, > > Thanks for your quick reply. > > Concerning the need for dynamic preview heap changes, we got the > impression from the sample Camera HAL implementation (specifically at > the top of the previewThread() function) that the application would be > allowed to change the preview size or frame rate or other preview > attributes while preview is running. If this is true, then doesn't > this imply the need for some sort of dynamic heap update feature? > > In our specific case, we expect all changes to be driven from the > application. So, when the application changes the preview size or > enables/disables image stabilization or other attributes that affect > the preview heap then Camera Services would need to be told of these > changes. > > If, by chance, the preview size and other attributes that effect the > heap size are not suppose to be changed while preview is running, how > is this (or how should this be) communicated to the application? > > I think either case (dynamic support or not) we can produce the > affects that we are hoping for, but without dynamic support the > application has to do more work, stopping preview and such, which may > cause semi-perceivable delays on the final output. > > Thanks, > > Steve. --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
