what you think about symbian softwares

they rock

thank you for creating such a great discussion.. i love to reply in this tag.. thank you for sharing with us... yes i agree with you..

Symbian OS is an operating system, designed for mobile devices, with associated libraries, user interface frameworks and reference implementations of common tools, produced by Symbian Ltd. It is a descendant of Psion's EPOC and runs exclusively on ARM processors. Symbian is currently owned by Ericsson (15.6%), Nokia (47.9%), Panasonic (10.5%), Samsung (4.5%), Siemens AG (8.4%), and Sony Ericsson (13.1%). Whilst BenQ has acquired the mobile phone subsidiary of Siemens AG the Siemens AG stake in Symbian does not automatically pass to BenQ - this will need the approval of the Symbian Supervisory Board.Symbian OS, with its roots in Psion Software's EPOC is structured like many desktop operating systems, with pre-emptive multitasking, multithreading, and memory protection. Symbian OS's major advantage is the fact that it was built for handheld devices, with limited resources, that may be running for months or years. There is a strong emphasis on conserving memory, using Symbian-specific programming idioms such as descriptors and a cleanup stack. Together with other techniques, these keep memory usage low and memory leaks rare. There are similar techniques for conserving disk space (though the disks on Symbian devices are usually flash memory). Furthermore, all Symbian OS programming is event-based, and the CPU is switched off when applications are not directly dealing with an event. This is achieved through a programming idiom called active objects. Correct use of these techniques helps ensure longer battery life. All of this makes Symbian OS's flavour of C++[citation needed] very specialised, with a gradual learning curve[citation needed]. However, many Symbian OS devices can also be programmed in OPL, Python, Visual Basic, Simkin, and Perl - together with the Java ME and PersonalJava flavours of Java. There are a number of smartphone user interface platforms based on Symbian OS, including open platforms UIQ, Nokia's Series 60, Series 80 and Series 90 and closed platforms such as that developed for NTT DoCoMo's FOMA handsets. This adaptability allows Symbian OS to be used on smartphones with a variety of form factors (e.g. clam-shell or "monoblock"/"candybar", keypad- or pen-driven).Symbian OS is often seen as competing with other mobile operating systems, such as Windows Mobile, Palm OS, and Linux. It primarily competes with the embedded operating systems[citation needed] used on lower-end phones, such as NOS and OSE, which tend to be maintained by the phone companies themselves. SymbianOS, like its smartphone competition, has long been encumbered by the need for two processor cores in order that it can ensure separation between the mobile network and the user's applications. This means that SymbianOS phones have tended to be larger, heavier, more expensive and less power-efficient[citation needed] than featurephones with similar capabilities. Symbian OS' major advantage over the embedded operating systems used in featurephones is its modularity - there is runtime linking between dynamically linked shared libraries (DLLs, see dynamic linking) on the device, and an emphasis on plug-in architectures. This makes complex phones quicker to develop[citation needed], though this is sometimes offset by the complexity of Symbian OS C++ and the awkwardness of going to another company for an OS (instead of doing it in-house). The advantages over other OS's such as Linux or Windows Mobile are more debatable. Phone vendors and network operators like the customisability of Symbian OS relative to Windows[citation needed]. This customisability, though, makes integrating a Symbian OS phone more difficult. It's possible that Linux goes too far in the other direction[citation needed], and is simply too hard to make a phone from at the moment (a fact that may change with Trolltech's introduction of the Greenphone). Symbian OS's ground-up design for mobile devices should make it more power-and memory-efficient[citation needed], as well as being flexible. SymbianOS EKA2 also supports hard enough real-time operation that it is possible to build a single-core phone around it- that is, a phone in which a single processor core executes both the user applications and the signalling stack. This is not a feature that is available from Linux or Windows CE. This has allowed SymbianOS EKA2 phones to become smaller, cheaper and more power efficient. Recently published statistics show that Symbian OS has a 67% share of the 'smart mobile device' market, with Microsoft having 15% and RIM having 6%.At its lowest level sit the base components of Symbian OS. This includes the kernel (EKA1 or EKA2 - see the 'History' section), along with the user library which allows user-side applications to request things of the kernel. Symbian OS has a microkernel architecture, which means that the minimum necessary is within the kernel. It contains a scheduler and memory management, but no networking or filesystem support. These things are provided by user-side servers. The base layer includes the file server, which provides a fairly DOS-like view of the filesystems on the device (each drive has a drive letter, and backslashes are used as the directory delimiter). Symbian OS supports various filesystem types including FAT32 and Symbian OS-specific NOR flash filing systems. The filesystem is generally not exposed to the user through the phone user interface. Immediately above base are a selection of system libraries. These take all shapes and sizes, including for example character set conversion, a DBMS database, and resource file handling. Further up, the software is not so readily arranged into a stack.There is a large networking and communication subsystem, which has three main servers - ETEL (EPOC telephony), ESOCK (EPOC sockets) and C32 (responsible for serial communication). Each of these has a plug-in scheme. For example ESOCK allows different ".PRT" protocol modules, implementing different types of networking protocol scheme. There's lots of stuff relating to short-range communication links too, such as Bluetooth, IrDA and USB. There's also a large amount of user interface code. Even though the user interfaces themselves are maintained by other parties, the base classes and substructure ("UIKON") for all UIs are present in Symbian OS, along with certain related servers (for example, a view server which controls transitions between different phone user interface screens). There's a lot of related graphics code too - such as a window server and a font and bitmap server. An application architecture provides for standard application types, embedding, and file and data recognition. There is also a selection of application engines for popular smartphone applications such as calendars, address books, and task lists. A typical Symbian OS application is split up into an engine DLL and a graphical application - the application being a thin wrapper over the engine DLL. Symbian OS provides some of these engine DLLs. There are, of course, many other things that don't yet fit into this model - for example, SyncML, Java ME providing another set of APIs on top of most of the OS and multimedia. Quite a few of these things are frameworks, and vendors are expected to supply plug-ins to these frameworks from third parties (for example, Helix player for multimedia codecs). This has the advantage that the APIs to such areas of functionality are the same on many phone models, and that vendors get a lot of flexibility, but means that phone vendors need to do a great deal of integration work to make a Symbian OS phone. Symbian OS device manufacturers also get supplied with an example user interface layer called TechView. This is very similar to the user interface from a Psion Series 5 personal organiser, so isn't particularly similar to any given phone user interface, but provides a basis to start customisation. It is also the environment in which a lot of Symbian OS test code and example code runs.In 1980, Psion was founded by David Potter. EPOC16. Psion released several Series 3 devices from 1991 to 1998 which used the EPOC16 OS, also known as SIBO. EPOC OS Releases 1–3. The Series 5 device, released in 1997, used the first iterations of the EPOC32 OS. EPOC Release 4. Oregon Osaris and Geofox 1 were released using ER4. In 1998, Symbian Ltd. was formed as a partnership between Ericsson, Nokia, Motorola and Psion, to explore the convergence between PDAs and mobile phones. EPOC Release 5 a.k.a. Symbian OS v5. Psion Series 5mx, Series 7, Psion Revo, Psion Netbook, netPad, Ericsson MC218 were released in 1999 using ER5. ER5u a.k.a. Symbian OS v5.1. u = Unicode. The first phone, the Ericsson R380 was released using ER5u in 2000. It was not an 'open' phone - software could not be installed. Notably, a number of never released Psion prototypes for next generation PDAs, including a Bluetooth Revo successor codenamed Conan were using ER5u. Symbian OS v6.0 and v6.1. Sometimes called ER6. The first 'open' Symbian OS phone, the Nokia 9210, was released on 6.0. Symbian OS v7.0 and v7.0s. First shipped in 2003. This is an important Symbian release which appeared with all contemporary user interfaces including UIQ (Sony Ericsson P800, P900, P910, Motorola A925, A1000), Series 80 (Nokia 9300, 9500), Series 90 (Nokia 7710), Series 60 (Nokia 6600, 7310) as well as several FOMA phones in Japan. In 2004, Psion sold its stake in Symbian. Also in 2004, the first worm for mobile phones using Symbian OS, Cabir, was developed, which used Bluetooth to spread itself to nearby phones. See Cabir and Symbian OS threats. Symbian OS v8.0. First shipped in 2004, one of its advantages would have been a choice of two different kernels (EKA1 or EKA2). However, the EKA2 kernel version did not ship until SymbianOS v8.1b. The kernels behave more or less identically from user-side, but are internally very different. EKA1 was chosen by some manufactu

they are ok you have created a cool discussion.. in your discussion you have taken a good issue..

can u tell me what are symbian softwares actually i never heard this word.thank you for creating such a discussion and i u will also create such interesting discussions in future.

I think symbian is cool but you can call and answer without symbian too:)

what symbian softwares means.. i sont understand..