======================================================================== RELEASE NOTES 20 December 2006 Series 40 SDK 3rd Edition Feature Pack 2 Based on Nokia 5300 XpressMusic device ======================================================================== 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/ site. Product Description: ==================== The Series 40 SDK 3rd Edition Feature Pack 2 is based on the Nokia 5300 XpressMusic, which is a Series 40 SDK 3rd Edition Feature Pack 2 compatible phone. The SDK provides a development and/or testing environment for Java TM Platform, Micro Edition (Java 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): - File Connection Optional Package API 1.0 (JSR 75) - Personal Information Mgmt Optional Package API 1.0 (JSR 75) - Java APIs for Bluetooth 1.0a (JSR 82) - Mobile Information Device Profile 2.0 (JSR 118) - Wireless Messaging SMS API 1.1 (JSR 120) - Mobile Media API 1.1 (JSR 135) - Connected Limited Device Configuration 1.1 (JSR 139) - Web Services JAXP API 1.0 (JSR 172) - APDU part of Security And Trust Services API 1.0 (JSR 177) - Mobile 3D Graphics API 1.0 (JSR 184) - Java Technology for Wireless Industry 1.0 (JSR 185) - Wireless Messaging API 2.0 for SMS and MMS (JSR 205) - Scalable 2D Vector Graphics API 1.1 (JSR 226) The SDK features support for - A Macromedia Flash Lite 2.0 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 5300 handset, including the general look, key layout, key definitions, error messages, display and rendering, soft keys, and menu selection. The Nokia 5300 device has keys on both sides that are made available to the user by emphasizing them in the GUI. The SDK is shipped with Dutch, English, French, German, Italian, Portuguese, Spanish and Turkish 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_2\bin> emulator -Xnew >>tracelog.txt Tested IDEs: =============== - Eclipse 3.1.2 (with Nokia Carbide.j) - Nokia Carbide.j 1.5 - Sun NetBeans 5.0 - Sun NetBeans with Mobility Pack 5.0 - Nokia Mobile Internet Toolkit (NMIT) 4.1 - Nokia Developer’s Suite for MMS 1.1 - Adobe GoLive CS2 - MacroMedia Dreamweaver 8 System Requirements: ==================== Supported Platforms: - Microsoft Windows XP Professional SP2 - Microsoft Windows XP Professional SP2 Chinese - Microsoft Windows XP Home Edition SP2 Additional requirement: - Java Runtime Environment 5 or later (JRE 1.5 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 2.8 GHz or faster CPU 512 MB RAM , 24-bit color, 1024x768 resolution 140MB of hard disk space Sound card Network interface card JSR177 developers need a smart card reader. Gemplus reader was used for testing. Disclaimer: =========== - While the SDK contains the actual handset software functionality is not identical due to simulations and differences in the hardware. 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 and Limitations: =============================== The SDK supports T=0 smart card communication in JSR 177 SATSA-APDU. The SDK does not support AAC and MP3 formats. As a consequnece Mobile Media API (JSR 135) method GetKeyValue cannot be applied on these file types. RTSP streaming in Mobile Media API (JSR 135) is not functional in the SDK as a consequence one TCK case was excluded from JSR 135. This issue will be corrected in the next SDK. You may use rtsp:// schema in URLs but the connection will not be completed. The SDK supports Flashlite 2.0. To load files in the SDK all related files should be copied into the SDK memory card (SDK file system) using standard Windows file explorer. If using the browser URL to upload these files it could cause deviations from FlashLite standard behavior. Using languages packs like AR and HE, use a consistent language to enter text in FlashLite input boxes, mixing the foreign language with English could result in a crash in the SDK. The handset supports DRM2.0 but the SDK is limited to DRM1.0 excluding support for MIDlets. Audio file handling is not working properly. In some use cases there are unnecessary locks on the files which prevent desired operations such as deleting or renaming files. By default music files are located in the Memory Card (drive E in Storage area of an instance) so not every Memory Card operation works, either. The workaround is to operate on the PC file system while the SDK is not running. Defect IDs: SEKA-6UYE28, SEKA-6UYE89, SEKA-6U37W5,SEKA-6VLERY, SEKA-6VLEUV. When the Music player is started and there are music files (AAC or MP3) the Music Player displays "Updating Library 0%" with no progress at all the user can ignore this and press Quit. Simulation 'No signal' does not prevent MMS to be sent from the handset menus nor from MIDlets. Defect ID: KN-6VJELM. In the MMS Java example the documentation contains screenshots with camera being operational. The example works as documented in the handset butbecause of the limited camera support the example behaviour in the SDK is different and the screenshot contents is not visible. Defect ID: KN-6UXDJL. 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.