s60 2nd 3rd ed differences in features v1 5 en

8/6/2019 S60 2nd 3rd Ed Differences in Features v1 5 En

1/50

S60 2nd/3rd Edi t ion:Di f ferenc es in Feat uresVersion 1.5October 16th, 2006

S60

p

l

a

t

f

o

rm


2/50

Legal Notices

Copyright 2006 Nokia Corporation. All rights reserved. Nokia and Nokia Connecting Peopleare registered trademarks of Nokia Corporation. Java and all Java-based marks are trademarksor registered trademarks of Sun Microsystems, Inc. Other product and company namesmentioned herein may be trademarks or trade names of their respective owners.

Disclaimer

The information in this document is provided as is, with no warranties whatsoever, includingany warranty of merchantability, fitness for any particular purpose, or any warranty otherwisearising out of any proposal, specification, or sample. Furthermore, information provided in thisdocument is preliminary, and may be changed substantially prior to final release. This documentis provided for informational purposes only.

Nokia Corporation disclaims all liability, including liability for infringement of any proprietaryrights, relating to implementation of information presented in this document. Nokia Corporationdoes not warrant or represent that such use will not infringe such rights.

Nokia Corporation retains the right to make changes to this specification at any time, without

notice.

License

A license is hereby granted to download and print a copy of this specification for personal useonly. No other license to any other intellectual property rights is granted herein.

S60 2nd/3rd Edition: Differences in Features | 2

Version 1.5 | October 16th, 2006


3/50

Contents1 Introduction.............................................................................................................................8

1.1 Purpose and scope........................................................................................................81.2 Target audience ............................................................................................................8

2 Overview of S60 3rd Edition ..................................................................................................92.1 S60 3rd Edition, Feature Pack 1....................................................................................9

3 S60 platform evolution..........................................................................................................114 Symbian C++ or Generic......................................................................................................13

4.1 Base.............................................................................................................................134.1.1 Small default stack size in S60 3rd Edition..........................................................134.1.2 Fonts API (3rd Edition FP1).................................................................................144.1.3 Real-time kernel (3rd Edition, Symbian OS v9.1)................................................144.1.4 Central Repository (3rd Edition, Symbian OS v9.1).............................................144.1.5 Install system (3rd Edition, Symbian OS v9.1).....................................................144.1.6 New tool chain (3rd Edition, Symbian OS v9.1)...................................................144.1.7 Wide usage of ECOM plug-ins (3rd Edition, Symbian OS v9.1)..........................144.1.8 Standard C++ additions.......................................................................................144.1.9 On-target debugging (3rd Edition)........................................................................15

4.1.10 Light API (3rd Edition)........................................................................................154.1.11 Vibra API (3rd Edition).......................................................................................154.1.12 Vibra Settings API (3rd Edition).........................................................................154.1.13 HWRM Power State API (3rd Edition)................................................................154.1.14 Remote Control Framework (3rd Edition, Symbian OS v9.1)............................154.1.15 Profiles Engine Active Profile Settings API (3rd Edition)....................................154.1.16 Find Item API (3rd Edition).................................................................................154.1.17 Secure Digital (SD) card support (3rd Edition)...................................................154.1.18 Startup List Management API (3rd Edition)........................................................154.1.19 PtiEngine API (3rd Edition)................................................................................164.1.20 Info Popup Note API (3rd Edition)......................................................................164.1.21 Server Application API (3rd Edition)...................................................................16

4.1.22 Common Audio Enhancements API (3rd Edition)..............................................164.1.23 Feature Discovery API (2nd Edition FP3)..........................................................164.1.24 Contacts Model API enhancement (2nd Edition FP3, Symbian OS v8.1)..........164.1.25 Publish & Subscribe API (2nd Edition FP2, Symbian OS v8.0).........................164.1.26 Message Queues (2nd Edition FP2, Symbian OS v8.0)....................................164.1.27 XML Framework (2nd Edition FP2, Symbian OS v8.0)......................................164.1.28 Huffman API (2nd Edition FP2, Symbian OS v8.0)............................................164.1.29 System Agent (3rd Edition, Symbian OS v9.1)..................................................174.1.30 Shared Data API (3rd Edition, Symbian OS v9.1)..............................................174.1.31 CSettingInfo API (3rd Edition)............................................................................174.1.32 Vibra Control API (3rd Edition)...........................................................................174.1.33 AIF (Application Information File) support (3rd Edition, Symbian OS v9.1).......174.1.34 PLPVariant API (3rd Edition, Symbian OS v9.1)................................................174.1.35 SysUtil API (3rd Edition).....................................................................................17

4.2 Security........................................................................................................................174.2.1 OMA DRM v2.0 (3rd Edition FP1)........................................................................174.2.2 Platform security (3rd Edition, Symbian OS v9.1)................................................174.2.3 Content Access Framework (3rd Edition, Symbian OS v9.1)..............................184.2.4 OMA DRM CAF Agent API (3rd Edition)..............................................................184.2.5 DRM Audio Player API (3rd Edition)....................................................................184.2.6 DRM Helper API (2nd Edition FP2)......................................................................184.2.7 DRM3 License Checker API (2nd Edition FP2)...................................................194.2.8 IPSec/VPN Client Application (2nd Edition FP2).................................................194.2.9 DRM Common API (2nd Edition FP3)..................................................................19

4.3 Multimedia and Graphics..............................................................................................19

4.3.1 Optical Character Recognition API (3rd Edition FP1)..........................................194.3.2 Content Listing Framework API (3rd Edition FP1)...............................................19




4/50

4.3.3 Exif API (3rd Edition)............................................................................................194.3.4 MIDI Client API (3rd Edition)................................................................................194.3.5 DRM Audio Player API (3rd Edition)....................................................................194.3.6 Audio Effects API (3rd Edition).............................................................................204.3.7 Audio Effects Presets API (3rd Edition)...............................................................204.3.8 Image Transform Library API (2nd Edition FP3, Symbian OS v8.1)....................204.3.9 Camera Support Enhancements (2nd Edition FP3).............................................20

4.3.10 GIF Scaler API (2nd Edition FP2, Symbian OS v8.0)........................................204.3.11 Speech recognition (2nd Edition FP2)...............................................................204.3.12 3-D Graphics - OpenGL ES (2nd Edition FP2, Symbian OS v8.0)....................204.3.13 Enhanced Media Gallery (2nd Edition FP2).......................................................204.3.14 Nokia Camera API (3rd Edition).........................................................................20

4.4 Communications...........................................................................................................214.4.1 Web Service Connection API (3rd Edition)..........................................................214.4.2 Web Service Description API (3rd Edition)..........................................................214.4.3 Web Service Manager API (3rd Edition)..............................................................214.4.4 XML Extensions API (3rd Edition)........................................................................214.4.5 SIP Stack and APIs (3rd Edition).........................................................................214.4.6 SIP Client Resolver API (3rd Edition)...................................................................214.4.7 OMA DNS 1.0 support (3rd Edition).....................................................................214.4.8 WLAN support (3rd Edition).................................................................................214.4.9 Network Status API (3rd Edition).........................................................................214.4.10 3rd Party Telephony API (3rd Edition, Symbian OS v8.0).................................214.4.11 Multiple secondary PDP contexts (2nd Edition FP3).........................................214.4.12 Connection Monitor API (2nd Edition FP2)........................................................224.4.13 WCDMA support (2nd Edition FP2)...................................................................224.4.14 Circuit Switched Video Call (2nd Edition FP2)...................................................224.4.15 EDGE support (2nd Edition FP1).......................................................................224.4.16 Bluetooth enhancements...................................................................................224.4.17 OBEX API (2nd Edition FP1).............................................................................234.4.18 SIP APIs moved from S60 to Symbian OS (3rd Edition FP1)............................234.4.19 ETEL classes (3rd Edition, Symbian OS v9.1)...................................................23

4.4.20 RNifMan / RGenericAgent (3rd Edition, Symbian OS v9.1)...............................234.4.21 WAP Stack and WSP API (2nd Edition FP3, Symbian OS v8.1).......................234.4.22 WAP Stack Client API (2nd Edition FP2, Symbian OS v8.0).............................234.4.23 Bluetooth Registry API (2nd Edition FP2, Symbian OS v8.0)............................234.4.24 PC Connectivity Server Framework API (2nd Edition FP1)...............................244.4.25 PLP Connection Link API (2nd Edition FP1)......................................................244.4.26 Connectivity Framework API (2nd Edition FP1).................................................24

4.5 UI..................................................................................................................................244.5.1 Flash Viewer Framework API (3rd Edition FP1)..................................................244.5.2 Flash Lite 2.0 Viewer (3rd Edition FP1)...............................................................244.5.3 Screen Mode API (3rd Edition FP1).....................................................................244.5.4 Qwerty keypad support (3rd Edition)....................................................................24

4.5.5 Scalable UI framework (2nd Edition FP3)............................................................244.5.6 Scalable Icons API (2nd Edition FP3)..................................................................254.5.7 Pictograph API (2nd Edition FP2)........................................................................254.5.8 Semi-transparent windows (2nd Edition FP2, Symbian OS v8.0)........................254.5.9 S60 UI APIs (3rd Edition).....................................................................................254.5.10 Platform icons (3rd Edition)................................................................................254.5.11 S60 UI localization file (2nd Edition FP2)...........................................................26

4.6 Data Synchronization and Device Management..........................................................264.6.1 SyncML APIs (3rd Edition)...................................................................................26

4.7 Location........................................................................................................................264.7.1 Landmarks API (3rd Edition)................................................................................264.7.2 Landmark Search API (3rd Edition).....................................................................264.7.3 Landmarks Database Management API (3rd Edition)..........................................26

4.7.4 Landmarks UI Add/Edit API (3rd Edition).............................................................264.7.5 Landmarks UI Selector API (3rd Edition).............................................................26




5/50

4.7.6 BLID Application Satellite Info API (3rd Edition)..................................................264.7.7 Location Acquisition API (2nd Edition FP2).........................................................27

4.8 Browsing and downloading..........................................................................................274.8.1 Download Manager APIs (2nd Edition FP3)........................................................274.8.2 Browser Control API (2nd Edition FP3)................................................................274.8.3 Browser Plug-in API (2nd Edition FP2)................................................................27

4.9 Messaging....................................................................................................................27

4.9.1 New Message Notification API (3rd Edition)........................................................284.9.2 IM API (3rd Edition)..............................................................................................284.9.3 IM Application Launch API (3rd Edition)..............................................................284.9.4 Presence API (3rd Edition)...................................................................................28

4.10 PIM.............................................................................................................................284.10.1 Calendar Interim API (3rd Edition, Symbian OS v9)..........................................284.10.2 Local time and daylight saving support (2nd Edition FP3, Symbian OS v8.1)

............................................................................................................................294.10.3 Agenda Model API (3rd Edition, Symbian OS v9)..............................................294.10.4 Calendar Conversion API (3rd Edition, Symbian OS v9)...................................294.10.5 World Server API (3rd Edition, Symbian OS v9)................................................29

5 Java MIDP............................................................................................................................305.1 Scalable 2D Vector Graphics API for Java ME, JSR-226 (3rd Edition FP1)................305.2 Advanced Multimedia Supplements, JSR-234 (3rd Edition FP1).................................305.3 Location API, JSR-179 (3rd Edition)............................................................................315.4 SIP API, JSR-180 (3rd Edition)....................................................................................315.5 Security and Trust Services (SATSA), JSR-177 (3rd Edition)......................................315.6 WMA API 2.0, JSR-205 (3rd Edition)...........................................................................32

5.6.1 Cell Broadcast and CB Push Registry support (2nd Edition FP3).......................325.7 Scalable 2D Vector Graphics API, JSR-226 (3rd Edition FP1)....................................325.8 Effects of Scalable UI for Java MIDP (2nd Edition FP3)..............................................325.9 J2ME Web Services Specification, JSR-172 (2nd Edition FP3)...................................325.10 Enhancements for Java APIs for Bluetooth, JSR-82..................................................32

5.10.1 OBEX support (2nd Edition FP3).......................................................................325.10.2 Push registry support (2nd Edition FP2)............................................................32

5.11 CLDC 1.1, JSR-139 (2nd Edition FP2).......................................................................325.12 PIM API, JSR-75 (2nd Edition FP2)...........................................................................335.13 FileConnection API, JSR-75 (2nd Edition FP2)..........................................................335.14 Mobile 3D Graphics API, JSR-184 (2nd Edition FP2)................................................33

5.14.1 Mobile 3D Graphics API for Java ME v1.1, JSR-184 (3rd Edition FP1).............335.15 Complete JTWI 1.0 compliancy, JSR-185 (2nd Edition FP2).....................................335.16 Enhancements for Mobile Media API, JSR-135.........................................................33

5.16.1 HTTP streaming support (3rd Edition FP1)........................................................335.16.2 Midi control support (3rd Edition).......................................................................335.16.3 Streaming media support (2nd Edition FP3)......................................................335.16.4 Mobile Media API 1.1 (2nd Edition FP1)............................................................34

5.17 Additional Notes or Changes......................................................................................34

5.17.1 Platform security................................................................................................345.17.2 Nokia UI API is deprecated (2nd Edition)...........................................................346 Browsing and downloading features....................................................................................35

6.1 New browser (3rd Edition FP1)....................................................................................356.2 Download Manager (2nd Edition FP3 / 3rd Edition).....................................................356.3 OMA download support for billing notification (3rd Edition)..........................................356.4 Large file downloads over HTTP (2nd Edition FP3).....................................................356.5 Browser Plug-ins..........................................................................................................36

6.5.1 Flash Lite 2.0 plug-in (3rd Edition FP1)................................................................366.5.2 Video plug-in (3rd Edition FP1)............................................................................366.5.3 Flash Lite 1.1 plug-in (3rd Edition).......................................................................366.5.4 SVG-Tiny plug-in (2nd Edition FP3).....................................................................366.5.5 Audio plug-in to Multimedia Framework (2nd Edition FP3)..................................36

6.6 Plug-in browser for (X)HTML rendering.......................................................................366.7 XHTML Mobile Profile 1.1 (2nd Edition FP2)...............................................................36




6/50

6.8 HTTP Digest authentication (2nd Edition FP2)............................................................366.9 Content/file upload (2nd Edition FP2)..........................................................................366.10 Links to other applications (2nd Edition FP2).............................................................366.11 New Accept Header (2nd Edition FP2)......................................................................376.12 SMS, MMS, and MMSto Schemes (2nd Edition FP2)................................................376.13 ECMAScript Mobile Profile (2nd Edition FP1)............................................................376.14 Support for HTML 4.01 (2nd Edition FP1)..................................................................37

6.15 Meta and object tag (2nd Edition FP1).......................................................................376.16 Performance Enhancements (2nd Edition FP1).........................................................376.17 UI Enhancements.......................................................................................................37

6.17.1 Enhanced narrow-screen rendering (2nd Edition FP3)......................................376.17.2 Scalable UI support (2nd Edition FP3)...............................................................386.17.3 Frames (2nd Edition FP2)..................................................................................386.17.4 Full-screen mode (2nd Edition FP1)..................................................................386.17.5 A download progress bar (2nd Edition FP1)......................................................386.17.6 Scrollbars (2nd Edition FP1)..............................................................................386.17.7 Adaptive history list (2nd Edition FP1)...............................................................386.17.8 An auto-complete feature (2nd Edition FP1)......................................................386.17.9 Background Image (2nd Edition FP1)................................................................38

6.18 Push service enhancements (2nd Edition FP1).........................................................386.19 WalletApplication is removed (2nd Edition FP3)........................................................38

7 Messaging features..............................................................................................................397.1 SMS enhancements.....................................................................................................39

7.1.1 Support for WCDMA Cell Broadcast (CBS) (3rd Edition).....................................397.1.2 Showing the unused characters real-time (3rd Edition).......................................397.1.3 SMS and Internet electronic mail interworking (3rd Edition)................................397.1.4 Reading and selecting SMSC (3rd Edition)..........................................................397.1.5 Sending and receiving of SMS messages in WCDMA (2nd Edition FP2)............397.1.6 Highlighted items in the message viewer (2nd Edition FP2) ...............................39

7.2 MMS enhancements....................................................................................................397.2.1 Subject, recipient, and priority fields (3rd Edition)................................................397.2.2 Enhanced delivery reports (3rd Edition)...............................................................39

7.2.3 MMS Postcard client (3rd Edition)........................................................................407.2.4 MMS Upload services (2nd Edition FP3).............................................................407.2.5 MMS Enhancements in 2nd Edition FP2.............................................................40

7.3 E-mail enhancements...................................................................................................417.3.1 Subject and recipient fields (3rd Edition)..............................................................417.3.2 E-mail enhancements in 2nd Edition FP2............................................................417.3.3 Enhancements in 2nd Edition FP1.......................................................................41

7.4 Instant Messaging and Presence.................................................................................417.4.1 IM enhancements in 3rd Edition...........................................................................427.4.2 IM and Presence enhancements in 2nd Edition FP2...........................................427.4.3 Instant Messaging and Presence (2nd Edition FP1)............................................427.4.4 Chat application (2nd Edition FP1)......................................................................42

7.4.5 Presence services (3rd Edition)...........................................................................428 Audio, video, and streaming.................................................................................................438.1 eAAC+ and other new media formats (3rd Edition FP1)..............................................438.2 Streaming Rate Adaptation (3rd Edition)......................................................................448.3 Streaming QoS (2nd Edition FP3)................................................................................44

9 DRM.....................................................................................................................................459.1 OMA DRM v2.0 (3rd Edition)........................................................................................459.2 OMA DRM v1.0 (2nd Edition FP2)...............................................................................46

10 Terms and Abbreviations...................................................................................................4711 References.........................................................................................................................4812 Evaluate this resource........................................................................................................50




7/50

Change History

September 5, 2005 Version 1.0 Initial document release

October 21, 2005 Version 1.1 Minor updates throughout thedocument

November 2, 2005 Version 1.2 Minor Terminology updates

May 4, 2006 Version 1.3 JSR-226, SATSA APDU,WebUtils API, and DS/DMAPIs removed

July 7, 2006 Version 1.4 Document updated to includeS60 3rd Edition FP1.

Published on Forum NokiaPRO.

October 16, 2006 Version 1.5 Minor editorial updates to thedocument.

Published on Forum Nokia




8/50

1 Introduction

1.1 Purpose and scope

This document discusses differences in features, relevant for developers, between S602nd Edition and 3rd Edition, (including S60 3rd Edition, Feature Pack 1). It presents new,

enhanced, and removed features or functionality between the versions. It also presents in whichrelease the change has taken place. This is always indicated together with the feature inbrackets.

The first chapters of this document will give an overview of the S60 platform evolution and anintroduction of S60 3rd Edition for developers. From chapter four onwards differences infeatures are listed by technology area.

In practice this document contains much of the same information as the following four What'sNew documents, and also partially some of the issues discussed in more detail in the S60Platform: Source and Binary Compatibility document:

S60 3rd Edition: What's New for Developers

S60 2nd Edition Feature Pack 3: What's New - Lead Features and APIsS60 2nd Edition Feature Pack 2: What's New - Lead Features and APIs

S60 2nd Edition Feature Pack 1: What's New - Lead Features and APIs

S60 Platform: Source and Binary Compatibility

1.2 Target audience

The document is targeted at software developers who have implemented applications (orservices) for earlier S60 platforms and who wish to migrate their applications to S60 3rd Edition.It is also intended for developers who are creating new applications for S60 3rd Edition, but whowish to produce applications that will run on earlier editions of the S60 platform as well.




9/50

2 Overview of S60 3rd Edition

The S60 3rd Edition platform is based on Symbian OS v9.1 (S60 3rd Edition, Feature Pack 1is based on Symbian OS v9.2). It incorporates important changes that Symbian C++ developersmust be aware of. For application developers, there are some new APIs for C++ development,and enhanced and new APIs for Java developers. Also support for updated versions for earlier

released standards and a couple of new technology features are introduced.From 3rd Edition onwards there has been a new compiler embedded into the platform. It isbased on ARM's Embedded Application Binary Interface (EABI) standard. One of the immediatedownsides of adopting a new compiler based on this standard is that it will cause a binary breakwith all previous versions of the S60 platform. Additionally, developers will have to acquire newtools. However, the new compiler produces applications with a smaller ROM footprint andenhances performance for S60 software. There will also be some improvement in third-partyapplication performance.

S60 3rd Edition includes new security issues. It presents mandatory .sis file signing, which

means that all .sis files must be signed before installing them to the device. The "Capability

Model" means that for third-party applications certain APIs are restricted and that specificcapabilities must be granted before an application can utilize the desired features. Capabilitiesare defined only for signed applications; unsigned applications have no capabilities defined.There are two certifications for signing which developers need for gaining access to restrictedAPIs: the "Symbian Signed" certification is needed to allow the release version of a suitablycomplex application to run on devices based on the 3rd Edition (and later), and "SymbianDeveloper Certificate" is required to allow developers to test the application on a real deviceduring development. It is important to note that these certification requirements allow Nokia topublish many APIs that were previously private. For more detailed information concerning thecapabilities, see the SDK documentation and the document Testing and Signing with Symbianplatform security at http://www.forum.nokia.com/info/sw.nokia.com/id/ecf0292f-e59b-4f6e-b7d1-6008679dba1e/Testing_and_Signing_with_Symbian_Platform_Security_v1_4_en.pdf.html.

Other new features available in the S60 3rd Edition platform include, for example, the following: Real-time kernel

C++ Landmarks APIs

C++ SIP Stack and APIs

Java SIP API, JSR-180

Java Location API, JSR-179

Java Security and Trust Services API, JSR-177

Java Wireless Messaging API (WMA) 2.0, JSR-205

New audio formats and APIs

Besides the totally new features, there are many new features introduced already on top of the2nd Edition as lead features with the Feature Packs, but which will now become part of the coresoftware of S60 3rd Edition. Probably the most significant of those is the support for ScalableUI introduced with the 2nd Edition, Feature Pack 3.

2.1 S60 3rd Edition, Feature Pack 1

S60 3rd Edition Feature Pack 1 is based on Symbian OS v9.2. New features available in S603rd Edition, Feature Pack 1 include, for example, the following APIs for C++ development:

Optical Character Recognition API

Content Listing Framework API

Flash Viewer Framework API

Central Repository Notification Handler API

Profiles Engine Wrapper API


http://www.forum.nokia.com/info/sw.nokia.com/id/ecf0292f-e59b-4f6e-b7d1-6008679dba1e/Testing_and_Signing_with_Symbian_Platform_Security_v1_4_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/ecf0292f-e59b-4f6e-b7d1-6008679dba1e/Testing_and_Signing_with_Symbian_Platform_Security_v1_4_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/ecf0292f-e59b-4f6e-b7d1-6008679dba1e/Testing_and_Signing_with_Symbian_Platform_Security_v1_4_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/ecf0292f-e59b-4f6e-b7d1-6008679dba1e/Testing_and_Signing_with_Symbian_Platform_Security_v1_4_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/ecf0292f-e59b-4f6e-b7d1-6008679dba1e/Testing_and_Signing_with_Symbian_Platform_Security_v1_4_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/ecf0292f-e59b-4f6e-b7d1-6008679dba1e/Testing_and_Signing_with_Symbian_Platform_Security_v1_4_en.pdf.html


10/50

Screen Mode API

New or updated features for Java development include:

Scalable 2D Vector Graphics API for J2ME (JSR-226)

Advanced Multimedia Supplements (JSR-234)

Mobile 3D Graphics API for J2ME v1.1 (JSR-184).

Other new features include:

New Browser

Flash Lite 2.0

OpenGL ES 3D Engine upgrade to v1.1

OMA DRM v2 for video




11/50

3 S60 platform evolution

According to the Nokia platform compatibility promise, all devices based on a certain platformedition are compatible with the core software of that edition. On top of that, later platformversions may introduce new functionalities as lead features (Feature Packs), but they are notallowed to introduce breaks or incompatibilities to the core software of that edition. Typically

most lead features introduced with the feature packs on top of the core software of the currentedition will later become part of the core software of the next edition. Also individual devicesmay introduce lead features, but again are not allowed to introduce any breaks orincompatibilities to the core software of that edition. In practice, some small and very minorbreaks may still occur, which are then documented and communicated.

Breaks and incompatibilities are only allowed when introducing a new core edition of theplatform, but not preferred with those either. When going from S60 1st Edition to the 2nd Edition,there were only a limited number of breaks and migration was fairly easy. In addition, makingthe same application run on both of those editions, and thereby on all devices currentlycompliant with the S60 platform, is fairly easy. Going from 2nd Edition to 3rd Edition, which wasnot binary compatible with the earlier releases, there were more breaks on source code level,and therefore migration from 2nd Edition to 3rd Edition was less trivial. Typically at least some

level of rework was needed to make existing S60 applications run on devices based on S60 3rdEdition. However, compatibility will be maintained after that between the future releases. Thisis true for S60 3rd Edition Feature Pack 1 also.

The following figure illustrates the evolution of the S60 platform.

Figure 1: S60 platform evolution with possible break points

The following figure illustrates the evolution from the S60 2nd Edition to the S60 3rd Edition. Italso presents the version of underlying Symbian OS and lists main new features in each release.




12/50

Figure 2: S60 platform evolution from 2nd Edition to 3rd Edition Feature Pack 1 with key featureadditions and the version of Symbian OS, on which the platform is based




13/50

4 Symbian C++ or Generic

Figure 3: Symbian OS architecture

The following sections list the differences between S60 2nd and 3rd Edition (including FeaturePack 1) for the Symbian C++ developers. The basis of the categorization of the differences hasbeen the figure above describing the Symbian OS architecture. In the architecture, securityservices happen on multiple levels and therefore they are not identifiable as their own high-levelblock. Messaging, Browsing, PIM, and Data Synchronization are examples of sub-blocks insideapplication services (only visible in a more detailed view). Location services are currently

provided by the S60 platform only, not by Symbian OS; they are therefore not visible in a moredetailed view either, but are otherwise considered as a sub-block of the application services.

The time of the change is indicated in brackets after the title of difference. The nature of thechange can be any of the following: new, enhanced/modified, deprecated, or removed.

Note: Detailed documentation of the APIs can be found from the SDK Help of the S60 SDK.

4.1 Base

NEW OR MODIFIED

4.1.1 Small default stack size in S60 3rd Edition

With Symbian OS v9, the default stack size was reduced from 20 kB to 8 kB to optimize

memory consumption because platform security caused an increase in the number ofrunning processes in the system.

In practice, the 8 kB stack has proven to be quite small for any larger S60 application.Even if the stack size were sufficient when the application is run on current devices,there is an increased risk of crashes due to stack overflow in future S60 3rd Editiondevices as new features can cause a slight increase in stack consumption of theplatform libraries. Thus, using a too small size for the stack endangers also binarycompatibility.

Increasing the stack size to 20 kB is recommended for all applications written with theS60 3rd Edition SDK. Applications need to be recompiled in order to modify the stacksize.

Stack sizes other than the default 8 kB can be configured with the epocstacksize

statement in the .mmp project definition file:




14/50

epocstacksize stacksize

The size of the stack, in bytes, can be specified in decimal or hexadecimal format. Usingthis statement will have no effect under the WINSCW/WINS platforms.

For example, adding the following line to the .mmp file will increase the stack size to 20

kB:

epocstacksize 0x5000

Alternatively, stack size can be defined for a new thread when creating the thread.

Example:

TARGET mce.exeEPOCSTACKSIZE 0x5000TARGETTYPE exeUID 0x0 0x100058C5

4.1.2 Fonts API (3rd Edition FP1)

A new class has been added to Fonts API. The aknfontaccess.h class gives access

to S60 font system.

4.1.3 Real-time kernel (3rd Edition, Symbian OS v9.1)

EKA2 (Epoc Kernel Architecture 2) kernel architecture

Support for real-time applications

Improved hardware adaptation

Foundation for Platform Security

4.1.4 Central Repository (3rd Edition, Symbian OS v9.1)

CenRep provides a generic way to access and share persistent settings and data. Onthe other hand, P&S is used for non-persistent (RAM-based) Shared Data settings. BothCenRep and P&S are services provided by Symbian OS. The Central Repository API

is offered to read the key values from the Central Repository.

4.1.5 Install system (3rd Edition, Symbian OS v9.1)

Applications install on S60 3rd Edition devices only if the enhanced installation fileformat SISX is used. When creating the installation package with tools such as MakeSISor CreateSIS (wrapper for MakeSIS, SignSIS, and MakeKeys utilities), the correctformat will be automatically used. Note that the actual file extension of the installationpackage still remains .sis.

4.1.6 New tool chain (3rd Edition, Symbian OS v9.1)

New ARM RVCT and GCC EABI compilers.

For more information on the new tool chain, see the document S60 3rd Edition: ToolChain, IDEs, And Development Process at http://www.forum.nokia.com/info/sw.nokia.com/id/5d1433ce-482a-4d12-9e48-d3ada8107aea/S60_3rd_Ed_Tool_Chain_IDEs_And_Development_Process_v1_2_en.pdf.html.

4.1.7 Wide usage of ECOM plug-ins (3rd Edition, Symbian OS v9.1)

All the scanning-based plug-in frameworks, recognizers, notifiers, FEPs, andconverters are now implemented as ECOM plug-ins. New location and registration filesfor ECOM plug-ins.

4.1.8 Standard C++ additions

For historical reasons the Symbian OS did not originally support the standard C++exception mechanism but from S60 3rd Edition onwards it does. However, nativeSymbian OS code should continue to use the TRAP/Leave mechanism. C++ style try-


http://www.forum.nokia.com/info/sw.nokia.com/id/5d1433ce-482a-4d12-9e48-d3ada8107aea/S60_3rd_Ed_Tool_Chain_IDEs_And_Development_Process_v1_2_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/5d1433ce-482a-4d12-9e48-d3ada8107aea/S60_3rd_Ed_Tool_Chain_IDEs_And_Development_Process_v1_2_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/5d1433ce-482a-4d12-9e48-d3ada8107aea/S60_3rd_Ed_Tool_Chain_IDEs_And_Development_Process_v1_2_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/5d1433ce-482a-4d12-9e48-d3ada8107aea/S60_3rd_Ed_Tool_Chain_IDEs_And_Development_Process_v1_2_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/5d1433ce-482a-4d12-9e48-d3ada8107aea/S60_3rd_Ed_Tool_Chain_IDEs_And_Development_Process_v1_2_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/5d1433ce-482a-4d12-9e48-d3ada8107aea/S60_3rd_Ed_Tool_Chain_IDEs_And_Development_Process_v1_2_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/5d1433ce-482a-4d12-9e48-d3ada8107aea/S60_3rd_Ed_Tool_Chain_IDEs_And_Development_Process_v1_2_en.pdf.html


15/50

catch exceptions should be used only in C++ code that is being ported from otherenvironments. When porting code that uses exceptions, do not mix them and theSymbian OS leave mechanism. Prior to S60 3rd Edition the only choice was to use theTRAP/TRAPD macro.

4.1.9 On-target debugging (3rd Edition)

MetroTRK replaces GDBSTUB as the on-target debugging solution.

4.1.10 Light API (3rd Edition)

The Light API provides control to, for example, background lights and keypad lights.

4.1.11 Vibra API (3rd Edition)

The new, more robust Vibra API replaces the earlier Vibra Control API providing controlto vibra.

4.1.12 Vibra Settings API (3rd Edition)

The Vibra Settings API provides access to vibra-related settings.

4.1.13 HWRM Power State API (3rd Edition)

The HWRM Power State API provides access to charging and power state information.

4.1.14 Remote Control Framework (3rd Edition, Symbian OS v9.1)

Remote Control Core API

Remote Control Framework operation API. This API provides functionality for controllingall operations defined in the Bluetooth Audio Video Remote Control Profile.

Remote Control Address API

Remote Control address used for identifying different connections in the Remote

Control Framework.Other related APIs that are needed to be able to use the Remote Control Core API andthe Remote Control Address API are:

Remote Control Client API

Remote Control Interface Selector API

Remote Control Types API

4.1.15 Profiles Engine Active Profile Settings API (3rd Edition)

Contains the settings (for example, ringing type and volume, keypad volume, andmessage alerts) of the active profile.

4.1.16 Find Item API (3rd Edition)

The Find Item API offers methods for parsing phone numbers, e-mail addresses, URIaddresses, or URL addresses from a given text.

4.1.17 Secure Digital (SD) card support (3rd Edition)

Support for SD card and Mini SD card.

4.1.18 Startup List Management API (3rd Edition)

The Startup List Management API provides the means for developers to add their nativeapplications (delivered inside installation packages) into the device's modifiable startuplist in order to launch the application at device startup.




16/50

4.1.19 PtiEngine API (3rd Edition)

The PtiEngine API provides access to low-level text input services, such as predictivetext input.

4.1.20 Info Popup Note API (3rd Edition)

The Info Popup Note API provides a control to the Info popup note with customizabletext.

4.1.21 Server Application API (3rd Edition)

The Server Application API provides an interface for server applications.

4.1.22 Common Audio Enhancements API (3rd Edition)

The Common Audio Enhancements API defines common interfaces used for audioenhancements.

4.1.23 Feature Discovery API (2nd Edition FP3)

The Feature Discovery API has been introduced in S60 2nd Edition, Feature Pack 3 toenquire whether certain features, such as WCDMA or Bluetooth, are supported by thecurrent environment.

4.1.24 Contacts Model API enhancement (2nd Edition FP3, Symbian OS v8.1)

An observer class has been added. Contacts model clients should subscribe to it inorder to be informed about the progress of a backup or restore operation.

4.1.25 Publish & Subscribe API (2nd Edition FP2, Symbian OS v8.0)

The Publish & Subscribe API provides a means to store system-wide global variablesand a new inter-process communication (IPC) mechanism for peer-to-peer

communication between threads. Publish & Subscribe will replace the System Agentand Shared Data (for temporary keys) functionality. The Publish & Subscribe featurewas introduced with S60 2nd Edition, Feature Pack 2.

4.1.26 Message Queues (2nd Edition FP2, Symbian OS v8.0)

Message Queues are a new IPC mechanism for peer-to-peer communication. Theyprovide a way of sending messages to an interested party without needing to knowwhether someone is listening or the identity of the recipient.

4.1.27 XML Framework (2nd Edition FP2, Symbian OS v8.0)

Symbian OS v8.0 introduces a unified XML parser framework through which all XMLparsing capabilities can potentially be made available. This should serve to allow greater

reuse of system code, as well as making client code more portable.

Although the API is delivered with S60 2nd Edition SDK, Supporting Feature Pack 2, itwas with prototype status in Symbian OS v8.0 and it has not been documented in theSymbian Developer Library (SDL) for v8.0. It is partially documented in SDL for v8.1shipping with S60 2nd Edition SDK, Supporting Feature Pack 3, and properlydocumented in SDL for v9.1 shipping with S60 3rd Edition SDK.

4.1.28 Huffman API (2nd Edition FP2, Symbian OS v8.0)

Support for Huffman encoding and decoding.

REMOVED




17/50


18/50

Data caging means that the applications and the users have access only to certainareas of the file system. In practice the applications can access their own privatedirectories and directories that are marked as open. It means, for example, that oneapplication cannot access another application's private directory and data.

The new file structure introduced through data caging is as follows:

/sys/ holds all executables (restricted access).

/private/ contains application-specific private data (restricted access).

/private/, where SID is the application's ID.

/resource/ contains publicly shared read-only files.

/Other directories/ open for read and write.

Capability model

A capability is an access token that corresponds to an access permission of sensitivesystem resources. The security architecture provides a number of differentcapabilities, such as access to the network connections or to the complete filesystem. To access a system resource, a client program must hold the appropriate

capability.Note: S60 3rd Edition includes mandatory .sis file signing, which means that

all .sis files must be signed using the SignSIS or CreateSIS utility (included in the

SDK) before installing them to the device. The installation package can be signedwith a self-created key and the certificate can be generated with the SDK.The .sis signing makes it difficult to tamper or otherwise change the original

installation package. In addition, any application can be certified with SymbianSigned. A Symbian Signed application has passed certain tests and the originator'sidentity has been verified. The aim behind these measures is to avoid malicioussoftware by providing a tamper-proof digital signature to the application.

For a more detailed description of the platform security and the capability model, seedocuments, such as the SDK documentation and the document Testing and Signingwith Symbian Platform Security at http://www.forum.nokia.com/info/sw.nokia.com/id/ecf0292f-e59b-4f6e-b7d1-6008679dba1e/Testing_and_Signing_with_Symbian_Platform_Security_v1_4_en.pdf.html.

4.2.3 Content Access Framework (3rd Edition, Symbian OS v9.1)

The Content Access Framework (CAF) includes the infrastructure to allow the handlingand protection of incoming content (for example, OMA DRM messages). ContentAccess Framework is partially supported already with S60 2nd Edition, Feature Pack 2and 3.

4.2.4 OMA DRM CAF Agent API (3rd Edition)

OMA DRM CAF Agent API provides OMA DRM CAF Agent-specific functions.

4.2.5 DRM Audio Player API (3rd Edition)

The DRM Audio Player API is used to play DRM-protected audio files for third-partyapplications that do not have DRM capability. This API is described also sectionMultimedia and Graphics.

4.2.6 DRM Helper API (2nd Edition FP2)

The DRM API is an interface for handling DRM-specific error situations (such as rightsexpiration and missing rights), registering and unregistering DRM-protected content asautomated content, and getting details of DRM-protected content. This API is intended

for applications that need to deal with DRM-protected content.


http://www.forum.nokia.com/info/sw.nokia.com/id/ecf0292f-e59b-4f6e-b7d1-6008679dba1e/Testing_and_Signing_with_Symbian_Platform_Security_v1_4_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/ecf0292f-e59b-4f6e-b7d1-6008679dba1e/Testing_and_Signing_with_Symbian_Platform_Security_v1_4_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/ecf0292f-e59b-4f6e-b7d1-6008679dba1e/Testing_and_Signing_with_Symbian_Platform_Security_v1_4_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/ecf0292f-e59b-4f6e-b7d1-6008679dba1e/Testing_and_Signing_with_Symbian_Platform_Security_v1_4_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/ecf0292f-e59b-4f6e-b7d1-6008679dba1e/Testing_and_Signing_with_Symbian_Platform_Security_v1_4_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/ecf0292f-e59b-4f6e-b7d1-6008679dba1e/Testing_and_Signing_with_Symbian_Platform_Security_v1_4_en.pdf.html


19/50

4.2.7 DRM3 License Checker API (2nd Edition FP2)

DRM3 License Checker (License Manager) is a component that can be used to protectnative applications (and themes) on S60 devices. The DRM3 Checker API provides aninterface to the DRM3 License Manager. DRM3 Checker allows usage rightsenforcement for native applications, and the API consists of functions for checkingusage rights. Clients of the DRM3 Checker API are the protected applicationsthemselves.

4.2.8 IPSec/VPN Client Application (2nd Edition FP2)

S60 VPN Client is a version of the Nokia Mobile VPN Client adapted to the S60 platform.VPN Client leverages the Internet Protocol security (IPSec) support of the platform toprovide Virtual Private Network (VPN) services. It enables S60 devices to haveencrypted and authenticated communication with enterprise networks through themobile network and the Internet. This is an optional feature in S60 devices that arecompatible with S60 2nd Edition, Feature Pack 2 and later.

DEPRECATED

4.2.9 DRM Common API (2nd Edition FP3)

The legacy DRM Common API (providing a set of basic DRM-related operations thatare needed for implementing DRM-aware applications) has been deprecated with 2ndEdition FP3 and will possibly be removed from S60 3rd Edition. The Content AccessFramework should be used instead.

4.3 Multimedia and Graphics

Multimedia and graphics covers aspects such as audio, video, graphics, imaging, and camera.See also sections UI and Audio, Video, and Streaming.

NEW

4.3.1 Optical Character Recognition API (3rd Edition FP1)

The Optical Character Recognition (OCR) API provides a picture to a text service forapplications. The API takes a picture as an input and produces text based on recognizedcharacters. The picture can be for example a photograph taken with the device'scamera.

4.3.2 Content Listing Framework API (3rd Edition FP1)

The purpose of the Content Listing Framework API is to enable applications to retrieveinformation about the media content stored in the device. The API provides listing, listediting, sorting, grouping, and filtering services.

4.3.3 Exif API (3rd Edition)Exif header information creation/read/modification support for compressed JPEGimages.

4.3.4 MIDI Client API (3rd Edition)

Symbian OS v8.0 provides a MIDI API that allows MIDI technology providers to integratetheir software into the multimedia framework.

4.3.5 DRM Audio Player API (3rd Edition)

The DRM Audio Player API is used to play both plain and DRM-protected audio filesfor third-party applications that do not have DRM capability. The API offers a simple

interface to open, play, and obtain information from sampled audio data. The plain audiodata can be supplied either in a file (file-based), as a descriptor (descriptor-based), oras a URL reference. DRM-protected audio can be played only from a file.




20/50

4.3.6 Audio Effects API (3rd Edition)

The Audio Effects API provides access to audio effects such as equalizer or reverb,which are implemented on adaptation/lower layer. Audio effects are artificially createdor enhanced sounds. The API supports the following audio effects: bass boost, Doppler,audio equalizer, distance attenuation, location, loudness, orientation, reverb, and stereowidening.

4.3.7 Audio Effects Presets API (3rd Edition)

The Audio Effects Presets API supports audio effects presets for equalizer, reverb, andstereo widening. This API is simpler than the Audio Effects API.

4.3.8 Image Transform Library API (2nd Edition FP3, Symbian OS v8.1)

An API for scaling images held in files or descriptors.

4.3.9 Camera Support Enhancements (2nd Edition FP3)

Flash, Tone, and White Balance support added.

4.3.10 GIF Scaler API (2nd Edition FP2, Symbian OS v8.0)

GIF Scaler is a new API addition to the multimedia framework (MMF) image conversionlibrary (ICL). The API provides scaling and color quantization of bitmaps asasynchronous operations.

4.3.11 Speech recognition (2nd Edition FP2)

The multimedia framework is extended with a speech-recognition utility framework. Thisallows providers of speech-recognition technology to integrate their software into anMMF and make it available to client code through a standard API.

4.3.12 3-D Graphics - OpenGL ES (2nd Edition FP2, Symbian OS v8.0)

OpenGL ES is a lightweight API for bringing advanced graphics capabilities to anincreasing variety of mobile and handheld devices, appliances, and embedded displays.It is based on well-defined subset profiles of OpenGL and enables the lightest-weightinterface between software and hardware. Symbian OS v8.0 includes header files forthe OpenGL ES 3D graphics library.

OpenGL ES 3D Engine upgrade to v1.1 (3rd Edition FP1)

S60 3rd Edition Feature Pack 1 provides OpenGL ES 3D Engine upgraded to version1.1. It is defined to implement OpenGL 1.5 specification and provides EGL 1.1 API forrendering. The version 1.1 is compatible with the previous 1.0 version.

4.3.13 Enhanced Media Gallery (2nd Edition FP2)The Media Gallery application is completely renewed with S60 2nd Edition Feature Pack2 and offers an easy way to manage the various media that a S60 device can captureand display (for example, pictures, video, music, and sound). It also offers advancedways for the end users to sort and organize their media according to their preferences.

The contents of the music file folder (playlists, single tracks, and albums) are shown intheir own groups in alphabetical order. Note that music albums are created accordingto ID3tag information.

REMOVED

4.3.14 Nokia Camera API (3rd Edition)

The wrapper for the Nokia Camera API (Camera Server) is removed. Use the SymbianOnboard Camera API (ECam) instead.




21/50

4.4 Communications

Communications covers aspects such as networking (HTTP, sockets, TCP/IP, SIP), telephony,data bearers, local connectivity (IR, BT, serial cable, USB), and Web services.

NEW

4.4.1 Web Service Connection API (3rd Edition)This API offers ways to establish new Web service connections and to send messagesusing an established connection.

4.4.2 Web Service Description API (3rd Edition)

This API consists of a family of classes for describing services and service accesses,providing ways to manage information on different services and frameworks. The mostimportant functionality provided is XML type service description.

4.4.3 Web Service Manager API (3rd Edition)

The Web Service Manager API is used to store and retrieve service and identity

information.

4.4.4 XML Extensions API (3rd Edition)

Web Services Framework-specific adaptations to standard XML APIs.

4.4.5 SIP Stack and APIs (3rd Edition)

S60 3rd Edition includes support for the session initiated protocol stack, which wasearlier available only as a plug-in. There are some changes compared to the plug-inimplementation, including new APIs for developers, the SIP Configuration API, and theSIP Client Resolver API.

4.4.6 SIP Client Resolver API (3rd Edition)The ECOM interface that SIP clients must realize in order to be able to receive SIPrequests outside the dialogs. The reception of a SIP request might require the launchof the resolved target client in case the client is not running.

4.4.7 OMA DNS 1.0 support (3rd Edition)

The name resolver client in the TCP/IP stack implements all the mandatory features ofthe OMA Wireless Profiled DNS 1.0 (OMA-WAP-DNS-v1_0-20020909-C) specificationand also the optional IPv6 support.

4.4.8 WLAN support (3rd Edition)

WLAN is supported, but the actual availability is hardware-dependent.

4.4.9 Network Status API (3rd Edition)

An API for accessing network status information.

4.4.10 3rd Party Telephony API (3rd Edition, Symbian OS v8.0)

Provides access to telephony features such as calling operations, and getting network,IMEI (device serial number), and IMSI (subscriber ID) information.

4.4.11 Multiple secondary PDP contexts (2nd Edition FP3)

Multiple secondary PDP contexts are required, for example, when a user already has

a primary PDP context to an access point but needs a new context to the same accesspoint with different connection settings, that is, QoS. Multiple secondary contexts perone primary context will be supported.




22/50

4.4.12 Connection Monitor API (2nd Edition FP2)

The Connection Monitor API provides an interface for an application to get informationabout active data connections. It also provides a way to close any connection or allconnections.

4.4.13 WCDMA support (2nd Edition FP2)

S60 2nd Edition Feature Pack 2 introduced WCDMA support for the S60 platform. Theaddition of WCDMA support increases the bandwidth between the mobile device andnetwork up to 384 Kbps to downlink and 128 Kbps to uplink. The significant increase inbandwidth makes video streaming and video telephony applications more impressive.In addition, simultaneous voice call and use of WCDMA network is also supported,which enables developing new kinds of applications. WCDMA support is compliant withthe 3GPP Release 99 WCDMA/GPRS Dual Mode Specification. Note that this requiressupport from the device as well, that is, there will be devices based on 2nd EditionFeature Pack 2 without WCDMA. For more information, see Forum Nokia DeviceSpecifications at http://www.forum.nokia.com/devices.

The underlying support for WCDMA and CDMA is provided by Symbian OS.

4.4.14 Circuit Switched Video Call (2nd Edition FP2)

The S60 platform enables Circuit Switched (CS) Video Call, which is available in theWCDMA network with S60 2nd Edition Feature Pack 2. In practice, a video call is a CS(multimedia) data call that transfers both the video image and the audio. In addition, itseparates image and audio data to different logical "channels." Both mobile ends of thevideo call recognize that this "multimedia" call is a special kind of CS data call, and itmust be handled as a video call.

The Video Telephony application cannot be seen in the application grid as its ownapplication, but it will be activated automatically when a video call turns to the ActiveCall state.

4.4.15 EDGE support (2nd Edition FP1)

EDGE, a new radio interface technology with enhanced modulation, increases the High-Speed Circuit Switched Data (HSCSD) and General Packet Radio Service (GPRS) datarates to up to three-fold. EDGE modulation increases the data throughput provided bythe packet-switched service theoretically over 400 Kbps; however, the actual speed isdependent on the device and network implementations.

S60 2nd Edition, Feature Pack 1 is verified against EDGE. The applications that useGPRS connections can benefit from higher data rates provided by EDGE.

The underlying support for EDGE is provided by Symbian OS.

4.4.16 Bluetooth enhancements

Bluetooth 2.0 support (3rd Edition FP1)

S60 3rd Edition Feature Pack 1 upgrades the support for Bluetooth to Bluetooth 2.0connectivity without eSCO support.

Remote SIM Access Profile (3rd Edition)

Needed to access SIM information from Bluetooth devices, such as car kits.


http://www.forum.nokia.com/deviceshttp://www.forum.nokia.com/deviceshttp://www.forum.nokia.com/devices


23/50

Headset Profile (2nd Edition FP2)

Support for the Headset Profile is added to expand interoperability of Bluetoothaccessories. Previously only the Hands-Free Profile was supported in the S60 platform.The mobile device provides a listener for accessories that connect to the device via theHeadset or Hands-Free Profile, and thus there is no need for an application running onthe device.

Basic Imaging Profile (2nd Edition FP2)

The Basic Imaging Profile enables compatible Bluetooth devices to negotiate the sizeand encoding of imaging data before sending or receiving it. The Basic Imaging Profileis dependent on the Generic Object Exchange Profile.

Bluetooth Notifier API (2nd Edition FP1)

Contains information for Bluetooth Notifiers.

4.4.17 OBEX API (2nd Edition FP1)

Object Exchange protocol services API.

OBEX Updated (3rd Edition FP1)

New header files added to OBEX API

REMOVED

4.4.18 SIP APIs moved from S60 to Symbian OS (3rd Edition FP1)

SIP Client API, SIP Configuration API, SIP Codec API, SDP Codec API, SIP Profile API,and SIP Client Resolver API are moved from S60 platform to Symbian OS with therelease of S60 3rd Edition Feature Pack 1. From now on, the documentation of theseSIP APIs will be therefore provided by Symbian.

4.4.19 ETEL classes (3rd Edition, Symbian OS v9.1)

ETEL core classes that were deprecated in Symbian OS v8.0a will no longer besupported in Symbian OS v9.1. Use the 3rd Party Telephony API instead.

4.4.20 RNifMan / RGenericAgent (3rd Edition, Symbian OS v9.1)

The obsolete and earlier deprecated Network Information Manager (RNifMan) and

RGenericAgent classes are no longer supported in Symbian OS v9.1.

4.4.21 WAP Stack and WSP API (2nd Edition FP3, Symbian OS v8.1)

The WAP Stack and WSP API have been removed from Symbian OS v8.1. The HTTPStack must be used instead. WAP-related header files from the HTTP Client API have

also been removed.

4.4.22 WAP Stack Client API (2nd Edition FP2, Symbian OS v8.0)

The WAP stack is no longer fully supported in Symbian OS v8.0. Applications using theWAP Stack API should be redesigned to use other connection methods instead, suchas the HTTP Client API.

4.4.23 Bluetooth Registry API (2nd Edition FP2, Symbian OS v8.0)

There are a number of architectural changes in the Bluetooth APIs provided by SymbianOS in v8.0, affecting both source and binary compatibility. The Bluetooth Registry APImanaging Bluetooth device registry has been removed (and replaced by the

RBTRegServ, RBTRegistry, TBTRegistrySearch , and theCBTRegistryResponse classes defined in btmanclient.h).




24/50

The btdefcommport.h managing port and service settings of the legacy serial port

applications has also been removed, and there are changes in the Bluetooth SecurityManager API, Bluetooth Device API, and in Bluetooth sockets. For more detailedinformation, see the document S60 Platform: Source And Binary Compatibility at http://www.forum.nokia.com/info/sw.nokia.com/id/2ac24078-a0b3-4bd2-8b03-1707fa2e1405/S60_Platform_Source_and_Binary_Compatibility_v1_4_en.pdf.html.

4.4.24 PC Connectivity Server Framework API (2nd Edition FP1)

The PC Connectivity Server Framework API is replaced by the OBEX API.

4.4.25 PLP Connection Link API (2nd Edition FP1)

The Psion Link Protocol (PLP) Connection Link API is replaced by the OBEX API.

4.4.26 Connectivity Framework API (2nd Edition FP1)

The Connectivity Framework API (mRouter) in S60 2nd Edition is replaced by the OBEXAPI.

4.5 UI

NEW

4.5.1 Flash Viewer Framework API (3rd Edition FP1)

The purpose of the Flash Viewer Framework API is to start Viewer UI for playing Flashcontent file (SWF). It provides the necessary UIs to display public SWF files created byauthoring tools and downloaded into a device. Content can be played by a viewerapplication or by stub applications, which view private SWF files representingapplications or games, for example. The framework also offers an interface to a viewerto pass necessary settings for playing customization.

4.5.2 Flash Lite 2.0 Viewer (3rd Edition FP1)Flash Lite 2.0 Viewer is a plug-in, which enables viewing of Flash Lite 2.0 content andis also backward compatible with the earlier Flash Lite 1.1 content.

Flash Lite 1.1 Viewer (3rd Edition)

Easy content authoring and deployment. The Flash Lite 1.1 Viewer may already beavailable with some S60 2nd Edition, Feature Pack 3 devices.

4.5.3 Screen Mode API (3rd Edition FP1)

The Screen Mode API provides an interface for producing screen mode data.

4.5.4 Qwerty keypad support (3rd Edition)Qwerty keypad is supported, but the actual availability is hardware-dependent.

4.5.5 Scalable UI framework (2nd Edition FP3)

The Scalable UI architecture has been introduced to extend the S60 platform to supportdifferent screen sizes. Using a scalable user interface allows developers to writeapplications that can display different user interfaces based on the physicalcharacteristics of the target device. Previous versions of the S60 platform onlysupported devices with a fixed screen resolution of 176 pixels by 208 pixels. Thisallowed developers to design a user interface for any S60 device confident that theapplication would look the same on any other S60 device, regardless of themanufacturer. Advances in hardware and network services allow applications to displayand process feature-rich content, and new device displays can take full advantage ofthese new features. Adding new screen resolutions would normally mean that


http://www.forum.nokia.com/info/sw.nokia.com/id/2ac24078-a0b3-4bd2-8b03-1707fa2e1405/S60_Platform_Source_and_Binary_Compatibility_v1_4_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/2ac24078-a0b3-4bd2-8b03-1707fa2e1405/S60_Platform_Source_and_Binary_Compatibility_v1_4_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/2ac24078-a0b3-4bd2-8b03-1707fa2e1405/S60_Platform_Source_and_Binary_Compatibility_v1_4_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/2ac24078-a0b3-4bd2-8b03-1707fa2e1405/S60_Platform_Source_and_Binary_Compatibility_v1_4_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/2ac24078-a0b3-4bd2-8b03-1707fa2e1405/S60_Platform_Source_and_Binary_Compatibility_v1_4_en.pdf.html


25/50

developers would have to produce device-specific versions of their applications. Theaim of the new architecture is to allow applications to provide a consistent 'look and feel'or layout across all platforms.

For more information on the scalable UI, see the documents:

Introduction To The S60 Scalable UI at http://www.forum.nokia.com/info/sw.nokia.com/id/7f92c18f-fe85-4987-a4f8-66133a16d009/

Introduction_To_The_S60_Scalable_UI_v1_4_en.pdf.html S60 Scalable UI Support at http://www.forum.nokia.com/info/sw.nokia.com/id/

69865916-eaa4-4957-83a9-f0c372a9b4a0/S60_Platform_Scalable_UI_Support_v4_3_en.pdf.html

S60 Scalable UI Example at http://www.forum.nokia.com/info/sw.nokia.com/id/381854ba-86f4-4106-a650-6ae139c6ba9a/S60_Platform_Scalable_UI_Example_v2_0_en.zip.html

4.5.6 Scalable Icons API (2nd Edition FP3)

2nd Edition Feature Pack 3 provides support for Scalable Vector Graphics Tiny profile(SVG-T). SVG-T files can be used in icons and themes instead of bitmaps. One of the

main disadvantages of bitmapped graphics formats is that image quality is often lostwhen the image is scaled up.

4.5.7 Pictograph API (2nd Edition FP2)

Pictographs are graphical symbols that can be inserted in the text in editors. Japaneseoperators also use them in SMS and e-mail messages. There is no universal standardfor representing pictograph code values in text. For example, the Japanese operatorsVodaphone and DoCoMo define their own sets of pictographs, which are notcompatible. Ultimately, this means that, without an appropriate conversion service,message transfer is not possible between devices from different operators, as far aspictographs are concerned. The API is part of the Avkon UI library and is providedthrough the CAknPictographInterface class.

4.5.8 Semi-transparent windows (2nd Edition FP2, Symbian OS v8.0)

One modification to the Uikon GUI framework of Symbian OS v8.0 is enabling semi-transparent windows. This is achieved by adding new methods to the RWindow class.

MODIFIED

4.5.9 S60 UI APIs (3rd Edition)

A general S60 UI framework API cleanup is done with S60 3rd Edition. Most deprecatedAPIs and obsolete UI framework headers will be removed. In addition, many APIoptimizations are introduced; for example, all the virtual functions in SDK API classesthat are derivable from outside the DLL are exported.

Additionally the S60 platform starts to use the Uikon UI library from Symbian, insteadof its own version of it, which should improve UI compatibility and portability amongSymbian OS-based platforms.

REMOVED

4.5.10 Platform icons (3rd Edition)

The Avkon.mbm file is removed from S60 3rd Edition. It is replaced by avkon2.mbm.

The icon indexes are still defined in the same header file (avkon.mbg). These icons

can be loaded normally using the methods available in the AknIconUtils class.


http://www.forum.nokia.com/info/sw.nokia.com/id/381854ba-86f4-4106-a650-6ae139c6ba9a/S60_Platform_Scalable_UI_Example_v2_0_en.zip.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/381854ba-86f4-4106-a650-6ae139c6ba9a/S60_Platform_Scalable_UI_Example_v2_0_en.zip.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/381854ba-86f4-4106-a650-6ae139c6ba9a/S60_Platform_Scalable_UI_Example_v2_0_en.zip.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/381854ba-86f4-4106-a650-6ae139c6ba9a/S60_Platform_Scalable_UI_Example_v2_0_en.zip.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/381854ba-86f4-4106-a650-6ae139c6ba9a/S60_Platform_Scalable_UI_Example_v2_0_en.zip.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/69865916-eaa4-4957-83a9-f0c372a9b4a0/S60_Platform_Scalable_UI_Support_v4_3_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/69865916-eaa4-4957-83a9-f0c372a9b4a0/S60_Platform_Scalable_UI_Support_v4_3_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/69865916-eaa4-4957-83a9-f0c372a9b4a0/S60_Platform_Scalable_UI_Support_v4_3_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/381854ba-86f4-4106-a650-6ae139c6ba9a/S60_Platform_Scalable_UI_Example_v2_0_en.zip.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/381854ba-86f4-4106-a650-6ae139c6ba9a/S60_Platform_Scalable_UI_Example_v2_0_en.zip.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/381854ba-86f4-4106-a650-6ae139c6ba9a/S60_Platform_Scalable_UI_Example_v2_0_en.zip.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/69865916-eaa4-4957-83a9-f0c372a9b4a0/S60_Platform_Scalable_UI_Support_v4_3_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/69865916-eaa4-4957-83a9-f0c372a9b4a0/S60_Platform_Scalable_UI_Support_v4_3_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/69865916-eaa4-4957-83a9-f0c372a9b4a0/S60_Platform_Scalable_UI_Support_v4_3_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/7f92c18f-fe85-4987-a4f8-66133a16d009/Introduction_To_The_S60_Scalable_UI_v1_4_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/7f92c18f-fe85-4987-a4f8-66133a16d009/Introduction_To_The_S60_Scalable_UI_v1_4_en.pdf.htmlhttp://www.forum.nokia.com/info/sw.nokia.com/id/7f92c18f-fe85-4987-a4f8-66133a16d009/Introduction_To_The_S60_Scalable_UI_v1_4_en.pdf.html


26/50

4.5.11 S60 UI localization file (2nd Edition FP2)

The file containing localization strings for S60 UI components, avkon.loc, is no

longer valid for S60 2nd Edition, Feature Pack 2 and has been removed from the SDK.

4.6 Data Synchronization and Device Management

REMOVED

4.6.1 SyncML APIs (3rd Edition)

SyncML APIs (Data Synchronization Adapter API and Device Management AdapterAPI) Common Synchronizer API, Data Synchronization Profile Listing API, and DataSynchronization Synchronizer API have been removed.

4.7 Location

4.7.1 Landmarks API (3rd Edition)

The Landmarks API provides basic landmark functionality for native Symbian C++

applications. It enables opening the default landmark database and performingoperations on it. This includes listing, reading, creating, updating, and deletinglandmarks, managing landmark categories, and listening for landmark database events.

Serialization support (3rd Edition FP1)

Serialization support enables packing and unpacking landmark objects for furtherserialization.

The class Epos_PosLmCategorySerialization.h contains static methods

PackL() and UnpackL() for packing and unpacking CPosLandmark instances.

The class Epos_PosLandmarkSerialization.h contains appropriate methods for

packing and unpacking CPosLandmarkCategory instances.

4.7.2 Landmark Search API (3rd Edition)

An API for Symbian C++ applications to search landmarks in the device by utilizingdifferent search criteria.

4.7.3 Landmarks Database Management API (3rd Edition)

The Landmarks Database Management API allows clients to manage landmarkdatabases, for example, creating new databases or deleting existing databases.

4.7.4 Landmarks UI Add/Edit API (3rd Edition)

The Landmarks UI Add/Edit API provides UI components for creating and manipulatinglandmarks.

4.7.5 Landmarks UI Selector API (3rd Edition)

The Landmarks UI Selector API provides an interface to applications for listing andselecting one or more landmarks or categories that exist in the landmarks database.

4.7.6 BLID Application Satellite Info API (3rd Edition)

This API provides UI components for showing current GPS satellite signal strengthinformation. BLID means Basic Location Info Display.

See also section Location API, JSR-179, for Java MIDP applications.




27/50

4.7.7 Location Acquisition API (2nd Edition FP2)

The Location Acquisition API enables terminal applications to acquire the location of aterminal. An application can utilize different positioning technologies via a single API.The API also enables simultaneous applications to use location information, locationmath operations, and provides access to advanced location information such as GPSsatellite information.

4.8 Browsing and downloading

See also chapter Browsing and downloading features which discusses the issue from a content/service developer's point of view.

4.8.1 Download Manager APIs (2nd Edition FP3)

Download Manager, which can be used by third-party applications, supports thefollowing features for file downloading:

File info provided before the download (for example, file size, type, target application)

Background downloading Downloads can take place in the background while the

user is still browsing. Notification of download completion

Downloads can be suspended / resumed (user commands)

Download of unsupported content after user confirmation

Download Manager UI Library API (2nd Edition FP3)

This is the API for Download Manager UI services. It enables the client to add a menuitem to its own Options list, show a list of active downloads, and gives support forregistration of user interactions and a Downloads List component.

Download Manager Engine API (2nd Edition FP3)

This is the client interface of the Download Manager server.

Note: Download Manager is not used by the standard browser in the S60 platform until3rd Edition, but it can be used by third-party applications already in S60 2nd Edition,Feature Pack 3 through these APIs.

4.8.2 Browser Control API (2nd Edition FP3)

A Browser Control is a plug-in browser that you embed into an application to enableusers to view Web content from within that application. The host application can controlthe way the Browser Control displays the Web content, dialogs, softkeys, scroll bars,and so on.

The Browser Control API enables developers to do the following:

Display XHTML, HTML, WML, CSS, or scripted content inside an application.

Customize the Browser Control for your specific application. For example, you candraw scroll bars, design options menus, display notification messages, customizesoftkeys, and change the display size of a Web page.

4.8.3 Browser Plug-in API (2nd Edition FP2)

This is a C++ API that can be used to create plug-ins for the browser. Additional plug-ins are needed for handling additional content types in the browser. Users can installbrowser plug-ins during normal device usage.

4.9 Messaging

Messaging covers aspects such as SMS, MMS, e-mail, IM, and Presence. See also chapterMessaging features written from the content/service developer's point of view.




28/50

NEW

4.9.1 New Message Notification API (3rd Edition)

The New Message Notification API is used by Messaging Server-compatible third-partye-mail plug-ins to get a notification to the user about new e-mail messages.

4.9.2 IM API (3rd Edition)

The IM (Instant Messaging) API is an interface for sending and receiving instantmessages. The API is intended for user applications that need this kind of functionality,for example, games.

From the functionality point of view the API can be divided as follows:

Connection management - connecting to the protocol stack and receiving connectionchange notifications

IM handling - sending and receiving instant messages and related sending errors,for example, invalid user IDs.

The Instant Messaging API is an ECom API. API instances are received through theECom framework. If the API is not available, the Ecom framework returns an error and

the application must act accordingly.

Both the mobile device and the network must support OMA IMPS v1.2 to be able to usethe Instant Messaging API.

4.9.3 IM Application Launch API (3rd Edition)

The IM Application Launch API provides the framework for the user application to launchthe application if an instant message addressed to the application arrives and theapplication is not running. It is only possible when there is already an existing IM sessionto the remote server created by some other application, such as the default ChatApplication.

This enables writing, for example, game applications using IM as the data transferprotocol and automatic startup of the related game application in case the game startinitialization message arrives. This API can be used together with the IM API.

The API provides an interface for starting the application and canceling the start. Theuser shall implement the interface functions. The correct implementation, that is, theone corresponding to the application ID received with the instant message, is found byusing the ECom framework. Because this is an ECom API, the application mustimplement it as an ECom plug-in.

REMOVED

4.9.4 Presence API (3rd Edition)

The Presence (Open) API (introduced in S60 2nd Edition, FP1) has been removedbecause the related Presence UI component has been removed from S60 3rd Edition.

4.10 PIM

NEW

4.10.1 Calendar Interim API (3rd Edition, Symbian OS v9)

The Calendar Interim API is the new interface to the Agenda subsystem. It replaces allthe previous Agenda, AgnVersit, and Versit APIs. It provides functionality to manipulateagenda data files and to store, retrieve, import, and export calendar events and To-Dolist items.




29/50

4.10.2 Local time and daylight saving support (2nd Edition FP3, Symbian OS v8.1)

Previously there have been some shortcomings in specifying and handling of local timezones and conversion of times as the associated time zone changes. These are nowaddressed in Symbian OS v8.1. First, conversion services are provided between UTCand local time (including allowance for Daylight Saving Time) through a new classcalled CTimeZoneConverter . Secondly, a database is provided which facilitates

association of time zone information with a unique ID (used by the time zone converter)and a name displayable in plain text. This is provided through a new class called

CTimeZoneLocations . Time zone is supported by the S60 platform's own clock and

calendar applications from 3rd Edition onwards, but the APIs provided by Symbian OSv8.1 should be available for third-party developers already in S60 2nd Edition FeaturePack 3.

Note: Time zone is supported by the S60 platform's own clock and calendar applicationsfrom 3rd Edition onwards, but the APIs provided by Symbian OS v8.1 should beavailable for third-party developers already in S60 2nd Edition, Feature Pack 3.

REMOVED

4.10.3 Agenda Model API (3rd Edition, Symbian OS v9)

The Calendar Interim API (see section Calendar Interim API) has replaced all theprevious Agenda, AgnVersit, and Versit APIs.

4.10.4 Calendar Conversion API (3rd Edition, Symbian OS v9)

The Calendar Conversion API has been removed from S60 3rd Edition.

4.10.5 World Server API (3rd Edition, Symbian OS v9)

The World Server API has been replaced with the Time Zone Localizer API.




30/50

5 Java MIDP

Figure 4: Java MIDP 2.0 and additional APIs in S60 3rd Edition, Feature Pack 1

5.1 Scalable 2D Vector Graphics API for Java ME, JSR-226 (3rd Edition FP1)

S60 3rd Edition Feature Pack 1 introduces Scalable 2D Vector Graphics API for Java ME. Itenables the use of 2-D vector graphics in a wide range of applications. The main features aremap visualization, scalable icons and other advanced graphics capabilities. The API can beused for:

2D vector image loading and rendering

Building and editing SVG content

Creating SVG elements

5.2 Advanced Multimedia Supplements, JSR-234 (3rd Edition FP1)

S60 3rd Edition Feature Pack 1 introduces 3D audio and stereo widening features specified inJSR-234, Advanced Multimedia Supplements. Advanced Multimedia Supplements enablessupport for gaming features such as positioning the sound sources i

s60 2nd 3rd ed differences in features v1 5 en

Documents