Product Code Database
Example Keywords: slacks -apple $71
   » » Wiki: Symbian
Tag Wiki 'Symbian'.
Tag

Symbian is a discontinued mobile operating system (OS) and computing platform designed for . Symbian was originally developed as a closed-source OS for in 1998 by the Symbian Ltd. consortium. Symbian OS was a descendant of Psion's EPOC, and ran exclusively on processors, although an unreleased x86 port existed. Symbian was used by many major mobile phone brands, like , , , and above all by . It was also prevalent in Japan by brands including , Sharp and . As a pioneer that established the smartphone industry, it was the most popular smartphone OS on a worldwide average until the end of 2010 at a time when smartphones were in limited use, when it was overtaken by Android, as Google and its partners achieved wide adoption. It was notably not as popular in North America.

The Symbian OS platform is formed of two components: one being the -based operating system with its associated libraries, and the other being the (as /ref> The most prominent user interface was the S60 (formerly Series 60) platform built by Nokia, first released in 2002 and powering most Nokia Symbian devices. was a competing user interface mostly used by Motorola and Sony Ericsson that focused on -based devices, rather than a traditional keyboard interface from S60. Another interface was the (S) platform from carrier /ref> Applications of these different interfaces were not compatible with each other, despite each being built atop Symbian OS. Nokia became the largest shareholder of Symbian Ltd. in 2004 and purchased the entire company in 2008.http://www.dailytech.com/Nokia+Offers+to+Purchase+All+Symbian+Shares+for+410M/article12178.htm The non-profit Symbian Foundation was then created to make a successor to Symbian OS – seeking to unify the platform, S60 became the Foundation's favoured interface and UIQ stopped development. The -focused Symbian^1 (or S60 5th Edition) was created as a result in 2009. Symbian^2 (based on MOAP) was used by NTT DoCoMo, one of the members of the Foundation, for the Japanese market. Symbian^3 was released in 2010 as the successor to S60 5th Edition, by which time it became fully . Symbian^3 received the Anna and Belle updates in 2011. Nokia announces Symbian 'Anna' update for N8, E7, C7 and C6-01; first of a series of updates (video). Engadget. Retrieved 25 September 2011. Nokia announces Symbian Belle alongside three new devices. Engadget. Retrieved 25 September 2011.

Https://www.bbc.co.uk/news/technology-11713192< /ref>http://www.visionmobile.com/blog/2010/10/symbian-is-dead-long-live-symbian/ In February 2011, Nokia, by now the only remaining company still supporting Symbian outside Japan, announced that it would use 's Windows Phone 7 as its primary smartphone platform, while Symbian would be gradually wound down. Nokia's new strategy and structure, Symbian to be a "franchise platform", MeeGo still in long term plans RIP: Symbian. Engadget. Retrieved 25 September 2011. Two months later, Nokia moved the OS to closed licensing, only collaborating with the Japanese OEMshttp://www.digitaltrends.com/mobile/nokia-moves-symbian-to-closed-licensing/ and later outsourced Symbian development to .Epstein, Zach. (23 June 2011) Symbian is officially no longer Nokia's problem. Bgr.com. Retrieved 25 September 2011. Although support was promised until 2016, including two major planned updates, by 2012 Nokia had mostly abandoned development and most Symbian developers had already left Accenture,http://www.allaboutsymbian.com/features/item/20007_Cest_la_vie-Support_expectatio.php and in January 2014 Nokia stopped accepting new or changed Symbian software from developers. The Nokia 808 PureView in 2012 was officially the last Symbian smartphone from Nokia.Techcrunch, "Nokia Confirms The PureView Was Officially The Last Symbian Phone", "Techcrunch", 24 January 2013 as by Nokia on 24 January 2013 Nokia Corporation Q4 and full year 2012 Interim Report: " The Nokia 808 PureView, a device which showcases our imaging capabilities and which came to market in mid-2012, was the last Symbian device from Nokia" Https://tizenindonesia.blogspot.co.uk/2013/11/ntt-docomo-akan-gunakan-tizen-sebagai.html< /ref> Phones running this include the from and from Sharp in 2014.http://www.mobile-japan.com/products/docomo-sharp-sh-07f-summer-flip-phone.htmlhttp://www.mobile-japan.com/products/docomo-unlocked-fujitsu-f-07f-flip-phone.html


History
Symbian originated from EPOC32, an operating system created by Psion in the 1990s. In June 1998, Psion Software became Symbian Ltd., a major joint venture between Psion and phone manufacturers , , and .

Afterwards, different software platforms were created for Symbian, backed by different groups of mobile phone manufacturers. They include S60 (, and LG), ( and ) and (S) (Japanese only such as , Sharp etc.).

With no major competition in the smartphone OS then ( and were comparatively small players), Symbian reached as high as 67% of the global smartphone market share in 2006. 64 million smartphones shipped worldwide 2016

Despite its sizable market share then, Symbian was at various stages difficult to develop for: First (at around early-to-mid-2000's) due to the complexity of then the only native programming languages OPL and Symbian C++ and of the OS itself; then the obstinate developer bureaucracy, along with high prices of various IDEs and SDKs, which were prohibitive for independent or very small developers; and then the subsequent fragmentation, which was in part caused by infighting among and within manufacturers, each of which also had their own IDEs and SDKs. All of this discouraged third-party developers, and served to cause the native app ecosystem for Symbian not to evolve to a scale later reached by Apple's App Store or Android's Google Play.

By contrast, iPhone OS (renamed in 2010) and Android had comparatively simpler design, provided easier and much more centralized infrastructure to create and obtain third-party apps, offered certain developer tools and programming languages with a manageable level of complexity, and having capabilities such as multitasking and graphics in order to meet future consumer demands.

Although Symbian was difficult to program for, this issue could be worked around by creating Java Mobile Edition apps, ostensibly under a "write once, run anywhere" slogan. Symbian and Nitobi Simplify cross platform app development This wasn't always the case because of fragmentation due to different device screen sizes and differences in levels of Java ME support on various devices.

In June 2008, announced the acquisition of Symbian Ltd., and a new independent non-profit organization called the Symbian Foundation was established. Symbian OS and its associated user interfaces S60, and (S) were contributed by their owners , , and Symbian Ltd., to the foundation with the objective of creating the Symbian platform as a royalty-free, open source software, under the OSI- and FSF-approved Eclipse Public License (EPL). The platform was designated as the successor to Symbian OS, following the official launch of the Symbian Foundation in April 2009. The Symbian platform was officially made available as open source code in February 2010.

Nokia became the major contributor to Symbian's code, since it then possessed the development resources for both the Symbian OS core and the user interface. Since then Nokia maintained its own code repository for the platform development, regularly releasing its development to the public repository. Symbian OS – one of the most successful failures in tech history. TechCrunch.com. 8 November 2010 Symbian was intended to be developed by a community led by the Symbian Foundation, 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 moved to Open Source in history.Menezes, Gary. (11 September 2010) Symbian OS, Now Fully Open Source . Watblog.com. Retrieved 25 September 2011.

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 was limited to member companies only, although membership was open to any organisation. Also, the open-source Qt framework was introduced to Symbian in 2010, as the primary upgrade path to , which was to be the next mobile operating system to replace and supplant Symbian on high-end devices; Qt was by its nature free and very convenient to develop with. Several other frameworks were deployed to the platform, among them Standard C/C++, Python, Ruby, and Flash Lite. IDEs and SDKs were developed and then released for free, and app development for Symbian picked up.

In November 2010, the Symbian Foundation announced that due to changes in global economic and market conditions (and also a lack of support from members such as No current plans for Samsung Symbian handsets and ), it would transition to a licensing-only organisation; Symbian Foundation Nokia announced it would take over the stewardship of the Symbian platform. Symbian Foundation would remain the trademark holder and licensing entity and would only have non-executive directors involved.

With market share sliding from 39% in Q32010 to 31% in Q42010, Nokia smartphone market share shrinks to 31 percent, operating profit takes a beating too Symbian was losing ground to iOS and Android quickly, eventually falling behind Android in Q42010. Canalys: Android overtakes Symbian as world's best-selling smartphone platform in Q4 2010 was appointed the CEO of Nokia in September 2010, and on 11 February 2011, he announced a partnership with that would see Nokia adopt as its primary smartphone platform, Open Letter from CEO Stephen Elop, Nokia and CEO Steve Ballmer, Microsoft – Nokia Conversations : the official Nokia blog and Symbian would be gradually phased out, together with MeeGo. As a consequence, Symbian's market share fell, and application developers for Symbian dropped out rapidly. Research in June 2011 indicated that over 39% of mobile developers using Symbian at the time of publication were planning to abandon the platform.

By 5 April 2011, Nokia ceased to openly source any portion of the Symbian software and reduced its collaboration to a small group of pre-selected partners in Japan. Source code released under the EPL remains available in third party repositories.. Sourceforge.net. Retrieved 25 September 2011. symbian-incubation-projects – Symbian Incubation Projects – Google Project Hosting. Google. Retrieved 25 September 2011.

On 22 June 2011, Nokia made an agreement with for an outsourcing program. Accenture will provide Symbian-based software development and support services to Nokia through 2016; about 2,800 Nokia employees became Accenture employees as of October 2011. The transfer was completed on 30 September 2011.

Nokia terminated its support of software development and maintenance for Symbian with effect from 1 January 2014, thereafter refusing to publish new or changed Symbian applications or content in the Nokia Store and terminating its 'Symbian Signed' program for software certification.


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 Widget; a preview was released in January 2010, however in October 2010 Nokia announced that Orbit/UIEMO had been cancelled.

Nokia currently recommends that developers use with , the new high-level declarative UI and scripting framework for creating visually rich touchscreen interfaces that allows development for both Symbian and ; it will be delivered to existing Symbian^3 devices as a Qt update. When more applications 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.


Browser
Symbian^3 and earlier have a built-in based browser. Symbian was the first mobile platform to make use of WebKit (in June 2005). Some older Symbian models have as their default browser.

Nokia released a new browser with the release of Symbian Anna with improved speed and an improved user interface. Browser and Maps updates for many S60 3rd Edition and S60 5th Edition phones. All About Symbian (29 June 2011). Retrieved 25 September 2011.


Multiple language support
Symbian has strong localization support enabling manufacturers and 3rd party application developers to localize their Symbian based products in order to support global distribution. Current Symbian release (Symbian Belle) has support for 48 languages, which Nokia makes available on device in language packs (set of languages which cover the languages commonly spoken in the area where the device variant is intended to be sold). All language packs have in common English (or a locally relevant dialect of it). The supported languages with (and scripts) in Symbian Belle are:
  • Arabic (Arabic),
  • Basque (Latin),
  • Bulgarian (Cyrillic),
  • Catalan (Latin),
  • Chinese PRC (Simplified Chinese),
  • Chinese Hong (Traditional Chinese),
  • Chinese Taiwan (Traditional Chinese),
  • Croatian (Latin),
  • Czech (Latin),
  • Danish (Latin),
  • Dutch (Latin),
  • English UK (Latin),
  • English US (Latin),
  • Estonian (Latin),
  • Finnish (Latin),
  • French (Latin),
  • French Canadian (Latin),
  • Galician (Latin),
  • German (Latin),
  • Greek (Greek),
  • Hebrew (Hebrew),
  • Hindi (Indian),
  • Hungarian (Latin),
  • Icelandic (Latin),
  • Indonesian Bahasa (Latin),
  • Italian (Latin),
  • Japanese (Japanese script)*
  • Kazakh (Cyrillic),
  • Latvian (Latin),
  • Lithuanian (Latin),
  • Malay Bahasa (Latin),
  • Marathi (Maharashtra),
  • Norwegian (Latin),
  • Persian Farsi,
  • Polish (Latin),
  • Portuguese (Latin),
  • Portuguese Brazilian (Latin),
  • Romanian Romania (Latin),
  • Russian (Cyrillic),
  • Serbian (Latin),
  • Slovak (Latin),
  • Slovene (Latin),
  • Spanish (Latin),
  • Spanish Latin (Latin),
  • Swedish (Latin),
  • Tagalog Filipino (Latin),
  • Thai (Thai),
  • Tamil (India)
  • Turkish (Latin),
  • Ukrainian (Cyrillic),
  • Urdu (Arabic),
  • Vietnamese (Latin).
Symbian Belle marks the introduction of Kazakh, while Korean is no longer supported.
  • Japanese is only available on Symbian^2 devices as they are made in Japan, and on other Symbian devices Japanese is still supported with limitations.


Application development

From 2010, Symbian switched to using standard C++ with Qt as the main SDK, which can be used with either or Carbide.c++. Qt supports the older Symbian/S60 3rd (starting with Feature Pack 1, a.k.a. S60 3.1) and Symbian/S60 5th Edition (a.k.a. S60 5.01b) releases, as well as the new Symbian platform. It also supports and , Windows, Linux and Mac OS X.

Alternative application development can be done using Python (see Python for S60), Adobe Flash Lite or .

Symbian OS previously used a Symbian specific C++ version, along with and later Carbide.c++ integrated development environment (IDE), as the native application development environment.

Web Run time (WRT) is a portable application framework that allows creating on the S60 Platform; it is an extension to the S60 based browser that allows launching multiple browser instances as separate JavaScript applications. Apps:Mobile Web Apps in a Nutshell. symlab.org wiki Nokia Developer – Web . Forum.nokia.com. Retrieved 25 September 2011.


Application development

Qt
As of 2010, the SDK for Symbian is standard C++, using Qt. It can be used with either , or Carbide (the older IDE previously used for Symbian development). 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. Application development can either use C++ or .


Symbian C++
As Symbian OS is written in C++ using Symbian Software's coding standards, it is possible to develop using Symbian C++, although it is not a standard implementation. Before the release of the Qt SDK, this was the standard development environment. There were multiple platforms based on Symbian OS that provided software development kits (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 maker's website too.

The SDKs contain documentation, the header files and library files needed 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 GNU Compiler Collection (GCC) compiler (a ) needed to build software to work on the device.

Symbian OS 9 and the Symbian platform use a new application binary interface (ABI) and needed 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 , 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 initially harder to implement than in other environments. It is possible that the techniques, developed for the much more restricted mobile hardware and compilers of the 1990s, caused extra complexity in source code because programmers are required to concentrate on low-level details instead of more application-specific features. As of 2010, these issues are no longer the case when using standard C++, with the Qt SDK.

Symbian C++ programming is commonly done with an integrated development environment (IDE). For earlier versions of Symbian OS, the commercial IDE 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 via 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++.

Visual Basic programmers can use to develop apps for S60 3rd Edition and UIQ 3 devices.

In the past, , Visual Basic .NET, and C# development for Symbian were possible through 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 Jan 18th, 2010, 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 IDE for Symbian OS. Symbian OS development is also possible on and Mac OS X using tools and methods 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 IDE for Mac OS X was available. Tom Sutcliffe and Jason Barrie Morley Xcode Symbian support. Symbian-xcode-plugin.tigris.org. Retrieved 25 September 2011.

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 . Other tools include , which can be used to build Symbian 7.0 and 7.0s programs using Java.

Nokia S60 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). Applications can now be signed for free. Nokia Developer News | Nokia Now Signing Symbian Apps for Free – Nokia Developer Blogs . Blogs.forum.nokia.com (16 August 2010). Retrieved 25 September 2011.


Architecture

Technology domains and packages
Symbian's design is subdivided into technology domains, each of which comprises a number of software packages. 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 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 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 . Introducing EKA2, by Jane Sales with Martin Tasker. (PDF). Retrieved 25 September 2011. The real-time kernel has a architecture containing only the minimum, most basic primitives and functionality, for maximum robustness, availability and responsiveness. It has been termed a , because it needs an extended kernel to implement any other abstractions. It contains a scheduler, memory management and device drivers, with networking, telephony and 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.


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 and is based on asynchronous server-based events.

Symbian OS was created with three systems design principles in mind:

  1. the integrity and security of user data is paramount
  2. user time must not be wasted
  3. all resources are scarce

To best follow these principles, Symbian uses a , 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 and a . Similar methods exist to conserve storage space. Further, all Symbian programming is event-based, and the central processing unit (CPU) is switched into a low power mode when applications are not directly dealing with an event. This is done via a programming idiom called . 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:

  • UI Framework Layer
  • 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 and User Library, a Plug-In Framework which manages all plug-ins, Store, Central Repository, 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 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 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 , 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 -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 .

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 , and .

There is also a large volume of (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 needed 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, , Java ME providing another set of APIs on top of most of the OS and . Many of these are frameworks, and vendors are expected to supply plug-ins to these frameworks from third parties (for example, for multimedia ). 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.


Symbian UI variants/platforms
Symbian, as it advanced to OS version 7.0, spun off into several different graphical user interfaces, each backed by a certain company or group of companies. Unlike 's cosmetic GUIs, Symbian GUIs are referred to as "platforms" due to more significant modifications and integrations. Things became more complicated when applications developed for different Symbian GUI platforms were not compatible with each other, and this led to OS fragmentation. The History of Symbian's Secret Fragmentation

User Interfaces platforms that run on or are based on Symbian OS include:

  • S60, Symbian, also called Series 60. It was backed mainly by Nokia. There are several editions of this platform, appearing first as S60 (1st Edition) on Nokia 7650. It was followed by S60 2nd Edition (e.g. Nokia N70), S60 3rd Edition (e.g. Nokia N73) and S60 5th Edition (which introduced touch UI e.g. Nokia N97). The name, S60, was changed to just Symbian after the formation of Symbian Foundation, and subsequently called Symbian^1, 2 and 3.
  • Series 80 used by Nokia Communicators such as Nokia 9300i.
  • Series 90 Touch and button based. The only phone using this platform is Nokia 7710.
  • backed mainly by and then . It is compatible with both buttons and touch/stylus based inputs. The last major release version is UIQ3.1 in 2008, on Sony Ericsson G900. It was discontinued after the formation of Symbian Foundation, and the decision to consolidate different Symbian UI variants into one led to the adoption of S60 as the version going forward. UIQ Technology puts remaining staff on notice
  • (Mobile Oriented Applications Platform) Japan used by , Mitsubishi, and Sharp-developed phones for . It uses an interface developed specifically for DoCoMo's "Freedom of Mobile Access" network brand and is based on the UI from earlier Fujitsu FOMA models. The user cannot install new C++ applications. (Japan Only)
  • Japan, successor of MOAP, used on 's phone.


Symbian (S60) version comparison
! NFC Support
! Yes
! No
! No
! No
! width="189"
No
! Latest firmware name
! Nokia Belle Feature Pack 2/ Belle Refresh
! Symbian^2
! Symbian^1/Series 60 5th Edition
! Series 60 3rd Edition Feature Pack 2
! width="189"
Series 80
* manufactured by
† manufactured by Sharp
Software update service for Nokia Belle and Symbian (S60) phones is discontinued at the end of December 2015


Market share and competition
Https://m.theregister.co.uk/2004/05/06/symbian_sales/< /ref>

3.7 million devices were shipped in Q3 2004, a growth of 201% compared to Q3 2003 and market share growing from 30.5% to 50.2%. However in the United States it was much less popular, with a 6% market share in Q3 2004, well behind (43%) and (25%). This has been attributed to North American customers preferring wireless over smartphones, as well as Nokia' Https://www.theregister.co.uk/2004/10/27/pda_market_q3_04/< /ref>

On 16 November 2006, the 100 millionth running the OS was shipped. As of 21 July 2009, more than 250 million devices running Symbian OS had been produced. Symbian Foundation Adds New Member, Nuance. News.softpedia.com (21 July 2009). Retrieved 25 September 2011.

In 2006, Symbian had 73% of the smartphone market, compared with 22.1% of the market in the second quarter of 2011. Gartner Says Sales of Mobile Devices in Second Quarter of 2011 Grew 16.5 Percent Year-on-Year; Smartphone Sales Grew 74 Percent. Gartner.com. Retrieved 25 September 2011.

By the end of May 2006, 10 million Symbian-powered phones were sold in Japan, representing 11% of Symbian's total worldwide shipments of 89 million.http://www.allaboutsymbian.com/news/item/4063_10_million_Symbian_OS_phone_un.php By November 2007 the figure was 30 million, achieving a market share of 65% by June 2007 in the Japanese market.http://www.allaboutsymbian.com/news/item/6576_30_million_Symbian_OS_Phones_i.php

Symbian has lost market share over the years as the market has dramatically grown, with new competing platforms entering the market, though its sales have increased during the same timeframe. E.g., although Symbian's share of the global smartphone market dropped from 52.4% in 2008 to 47.2% in 2009, shipments of Symbian devices grew 4.8%, from 74.9 million units to 78.5 million units. From Q2 2009 to Q2 2010, shipments of Symbian devices grew 41.5%, by 8.0 million units, from 19,178,910 units to 27,129,340; compared to an increase of 9.6 million units for Android, 3.3 million units for RIM, and 3.2 million units for Apple.

Prior reports on device shipments as published in February 2010 showed that the Symbian devices formed a 47.2% share of the smart mobile devices shipped in 2009, with RIM having 20.8%, Apple having 15.1% (via iOS), Microsoft having 8.8% (via and ) and Android having 4.7%.

In the number of "smart mobile device" sales, Symbian devices were the market leaders for 2010. Statistics showed that Symbian devices formed a 37.6% share of smart mobile devices sold, with Android having 22.7%, RIM having 16%, and Apple having 15.7% (via iOS). Some estimates indicate that the number of mobile devices shipped with the Symbian OS up to the end of Q2 2010 is 385 million. 100 Million Club H1 2010. VisionMobile (18 October 2010). Retrieved 25 September 2011.

Over the course of 2009–10, Motorola, Samsung, , and announced their withdrawal from Symbian in favour of alternative platforms including Google's Android, Microsoft's . Nokia and Microsoft enter strategic alliance on Windows Phone, Bing, Xbox Live and more. Engadget. Retrieved 25 September 2011.Woods, Ben. (1 October 2010) Samsung to drop Symbian support | Wireless – CNET News. CNET. Retrieved 25 September 2011.Meyer, David. (3 November 2008) Motorola ditches Symbian, announces 3,000 layoffs | Networking | ZDNet UK. ZDNet.co.uk. Retrieved 25 September 2011.Mello, John P.. (15 October 2010) Sony Ditches Symbian. PC World. Retrieved 25 September 2011.

In Q2 2012, according to IDC worldwide market share has dropped to an all-time low of 4.4%.


Criticism
The users of Symbian in the countries with non-Latin alphabets (such as Russia, Ukraine and others) have been criticizing the complicated method of language switching for many years. Mobile-reviews. Review of Nokia E7. 9 August 2011 For example, if a user wants to type a Latin letter, they must call the menu, click the languages item, use arrow keys to choose, for example, the English language from among many other languages, and then press the 'OK' button. After typing the Latin letter, the user must repeat the procedure to return to their native keyboard. This method slows down typing significantly. In touch-phones and QWERTY phones the procedure is slightly different but remains time-consuming. All other mobile operating systems, as well as Nokia's S40 phones, enable switching between two initially selected languages by one click or a single gesture.

Early versions of the firmware for the original Nokia N97, running on Symbian^1/Series 60 5th Edition have been heavily criticized as buggy (also contributed by the low amount of installed in the phone).

In November 2010, Smartphone blog All About Symbian criticized the performance of Symbian's default web browser and recommended the alternative browser . Mobile browser comparison, November 2010. Allaboutsymbian.com (25 November 2010). Retrieved 25 September 2011. Nokia's Senior Vice President promised an updated browser in the first quarter of 2011.

There are many different versions and editions of Symbian, which led to fragmentation. Apps and software may be incompatible when installed across different versions of Symbian.


Malware
Symbian OS is 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, although some rely on social engineering, often in the form of messages that come with the malware, , game or some other application for Symbian.

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 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 a 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 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 the form of 'cooked firmware' was demonstrated at the International Malware Conference, , December 2010, by Indian hacker Atul Alex.. H-online.com (8 December 2010). Retrieved 25 September 2011. Hacker Creates Modified Symbian S60 Firmware with Hidden Back Door. Live Hacking (10 December 2010). Retrieved 25 September 2011.


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. Nokia's S60 3rd Ed security has been hacked?, Symbian Freak This allows altering 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 can be executed. ''S60 v3 Hacking – Mission accomplished, FP1 hacked!''. Symbian Freak (27 March 2008). Retrieved 25 September 2011.


Version history
EPOC16, originally simply named EPOC, was the operating system developed by Psion in the late 1980s and early 1990s for Psion's "SIBO" (SIxteen Bit Organisers) devices. All EPOC16 devices featured an 8086-family processor and a 16-bit architecture. EPOC16 was a single-user preemptive multitasking operating system, written in Intel 8086 assembler language and C and designed to be delivered in . It supported a simple programming language called Open Programming Language (OPL) and an integrated development environment (IDE) called OVAL. SIBO devices included the: MC200, MC400, Series 3 (1991–98), Series 3a, Series 3c, Series 3mx, Siena, Workabout and Workabout mx. The MC400 and MC200, the first EPOC16 devices, shipped in 1989.

EPOC16 featured a primarily monochrome, keyboard-operated graphical interface the hardware for which it was designed originally had input in the form of a digitiser panel.

In the late 1990s, the operating system was referred to as EPOC16 to distinguish it from Psion's then-new EPOC32 OS.

The first version of EPOC32, Release 1 appeared on the Psion Series 5 ROM v1.0 in 1997. Later, ROM v1.1 featured Release 3. (Release 2 was never publicly available.) These were followed by the Psion Series 5mx, / Revo plus, Psion Series 7 / and netPad (which all featured Release 5).

The EPOC32 operating system, at the time simply referred to as EPOC, was later renamed Symbian OS. Adding to the confusion with names, before the change to Symbian, EPOC16 was often referred to as SIBO to distinguish it from the "new" EPOC. Despite the similarity of the names, EPOC32 and EPOC16 were completely different operating systems, EPOC32 being written in C++ from a new codebase with development beginning during the mid-1990s.

EPOC32 was a pre-emptive multitasking, single user operating system with memory protection, which encourages the application developer to separate their program into an engine and an . The Psion line of PDAs come with a graphical user interface called which is specifically tailored for handheld machines with a keyboard (thus looking perhaps more similar to desktop GUIs than palmtop GUIs). However, one of EPOC's characteristics is the ease with which new GUIs can be developed based on a core set of GUI classes, a feature which has been widely explored from Ericsson R380 and onwards.

EPOC32 was originally developed for the of processors, including the ARM7, ARM9, and Intel's , but can be compiled towards target devices using several other processor types.

During the development of EPOC32, Psion planned to license EPOC to third-party device manufacturers, and spin off its software division as Psion Software. One of the first licensees was the short-lived , which halted production with less than 1,000 units sold. marketed a rebranded Psion Series 5mx called the MC218, and later created the EPOC Release 5.1 based , the R380. Oregon Scientific also released a budget EPOC device, the (notable as the only EPOC device to ship with Release 4).

Work started on the 32-bit version in late 1994.

The Series 5 device, released in June 1997, used the first iterations of the EPOC32 OS, codenamed "Protea", and the "Eikon" graphical user interface.

The Oregon Scientific was the only PDA to use the ER4.

The Psion Series 5mx, Psion Series 7, , , and Ericsson MC218 were released in 1999 using ER5. A phone project was announced at , the Phillips Illium/Accent, but did not achieve a commercial release. This release has been retrospectively dubbed Symbian OS 5.

The first phone using ER5u, the Ericsson R380 was released in November 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. The 'u' in the name refers to the fact that it supported .

In June 1998, Psion Software became Symbian Ltd., a major joint venture between Psion and phone manufacturers , , and . As of Release 6, EPOC became known simply as Symbian OS.

The OS was renamed Symbian OS and was envisioned as the base for a new range of . This release is sometimes called ER6. Psion gave 130 key staff to the new company and retained a 31% shareholding in the spin-off.

The first 'open' Symbian OS phone, the Nokia 9210 Communicator, was released in June 2001. support was added. Almost 500,000 Symbian phones were shipped in 2001, rising to 2.1 million the following year.

Development of different UIs was made generic with a "reference design strategy" for either 'smartphone' or 'communicator' devices, subdivided further into keyboard- or tablet-based designs. Two reference UIs (DFRDs or Device Family Reference Designs) were shipped Quartz and Crystal. The former was merged with Ericsson's 'Ronneby' design and became the basis for the interface; the latter reached the market as the Nokia Series 80 UI.

Later DFRDs were Sapphire, Ruby, and Emerald. Only Sapphire came to market, evolving into the Pearl DFRD and finally the Nokia Series 60 UI, a keypad-based 'square' UI for the first true smartphones. The first one of them was the Nokia 7650 smartphone (featuring Symbian OS 6.1), which was also the first with a built-in camera, with VGA (0.3 Mpx = 640×480) resolution. Other notable S60 Symbian 6.1 devices are the Nokia 3650, the short lived and Siemens SX1 the first and the last Symbian phone from Siemens.

Despite these efforts to be generic, the UI was clearly split between competing companies: Crystal or Sapphire was Nokia, Quartz was Ericsson. DFRD was abandoned by Symbian in late 2002, as part of an active retreat from UI development in favour of 'headless' delivery. Pearl was given to Nokia, Quartz development was spun off as UIQ Technology AB, and work with Japanese firms was quickly folded into the standard.

First shipped in 2003. This is an important Symbian release which appeared with all contemporary user interfaces including (Sony Ericsson P800, P900, P910, Motorola A925, A1000), Series 80 (Nokia 9300, 9500), Series 90 (Nokia 7710), Series 60 (Nokia 3230, 6260, 6600, 6670, 7610) as well as several phones in Japan. It also added EDGE support and IPv6. Java support was changed from and JavaPhone to one based on the Java ME standard.

One million Symbian phones were shipped in Q1 2003, with the rate increasing to one million a month by the end of 2003.

Symbian OS 7.0s was a version of 7.0 special adapted to have greater backward compatibility with Symbian OS 6.x, partly for compatibility between the Communicator 9500 and its predecessor the Communicator 9210.

In 2004, Psion sold its stake in Symbian. The same year, the first for mobile phones using Symbian OS, Cabir, was developed, which used to spread itself to nearby phones. See Cabir and Symbian OS threats.

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 Symbian OS 8.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, while EKA2 was a real-time kernel. 8.0b was deproductised in 2003.

Also included were new APIs to support , 3G, two-way data streaming, , and ES with and direct screen access.

An improved 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 real-time support but not allowing open application installation. The first and maybe the most famous smartphone featuring Symbian OS 8.1a was Nokia N90 in 2005, 's first in .
Symbian OS 9.0 was used for internal Symbian purposes only. It was de-productised in 2004. 9.0 marked the end of the road for EKA1. 8.1a is the final EKA1 version of Symbian OS.

Symbian OS has generally maintained reasonable binary code 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.

Released early 2005. It includes many new security related features, including platform security module facilitating mandatory code signing. The new ARM binary model means developers need to retool and the security changes mean they may have to recode. S60 platform 3rd Edition phones have Symbian OS 9.1. Sony Ericsson is shipping the M600 and P990 based on Symbian OS 9.1. The earlier versions had a defect where the phone hangs temporarily after the owner sent a large number of SMS'es. However, on 13 September 2006, Nokia released a small program to fix this defect. Solution to Nokia Slow SMS / Hang Problem Support for 2.0 was also added.

Symbian 9.1 introduced capabilities and a Platform Security framework. To access certain APIs, developers have to sign their application with a digital signature. Basic capabilities are user-grantable and developers can self-sign them, while more advanced capabilities require certification and signing via the Symbian Signed program, which uses independent 'test houses' and phone manufacturers for approval. For example, file writing is a user-grantable capability while access to Multimedia Device Drivers require phone manufacturer approval. A TC TrustCenter ACS Publisher ID certificate is required by the developer for signing applications.

Released Q1 2006. Support for OMA Device Management 1.2 (was 1.1.2). Vietnamese language support. S60 3rd Edition Feature Pack 1 phones have Symbian OS 9.2. Nokia phones with Symbian OS 9.2 OS include the Nokia E71, Nokia E90, Nokia N95, Nokia N82, Nokia N81 and Nokia 5700.
Released on 12 July 2006. Upgrades include improved memory management and native support for Wifi 802.11, . The Nokia E72, Nokia 5730 XpressMusic, Nokia N79, Nokia N96, Nokia E52, Nokia E75, Nokia 5320 XpressMusic, Sony Ericsson P1 and others feature Symbian OS 9.3.
Announced in March 2007. Provides the concept of demand paging which is available from v9.3 onwards. Applications should launch up to 75% faster. Additionally, support is provided by . Ships with the Samsung i8910 Omnia HD, Nokia N97, Nokia N97 mini, Nokia 5800 XpressMusic, Nokia 5530 XpressMusic, Nokia 5228, Nokia 5230, Nokia 5233, Nokia 5235, Nokia C6-00, Nokia X6, Sony Ericsson Satio, Sony Ericsson Vivaz and Sony Ericsson Vivaz Pro. Used as the basis for Symbian^1, the first Symbian platform release. The release is also better known as S60 5th edition, as it is the bundled interface for the OS.
Symbian^2 is a version of Symbian that only used by Japanese manufacturers, started selling in Japan market since May 2010. The version is not used by Nokia. Nokia: go straight to Symbian 3, skip Symbian 2 • Reg Hardware
Symbian^3 is an improvement over previous S60 5th Edition and features single touch menus in the user interface, as well as new Symbian OS kernel with hardware-accelerated graphics; further improvements will come in the first half of 2011 including portrait qwerty keyboard, a new browser and split-screen text input. Nokia announced that updates to Symbian^3 interface will be delivered gradually, as they are available; Symbian^4, the previously planned major release, is now discontinued and some of its intended features will be incorporated into Symbian^3 in successive releases, starting with Symbian Anna.
In the summer of 2011 videos showing an early leaked version of Symbian Belle (original name of Nokia Belle) running on a Nokia N8 were published on YouTube.

On 24 August 2011, Nokia announced it officially for three new smartphones, the Nokia 600 (later replaced by Nokia 603), Nokia 700, and Nokia 701.

Nokia officially renamed Symbian Belle to Nokia Belle in a company blog post. Nokia Belle coming soon – Nokia Conversations : the official Nokia blog

Nokia Belle adds to the Anna improvements with a pull-down status/notification bar, deeper near field communication integration, free-form re-sizable homescreen widgets, and six homescreens instead of the previous three. As of 7 February 2012, Nokia Belle update is available for most phone models through Nokia Suite, coming later to Australia. Users can check the availability at the Nokia homepage.

On 1 March 2012, Nokia announced a Feature Pack 1 update for Nokia Belle which will be available as an update to Nokia 603, 700, 701 (excluding others), and for Nokia 808 PureView natively.

Symbian Carla and Donna were the planned follow-up releases to Belle, to be released in late 2012 and late 2013 respectively. However it was acknowledged in May 2012 that these had been cancelled and that the upcoming Belle Feature Pack 2 would be the last version of the operating system.http://www.itproportal.com/2012/05/25/symbian-carla-cancelled-beginning-of-the-end-for-symbian/

The latest software release for Nokia 1st generation Symbian Belle smartphones (Nokia N8, C7, C6-01, Oro, 500, X7, E7, E6) is Nokia Belle Refresh (111.040.1511).

In October 2012, the Nokia Belle Feature Pack 2, widely considered the last major update for Symbian, was released for Nokia 603, 700, 701, and 808 PureView.


See also

General
  • Nokia Ovi suite
  • Nokia PC Suite, software package used to establish an interface between Nokia mobile devices and computers running Microsoft Windows operating system; not limited to Symbian
  • Nokia Software Updater
  • Ovi store Nokia's application store on the Internet, not limited to Symbian


Development-related
  • Accredited Symbian Developer
  • Carbide.c++, alternative application and OS development IDE
  • P.I.P.S. Is POSIX on Symbian
  • Python for S60, alternative application development language
  • Qt, preferred development tool, both for the OS and applications, not limited to Symbian


Bibliography


External links


Symbian^3 EPL source

Page 1 of 1
1

Account

Social:
Pages:  ..   .. 
Items:  .. 

Navigation

General: Atom Feed Atom Feed  .. 
Help:  ..   .. 
Category:  ..   .. 
Media:  ..   .. 
Posts:  ..   ..   .. 

Statistics

Page:  .. 
Summary:  .. 
1 Tags
10/10 Page Rank
5 Page Refs
3s Time