> If you can have just 3 things be much faster, what will they be? I need to make a custom camera filter display based on the camera preview run faster than I am currently able to do. We must get the display rate up to 5 to 10+ frames per second, through the G1 can barely display 1 fps. In order to do this, here are three requests: 1. Faster delivery of individual preview frames to the preview callback onPreviewFrame. 2. Support another data format that I can decode more quickly than the current YCbCr_422_SP data and support configurable preview frame size. 3. Faster looping through every pixel in the image in order to process per-pixel calculations more quickly. P.S. iPhone suffers the same issues, but many J2ME devices do not. As far as I am concerned, this is strictly an issue of camera API support in the JVM.
- Regards, David Manpearl On Jan 12, 2:21 pm, Tomei Ningen <[email protected]> wrote: > Hello Android developers, > > We are building an Android-based device, and would like to know what we > should try to improve in terms of performance. If you can have just 3 things > be much faster, what will they be? > > .... please be specific (instead of "graphics is too slow", something like > "drawing red poker dots on translucent canvas is slow") > > .... and why are they important (a real-world use case would be good). > > Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
