J2ME Client Stabilization

UPDATE: 4/4/14

Update Mechanism: Currently the client has now a update mechanism. It is just needed to test it also.

====================================================

INTRODUCTION
"Stabilization" is a big word, and the customer didn't articulate what instability they are experiencing. They only said that "It hangs on 'Please Wait...'". So this would probably the part we would be solving.

Please note the most of the other requirements are found in a separate blueprint called "Enchanced Network Module" due to this nature of bug.

https://blueprints.launchpad.net/dhis-mobile/+spec/network-module

====================================================
#1 FEATURE: Update Mechanism
Priority: Moderate Priority
Difficulty: Moderate
Estimate: (Rough-Most Likely) 3-4 days

Use Case: Maybe the reason why it hanged on the "Please wait..." is that because the client didn't understand the new server responses. Upon logging in, there should be an "update check" for whether mandatory or optional update. If there's an update, there would be a menu to update or cancel it. If it is an update. Then the client would go to the download server and perform an OTA Installation.

Technical Implementation: Major work for here is making an "Update API" with the server, and also the download server.

MORE TASKS:
Other more solutions are conduction Unit Tests and Logging.