======================================================================= RELEASE NOTES Series 40 SDK 3rd Edition Feature Pack 1 (20 Jun 2006) ======================================================================= This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.OpenSSL.org/). For product support and the latest release notes, please visit Nokia's Developer Home at http://www.forum.nokia.com/ Product Description: ==================== The Series 40 SDK 3rd Edition Feature Pack 1 is based on the Nokia 6136, which is a Series 40 SDK 3rd Edition Feature Pack 1 compatible phone. The SDK provides a development and/or testing environment for Java TM Platform, Micro Edition (Java TM ME) applications, MMS, SMS, WAP and XHTML browser content, WAP Push (Service Indication) messages and Digital Rights Management (DRM). Features: ========= This version of the SDK supports the following Java Specification Requests (JSRs): - Mobile Information Device Profile 2.0 (JSR 118). - Connected Limited Device Configuration 1.1 (JSR 139). - Java Technology for Wireless Industry (JSR 185). - File Connection Optional Package API (JSR 75 File). - Personal Information Management Optional Package API (JSR 75 PIM). - Mobile Media API (JSR 135). - Mobile 3D Graphics API (JSR 184). - Scalable 2D Vector Graphics API (JSR 226). - Wireless Messaging API 2.0 for SMS and MMS (JSR 205). - Web Services JAXP API (JSR 172). The SDK features support for - A Macromedia Flash Lite 1.1 player. - A TCP/IP protocol stack. - various Diagnostics features including on/off on-the-fly tracing, a network traffic monitor and a MIDP memory monitor. The SDK replicates the UI of the Nokia 6136 handset, including the general look, key layout, key definitions, error messages, display and rendering, soft keys, and menu selection. The SDK is shipped with Bulgarian, Dutch, English, French, German, Italian and Portuguese language support as standard. To add additional language support, you may install the World Languages pack from the same web site from which you installed the SDK. The SDK allows MIDP tracing of many Java events. You can enable tracing by using the SDK menu selection: Tools/Preferences/MIDP Monitor. To capture the tracing information to a file, use the SDK command line interface to start the SDK. For example: C:\Nokia\Devices\S40_SDK_3rd_Edition_Feature_Pack_1\bin> emulator -Xnew >>tracelog.txt Tested IDEs: =============== - Eclipse 3.1.2 (requires Nokia Carbide.j) - Nokia Carbide.j 1.0 - Sun NetBeans 4.1 - Sun Wireless Toolkit 2.2 - Sun NetBeans with Mobility Pack 4.1 - Nokia Mobile Internet Toolkit (NMIT) 4.1 - Nokia Developer’s Suite for MMS 1.1 - Adobe GoLive CS and CS2 - MacroMedia Dreamweaver 8 System Requirements: ==================== Supported Platforms: - Microsoft Windows XP Professional SP2 - Microsoft Windows XP Home Edition SP2 - Microsoft Windows XP Professional SP2 Chinese Additional requirement: - Java Runtime Environment 5 or later (JRE 1.5.0_06 was used during the testing of this product) - Adobe Acrobat Reader 5.5 or higher Minimum hardware requirements: - Pentium-class computer with 667 MHz or faster CPU 256 MB RAM , 16-bit color, 1024x768 resolution 100MB of hard disk space Network interface card Recommended hardware configuration: - Pentium-class computer with 1.8 GHz or faster CPU 512 MB RAM , 24-bit color, 1024x768 resolution 140MB of hard disk space Sound card Network interface card Disclaimer: =========== - The SDK contains a version of the 6136 handset software produced approximately six weeks earlier than the version used for the first customer release of the handset. While the SDK software is very similar to that of the handset, it is not identical. It is recommended to do final tests on actual handsets. - The PC rendering of colors in the SDK may not match colors seen on the actual handset. However, the SDK is ideal for verifying pixel location and the general appearance of the handset UI. - Sound simulation in the SDK does not accurately represent the handset. This SDK is not recommended as a primary tool for development of sound. However, it is ideal for verifying sound as part of application testing. Compatibility Issues: ===================== - The SDK may not work well with some sound card/driver combinations. In such cases, sound may be inaudible and MIDlets that use MMAPI may fail. As a workaround try replacing the driver for the sound card. General Information: ==================== When using Java ME traces from the command line in tandem with the instance reuse feature, traces that are implemented on a per-run time basis are cumulative. For example, one run-time you choose to run emulator.exe –Xverbose:gc c:\mymidlet.jad, the midlet will be executed in the running SDK instance with garbage collection traces turned on. Running a second time, emulator.exe –Xverbose:class c:\mymidlet.jad, will cause your midlet to load and run in the running instance with both gc and class traces turned on. You can turn the traces off in the SDK preferences GUI. Alternatively, you can restart the SDK. If you use an upper case letter in the name of a Java MIDlet RMS file, you will see that the name of the RMS file duplicated on your PC contains a box in place of that character. This accurately duplicates the internal file name coding of the handset. Known Problems: ===================== VVAI-6MXSDW Very rarely, the SDK fails to uninstall from the Windows Add or Remove Programs Control Panel applet and displays the error message, "Error loading C:\PROGRA~1\COMMON~1\INSTAL~1\PROFES~1\RunTime\11\00\Intel32\Ctor.dll. The specified module could not be found." Workaround: Cancel from the uninstaller. Instead, run the SDK installer executable. The first dialog in the installer will notify you that you must uninstall the SDK. Click "OK". The next dialog will offer to uninstall the SDK. Click "Yes" to uninstall the SDK. JCHI-6QKTET Setting the Tools/Preferences/MIDP/KVM heapsize to a negative value results in a positive value being entered in the SDK. Workaround: Use positive values. TYU-6HRSB6 When the SDK runs a MIDlet, some PC keyboards can only simulate holding down two numeric keypad buttons simultaneously. Workaround: You can simulate pressing a third button using the mouse. VVAI-699S3P Contact, Event and ToDo items, created via the JSR 75 PIM API, are not persistently saved when the SDK is shut down. Workaround: Create a MIDlet suite containing both your target MIDlet and a "helper MIDlet" that adds the PIM items you need. Each time you load your MIDlet suite into a new SDK instance, run the helper MIDlet first and then the target MIDlet. SVEL-6N4QXW Intermittently, MIDlets that use the Nokia Sound UI may produce no sound. Workaround: Use the Series 40 SDK 3rd Edition instead of this SDK to test the Nokia Sound UI with your MIDlet. RRED-6P9SGR When you run the SVG example MIDlet and choose the SvgAnimator test, the MIDlet displays correctly, but selecting "Play" causes an Application error. TYU-6HXQJ7 If you create a multipart MMS message in NMIT 4.1, but fail to associate a content type with one of the message parts, the SDK will discard the MMS message when you push it to the SDK and will not issue a warning. Workaround: Check the Content-Type check box in the NMIT Part Properties window for each of the message parts. MLUP-5V8QUF The SDK does not handle characters with diacritical marks in path names used on the command line or in the File/Open dialog. For example loading a file C:\ûûõõííÕÛûöööéáû\myMIDlet.JAD will result in a "File not found" error message. Workaround: Use only English characters in the resource locator. MLUP-6PHG66 If the SDK Web Browser is active and you select the Tools/Generate Event/ Incoming Call event from the SDK menu, the SDK permits you to continue using the Web Browser but the handset does not. MLUP-6PDK8T When a MIDlet displays a MIDP security dialog asking to allow the operation, pressing the End Call key and responding "Yes" to close the MIDlet displays a second security dialog displays for 5 seconds before the MIDlet closes. After this, running the MIDlet displays an "Application error" instead of displaying the security prompt. Workaround: Do not press the End Call key in a security prompt. If you encounter this error and the MIDlet does not run correctly, stop and restart the SDK. SVEL-6P2KUL If your network requires a proxy server, running a MIDlet with an HTTPS operation with the proxy server disabled will cause an SDK failure. Workaround: Restart the SDK and enable "Tools/Preferences/Networking/ Use an HTTP Proxy Server". RRED-6P9NN7 Turning off the No Signal event restores the emulated network support in the SDK, but does not restore the signal bars in the SDK idle screen. TYU-6PLSY9 After closing a directly loaded MIDlet, the SDK sometimes fails to remove the MIDlet JAR and JAD files from the C\DirectLoaded directory under the SDK instance directory. Workaround: Delete the files manually. AHUS-6QCRL6 Using Nokia Mobile Internet Toolkit (NMIT 4.1) with Java Runtime Environment 5 or later will not create WML/XHTML files. Workaround: Download the Nokia Mobile Internet Toolkit 4.1 Patch for JRE 5 using Nokia's Developer Home at http://www.forum.nokia.com/. SVEL-6NYPGT The MIDP security communication function group can be modified for a downloaded MIDlet using Menu>Applications>Games>App, but cannot be modified in the SDK. Workaround: modify the connectivity settings using Tools>Preferences>MIDP>Set Permissions and directly load the MIDlet (enable Tools/Preferences/MIPD/Direct loading). VVAI-6QXPJP The Interactive Graphics Player in this SDK can only open FlashLite (SWF) files using relative URLs. Workaround: Use absolute paths to open non-SWF files. Copyright © 2006 Nokia Corporation. All rights reserved. Nokia and Nokia Connecting People are registered trademarks of Nokia Corporation. Other product and company names mentioned herein may be trademarks or trade names of their respective owners.