Highly unlikely. Applications are restricted to a heap of 16MB. An 8MP image in RG888 will use 32MB.
I am inclined to deprecate that API entirely and replace it with hooks for native signal processing. On Feb 10, 6:17 pm, gjs <garyjamessi...@gmail.com> wrote: > Hi, > > I'm hoping that Android will supported this in future for RGB888 and > (at least) 8mp images. > > I know this is a big ask, probably requiring much larger process heap > size ( > 16MB & high speed bus/memory ) but there already is 8mp > camera phones available on other platforms. > > And yes I know these phones do not yet support loading such large > images into (java) application memory but I'm hoping the Android > architecture can accommodate this in the not to distant future. > > Regards > > On Feb 10, 7:01 pm, Dave Sparks <davidspa...@android.com> wrote: > > > On the G1, no data is returned - only a null pointer. The original > > intent was to return an uncompressed RGB565 frame, but this proved to > > be impractical. > > > On Feb 9, 3:57 pm, Xster <xyxyx...@gmail.com> wrote: > > > > Hi, > > > Our university is intending to use the Android as a platform for > > > mobile image analysis. We're wondering what kind of information is > > > returned in the raw format when android.hardware.Camera.takePicture() > > > is called with a raw Camera.PictureCallback. I can't seem to find more > > > information about it on > > > thehttp://code.google.com/android/reference/android/hardware/Camera.Pict... > > > page. > > > > Thanks, > > > Xiao --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
