Blackberry Tracking App

I need a BlackBerry App that will track the user's GPS position continuously, and periodically report location data to a server. The app should run in the background at all times. The application should extend the open-source bbTracker project ([login to view URL]). ## Deliverables I need a BlackBerry App that will track the user's GPS position continuously, and periodically report location data to a server. The app should run in the background at all times. The final deliverables will be JAR, JAD, and COD files. The success of the application will be achieved when the application **tracks and reports my location at a 10 second interval for 96 hours (4 days) without interruption** (With regular nightly charging). It will be installed on my **Sprint BlackBerry Curve 8330 CDMA** phone running **BlackBerry OS 4.5.0.131**. More performance checkpoints might be established when I gain access to other phones, but this will likely be incorporated into a separate Rentacoder contract. UPDATE: (7/22/2009) I initially asked for the application to extend the bbTracker project because of its support for many BlackBerry and Nokia devices. But there are severe shortcomings in bbTracker that you must address in order to meet my project requirements. I am not certain that starting from bbTracker would make the application easier or more robust. Please be aware of this when placing your bid. At minimum, I would recommend you download and install the bbTracker project on a BlackBerry device or simulator. My critical project requirement is that the application tracks continuously (without freezing, crashing, or needing to be manually restarted) for 4 days on my Sprint BlackBerry Curve 8330. The bbTracker app utterly fails in this regard on my device. It does not continue position tracking when backgrounded and frequently gets stuck. The recommendation to use bbTracker as a starting point is not a requirement. If you can develop this application without extending the bbTracker project, and exceed my expectations for reliability and friendly architecture, you by no means have to use the bbTracker project as a starting point. I would instead require that the application is compatible with at least as many BlackBerry devices and carrier networks as bbTracker. If the application is developed using BlackBerry APIs, I require compatibility with API version 4.3.0. The application should modify and extend the open-source bbTracker project ([[login to view URL]][1]) because of its compatibility with a variety of BlackBerry smartphones plus a few location-enabled Nokia phones. Many display features of the bbTracker project can be disabled since the purpose of this app is only to report **latitude, longitude, altitude, accuracy,** and **timestamp** records to a remote server; with a priority first on optimizing battery usage and application stability for 24/7 coverage, and second priority on location accuracy and sampling rate. In other words, position should be sampled as frequently and accurately as possible while still maintaining 24/7 tracking. Certain optimizations may be developed such as slowing the location sample rate during periods of inactivity, etc. to be determined later. By default, location data should be recorded about every 10 seconds - as noted in RIM documentation, this will keep the GPSOne chip in the BlackBerry Curve 8330 "hot". A queue of location records should be reported to a server about every 10 minutes. These defaults may need to differ for each phone model, and the application design should make that simple. Users should have an option to "force" an update to the server. The application should not shut down unless the user explicitly chooses a special "Shut Down" option from the application menu. The Escape key should not close the application but instead send it to the background. The application will provide an options screen with input for username, password, reporting server URL, location update interval (seconds), and server reporting interval (minutes). Application should provide a menu item to "reset" the location tracking function in case it should hang or stop responding. Application should be robust so that if the reporting server is unavailable, unreported location information is queued and saved to persistent storage until the reporting server connection is reestablished. Location data reporting should be encrypted and/or occur over secure HTTPS POST. Username/password authentication should occur over HTTPS transport. **I will provide the HTTPS server URL and a simple spec for posting the location data.** This summary is subject to revision. Additional requirements, especially regarding application screens and information display, will be discussed.