Table of Contents
Advertisement
In these handsets, the user is given an option of deleting any MIDlets that are on the
phone if an OTA download cannot be achieved due to lack of space.
The following error codes are supported:
900 Success
901 Insufficient Memory
902 User Cancelled
903 Loss Of Service
904 JAR Size Mismatch
905 Attribute Mismatch
906 Invalid Descriptor
907 Invalid JAR
908 Incompatible Configuration or Profile
909 Application Authentication Failure
910 Application Authorization Failure
911 Push Registration Failure
912 Deletion Notification
Please be aware that the method used by the handset, as per the specifications, is POST.
Using a GET (URL encoding) style for the URL will fail. This is not the correct use of the
MIDlets JAD parameters.
Possible Screen Messages Seen With Downloading:
If JAR -file size does not match with specified size, it displays "Failed Invalid
File". Upon time-out, the handset goes back to browser.
When downloading is done, the handset displays a transient notice "Download
Completed" and starts to install the application.
Upon completing installation, the handset displays a transient notice "Installed"
and returns to Browser after time-out.
If the MANIFEST file is wrong, the handset displays a transient notice "Failed File
Corrupt" and returns to Browser after time-out.
If JAD does not contain mandatory attributes, "Failed Invalid File" notice appears
Method 2 - Direct Cable & Motorola MIDway Tool
The direct cable approach can be performed using a tool available from MOTOCODER
called MIDway. The version available of writing is 2.8, which supports USB cable
download. In order to use the tool properly, review FAQ 64 which contains the following
about downloading:
1. MIDway 2.8.x executable
2. USB Driver for the cable to handset
3. Instructions on installation
4. User Guide for 2.8.x MIDway
21
Advertisement
Table of Contents
