Fixes to a Java application running on mobile phones

We have a home automation remote control written in Java that runs on mobile phones, mainly Blackberry. ? It uses basic HTTP get's to retrieve from a server a list of devices in the home (light switches, thermostats, etc.), and displays the devices in a tree with a basic user interface for each device. ? For example, for light switches the UI shows buttons 'on' and 'off'. ? For thermostats, it has more buttons like cool, heat, etc. The application works fine, but there are a couple bugs we need fixed and some enhancements to it. ? Our in-house Java programmer who wrote this a year ago is not around anymore. ? We will provide the current source code. ## Deliverables You can see the current application by downloading it from here:? <[login to view URL]>? ? and when prompted for a username/password, use the 'secure server' option with user: testvera, and password: myvera123 Here are the changes/fixes we need: 1. ? On the connection options, and when using the "Connect Directly (not secure)" option, there is a character limit on the input box for the IP Address / Domain field of 20 characters. It is highly suggested to increase this as some domains may be very long. ? 2. ? Presently it only responds to up/down/left/right key presses, but not to 'touch' events. ? Add support for touch events so users can touch the buttons. 3. ? On the settings menu add a 'mute sounds' checkbox which, if checked, causes it not to play the audio beeps. 4. ? For some reason it runs fine on some mobile phones, like earlier Blackberry's, but not on the new Blackberry Curve, and some users have reported problems on other new cell phones. ? So it's best if the programmer knows about Java apps on mobile phones and can help us figure out why it doesn't run on some phones, perhaps by creating a test application that checks the various necessary components on the phone. 5. ? On some cellular networks we sometimes get general 'network failure' errors. ? We don't know the reason for this. ? But it needs to display more information about why the network connection is failing, and, barring a problem with the cellular data network, there shouldn't be network fail messages 6. ? When you change the connection info, it should automatically re-retrieve the list of devices/rooms and show the user this. 7. ? There's a feature where it checks a URL on the internet for the latest version, and if that doesn't match the version that's hardcoded in the java app, it displays a popup asking the user if he wants to upgrade, which, if the user says 'yes', displays the [login to view URL] web page in phone's browser. 8. ? We changed the format of the string with the device status. ? It used be ON or OFF, etc. ? Now it's <POWER=ON>, <MODE=COOL>, etc. ? Just a format change. ? The data is the same. 9. ? It used to request the current status for an individual device/job, and update the 'status' icon for the one device only. ? This was done by calling a url with the device id, like http://whatever/getstatus?id=2. ? Now when you request the status from the server's URL, you should leave off the device id and you'll get back a list of all the devices and their status's. ? This way you can update all the status icons at once. 10. ? We added a couple new types of devices, so we need the new UI controls for them. ? There's a window blind, which is essentially the same as a light switch, and a door lock, which is also the same as a light switch. ? In all cases, the current code has a 'switch' block with the various device types and the buttons to display. ? So this consists of adding that switch block a couple more types.