Basic Camera Image Processor

I need an Android project (source files, manifest, output apk, etc) that can process camera frames as they arrive from the camera and alter the image before displaying to the user. With this app I have a specific layout request. Layout - top to bottom: - camera preview (upper 70%) - text view (lower 20%) - button row (lowest 10%) Camera Processing: I have a general idea how I would like this version of the app to work. I know that JNI/NDK or GL calls could speed up the processing but I think I'd like to begin with the standard API calls unless, as the developer, it is suggested that one of the other options will not add too much cost or complexity to the project but yield significant performance improvements. Assuming the standard API, I would like onPreviewFrame to store a copy of the current frame (mCurrentFrame). Processing may occur during the call to onDraw. The program will check if mCurrentFrame is valid and also if mPreviousFrame is valid. If not, mCurrentFrame will be stored as mPreviousFrame and mCurrentFrame is displayed. If both mCurrentFrame and mPreviousFrame are present, the program checks for any pixed in mCurrentFrame that is not equal to mPreviousFrame and multiples the pixel by 10% (effectively, this pixel is much lighter). The new "lightened" frame is now displayed to the user. At any point during processing, the program may call [login to view URL]("some text") and it will show debugging information in the visible text area. The button row will have a "+" button (increases the 10% value above in increments of 10%, so the user can step from 0%, 10%, 20%... 100%). The second button "-" will do the opposite. The third button "sound", will play an audio sound, perhaps a small sound clip of a bell. The fourth button "+" will hide the text area. I will use this project to evaluate performance for image processing. Another project may involve improving the performance. Any bids that clearly state alternative approaches to improve the image processing performance or layout improvements are welcome if they discuss the trade-offs associated with the improvements (ie: more library dependencies, more complex build environment, etc).