Motorola E680 - Smartphone - GSM Instruction Manual

Technical Manual
IBU
Version 1.5
Motorola E680 Handset
J2ME™ Developer Guide

2
Table of Contents
TABLE OF CONTENTS ............................................................................................................................... 2
1 INTRODUCTION ...................................................................................................................................... 6
PURPOSE...................................................................................................................................................... 6
AUDIENCE .................................................................................................................................................... 6
DISCLAIMER ................................................................................................................................................ 6
REFERENCES ................................................................................................................................................ 7
REVISION HISTORY .................................................................................................................................... 8
DEFINITIONS,ABBREVIATIONS,ACRONYMS............................................................................................. 8
DOCUMENT OVERVIEW .................................................................................................................................. 9
2 J2ME INTRODUCTION......................................................................................................................... 11
THE JAVA 2PLATFORM,MICRO EDITION (J2ME).............................................................................. 11
THE MOTOROLA J2ME PLATFORM............................................................................................................. 12
RESOURCES AND API’S AVAILABLE........................................................................................................ 12
3 DEVELOPING AND PACKAGING J2ME APPLICATIONS............................................................. 14
GUIDE TO DEVELOPMENT IN J2ME.......................................................................................................... 14
4 DOWNLOADING APPLICATIONS........................................................................................................ 16
METHOD OF DOWNLOADING......................................................................................................................... 16
ERROR LOGS.............................................................................................................................................. 18
5 APPLICATION MANAGEMENT............................................................................................................. 20
DOWNLOADING A JAR FILE WITHOUT A JAD.......................................................................................... 20
MIDLET UPGRADE ..................................................................................................................................... 20
INSTALLATION AND DELETION STATUS REPORTS.................................................................................... 21
6 MULTIPLE APPLICATIONS............................................................................................................... 22
MULTIPLE APPLICATIONS......................................................................................................................... 22
7 JAD ATTRIBUTES................................................................................................................................23
JAD /MANIFEST ATTRIBUTE IMPLEMENTATIONS .................................................................................. 23
8 GAMING API/MULTIPLE KEY PRESS............................................................................................ 26
GAMING API............................................................................................................................................. 26
MULTIPLE KEY PRESS SUPPORT .............................................................................................................. 26

Table of Contents
3
9 JSR 184 ................................................................................................................................................ 29
OVERVIEW .................................................................................................................................................. 29
MOBILE 3D API...................................................................................................................................... 29
Mobile 3D API File Format Support ............................................................................... 30
Mobile 3D Graphics – M3G API ........................................................................................... 30
10 VIBE AND BACKLIGHT API .......................................................................................................... 38
VIBE AND BACKLIGHT API...................................................................................................................... 38
11 JAVA.LANG IMPLEMENTATION...................................................................................................... 40
JAVA.LANG SUPPORT................................................................................................................................. 40
12 NETWORK APIS.................................................................................................................................. 41
NETWORK CONNECTIONS............................................................................................................................. 41
USER PERMISSION .................................................................................................................................... 43
INDICATING A CONNECTION TO THE USER.............................................................................................. 43
HTTPS CONNECTION ................................................................................................................................44
13 JSR 135 MOBILE MEDIA API...................................................................................................... 46
JSR 135 MOBILE MEDIA API............................................................................................................... 46
TONECONTROL............................................................................................................................................ 48
VIDEO CONTROL ........................................................................................................................................ 48
Snapshot Image............................................................................................................................. 48
GUICONTROL............................................................................................................................................. 48
VOLUMECONTROL ........................................................................................................................................ 49
STOPTIMECONTROL.................................................................................................................................... 49
MANAGER CLASS ........................................................................................................................................ 49
AUDIO MEDIA............................................................................................................................................ 50
14 JSR 120 – WIRELESS MESSAGING API .................................................................................. 52
WIRELESS MESSAGING API (WMA)........................................................................................................ 52
SMS CLIENT MODE AND SERVER MODE CONNECTION.............................................................................. 52
SMS PORT NUMBERS................................................................................................................................. 53
SMS MESSAGE TYPES............................................................................................................................... 54
SMS MESSAGE STRUCTURE ....................................................................................................................... 54
SMS NOTIFICATION ................................................................................................................................. 54
15 PHONEBOOK ACCESS API............................................................................................................... 60
PHONEBOOK ACCESS API ......................................................................................................................... 60
PHONEBOOK ACCESS API PERMISSIONS.................................................................................................. 60
16 FILE SYSTEM ACCESS API .......................................................................................................... 65
FILE CONNECTION METHODS..................................................................................................................... 65
ESTABLISHING A CONNECTION ................................................................................................................. 65
CONNECTION BEHAVIOR............................................................................................................................. 66
SECURITY .................................................................................................................................................. 66
17 TELEPHONY API................................................................................................................................72
DIALER CLASS.......................................................................................................................................... 72
CLASS DIALEREVENT................................................................................................................................72
CLASS DIALER.......................................................................................................................................... 74
getDefaultDialer........................................................................................................................ 75

4
setDialerListener ..................................................................................................................... 75
startCall ........................................................................................................................................ 75
startCall ........................................................................................................................................ 76
sendExtNo ........................................................................................................................................ 76
endCall............................................................................................................................................. 76
INTERFACE DIALERLISTENER................................................................................................................... 77
SAMPLE DIALERLISTENER IMPLEMENTATION ........................................................................................... 77
notifyDialerEvent ..................................................................................................................... 79
CLASS HIERARCHY .................................................................................................................................... 79
INTERFACE HIERARCHY............................................................................................................................. 79
18 DRM PROTECTION IN JAVA .......................................................................................................... 80
OVERVIEW .................................................................................................................................................. 80
RIGHTS ENFORCEMENT -MIDLETS ACCESSING DRM PROTECTED CONTENT........................................... 80
ACQUIRING LICENSE ................................................................................................................................80
19 CLDC 1.1............................................................................................................................................ 81
CLDC 1.1 COMPLIANCE.......................................................................................................................... 81
20 JTWI..................................................................................................................................................... 86
OVERVIEW .................................................................................................................................................. 86
CLDC RELATED CONTENT FOR JTWI....................................................................................................... 87
MIDP 2.0 SPECIFIC INFORMATION FOR JTWI .................................................................................... 88
WIRELESS MESSAGING API 1.1 (JSR 120) SPECIFIC CONTENT FOR JTWI.................................. 89
MOBILE MEDIA API 1.1 (JSR 135) SPECIFIC CONTENT FOR JTWI.............................................. 90
MIDP 2.0 SECURITY SPECIFIC CONTENT FOR JTWI .......................................................................... 90
21 MIDP 2.0 SECURITY MODEL........................................................................................................ 91
UNTRUSTED MIDLET SUITES.................................................................................................................... 92
UNTRUSTED DOMAIN .................................................................................................................................. 92
TRUSTED MIDLET SUITES ....................................................................................................................... 93
PERMISSION TYPES CONCERNING THE HANDSET ...................................................................................... 93
USER PERMISSION INTERACTION MODE................................................................................................... 93
IMPLEMENTATION BASED ON RECOMMENDED SECURITY POLICY............................................................... 94
TRUSTED 3RD PARTY DOMAIN.................................................................................................................... 94
TRUSTED MIDLET SUITES USING X.509 PKI..................................................................................... 95
SIGNING A MIDLET SUITE...................................................................................................................... 96
SIGNER OF MIDLET SUITES.................................................................................................................... 96
MIDLET ATTRIBUTES USED IN SIGNING MIDLET SUITES.................................................................... 96
CREATING THE SIGNING CERTIFICATE ................................................................................................... 96
INSERTING CERTIFICATES INTO JAD .................................................................................................... 97
CREATING THE RSA SHA-1 SIGNATURE OF THE JAR.......................................................................... 97
AUTHENTICATING A MIDLET SUITE ........................................................................................................ 97
VERIFYING THE SIGNER CERTIFICATE ................................................................................................... 98
VERIFYING THE MIDLET SUITE JAR..................................................................................................... 98
APPENDIX A: AUDIO MIX TABLE.................................................................................................... 100
APPENDIX B: KEY MAPPING............................................................................................................. 101
KEY MAPPING FOR THE E680 ............................................................................................................... 101
APPENDIX C: MEMORY MANAGEMENT CALCULATION.................................................................. 102

Table of Contents
5
AVAILABLE MEMORY ................................................................................................................................102
MEMORY CALCULATION FOR MIDLETS .................................................................................................... 102
APPENDIX D: FAQ................................................................................................................................103
ONLINE FAQ........................................................................................................................................... 103
APPENDIX E: HTTP RANGE ............................................................................................................... 104
GRAPHIC DESCRIPTION........................................................................................................................... 104
APPENDIX F: SPEC SHEET ............................................................................................................... 105
E680 SPEC SHEET ................................................................................................................................105

6
1
Introduction
Purpose
This document describes the application program interfaces used to develop Motorola
compliant Java™ 2 Platform, Micro Edition (J2ME™) applications for the E680 handset.
Audience
This document is intended for premium J2ME developers and specific carriers involved
with the development of J2ME applications for the E680 handset.
Disclaimer
Motorola reserves the right to make changes without notice to any products or services
described herein. “Typical” parameters, which may be provided in Motorola Data sheets
and/or specifications can and do vary in different applications and actual performance
may vary. Customer’s technical experts will validate all “Typicals” for each customer
application.
Motorola makes no warranty with regard to the products or services contained herein.
Implied warranties, including without limitation, the implied warranties of merchantability
and fitness for a particular purpose, are given only if specifically required by applicable
law. Otherwise, they are specifically excluded.
No warranty is made as to coverage, availability, or grade of service provided by the
products or services, whether through a service provider or otherwise.
No warranty is made that the software will meet your requirements or will work in
combination with any hardware or applications software products provided by third
parties, that the operation of the software products will be uninterrupted or error free, or
that all defects in the software products will be corrected.

1
Introduction
7
In no event shall Motorola be liable, whether in contract or tort (including negligence), for
any damages resulting form use of a product or service described herein, or for any
indirect, incidental, special or consequential damages of any kind, or loss of revenue or
profits, loss of business, loss of information or data, or other financial loss arising out of or
in connection with the ability or inability to use the Products, to the full extent these
damages may be disclaimed by law.
Some states and other jurisdictions do not allow the exclusion or limitation of incidental or
consequential damages, or limitation on the length of an implied warranty, so the above
limitations or exclusions may not apply to you.
This warranty gives you specific legal rights, and you may also have other rights, which
vary from jurisdiction to jurisdiction.
Motorola products or services are not designed, intended, or authorized for use as
components in systems intended for surgical implant into the body, or other applications
intended to support or sustain life, or for any other application in which the failure of the
Motorola product or service could create a situation where personal injury or death may
occur.
Should the buyer purchase or use Motorola products or services for any such unintended
or unauthorized application, buyer shall release, indemnify and hold Motorola and its
officers, employees, subsidiaries, affiliates, and distributors harmless against all claims,
costs, damages, and expenses, and reasonable attorney fees arising out of, directly or
indirectly, any claim of personal injury or death associated with such unintended or
unauthorized use, even if such claim alleges that Motorola was negligent regarding the
designing or manufacture of the product or service.
Motorola recommends that if you are not the sole author or creator of the graphics, video,
or sound, you obtain sufficient license rights, including the rights under all patents,
trademarks, trade names, copyrights, and other third party proprietary rights.
References
Reference Link
RFC 2068 http://ietf.org/rfc/rfc2068.txt
SAR http://www.wapforum.org
MIDP 2.0 http://java.sun.com/products/midp/
JSR 118 http://www.jcp.org
JSR 120 http://www.jcp.org
JSR 135 http://www.jcp.org
Sun MIDP 2.0 SDK http://java.sun.com/products/midp/
TLS protocol version 1.0 http://www.ietf.org/rfc/rfc2246.txt
SSL protocol version 3.0 http://home.netscape.com/eng/ssl3/draft302.txt
GSM 03.38 standard http://www.etsi.org

8
GSM 03.40 standard http://www.etsi.org
RFC 2437 http://ietf.org/rfc/rfc2437.txt
Sun J2ME http://java.sun.com/j2me/).
Revision History
Version Date Name Reason
0.1 January 14, 2004 Motorola Initial Draft
0.2 February 1, 2004 Motorola Revised Draft
0.3 February 10, 2004 Motorola Revised Draft
0.4 February 16, 2004 Motorola Updated TOC
0.5 March 1, 2004 Motorola JSR 184 added
1.4 June 22, 2004 Motorola Updated per SW
Definitions, Abbreviations, Acronyms
Acronym Description
AMS Application Management Software
API Application Program Interface.
CLDC Connected Limited Device Configuration
GPS Global Positioning System
IDE Integrated Development Environment
ITU International Telecommunication Union
JAD Java Application Descriptor
JAL Java Application Loader
JAR Java Archive. Used by J2ME applications for compression and packaging.
J2ME Java 2 Micro Edition
JSR 120 Java Specification Request 120 defines a set of optional APIs that provides
standard access to wireless communication resources.
JVM Java Virtual Machine

1
Introduction
9
KVM Kilo Virtual Machine
MIDP Mobile Information Device Profile
MMA Multimedia API
MT Mobile Terminated
OEM Original Equipment Manufacturer
OTA Over The Air
RMS Record Management System
RTOS Real Time Operating System
SDK Software Development Kit
SMS Short Message Service
SMSC Short Messaging Service Center
SU Subscribe Unit
UI User Interface
URI Unified Resource Identifier
VM Virtual Machine
WMA Wireless Messaging API
Document Overview
This developer’s guide is organized into the following chapters and appendixes:
Chapter 1 –Introduction: this chapter has general information about this document,
including purpose, scope, references, and definitions.
Chapter 2 –J2ME Introduction: this chapter describes the J2ME platform and the
available resources on the Motorola E680 handset.
Chapter 3 –Developing and Packaging J2ME Applications: this chapter describes
important features to look for when selecting tools and emulation environments. It also
describes how to package a J2ME application, how to package a MIDlet, and generate
JAR and JAD files properly.
Chapter 4 –Downloading Applications: this chapter describes the process for
downloading applications.
Chapter 5 –Application Management: this chapter describes the lifecycle,
installation/de-installation, and updating process for a MIDlet suite.
Chapter 6 -- Multiple Applications: this chapter describes all multiple applications.
Chapter 7– JAD Attributes: this chapter describes what attributes are supported.
Chapter 8 – Gaming API/Multiple Key Press: this chapter describes the Gaming API.

10
Chapter 9 – JSR 184: this chapter describes JSR 184.
Chapter 10 -- Vibe and Backlight API – this chapter describes the Vibe and Backlight
API.
Chapter 11 –Java.lang Implementation: this chapter describes the java.lang
implementation.
Chapter 12 –Networking APIs: this chapter describes the Java Networking API.
Chapter 13 – JSR 135 Mobile Media: this chapter describes image types and supported
formats.
Chapter 14 – JSR 120 Wireless Messaging API: this chapter describes JSR 120
implementation.
Chapter 15 -- Phonebook Access: this chapter describes the Phonebook Access API.
Chapter 16 – File System Access: this chapter describes the File System Access API.
Chapter 17 – Telephony API: this chapter describes the Telephony API.
Chapter 18 – DRM Protection in Java: this chapter describes DRM protection of files in
Java.
Chapter 19 – CLDC 1.1: this chapter describes CLDC 1.1
Chapter 20 – JTWI: this chapter describes JTWI functionality.
Chapter 21 – MIDP 2.0 Security Model: this chapter describes the MIDP 2.0 default
security model.
Appendix A –Key Mapping: this appendix describes the key mapping of the Motorola
E680 handset, including the key name, key code, and game action of all Motorola keys.
Appendix B –Memory Management Calculation: this appendix describes the memory
management calculations.
Appendix C – FAQ: this appendix provides a link to the dynamic online FAQ.
Appendix D – HTTP Range: this appendix provides a graphic description of HTTP
Range.
Appendix E – Spec Sheet: this appendix provides the spec sheet for the Motorola E680
handset.

2
J2ME Introduction
11
2
J2ME Introduction
The Motorola E680 handset includes the Java™ 2 Platform, Micro Edition, also known as
the J2ME platform. The J2ME platform enables developers to easily create a variety of
Java applications ranging from business applications to games. Prior to its inclusion,
services or applications residing on small consumer devices like cell phones could not be
upgraded or added to without significant effort. By implementing the J2ME platform on
devices like the Motorola E680 handset, service providers, as well as customers, can
easily add and remove applications allowing for quick and easy personalization of each
device. This chapter of the guide presents a quick overview of the J2ME environment and
the tools that can be used to develop applications for the Motorola E680 handset.
The Java 2 Platform, Micro Edition (J2ME)
The J2ME platform is a new, very small application environment. It is a framework for the
deployment and use of Java technology in small devices such as cell phones and pagers.
It includes a set of APIs and a virtual machine that is designed in a modular fashion
allowing for scalability among a wide range of devices.
The J2ME architecture contains three layers consisting of the Java Virtual Machine, a
Configuration Layer, and a Profile Layer. The Virtual Machine (VM) supports the
Configuration Layer by providing an interface to the host operating system. Above the VM
is the Configuration Layer, which can be thought of as the lowest common denominator of
the Java Platform available across devices of the same “horizontal market.” Built upon this
Configuration Layer is the Profile Layer, typically encompassing the presentation layer of
the Java Platform.
Mobile Information Device
Native System Software
CLDC
MIDP OEM
Classes
MIDP-Compliant
Apps OEM Apps Native
Apps
Mobile Information Device
Native System Software
CLDC
MIDP OEM
Classes
MIDP-Compliant
Apps OEM Apps Native
Apps

12
The Configuration Layer used in the Motorola E680 handset is the Connected Limited
Device Configuration 1.1 (CLDC 1.1) and the Profile Layer used is the Mobile Information
Device Profile 2.0 (MIDP 2.0). Together, the CLDC and MIDP provide common APIs for
I/O, simple math functionality, UI, and more.
For more information on J2ME, see the Sun™ J2ME documentation
(http://java.sun.com/j2me/).
The Motorola J2ME Platform
Functionality not covered by the CLDC and MIDP APIs is left for individual OEMs to
implement and support. By adding to the standard APIs, manufacturers can allow
developers to access and take advantage of the unique functionality of their handsets.
The Motorola E680 handset contain OEM APIs for extended functionality ranging from
enhanced UI to advanced data security. While the Motorola E680 handset can run any
application written in standard MIDP, it can also run applications that take advantage of
the unique functionality provided by these APIs. These OEM APIs are described in this
guide.
Resources and API’s Available
MIDP 2.0 will provide support to the following functional areas on the Motorola E680
handset:
MIDP 2.0
•Application delivery and billing
•Application lifecycle
•Application signing model and privileged security model
•End-to-end transactional security (HTTPS)
•MIDlet push registration (server push model)
•Networking
•Persistent storage
•Sounds
•Timers
•User Interface
•File Image Support (.PNG, .JPEG, .GIF)

2
J2ME Introduction
13
Additional Functionality
•WMA (JSR 120)
•MMA (JSR 135)
•M3D (JSR 184)
•Fun Lights API
•Phonebook API
•File System API
•Telephony API

14
3
Developing and Packaging
J2MEApplications
Guide to Development in J2ME
Introduction to Development
This appendix assumes the reader has previous experience in J2ME development and
can appreciate the development process for Java MIDlets. This appendix will provide
some information that a beginner in development can use to gain an understanding of
MIDlets for J2ME handsets.
There is a wealth of material on this subject on websites maintained by Motorola, Sun
Microsystems and others. Please refer to the following URLs for more information:
http://www.motocoder.com
http://www.java.sun.com/j2me
http://www.corej2me.com/
http://www.javaworld.com/
As an introduction, brief details of J2ME are explained below.
The MIDlet will consist of two core specifications, namely Connected, Limited Device
Configuration (CLDC) and Mobile Information Device Profile (MIDP). Both of these
specifications (Java Specification Requests) can be located at the http://www.jcp.org/ site
for reading.
For MIDP 1.0; JSR 37 should be reviewed.
For MIDP 2.0; JSR 118 should be reviewed.
For CLDC 1.0.4; JSR 30 should be reviewed.
For CLDC 1.1; JSR 139 should be reviewed.
To determine what implementation is on Motorola handset, review the “Java System”
details through the menu on the Motorola handset (located under Java Settings).

3
Developing and Packaging J2ME Applications
15
For beginning development, key points to remember are memory size, processing power,
screen capabilities and wireless network characteristics. These all play an important part
in development of a MIDlet. The specifications listed above are designed to work upon
devices that have these characteristics.
Network conditions would only apply for networked applications such as streaming tickers,
email clients, etc.
In addition to the specifications, an array of tools is available to assist the development
cycle. These range from the command line tools provided with Software Development Kits
(SDK) from Sun (as of writing 1.4.1_04) to Integrated Development Environments (IDEs)
which can be free or purchased. These IDEs come from a range of sources such as Sun,
IBM, Metrowerks and Borland to name a few.
For a look at such environments, review the “Motorola T720 Handset Developer Guide”
which is available from the MOTOCODER website.
In addition to the IDEs and Sun SDK for development, Motorola offers access to our own
SDK which contains Motorola device emulators. From here, a MIDlet can be built and
then deployed onto an emulated target handset. This will enable debugging and validation
of the MIDlet before deployment to a real, physical handset. The latest Motorola SDK can
be downloaded from the MOTOCODER website.
Please refer to the product specifications at the back of this guide for detailed information
on each handset.

16
4
DownloadingApplications
Method of Downloading
The option open to the developer for deploying the MIDlet to a physical Motorola device is
OTA (over -the-air) downloading.
OTA
To use the OTA method, the developer will have a connection through a wireless network
to a content server. This content server could be, for example, Apache
(http://httpd.apache.org) which is free to use, deployable on multiple operating systems,
and has extensive documentation on how to configure the platform.
The required file will be downloaded (either .jad and/or .jar) by issuing a direct URL
request to the file in question or it could be a URL request to a WAP page and a hyperlink
on that page to the target file. This request will be made through the Motorola Internet
Browser (MIB). In MIDP 2.0, the need for a JAD file before download is not required, so
the JAR file can be downloaded directly. The information about the MIDlet will be pulled
from the manifest file.
The transport mechanism used to download the file will be one of two depending on the
support from the network operators WAP Gateway and thesize of file requested.
HTTP Range – see specification RFC 2068 at http://www.rfc-editor.org/rfc.html
if content greater than 30k in size. Below is a ladder diagram showing the flow
through HTTP range transfer, although recall use of the .JAD is optional.
SAR (Segmentation & Reassembly) – see specification of wireless transaction
protocol at the http://www.wapforum.org if less than 100k in size.
During a download of the application, the user will see the MIB 2.2 browser displaying a
progress dialog for either SAR or HTTP Byte Range type downloads.
A complete guide for setting up an OTA server can be obtained through the
MOTOCODER website (http://www.motocoder.com). This includes details of configuring
the server and also example WAP pages.
In this handset, 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.

4
Downloading Applications
17
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
913 Required package not supported by device
999 Other errors
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 will display a dialog stating
“Installation failed. Package invalid.” To dismiss this dialog, press “OK”.
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 dialog “Install complete”. To
dismiss this dialog, press “OK”.
If the MANIFEST file is wrong, the handset displays a dialog stating “Installation
failed. Package invalid.” To dismiss this dialog, press “OK”.
If JAD does not contain mandatory attributes, “Installation failed. Package
invalid.” notice appears.
The USER-AGENT String
The following table describes USER_AGENT strings associated with Motorola devices:
Motorola Device USER_AGENT STRING
E680 User-Agent: MOT-E680/xx.xx.xx MIB/2.2 Profile/MIDP-2.0
Configuration/CLDC-1.1
The USER_AGENT string can be used to identify a handset and render specific content to
it based on it information provided in this string (example CGI on a content server). These
strings can be found in the connection logs at the content server.

18
This table above provides information about the following components:
1. WAP Browser Release, Motorola Internet Browser (MIB) 2.2
2. MIDP version 2.0
3. CLDC version 1.1
4. The Phone Software Version is detailed by xx.xx.xx
Error Logs
The following table represents the error logs associated with downloading applications.
Error Logs Scenario Possible Cause Error Dialog
Failed: Invalid File JAD
Download Missing or incorrectly formatted mandatory JAD attributes
Mandatory:
MIDlet-Name (up to 32 symbols)
MIDlet-Version
MIDlet-Vendor (up to 32 symbols)
MIDlet-JAR-URL (up to 256 symbols)
MIDlet-JAR_Size
906 Installation
failed. Package
invalid.
Download Failed OTA JAR
Download The received JAR size does not match the size indicated 904 Installation failed. Package
invalid.
Cancelled:
<Icon> <Filename>
OTA JAR
Download User cancelled download 902
Download Failed OTA JAR
Download Browser lost connectionwith server
Certification path cannot be validated
JAD signature verification failed
Unknown error during JAD validation
See ‘Details’ field in the dialog for information
about specific error
903 Dowload
failed.
Insufficient Storage OTA JAR
Download Insufficient data space to temporarily store the JAR file 901 Memory Full. Cannot
install
application.
Application Already
Exists OTA JAR Download MIDlet version numbers are identical 905 Attribute Mismatch

4
Downloading Applications
19
Different Version
Exists OTA JAR Download MIDlet version on handset supercedes version being downloaded
Failed File Corrupt Installation Attributes are not identical to respective JAD
attributes
Insufficient Storage Installation Insufficient Program Space or Data Space to
install suite 901 Memory Full. Cannot
install
application.
Application Error Installation Class references non-existent class or method
Security Certificate verification failure
Checksum of JAR file is not equal to
Checksum in MIDlet-JAR-SHA attribute
Application not authorized
Application Expired MIDlet
Launching Security Certificates expired or removed
Application Error MIDlet
Execution Authorization failure during MIDlet execution
Incorrect MIDlet

20
5
Application Management
The following sections describe the application management scheme for the Motorola
E680 handset. This chapter will discuss the following:
•Downloading a JAR without a JAD
•MIDlet upgrade
•Installation and Deletion Status Reports
Downloading a JAR file without a JAD
In Motorola’s MIDP 2.0 implementation, a JAR file can be downloaded without a JAD. In
this case, the user clicks on a link for a JAR file, the file is downloaded, and a confirmation
will be obtained before the installation begins. The information presented is obtained from
the JAR manifest instead of the JAD.
MIDlet Upgrade
Rules from the JSR 118 will be followed to help determine if the data from an old MIDlet
should be preserved during a MIDlet upgrade. When these rules cannot determine if the
RMS should be preserved, the user will be given an option to preserve the data.
The following conditions are used to determine if data can be saved:
•The data is saved if the new MIDlet-version is the same or newer, and if the new
MIDlet-data-space requirements is the same or more than the current MIDlet.
•The data is not saved if the new MIDlet-data-space requirement is smaller than
the current MIDlet requirement.
•The data is not saved if the new MIDlet-version is older than the current version.
If the data cannot be saved, the user will be warned about losing data. If the user
proceeds, the application will be downloaded. If the user decides to save the data from
the current MIDlet, the data will be preserved during the upgrade and the data will be
made available for thenew application. In any case, an unsignedMIDlet will not be
allowed to update a signed MIDlet.