Welcome

Thursday, December 07, 2006

Symbian OS

Symbian OS

From Wikipedia, the free encyclopedia

Jump to: navigation, search
Symbian OS
Image:Symbian logo.png
Website: http://www.symbian.com
Company/
developer:		 Symbian Ltd.
Source model: Shared
Supported platforms: ARM, x86
Kernel type: Real time
Default user interface: Series 60, UIQ
Working state: Current


Symbian OS is an operating system, designed for mobile devices, with associated libraries, user interface frameworks and reference implementations of common tools, produced by Symbian Ltd. It is a descendant of Psion's EPOC and runs exclusively on ARM processors.

Symbian is currently owned by Ericsson (15.6%), Nokia (47.9%), Panasonic (10.5%), Samsung (4.5%), Siemens AG (8.4%), and Sony Ericsson (13.1%). Whilst BenQ has acquired the mobile phone subsidiary of Siemens AG the Siemens AG stake in Symbian does not automatically pass to BenQ - this will need the approval of the Symbian Supervisory Board.

Contents

[hide]

[edit] Design

Symbian OS, with its roots in Psion Software's EPOC is structured like many desktop operating systems, with pre-emptive multitasking, multithreading, and memory protection.

Symbian OS's major advantage is the fact that it was built for handheld devices, with limited resources, that may be running for months or years. There is a strong emphasis on conserving memory, using Symbian-specific programming idioms such as descriptors and a cleanup stack. Together with other techniques, these keep memory usage low and memory leaks rare. There are similar techniques for conserving disk space (though the disks on Symbian devices are usually flash memory). Furthermore, all Symbian OS programming is event-based, and the CPU is switched off when applications are not directly dealing with an event. This is achieved through a programming idiom called active objects. Correct use of these techniques helps ensure longer battery life.

All of this makes Symbian OS's flavour of C++[citation needed] very specialised, with a gradual learning curve[citation needed]. However, many Symbian OS devices can also be programmed in OPL, Python, Visual Basic, Simkin, and Perl - together with the Java ME and PersonalJava flavours of Java.

There are a number of smartphone user interface platforms based on Symbian OS, including open platforms UIQ, Nokia's Series 60, Series 80 and Series 90 and closed platforms such as that developed for NTT DoCoMo's FOMA handsets. This adaptability allows Symbian OS to be used on smartphones with a variety of form factors (e.g. clam-shell or "monoblock"/"candybar", keypad- or pen-driven).

[edit] Competition
The neutrality of this article is disputed.
Please see the discussion on the talk page.

Symbian OS is often seen as competing with other mobile operating systems, such as Windows Mobile, Palm OS, and Linux. It primarily competes with the embedded operating systems[citation needed] used on lower-end phones, such as NOS and OSE, which tend to be maintained by the phone companies themselves. SymbianOS, like its smartphone competition, has long been encumbered by the need for two processor cores in order that it can ensure separation between the mobile network and the user's applications. This means that SymbianOS phones have tended to be larger, heavier, more expensive and less power-efficient[citation needed] than featurephones with similar capabilities. Symbian OS' major advantage over the embedded operating systems used in featurephones is its modularity - there is runtime linking between dynamically linked shared libraries (DLLs, see dynamic linking) on the device, and an emphasis on plug-in architectures. This makes complex phones quicker to develop[citation needed], though this is sometimes offset by the complexity of Symbian OS C++ and the awkwardness of going to another company for an OS (instead of doing it in-house).

The advantages over other OS's such as Linux or Windows Mobile are more debatable. Phone vendors and network operators like the customisability of Symbian OS relative to Windows[citation needed]. This customisability, though, makes integrating a Symbian OS phone more difficult. It's possible that Linux goes too far in the other direction[citation needed], and is simply too hard to make a phone from at the moment (a fact that may change with Trolltech's introduction of the Greenphone). Symbian OS's ground-up design for mobile devices should make it more power-and memory-efficient[citation needed], as well as being flexible.

SymbianOS EKA2 also supports hard enough real-time operation that it is possible to build a single-core phone around it- that is, a phone in which a single processor core executes both the user applications and the signalling stack. This is not a feature that is available from Linux or Windows CE. This has allowed SymbianOS EKA2 phones to become smaller, cheaper and more power efficient.

Recently published statistics show that Symbian OS has a 67% share of the 'smart mobile device' market, with Microsoft having 15% and RIM having 6%. [1]

[edit] Structure

At its lowest level sit the base components of Symbian OS. This includes the kernel (EKA1 or EKA2 - see the 'History' section), along with the user library which allows user-side applications to request things of the kernel. Symbian OS has a microkernel architecture, which means that the minimum necessary is within the kernel. It contains a scheduler and memory management, but no networking or filesystem support. These things are provided by user-side servers. The base layer includes the file server, which provides a fairly DOS-like view of the filesystems on the device (each drive has a drive letter, and backslashes are used as the directory delimiter). Symbian OS supports various filesystem types including FAT32 and Symbian OS-specific NOR flash filing systems. The filesystem is generally not exposed to the user through the phone user interface.

Immediately above base are a selection of system libraries. These take all shapes and sizes, including for example character set conversion, a DBMS database, and resource file handling.

Further up, the software is not so readily arranged into a stack.

This article or section is not written in the formal tone expected of an encyclopedia article.
Please improve it or discuss changes on the talk page. See Wikipedia's guide to writing better articles for suggestions.

There is a large networking and communication subsystem, which has three main servers - ETEL (EPOC telephony), ESOCK (EPOC sockets) and C32 (responsible for serial communication). Each of these has a plug-in scheme. For example ESOCK allows different ".PRT" protocol modules, implementing different types of networking protocol scheme. There's lots of stuff relating to short-range communication links too, such as Bluetooth, IrDA and USB.

There's also a large amount of user interface code. Even though the user interfaces themselves are maintained by other parties, the base classes and substructure ("UIKON") for all UIs are present in Symbian OS, along with certain related servers (for example, a view server which controls transitions between different phone user interface screens). There's a lot of related graphics code too - such as a window server and a font and bitmap server.

An application architecture provides for standard application types, embedding, and file and data recognition. There is also a selection of application engines for popular smartphone applications such as calendars, address books, and task lists. A typical Symbian OS application is split up into an engine DLL and a graphical application - the application being a thin wrapper over the engine DLL. Symbian OS provides some of these engine DLLs.

There are, of course, many other things that don't yet fit into this model - for example, SyncML, Java ME providing another set of APIs on top of most of the OS and multimedia. Quite a few of these things are frameworks, and vendors are expected to supply plug-ins to these frameworks from third parties (for example, Helix player for multimedia codecs). This has the advantage that the APIs to such areas of functionality are the same on many phone models, and that vendors get a lot of flexibility, but means that phone vendors need to do a great deal of integration work to make a Symbian OS phone.

Symbian OS device manufacturers also get supplied with an example user interface layer called TechView. This is very similar to the user interface from a Psion Series 5 personal organiser, so isn't particularly similar to any given phone user interface, but provides a basis to start customisation. It is also the environment in which a lot of Symbian OS test code and example code runs.

[edit] History

In 1980, Psion was founded by David Potter.

EPOC16. Psion released several Series 3 devices from 1991 to 1998 which used the EPOC16 OS, also known as SIBO.

EPOC OS Releases 1–3. The Series 5 device, released in 1997, used the first iterations of the EPOC32 OS.

EPOC Release 4. Oregon Osaris and Geofox 1 were released using ER4.

In 1998, Symbian Ltd. was formed as a partnership between Ericsson, Nokia, Motorola and Psion, to explore the convergence between PDAs and mobile phones.

EPOC Release 5 a.k.a. Symbian OS v5. Psion Series 5mx, Series 7, Psion Revo, Psion Netbook, netPad, Ericsson MC218 were released in 1999 using ER5.

ER5u a.k.a. Symbian OS v5.1. u = Unicode. The first phone, the Ericsson R380 was released using ER5u in 2000. It was not an 'open' phone - software could not be installed. Notably, a number of never released Psion prototypes for next generation PDAs, including a Bluetooth Revo successor codenamed Conan were using ER5u.

Symbian OS v6.0 and v6.1. Sometimes called ER6. The first 'open' Symbian OS phone, the Nokia 9210, was released on 6.0.

Symbian OS v7.0 and v7.0s. First shipped in 2003. This is an important Symbian release which appeared with all contemporary user interfaces including UIQ (Sony Ericsson P800, P900, P910, Motorola A925, A1000), Series 80 (Nokia 9300, 9500), Series 90 (Nokia 7710), Series 60 (Nokia 6600, 7310) as well as several FOMA phones in Japan.

In 2004, Psion sold its stake in Symbian.

Also in 2004, the first worm for mobile phones using Symbian OS, Cabir, was developed, which used Bluetooth to spread itself to nearby phones. See Cabir and Symbian OS threats.

Symbian OS v8.0. First shipped in 2004, one of its advantages would have been a choice of two different kernels (EKA1 or EKA2). However, the EKA2 kernel version did not ship until SymbianOS v8.1b. The kernels behave more or less identically from user-side, but are internally very different. EKA1 was chosen by some manufacturers to maintain compatibility with old device drivers, whilst EKA2 offered advantages such as a hard real-time capability. v8.0b was deproductized in 2003.

Symbian OS v8.1. Basically a cleaned-up version of 8.0, this was available in 8.1a and 8.1b versions, with EKA1 and EKA2 kernels respectively. The 8.1b version, with EKA2's single-chip phone support but no additional security layer, was popular among Japanese phone companies desiring the realtime support but not allowing open application installation.

Symbian OS v9.0. This version was used for internal Symbian purposes only. It was deproductised in 2004. v9.0 marked the end of the road for EKA1. v8.1a is the final EKA1 version of SymbianOS.

Symbian OS has generally maintained reasonable binary compatibility. In theory the OS was BC from ER1-ER5, then from 6.0 to 8.1b. Substantial changes were needed for 9.0, related to tools and security, but this should be a one-off event. The move from requiring ARMv4 to requiring ARMv5 did not break backwards compatibility.

A Symbian developer proclaims that porting from Symbian 8.x to Symbian 9.x is a more daunting process than Symbian says. [2]

Symbian OS v9.1 released early 2005. It includes many new security related features, particularly a controversial platform security module facilitating mandatory code signing. Symbian argues that applications and content, and therefore a developers investment, are better protected than ever, however others contend that the requirement that every application be signed (and thus approved) violates the rights of the end-user, the owner of the phone, and limits the amount of free software available. The new ARM EABI binary model means developers need to retool and the security changes mean they may have to recode. S60 3rd Edition phones have Symbian OS 9.1. Sony Ericsson is shipping the M600i based on Symbian OS 9.1 and should ship the P990 in Q3 2006. The earlier versions had a fatal defect where the phone hangs temporarily after the owner sent hundreds of SMSes. However, on 13 September 2006, Nokia releases a small program to fix this defect[3].

Symbian OS v9.2 released Q1 2006. Support for Bluetooth 2.0 (was 1.2) and OMA Device Management 1.2 (was 1.1.2). S60 3rd Edition Feature Pack 1 phones have Symbian OS 9.2.

Symbian OS v9.3 released on 12 July 2006. Upgrades include native support for Wifi 802.11, HSDPA, Vietnamese language support.

On November 16, 2006, the 100 millionth smartphone running the OS was shipped. [4]

[edit] Open Source Software for Symbian 9.1

The following Open Source software has been rewritten for Symbian 9.1:

  • Game emulation:
    • ScummVM (Currently only a very early port is available)

[edit] Security and Malware

Symbian OS has been subject to a variety of viruses, the best known of which is Cabir. Usually these send themselves from phone to phone by Bluetooth. So far, none have taken advantage of any flaws in Symbian OS - instead, they have all asked the user whether they would like to install the software, with somewhat prominent warnings that it can't be trusted.

However, of course, the average mobile phone user shouldn't have to worry about such things, so Symbian OS 9 is adopting a capability model. Installed software will theoretically be unable to do damaging things (such as costing the user money by sending network data) without being digitally signed - thus making it traceable. Developers can apply to have their software signed via the Symbian Signed program. Developers also have the option of self-signing their programs.

Some other hostile programs are listed below, but all of them still require the input of the user to run.

  • Drever.A is a malicious SIS file trojan that attempts to disable the automatic startup from Simworks and Kaspersky Symbian Anti-Virus applications.
  • Locknut.B is a malicious SIS file trojan that pretends to be patch for Symbian Series 60 mobile phones. When installed, it drops a binary that will crash a critical system service component. This will prevent any application from being launched in the phone.
  • Mabir.A is basically Cabir with added MMS functionality. The two are written by the same author, and the code shares many similarities. It spreads using Bluetooth via the same routine as early variants of Cabir. As Mabir.A activates it will search for the first phone it finds, and starts sending copies of itself to that phone.
  • Frontal.A is a SIS file trojan that installs a corrupted file which causes the phone to fail at reboot. If the user tries to reboot the infected phone, it will be permanently stuck on the reboot, and cannot be used without disinfectation - that is, the use of the reformat key combination which causes the phone to lose all data. Being a trojan, Frontal.A cannot spread by itself - the most likely way for the user to get infected would be to acquire the file from untrusted sources, and then install it to the phone, inadvertently or otherwise.

[edit] Openness

A common question is whether Symbian OS is "open". It is not open in the sense of Open Source software - the source code is not publicly available. However, nearly all the source code is provided to Symbian OS phone manufacturers and many other partners. Moreover, the APIs are publicly documented and anyone can develop software for Symbian OS. This contrasts with traditional embedded phone operating systems, which typically cannot accept any aftermarket software with the exception of Java applications.

Symbian is also open in terms of the Open Standards it supports.

[edit] Devices that have used the Symbian OS

[edit] Developing on Symbian OS

There are multiple platforms, based upon Symbian OS, that provide an SDK for application developers wishing to target a Symbian OS device - the main ones being UIQ, Series 60, etc. Individual phone products, or families, often have SDKs or SDK extensions downloadable from the manufacturer's website too. The SDKs contain documentation, the header files and library files required to build Symbian OS software, and a Windows-based emulator ("WINS"). Up until Symbian OS version 8, the SDKs also included a version of the GCC compiler (a cross-compiler) required to build software to work on the device.

Symbian OS 9 uses a new ABI and so requires a new compiler - a choice of compilers is available including a new version of GCC (see external links below). In terms of SDKs, UIQ Technology now provides a simplified framework so that the single UIQ SDK forms the basis for developing on all UIQ 3 devices, such as the Sony Ericsson P990 and Sony Ericsson M600.

Symbian C++ programming is commonly done with a commercial IDE. For current versions of Symbian OS, CodeWarrior for Symbian OS is favoured. The CodeWarrior tools will be replaced during 2006 by Carbide.c++, an Eclipse-based IDE developed by Nokia. It is expected that Carbide.c++ will be offered in different versions: a free version may allow users to prototype software on the emulator for the first time in a free product.

Visual Basic, VB.NET, and C# development for Symbian can be accomplished through AppForge Crossfire, a plugin for Microsoft Visual Studio.

There's also a version of a Borland IDE for Symbian OS. Symbian OS development is also possible on Linux and Mac OS X using tools and techniques developed by the community, partly enabled by Symbian releasing the source code for key tools. A plugin that allows development of Symbian OS applications in Apple's Xcode IDE for Mac OS X is available. [6]

Once developed, Symbian OS applications need to find a route to customers' mobile phones. They are packaged in SIS files which may be installed over-the-air, via PC connect or in some cases via Bluetooth or memory cards. An alternative is to partner with a phone manufacturer to have the software included on the phone itself. The SIS file route will be a little more difficult from Symbian OS 9, because any application wishing to have any capabilities beyond the bare minimum must be signed via the Symbian Signed[7] program.

Java ME applications for Symbian OS are developed using standard techniques and tools such as the Sun Java Wireless Toolkit (formerly the J2ME Wireless Toolkit). They are packaged as JAR (and possibly JAD) files. Both CLDC and CDC applications can be created with NetBeans. Other tools include SuperWaba, which can be used to build Symbian 7.0 and 7.0s programs using Java.

Nokia Series 60 phones can also run python scripts when the interpeter is installed, with a custom made API that allows for Bluetooth support and such. There is also an interactive console to allow the user to write python scripts directly from the phone.

[edit] See also

[edit] Notes

  1. ^ http://www.canalys.com/pr/2006/r2006071.htm
  2. ^ Symbian developer reports on porting from 8.x to 9.x
  3. ^ Solution to Nokia Slow SMS / Hang Problem
  4. ^ http://www.thesmartpda.com/50226711/six_years_of_symbian_produces_100_models_and_100_million_shipments.php
  5. ^ Symbian series 60 phones
  6. ^ Tom Sutcliffe and Jason Barrie Morley Xcode Symbian support
  7. ^ Symbian Signed

[edit] Sources

[edit] External links

posted by ArunKanth A @ 8:28 AM 

0 Comments:

Post a Comment

<< Home