======================================================================== RELEASE NOTE FOR S60 3RD EDITION SDK FOR SYMBIAN OS, 13.02.2007 SUPPORTING FEATURE PACK 1, FOR MIDP ======================================================================== Product Description =================== The S60 3rd Edition SDK for Symbian OS, Supporting Feature Pack 1, for MIDP enables application development for devices based on the S60 Platform using Java. The SDK is based on the S60 3rd Edition, supporting Feature Pack 1 and Symbian OS 9.2. The SDK includes all key functionality needed for application development (documentation, JavaDoc API reference, add-on tools, emulator, on-device debugging) excluding IDE and compiler. This SDK supports: - JSR 75: PDA Optional Packages for the J2ME™ Platform 1.0, FileConnection and PIM APIs optional package - JSR 82: Java™ APIs for Bluetooth 1.0 - JSR 118: Mobile Information Device Profile 2.0 - JSR 120: Wireless Messaging API 1.1 - JSR 139: Connected Limited Device Configuration 1.1 - JSR 172: J2METM Web Services Specification 1.0 - JSR 177: Security and Trust Services API for J2ME™ 1.0, SATSA-CRYPTO - JSR 177: Security and Trust Services API for J2ME™ 1.0, SATSA-PKI - JSR 179: Location API for J2ME™ 1.1 - JSR 180: SIP API for J2ME™ 1.0 - JSR 184: Mobile 3D Graphics API for J2ME™ 1.1 - JSR 205: Wireless Messaging API 2.0 - JSR 226: Scalable 2D Vector Graphics API for J2ME™ 1.0 - Nokia UI API 1.1 This SDK contains an implementation of (known issues are covered below): - JSR 135: Mobile Media API 1.1 - JSR 234: Advanced Multimedia Supplements 1.0 S60 Platform is a complete smartphone reference design. It represents a rich environment for developers to create exciting content and innovative applications. The platform builds on top of Symbian OS, complementing it with a configurable graphical user interface library and a comprehensive suite of reference applications. A set of robust components and many varied APIs are provided for developers. Features ======== - S60 Emulator - Building tools and environment for emulator - Documentation - User's guide - Installation guide - Java API Javadoc reference documentation - Example applications - Support for TCP/IP connections in the emulator - Emulator supports UI resolutions: QVGA Portrait and QVGA Landscape - Emulator supports multiple emulator instances - Emulator supports localization plugins for English, Chinese Simplified, Japanese and Thai. - On-device debugging support - Support for following IDEs and development products is tested with: - NetBeans IDE with mobility pack 5.0 - IBM WebSphere Studio Device Developer 5.7.1 - Eclipse 3.1.2 (Carbide.j 1.5 is needed for Eclipse and SDK integration and it is recommended to be installed after Eclipse and before MIDP SDK) - Carbide.j 1.5 - The following IDEs and tools are also supported - Nokia Mobile Internet Toolkit 4.1 - Nokia Developer's Suite for MMS 1.1 New Features ============ - See "What's new in this release" in SDK User's Guide. New APIs ======== JSR 184: Mobile 3D Graphics API for J2ME™ 1.1 JSR 226: Scalable 2D Vector Graphics API for J2ME™ 1.0 JSR 234: Advanced Multimedia Supplements 1.0 For more info see SDK Help Java API Documentation. System Requirements =================== Basic Requirements: - Microsoft Windows XP SP2 - Minimum 1 GHz Pentium PC, 512 MB of available memory - 1 GB free disk space - J2SE 5.0 SDK - Other requirements as required by the IDE used Additional Requirements: - Installation/uninstallation of the SDK requires local admin rights. - The supported Bluetooth protocols are BCSP and H4. Bluetooth has been tested with the following devices: - Brainboxes BL-500 - Casira Bluetooth Development Kit - IrDA has been tested with Extended Systems, Inc. Jeteye pods ESI 9680. - A MS Windows compatible sound card is required for the audio support. - Security and Trust Services API was tested with GemPC USB-SL Smart Card Reader from GemPlus. This product requires free registration after test period. Compatibility Issues ==================== Differences between emulator and S60 devices -------------------------------------------- - Camera features are not supported. - With some Bluetooth adapters there are problems in using certain physical COM-ports for Bluetooth adapter with the emulator. Workaround: Try different COM-port for the adapter. Known Issues ============ Installation/Uninstallation --------------------------- - It is recommended that Java and IDE are installed before installing the SDK. - The SDK installation path should contain only alphanumeric characters. Currently, the installer allows selecting a path which contains spaces, but the functionality of a SDK installed to such path may fail. - Installation/uninstallation of the SDK requires local admin rights. Emulator -------- - The emulator includes most of the S60 application for convenience. The lack of the actual terminal hardware limits availability of some features like SIM features. - The emulated MMC card must be initialized with Memory Application before first use. - In MMC Emulation, removable drive letter is not always updated in configuration panel. - When opening DRM content in the SDK, rights object (DRC) must be loaded first using File-Open, before the content (DCF), unlike in S60 devices. - DRC (Digital Rights) content cannot be 'pushed' to the SDK from NMIT (Nokia Mobile Internet Toolkit). Instead save DRC content in NMIT by using the Save Binary option, and then File-Open them using the SDK. Emulator Applications --------------------- - Camera is not supported by S60 Emulator. - RealPlayer supports playing 3gp and mp4 files. Also Real Video 10, 9, 8 can be played, video part is displayed but the audio part may suffer distortions. Other formats are not supported in S60 emulator. - RealPlayer streaming is not working properly in the emulator. - Smart message sending of the following items do not work in the emulator. - Phonebook (contacts) - Calendar (calendar items) Emulator -> Tools -------------------------------- - Diagnostics -> Drives - RAM Consumption is not happening when open any Memory Eater Applications on Device - Diagnostics -> MIDlet System.out Redirection: System output has 100 character buffer, and can not be seen before the buffer is full. - Events -> Enhancement Events -> Handsfree mode on/off event does not work. - The emulator fails to start if very large values are configured in the Preferences 'Memory Capacity' setting (192M or more depending on environment). oo high value can be reset by editing the epoc.ini file in bin\epoc32\data\epoc.ini and changing the MegabytesOfFreeMemory setting to a lower value. Eg. the default 32. - Preferences -> MIDP Security - "Ask once" is not working correctly for User Defined:Messaging. - Utilities -> Removable Drive is not always detected IDEs ---- - In Eclipse Run Configuration dialog the Nokia SDK Plug-in does not show the name of the SDK for available emulator devices. The S60 3rd Ed. FP1 SDK for MIDP provides three available targets: S60 Emulator, S60 Device. - Debugging of MIDlets in IBM WSDD does not work. - IBM WSDD may fail to start emulator with error "Jar file could not be initialized" and reporting a duplicate entry. Fix: Remove the MIDlet path from WSDD ClassPath under "Running Configuration". This setting should contain only the MIDlet's JAR file. - IBM WSDD may fail to compile a MIDlet. Fix: Add hmidps60v31.jar to Libraries -tab under Project settings -> Java Build Path - IBM WSDD may not find project resource files when running. Fix: After building the project according to SDK documentation, open the .jxeLinkOptions -file under "generic" -folder. The resource files can be added in the In/exclusion -tab, by selecting "Include resources" from the first drop-down list, and clicking on "New". Each resource file must be added separately, and the full path from project root must be entered, e.g. "com/nokia/midp/examples/hawk/res/hawk.png" for the Hawk example MIDlet resource file "hawk.png". After adding all necessary resource files, save and close the .jxeLinkOptions -file. Reopen the Device Developer Builds -dialog and continue from step 5 on "Compile source code" by clicking "Run". You can verify the inclusion of resources by clicking on "Details>>" when the build has completed successfully. The [preverify] Summary lines contain information about included classes and resources. For more information about resource inclusion, see IBM WSDD Help topic "SmartLinker Inclusion and Exclusion Options" - Switching to devices of a different S60 emulator instance in Carbide.j Runtime settings does not work. Workaround: remove old SDKs and restart IDE. JSR 135: Mobile Media API ------------------------- - Problems may occur when developing Java applications which use multimedia, e.g. problems when creating sound loops or controlling tune timing in mobile Java games or when playing video streaming over rtsp protocol by mobile Java. Workarounds: - use S60 device hardware (S60 3rd Edition Feature Pack 1) for testing - use S60 3rd Edition SDK for Symbian OS, for MIDP JSR 234: Advanced Multimedia Supplements ---------------------------------------- - Problems may occur when developing Java applications which use 3D audio, e.g. 3D sound direction, pitch or reverb may not be heard correctly. Workarounds: - use S60 device hardware (S60 3rd Edition Feature Pack 1) for testing Documentation ------------- - Some IDEs cannot find the Javadoc API documentation provided with the SDK. Workaround: Java API Javadocs are packaged per JSR under the directory S60_3rd_MIDP_FP1\doc\ and can be accessed from index.html - Java API Javadocs contain broken links to files and anchors that are not part of the documentation package. Example applications ------------------- - PersonalController MIDlet displays UID field for Event items in a wrong format. - PersonalController MIDlet can not import data. - PersonalController MIDlet Repeat Rules not working under Events. - PersonalController MIDlet Exception occurs on deleting a category under contacts. - FileConnection MIDlet has no Exit Option in the "Options" menu. - SIP RegisterTest MIDlet screen shows Connection Exception on the screen. - SVG MIDlet - Exception on selecting menu option Stop or Pause without playing the animation. S60 Tools --------- - SIP Server Emulator can only be run in a two or more PCs configuration. PC1: S60 Emulator running Client application using SIP PC2: S60 Emulator running Client application using SIP SIP Server emulator running on PC1 or dedicated PC. SIP Invitation can only be sent from PC2. SIP Server Emulator fails to register invitations coming from S60 Emulator running on same PC as the Server Emulator. - SIP Configuration: both SIP Registrar and SIP Proxy servers need to be configured. Note that Proxy configuration is a mandatory step. Otherwise SIP Server emulator connection can't be made. Copyright © 2001-2007 Nokia Corporation. All rights reserved. Nokia and Nokia Connecting People are registered trademarks of Nokia Corporation.