Develop Phonegap Camera Plugin For Android

I. Problem / Background ----------------------- When the camera is triggered on a Phonegap Android application to capture video, the Android activity goes background (onPause state), waiting for the camera to record the content. If the internal and cache memory of the device is low, the Phonegap application can be put in the onStop state (as Android has trouble keeping the Phonegap app in the "back stack" along with the camera activity.) In this situation, the Android Garbage Collector (GC) comes and kills the Phonegap activity to free memory before the conclusion of camera action, and when the camera is done, the Phonegap activity has already died (i.e., having been killed by Android GC). This causes the Phonegap app to restart when camera action ends. This results in a bad user experience. This Android behavior is described in the Android Lifecycle docs here: ([login to view URL] ): Specifically, if an activity is completely obscured by another activity, it is stopped. It still retains all state and member information, however, it is no longer visible to the user so its window is hidden and it will often be killed by the system when memory is needed elsewhere. The same problem occurs by capturing an image, or accessing the media gallery as these also cause the Phonegap app activity to go background. II. The Job -------------- I'm looking for someone to develop custom Foreground Phonegap camera plugins for Android, working around the Android GC behavior such that our Phonegap app activity never go to onStop state, and not be killed by the Android GC. ** I will firm up a budget with serious inquires. III. Requirements: ------------------ 1. The new, custom camera plugin (referred to as <customplugin>) must follow the Android API instructions on [login to view URL] 2. The <customplugin>.[login to view URL] method should follow same API design as Phonegap [login to view URL], as defined here: [login to view URL] I.e., the calling convention, callbacks etc., should behave exactly the same. Replacing the Phonegap [login to view URL] call with the newly developed <customplugin>.[login to view URL] call in our pre-existing code should be completely seamless. 3.) The <customplugin>.[login to view URL] method should follow same API design as Phonegap [login to view URL], as defined here: [login to view URL] As with the above, the calling convention, callback etc., should behave exactly the same. Replacing the phonegap [login to view URL] with the <customplugin>.[login to view URL] should be completely seamless. 4. The plugin should support Phonegap Version 2.7 - 3.2 Instructions must be provided for installing and configuring the plugins for Phonegap 2.7 (without plugman), and for installing configuring on Phonegap 3+ (instruction for plugman install) As an aside, there are a couple foreground plugins out there, but they are old (Phonegap 2.1), and not maintained, but maybe they will be helpful to you: [login to view URL] [login to view URL] 5. The developed source code must be well documented 6. The plugins must be well tested on Phonegap 2.7 and 3.2, and most importantly -- the Phonegap app must not be restarted by the Android GC when the camera <customplugin> methods are called. 7. Service Provider must warranty their code for at least 3 months for bug fixes. If bugs are found in the service providers code, timely fixes must be provided at no charge.