Hardware android

The main hardware platform for Android is the ARM architecture (ARMv7 and ARMv8-A architectures), with x86 and MIPS architectures also officially supported in later versions of Android. Since Android 5.0 "Lollipop", 64-bit variants of all platforms are supported in addition to the 32-bit variants.^[79] Unofficial Android-x86 project used to provide support for the x86 and MIPS architectures ahead of the official support.^[5][80] Since 2012, Android devices with Intel processors began to appear, including phones^[81] and tablets. While gaining support for 64-bit platforms, Android was first made to run on 64-bit x86 and then on ARM64.
Requirements for the minimum amount of RAM for devices running Android 5.1 range from 512 MB of RAM for normal-density screens, to about 1.8 GB for high-density screens.^[82] The recommendation for Android 4.4 is to have at least 512 MB of RAM,^[83] while for "low RAM" devices 340 MB is the required minimum amount that does not include memory dedicated to various hardware components such as the baseband processor.^[84] Android 4.4 requires a 32-bit ARMv7, MIPS or x86 architecture processor (latter two through unofficial ports),^[5][85] together with an OpenGL ES 2.0 compatible graphics processing unit (GPU).^[86] Android supports OpenGL ES 1.1, 2.0, 3.0 and 3.1. Some applications may explicitly require a certain version of the OpenGL ES, and suitable GPU hardware is required to run such applications.^[86]
Android devices incorporate many optional hardware components, including still or video cameras, GPS, orientation sensors, dedicated gaming controls, accelerometers, gyroscopes, barometers, magnetometers, proximity sensors, pressure sensors, thermometers, and touchscreens. Some hardware components are not required, but became standard in certain classes of devices, such as smartphones, and additional requirements apply if they are present. Some other hardware was initially required, but those requirements have been relaxed or eliminated altogether. For example, as Android was developed initially as a phone OS, hardware such as microphones were required, while over time the phone function became optional.^[69] Android used to require an autofocus camera, which was relaxed to a fixed-focus camera^[69] if present at all, since the camera was dropped as a requirement entirely when Android started to be used on set-top boxes.
In addition to running on smartphones and tablets, several vendors run Android natively on regular PC hardware with a keyboard and mouse.^[87][88][89] In addition to their availability on commercially available hardware, similar PC hardware–friendly versions of Android are freely available from the Android-x86 project, including customized Android 4.4.^[90] Using the Android emulator that is part of the Android SDK, or by using BlueStacks or Andy, Android can also run non-natively on x86.^[91][92] Chinese companies are building a PC and mobile operating system, based on Android, to "compete directly with Microsoft Windows and Google Android".^[93] The Chinese Academy of Engineering noted that "more than a dozen" companies were customising Android following a Chinese ban on the use of Windows 8 on government PCs.^[94][95][96]

Memory management android

Since Android devices are usually battery-powered, Android is designed to manage memory (RAM) to keep power consumption at a minimum, in contrast to desktop operating systems which generally assume they are connected to unlimited mains electricity. When an Android application is no longer in use, the system will automatically suspend it in memory; while the application is still technically "open", suspended applications consume no resources (for example, battery power or processing power) and sit idly in the background until needed again. This brings a dual benefit by increasing the general responsiveness of Android devices, since applications do not need to be closed and reopened from scratch each time, and by ensuring that background applications do not consume power needlessly.^[74][75]
Android manages the applications stored in memory automatically: when memory is low, the system will begin killing applications and processes that have been inactive for a while, in reverse order since they were last used (oldest first). This process is designed to be invisible to the user, so that users do not need to manage memory or the killing of applications themselves.^[76][77] Lifehacker reported in 2011 that third-party task killers were doing more harm than good.^[78]

Applications android

Applications ("apps"), which extend the functionality of devices, are written using the Android software development kit (SDK) and, often, the Java programming language that has complete access to the Android APIs. Java may be combined with C/C++, together with a choice of non-default runtimes that allow better C++ support;^[59][60][61] the Go programming language is also supported since its version 1.4, which can also be used exclusively although with a restricted set of Android APIs.^[62] The SDK includes a comprehensive set of development tools,^[63] including a debugger, software libraries, a handset emulator based on QEMU, documentation, sample code, and tutorials. Initially, Google's supported integrated development environment (IDE) was Eclipse using the Android Development Tools (ADT) plugin; in December 2014, Google released Android Studio, based on IntelliJ IDEA, as its primary IDE for Android application development. Other development tools are available, including a native development kit (NDK) for applications or extensions in C or C++, Google App Inventor, a visual environment for novice programmers, and various cross platform mobile web applications frameworks. In January 2014, Google unveiled an framework based on Apache Cordova for porting Chrome HTML 5 web applications to Android, wrapped in a native application shell.^[64]
Android has a growing selection of third-party applications, which can be acquired by users by downloading and installing the application's APK (Android application package) file, or by downloading them using an application store program that allows users to install, update, and remove applications from their devices. Google Play Store is the primary application store installed on Android devices that comply with Google's compatibility requirements and license the Google Mobile Services software.^[3][65] Google Play Store allows users to browse, download and update applications published by Google and third-party developers; As of July 2013, there are more than one million applications available for Android in Play Store.^[66] As of May 2013, 48 billion applications have been installed from Google Play Store^[67] and in July 2013, 50 billion applications were installed.^[68][69] Some carriers offer direct carrier billing for Google Play application purchases, where the cost of the application is added to the user's monthly bill.^[70]
Due to the open nature of Android, a number of third-party application marketplaces also exist for Android, either to provide a substitute for devices that are not allowed to ship with Google Play Store, provide applications that cannot be offered on Google Play Store due to policy violations, or for other reasons. Examples of these third-party stores have included the Amazon Appstore, GetJar, and SlideMe. F-Droid, another alternative marketplace, seeks to only provide applications that are distributed under free and open source licenses.^{[3][71][72][73]}

Features android

Interface

Notifications are accessed by sliding from the top of the display; individual notifications can be dismissed by sliding them away, and may contain additional functions as seen on this example of the "missed call" notification from an older version of Android.

Android's default user interface is based on direct manipulation,^[48] using touch inputs that loosely correspond to real-world actions, like swiping, tapping, pinching, and reverse pinching to manipulate on-screen objects, along with a virtual keyboard.^[48] Game controllers and full size physical keyboards are supported via Bluetooth.^[49] The response to user input is designed to be immediate and provides a fluid touch interface, often using the vibration capabilities of the device to provide haptic feedback to the user. Internal hardware, such as accelerometers, gyroscopes and proximity sensors^[50] are used by some applications to respond to additional user actions, for example adjusting the screen from portrait to landscape depending on how the device is oriented, or allowing the user to steer a vehicle in a racing game by rotating the device, simulating control of a steering wheel.^[51]
Android devices boot to the homescreen, the primary navigation and information "hub" on Android devices that is analogous to the desktop found on personal computers. (Android also runs on regular personal computers, as described below). Android homescreens are typically made up of app icons and widgets; app icons launch the associated app, whereas widgets display live, auto-updating content, such as the weather forecast, the user's email inbox, or a news ticker directly on the homescreen.^[52] A homescreen may be made up of several pages, between which the user can swipe back and forth, though Android's homescreen interface is heavily customisable, allowing users to adjust the look and feel of the devices to their tastes.^[53] Third-party apps available on Google Play and other app stores can extensively re-theme the homescreen, and even mimic the look of other operating systems, such as Windows Phone.^[54] Most manufacturers, and some wireless carriers, customise the look and feel of their Android devices to differentiate themselves from their competitors.^[55] Applications that handle interactions with the homescreen are called "launchers" because they, among other purposes, launch the applications installed on a device.
Along the top of the screen is a status bar, showing information about the device and its connectivity. This status bar can be "pulled" down to reveal a notification screen where apps display important information or updates, such as a newly received email or SMS text, in a way that does not immediately interrupt or inconvenience the user.^[56] Notifications are persistent until read (by tapping, which opens the relevant app) or dismissed by sliding it off the screen. Beginning on Android 4.1, "expanded notifications" can display expanded details or additional functionality; for instance, a music player can display playback controls, and a "missed call" notification provides buttons for calling back or sending the caller an SMS message.^[57]
Android provides the ability to run applications that change the default launcher, and hence the appearance and externally visible behaviour of Android. These appearance changes include a multi-page dock or no dock, and many more changes to fundamental features of the user interface.^[58]

History android

Android, Inc. was founded in Palo Alto, California in October 2003 by Andy Rubin (co-founder of Danger),^[24] Rich Miner (co-founder of Wildfire Communications, Inc.),^[25] Nick Sears (once VP at T-Mobile),^[26] and Chris White (headed design and interface development at WebTV^[12]) to develop, in Rubin's words, "smarter mobile devices that are more aware of its owner's location and preferences".^[12] The early intentions of the company were to develop an advanced operating system for digital cameras. Though, when it was realized that the market for the devices was not large enough, the company diverted its efforts toward producing a smartphone operating system that would rival Symbian and Microsoft Windows Mobile.^[27] Despite the past accomplishments of the founders and early employees, Android Inc. operated secretly, revealing only that it was working on software for mobile phones.^[12] That same year, Rubin ran out of money. Steve Perlman, a close friend of Rubin, brought him $10,000 in cash in an envelope and refused a stake in the company.^[28]
In July 2005, Google acquired Android Inc. for at least $50 million, whose key employees, including Rubin, Miner and White, stayed at the company after the acquisition.^[11][12] Not much was known about Android Inc. at the time, but many assumed that Google was planning to enter the mobile phone market with this move.^[12] At Google, the team led by Rubin developed a mobile device platform powered by the Linux kernel. Google marketed the platform to handset makers and carriers on the promise of providing a flexible, upgradable system. Google had lined up a series of hardware component and software partners and signaled to carriers that it was open to various degrees of cooperation on their part.^[29][30][31]
Speculation about Google's intention to enter the mobile communications market continued to build through December 2006.^[32] An earlier prototype codenamed "Sooner" had a closer resemblance to a BlackBerry phone, with no touchscreen, and a physical, QWERTY keyboard, but was later re-engineered to support a touchscreen, to compete with other announced devices such as the 2006 LG Prada and 2007 Apple iPhone.^[33][34] In September 2007, InformationWeek covered an Evalueserve study reporting that Google had filed several patent applications in the area of mobile telephony.^[35][36]

Eric Schmidt, Andy Rubin and Hugo Barra at a 2012 press conference announcing Google's Nexus 7 tablet

On November 5, 2007, the Open Handset Alliance, a consortium of technology companies including Google, device manufacturers such as HTC, Sony and Samsung, wireless carriers such as Sprint Nextel and T-Mobile, and chipset makers such as Qualcomm and Texas Instruments, unveiled itself, with a goal to develop open standards for mobile devices.^[13] That day, Android was unveiled as its first product, a mobile device platform built on the Linux kernel.^[13][37] The first commercially available smartphone running Android was the HTC Dream, released on October 22, 2008.^[38]
Since 2008, Android has seen numerous updates which have incrementally improved the operating system, adding new features and fixing bugs in previous releases. Each major release is named in alphabetical order after a dessert or sugary treat; for example, version 1.5 "Cupcake" was followed by 1.6 "Donut". In 2010, Google launched its Nexus series of devices – a line of smartphones and tablets running the Android operating system, and built by manufacturing partners. HTC collaborated with Google to release the first Nexus smartphone,^[39] the Nexus One. Google has since updated the series with newer devices, such as the Nexus 5 phone (made by LG) and the Nexus 7 tablet (made by Asus). Google releases the Nexus phones and tablets to act as their flagship Android devices, demonstrating Android's latest software and hardware features. From 2013 until 2015, Google offered several Google Play Edition devices over Google Play. While not carrying the Google Nexus branding, these were Google-customized Android phones and tablets that also ran the latest version of Android, free from manufacturer or carrier modifications.
From 2010 to 2013, Hugo Barra served as product spokesperson, representing Android at press conferences and Google I/O, Google’s annual developer-focused conference. Barra's product involvement included the entire Android ecosystem of software and hardware, including Honeycomb, Ice Cream Sandwich, Jelly Bean and KitKat operating system launches, the Nexus 4 and Nexus 5 smartphones, the Nexus 7^[40] and Nexus 10 tablets,^[41] and other related products such as Google Now^[42] and Google Voice Search, Google’s speech recognition product comparable to Apple’s Siri.^[42] In 2013, Barra left the Android team for Chinese smartphone maker Xiaomi.^[43] The same year, Larry Page announced in a blog post that Andy Rubin had moved from the Android division to take on new projects at Google.^[44] He was replaced by Sundar Pichai who became the new head of Android and Chrome OS,^[45] and, later, by Hiroshi Lockheimer when Pichai became CEO of Google.^[46]
In 2014, Google launched Android One, a line of smartphones mainly targeting customers in the developing world. In May 2015, Google announced Project Brillo as a cut-down version of Android that uses its lower levels (excluding the user interface), intended for the "Internet of Things" (IoT) embedded systems.^[47]

Android (operating system)

Android is a mobile operating system (OS) currently developed by Google, based on the Linux kernel and designed primarily for touchscreen mobile devices such as smartphones and tablets. Android's user interface is mainly based on direct manipulation, using touch gestures that loosely correspond to real-world actions, such as swiping, tapping and pinching, to manipulate on-screen objects, along with a virtual keyboard for text input. In addition to touchscreen devices, Google has further developed Android TV for televisions, Android Auto for cars, and Android Wear for wrist watches, each with a specialized user interface. Variants of Android are also used on notebooks, game consoles, digital cameras, and other electronics. As of 2015, Android has the largest installed base of all operating systems.^[11]
Initially developed by Android, Inc., which Google bought in 2005,^[12] Android was unveiled in 2007, along with the founding of the Open Handset Alliance – a consortium of hardware, software, and telecommunication companies devoted to advancing open standards for mobile devices.^[13] As of July 2013, the Google Play store has had over one million Android applications ("apps") published, and over 50 billion applications downloaded.^[14] An April–May 2013 survey of mobile application developers found that 71% of developers create applications for Android,^[15] and a 2015 survey found that 40% of full-time professional developers see Android as their priority target platform, which is comparable to Apple's iOS on 37% with both platforms far above others.^[16] At Google I/O 2014, the company revealed that there were over one billion active monthly Android users, up from 538 million in June 2013.^[17]
Android's source code is released by Google under open source licenses, although most Android devices ultimately ship with a combination of open source and proprietary software, including proprietary software required for accessing Google services.^[3] Android is popular with technology companies that require a ready-made, low-cost and customizable operating system for high-tech devices.^[18] Its open nature has encouraged a large community of developers and enthusiasts to use the open-source code as a foundation for community-driven projects, which add new features for advanced users^[19] or bring Android to devices originally shipped with other operating systems. At the same time, as Android has no centralised update system most Android devices fail to receive security updates: research in 2015 concluded that almost 90% of Android phones in use had known but unpatched security vulnerabilities due to lack of updates and support.^[20][21] The success of Android has made it a target for patent litigation as part of the so-called "smartphone wars" between technology companies.^[22][23]

Symbian

Symbian was a closed-source^[3] mobile operating system (OS) and computing platform designed for smartphones.^[6] Symbian was originally developed by Symbian Ltd.,^[7] as a descendant of Psion's EPOC and runs exclusively on ARM processors, although an unreleased x86 port existed.
Symbian was previously an open-source platform developed by the now defunct Symbian Foundation in 2009, as the successor of the original Symbian OS. Symbian was used by many major mobile phone brands, like Samsung, Motorola, Sony Ericsson, and above all by Nokia. It was the most popular smartphone OS on a worldwide average until the end of 2010, when it was overtaken by Android.
Symbian rose to fame from its use with the S60 platform built by Nokia, first released in 2002 and powering most Nokia smartphones. UIQ, another Symbian platform, ran in parallel, but these two platforms were not compatible with each other. Symbian^3 was officially released in Q4 2010 as the successor of S60 and UIQ, first used in the Nokia N8, to use a single platform for the OS. In May 2011 an update, Symbian Anna, was officially announced, followed by Nokia Belle (previously Symbian Belle) in August 2011.^[8][9]
On 11 February 2011, Nokia announced that it would use Microsoft's Windows Phone OS as its primary smartphone platform, whilst Symbian would be gradually wound down.^[10][11] On 22 June 2011 Nokia signed an agreement for Accenture to provide Symbian-based software development and support services to Nokia through 2016; about 2,800 Nokia employees became Accenture employees as of October 2011.^[12] The transfer was completed on 30 September 2011.^[6] The Nokia 808 PureView is officially the last Symbian smartphone from Nokia.^[13] In January 2014 Nokia stopped accepting new or changed Symbian software from developers, effectively terminating its support of the operating system.^[14]
Several non-Nokia companies are still releasing new Symbian phones after Nokia stopped releasing new phones, like F-07F from Fujitsu^[15] or SH-07F from Sharp,^[16] as late as mid-2014.

Contents

• 1 History
• 2 Features
  • 2.1 User interface
  • 2.2 Browser
  • 2.3 Multiple language support
  • 2.4 Application development
• 3 Application development
  • 3.1 Qt
  • 3.2 Symbian C++
  • 3.3 Other languages
  • 3.4 Deployment
• 4 Architecture
  • 4.1 Technology domains and packages
  • 4.2 Symbian kernel
  • 4.3 Design
  • 4.4 Operating system
• 5 Symbian UI variations and platforms
• 6 Symbian (S60) version comparison
• 7 Market share and competition
• 8 Criticism
  • 8.1 Malware
  • 8.2 Bypassing platform security
• 9 Version history
• 10 See also
  • 10.1 General
  • 10.2 Development-related
  • 10.3 Applications
• 11 References
• 12 Bibliography
• 13 External links
  • 13.1 Symbian^3 EPL Source

History

Main articles: EPOC (operating system), S60 (software platform), MOAP and UIQ

The Symbian logo until April 2009

Symbian originated from EPOC, an operating system created by Psion in the 1980s. In June 1998, Psion Software became Symbian Ltd., a major joint venture between Psion and phone manufacturers Ericsson, Motorola, and Nokia.
Afterwards, different software platforms were created for Symbian, backed by different groups of mobile phone manufacturers. They include S60 (Nokia, Samsung and LG), UIQ (Sony Ericsson and Motorola) and MOAP(S) (Japanese only such as Fujitsu, Sharp etc.).
In June 2008, Nokia 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, UIQ and MOAP(S) were contributed by their owners Nokia, NTT DoCoMo, Sony Ericsson 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 has been 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.^[17]
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 has been maintaining its own code repository for the platform development, regularly releasing its development to the public repository.^[18] 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.^[17][19]
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.^[20]
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 Samsung^[21] and Sony Ericsson), it would transition to a licensing-only organisation;^[22] Nokia announced it would take over the stewardship of the Symbian platform. Symbian Foundation will remain the trademark holder and licensing entity and will only have non-executive directors involved.
On 11 February 2011, Nokia announced a partnership with Microsoft that would see it adopt Windows Phone as its primary smartphone platform,^[23] and Symbian will be its franchise platform (dropping Symbian as its main smartphone OS of choice).^[11] As a consequence, the use of the Symbian platform for building mobile applications dropped 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.^[24]
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.^[5] Source code released under the EPL remains available in third party repositories.^[25][26]
On 22 June 2011, Nokia made an agreement with Accenture 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.^[12] The transfer was completed on 30 September 2011.^[6]
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. ^[27]

Features

User interface

Main menu of the original S60v3

Main menu of Symbian S60v5

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 Qt Quick with QML, the new high-level declarative UI 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. 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.^[28][29]

Browser

Main articles: S60 browser and Opera Mobile

Symbian^3 and earlier have a built-in WebKit based browser. Symbian was the first mobile platform to make use of WebKit (in June 2005).^[30] Some older Symbian models have Opera Mobile as their default browser.
Nokia released a new browser with the release of Symbian Anna with improved speed and an improved user interface.^[31]

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 dialects] (and scripts) in Symbian Belle are:

Arabic (Arabic), Basque (Latin), Bulgarian (Cyrillic), Catalan (Latin), Chinese [PRC] (Simplified Chinese), Chinese [Hong Kong] (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 Indonesia] (Latin),

Italian (Latin), Japanese (Japanese script)* Kazakh (Cyrillic), Latvian (Latin), Lithuanian (Latin), Malay [Bahasa Malaysia] (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 America] (Latin), Swedish (Latin), Tagalog [Filipino] (Latin), Thai (Thai), 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

Symbian v9.3 with a S60v3 interface, on a Nokia 6710

From 2010, Symbian switched to using standard C++ with Qt as the main SDK, which can be used with either Qt Creator or Carbide.c++. Qt supports the older Symbian/S60 3rd (starting with Feature Pack 1, aka S60 3.1) and Symbian/S60 5th Edition (aka S60 5.01b) releases, as well as the new Symbian platform. It also supports Maemo and MeeGo, Windows, Linux and Mac OS X.^[32][33]
Alternative application development can be done using Python (see Python for S60), Adobe Flash Lite or Java ME.
Symbian OS previously used a Symbian specific C++ version, along with Carbide.c++ integrated development environment (IDE), as the native application development environment.
Web Run time (WRT) is a portable application framework that allows creating widgets on the S60 Platform; it is an extension to the S60 WebKit based browser that allows launching multiple browser instances as separate JavaScript applications.^[34][35]

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).^[32][36] 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.^[37] Application development can either use C++ or QML.

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 kit (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 cross-compiler) 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 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 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 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 via the Carbide.vs plugin.

Other languages

Symbian v9.1 with a S60v3 interface, on a Nokia E61

Symbian devices can also be programmed using Python, Java ME, Flash Lite, Ruby, .NET, Web Runtime (WRT) Widgets and Standard C/C++.^[38]
Visual Basics programmers can use NS Basic to develop apps for S60 3rd Edition and UIQ 3 devices.
In the past, Visual Basic, Visual Basic .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 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 Xcode IDE for Mac OS X was available.^[39]
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 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

Symbian Belle, on a Nokia C7

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).^[40] Applications can now be signed for free.^[41]

Architecture

Technology domains and packages

Symbian's design is subdivided into technology domains,^[42] each of which comprises a number of software packages.^[43] 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^[44] 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.^[45] The real-time kernel has a microkernel architecture containing only the minimum, most basic primitives and functionality, for maximum robustness, availability and responsiveness. It has been termed a nanokernel, because it needs an extended kernel to implement any other abstractions. It contains a scheduler, memory management and device drivers, with networking, telephony and file system 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 VMS 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 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 descriptors and a cleanup stack. 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 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:

• UI Framework Layer
• Application Services Layer
  • Java ME
• 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 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, 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.

Symbian UI variations and platforms

Symbian, as it advanced to OS version 7.0, began to spun off into several different user interfaces or UIs, each back by a certain company or group of companies. Unlike Android OS with its different cosmetic UIs, Symbian UIs are deeper in code modifications and integrations (therefore referred to as UI platforms). Things began more complicated when applications developed for different Symbian UIs platforms are not compatible with each other, and this led to OS fragmentation.^[46]
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 (Nokia N70, S60 3rd Edition (Nokia N73) and touch-based S60 5th Edition (Nokia N97). The name, S60, was dropped after the formation of Symbian Foundation and renames itself as Symbian^1, 2 and 3.

• Series 80

Used by Nokia Communicators such as Nokia 9300i.

• Series 90

Touch and button based. Only phone using this platform is Nokia 7710.

• UIQ

Backed mainly by Sony Ericsson and then Motorola, 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 versions into one led to the adoption of S60 as the version going forward.^[47]

• MOAP (Mobile Oriented Applications Platform) [Japan Only]

Used by Fujitsu, Mitsubishi, Sony Ericsson and Sharp developed phones for NTT DoCoMo. It uses an interface developed specifically for DoCoMo's FOMA "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)

• OPP [Japan Only], successor of MOAP, used on NTT DoCoMo's FOMA phone.

Symbian (S60) version comparison

Feature	Symbian^3/Anna/Belle	Symbian^2[48]	Symbian^1/Series 60 5th Edition	Series 60 3rd Edition	Series 80
Year released	2010 (Symbian^3), 2011 (Symbian Anna, Nokia Belle)	2010 (Japan only with MOAP/OPP middleware)	2008	2006	2001
Company	Symbian Foundation	Symbian Foundation	Symbian Foundation	Nokia	Nokia
Symbian OS version	9.5 (Symbian^3/Symbian Anna), 10.1 (Nokia Belle)	?	9.4	9.3
Series 60 version	5.2 (Symbian^3/Symbian Anna),[49] 5.3 (Nokia Belle), 5.4 (Nokia Belle FP1)	5.1	5th Edition	3rd Edition Feature Pack 2	N/A
Touch input support	Yes	Yes	Yes	No	No
Multi touch input support	Yes		No	No	No
Number of customizable home screens	Three to six (Five on Nokia E6 and Nokia 500, six on Nokia Belle)		One	Two	One
Wi-Fi version support	B, G, N		B, G	B, G	B, G
USB on the go support	Yes		No	No
DVB-H support	Yes, with extra headset[50]	Unknown, but have 1seg support[51]	Yes, with extra headset	Yes, with extra headset
Short range FM transmitter support	Yes		Yes	Yes	No
FM radio support	Yes	?	Yes	Yes	No
External Storage Card Support	MicroSD, up to 32GB	MicroSD	MicroSD	MicroSD, MiniSD	MultiMedia Card
Adobe Flash support	Yes, Flash Lite native version 4.0, upgradable		Yes, Flash Lite native version 3.1, upgradable	Yes, Flash Lite native version 3.1, upgradable	Yes, Flash native version 6, not upgradable
Microsoft Silverlight support	No[52][citation needed]		Yes[53][54]	No[55][citation needed]	No
OpenGL ES support	Yes, version 2.0				No
SQLite support	Yes		Yes	Yes[56]
CPU architecture support	ARM	SH-Mobile	ARM	ARM	ARM
Programmed in	C++, Qt	?	C++, Qt	C++, Qt
License	Eclipse Public License; Since 31 March 2011: Nokia Symbian License 1.0	proprietary SFL license, while some portions of source code are EPL licensed.
Public issues list	No more
Package manager	.sis, .sisx	?	.sis, .sisx	.sis, .sisx	.sis, .sisx
Non English languages support	Yes	mainly Japanese	Yes	Yes	Yes
Underlining spell checker	Yes	Yes[57]	Yes	Yes
Keeps state on shutdown or crash	No		No	No	No
Internal search	Yes	Yes[51]	Yes	Yes	Yes
Proxy server	Yes	?	Yes	Yes	Yes
On-device encryption	Yes	Yes[51]	Yes	Yes
Cut, copy, and paste support	Yes	Yes[57]	Yes	Yes	Yes
Undo	No		No	Yes	Yes
Default Web Browser for S60, WebKit engine	version 7.2, engine version 525 (Symbian^3);[58] version 7.3, engine version 533.4 (Symbian Anna)		version 7.1.4, engine version 525; version 7.3, engine version 533.4 (for 9 selected units after firmware updates released in summer 2011)	engine version 413 (Nokia N79)	N/A
Official App Store	Nokia Ovi Store	i-αppli/i-Widget[57]	Nokia Ovi Store, Sony Ericsson PlayNow Arena	Nokia Ovi Store, Download!
Email sync protocol support	POP3, IMAP	i-mode mail[57]	POP3, IMAP	POP3, IMAP	POP3, IMAP
NFC Support	Yes	No	No	No	No
Push alerts	Yes		Yes	Yes	Yes
Voice recognition	Yes	Yes	Yes	Yes
Tethering	USB, Bluetooth; mobile Wi-Fi hotspot, with third-party software		USB, Bluetooth; mobile Wi-Fi hotspot, with third-party software	USB, Bluetooth; mobile Wi-Fi hotspot, with third-party software	USB, Bluetooth;
Text, document support	Mobile Office Applications, PDF	Mobile Office Applications, PDF	Mobile Office Applications, PDF	Mobile Office Applications, PDF	Mobile Office Applications, PDF
Audio playback	All	wma,[51] aac[citation needed]	All	All	wav, mp3
Video playback	H.263, H.264, WMV, MPEG4, MPEG4@ HD 720p 25–30 frame/s, MKV, DivX, XviD	WMV,[57] MPEG4[citation needed]	H.263, WMV, MPEG4, 3GPP, 3GPP2	H.263, WMV, MPEG4, 3GPP, 3GPP2	H.263, 3GPP, 3GPP2
Turn-by-turn GPS	Yes, with third-party software, or Nokia Maps	Yes, with monthly paid Docomo Map Navi[59] (ドコモ地図ナビ[60]?)	Yes, with third-party software, or Nokia Maps	Yes, with third-party software, or Nokia Maps	Yes, with third-party software
Video out	Nokia AV (3.5mm), PAL, NTSC, HDMI, DLNA via Nokia Play To	HDMI, and	Nokia AV (3.5mm), PAL, NTSC	Nokia AV (3.5mm), PAL, NTSC	No
Multitasking	Yes	Yes	Yes	Yes	Yes
Desktop interactive widgets	Yes	Yes	Yes	No
Integrated hardware keyboard	Yes	Yes	Yes	Yes	Yes
Bluetooth keyboard	Yes	Yes[51]	Yes	Yes	Yes
Video conference front video camera	Yes	Yes	Yes	Yes	Yes
Can share data via Bluetooth with all devices	Yes	Yes	Yes	Yes	Yes
Skype, third-party software	Yes[61]		Yes[61]	Yes[61]
Facebook IM chat	Yes	?	Yes	Yes
Secure Shell (SSH)	Yes, third-party software		Yes, third-party software	Yes, third-party software
OpenVPN	No, Nokia VPN can be used		No, Nokia VPN can be used	No, Nokia VPN can be used	Yes, third-party software
Remote frame buffer	?
Screenshot	Yes, third-party software[62]		Yes, third-party software[62]	Yes, third-party software[62]	Yes
GPU acceleration	Yes				No
Official SDK platform(s)	Cross-platform, Windows (preferred is Qt), Carbide.c++, Java ME, Web Runtime Widgets (WRT), Flash lite, Python for Symbian		Cross-platform, Windows (preferred is Qt), Carbide.c++, Java ME, Web Runtime Widgets (WRT), Flash lite, Python for Symbian	Cross-platform, Windows (preferred is Qt), Carbide.c++, Java ME, Web Runtime Widget (WRT), Flash lite, Python for Symbian	Cross-platform, Windows (preferred is Qt), Carbide.c++, Java ME, third-party software (OPL)
Status of updates	Discontinued	?	Discontinued	Discontinued	Discontinued
First device(s)	Nokia N8 (Symbian^3), Nokia C7 (Symbian^3), Nokia X7, Nokia E6 (Anna), Nokia 603, Nokia 700, Nokia 701 (Belle)	NTT DOCOMO STYLE Series F-07B	Nokia 5800 (2 October 2008)	Nokia N96, Nokia N78, Nokia 6210 Navigator and Nokia 6220 Classic (11 February 2008)	Nokia 9210
Devices	Nokia N8, Nokia C6-01, Nokia C7-00, Nokia E7-00, Nokia E6, Nokia X7, Nokia 500, Nokia 603, Nokia 600 (cancelled), Nokia 700, Nokia 701, Nokia 808 PureView	NTT DoCoMo: F-06B*,[63] F-07B*,[63] F-08B*,[63] SH-07B†,[63] F-10B,[64] Raku-Raku Phone 7,[64] F-01C*,[65] F-02C*,[65] F-03C*,[65] F-04C*,[65] F-05C*,[65] SH-01C†,[65] SH-02C†,[65] SH-04C†,[65] SH-05C†,[65] SH-06C†,[65] Touch Wood SH-08C†[65]	Nokia: 5228, 5230, 5233, 5235, 5250, 5530 XpressMusic, 5800 XpressMusic, 5800 Navigation Edition, C5-03, C6-00, N97, N97 mini, X6; Samsung: i8910 Omnia HD,[66] Sony Ericsson: Satio, Vivaz, Vivaz Pro	Nokia: 5320 XpressMusic, 5630 XpressMusic, 5730 XpressMusic, 6210 Navigator, 6220 Classic, 6650 fold, 6710 Navigator, 6720 Classic, 6730 Classic, 6760 Slide, 6790 Surge, E5-00, E51, E52, E55, E71, E72, E75, N78, N79, N82, N85, N86 8MP, N96, X5, C5-00; Samsung: GT-i8510 (INNOV8), GT-I7110, SGH-L870, SGH-i550w	Nokia 9210, Nokia 9300, Nokia 9300i, Nokia 9500
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	Series 80

* manufactured by Fujitsu
† manufactured by Sharp

Market share and competition

On 16 November 2006, the 100 millionth smartphone running the OS was shipped.^[67] As of 21 July 2009, more than 250 million devices running Symbian OS had been produced.^[68]
In 2006, Symbian had 73% of the smartphone market,^[69] compared with 22.1% of the market in the second quarter of 2011.^[70]
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.^[71] 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.^[72]
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 Windows CE and Windows Mobile) and Android having 4.7%.^[71]
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).^[73] Some estimates indicate that the number of mobile devices shipped with the Symbian OS up to the end of Q2 2010 is 385 million.^[74]
Over the course of 2009–2010, Motorola, Samsung, LG, and Sony Ericsson announced their withdrawal from Symbian in favour of alternative platforms including Google's Android, Microsoft's Windows Phone.^{[75][76][77][78]}
In Q2 2012 according to IDC worldwide market share has dropped to an all-time low of 4.4%.^[79]

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.^[80] 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 his 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 RAM installed in the phone).^[81]
In November 2010, Smartphone blog All About Symbian criticized the performance of Symbian's default web browser and recommended the alternative browser Opera Mobile.^[82] Nokia's Senior Vice President Jo Harlow promised an updated browser in the first quarter of 2011.^[83]
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.^[84]

Malware

Main article: Mobile virus

See also: Mobile security

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, purporting to be a utility, 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 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 a patch for Symbian S60 mobile phones. When installed, it drops^{[clarification needed]} 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,^{[citation needed]} 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 the form of 'cooked firmware' was demonstrated at the International Malware Conference, MalCon, December 2010, by Indian hacker Atul Alex.^[85][86]

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.^[87] 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 unsigned code can be executed.^[88]

Version history

Version	Description
EPOC16	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 ROM. 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 1-bit-per-pixel, keyboard-operated graphical interface[89] — the hardware for which it was designed originally had pointer 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.
EPOC32 (releases 1 to 5)	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 / Revo plus, Psion Series 7 / netBook 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 interface. The Psion line of PDAs come with a graphical user interface called EIKON which is specifically tailored for handheld machines with a keyboard (thus looking perhaps more similar to desktop GUIs than palmtop GUIs[90]). 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 ARM family of processors, including the ARM7, ARM9, StrongARM and Intel's XScale, 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 Geofox, which halted production with less than 1,000 units sold. Ericsson marketed a rebranded Psion Series 5mx called the MC218, and later created the EPOC Release 5.1 based smartphone, the R380. Oregon Scientific also released a budget EPOC device, the Osaris (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 Osaris was the only PDA to use the ER4. The Psion Series 5mx, Psion Series 7, Psion Revo, Diamond Mako, Psion netBook and Ericsson MC218 were released in 1999 using ER5. A phone project was announced at CeBIT, 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 Unicode. In June 1998, Psion Software became Symbian Ltd., a major joint venture between Psion and phone manufacturers Ericsson, Motorola, and Nokia. As of Release 6, EPOC became known simply as Symbian OS.
Symbian OS 6.0 and 6.1	The OS was renamed Symbian OS and was envisioned as the base for a new range of smartphones. 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. Bluetooth 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 UIQ 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 Sendo X 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 MOAP standard.
Symbian OS 7.0 and 7.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 3230, 6260, 6600, 6670, 7610) as well as several FOMA phones in Japan. It also added EDGE support and IPv6. Java support was changed from pJava 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 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 8.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 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 CDMA, 3G, two-way data streaming, DVB-H, and OpenGL ES with vector graphics and direct screen access.
Symbian OS 8.1	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, Nokia's first in Nseries.
Symbian OS 9.0	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.
Symbian OS 9.1	Released early 2005. It includes many new security related features, including platform security module facilitating mandatory code signing. The new ARM EABI 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.[91] Support for Bluetooth 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.
Symbian OS 9.2	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.
Symbian OS 9.3	Released on 12 July 2006. Upgrades include improved memory management and native support for Wifi 802.11, HSDPA. 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.
Symbian OS 9.4	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, SQL support is provided by SQLite. 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	Symbian^2 is a version of Symbian that only used by Japanese manufacturers[citation needed], started selling in Japan market since May 2010.[92] The version is not used by Nokia.[93]
Symbian^3 (Symbian OS 9.5) and Symbian Anna	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.
Nokia Belle (Symbian OS 10.1)	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.[94] 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.[95] Nokia officially renamed Symbian Belle to Nokia Belle in a company blog post.[96][97] 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.[98] 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. 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).[99] 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.[100]

See also

General

• Android
• Bada
• EKA2 current Symbian kernel, successor of EKA1
• EPOC (operating system)
• List of Symbian devices
• MOAP user interface
• Nokia Ovi suite
• Series60-Remote
• 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
• S60, Series 60, user interface used by Nokia and others
  • Web Browser for S60 default web browser
• Ovi store Nokia's application store on the Internet, not limited to Symbian
• Symbian Foundation
• Symbian Ltd.

Development-related

• Accredited Symbian Developer
• Active object (Symbian OS)
• Carbide.c++, alternative application and OS development IDE
• Cleanup stack
• P.I.P.S. Is POSIX on Symbian
• Python for S60, alternative application development language
• Qt (framework), preferred development tool, both for the OS and applications, not limited to Symbian
  • Qt Creator IDE
  • Qt Quick
  • QML, JavaScript based language

Applications

• See category:Symbian software

References

1. Nokia and Accenture Finalize Symbian Software Development and Support Services Outsourcing Agreement
2. Lextrait, Vincent (January 2010). "The Programming Languages Beacon, v10.0". Retrieved 5 January 2010.
3. Nokia transitions Symbian source to non-open license. Ars Technica. Retrieved on 2014-06-12.
4. Lee Williams Symbian on Intel's Atom architecture at the Wayback Machine (archived April 19, 2009). blog.symbian.org. 16 April 2009
5. "Not Open Source, just Open for Business". symbian.nokia.com. 2011-04-04. Archived from the original on 2012-03-16. Retrieved 2014-08-23.
6. Lunden, Ingrid (2011-09-30). "Symbian Now Officially No Longer Under The Wing Of Nokia, 2,300 Jobs Go". moconews.net. Retrieved 30 September 2011.
7. "infoSync Interviews Nokia Nseries Executive". Infosyncworld.com. 2010-06-24. Archived from the original on 2011-07-13. Retrieved 2010-08-12.
8. Nokia announces Symbian 'Anna' update for N8, E7, C7 and C6-01; first of a series of updates (video). Engadget. Retrieved on 2011-09-25.
9. Nokia announces Symbian Belle alongside three new devices. Engadget. Retrieved on 2011-09-25.
10. Nokia's new strategy and structure, Symbian to be a "franchise platform", MeeGo still in long term plans - All About MeeGo
11. RIP: Symbian. Engadget. Retrieved on 2011-09-25.
12. Epstein, Zach. (2011-06-23) Symbian is officially no longer Nokia's problem. Bgr.com. Retrieved on 2011-09-25.
13. Techcrunch, "Nokia Confirms The PureView Was Officially The Last Symbian Phone", "Techcrunch", 2013-01-24 as by Nokia on January 24, 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"
14. Tung, Liam. "Nokia says final sayonara to Symbian and MeeGo apps as store freezes updates". ZDnet. CBS Interactive. Retrieved 16 February 2015.
15. https://www.nttdocomo.co.jp/support/trouble/manual/download/f07f/index.html
16. https://www.nttdocomo.co.jp/support/trouble/manual/download/sh07f/download.html
17. Menezes, Gary. (2010-09-11) Symbian OS, Now Fully Open Source. Watblog.com. Retrieved on 2011-09-25.
18. Symbian OS – one of the most successful failures in tech history. TechCrunch.com. 8 November 2010
19. Symbian Foundation (2010-02-04), Symbian Completes Biggest Open Source Migration Project Ever, retrieved 2010-02-07
20. "Symbian Foundation website, members section".
21. No current plans for Samsung Symbian handsets
22. Symbian Foundation
23. Open Letter from CEO Stephen Elop, Nokia and CEO Steve Ballmer, Microsoft – Nokia Conversations : the official Nokia blog
24. "Developer Economics 2011".
25. symbian-dump | Download symbian-dump software for free at. Sourceforge.net. Retrieved on 2011-09-25.
26. symbian-incubation-projects – Symbian Incubation Projects – Google Project Hosting. Code.google.com. Retrieved on 2011-09-25.
27. "New Symbian and Meego Applications not allowed in Nokia Stores from Jan 1st".
28. Nokia PR (21 October 2010). "Nokia further refines development strategy to unify environments for Symbian and MeeGo". Retrieved 2010-11-05.
29. AllAboutSymbian (26 October 2010). "The future of the Symbian platform". Retrieved 2010-11-05.
30. Nokia PR (24 May 2006). "Nokia releases 'Web Browser for S60' engine code to open source community". press.nokia.com. Retrieved 2007-03-21.
31. Browser and Maps updates for many S60 3rd Edition and S60 5th Edition phones. All About Symbian (2011-06-29). Retrieved on 2011-09-25.
32. "Symbian — Qt – A cross-platform application and UI framework". Qt.nokia.com. Retrieved 2010-08-12.
33. Nokia Developer (2010-06-18), Nokia Qt SDK, retrieved 2012-01-20
34. Apps:Mobile Web Apps in a Nutshell. symlab.org wiki
35. Nokia Developer – Web. Forum.nokia.com. Retrieved on 2011-09-25.
36. "Qt Labs Blogs " Nokia Qt SDK 1.0 released". Labs.trolltech.com. Retrieved 2010-08-12.
37. "Qt Labs Blogs " Qt Simulator is going public". Labs.trolltech.com. Retrieved 2010-08-12.
38. "Symbian developer community". Developer.symbian.org. 2010-01-27. Retrieved 2010-08-12.
39. Tom Sutcliffe and Jason Barrie Morley Xcode Symbian support. Symbian-xcode-plugin.tigris.org. Retrieved on 2011-09-25.
40. "Capabilities (Symbian Signed) – Symbian Developer Community". Developer.symbian.org. Retrieved 2010-08-12.
41. Nokia Developer News | Nokia Now Signing Symbian Apps for Free – Nokia Developer Blogs. Blogs.forum.nokia.com (2010-08-16). Retrieved on 2011-09-25.
42. "Symbian developer community – technology domains". Developer.symbian.org. Retrieved 2010-08-12.
43. "Symbian developer community – packages". Developer.symbian.org. Retrieved 2010-08-12.
44. "Symbian System Model – Symbian Developer Community". Developer.symbian.org. Retrieved 2010-08-12.
45. Introducing EKA2, by Jane Sales with Martin Tasker. (PDF) . Retrieved on 2011-09-25.
46. The History of Symbian's Secret Fragmentation
47. UIQ Technology puts remaining staff on notice
48. Symbian Blog - Symbian^ 2 – History
49. Nokia N8 User Agent Profile. Nds.nokia.com (1999-02-22). Retrieved on 2011-09-25.
50. Nokia launches mobile TV | Nokia Conversations – The official Nokia Blog. Conversations.nokia.com (2010-09-09). Retrieved on 2011-09-25.
51. "F-07B Instruction Manual ’10.5" (PDF). docomo STYLE series. NTT DoCoMo. May 2010. Retrieved 2012-05-23.
52. "Any plans to have SilverLight for Symbian^3 (Nokia N8,E7,C7) ?". Mobile / Silverlight for Nokia Symbian. Silverlight.NET Forums. 2011-04-27. Retrieved 2012-05-23.
53. Psychlist1972 (2010-07-06). "Silverlight for Nokia Symbian RTW Now Available". Mobile / Silverlight for Nokia Symbian. Silverlight.NET Forums. Retrieved 2012-05-23.
54. Obsolete. Silverlight.NET. Retrieved on 2011-09-25.
55. Silverlight Category
56. Inside Symbian SQL: A Mobile Developer's Guide to SQLite | By Ivan Litovski, Richard Maynard, 2010, page 9
57. SH-08C Instruction Manual ’11.3 (PDF), NTT DoCoMo, March 2011, retrieved 2012-05-23
58. "Help – Eclipse Platform". library.forum.nokia.com. Retrieved 2011-09-25.
59. ドコモ地図ナビ (@docomo_map_navi) op Twitter
60. ドコモ地図ナビ
61. on your Mobile. Skype. Retrieved on 2011-09-25.
62. Screenshot for Symbian OS | AntonyPranata.com 2.0. Antonypranata.com. Retrieved on 2011-09-25.
63. Horikawa, Kyoko (2010-06-01). "NTT DoCoMo releases S^2 devices". Symbian Blog. Symbian.org. Archived from the original on 2010-08-24.
64. Asuk Ustundag, Sennur (2010-10-07). "SYMBIAN Devices, Hardware & Software Requirements, Basic App Development" (PDF). Bridgewater State University. p. 6. Retrieved 2012-05-23.
65. "Symbian^2 platform used in eleven new models of NTT DoCoMo FOMA 3G handsets". SymbianOne. Retrieved 2010-11-10.
66. "Samsung OMNIAHD Dazzles at Mobile World Congress with Its HD Brilliance". United Kingdom: Samsung.com. Archived from the original on 10/04/2009. Retrieved 2011-09-25. Check date values in: |archive-date= (help)
67. "Six Years of Symbian Produces 100 Models and 100 Million Shipments". The Smart PDA. 2006-11-17. Retrieved 2012-05-23.
68. Symbian Foundation Adds New Member, Nuance. News.softpedia.com (2009-07-21). Retrieved on 2011-09-25.
69. "Nokia Leading Smartphone Market with 56%, While Symbian's Share of OS Market Is Set to Fall" (Press release). ABI Research. 2012-03-29. Archived from the original on 2012-03-29. Retrieved 2011-09-25.
70. 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 on 2011-09-25.
71. "Majority of smart phones now have touch screens (Canalys press release: r2010021)". Canalys.com. 2010-02-08. Retrieved 2010-08-12.
72. "BBC News – Google Android phone shipments increase by 886%". Bbc.co.uk. 2010-08-02. Retrieved 2010-08-12.
73. Pettey, Christy. "Gartner Says Worldwide Mobile Device Sales to End Users Reached 1.6 Billion Units in 2010; Smartphone Sales Grew 72 Percent in 2010". Gartner.com. Retrieved 2011-03-10.
74. 100 Million Club H1 2010. VisionMobile (2010-10-18). Retrieved on 2011-09-25.
75. Nokia and Microsoft enter strategic alliance on Windows Phone, Bing, Xbox Live and more. Engadget. Retrieved on 2011-09-25.
76. Woods, Ben. (2010-10-01) Samsung to drop Symbian support | Wireless – CNET News. News.cnet.com. Retrieved on 2011-09-25.
77. Meyer, David. (2008-11-03) Motorola ditches Symbian, announces 3,000 layoffs | Networking | ZDNet UK. Zdnet.co.uk. Retrieved on 2011-09-25.
78. Mello, John P.. (2010-10-15) Sony Ditches Symbian. PCWorld. Retrieved on 2011-09-25.
79. "Google's Android smartphone market share quadruples Apple's iOS". CNN. 8 August 2012.
80. Mobile-reviews. Review of Nokia E7. 9 August 2011
81. Litcfield, Steve (2011-08-08). "Nokia N97 RIP: the derailed flagship that ended up as a train wreck". All About Symbian. Retrieved 2012-10-30.
82. Mobile browser comparison, November 2010. Allaboutsymbian.com (2010-11-25). Retrieved on 2011-09-25.
83. Meyer, David (9 November 2010). "Nokia times first Symbian updates for 'early 2011'". ZDNet UK. Retrieved 4 January 2011.
84. Gilson, David (2012-03-12). "The History of Symbian's Secret Fragmentation". All About Symbian. Retrieved 2012-10-30.
85. Hacker plants back door in Symbian firmware – The H Security: News and Features at the Wayback Machine (archived December 8, 2013). H-online.com (2010-12-08). Retrieved on 2011-09-25.
86. Hacker Creates Modified Symbian S60 Firmware with Hidden Back Door. Live Hacking (2010-12-10). Retrieved on 2011-09-25.
87. Nokia's S60 3rd Ed security has been hacked?, Symbian Freak
88. ''S60 v3 Hacking – Mission accomplished, FP1 hacked!''. Symbian Freak (2008-03-27). Retrieved on 2011-09-25.
89. Sibo3a screenshots, Guide Book Gallery
90. Marcin Wichary. "GUIdebook - Screenshots - EPOC R5/Psion Revo". Guidebookgallery.org. Retrieved 2010-08-12.
91. Solution to Nokia Slow SMS / Hang Problem
92. Blanford, Rafe (2010-06-01). "First Symbian^2 phones ship in Japan". Retrieved 2012-10-30.
93. Nokia: go straight to Symbian 3, skip Symbian 2 • Reg Hardware
94. Molen, Brad (2011-08-17). "Symbian Belle download leaked to N8 community, quickly pulled from site (update: Anna available on NaviFirm)". engadget. Retrieved 2012-10-30.
95. Bobleanta, Vlad (2011-08-24). "Nokia 600, 700, and 701 announced, all running Symbian Belle and coming before the end of September". unwired view. Retrieved 2012-10-30.
96. Nokia Belle coming soon – Nokia Conversations : the official Nokia blog
97. Reisinger, Don (2011-12-21). "So long, Symbian Belle. Hello, Nokia Belle". c|net. Retrieved 2012-10-30.
98. "Software Update for Nokia Belle-compatible phones". Nokia. 2012. Retrieved 2012-10-30.
99. Delaney, Ian (2012-03-01). "All about Nokia Belle, Feature Pack 1". Nokia Conversations. Retrieved 2012-10-30.
100. Ly, Boc (2012-10-02). "Update makes the Nokia 808 PureView even better". Nokia Conversations. Retrieved 2012-10-30.