 | |
|---|---|
| Company / developer | Nokia |
| Programmed in | C++[1] |
| OS family | Embedded operating systems |
| Working state | Current |
| Source model | open source |
| Latest stable release | Symbian^3 platform / Q4 2010 |
| Latest unstable release | none as yet (Symbian^4 cancelled) / none as yet (update first half of 2011) |
| Marketing target | smartphones |
| Supported platforms | ARM, x86 [2] |
| Kernel type | Microkernel |
| Default user interface | Currently based on S60 platform, later to use Qt |
| License | EPL |
| Official website | symbian.nokia.com |
Symbian is an open source operating system (OS) and software platform designed for smartphones and maintained by Nokia. The Symbian platform is the successor to Symbian OS and Nokia Series 60; unlike Symbian OS, which required an additional user interface system, Symbian includes a user interface component based on S60 5th Edition. The latest version, Symbian^3, was officially released in Q4 2010, first used in the Nokia N8.
Symbian OS was originally developed by Symbian Ltd.[3] It is a descendant of Psion's EPOC and runs exclusively on ARM processors, although an unreleased x86 port existed.
Devices based on Symbian accounted for 43.5% of worldwide smartphone sales in 2010 Q2.[4] Some estimates indicate that the cumulative number of mobile devices shipped with the Symbian OS up to the end of Q2 2010 is 385 million.[5]
History
The Symbian platform was created by merging and integrating software assets contributed by Nokia, NTT DoCoMo, Sony Ericsson and Symbian Ltd., including Symbian OS assets at its core, the S60 platform, and parts of the UIQ and MOAP(S) user interfaces.
In December 2008, Nokia bought Symbian Ltd., the company behind Symbian OS; as a result, Nokia has become the major contributor to Symbian's code, as it now had the development resources for both the Symbian OS core and the user interface. Since then, Nokia has been maintaining their own code repository for the platform development, regularly releasing their development to the public repository.[6]
Symbian was intended to be developed by a community led by the Symbian Foundation,[7] which was first announced in June 2008 and which officially launched in April 2009. Its objective was to publish the source code for the entire Symbian platform under the OSI- and FSF-approved Eclipse Public License (EPL). The code was published under EPL on 4 February 2010; Symbian Foundation reported this event to be the largest codebase transitioned to Open Source in history .[8] [9]
However, some important components within Symbian OS were licensed from third parties, which prevented the foundation from publishing the full source under EPL immediately; instead much of the source was published under a more restrictive Symbian Foundation License (SFL) and access to the full source code was limited to member companies only, although membership was open to any organisation.[10]
In November 2010, the Symbian Foundation announced that due to a lack of support from funding members, it would transition to a licensing-only organisation; Nokia announced that it will take over the stewardship of the Symbian platform. Symbian Foundation will remain as the trademark holder and licensing entity and will only have non-executive directors involved.
Version history
Symbian releases are styled Symbian^1, Symbian^2 etc. (vocalised as "Symbian one", "Symbian two").
Symbian^1, as the first release, forms the basis for the platform. It incorporates Symbian OS and S60 5th Edition (which is built on Symbian OS 9.4) and thus it was not made available as open source.[11]
Symbian^2 was the first royalty-free version of Symbian.[12] While portions of Symbian^2 are EPL licensed, most of the source code is under the proprietary SFL license and available only to members of the Symbian Foundation. On June 1, 2010, a number of Japanese companies including DoCoMo and Sharp announced smartphones using Symbian^2.[13]
Symbian^3 was announced on 15 February 2010.[14] It was designed to be a more ‘next generation’ smartphone platform.[15] The Symbian^3 release introduced new features such as a new 2D and 3D graphics architecture, UI improvements, and support for external displays through HDMI.[16][17] It has single tap menus and up to three customizable homescreens. The Symbian^3 SDK was released September 2010.[18]
Four phones with the open source Symbian^3 have been released, the Nokia N8, Nokia C6-01, Nokia E7-00 and Nokia C7-00.[19]
Symbian^4 was expected to be released in the first half of 2011. However, Nokia announced in October 2010 that Symbian^4 will not ship as a separate release. Instead, improvements to Symbian will be delivered as software updates to all current Symbian^3 devices.[20]
Features
User interface
Symbian has had a native graphics toolkit since its inception, known as AVKON (formerly known as Series 60). S60 was designed to be manipulated by a keyboard-like interface metaphor, such as the ~15-key augmented telephone keypad, or the mini-QWERTY keyboards. AVKON-based software is binary-compatible with Symbian versions up to and including Symbian^3.
Symbian^3 includes the Qt framework, which is now the recommended user interface toolkit for new applications. Qt can also be installed on older Symbian devices.
Symbian^4 was planned to introduce a new GUI library framework specifically designed for a touch-based interface, known as "UI Extensions for Mobile" or UIEMO (internal project name "Orbit"), which was built on top of Qt; a preview was released in January 2010, however in October 2010 Nokia announced that Orbit/UIEMO has been cancelled.
Nokia currently recommends that developers use Qt Quick with QML, the new high-level GUI and scripting framework for creating visually rich touchscreen interfaces that allows development for both Symbian and MeeGo; it will be delivered to existing Symbian^3 devices as a Qt update. As more applications will gradually feature a user interface reworked in Qt, the legacy S60 framework (AVKON) will be deprecated and no longer included with new devices at some point, thus breaking binary compatibility with older S60 applications.[20][21]
Browser
Symbian^3 and earlier have a native WebKit based browser; indeed, Symbian was the first mobile platform to make use of WebKit (in June 2005).[22]
Nokia plans to introduce a new Qt-based browser as a free update for Symbian^3 devices.
Application development
From 2010, Symbian switched to using standard C++ with Qt as the SDK, which can be used with either Qt Creator or Carbide. Qt supports the older Symbian S60 3rd and 5th editions, as well as the new Symbian platform. It also supports Maemo and MeeGo, Windows, Linux and Mac OS X.[23][24]
Alternative application development can be done with using Python (see Python for S60), Adobe Flash or Java ME.
Symbian OS previously used a Symbian specific C++ version along with Carbide.c++ IDE as the native application development environment
Web Runtime (WRT) is a portable application framework that allows the creation of widgets on the S60 Platform; it is an extension to the S60 Webkit based browser that allows to launch multiple instances of the browser as separate JavaScript applications.[25][26]
Architecture
Technology domains and packages
Symbian's design is subdivided into technology domains,[27] each of which comprises a number of software packages.[28] Each technology domain has its own roadmap, and the Symbian Foundation has a team of technology managers who manage these technology domain roadmaps.
Every package is allocated to exactly one technology domain, based on the general functional area to which the package contributes and by which it may be influenced. By grouping related packages by themes, the Symbian Foundation hopes to encourage a strong community to form around them and to generate discussion and review.
The Symbian System Model[29] illustrates the scope of each of the technology domains across the platform packages.
Packages are owned and maintained by a package owner, a named individual from an organization member of the Symbian Foundation, who accepts code contributions from the wider Symbian community and is responsible for package.
Symbian kernel
The Symbian kernel (EKA2) supports sufficiently-fast real-time response 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.[30] Symbian has a microkernel architecture that contains the basic minimum functionality for maximum robustness, availability and responsiveness. It contains a scheduler, memory management and device drivers; with networking, telephony and filesystem support services in the OS Services Layer or the Base Services Layer. The inclusion of device drivers means the kernel is not a true microkernel. The EKA2 real-time kernel, which has been termed a nanokernel, contains only the most basic primitives and requires an extended kernel to implement any other abstractions.
Design
Symbian features pre-emptive multitasking and memory protection, like other operating systems (especially those created for use on desktop computers). EPOC's approach to multitasking was inspired by VMS and is based on asynchronous server-based events.
Symbian OS was created with three systems design principles in mind:
- the integrity and security of user data is paramount,
- user time must not be wasted, and
- all resources are scarce.
To best follow these principles, Symbian uses a microkernel, has a request-and-callback approach to services, and maintains separation between user interface and engine. The OS is optimised for low-power battery-based devices and for ROM-based systems (e.g. features like XIP and re-entrancy in shared libraries). Applications, and the OS itself, follow an object-oriented design: Model-view-controller (MVC).
Later OS iterations diluted this approach in response to market demands, notably with the introduction of a real-time kernel and a platform security model in versions 8 and 9.
There is a strong emphasis on conserving resources which is exemplified by Symbian-specific programming idioms like descriptor [disambiguation needed]s and a cleanup stack. There are similar techniques for conserving disk space (though the disks on Symbian devices are usually flash memory). Furthermore, all Symbian programming is event-based, and the CPU is switched into a low power mode when applications are not directly dealing with an event. This is achieved through a programming idiom called active objects. Similarly the Symbian approach to threads and processes is driven by reducing overheads.
Operating system
The All over Model contains the following layers, from top to bottom:
- Application Services Layer
- OS Services Layer
- generic OS services
- communications services
- multimedia and graphics services
- connectivity services
- Base Services Layer
- Kernel Services & Hardware Interface Layer
The Base Services Layer is the lowest level reachable by user-side operations; it includes the File Server and User Library, a Plug-In Framework which manages all plug-ins, Store, Central Repository, DBMS and cryptographic services. It also includes the Text Window Server and the Text Shell: the two basic services from which a completely functional port can be created without the need for any higher layer services.
Symbian has a microkernel architecture, which means that the minimum necessary is within the kernel to maximise robustness, availability and responsiveness. It contains a scheduler, memory management and device drivers, but other services like networking, telephony and filesystem support are placed in the OS Services Layer or the Base Services Layer. The inclusion of device drivers means the kernel is not a true microkernel. The EKA2 real-time kernel, which has been termed a nanokernel, contains only the most basic primitives and requires an extended kernel to implement any other abstractions.
Symbian is designed to emphasise compatibility with other devices, especially removable media file systems. Early development of EPOC led to adopting FAT as the internal file system, and this remains, but an object-oriented persistence model was placed over the underlying FAT to provide a POSIX-style interface and a streaming model. The internal data formats rely on using the same APIs that create the data to run all file manipulations. This has resulted in data-dependence and associated difficulties with changes and data migration.
There is a large networking and communication subsystem, which has three main servers called: 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 to implement various networking protocol schemes. The subsystem also contains code that supports short-range communication links, such as Bluetooth, IrDA and USB.
There is also a large volume of user interface (UI) Code. Only the base classes and substructure were contained in Symbian OS, while most of the actual user interfaces were maintained by third parties. This is no longer the case. The three major UIs — S60, UIQ and MOAP — were contributed to Symbian in 2009. Symbian also contains graphics, text layout and font rendering libraries.
All native Symbian C++ applications are built up from three framework classes defined by the application architecture: an application class, a document class and an application user interface class. These classes create the fundamental application behaviour. The remaining required functions, the application view, data model and data interface, are created independently and interact solely through their APIs with the other classes.
Many other things do not yet fit into this model — for example, SyncML, Java ME providing another set of APIs on top of most of the OS and multimedia. Many of these 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 it means that phone vendors needed to do a great deal of integration work to make a Symbian OS phone.
Symbian includes a reference user-interface called "TechView". It provides a basis for starting customisation and is the environment in which much Symbian test and example code runs. It is very similar to the user interface from the Psion Series 5 personal organiser and is not used for any production phone user interface.
Devices and feature comparison
On 16 November 2006, the 100 millionth smartphone running the OS was shipped.[31] As of 21 July 2009, more than 250 million devices running Symbian OS had been shipped.[32]
- The Nokia S60 interface is used in various phones, the first being the Nokia 7650. The Nokia N-Gage and Nokia N-Gage QD gaming/smartphone combos are also S60 platform devices. It was also used on other manufacturers' phones such as the Siemens SX1 and Samsung SGH-Z600. Recently, more advanced devices using S60 include the Nokia 6xxx, the Nseries (except Nokia N8xx and N9xx), the Eseries and some models of the Nokia XpressMusic mobiles.
- Fujitsu, Mitsubishi, Sony Ericsson and Sharp developed phones for NTT DoCoMo in Japan, using an interface developed specifically for DoCoMo's FOMA "Freedom of Mobile Access" network brand. This UI platform is called MOAP "Mobile Oriented Applications Platform" and is based on the UI from earlier Fujitsu FOMA models. The user cannot install new C++ applications.
User interfaces that run on or are based on Symbian OS include:
Versions that are actively marketed as of January 2011 are Symbian^3/Symbian^4, Symbian^2, Symbian^1 (Series 60 5th edition), and Series 60 3rd edition Feature Pack 2. For features of older versions see history of Symbian. Note that the operating system supporting a certain feature does not imply that all devices running on it have that feature available, especially if it involves expensive hardware, such as HDMI output.
| Feature? | Symbian^3/Symbian^4 | Symbian^2 | Symbian^1 (Series 60 5th edition) | Series 60 3rd edition Feature Pack 2 |
| Year released | 2010 | 2009 | ||
| Company | Symbian Foundation | Symbian Foundation | Symbian Foundation | |
| Symbian OS version | 9.5 | 9.4 | 9.3 | |
| Series 60 version | 5.2[33] | 5th edition | 3rd edition feature pack 2 | |
| Supports touch input? | Yes | Yes | No | |
| Supports multi touch input? | Yes | No | No | |
| Number of customizable home screens? | Three | One | ||
| Supported Wifi versions? | B, G, N | B, G | ||
| Supports USB on the go? | Yes | No | No | |
| Supports DVB-H? | Yes with an extra headset[34] | |||
| Supports short range FM transmitter? | Yes | Yes | Yes | |
| Supports FM radio? | Yes | Yes | Yes | |
| Feature? | Symbian^3/Symbian^4 | Symbian^2 | Symbian^1 (Series 60 5th edition) | Series 60 3rd edition Feature Pack 2 |
| Supports Adobe Flash? | Yes, Flash Lite version 4.0 | Yes, Flash Lite version ? | Yes, Flash Lite version ? | |
| Supports Microsoft Silverlight? | Yes[35] | |||
| Supports OpenGL ES? | Yes, version 2.0 | |||
| Supports SQLite? | Yes | Yes | Yes[36] | |
| Supported CPU Architecture | ARM | |||
| Programmed in | C++ | |||
| License | Eclipse Public License | |||
| Public issues list | Not anymore | |||
| Package manager | see .sis | |||
| Non english languages support | Yes | Yes | ||
| Underlining spell checker | ? | |||
| Keeps state on shutdown or crash | ? | |||
| Internal Search | Yes | Yes | ||
| Proxy server | Yes | |||
| On-device encryption | ? | |||
| Supports cut, copy, and paste? | Yes | Yes | ||
| undo | ? | |||
| Default web Browser for S60 (webkit engine) | version 7.2 (engine version 525)[37] | |||
| 3rd Party Application Store | Ovi store | Ovi store | Ovi store | |
| Email Sync protocols supported | POP3, IMAP | POP3, IMAP | POP3, IMAP | |
| Feature | Symbian^3/Symbian^4 | Symbian^2 | Symbian^1 (Series 60 5th edition) | Series 60 3rd edition feature pack 2 |
| Push Notifications | Yes | |||
| Voice Recognition | Yes | Yes | ||
| Tethering | USB, Bluetooth, Mobile Wi-Fi Hotspot (with 3rd party software | USB, Bluetooth, Mobile Wi-Fi Hotspot (with 3rd party software | ||
| Text/Document Support | Microsoft Office Mobile, PDF,djvu | Microsoft Office Mobile, PDF | ||
| Audio Playback | All | All | ||
| Video Playback | H.263, H.264, WMV, MPEG4, MPEG4@ HD 720p 30fps, MKV, DivX, XviD | |||
| Turn-by-turn GPS | 3rd Party Software, free global Nokia Ovi Maps (works offline) | 3rd Party Software, free global Nokia Ovi Maps (works offline) | 3rd Party Software, free global Nokia Ovi Maps (works offline) | |
| Video out | Nokia AV Out (PAL/NTSC), HDMI-out | Nokia AV Out (PAL/NTSC) | ||
| Multitasking | Yes | Yes | Yes | |
| Desktop interactive widgets | Yes | Yes | ||
| Integrated Hardware keyboard | Yes | Yes | ||
| Bluetooth keyboard | Yes | Yes | ||
| Videoconference front video camera | Yes | Yes | Yes | |
| Can share images via Bluetooth with all mobile? | Yes | Yes | Yes | |
| Skype (3rd party application) | Yes[38] | Yes[38] | Yes[38] | |
| Facebook IM chat | Yes | Yes | ||
| ssh | ? | Yes | ||
| OpenVPN | Yes(3rd Party Software) | |||
| Remote Frame Buffer | ? | |||
| Screenshot | Yes, 3rd party application.[39] | Yes, 3rd party application.[39] | ||
| GPU Accelerated GUI | Yes | |||
| Official SDK platform(s) | Windows/Multiplatform (preferred is Qt) , Carbide.c++, Java ME, Web Runtime (WRT), Flash lite, Python for Symbian | |||
| Feature | Symbian^3/Symbian^4 | Symbian^2 | Symbian^1 (Series 60 5th edition) | Series 60 3rd edition feature pack 2 |
| First device | Nokia N8 | Nokia 5800 | ? | |
| Devices | Nokia N8, Nokia C6-01, Nokia C7-00, Nokia E7-00 | NTT DOCOMO F-06B (manufactured by Fujitsu),[40] NTT DOCOMO F-07B (manufactured by Fujitsu),[40] NTT DOCOMO F-08B (manufactured by Fujitsu),[40] NTT DOCOMO SH-07B (manufactured by Sharp),[40] NTT DOCOMO F-10B,[41] NTT DOCOMO Raku-Raku PHONE 7,[41] NTT DOCOMO F-01C (manufactured by Fujitsu),[42] NTT DOCOMO F-02C (manufactured by Fujitsu),[42] NTT DOCOMO F-03C (manufactured by Fujitsu),[42] NTT DOCOMO F-04C (manufactured by Fujitsu),[42] NTT DOCOMO F-05C (manufactured by Fujitsu),[42] NTT DOCOMO SH-01C (manufactured by Sharp),[42] NTT DOCOMO SH-02C (manufactured by Sharp),[42] NTT DOCOMO SH-04C (manufactured by Sharp),[42] NTT DOCOMO SH-05C (manufactured by Sharp),[42] NTT DOCOMO SH-06C (manufactured by Sharp),[42] NTT DOCOMO TOUCH WOOD SH-08C (manufactured by Sharp)[42] | Nokia 5228, Nokia 5230, Nokia 5233, Nokia 5235 , Nokia 5250, Nokia 5530 XpressMusic, Nokia 5800 XpressMusic, Nokia 5800 Navigation Edition, Nokia C5-03, Nokia C6-00, Nokia N97, Nokia N97 mini, Nokia X6 , Samsung i8910 Omnia HD,[43]Sony Ericsson Satio, Sony Ericsson Vivaz, Sony Ericsson Vivaz Pro | Nokia 5320 XpressMusic, Nokia 5630 XpressMusic, Nokia 5730 XpressMusic, Nokia 6210 Navigator, Nokia 6220 Classic, Nokia 6650 fold, Nokia 6710 Navigator, Nokia 6720 Classic, Nokia 6730 Classic, Nokia 6760 Slide, Nokia 6790 Surge, Nokia C5-00, Nokia E5-00, Nokia E52, Nokia E55, Nokia E71, Nokia E72, Nokia E75, Nokia N78, Nokia N79, Nokia N85, Nokia N86 8MP, Nokia N96, Nokia X5, Samsung GT-i8510 (INNOV8), Samsung GT-I7110, Samsung SGH-L870, Nokia C5-00 |
| Feature | Symbian^3/Symbian^4 | Symbian^2 | Symbian^1 (Series 60 5th edition) | Series 60 3rd edition feature pack 2 |
Application development
Qt
As of 2010, the SDK for Symbian is standard C++, using Qt. It can be used with either Qt Creator, or Carbide (the older IDE previously used for Symbian development).[23][44] A phone simulator allows testing of Qt apps. Apps compiled for the simulator are compiled to native code for the development platform, rather than having to be emulated.[45]
Symbian C++
It is also possible to develop using Symbian C++, although it is not a standard implementation. Prior to the release of the Qt SDK, this was the standard development environment. There were multiple platforms based upon Symbian OS that provided SDKs for application developers wishing to target Symbian OS devices – the main ones being UIQ and S60. Individual phone products, or families, often had 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 and the Symbian platform use a new ABI and required a different compiler – a choice of compilers is available including a newer version of GCC (see external links below).
Unfortunately, Symbian C++ programming has a steep learning curve, as Symbian C++ requires the use of special techniques such as descriptors, active objects and the cleanup stack. This can make even relatively simple programs harder to implement than in other environments. Moreover, it was questionable whether these techniques, such as the memory management paradigm, were actually beneficial. It is possible that the techniques, developed for the much more restricted mobile hardware of the 1990s, simply caused unnecessary complexity in source code because programmers are required to concentrate on low-level routines instead of more application-specific features. These issues however are no longer the case when using standard C++, with the Qt SDK.
Symbian C++ programming is commonly done with an IDE. For earlier versions of Symbian OS, the commercial IDE CodeWarrior for Symbian OS was favoured. The CodeWarrior tools were replaced during 2006 by Carbide.c++, an Eclipse-based IDE developed by Nokia. Carbide.c++ is offered in four different versions: Express, Developer, Professional, and OEM, with increasing levels of capability. Fully featured software can be created and released with the Express edition, which is free. Features such as UI design, crash debugging etc. are available in the other, charged-for, editions. Microsoft Visual Studio 2003 and 2005 are also supported through the Carbide.vs plugin.
Other languages
Symbian devices can also be programmed using Python, Java ME, Flash Lite, Ruby, .NET, Web Runtime (WRT) Widgets and Standard C/C++.[46]
In the past, Visual Basic, VB.NET, and C# development for Symbian were possible through AppForge Crossfire, a plugin for Microsoft Visual Studio. On 13 March 2007 AppForge ceased operations; Oracle purchased the intellectual property, but announced that they did not plan to sell or provide support for former AppForge products. Net60, a .NET compact framework for Symbian, which is developed by redFIVElabs, is sold as a commercial product. With Net60, VB.NET and C# (and other) source code is compiled into an intermediate language (IL) which is executed within the Symbian OS using a just-in-time compiler. (As of 18/1/10 RedFiveLabs has ceased development of Net60 with this announcement on their landing page: ”At this stage we are pursuing some options to sell the IP so that Net60 may continue to have a future”.)
There is 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 was available.[47]
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 S60i phones can also run Python scripts when the interpreter Python for S60 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.
Deployment
Once developed, Symbian 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, Bluetooth or on a memory card. An alternative is to partner with a phone manufacturer and have the software included on the phone itself. Applications must be Symbian Signed for Symbian OS 9.x in order to make use of certain capabilities (system capabilities, restricted capabilities and device manufacturer capabilities).[48] Applications can now be signed for free.[49]
Competition and alternatives
Nokia plans to start using MeeGo that succeeded its Linux based Maemo in 2011. Both of them share with Symbian the Qt (framework) as their official preferred application development tool. There have been reports that Nokia will use MeeGo and not Symbian anymore for high-end smartphones.[50]Nevertheless, as of January 2011 Nokia has released only the Nokia N900 non-Symbian smartphone in last few years and has not announced any new non-Symbian smartphones.
In the number of "smart mobile device" sales, Symbian devices are the market leaders. Statistics published for the second quarter of 2010 showed that Symbian devices comprised a 41.2% share of smart mobile devices sold, with RIM having 18.2%, Android having 17.2%, and Apple having 15.1% (through iPhone OS) [51]
Previous reports on device shipments as published in February 2010 showed that the Symbian devices comprised a 47.2% share of the smart mobile devices shipped in 2009, with RIM having 20.8%, Apple having 15.1% (through iPhone OS), Microsoft having 8.8% (through Windows CE and Windows Mobile) and Android having 4.7%.[52] Other competitors include webOS, Qualcomm's BREW, SavaJe, Linux and MontaVista Software.
Although the share of the global smartphone market dropped from 52.4% in 2008 to 47.2% in 2009, the shipment volume of Symbian devices grew 4.8%, from 74.9 million units to 78.5 million units.[52] From Q2 2009 to Q2 2010, the shipment volume of Symbian devices grew 41.5%, by 8.0 million units, from 19,178,910 units to 27,129,340; compared with an increase of 9.6 million units for Android, but 3.3 million units for RIM and 3.2 million units for Apple.[53]
Symbian has lost market share in recent years; it dropped from 72.8% of the market in Q3 2006 to 36% in Q3 2010.[citation needed] In 2009-2010, Motorola, Samsung, LG, and Sony-Ericsson announced their withdrawal from the platform, leaving only Nokia and several small Japanese-only vendors.[citation needed] By the end of 2010, Samsung will totally leave Symbian including the support and service and also remove all content relating to Symbian from its website, whereas Sony Ericsson will not introduce new mobile phone with Symbian.[54][unreliable source?]
Criticism
In November 2010, Smartphone blog All About Symbian criticised the performance of Symbian's default web browser and recommended the alternative browser Opera Mobile.[55]
Nokia's Senior Vice President Jo Harlow promised an updated browser in the first quarter of 2011.[56] Nokia denied any plans for switching to competitive platforms such as Android operating system. Industry analysts expect Symbian's market share to decline, although it would still continue to dominate worldwide as the number two platform, after Android.[57] Nokia's new Symbian^3 devices have also been received well by the market and the reviewers. The announcement to switch to "continuous development" model of iPhone OS and Android OS, where existing devices will be supported with new OS updates during their lifetime, has been welcomed by the community.[citation needed]
[edit] Malware
Main article: Mobile virus
Symbian OS was 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, with a view that the average mobile phone user shouldn't have to worry about security, Symbian OS 9.x adopted a UNIX-style capability model (permissions per process, not per object). Installed software is theoretically unable to do damaging things (such as costing the user money by sending network data) without being digitally signed – thus making it traceable. Commercial developers who can afford the cost can apply to have their software signed via the Symbian Signed program. Developers also have the option of self-signing their programs. However, the set of available features does not include access to Bluetooth, IrDA, GSM CellID, voice calls, GPS and few others. Some operators have opted to disable all certificates other than the Symbian Signed certificates.
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 S60 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.
- Fontal.A is an 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 stick on the reboot, and cannot be used without disinfection – that is, the use of the reformat key combination which causes the phone to lose all data. Being a trojan, Frontal 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.
A new form of malware threat to Symbian OS in form of Cooked Firmware [58][59] was recently demonstrated at the International Malware Conference, MalCon [60] (December 2010) by an Indian Hacker Atul Alex.
Bypassing Platform Security
Symbian OS 9.x devices can be hacked to remove the platform security introduced in OS 9.1 onwards, allowing users to execute unsigned code.[61] This allows alteration of system files, and access to previously locked areas of the OS. The hack was criticised by Nokia for potentially increasing the threat posed by mobile viruses as unsigned code can be executed
0 comments:
Post a Comment