===================================================================== RELEASE NOTE FOR S60 5th Edition SDK v1.0 05.03.

2009 ===================================================================== Refer Forum Nokia website for updated release notes. ---------------------------------------------------The S60 5th Edition SDK v1.0 enables application development using C++,Standard C/C++,JAVA and Web Runtime for devices based on the S60 Platform. The SDK is based on S60 5th Edition and Symbian OS 9.4. The SDK includes all key functionalities needed for application development (documentation, API reference, emulator etc.)excluding IDEs. What's new in S60 5th Edition SDK ---------------------------------- Touch UI support: The S60 5th Edition SDK supports touch UI emulation. - Tactile Feedback in Emulator in the form of sound. - Standard C++ and Boost libraries designed to ease and encourage porting of open-source C++ applications from desktop to the Nokia S60 mobile phone platform. - Web Runtime Widget support and Web Runtime Service APIs support (See API section) - New APIs (See API section) - S60 OpenC++ Documentation Updated S60 3RD EDITION FP2 Features ------------------------------------- Transition Effects Transition Effects decorate application changes, including start, switch and exit cases. GfxTransEffect API was missing in S60 3RD EDITION FP2, added in S60 5th Edition SDK. - Enhanced emulator startup speed and Start Up Mode Notification on Emulator Skin."P" indicates emulator is started in partial mode. "F" indicates emulator is started in full mode.Also, Emulator title bar displays a message 'S60 Emulator loading. Please wait" till the emulator starts completely. - Updated J2ME API: JSR 234: Advanced Multimedia Supplements 1.1 - JavaScript Console support for debugging of widgets - Web Runtime API Reference For more details see What's New section in SDK documentation. Features --------- This product requires free registration 14 days after installation. - Emulator for testing and debugging applications. - Building tools and environment for emulator (WINSCW UDEB). - Building tools and environment for terminal deployment (GCCE, RVCT) RVCT compiler is not bundled with the SDK. - Symbian and S60 platform documentation, as specified below: + Help + Installation Guide + API set documentation + Platform security documentation including description of the

modified development process + OpenC and OpenC++ Documentation - 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 - Emulator TCP/IP support using Winsock. - Emulator supports UI resolutions: QHD Portrait, QHD Landscape,QVGA Portrait and QVGA Landscape (Both with Keypad and Keypadless) Supported IDEs for C++ ----------------------- Carbide.C++ v1.2 ,v1.3 and v2.0 Express,Professional and Developer Supported IDEs for JAVA ------------------------ NetBeans IDE 6.0, 6.1 and 6.5 - Eclipse 3.3.1 with EclipseME 1.7.7 and MTJ C++ New APIs ------------- Accessory Monitoring API - Choice List API - Generic Button API - Hierarchical Lists API - Hostlet Connection API - Messaging Integration API - Sensor Channel API - Sensor definitions API - Standard C++ with STL and IO streams support - Stylus Pop-up Menu API - Tactile Feedback Client API - Title Pane Touch Observer API - Toolbar API - Touch UI Utilities API - Web Service Messaging API - WLAN SDK Info API - XML Engine DOM API - XML Fragment API Compliant J2ME APIs ------------------- JSR 139: Connected Limited Device Configuration 1.1 - JSR 118: Mobile Information Device Profile 2.1 - JSR 75: PDA Optional Packages for the J2ME Platform 1.0, FileConnection and PIM APIs optional package - JSR 82: Java APIs for Bluetooth 1.1 - JSR 120: Wireless Messaging API 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 JSR 179: Location API for J2ME 1.1 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 JSR 135: Mobile Media API 1.1 JSR 234: Advanced Multimedia Supplements 1.1 JSR 248: Mobile Service Architecture subset Nokia UI API 1.1 System property IAP Info API eSWT API

1.0, SATSA-PKI

1.1

Web Runtime Service APIs ------------------------ Logging - Calendar - Messaging (SMS, MMS) - Multimedia (media gallery) - Contacts - Location - Landmarks - Application Manager - System Info - Sensor New C++ Example Applications ----------------------------- CommonDialogsEx - HierarchicalColumnList - OpenCpp_Ex + helloworld + iostream + iterators + stl - TouchEx + ChoiceListEx + LongTapDetectorEx + NoughtsAndCrosses + StylusPopupMenuEx + TactileExample - SensorExample - XeDomExample New J2ME Example Applications ------------------------------ eSWT MIDLet Additional example applications can be found on www.forum.nokia.com - SystemProperty Midlet - demonstrates the usage of Nokia API to retrieve the system property information.User need to sign Midlet to run it on device. Web Runtime Widget Examples ---------------------------- LoggingWidget - MessagingWidget

MediaManagementWidget ContactWidget LocationWidget SensorWidget JavaScriptConsole SysInfoWidget AppManagerWidget CalendarWidget Additional Widget applications can be found on www.forum.nokia.com

System Requirements -------------------Basic Requirements: -------------------- Microsoft Windows XP SP2. - Minimum 1 GHz Pentium PC, 1024 MB of memory - At least 2 GB free disk space, other requirements according to the IDE used. - Installation/Uninstallation and using of the SDK requires local admin rights. - Other Requirements as required by IDE used Additional Softwares: --------------------- Active Perl 5.6.1 build 635 for SDK build tools. Newer or older versions of Perl maynot be fully compatible with Symbian toolchain. Perl must be installed before using the SDK to build applications. - Java Runtime version 1.6.0_xx - ARM RVCT compiler 2.2 build 593 or newer is supported.

Known Issues and Deficiencies in this SDK Release -------------------------------------------------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 browser session to crash. Workaround: NONE - Web Feeds feature is NOT supported in the S60 emulator browser. Workaround: NONE Build Tools and IDEs -------------------- For MIDlet debugging to work on Eclipse for Emulator. Please follow the Workaround: Go to Windows->Preference->Java->Debug tab Deselect all checkbox Debug timeout: 150000 (Better to put 200000) Launch timeout: 200000 - MIDlet On Device Debugging over a Bluetooth and USB connection does not work. Workaround: MIDLet ODD can be done over WLAN connection. - To enhance NetBeans MIDlet debugging, use 'Attach Debuger' option.

You need to provide the application port number to attach the debugger with running MIDlet. S60 APIs ---------- RestoreHeaderL, SetHintType methods in the Class CContactItemField of the header Cntfield.h doesn't have implementation in the SDK - CParserPropertyValueAlarm() method in CParserPropertyValueAlarm Class of header vcal.h does not have implementation in the SDK - DataTypes Method in the Class TApaAppServiceInfo of the header apaid.h does not have implementation in the SDK - Method TASN1DecEnumerated() in the header asn1dec.h does not have implementation in the SDK. - In file sensrvpropertylistener.h the SetPropertySuccessIndicationChanged() has inline implementation. Inline implementation will be removed and function will be pure virtual. It is only SC break when migrating to the version where the function is pure virtual. It is mentioned in the header that function will be changed to pure virtual. Clients can be prepared by overriding default implementation for the function. - CCameraAdvancedSettings in ecam.h does not have implementation in the SDK. - Implementation for some of the methods from following headers are missing. cntfilt.h,cntfield.h,cntviewbase.h,vcal.h,apaid.h, ct/ccttokentypeinfo.h,ct/ccttokentype.h,cfstokentypeclient.h, pkixcertchain.h, pkixvalidationresult.h,asn1dec.h, ct/tctfindtokentypesbyinterfaceandattribute.h, ct/tctfindtokentypesbyinterface.h. Installation/Uninstallation ---------------------------- It is recommended that JDK and IDE are installed before installing the SDK. - If SDK installation path contains other than alphanumeric characters,installation fails. Currently, the installer allows selecting a path which contains spaces, but the functionality of a SDK installed to such path may fail. Workaround: Do not give any non alphanumeric characters or white spaces in the installation path. - Installation to non-default folder creates extra folders to the C: drive. Workaround:It is recommended to install the SDK to the default installation path. - SDK uninstallation doesn't remove all the folders under S60/Devices. Workaround: It is recommended to delete these folders manually before installing another fresh instance of the SDK as some data from previous installation may persist. S60 Tools ---------- 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.

Minimum configuration: + PC1: S60 Emulator running Client application using SIP+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). - Executing ceddump.exe does not create a cedout.cfg file if the emulator is running. Workaround: Run the ceddump.exe from command prompt before starting the emulator or closing the emulator for creating the cedout.cfg Emulator Applications ---------------------- Saving locally stored Web pages does not work in the Web application (browser). - 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 business cards or calendar events via text message ("Smart Messaging") is not supported in S60 emulator. - Music Player may not work properly, but it does not affect the play functionality which can be done via Gallery. - It is not possible to add any word to the Dictionary emulator application. - RA10 media format is not supported by Media Player. - The Camera application is not supported by the S60 emulator. Emulator --------- Emulator prompts for selecting an access point every time midlet is opened for running, but this has no functional impact. - The emulator includes most of the S60 applications for convenience. The lack of the actual terminal hardware limits availability of some features like SIM features. - 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. - The emulated MMC card should be initialized with 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. - Local HTML files do not open through File-->Open utility. Workaround: Copy the required HTML files to epoc32\winscw\c\Data and the HTML files can be opened through File Manager. - 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). - 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 fail to have effect. - Emulator does not support USB connectivity. - Emulator does not support Bluetooth peripherals (headsets and printers). - Transition effects are not fully functional in the emulator. - HTTPS is not working with Apache. - It is not possible to install applications when install to mass memory option is selected in the emulator after running the multiple drive configuration scripts which are present at C:\S60\devices\ S60_5th_Edition_SDK_v1.0\epoc32\tools\mds. Workaround: Select phone memory in the query. Installation will progress. Emulator Partial mode start up issues: --------------------------------------Following is a list of issues in the partial startup mode of the emulator. However, while using the limited set of services option enhances emulator startup speed, it may be that you need some of the services missing from the startup list in your application development. If you experience such problems, it is recommended that you use the full set of services at emulator startup. - MMS Notification Event in utilities does not work in Partial Startup mode. - No Send option for images and business card in Partial mode. - Sending files between emulator and device through bluetooth does not work in Partial mode. - "New message" shortcut in the Idle screen does not work in Partial mode. Workaround: To use the above listed functionalities, Restart the emulator in Full mode. C++ Example Applications -------------------------- Webclient example panics on exit. This panic is caused by S60 emulator implementation. - BrCtlSampleApp example application does not render HTML properly in emulator. Also some of the options do not work. - SIP example: In the two PC setup Instant Messages are not sent from the machine where the SIP Server Emulator is running. Workaround: Use 3 PC setup, with the SIP server running on a third PC for two way messaging. - ContactsDB and some other S60 example application may display ALLOC error on exit. - Symbian Example BIOMessage fails to build but, this example demonstrates API usage. - Some Example applications do not have documentation AcceptPrintInput, debugging and EgConverter. - Some example applications (OpenGL, GUIEngine etc) which have custom UI controls, fail to respond to touch in emulator and device.These examples are meant to demonstrate respective API usage. - Console based example applications like OpenC, OpenC++ examples fail to respond to touch on emulator and device. These examples are meant to demonstrate respective API usage. - Lensflare example is not launching on device tube however it is working fine with emulator.

Removed/Deprecated Headers --------------------------- ClkDateTimeView.h - ClkMdlObserver.h Workaround: Removed/Deprecated headers do not affect application development. However, it is recommended to see the SDK Documentation for alternatives. Documentation -------------- Some Java Documentation links do not work. Workaround: Documents are available upon search in S60\Devices\ S60_5th_Edition_SDK_v1.0\docs\javadocs. - Code Assist in Netbeans IDE may not be available for some APIs (ex: java.utils APIs) due to missing API documents in doc\javadocs folder. Workaround: To enable the code assist, you may add proper javadoc for missing JSR APIs from other sources to doc\javadoc folder Microsoft Windows Vista operating system specific known issues -------------------------------------------------------------The S60 5th Edition SDK v1.0 for Symbian OS works on Microsoft Windows Vista Business, with the following known limitations - ARMV5 support is not available for Vista. - Compilation for GCCE from command line and Carbide.C++ needs following modifications WORKAROUND: Build for GCCE target fails on Vista. There is a patch available to enable compilation for GCCE target over command line at C:\<SDK_Installation_directory>\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 affect. Note that CSL Arm Tool chain 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-2009 Nokia Corporation. All rights reserved. Nokia and Nokia Connecting People are registered trademarks of Nokia Corporation.