Eo malo c/p

UPDATE:- The new symbian OS also support direct memory link with the processer. What this means is that the controlers for the memory will be inside the die of the ARM architecture this allows speed and performance to improved as the processer has a open link with the memory...

Handsets differences:-
Nokia 3250:- This method is not installed in 3250 mainly due to buget..

N91:- The speed of Sustained Data Rate in its HDD is quite higher than normal MMC pro or miniSD cards at 4.3-7.2 (Mb/s)

N92:- Its memory system is totally different its more fleaxable with enhanced buffer system similar to N91 but way too complex and effective.

Now we can observe the passage from the second edition of the platform 60 to its third version, and that means not only a smooth improvement of characteristics of the operating system, but the change if its version, and as a result a partial incompatibility with programs developed for the previous models. The majority of old system programs can run on devices using platform 60 third edition, however they can't use all capabilities of the system provided by various API. Such programs are stretched for the screen's resolution, which grew to at least QVGA. And from esthetical point of view, their appearance really suffers a great deal. The majority of games and other applications using system capabilities of Series 60 Edition 2 won't work on new devices, and that is the pay for a grown functionality.

The third edition applies Symbian 9.1 as a version of operating system, the kernel of which is completely redeveloped. And it is run in real time - EKA2. That allows making applications, which are crucial to run time, for instance, VoIP.

Developers will find it interesting to know about a new compiler used and improvements regarding security capabilities. In particular, an idea of certified applications is being brought, which will have access to some APIs, and the company opened many of them (about 40 APIs are now available, which allows developing any type of application). We won't list all APIs here and will highlight only the most interesting ones. People uninterested in cobwebs of the operating system and applying only a user part of the interface can surely skip this paragraph and pass to the last part of the material.

New APIs and functions in 3rd Edition
Installation - despite the .SIS file extension is preserved, only SISX applications can be installed (that is an extended format of installation files).

New data keep model. By default applications can access memory of the device and folders marked as open for various operations. Others can be addressed corresponding with the certificates correlating with the program. This is the first time the Central Repository of data appears, all settings and application data are stored there. You can compare this with a Windows registry, they are similar. The repository keeps data permanent for all applications; all variables kept in RAM refer to Publish&Subscribe API (it was introduced in 2nd FP2, Symbian 8.0). And correspondingly APIs used for the same purposes (System Agent, Shared Data) were withdrawn.

Light API - allows control over the keypad and screen backlighting from applications.

Vibra API - expanded control over a vibracall, during games and application work. It replaces Vibra Control API. Also Vibra Settings API which allows change settings present.

HWRM Power State API - information about the battery level and current status. It allows creating a corresponding function in applications easily, for instance, in shell analogs widely available for Windows Mobile devices.

Profiles Engine Active Profile Settings API - contains data about an active profile (for example, sound level, and call type selected for voice calls or SMS alert).

Find Item API - allows marking out numbers, e-mail addresses and links in text.

Startup List Management API - is a capability for developers to add their applications to the list of programs automatically starting up with the device.

PtiEngine API - low-level access to text input functions, using predictive input. In perspective, that means that third-party applications support the same input methods that the original shipment applies.

Common Audio Enhancements API - defines an interface used by audio applications.

OMA DRM v2.0 - the passage to the second version of control over digital rights for content, brings strengthening of the control, fully compatible with the first version.

DRM Audio Player API - allows playing protected content in applications equipped with a DRM functionality, only files saved on the device can be played (no capability to play threads).

Exif API - represents information about the headings of JPEG files (time of creation, change, and reading).

MIDI client API - integrates work with MIDI into third party applications (Symbian version 8.0).

Audio Effects API - allows access to equalizer settings, selecting them, access to various sound effects, including Stereo Widening. Audio Effects Preset API is responsible for setting of effects and equalizer.

Network Status API - shows data about the current network condition.

Location API is a set of 7 various APIs which allows working with GPS-devices (both external receivers and integrated ones). Routes and anchor points are supported.

Scalable 2D Vector Graphics API (JSR-226) - view SVG-files, which is a 2D vector graphics, can be used in various applications, for instance, showing cartographic information.

New programs in a standard package
Flash Lite Viewer 1.1 - an application which allows viewing SWF files on a smartphone, preset. Can be available for some products based on FP3

by ajai_dev (i-phone forum)