======================================================================== RELEASE NOTE FOR S60 3RD EDITION SDK FOR SYMBIAN OS, 08.10.2007 FEATURE PACK 2, FOR C++ BETA RELEASE ======================================================================== The S60 SDK for Symbian OS enables application development for devices based on S60 platform using C++. The SDK is based on S60 3rd Edition, supporting Feature Pack 2 and Symbian OS 9.3. The SDK includes all key functionalities needed for application development (documentation, API reference, emulator) excluding IDE. This is a Beta release of the SDK. This is a binary compatibility baseline for new APIs (see list in "What's New" in SDK documentation). Binary compatibility for APIs introduced in S60 3rd Edition is maintained unless otherwise stated below. SDK Features Supported ======================= - This product requires free registration after 14 days of use. - Emulator for debugging applications. - Building tools and environment for emulator (WINSCW UDEB). - Building tools and environment for terminal deployment (GCCE, RVCT). - Symbian and S60 platform documentation, as specified below: + Help + Installation Guide + API set documentation + Platform security documentation including description of the modified development process - S60 Tools including: + SimPSY, including tool for generating simulated locations + Svg2Svgt for converting SVG images to SVG-T 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 - Support for CodeWarrior version 3.1 for Symbian OS. - Support for Carbide.c++. - Emulator TCP/IP support using Winsock. New Features ============= - Standard C library support The standard C library support of the SDK provides access to standard POSIX and middleware C libraries making it easier to port existing standard C applications to S60 3rd Edition - Widget support Widgets are lightweight Web applications developed using standards-based Web technologies such as HTML, CSS, JavaScript, and even AJAX. Mobile widgets give S60-based device users a full Web experience with instant access to the most essential Web 2.0 services and Internet content. - Enhanced emulator startup speed - Platform UID - New APIs - Middle Softkey For more details see What's New in SDK documentation. New Example Applications ========================= - AIWConsumerBasics - AudioStreamExample - DataMobility - DirectoryLocalizerEx - DynamicSettingList - ListBox - Localization - MyView (replaced MultiViews example) - RichTextEditor (replaced Editor example) - UnitEditorEx - 10 OpenC examples - Antiword Example - Dll Usage Example Application - Example application to simulate Active Object using Open C APIs - Libz usage example - Message Queue Library Example - Open C Hello World with Glib Events Example - Open C OpenGL ES Example - Producer Consumer Problem Solution Example - Redirect stdio to a file - String Utilities Library Example System Requirements ==================== Basic Requirements: - Microsoft Windows XP SP2. - IDE: Carbide.C++ v1.2 or v1.3 Express and Professional, CodeWarrior for Symbian OS v3.1 - ARM RVCT compiler 2.2 build 593 or newer is supported. (Version 3.0 is not supported by SDK toolchain) - Minimum 1 GHz Pentium PC, 1024 MB of memory - At least 2 GB free disk space, other requirements according to the IDE used. Additional Requirements: - Installation/uninstallation and using of the SDK requires local admin rights. - Active Perl 5.6.1 build 635 for SDK build tools. Newer or older versions of Perl may not be fully compatible with Symbian toolchain. Perl must be installed before using the SDK to build applications. - Java Runtime version 1.5.0_10 or later is required. Known Issues and Deficiencies in this SDK Release ================================================== Web Run-Time 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 browser session to crash. - After closing a widget browser session, ALLOC error note can be seen. This issue is specific to emulator implementation and has no functional impact. - After installing a widget via Application Installer in S60 emulator, ALLOC error note can be seen on exit. This issue is specific to emulator implementation and has no functional impact. - Web Feeds feature is not supported in the S60 emulator browser. Build Tools and IDEs -------------------- - This SDK is not fully compatible with older CodeWarrior family of IDE. WINSCW compilation back-end versions prior 3.2.5 will produce binaries that will cause emulator to crash on exit If applications source code is using OpenC APIs. To check the version of WINSCW compiler in your environment, issue "m2ccsym2.exe" in command prompt. S60 APIs --------- - Header tzconverter.h uses class RTz which is defined in tz.h but this header is not included in tzconverter.h. To utilize tzconverter.h, header tz.h must be also included into scope. - Header wngmodel.h uses class MPictureFactory which is defined in gdi.h but this header is not included in wngmodel.h. To utilize wngmodel.h, header gdi.h must be also included into scope. - Symbian class CCameraAdvancedSettings (part of ecam.h) is documented in Symbian Developlment Library but not implemented in S60. Installation/Uninstallation ---------------------------- - Installation to non-default folder creates extra folders to the C: drive. - SDK uninstall does not remove SDK entries from installationRegistry.xml. - Uninstalling SDK versions prior 3rd Edition FP2 while 3rd Edition FP2 present will cause error note at the end of installation. In that case the active remaining SDK device needs to be set manually via 'devices' utility in command prompt. S60 Tools ---------- - NMIT and NDS for MMS integration has issues that occassionally block incoming messages. Resending the message usually fixes the problem. - It is recommended to install the SDK to default location. - 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. - You need at least two PCs to run SIP Applications. Minimum configuration: PC1: S60 Emulator running Client application using SIP + SIP Server Emulator. PC2: S60 Emulator running Client application using SIP. SIP Server emulator can also reside on a third computer. When using SIP Server Emulator 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. Emulator Applications ---------------------- - Saving locally stored web pages does not work in the Web application. - Camera application is not supported by the S60 emulator. - RealPlayer in emulator may fail to play some samples or play only partial audio or video content. This issue is related to limitation on supported codecs in the emulator. - Sending and recieving email fails in Landscape, when Security Settings are ON i.e Email configured with SSL/TLS or Start TLS. - Sending business cards or calendar events via text message ("Smart Messaging") is not supported in S60 emulator. - After closing GPS application or an application utilizing Location service, PosServer ALLOC panic note can be seen. This issue is specific to emulator implementation and has no functional impact. Emulator --------- - When debugger is started a menu application sometimes overlaps the application being debugged. Use quick task switch button to bring the application to front. - 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 locale supported by the current language setting can be selected. Emulator language is modified through the S60 SDK Start menu. - 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, rights object (DRC) must be loaded before content (DCF). - SIC (Service Indication) and DRC (Digital Rights) content cannot be 'pushed' to the SDK from NMIT (Nokia Mobile Internet Toolkit). Workaround: Save the SIC and DRC content in NMIT by using the Save Binary option, and then File > Open them using the SDK. - Emulated events are not visible in emulator UI in all situations. Events need to be catched programmatically. - Pressing PC keyboard softkey shortcuts (Alt+1 and Alt+2) in Application Shell occasionally fail to have effect. - Emulator does not support USB connectivity. - Emulator does not support Bluetooth peripherials (headsets and printers). - With default Theme some Note controls lack icons. Changing Theme fixes the appearance. - With default Theme Progress Indicator bar controls are not getting animated or updated. Changing Theme fixes the appearance. - Localization of Chinese and Japanese variants is not fully complete and may lack some items. - Screensaver in idle mode is not enabled by default in S60 emulator. This casues opening Personalization folder under Settings, changing screensaver text or animation file to fail with error in S60 emulator. To enable screensaver, set the startup mode to "Start all services" in emulator Preferences. After that, screensaver and its configuration becomes active in this emulator session. - Transition effects are not fully functional in the emulator. Example Applications --------------------- - In emulator Webclient example a panic is shown at exit. This panic is caused by S60 emulator implementation. - BrCtlSampleApp example application does not render HTML properly in emulator. - SIP example: In the two PC setup Instant Messages are not sent from the machine where the SIP Server Emulator is running. - ContactsDB and some other S60 example application may display ALLOC error on exit. This issue is not related to example code and causes no functional impact. Copyright (c) 2001-2007 Nokia Corporation. All rights reserved. Nokia and Nokia Connecting People are registered trademarks of Nokia Corporation.