Release notes for Sony Ericsson SDK 2.5.0 for the Java(TM) ME Platform

Table of Contents:

1. System Requirements

2. SDK description (API and phone support)

3. Documentation

4. Change log

5. Sony Ericsson Developer World

System Requirements

Operation System

Microsoft Windows XP/Vista

Required hardware & memory

250 MB hard disk. IDE will requires additional hard disk space.
256 MB system RAM.
500 MHz CPU.

Required Software (IMPORTANT)

Java SE Development Kit (JDK) 1.6 or higher (JDK 1.6 is recommended).
- Available from http://java.sun.com/j2se/
DirectX 8.1 or later
- Available from http://www.microsoft.com/downloads/details.aspx?FamilyID=0A9B6820-BFBB-4799-9908-D418CDEAC197&displaylang=en

3rd party plugins requirements

SDK includes SPOT xde(R) Player from VoiceAge Networks. This package is required for 3GP, MPEG4, AMR and MP3 playback. You should install this package, or the emulator will not work.
Note Antivirus programs can prevent you from installing SPOT xde® Player DLL. Temporarily disable your antivirus program and rerun the SPOT xde® Player DLL installation program.
Note Administrator privileges are required to successfully install SPOT xde® Player DLL.
Windows Script 5.6 (required by the SPOT xde(R) Player)
Check the version of Windows Script by running "cscript" from the command prompt. If you do not see Windows Script Host Version 5.6, download and install Windows Script 5.6 from the Microsoft website using the provided links.
For Windows 2000 and Windows XP: download
For Windows Server 2003: download

Installation

It is recommended that you install the Sony Ericsson SDK 2.5.0 for the Java(TM) ME Platform in a directory path without spaces. E.g. "My_own_directory" instead of "My own directory"

Description of support

This suite of tools supports Java development for the following Sony Ericsson phones:

MIDP 1.0 and CLDC 1.04:
- P800 series
- T610 series
- T630 series
- Z600 series

MIDP 2.0 and CLDC 1.0 HI:
- Sony Ericsson Symbian Java Platform 2

MIDP 2.0 and CLDC 1.1:
- Sony Ericsson Java Platform 2+
- Sony Ericsson Symbian Java Platform 3+

Note that on-device debugging (ODD) is not supported on the Sony Ericsson Symbian Java Platform

Detailed phone specifications including supported JSRs, memory/heap, Java multimedia, Java bluetooth and Java 3D support are described in the Developers' Guidelines available at Sony Ericsson Developer World

For detailed lists of new features, bugfixes, and known issues, please see the release notes in the SDK documentation.

The main features in the Sony Ericsson SDK 2.5.0 for the Java(TM) ME Platform:

API and emulation support

The Sony Ericsson SDK for the Java(TM) ME Platform is a modified version of Sun Java Wireless Toolkit (WTK 2.5.0).

After installation, there are two subdirectories located in the J2ME_SDK\PC_Emulation directory, WTK1 and WTK2. These correspond to Sun Microsystems Wireless Toolkit 1.04.01 (WTK1) and Sun Java Wireless Toolkit 2.5.0 (WTK2) respectively.

WTK1 API/emulation

WTK1 has been modified to support multimedia playback emulation
- MMAPI (JSR 135)

The WTK1 subdirectory supports the following phone emulation:
- P800
- T610, T616, T630
- Z600

WTK2 API/emulation

WTK2 has been modified to support these additional APIs
- Mascot Capsule Version 3 (MCv3).
- VSCL (Vodafone Specific Class Library)

The WTK2 subdirectory supports both the Sony Ericsson Java Platform and Sony Ericsson Symbian Java Platform.

Java APIs for Bluetooth (JSR 82) are supported on the following platforms:

- Sony Ericsson Java Platform 5+ (optional)
- Sony Ericsson Symbian Java Platform 2+ (optional)

Mascot Capsule Version 3 and Mobile 3D Graphics API for the Java ME platform (JSR 184) is supported on the following platforms:

- Sony Ericsson Java Platform 3+

PDA Optional Packages for the Java ME platform (JSR 75) is supported on the following platforms:

- Sony Ericsson Java Platform 5+
- Sony Ericsson Symbian Java Platform 2+

Web Services for the Java ME platform (JSR 172 ) is supported on the following platforms:

- Sony Ericsson Java Platform 6+
- Sony Ericsson Symbian Java Platform 3+

Scalable 2D Vector Graphics API for J2ME (JSR 226) is supported on the following platforms:

- Sony Ericsson Java Platform 8+
- Sony Ericsson Symbian Java Platform 3+

Note that JSR-226 was added in later software revisons of Sony Ericsson Symbian Java Platform 3 phones

Wireless Messaging 2.0 (JSR 205) is supported on the following platforms:

- Sony Ericsson Java Platform 6+
- Sony Ericsson Symbian Java Platform 2+

Java Binding for the OpenGL® ES API (JSR 239) is supported on the following platforms:

- Sony Ericsson Java Platform 8+

Mobile Sensor API (JSR 256) is supported on the following platforms:

- Sony Ericsson Java Platform 8+

Mobile Service Architecture (JSR 248) is supported on the following platforms:

- Sony Ericsson Java Platform 8+

Note that Mobile Service Architecture (MSA) is an umbrella of many different JSR, including JSR-211, JSR-179, JSR-238, JSR-229, JSR-226, JSR-180

On Device Debugging (ODD)

This toolset is located in the JavaME_SDK_CLDC\OnDeviceDebug folder.

Use of this toolset requires a Sony Ericsson phone, enabling developers to perform application/Midlet debugging directly from the phone. This feature enables you to pinpoint any SW errors which are hard to trap in an emulator environment.

Connection Proxy

Communication between the PC and the phone is handled through the "Connection Proxy" tool using serial/USB data cable, Bluetooth or Infrared.

Note that Sony Ericsson Java Platform 8 phones requires "Developer Mode" to be enabled through the service menu before the connection proxy can be used. The service menu can be accessed through the follow stick and key sequence: >* <<* <*

Device Explorer

With "Device Explorer" tool, developers are able to directly manipulate MIDlets and Java management in the phone directly from the PC. This includes uploading, start, pause, resume, delete and stopping MIDlet execution on the phone from the convenience of your development environment. Furthermore, developers can perform garbage collection, heap trace, examine trace messages and stdout functions.

By combining this toolset with a UEI compliant IDE, midlet source code can be debugged using the VM on the actual phone!

Phones that support On Device Debugging (ODD)

MIDP 1.0 and CLDC 1.04:

- T610 series
- T630 series
- Z600 series

MIDP 2.0 and CLDC 1.1:

- Sony Ericsson Java Platform 2+

Note that the Sony Ericsson Symbian Java Platform does not support on-device debugging.

Compatibility

The Sony Ericsson SDK 2.5.0 for the Java(TM) ME Platform is compatible with the following specifications:
- CLDC 1.0
- CLDC 1.1
- MIDP 1.0
- MIDP 2.0
- MMAPI 1.1 (JSR 135)
- WMA 1.1 (JSR 120)
- WMA 2.0 (JSR 205)
- Mobile 3D Graphics (JSR 184)
- Bluetooth and OBEX (JSR 82)
- PDA Optional Package (JSR 75)
- Web Services for Java ME (JSR 172)
- Advanced Multimedia Supplements (JSR 234)
- Mobile Service Architecture (JSR 248)

- Unified Emulator Interface (UEI)

Documentation

The SDK includes Javadoc for
- MIDP 1.0, MIDP 2.0, CLDC 1.0 and CLDC 1.1.
- JSR 135, JSR 120, JSR 205, JSR 184, JSR 82, JSR 75, JSR 172, JSR 234, JSR 248
- Mascot Capsule Ver. 3

FAQ

Question: What is "Java Platform x " and why dont I see a selection for my specific phone ?
Answer: Sony Ericsson has a Java platform strategy and, with the advent of Java Platform 7, we have introduced the concept to the SDK. By identifying their screen size you can simply use the generic profiles, such SonyEricsson_JP7_128x128, SonyEricsson_JP7_128x160, SonyEricsson_JP8_176x220 or SonyEricsson_JP8_240x320. As a developer this allows you to concentrate on two variables, the platform and the screen size.

Question: How accurate is phone emulation in the Wireless Toolkit?
Answer: The Wireless Toolkit emulator provides a rough approximation of the Java(TM) ME Platform in the actual phone. The emulation of the navigation and input behavior does not exactly correspond to the actual device. For more detailed information about the operation and function of the buttons on the device please refer to the User's Guide which can be downloaded from http://www.sonyericsson.com/developer/java .

Question: What if the Connection Proxy does not connect to the phone?
Answer(s):

Verify that the serial cable is securely attached to both the phone and the PC.
Click the "Connect" button to retry the connection.
Verify that the correct COM port has been configured for the Connection Proxy (COM1, COM2, etc).
Reduce the baud rate (for example, from 115200 to 57600).
Close the Device Explorer, close the Connection Proxy, and then restart the Device Explorer.
Disable the cable pull listener by setting the serialproxy.disable_cable_pull_listener property to false in the sdkme.properties file

Question: Which serial cable should we use to connect the PC and phone?
Answer: The DRS-11 Enhanced RS 232 Cable or the DCU-10 USB Cable. For more information, go to http://www.sonyericsson.com/support

Question: I cannot connect to the phone using a USB cable ?
Answer: Having connected a phone and followed the driver installation prompts, 4 new COM ports will be created. You must select the lowest COM port number in order to succefully connect. For example, if your system originally had 3 COM ports 1,2 and 3 and, having installed all the necessary phone drivers, ports 4,5,6 and 7 are created, you should select COM port 4 in order to successfully establish a connection. Please refer to http://www.sonyericsson.com/support for more extensive support.

Question: I want to use Bluetooth to connect to my phone. Which adapter should I use?
Answer: We have tested the following adapters and found these to work well.

3COM Bluetooth USB Adapter (3CREB96)
Belkin Bluetooth USB Adapter, 10m (F8T003)
IOGear Bluetooth USB Adapter, 10m (GBU301)
[Note: Requires that the Network Access and Dial-up Networking Services be disabled! ]
D-Link Bluetooth USB Adapter (DBT120)

Question: How do I change the COM port settings for the Connection Proxy?
Answer:

From the Connection Proxy window, click "File" -> "Settings" to open the settings window.
Change the COM port settings and then click "OK" to close the window and save your changes.
Click "Disconnect" and then click "Connect" to make a connection using the changed settings.

Question: How do I change the advanced settings for the Connection Proxy and Device Explorer?
Answer:

Click "Start" -> "Programs" -> "Java ME SDK for CLDC" -> "Connection Proxy Settings" to open the properties file (C:\SonyEricsson\JavaME_SDK_CLDC\OnDeviceDebug\lib\sdkme.properties).
Edit and save the properties file.
Close the Device Explorer and close the Connection Proxy.
Open the Device Explorer and/or Connection Proxy and the changes to the properties file will take effect.

Question: What can be done if the sdkme.properties has been corrupted or contains invalid settings with no back up ?
Answer: Remove or rename the corrupted sdkme.properties file and then restart the connection proxy. A new file with the default settings is generated.

Question: When I use my IDE to run a MIDlet on the device, the first MIDlet (alphabetical order) in the MIDlet suite is always executed. How do I run the other MIDlets in a suite that contains multiple MIDlets?
Answer: Install the MIDlet into the phone and either start the MIDlet from the phone or start it using this SDK's Device Explorer tool.

Question: Using JBuilder to build a MIDP project that uses " Sony Ericsson SDK 2.5.0 for the Java(TM) ME Platform (Debug On-Device)" results in a class preverifying error. How do we work around this problem?
Answer: Set the project build target VM to "All Java SDKs".

Question: Which Sony Ericsson phones support on-device source-level debugging?
Answer: All Sony Ericsson MIDP 1 and MIDP 2 support on-device debugging with the exception of Symbian based phones.

Question: Can the SDK be used to install a Java MIDlet into the phone?
Answer: Yes. Java MIDlets are packaged as a .jad and .jar file pair. Save these files in a directory on your PC and then use the SDK's Device Explorer to install them on the phone. As a short cut, select only the .jad file and then click "Install". The .jar file will be automatically located if it has been stored in the same directory. You may also use the ejava commandline tool to list, install or remove midlets.

Question: The message "response timed out" is displayed while using the SDK command line tool. What can be done?
Answer: Edit the sdkme.properties file and increase the time out, or disable the time out by setting it to "0". Search for the following properties: " timeout.readatcmd ", " timeout.proxy " and " ping.time ".

Question: How do I build my project using APIs like Mascot Capsule Micro3D Version 3 API?
Answer: Create a new project in Ktoolbar. Select Project->Settings Menu, on API Selection tab choose "Custom" Platform. Check the appropriate checkbox "Mascot Capsule V3 API". Now you will be able to build your project with support of Mascot Capsule V3 API.

Question: How do I take snapshots of the emulated screen?
Answer: In the emulator window, you select MIDlet > Take snapshot in menu. You can also press F12 in the emulator window. The snapshot will be stored under /snapshots in same directory as the jad file of the midlet.

Question: How do I create project from a midlet jar or jad file?
Answer: In Ktoolbar, select File > Create Project from jad/jar ... Specify the jar and/or the jad file that are subject for importing. Press Create. If you only specify jar file, a jad file will be created from the manifest of the jar file - this requires a valid manifest file in the jar. If you only specify jad file, jar file will pointed out from jad file properties, and after jar file extraction specified jad file will be copied to project directory. On specification of both jar and jad, the jar file will be extracted and jad file will be copied. Additionally, if the MIDlet uses APIs that are not emulated, you cannot run the MIDlet.

KNOWN ISSUES

Question: My phone contains an application named tempXXXX?
Answer: This is a temporary skeleton Java application that is created when you debug an application using an IDE and the on-device source-level debugging feature of the Sony Ericsson SDK 2.5.0 for the Java(TM) ME Platform. You should remove this temporary application from the phone.

Question: When I try to start a pre-installed Java application using Device Explorer, the following error message is displayed: "Unknown status code: Internal method error: point-3 OAFcode=19 EXEcode=0".
Answer: Start the application using the phone's user interface and then stop the application. This will complete the installation process for the pre-installed application and allow the application to be started using the SDK.

Question: When I try to install a MIDlet using Device Explorer, the following error message is displayed: "Unknown status code: Internal method error: point-2 OAFcode=24 EXEcode=0".
Answer: This error occurs sometimes when the MIDlet has an icon. A work around is to remove the reference to the icon file from the second parameter of the MIDlet-N property. The parameter should be empty in both the jad file and the jar file's manifest. For example, "MIDlet-1: TilePuzzle, , example.tilepuzzle.TilePuzzle".

Question: When running or debugging my MIDlet in the phone, I get a file not found error for any resources files such as images (.jpg, .png, etc). I can see these files in the IDE project. Why does the phone not find these files?
Answer: Copy the resource files into your project's classpath so that they will be found when the phone requests them. For example, an IDE project might place image files in the /res folder. Copy these files to the /classes folder which should be included in the classpath. Alternatively, add the /res folder to your project's classpath.

CHANGE LOG

This section is a high level change log for different releases of the Sony Ericsson SDK 2.5.0 for the Java(TM) ME Platform. See online documentation for known issues, SW error fix, and functional updates

Version 2.5.0 (August 2007)
-------------------------------------
- Connection Proxy minor fixes and improvements

Version 2.5.0 Beta (July 2007)
----------------------------------------
- New release based upon Sun Wireless Toolkit 2.5.0
- New connection proxy to improve connectivity between phone and PC for Sony Ericsson Java Platform 8
- New support for Chinese fonts
- New compile and limited runtime support for the accelerometer sensor of the Mobile Sensor API (JSR-256)
- New support for multiple midlets (MVM) through the Device Explorer tool
- Misc minor fixes and improvements

Version 2.2.4 (June 2006)
----------------------------------
- Introduced platformised emulation for Sony Ericsson Java Platform 7
- Introduced platformised on-device debugging for Sony Ericsson Java Platform 7
- Improved stability of on-device debugging
- Updated Eclipse plug-ins for usage with Eclipse 3.1
- Added support for multiple midlets (MVM) through the ejava command line tool
- Added compile-time support for the camera functionality found in JSR 234: Advanced Multimedia Supplements
- Added compile-time support for VSCL 2.1
- Added emulator and on-device debugging profiles for product announcements
- Added support for Sony Ericsson platform version system property
- Numerous minor fixes and improvements

Version 2.2.3 (September 2005)
-------------------------------------------
- Added class loading restriction ensuring only device relevant classes can be used during compile and runtime
- Changed default behaviour of File Explorer in Device Explorer to point to "Favorites Folder" list reducing start up time
- Synchronisation added between selected device and Ktoolbar Settings compilation target platform in WTK
- Numerous minor fixes and improvements

Version 2.2.2 (August 2005)
---------------------------------
- Added support for the W600
- Removed S600, added support for the W550 (ODD)
- FIX: Memory leak in JSR 184 implementation

Version 2.2.1 (June 2005)
---------------------------------
- System properties exposed by SDK better reflect properties defined in phone
- Added 3GP playback support (under JSR 135)
- Further ODD refinement (Connection Proxy)
- Inclusion and first release of Device Explorer Eclipse Plugin
- Added support for W800, S600 and Z520 emulators

Version 2.2.0 (March 2005)
---------------------------------
- SDK is based on Sun Microsystems Wireless Toolkit 2.2
- Usability enhancements of ODD tools (Connection Proxy and Device Explorer)
- FIX: On-device debugging with various IDEs
- Added support for J300, K300, K600, K750, W800 and Z800 emulators

Version 2.1.5 (November 2004)
---------------------------------
- Added support for V800 emulator
- Added VSCL API
- Snapshot feature in emulation (Via menu or F12)
- True font and softkey emulation for
*Z1010, K700i, F500i, K500i, K508i, Z500a, Z500i, S700i, S710a, V800
NOTE Only Western font emulation is supported
- Import a JAR/JAD as a project
- More descriptive Device Connectivity error messages
- FIX: Memory leaks in J2SE when closing emulator from KToolbar
- FIX: Device connectivity SW errors
- FIX: DirectX install

Version 2.1.4 Beta (September 2004)
---------------------------------
- Full Java 3D emulation; Mascot Capsule Micro3D Ver.3 and JSR 184 API
- Added support for S700 emulator
- Fix SW errors

Version 2.1.3 Beta (July 2004)
---------------------------------
- Added support for K500, K508 emulators
- Added JSR 184 API Javadoc refernce

Version 2.1.2 Beta (May 2004)
-----------------------------
- Added support for Z1010, K700, Z500 and F500i emulators
- Added Mascot Capsule Micro3D Ver. 3 APIs and Javadoc

SONY ERICSSON DEVELOPER WORLD

For latest Sony Ericsson SDK for the Java(TM) ME Platform and Developers' Guidelines for Sony Ericsson phones, visit Sony Ericsson Developer World.

There you will also find tips&tricks, knowledge base, training material, white papers and discussions forums.