======================================================================== RELEASE NOTES FOR S60 3RD EDITION SDK FOR SYMBIAN OS, 24.07.2008 FEATURE PACK 2 v1.1 ======================================================================== The S60 3rd Edition SDK for Symbian OS, Feature Pack 2 v1.1 enables application development using C++, standard C, Java(tm) technology, and Web Runtime (WRT) for devices based on the S60 platform. The SDK is based on S60 3rd Edition, Feature Pack 2 and Symbian OS v9.3. The SDK includes all the key resources needed for application development, including documentation, API reference, and an emulator, among other tools, but excluding an IDE. New in v1.1 =========== - Microsoft Windows Vista Business support. - Java application on-device MIDlet debugging over WLAN. - Debugging of widgets using JavaScript(tm) Console. - Web Runtime API Reference. - Example widget - Java Console support. - S60 Open C documentation. - Start-up mode notification on emulator skin. Features ======== - This product requires free registration 14 days after installation. - Emulator for testing and debugging applications. - Build tools and environment for emulator (WINSCW UDEB). - Build tools and environment for device deployment (GCCE, RVCT). (An RVCT compiler is not included in the SDK.) - Symbian OS and S60 platform documentation, including: + Help. + Installation guide. + API documentation. - S60 tools: + SimPSY - for generating simulated locations. + Svg2Svgt - for converting SVG images to SVGT format. + Task manager. + HTTP monitoring. + System event generator. + Emulator configuration tool. + Command-line interface - for mobile content developers. + Content Push to device through command-line interface. + Remote Logging API. - Emulator TCP/IP support using Winsock. - Emulator supports localization plug-ins for English, Chinese Simplified, and Japanese. - Emulator supports UI resolutions: QVGA portrait and QVGA landscape. - ODD on WLAN with supported Java IDEs. - Web Runtime debug support. - IAPInfo and eSWT API reference documentation available. - Web Developer Library 1.0 supported. - Runs on Microsoft Windows Vista Business with limitations. Please refer to Known Issues section for details. Supported IDEs for C++ ====================== - Carbide.c++ v1.2 or v1.3 Express, Professional, and Developer -Carbide.vs 3.0.1 CodeWarrior versions are no longer supported. Supported IDEs for Java development =================================== - NetBeans Mobility 6.0 - Eclipse 3.3.1 with EclipseME 1.7.7 New C++ applications examples ============================= - None New Java application examples ============================= - IAPInfoMIDlet Web Runtime widget examples =========================== - Java Console Widget System requirements =================== Basic requirements: - Microsoft Windows XP Service Pack 2 or Microsoft Windows Vista Business. - Minimum 1-GHz Pentium PC; 1024 MB of memory. - At least 2 GB of free disk space. - Installation/uninstallation and use of the SDK requires local admin rights. - Other requirements as necessary by IDE used. Additional software: - Active Perl 5.6.1 build 635 for SDK build tools. Earlier or later versions of Perl may not be fully compatible with Symbian toolchain. Perl must be installed before using the SDK to build applications. - Java(TM) Runtime Environment (JRE) 5.0. - Java(TM) Development Kit (JDK) 1.5.0_10 or later is required. - ARM RVCT compiler 2.2 build 593 or later is supported. (Version 3.0 is not supported by SDK toolchain.) Known issues and deficiencies in this SDK version for Windows XP and Windows Vista ==================================================================== Web Runtime and widget support ------------------------------ Widgets support in emulator is affected by the emulator-specific limitation of the S60 browser: - openURL commands from the widget code do not succeed and may cause a browser session to crash. Workaround: NONE. - After installing a widget via Application Installer in the S60 emulator, an ALLOC error note can be seen on exit. This issue is specific to emulator implementation and has no functional impact. Workaround: NONE. - Web feeds feature is NOT supported in the S60 emulator browser. Workaround: NONE. Build tools and IDEs -------------------- - To enable MIDlet debugging on Eclipse, please follow this workaround: Go to Windows->Preference->Java->Debug tab. Deselect all checkboxes. Debug timeout: 200000. Launch timeout: 200000. - Redirection of sys.out and sys.err doesn't work for Java applications. Workaround: NONE. - Carbide.vs 3.0.1 integration: While installing Carbide.vs 3.0.1, the tools does not detect this particular SDK and installation halts. Workaround: To skip the SDK detection during installation of Carbide.vs 3.0.1, add a new key named "Carbide.vs.30" with the string value "ForcePrereq" = "1" to the registry entry at HKEY_LOCAL_MACHINE\SOFTWARE\Nokia\. - In the Run/Debug window of the Carbide.C++ 1.3 IDE, the entry for the Emulator field is empty by default. Because of this, the emulator closes on exit from the example application that is being run through the IDE. Workaround: Set \epoc32\release\winscw\udeb\epoc.exe to this field. - MIDlet on-device debugging over a Bluetooth connection is not working. Workaround: NONE. - Code assist in the Netbeans IDE may not be available for some APIs (such as the java.utils APIs) due to API documents missing from the doc\javadocs folder. Workaround: To enable code assist add the missing javadoc files from another source to the doc\javadoc folder. S60 APIs -------- - Header tzconverter.h uses class RTz, which is defined in tz.h; however, this header is not included in tzconverter.h. Workaround: To utilize tzconverter.h, header tz.h must be included in scope. - Header wngdoor.h uses TApaAppIdentifier in the method virtual IMPORT_C TApaAppIdentifier AppId() const, class TapaAppIdentifier, which is defined in apaid.h; however, this header is not included in wngdoor.h. Workaround: To utilize wngdoor.h header, apaid.h must be included in scope. - Header wngmodel.h uses class MpictureFactory, which is defined in gdi.h; however, this header is not included in wngmodel.h. Workaround: To utilize wngmodel.h, header gdi.h must be included in scope. - Symbian class CCameraAdvancedSettings (part of ecam.h) is documented in Symbian Development Library but not implemented in S60. Workaround: This API must not be used. - RestoreHeaderL, SetHintType methods in the Class CContactItemField of the header Cntfield.h is not implemented in the SDK. Workaround: This method must not be used. - CParserPropertyValueAlarm() method in CParserPropertyValueAlarm Class of header vcal.h is not implemented in the SDK Workaround: This method must not be used. - The DataTypes method in the Class TApaAppServiceInfo of the header apaid.h is not implemented in the SDK. Workaround: This method must not be used. - CViewContact(long) method in the class CViewContact of the header cntviewbase.h is not implemented in the SDK. Workaround: This method must not be used. - The transition effects APIs are not available, although they are documented in the SDK Help’s What is New section. Workaround: NONE Installation/uninstallation ---------------------------- - It is recommended that the JDK and IDE be installed before installing the SDK. - If SDK installation path contains other than alphanumeric characters, installation fails. Currently, the installer allows selecting a path that contains spaces, but the functionality of an SDK installed to such path may fail. Workaround: Do not include any nonalphanumeric characters or spaces in the installation path. - Installation to nondefault folder creates extra folders to the C: drive. Workaround: It is recommended that you install the SDK to the default installation path. - Uninstalling SDK versions prior to 3rd Edition, Feature Pack 2 while 3rd Edition, Feature Pack 2 is present will cause error note at the end of uninstallation. Workaround: In that case, the active remaining SDK device needs to be set manually via the Devices utility at the command prompt. S60 tools --------- - A single Ecmt Agent file (EcmtAgent_MIDP.sis) is provided with the SDK for device connectivity. - Multiple JRE installation confuses the svg2svgt installer. Workaround: Add JRE (1.4.2 or newer) folder to PATH before running the installer; after installation, the JRE installation folder can be removed from PATH. - It is not possible to run SIP applications on a single PC. Workaround: You need at least two PCs to run SIP Applications. The minimum configuration is: + PC1: S60 Emulator running client application using SIP and SIP server. + PC2: S60 Emulator running client application using SIP. + SIP server can also reside on a third computer. When using SIP server on the same PC with S60 emulator, the SIP Profile configured on this S60 emulator must include SIP Proxy set to the same server address and SIP Realm as configured for SIP Registrar (e.g., the IP address of the machine where both run). Connectivity ------------ - Executing ceddump.exe does not create a cedout.cfg file if the emulator is running. Workaround: Run the Cedump.exe from command prompt before starting the emulator or closing the emulator for creating the cedout.cfg. Emulator applications --------------------- - Saving locally stored Web pages is not supported in the Web browser. - The Camera application is not supported by the S60 emulator. - RealPlayer in emulator may fail to play some examples or play only partial audio or video content. This issue is related to limitation on supported codecs in the emulator. - Sending and receiving email fails in landscape mode, when security settings are ON, i.e., email configured with SSL/TLS or Start TLS. - Sending business cards or calendar events via text message (Nokia Smart Messaging) is not supported in S60 emulator. - After closing a GPS application or an application utilizing location- based services, PosServer ALLOC panic note can be seen. This issue is specific to emulator implementation. This has no functional impact. - Sending an audio message throws an ALLOC error. This has no functional impact. - On opening Gallery, the error "Feature not Supported" is occasionally displayed. Workaround: Restart the emulator. - Slideshow feature may not work in landscape mode. It does not have any functional impact. - Upon selecting 'copy' from options menu of Contacts View, the application closes with KERN-EXEC 3 when any contact is opened. This has no functional impact. Note: These failures have no major functional impact on application development. Workaround: NONE. Emulator --------- - Emulator may terminate intermittently. Workaround: Restart emulator. - The emulator prompts for an access point to be selected every time a MIDlet is opened. This has no functional impact. - Locale of the emulator can be changed by renaming a locale-dependent file elocl.xxx in \release\winscw\udeb. For instance, to set the emulator to Swedish locale, rename elocl.006 to elocl.loc. Make a backup of the original elocl.loc. Only the locale supported by the current language setting can be selected. Emulator language is modified through the S60 SDK Start menu. - The emulator includes most of the S60 applications. The lack of the actual device hardware limits availability of some features, such as SIM features. - With some Bluetooth adapters, there are problems using certain physical COM ports for Bluetooth connectivity with the emulator. Workaround: Try different COM ports for the adapter. - The emulated MMC card should be initialized with the Memory application before first use. - In MMC emulation, removable drive letter is not always updated in configuration panel. - WAP Push files do not open in the emulator. - Epoc.exe process hangs if the emulator is turned off in standby mode. Workaround: Kill process using Windows Task Manager. - In the emulator, the value of the User::NTickCount() function advances every 5 ms (200 Hz) instead of every 1 ms (1000 Hz) as mentioned in the documentation. - When opening DRM content using File > Open, the rights object (DRC) must be loaded before content (DCF). - Emulated events are not visible in emulator UI in all situations. Workaround: Events need to be caught programmatically. - Pressing PC keyboard softkey shortcuts (Alt+1 and Alt+2) in application shell occasionally fails to have effect. - Emulator does not support USB connectivity. - Emulator does not support Bluetooth peripherals (headsets and printers). - In the default theme, some Note controls lack icons. Workaround: Changing the theme fixes the appearance. - With the default theme, the Progress Indicator bar controls are not animated or updated. Workaround: Changing the theme fixes the appearance. - Localization of Chinese and Japanese variants is not complete. Some menu items may be displayed in English, and some of the menu items may not be available compared to English variant. - Screen saver in idle mode is not enabled by default in S60 emulator. When using the Personalization folder under Settings, changing the screen saver text or animation file will fail with an error in the S60 emulator. Workaround: To enable screen saver, set the startup mode to "Start all services" in emulator Preferences. After that, screen saver and its configuration become active in this emulator session. - Transition effects are not fully functional in the emulator. - HTTPS is not working with Apache. - The Contacts application cannot be launched in the Chinese variant. - "OK" button is in English for both Chinese and Japanese variants. - Installing ECMT Agent on the device causes form POST requests to fail with the error "Unable to perform operation." Workaround: Uninstall the ECMT Agent from the device. C++ example applications ------------------------ - Web-client example panics on exit. This panic is caused by S60 emulator implementation. Workaround: NONE. - BrCtlSampleApp example application does not render HTML properly in emulator. Workaround: NONE. - SIP example: In the two-PC setup, instant messages are not sent from the machine where the SIP server emulator is running. Workaround: Use three-PC setup, with the SIP server running on a third PC for two-way messaging. - Symbian example BIOMessage fails to build, but this example demonstrates API usage. Workaround: NONE. - Some Symbian example applications do not have documentation: AcceptPrintInput, debugging, and EgConverter. Workaround: NONE. Removed and deprecated headers ------------------------------ - autosend.h - biocmtm.h - biocmds.h - biosmtm.h - icl/jp2kuids.hrh - icl/jp2kimagedata.h - imcmmain.h - imcvrecv.h - imcvsend.h - imcvutil.h - mmssettingsproxybase.h - wapp.h - wappdf.h - watcher.h Workaround: Removed and deprecated headers do not affect application development. However, it is recommended that the SDK documentation is consulted to determine suitable alternatives. Documentation ------------- - Some Java documentation links do not work. Workaround: Documents are available upon search in S60\Devices\S60_3rd_SDK_Final\docs\javadocs. - Some API documents are missing from the doc\javadocs folder. This may Also affect the code assist option in the NetBeans IDE. Workaround: Add the missing javadoc from another source to the doc\javadoc folder. Java APIs --------- - In the emulator, COM port is not supported in JSR-118 (MIDP 2.0). Workaround: NONE. - In the emulator, RTSP is not supported in JSR-135 (MMAPI). Workaround: NONE. Microsoft Windows Vista operating-system-specific known issues -------------------------------------------------------------- The S60 3rd Edition SDK for Symbian OS, Feature Pack 2 v1.1 works on Microsoft Windows Vista Business, with the following known limitations: - ARMV5 support is not available for Vista. - Build for GCCE target fails on Vista. Compilation for GCCE from command line and Carbide.C++ needs the following modifications: There is a patch available to enable compilation for GCCE target over command line at C:\\Plugins\vistapatch. Please refer to the help.txt file available with the package for instructions. However, to build via Carbide.c++, an extra step is needed in addition to replacing the cl_bpabi.pm file provided in the package. Add the following to the system PATH variable (through Control Panel->System->Advanced system settings) in the following order: C:\Program Files\CSL Arm Toolchain\bin;C:\Program Files\CSL Arm Toolchain\arm-none-symbianelf\bin;C:\Program Files\CSL Arm Toolchain\libexec\gcc\arm-none-symbianelf\3.4.3;C:\Program Files\Common Files\Symbian\tools. Restart the system for changes to take effect. Note that CSL Arm Toolchain needs to be installed to C:\Program Files\CSL Arm Toolchain for the patch to work. - Audio might cause panics at the end of play. This has no functional impact. Copyright (c) 2001-2008 Nokia Corporation. All rights reserved. Nokia and Forum Nokia are trademarks or registered trademarks of Nokia Corporation. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. Bluetooth is a registered trademark of Bluetooth SIG, Inc. Other product and company names mentioned herein may be trademarks or trade names of their respective owners.