how bihari became a gaali?

Who carries you on a rickshaw
or an autorickshaw in Delhi?
Biharis. Who drives the cars of
Delhiites? Biharis. Who built the
Delhi Metro?Biharis. (You may not agree with
the last one.)
Who is building the new houses
and the expanding suburbs of
Delhi? Biharis. Who made Punjab
the most prosperous state in the
country? The answer again is
Biharis. (Here too you may not
agree.)
The credit for building the Delhi
Metro or making Punjab
prosperous will never go to
Biharis. Does anyone ever say
that blacks built America?
In colonial days, Bihar supplied
the "girmitiya", or indentured,
labour force that built countries
like Mauritius, Suriname and Fiji.
A bulk of the labour employed in
the Raj capital of Calcutta came
from Bihar. After Independence,
as opportunities grew, Bihari
workers flocked to places like
Delhi, Punjab and Mumbai.
At the same time, Biharis excelled
in other fields. Many of them
became great political leaders, ICS
and IAS
officers, scientists, doctors,
engineers, writers and artists.
Delhi and other Indian cities
attracted huge white-collar Bihari
populations and Biharis formed
a large part of the Indian
diaspora of professionals.
But in the eyes of the rest of
India, "Bihari" had come to mean
a labourer, a person doing
menial jobs. It had become a
term of scorn and contempt. In
their anglicized lingo, places like
Delhi University turned the word
into "Harry", but the pejorative
tone remained unmistakable.
Heaping scorn on the working
classes is a universal
phenomenon. That is how words
like Negro, Paki (used for
Pakistanis and Indians in Britain)
and some of the words denoting
dalit castes in India earned
contemptuous connotations.
In fact, while Biharis were
getting their hands dirty on
Punjab's farms, Punjabis were
migrating in hordes to the US,
Canada, the UK and Australia.
Never mind that they would take
up blue-collar jobs as taxi
drivers, petrol pump attendants
and waiters in those faraway
lands.
As the years passed, many of the
Biharis who had come to Punjab
or Mumbai as manual labourers
started moving up the economic
ladder as did the blue-collar
Indian emigrants abroad. A
usually unnoticed aspect of the
so-called racial attacks against
Indians abroad is the threat the
rise of working classes poses to
the entrenched social order. This
accentuates the contempt they
face. Viewed thus, the attacks on
Biharis in Punjab, and Mumbai,
and the attacks on Indians
abroad are manifestations of the
same phenomenon.
What stopped Biharis from
bringing about a green
revolution or building a Metro in
Bihar? The answer is geography
and history. Geography, because
ravaged by floods, the land of
Bihar was unable to feed its
growing population. And history,
because what was the centre of
the biggest Indian empire in
ancient times was reduced to an
obscure provincial existence. The
skewed landownership system
introduced by the British rulers
worsened the situation.
It is a story of a couple of
hundred years. Things could
have improved after
Independence had the political
leadership of Bihar been able to
exert influence on the rulers in
New Delhi to get enough funds
for development projects and set
off a process of industrialization
in the state.
On the contrary, Bihar continued
to live the same, conveniently
ignored, provincial existence. A
system built on casteism,
nepotism, corruption and crime
came to dominate the state. It
spawned a neo-rich class of
netas, babus, contractors and
government engineers who
would build palatial houses for
themselves with the money
meant for dams, power projects,
ration for the poor or even
fodder for cattle.
The money meant for roads,
other infrastructure and public
amenities would go into their
bank accounts. No wonder, the
roads - supposed to be built with
public money - in front of those
houses would be full of ditches
and become the playground of
pigs every monsoon.
With limited options of higher
education and hardly any
employment opportunities in the
state, the youth of Bihar started
looking out. They flooded places
like Delhi University and
Jawaharlal Nehru University.
They started dominating the
country's toughest competitive
tests like the IIT Joint Entrance
Examination and the UPSC's civil
services examination. With this
success, Biharis started believing
that they were the brainiest. As
for others, they at least began to
acknowledge that Biharis were
inferior to none when it came to
brainpower.
The academic success, however,
did not do much to rid the word
"Bihari" of the scorn it had
gathered. People in Delhi
continued to laugh at those who
spoke with a Bihari accent. Those
who spoke without an accent
would get this compliment: "Oh,
you are from Bihar? But you
don't sound like a Bihari."
Biharis, meanwhile, were
retreating into a shell, with little
but the glory of ancient and
medieval heroes like Buddha,
Mahavira, Chandragupta,
Chanakya, Ashoka, Aryabhatta,
Guru Gobind Singh and Sher
Shah to bask in. Now comes 11%
growth. The state can recover
from the damage it has suffered
over hundreds of years only if
such a high rate of growth can
be sustained for many, many
years. Then Biharis would not
have to till others' land or build
cities and countries elsewhere.
The writer is proud to be a
Bihari.Because he is bihari.genx.

blackberry

what;s special in blackberry?everyone want to know about blackberry,how it functions,what si special and why obama love it.

so,here are some details about blacbeery by genxarmy and internet.
BlackBerry is a line of wireless mobile devices developed by Canadian company Research In Motion (RIM). While including smartphone applications (address book, calendar, to-do lists, etc.) as well as telephone capabilities on newer models, the BlackBerry is primarily known for its ability to send and receive e-mail wherever it can access a wireless network of certain cellular phone carriers. It commands a 20.8% share of worldwide smartphone sales, making it the second most popular platform after Nokia's Symbian,[2] and is the most popular smartphone among business users.[3]
The first BlackBerry device was introduced in 1999 as a two-way pager. In 2002, the more commonly known smartphone BlackBerry was released, which supports push e-mail, mobile telephone, text messaging, Internet faxing, Web browsing and other wireless information services. It is an example of a convergent device.
BlackBerry first made headway in the marketplace by concentrating on e-mail. RIM currently offers BlackBerry e-mail service to non-BlackBerry devices, such as the Palm Treo, through the BlackBerry Connect software. The original BlackBerry device had a monochrome display, but all current models have color displays.
Most current BlackBerry models have a built-in QWERTY keyboard, optimized for "thumbing", the use of only the thumbs to type, and there are also several models that include a standard cell phone keypad for typing, and two models that are full touch-screen devices with no physical keyboard. System navigation is primarily accomplished by a scroll ball, or "trackball" in the middle of the device, older devices used a track wheel on the side and newer devices like the Blackberry Bold 9700 or Curve 8520/8530 use a small pad for navigation "trackpad" instead of a trackball. Some models (currently, those manufactured for use with iDEN networks such as Nextel and Mike) also incorporate a Push-to-Talk (PTT) feature, similar to a two-way radio.
Modern GSM-based BlackBerry handhelds incorporate an ARM 7 or 9 processor, while older BlackBerry 950 and 957 handhelds used Intel 80386 processors. The latest GSM BlackBerry models (8100, 8300 and 8700 series) have an Intel PXA901 312 MHz processor, 64 MB flash memory and 16 MB SDRAM.[4] CDMA BlackBerry smartphones are based on Qualcomm MSM6x00 chipsets which also include the ARM 9-based processor and GSM 900/1800 roaming (as the case with the 8830 and 9500) and include up to 256MB flash memory.[5][6]
Contents [hide]
1 Operating system
2 CPU
3 Database
4 Supporting software
4.1 BlackBerry Enterprise Server
4.2 BlackBerry Internet Service
4.3 BlackBerry Desktop Redirector
5 Supported Software
5.1 BlackBerry Messenger
6 Future features
7 Nicknames
8 Models
9 Phones with BlackBerry e-mail client
10 BlackBerry PIN
11 Certification
12 The BlackBerry Store
13 RIM patent infringement litigation
14 See also
15 Notes
16 References
17 External links
[edit]Operating system

Main article: BlackBerry OS


BlackBerry 7250
RIM provides a proprietary multi-tasking operating system (OS) for the BlackBerry, which makes heavy use of the device's specialized input devices, particularly the scroll wheel (1999–2006) or more recently the trackball (September 12 2006–present) and trackpad (September 2009-present). The OS provides support for Java MIDP 1.0 and WAP 1.2. Previous versions allowed wireless synchronization with Microsoft Exchange Server's e-mail and calendar, as well as with Lotus Domino's e-mail. The current OS 4 provides a subset of MIDP 2.0, and allows complete wireless activation and synchronization with Exchange's e-mail, calendar, tasks, notes and contacts, and adds support for Novell GroupWise and Lotus Notes.
Third-party developers can write software using these APIs, proprietary BlackBerry APIs as well, but any application that makes use of certain restricted functionality must be digitally signed so that it can be associated to a developer account at RIM. This signing procedure guarantees the authorship of an application, but does not guarantee the quality or security of the code.
[edit]CPU

Early BlackBerry devices used Intel-80386-based processors.[7] The latest BlackBerry 9000 series is equipped with Intel XScale 624 MHz CPU,which makes the fastest BlackBerry to date. Earlier BlackBerry 8000 series smartphones, such as the 8700 and the Pearl, are based on the 312 MHz ARM XScale ARMv5TE PXA900. An exception to this is the BlackBerry 8707 which is based on the 80 MHz Qualcomm 3250 chipset; this was due to the ARM XScale ARMv5TE PXA900 chipset not supporting 3G networks. The 80 MHz Processor in the BlackBerry 8707 actually meant the device was often slower to download and render web pages over 3G than the 8700 was over EDGE networks.
[edit]Database

Data extracted from a BlackBerry to a host computer is stored in a single file in a BlackBerry-specific format known as IPD.[8]
[edit]Supporting software

[edit]BlackBerry Enterprise Server


A BlackBerry 8800 with custom theme and wallpaper.
BlackBerry handhelds are integrated into an organization's e-mail system through a software package called "BlackBerry Enterprise Server" (BES). Versions of BES are available for Microsoft Exchange, Lotus Domino and Novell GroupWise. While individual users may be able to use a wireless provider's e-mail services without having to install BES themselves, organizations with multiple users usually run BES on their own network. Some third-party companies provide hosted BES solutions. Every BlackBerry has an ID called BlackBerry PIN, which is used to identify the device to the BES.
BES can act as a sort of e-mail relay for corporate accounts so that users always have access to their e-mail. The software monitors the user's local "inbox", and when a new message comes in, it picks up the message and passes it to RIM's Network Operations Center (NOC). The messages are then relayed to the user's wireless provider, which in turn delivers them to the user's BlackBerry device.
This is called "push e-mail," because all new e-mails, contacts and calendar entries are "pushed" out to the BlackBerry device automatically, as opposed to the user synchronizing the data by hand or on a polling basis. Blackberry also supports polling email, which is how it supports POP. Device storage also enables the mobile user to access all data offline in areas without wireless service. As soon as the user connects again, the BES sends the latest data.
An included feature in the newer models of the BlackBerry is the ability for it to track your current location through trilateration. One can view the online maps on the phone and see current location denoted by a flashing dot. However, accuracy of BlackBerry trilateration is less than that of GPS due to a number of factors, including cell tower blockage by large buildings, mountains, or distance.
BES also provides handhelds with TCP/IP connectivity accessed through a component called "Mobile Data Service - Connection Service" (MDS-CS). This allows for custom application development using data streams on BlackBerry devices based on the Sun Microsystems Java ME platform.
In addition, BES provides network security, in the form of Triple DES or, more recently, AES encryption of all data (both e-mail and MDS traffic) that travels between the BlackBerry handheld and a BlackBerry Enterprise Server.
Most providers offer flat monthly pricing for unlimited data between BlackBerry units and BES. In addition to receiving e-mail, organizations can make intranets or custom internal applications with unmetered traffic.
With more recent versions of the BlackBerry platform, the MDS is no longer a requirement for wireless data access. Beginning with OS 3.8 or 4.0, BlackBerry handhelds can access the Internet (i.e. TCP/IP access) without an MDS - previously only e-mail and WAP access was possible without a BES/MDS. The BES/MDS is still required for secure e-mail, data access, and applications that require WAP from carriers that do not allow WAP access.
[edit]BlackBerry Internet Service
The primary alternative to using BlackBerry Enterprise Server is to use the BlackBerry Internet Service. It was developed primarily for the average consumer rather than for the business consumer. This service allows POP3 and IMAP email integration for the personal user. It allows up to 10 email accounts to be accessed, including many popular email accounts such as Gmail, Hotmail, Yahoo and AOL. There are also special bundles for just Myspace, Facebook, & MSN as well.
[edit]BlackBerry Desktop Redirector
A less common alternate to using BlackBerry Enterprise Server is to use the BlackBerry Desktop Redirector. This software is installed on a desktop computer that has the enterprise email client installed.
[edit]Supported Software

[edit]BlackBerry Messenger
Newer BlackBerry devices use the proprietary Blackberry Messenger, also known as BBM, software for sending and receiving text messages via Blackberry PIN or barcode scan. There is also the BlackBerry Alliance program of partners who work under contract with Research In Motion to innovate new applications to differentiate the BlackBerry solution. Typical applications include digital dictation, GPS tracking, CRM and expense management. On October 6, 2009 Blackberry Messenger 5.0 was officially released, adding a whole new set of features, including bar code scanning to add contacts, profiles, sharing your location via GPS, and creating groups.
Third-party software available for use on BlackBerry devices includes full-featured database management systems, which can be used to support customer relationship management clients and other applications that must manage large volumes of potentially complex data.[9]
[edit]Future features

On September 11, 2008 Tivo and Research in Motion announced that soon TiVo users would be able to control their system from a BlackBerry phone. The integration was expected by the end of 2008. No price—if any—was disclosed.[10]
On November 9, 2009 Research in Motion announced that OpenGL ES and the Flash platform will be available on BlackBerry devices.
[edit]Nicknames

The ability to read e-mail that is received in real time, anywhere, has made the BlackBerry devices infamously addictive, earning them the nickname "CrackBerry," a reference to the freebase form of cocaine known as crack, which is also highly addictive. Use of the term CrackBerry became so widespread that in November 2006 Webster's New World College Dictionary named "crackberry" the "New Word of the Year".[11]
When coupled with Boost Mobile service, the smart phones are sometimes referred to as "BoostBerry."[citation needed]
Many users also refer to BlackBerry smart phones in general simply as "berries", spawning a litany of offshoots. For example, "berry thumb" or "berry blister" is the soreness that occurs from handling the keyboard.
[edit]Models

Main article: List of BlackBerry products


A BlackBerry Pearl 8100
Early Pager Models: 850, 857, 950, 957
Monochrome Java-based Models: 5000-series and 6000-series
First Color Models: 7200-series, 7500-series and 7700-series
First SureType Phone Models: 7100-series
Modern BlackBerry Models (2006 - 2008): 8000-8830-series including: BlackBerry 8800, BlackBerry Pearl, Pearl Flip and BlackBerry Curve
Latest BlackBerry Models (2008 - 2009): 8900+ GPS WiFi Series: BlackBerry Bold (9000), BlackBerry Curve 8900, BlackBerry Tour (9630), BlackBerry Storm (9500/9530)
BlackBerry Storm 2 (2009): BlackBerry Storm 2 [12]
BlackBerry Bold 2 (2009): BlackBerry 9700 (9700 / Bold 2) [13]
[edit]Phones with BlackBerry e-mail client

Several non-BlackBerry mobile phones have been released featuring the BlackBerry e-mail client which connects to BlackBerry servers. Many of these phones have full QWERTY keyboards
AT&T Tilt Operates on 3G/HSDPA/850/900/1800/1900 MHz GSM network, 240 x 320 pixel touch screen, QWERTY keyboard
HTC Advantage X7500
HTC TyTN Operates on 3G/HSDPA/850/900/1800/1900 MHz GSM network, 240 × 320 pixel touch screen, QWERTY keyboard
Motorola MPx220 (selected models only), Operates on 850/900/1800/1900 MHz GSM network, 176 × 220 pixel screen
Nokia 6810 Operates on 900/1800/1900 MHz GSM network, 128 × 128 pixel screen
Nokia 6820 Operates on 900/1800/1900 MHz GSM network, American variant on 850/1800/1900 GSM network, 128 × 128 pixel screen
Nokia 9300 Operates on 900/1800/1900 MHz GSM network, 128 × 128 and 640 × 200 pixel screen
Nokia 9300i Operates on 900/1800/1900 MHz GSM network, 128 × 128 and 640 × 200 pixel screen
Nokia 9500 Operates on 900/1800/1900 MHz GSM network, 128 × 128 and 640 × 200 pixel screen
All Nokia E-Series phones (Excluding the Nokia E71 and Nokia E66 models)
Qtek 9100 Operates on 850/900/1800/1900 MHz GSM network, 240 × 320 pixel touch screen and QWERTY keyboard
Qtek 9000 Operates on 3G-UMTS/850/900/1800/1900 MHz GSM network, 640 × 480 pixel touch screen, QWERTY keyboard
Samsung t719 Operates on 850/900/1800/1900 MHz GSM network, 176 × 220 pixel screen
Siemens SK65, Operates on 900/1800/1900 MHz GSM network, 132 × 176 pixel screen
Sony Ericsson P910 Operates on 900/1800/1900 MHz GSM network, American and Chinese variants on 850/1800/1900, 208 × 320 pixel screen
Sony Ericsson P990
Sony Ericsson M600i
Sony Ericsson P1
[edit]BlackBerry PIN

BlackBerry PIN is an eight character hexadecimal identification number assigned to each BlackBerry device. PINs cannot be changed and are locked to each handset device. BlackBerrys can message each other using the PIN directly or by using the Blackberry Messenger application.
[edit]Certification



A BlackBerry Bold.
BCESA (BlackBerry Certified Enterprise Sales Associate, BCESA40 in full) is a BlackBerry Certification for professional users of RIM (Research In Motion) BlackBerry wireless e-mail devices.
The Certification requires the user to pass several exams relating to the BlackBerry Device, all its functions including Desktop software and providing technical support to Customers of BlackBerry Devices.
The BCESA, BlackBerry Certified Enterprise Sales Associate qualification, is the first of three levels of professional BlackBerry Certification.
BCTA (BlackBerry Certified Technical Associate)
BlackBerry Certified Support Associate T2
Additional information on certifications can be found on the Blackberry.com website.
The BlackBerry Technical Certifications available are:
BlackBerry Certified Enterprise Server Consultant (BCESC)
BlackBerry Certified Server Support Technician (BCSST)
BlackBerry Certified Support Technician (BCST)
[edit]The BlackBerry Store

In December 2007 , it was reported that the first ever BlackBerry store was opened.[14] While it is the only BlackBerry store currently in existence, it actually is not the first. There were three prior attempts at opening BlackBerry stores in Toronto, London, and Charlotte,[15] but they eventually folded.[16] The current location is in Farmington Hills, Michigan. The store offers BlackBerry device models from AT&T, T-Mobile, Verizon, and Sprint, the major U.S. carriers which offer smartphones. Employees are trained not only on the BlackBerry devices themselves, but on the regulations of each service provider.
[edit]RIM patent infringement litigation

In 2000, NTP sent notice of their wireless email patents to a number of companies and offered to license the patents to them. NTP brought a patent infringement lawsuit against one of the companies, Research In Motion, in the United States District Court for the Eastern District of Virginia. This court is well known for its strict adherence to timetables and deadlines, sometimes referred to as the "rocket docket," and is particularly efficient at trying patent cases.[17]
The jury eventually found that the NTP patents were valid, that RIM had infringed them, that the infringement had been "willful", and that the infringement had cost NTP $33 million dollars in damages (the greater of a reasonable royalty or lost profits). The judge, James R. Spencer increased the damages to $53 million as a punitive measure because the infringement had been willful. He also instructed RIM to pay NTP's legal fees of $4.5 million and issued an injunction ordering RIM to cease and desist infringing the patents. This would have shut down the BlackBerry systems in the US.[18]
RIM appealed all of the findings of the court. The injunction and other remedies were stayed pending the outcome of the appeals.
In March 2005 during the appeals process, RIM and NTP tried to negotiate a settlement of their dispute. One of the terms of the settlement was to be for $450 million. But negotiations broke down due to other issues. On June 10, 2005 the matter returned to the courts.
In early November, 2005 the US Department of Justice filed a brief requesting that RIM's service be allowed to continue because of the large number of BlackBerry users in the US Federal Government.[19]
In January 2006, the US Supreme Court refused to hear RIM's appeal of the holding of liability for patent infringement, and the matter was returned to a lower court. The previously granted injunction preventing all RIM sales in the US and use of the BlackBerry device might have been enforced by the presiding district court judge had the two parties not been able to reach a settlement.
On February 9, 2006, the US Department of Defense (DOD) filed a brief stating that an injunction shutting down the BlackBerry service while excluding government users was unworkable. The DOD also stated that the BlackBerry was crucial for national security given the large number of government users.
On February 9, 2006, RIM announced that it had developed software workarounds that would not infringe the NTP patents, and would implement those if the injunction was enforced.
On March 3, 2006, after a stern warning from Judge Spencer, RIM and NTP announced that they had settled their dispute. Under the terms of the settlement, RIM has agreed to pay NTP $612.5 million (USD) in a “full and final settlement of all claims.” In a statement, RIM said that “all terms of the agreement have been finalized and the litigation against RIM has been dismissed by a court order this afternoon. The agreement eliminates the need for any further court proceedings or decisions relating to damages or injunctive relief.” The settlement amount is believed low by some analysts, because of the absence of any future royalties on the technology in question.[20]

smartphone

Market share of Smartphone operating system sales during Q2/2009 by Canalys.[1] (data does not include Palm WebOS, which was introduced in June, 2009)
A smartphone is a mobile phone offering advanced capabilities, often with PC-like functionality (PC-mobile handset convergence). There is no industry standard definition of a smartphone.[2][3] For some, a smartphone is a phone that runs complete operating system software providing a standardized interface and platform for application developers.[4] For others, a smartphone is simply a phone with advanced features like e-mail, Internet and e-book reader capabilities, and/or a built-in full keyboard or external USB keyboard and VGA connector. In other words, it is a miniature computer that has phone capability.[5][6]
Growth in demand for advanced mobile devices boasting powerful processors, abundant memory, larger screens and open operating systems has outpaced the rest of the mobile phone market for several years.[7]
Contents [hide]
1 History
2 Operating systems
3 Smartbook
4 See also
5 References
[edit]History

The first smartphone was called Simon; it was designed by IBM in 1992 and shown as a concept product[8] that year at COMDEX, the computer industry trade show held in Las Vegas, Nevada. It was released to the public in 1993 and sold by BellSouth. Besides being a mobile phone, it also contained a calendar, address book, world clock, calculator, note pad, e-mail, send and receive fax, and games. It had no physical buttons to dial with. Instead customers used a touch-screen to select phone numbers with a finger or create facsimiles and memos with an optional stylus. Text was entered with a unique on-screen "predictive" keyboard. By today's standards, the Simon would be a fairly low-end product; however, its feature set at the time was incredibly advanced.
The Nokia Communicator line was the first of Nokia's smartphones starting with the Nokia 9000, released in 1996. This distinctive palmtop computer style smartphone was the result of a collaborative effort of an early successful and expensive PDA model by Hewlett Packard combined with Nokia's bestselling phone around that time and early prototype models had the two devices fixed via a hinge; the Nokia 9210 as the first color screen Communicator model which was the first true smartphone with an open operating system; the 9500 Communicator that was also Nokia's first cameraphone Communicator and Nokia's first WiFi phone; the 9300 Communicator was the third dimensional shift into a smaller form factor; and the latest E90 Communicator includes GPS. The Nokia Communicator model is remarkable also having been the most expensive phone model sold by a major brand for almost the full lifespan of the model series, easily 20% and sometimes 40% more expensive than the next most expensive smartphone by any major manufacturer.
The Ericsson R380 was sold as a 'smartphone' but could not run native third-party applications.[9] Although the Nokia 9210 was arguably the first true smartphone with an open operating system, Nokia continued to refer to it as a Communicator.
In October 2001 Handspring unveiled the Palm OS Treo smartphone, utilizing a full keyboard that combined wireless web browsing, email, calendar and contact organizer, with mobile third-party applications that could be downloaded or synced with a computer.[10]
In 2002 RIM released the first BlackBerry which was the first smartphone optimized for wireless email use and has achieved a total customer base of 8 million subscribers by June 2007, of which three quarters are in North America.
Although the Nokia 7650, announced in 2001, was referred to as a 'smart phone' in the media, and is now called a 'smartphone' on the Nokia support site, the press release referred to it as an 'imaging phone'.[11][12][13] Handspring delivered the first widely popular smartphone devices in the US market by marrying its Palm OS based Visor PDA together with a piggybacked GSM phone module, the VisorPhone. By 2002, Handspring was marketing an integrated smartphone called the Treo; the company subsequently merged with Palm primarily because the PDA market was dying but the Treo smartphone was quickly becoming popular as a phone with extended PDA organizer features. That same year, Microsoft announced its Windows CE Pocket PC OS would be offered as "Microsoft Windows Powered Smartphone 2002".[14] Microsoft originally defined its Windows Smartphone products as lacking a touchscreen and offering a lower screen resolution compared to its sibling Pocket PC devices. Palm then introduced a few Windows Mobile smartphones alongside the existing Palm OS smartphones, and has now abandoned both platforms in favor of its new Palm webOS.
In 2005 Nokia launched its N-Series of 3G smartphones which Nokia started to market not as mobile phones but as multimedia computers.
Out of 1 billion camera phones to be shipped in 2008, smartphones, the higher end of the market with full email support, will represent about 10% of the market or about 100 million units.[citation needed]
The Smartphone Summit semi-annual conference details smartphone industry market data, trends, and updates among smartphone related hardware, software, and accessories.
Android, a cross platform OS for smartphones was released in 2008. Android is an Open Source platform backed by Google, along with major hardware and software developers (such as Intel, HTC, ARM, Motorola and eBay, to name a few), that form the Open Handset Alliance[15].
The first phone to use the Android OS was the HTC Dream, branded for distribution by T-Mobile as the G1[16]. The phone features a full, capacitive touch screen, a flip out QWERTY keyboard, and a track ball for navigating web pages. The software suite included on the phone consists of integration with Google's proprietary applications, such as Maps, Calendar, and Gmail, as well as Google's Chrome Lite full HTML web browser[17]. Third party apps are available via the Android Market, including both free and paid apps[18].
In July 2008 Apple introduced its App Store with both for fee and free applications. The app store can deliver smartphone applications developed by third parties directly to the iPhone or iPod Touch over wifi or cellular network without using a PC to download. The App Store has been a huge success for Apple and by June 2009 hosted more than 50,000 applications.[19] The app store hit one billion application downloads on April 23, 2009.[20]
Following the popularity of Apple's App Store, many other mobile platforms are following Apple with their own application stores. Palm, Microsoft and Nokia have all announced they will launch Apple-like app stores. RIM recently launched its app store, BlackBerry App World.
In January 2010, Google launches Nexus One using its Android OS. Although Android OS has a multi-touch capabilities, Google removes that feature from Nexus One[21].
[edit]Operating systems

Main article: Mobile operating system
Operating systems that can be found on smartphones include Symbian OS, iPhone OS, Palm WebOS, BlackBerry OS, Samsung bada, Windows Mobile, Android and Maemo. WebOS, Android and Maemo are built on top of Linux, and the iPhone OS is derived from the BSD and NeXTSTEP operating systems, which all are related to Unix.

android mobile plateform

mch hyped and future based operating system.eveyone want to know about this because this is from google.


Android


Android version 2.0 running in the Android SDK Emulator
Company / developer Open Handset Alliance
Working state Current
Source model Free and open source software
Initial release 2008-10-21; 14 months ago
Latest stable release Android 2.1 (Eclair) / 2010-1-05; 4 days ago[1]
Supported platforms ARM, MIPS, Power Architecture, x86
Kernel type Monolithic (Linux)
License Apache 2.0 and GPLv2[2]
Website android.com
Android is a mobile operating system running on the Linux kernel.[3] It was initially developed by Android Inc., a firm later purchased by Google, and lately by the Open Handset Alliance.[4] It allows developers to write managed code in the Java language, controlling the device via Google-developed Java libraries.[5]
The unveiling of the Android distribution on 5 November 2007 was announced with the founding of the Open Handset Alliance, a consortium of 47 hardware, software, and telecom companies devoted to advancing open standards for mobile devices.[6][7] Google released most of the Android code under the Apache License, a free software and open source license.[8]
Contents [hide]
1 History
1.1 Open Handset Alliance
1.2 Licensing
1.3 Update history
2 Features
3 Hardware running Android
4 Software development
4.1 Software development kit
4.2 Android Developer Challenge
4.3 Google applications
4.4 Native code
4.5 Community-based firmware
5 Marketing
5.1 Logos
5.2 Market share
6 Etymology
7 Restrictions and issues
8 See also
9 References
10 Bibliography
11 External links
[edit]History



Android at Googleplex.
In July 2005, Google acquired Android, Inc., a small startup company based in Palo Alto, California, USA.[9] Android's co-founders who went to work at Google included Andy Rubin (co-founder of Danger[10]), Rich Miner (co-founder of Wildfire Communications, Inc.[11]), Nick Sears (once VP at T-Mobile[12]), and Chris White (headed design and interface development at WebTV[13]). At the time, little was known about the functions of Android, Inc. other than that they made software for mobile phones.[9] This began rumors that Google was planning to enter the mobile phone market, although it was unclear what function it might perform in that market.[citation needed]
At Google, the team led by Rubin developed a mobile device platform powered by the Linux kernel which they marketed to handset makers and carriers on the premise of providing a flexible, upgradeable system.[citation needed] It was reported that Google had already 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.[14][15][16] More speculation that Google would be entering the mobile-phone market came in December 2006.[17] Reports from the BBC and The Wall Street Journal noted that Google wanted its search and applications on mobile phones and it was working hard to deliver that. Print and online media outlets soon reported rumors that Google was developing a Google-branded handset.[18] More speculation followed reporting that as Google was defining technical specifications, it was showing prototypes to cell phone manufacturers and network operators.
In September 2007, InformationWeek covered an Evalueserve study reporting that Google had filed several patent applications in the area of mobile telephony.[19][20]. Ultimately Google unveiled its smartphone Nexus One that uses the Android open source mobile operating system. The device is manufactured by Taiwan's HTC Corporation, and became available on January 5, 2010
[edit]Open Handset Alliance
Main article: Open Handset Alliance
"Today's announcement is more ambitious than any single 'Google Phone' that the press has been speculating about over the past few weeks. Our vision is that the powerful platform we're unveiling will power thousands of different phone models."
—-Eric Schmidt, Google Chairman/CEO[4]
On 5 November 2007, the Open Handset Alliance, a consortium of several companies which include Texas Instruments, Broadcom Corporation, Google, HTC, Intel, LG, Marvell Technology Group, Motorola, Nvidia, Qualcomm, Samsung Electronics, Sprint Nextel and T-Mobile was unveiled with the goal to develop open standards for mobile devices.[4] Along with the formation of the Open Handset Alliance, the OHA also unveiled their first product, Android, a mobile device platform built on the Linux kernel version 2.6.[4]
On 9 December 2008, it was announced that 14 new members would be joining the Android project including: ARM Holdings Plc, Atheros Communications, Asustek Computer Inc, Garmin Ltd, Softbank, Sony Ericsson, Toshiba Corp, and Vodafone Group Plc.[21][22]
Google Chairman and CEO Eric Schmidt took some time in the official press release to dispel all previous rumors and speculation about the existence of a stand-alone Google phone.[4]
[edit]Licensing
With the exception of brief update periods, Android has been available as open source since 21 October 2008. Google opened the entire source code (including network and telephony stacks[23]) under an Apache License.[24]
With the Apache License, vendors are free to add proprietary extensions without submitting those back to the open source community.
[edit]Update history


A cupcake was placed beside Android at Googleplex to commemorate the 1.5 release of Android.
Android has seen a number of updates since its original release. These updates to the base Operating System typically fix bugs and add new features.
1.5 (Cupcake) On 30 April 2009, the official 1.5 (Cupcake) update for Android was released.[25][26] There are several new features and UI updates included in the 1.5 update:
Ability to record and watch videos with the camcorder mode
Uploading videos to YouTube and pictures to Picasa directly from the phone
A new soft keyboard with an "Autocomplete" feature
Bluetooth A2DP support (which in turn broke Bluetooth connectivity with many popular cars and headsets. This has still yet to be fixed as of Dec-09)
Ability to automatically connect to a Bluetooth headset within a certain distance
New widgets and folders that can populate the desktop
Animations between screens
Expanded ability of Copy and paste to include web pages[27]
1.6 (Donut) On 15 September 2009, the 1.6 (Donut) SDK was released.[28][29] Included in the update are:
An improved Android Market experience.
An integrated camera, camcorder, and gallery interface.
Gallery now enables users to select multiple photos for deletion.
Updated Voice Search, with faster response and deeper integration with native applications, including the ability to dial contacts.
Updated search experience to allow searching bookmarks, history, contacts, and the web from the home screen.
Updated Technology support for CDMA/EVDO, 802.1x VPN, Gestures, and a Text-to-speech engine
Speed improvements for searching, the camera.[30]
2.0/2.0.1/2.1 (Eclair)[31] On 26 October 2009 the 2.0 (Eclair) SDK was released.[32] Among the changes are:[33]
Optimized hardware speed
Support for more screen sizes and resolutions
Revamped UI
New browser UI and HTML5 support
New contact lists
Better white/black ratio for backgrounds
Improved Google Maps 3.1.2
Microsoft Exchange support
Built in flash support for Camera
Digital Zoom
Improved virtual keyboard
Bluetooth 2.1
A subsequent version is to be named Flan.[34]
[edit]Features



The Android Emulator default home screen.
Current features and specifications:[35][36][37]
Handset layouts The platform is adaptable to larger, VGA, 2D graphics library, 3D graphics library based on OpenGL ES 1.0 specifications, and traditional smartphone layouts.
Storage The Database Software SQLite is used for data storage purposes
Connectivity Android supports connectivity technologies including GSM/EDGE, CDMA, EV-DO, UMTS, Bluetooth, and Wi-Fi.
Messaging SMS and MMS are available forms of messaging including threaded text messaging.
Web browser The web browser available in Android is based on the open-source WebKit application framework. The browser scores a 93/100 on the Acid3 Test.
Java support Software written in Java can be compiled to be executed in the Dalvik virtual machine, which is a specialized VM implementation designed for mobile device use, although not technically a standard Java Virtual Machine.
Media support Android supports the following audio/video/still media formats: H.263, H.264 (in 3GP or MP4 container), MPEG-4 SP, AMR, AMR-WB (in 3GP container), AAC, HE-AAC (in MP4 or 3GP container), MP3, MIDI, OGG Vorbis, WAV, JPEG, PNG, GIF, BMP.[37]
Additional hardware support Android can use video/still cameras, touchscreens, GPS, accelerometers, magnetometers, accelerated 2D bit blits (with hardware orientation, scaling, pixel format conversion) and accelerated 3D graphics.
Development environment Includes a device emulator, tools for debugging, memory and performance profiling, a plugin for the Eclipse IDE.
Market Like many phone-based application stores, the Android Market is a catalog of applications that can be downloaded and installed to target hardware over-the-air, without the use of a PC. Originally only freeware applications were supported. Paid-for apps have been available on the Android Market in the United States since 19 February 2009.[38] The Android Market has been expanding rapidly. By December, 2009, it had over 20,000 Android applications for download.[39]
Multi-touch Android has native support for multi-touch which is available in newer handsets such as the HTC Hero. The feature was initially disabled at the kernel level (possibly to avoid infringing Apple patents on touch-screen technology[40]).
Android does not support bluetooth file exchange, videocall or native J2ME, as do other mobile operating systems, such as Symbian OS and Windows Mobile.
[edit]Hardware running Android

Main article: List of Android devices
The first phone to run the Android operating system was the HTC Dream, released on 22 October 2008.[41]
By the end of 2009 there will be at least 18 phone models using Android worldwide, according to Google.[42] In addition to the mobile devices that ship with Android, some users have been able (with some amount of hacking, and with limited functionality) to install it on mobile devices shipped with other operating systems.[43]
[edit]Software development



Early Android device.
The early feedback on developing applications for the Android platform was mixed.[44] Issues cited include bugs, lack of documentation, inadequate QA infrastructure, and no public issue-tracking system. (Google announced an issue tracker on 18 January 2008.)[45] In December 2007, MergeLab mobile startup founder Adam MacBeth stated, "Functionality is not there, is poorly documented or just doesn't work... It's clearly not ready for prime time."[46] Despite this, Android-targeted applications began to appear the week after the platform was announced. The first publicly available application was the Snake game.[47][48] The Android Dev Phone is a SIM-unlocked and hardware-unlocked device that is designed for advanced developers. While developers can use regular consumer devices purchased at retail to test and use their apps, some developers may choose not to use a retail device, preferring an unlocked or no-contract device.
[edit]Software development kit
The Android SDK includes a comprehensive set of development tools.[49] These include a debugger, libraries, a handset emulator (based on QEMU), documentation, sample code, and tutorials. Currently supported development platforms include x86-architecture computers running Linux (any modern desktop Linux distribution), Mac OS X 10.4.8 or later, Windows XP or Vista. Requirements also include Java Development Kit, Apache Ant, and Python 2.2 or later. The officially supported integrated development environment (IDE) is Eclipse (3.2 or later) using the Android Development Tools (ADT) Plugin, though developers may use any text editor to edit Java and XML files then use command line tools to create, build and debug Android applications as well as control attached Android devices (e.g., triggering a reboot, installing software package(s) remotely).[50]
A preview release of the Android software development kit (SDK) was released on 12 November 2007. On 15 July 2008, the Android Developer Challenge Team accidentally sent an email to all entrants in the Android Developer Challenge announcing that a new release of the SDK was available in a "private" download area. The email was intended for winners of the first round of the Android Developer Challenge. The revelation that Google was supplying new SDK releases to some developers and not others (and keeping this arrangement private) has led to widely reported frustration within the Android developer community.[51]
On 18 August 2008 the Android 0.9 SDK beta was released. This release provides an updated and extended API, improved development tools and an updated design for the home screen. Detailed instructions[52] for upgrading are available to those already working with an earlier release. On 23 September 2008 the Android 1.0 SDK (Release 1) was released.[53] According to the release notes, it included "mainly bug fixes, although some smaller features were added". It also included several API changes from the 0.9 version.
On 9 March 2009, Google released version 1.1 for the Android dev phone. While there are a few aesthetic updates, a few crucial updates include support for "search by voice, priced apps, alarm clock fixes, sending gmail freeze fix, fixes mail notifications and refreshing intervals, and now the maps show business reviews". Another important update is that Dev phones can now access paid apps and developers can now see them on the Android Market.[54]
In the middle of May 2009, Google released version 1.5 (Cupcake) of the Android OS and SDK. This update included many new features including video recording, support for the stereo bluetooth profile, a customizable onscreen keyboard system and voice recognition. This release also opened up the AppWidget framework to third party developers allowing anyone to create their own home screen widgets.[55]
In September 2009 the "Donut" version (1.6) was released which featured better search, battery usage indicator and VPN control applet. New platform technologies included Text to Speech engine (not available on all phones), Gestures & Accessibility framework.[56]
Android Applications are packaged in .apk format and stored under /data/app folder on the Android OS. The user can run the command adb root to access this folder as only the root has permissions to access this folder.
[edit]Android Developer Challenge
The Android Developer Challenge was a competition for the most innovative application for Android. Google offered prizes totaling 10 million US dollars, distributed between ADC I and ADC II. ADC I accepted submissions from 2 January to 14 April 2008. The 50 most promising entries, announced on 12 May 2008, each received a $25,000 award to fund further development.[57][58] It ended in early September with the announcement of ten teams that received $275,000 each, and ten teams that received $100,000 each.[59] ADC II was announced on 27 May 2009.[60] The first round of the ADC II closed on 6 October 2009.[61] The first-round winners of ADC II comprising the top 200 applications were announced on 5 November 2009. Voting for the second round also opened on the same day and ended on November 25. Google announced the top winners on November 30.[62][63]
[edit]Google applications
Google has also participated in the Android Market by offering several applications for its services. These applications include Google Voice for the Google Voice service, Scoreboard for following sports, Sky Map for watching stars, Finance for their finance service, Maps Editor for their MyMaps service, Places Directory for their Local Search, Google Goggles that searches by image, and My Tracks, a jogging application. Android phones that include the 'Google Experience' also have Google Search, Google Calendar, Google Maps, Google Navigation and Gmail integrated.
[edit]Native code
Libraries written in C and other languages can be compiled to ARM native code and installed using the Android Native Development Kit. Native classes can be called from Java code running under the Dalvik VM using the System.loadLibrary call, which is part of the standard Android Java classes.[64][65]
Complete applications can be compiled and installed using traditional development tools.[66] The ADB debugger gives a root shell under the Android Emulator which allows native ARM code to be uploaded and executed. ARM code can be compiled using GCC on a standard PC.[66] Running native code is complicated by the fact that Android uses a non-standard C library (known as Bionic). The underlying graphics device is available as a framebuffer at /dev/graphics/fb0.[67] The graphics library that Android uses to arbitrate and control access to this device is called the Skia Graphics Library (SGL), and it has been released under an open source license.[68] Skia has backends for both win32 and Cairo, allowing the development of cross-platform applications, and it is the graphics engine underlying the Google Chrome web browser.[69]
Elements Interactive Mobile B.V. have ported their EdgeLib C++ library to Android, and native code executables of their S-Tris2 game (a Tetris clone) and Animate3D technology demo are available for download.[70]
[edit]Community-based firmware
There is a thriving community of open-source enthusiasts that build and share Android-based firmware with a number of customizations and additional features, such as FLAC lossless audio support and the ability to store downloaded apps on the microSD card.[71]
Those firmware packages are updated frequently, incorporate elements of Android functionality that haven't yet been officially released within a carrier-sanctioned firmware, and tend not to have arbitrary limitations. CyanogenMod is one such firmware.
On 24 September 2009, Google issued a cease and desist letter[72] to the modder Cyanogen, citing issues with the re-distribution of Google's closed-source applications[73] within the custom firmware. Even though Android OS is open source, phones come packaged with closed-source Google applications for functionality such as the application store and GPS navigation. Google has asserted that these apps can only be provided through approved distribution channels by licensed distributors. Cyanogen has complied with Google's wishes and is continuing to distribute his mod without the proprietary software. He has provided a method to back up licensed Google applications during the mod's install process and restore them when it is complete.[74]
[edit]Marketing

[edit]Logos


Text logo.
Android uses the Droid font family made by Ascender Corporation.[75]
Android Green is the color of the Android Robot that represents the Android operating system. The print color is PMS 376C and the online hex color is #A4C639, as specified by the Android Brand Guidelines.[76]
[edit]Market share
The first Android phone was released on 22 October 2008. Research company Canalys estimates that by Q2, 2009, Android had a 2.8% share of the worldwide smartphone market.[77] By the following quarter (Q3 2009), Android's market share had grown to 3.5%.[78]
In October, 2009, Gartner Inc. predicted that by 2012, Android would become the world's second most popular smartphone platform, behind only the Symbian OS which powers Nokia phones very popular outside the US. Meanwhile, BlackBerry would fall from 2nd to 5th place, iPhone would remain in 3rd place, and Microsoft's Windows Mobile would remain in 4th place.[79] Taiwan's Market Intelligence & Consulting Institute (MIC) predicted that in 2013, 31.8 million Android phones and 126 million Android-based portable products would ship.[80]
Analytics firm Flurry estimates that 250,000 Motorola Droid phones were sold in the United States, during the phone's first week in stores.[81]
[edit]Etymology

Both the Android and Nexus One names allude to the novel (by Philip K. Dick) Do Androids Dream of Electric Sheep, which was later adapted into the film Blade Runner. Both the book and film are centered on a group of rogue androids called 'replicants' that are identified through the model designation Nexus-6.[82][83][84]
[edit]Restrictions and issues

The Android platform does not support animated .gif files at this time. It only shows the first frame.
Android uses Linux as its kernel,[85] but according to Google, it is not a conventional Linux distribution; it does not have a native X Window System, nor does it support the full set of standard GNU libraries like its system libraries (GNU C Library). This specific modification makes it difficult to reuse existing Linux applications or libraries on Android.[86]
Android does not use established Java standards, i.e. Java SE and ME. This prevents compatibility among Java applications written for those platforms and those for the Android platform. Android only reuses the Java language syntax, but does not provide the full-class libraries and APIs bundled with Java SE or ME.[87]
Because of potential security issues,[88] Android does not officially allow apps to be installed on, nor run from, an SD card. Current Android products such as the HTC Dream and Magic have limited onboard memory and many users feel restricted by this lack of functionality.[89] However, several unsupported modifications exist, to give the user this capability.[90]
ARM Holdings and RealNetworks have expressed doubt that it will gain a major market share as a netbook OS.[91]
Garbage collection will slow down programs that make too many memory allocations so that Dalvik can keep a pool of free memory. This may noticeably affect responsiveness.[92]
Developers reported that it's difficult to maintain applications working on different versions of Android, because of various compatibility issues between versions 1.5 and 1.6. This however was only true in some rare cases, specifically during the ADC2 contest.[93].

symbian os

one of the most hot and talked.i am obliged to write and collect excerpt on this topic.i am also a fan of symbian as i also use symbian s60 phone.so what is symbian?

Symbian is an operating system (OS) designed for mobile devices and smartphones, with associated libraries, user interface, frameworks and reference implementations of common tools, originally developed by Symbian Ltd. It was a descendant of Psion's EPOC and runs exclusively on ARM processors, although an unreleased x86 port existed.
In 2008 the former Symbian Software Limited was acquired by Nokia and a new independent non-profit organisation called the Symbian Foundation was established. Symbian OS and its associated user interfaces S60, UIQ and MOAP(S) were contributed by their owners to the foundation with the objective of creating the Symbian platform as a royalty-free, open source software. The resulting Symbian platform has been designated as the successor to Symbian OS, following the official launch of the Symbian Foundation in April 2009. The process of publishing the source code under the Eclipse Public License (EPL) was slated for completion in 2010.[2]
Symbian is the world's most popular mobile operating system, accounting for 50% of smartphone sales.[3]
Contents [hide]
1 Design
2 Competition
3 Structure
4 History
4.1 Psion
4.2 EPOC
4.2.1 EPOC16
4.2.2 EPOC32
4.2.3 EPOC OS Releases 1–5
4.3 Symbian OS 6.0 and 6.1
4.4 Symbian OS 7.0 and 7.0s
4.5 Symbian OS 8.0
4.5.1 Symbian OS 8.1
4.6 Symbian OS 9
4.6.1 Symbian OS 9.1 and open source development
4.6.1.1 Open source software for Symbian 9.1
4.6.1.1.1 Utilities
4.6.1.1.2 Game emulation
4.6.1.1.3 Multimedia
4.6.1.1.4 Frameworks
4.6.1.1.5 Mobile Office
4.6.2 Symbian OS 9.2
4.6.3 Symbian OS 9.3
4.6.4 Symbian OS 9.4
4.6.5 Symbian OS 9.5
4.7 Integrated Symbian platform
4.7.1 Symbian^1
4.7.2 Symbian^2, Symbian^3 and Symbian^4
4.7.3 Applications for the Symbian Platform
5 Devices that use Symbian OS
6 Security
6.1 Malware
6.2 Hacking Symbian
7 Developing on Symbian OS
8 See also
9 Notes and references
10 Bibliography
11 External links
[edit]Design

Symbian features pre-emptive multitasking and memory protection, like other operating systems (especially those created for use on desktop computers). EPOC's approach to multitasking was inspired by VMS and is based on asynchronous server-based events.
Symbian OS was created with three systems design principles in mind:
the integrity and security of user data is paramount,
user time must not be wasted, and
all resources are scarce.
To best follow these principles, Symbian uses a microkernel, has a request-and-callback approach to services, and maintains separation between user interface and engine. The OS is optimised for low-power battery-based devices and for ROM-based systems (e.g. features like XIP and re-entrancy in shared libraries). Applications, and the OS itself, follow an object-oriented design: Model-view-controller (MVC).
Later OS iterations diluted this approach in response to market demands, notably with the introduction of a real-time kernel and a platform security model in versions 8 and 9.
There is a strong emphasis on conserving resources which is exemplified by Symbian-specific programming idioms such as descriptors and a cleanup stack. There are similar techniques for conserving disk space (though the disks on Symbian devices are usually flash memory). Furthermore, all Symbian programming is event-based, and the CPU is switched into a low power mode when applications are not directly dealing with an event. This is achieved through a programming idiom called active objects. Similarly the Symbian approach to threads and processes is driven by reducing overheads.
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[4]. This is a feature which is not available in Linux. This has allowed Symbian EKA2 phones to become smaller, cheaper and more power efficient than their predecessors[citation needed].
[edit]Competition

Symbian is the leading OS in the "smart mobile device" market. Statistics published in November 2008 showed that Symbian OS had a 46.6% share of the smart mobile devices shipped in third quarter of 2008, with Apple having 17.3% (through iPhone OS), RIM having 15.3% and Microsoft having 13.5% (through Windows CE and Windows Mobile).[5] Other competitors include Palm OS, Qualcomm's BREW, Google Android, SavaJe, Linux and MontaVista Software.
[edit]Structure

The Symbian System 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 required functions, the application view, data model and data interface, are created independently and interact solely through their APIs with the other classes.
Many other things do not yet fit into this model – for example, SyncML, Java ME providing another set of APIs on top of most of the OS and multimedia. Many of these are frameworks, and vendors are expected to supply plug-ins to these frameworks from third parties (for example, Helix Player for multimedia codecs). This has the advantage that the APIs to such areas of functionality are the same on many phone models, and that vendors get a lot of flexibility. But it means that phone vendors needed to do a great deal of integration work to make a Symbian OS phone.
Symbian includes a reference user-interface called "TechView". It provides a basis for starting customisation and is the environment in which much Symbian test and example code runs. It is very similar to the user interface from the Psion Series 5 personal organiser and is not used for any production phone user interface.
[edit]History

[edit]Psion
In 1980, Psion was founded by David Potter.
[edit]EPOC


Osaris PDA by Oregon Scientific with EPOC operating system
EPOC is a family of graphical operating systems developed by Psion for portable devices, primarily PDAs. EPOC came from epoch, the beginning of an era, but was backfitted by the engineers to "Electronic Piece Of Cheese".[6]
[edit]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 pre-emptive 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 OPL and an IDE called OVAL. SIBO devices included the: MC200, MC400, Series 3 (1991-1998), 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 (the hardware for which it was designed did not have pointer input).
In the late 1990s the operating system was referred to as EPOC16 to distinguish it from Psion's then-new EPOC32 OS.
[edit]EPOC32
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 [1]). 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).
In June 1998, Psion Software became Symbian, a major joint venture between Psion and phone manufacturers Ericsson, Motorola, and Nokia. As of Release 6, EPOC became known simply as Symbian OS.
[edit]EPOC OS Releases 1–5
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 phone 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.
[edit]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 sometime is called ER6. Psion gave 130 key staff to the new company and retained a 31% shareholding in the spun-out business.
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.
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.
[edit]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.
[edit]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.
[edit]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.
[edit]Symbian OS 9
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.
A Symbian developer proclaims that porting from Symbian 8.x to Symbian 9.x is a more daunting process than Symbian says.[7]
[edit]Symbian OS 9.1 and open source development
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.[8] 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 theSymbian 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.
The Symbian Foundation was announced in June 2008 and came into existence in 2009. Its objective was to publish the source for the entire Symbian platform under the OSI- and FSF-approved Eclipse Public License (EPL). However, components within Symbian OS were licensed from third parties which prevented the foundation from publishing the full source under EPL immediately. Initially much of the source was published under a more restrictive Symbian Foundation License (SFL) and available to foundation member companies only.
[edit]Open source software for Symbian 9.1
Open source software for Symbian is available[9][10]and following software has been ported or rewritten for Symbian 9.1:
[edit]Utilities
Mobile Web Server, a port of the Apache HTTP Server
Nokia Internet Radio, an Internet radio player, that works with SHOUTcast directory
PuTTY, a telnet/ssh client[11]
SymTorrent, a bittorrent client
Symella, a gnutella client
[edit]Game emulation
ScummVM
DOSBox (for Symbian 9.1 and above)
[edit]Multimedia
OggPlay – Audio player with ogg vorbis audio format support
[edit]Frameworks
Qt (toolkit) for S60[12][13][14][15][16][17][18][19]
Symbian also announced P.I.P.S. (PIPS Is POSIX on Symbian) which may increase the number of open source projects written for Symbian 9.1.[20][21]
Python for S60, a general port of the Python programming language
[edit]Mobile Office
OfficeReader – Opensource document reader for S60
[edit]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 E90, Nokia N95, Nokia N82 and Nokia 5700.
[edit]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 E75 and others feature Symbian OS 9.3.
[edit]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 5800 XpressMusic, Nokia 5530 XpressMusic and Sony Ericsson Satio. 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.
[edit]Symbian OS 9.5
In 26 March 2007 Symbian Ltd. announced v9.5 which includes native support for mobile digital television broadcasts in DVB-H and ISDB-T formats and also location services.[22] There is no device announced yet under this version.
[edit]Integrated Symbian platform
Symbian platform is the open source operating system and software platform for mobile devices created by merging and integrating software assets contributed by Nokia, NTT DoCoMo, Sony Ericsson and Symbian Ltd. (through the Symbian Foundation), including the Symbian OS assets as its core, the S60, UIQ and MOAP(S) user interfaces. It is being actively developed by the Symbian Foundation.
This integrated Symbian platform is the successor to Symbian OS following the official launch of the Symbian Foundation in April 2009.
[edit]Symbian^1
Symbian^1, as the first release, forms the basis for the platform. It incorporates Symbian OS and S60 5th Edition (which is built on Symbian OS 9.4) and thus it was not yet open source.[23]
[edit]Symbian^2, Symbian^3 and Symbian^4
The first open source version of Symbian is Symbian^2[23][24], however as of 3 December 2009 there are no devices with this version announced. [25]
Other versions of the Symbian platform under development include Symbian^3 [26] and Symbian^4. [27]
It has been suggested that Nokia might skip the Symbian^2 release of the platform. Instead the first phones running Symbian (not counting Symbian^1) will be announced in the first half of 2010 and will start shipping in the second half of 2010. These phones will run Symbian^3. [28]
[edit]Applications for the Symbian Platform
Symbian Horizon is an application-publishing program and directory of applications for Symbian mobile devices that was launched on 27 October 2009.[29][30]
Key to colours
Symbian OS before platform integration
unreleased Symbian platform milestone
Symbian edition Devices
Symbian OS 9.3
(Corresponds to S60 3rd Edition, Feature Pack 2)
Nokia 5730 XpressMusic[31]
Nokia E75[31]
Nokia N96[31]
Nokia N86[31]
Nokia N79[31]
Samsung GT-i8510[31]
Symbian^1
(Corresponds to S60 5th Edition)
Nokia 5800 XpressMusic[32]
Nokia 5530 XpressMusic[32]
Nokia 5230[32]
Nokia N97[32]
Nokia N97 mini[32]
Nokia X6[32]
Sony Ericsson Satio[32]
Samsung i8910[32]
Symbian^2 None announced as of 3 December 2009[25]
Symbian^3 Unreleased as of 3 December 2009[25]
Symbian^4 Unreleased as of 3 December 2009[25]
[edit]Devices that use Symbian OS

On 16 November 2006, the 100 millionth smartphone running the OS was shipped.[33]
The Ericsson R380, in 2000, was the first commercially available phone based on Symbian OS. As with the modern "FOMA" phones, this device was closed, and the user could not install new C++ applications. Unlike those, however, the R380 could not even run Java applications, and for this reason, some have questioned whether it can properly be termed a 'smartphone'.
The UIQ interface was used for PDAs such as Sony Ericsson P800, P900, W950 and the RIZR Z8 and RIZR Z10.
The Nokia S60 interface is used in various phones, the first being the Nokia 7650. The Nokia N-Gage and Nokia N-Gage QD gaming/smartphone combos are also S60 platform devices. It was also used on other manufacturers' phones such as the Siemens SX1 and Samsung SGH-Z600. Recently, more advanced devices using S60 include the Nokia 6xxx and the Nseries, with the exclusion of the N8xx and N9xx; the enterprise Eseries and some models of the Nokia XpressMusic mobiles.
The Nokia 9210, 9300 and 9500 Communicator smartphones used the Nokia Series 80 interface.
The Nokia 7710 is the only device currently using the Nokia Series 90 interface.
Fujitsu, Mitsubishi, Sony Ericsson and Sharp developed phones for NTT DoCoMo in Japan, using an interface developed specifically for DoCoMo's FOMA "Freedom of Mobile Access" network brand. This UI platform is called MOAP "Mobile Oriented Applications Platform" and is based on the UI from earlier Fujitsu FOMA models.
[edit]Security

[edit]Malware
Main article: Mobile virus
Symbian OS was subject to a variety of viruses, the best known of which is Cabir. Usually these send themselves from phone to phone by Bluetooth. So far, none have taken advantage of any flaws in Symbian OS – instead, they have all asked the user whether they would like to install the software, with somewhat prominent warnings that it can't be trusted.
However, with a view that the average mobile phone user shouldn't have to worry about security, Symbian OS 9.x adopted a UNIX-style capability model (permissions per process, not per object). Installed software is theoretically unable to do damaging things (such as costing the user money by sending network data) without being digitally signed – thus making it traceable. Commercial developers who can afford the cost can apply to have their software signed via the Symbian Signed program. Developers also have the option of self-signing their programs. However, the set of available features does not include access to Bluetooth, IrDA, GSM CellID, voice calls, GPS and few others. Some operators have opted to disable all certificates other than the Symbian Signed certificates.
Some other hostile programs are listed below, but all of them still require the input of the user to run.
Drever.A is a malicious SIS file trojan that attempts to disable the automatic startup from Simworks and Kaspersky Symbian Anti-Virus applications.
Locknut.B is a malicious SIS file trojan that pretends to be patch for Symbian S60 mobile phones. When installed, it drops a binary that will crash a critical system service component. This will prevent any application from being launched in the phone.
Mabir.A is basically Cabir with added MMS functionality. The two are written by the same author, and the code shares many similarities. It spreads using Bluetooth via the same routine as early variants of Cabir. As Mabir. A activates it will search for the first phone it finds, and starts sending copies of itself to that phone.
Fontal.A is an SIS file trojan that installs a corrupted file which causes the phone to fail at reboot. If the user tries to reboot the infected phone, it will be permanently stick on the reboot, and cannot be used without disinfection – that is, the use of the reformat key combination which causes the phone to lose all data. Being a trojan, Frontal cannot spread by itself – the most likely way for the user to get infected would be to acquire the file from untrusted sources, and then install it to the phone, inadvertently or otherwise.
[edit]Hacking Symbian
S60 v3 and v5 (OS 9.x) devices can be hacked to remove the platform security introduced in OS 9.1 onwards thus allowing users to install "unsigned" files (files without certificates validated by Symbian) and allowing access to previously locked system files.[34] This allows changing of how the operating system works, allowing hidden applications etc. to be viewable and possibly increases the threat posed by mobile viruses as the operating system files are now exposed.[35].
[edit]Developing on Symbian OS

The native language of Symbian is C++, although it is not a standard implementation. There were multiple platforms based upon Symbian OS that provided SDKs for application developers wishing to target Symbian OS devices – the main ones being UIQ and S60. Individual phone products, or families, often had SDKs or SDK extensions downloadable from the manufacturer's website too. With the various UI platforms unified in the Symbian platform there should be less diversity between manufacturer's SDKs from 2010 onwards.
The SDKs contain documentation, the header files and library files required to build Symbian OS software, and a Windows-based emulator ("WINS"). Up until Symbian OS version 8, the SDKs also included a version of the GCC compiler (a cross-compiler) required to build software to work on the device.
Symbian OS 9 and the Symbian platform use a new ABI and require 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 requires the use of special techniques such as descriptors and the cleanup stack. This can make even relatively simple programs harder to implement than in other environments. Moreover, it is questionable whether Symbian's techniques, such as the memory management paradigm, are actually beneficial. It is possible that the techniques, developed for the much more restricted mobile hardware of the 1990s, simply cause unnecessary complexity in source code because programmers are required to concentrate on low-level routines instead of more application-specific features. It seems difficult, however, to make a move towards a more high-level and modern programming paradigm.[36]
Symbian C++ programming is commonly done with an IDE. For previous versions of Symbian OS, the commercial IDE CodeWarrior for Symbian OS was favoured. The CodeWarrior tools were replaced during 2006 by Carbide.c++, an Eclipse-based IDE developed by Nokia. Carbide.c++ is offered in four different versions: Express, Developer, Professional, and OEM, with increasing levels of capability. Fully featured software can be created and released with the Express edition, which is free. Features such as UI design, crash debugging etc. are available in the other, charged-for, editions. Microsoft Visual Studio 2003 and 2005 are also supported through the Carbide.vs plugin.
Symbian's flavour of C++ is very specialised.[citation needed]. However, Symbian devices can also be programmed using Python, Java ME, Flash Lite, Ruby, .NET, Web Runtime (WRT) Widgets and Standard C/C++.[37].
Visual Basic programmers can use NS Basic to develop apps for S60 3rd Edition and UIQ 3 devices.
In the past, Visual Basic, VB.NET, and C# development for Symbian were possible through AppForge Crossfire, a plugin for Microsoft Visual Studio. On 13 March 2007 AppForge ceased operations; Oracle purchased the intellectual property, but announced that they did not plan to sell or provide support for former AppForge products. Net60, a .NET compact framework for Symbian, which is developed by redFIVElabs, is sold as a commercial product. With Net60, VB.NET and C# (and other) source code is compiled into an intermediate language (IL) which is executed within the Symbian OS using a just-in-time compiler.
There is also a version of a Borland IDE for Symbian OS. Symbian OS development is also possible on Linux and Mac OS X using tools and techniques developed by the community, partly enabled by Symbian releasing the source code for key tools. A plugin that allows development of Symbian OS applications in Apple's Xcode IDE for Mac OS X is available.[38]
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. The SIS file route is more difficult for Symbian OS 9.x, because any application wishing to have any capabilities beyond the bare minimum must be signed via the Symbian Signed program. There are however various hacks, which allow installing unsigned programs with any capabilities to Symbian OS 9.x.
Introduction of the Symbian Signed system in which application developers need to pay in order to use some of the more attractive smartphone features (as contrasted to platforms like Palm OS and Windows Mobile) is making it an increasingly unpopular platform for Open Source projects[39], independent developers and small startups. This situation is worsened by the fragmentation of user interface systems (UIQ vs S60 vs MOAP)[40], meaning that developers need to build and maintain multiple incompatible versions of their software[41] if they want to target multiple devices which use the same underlying Symbian OS version.
Java ME applications for Symbian OS are developed using standard techniques and tools such as the Sun Java Wireless Toolkit (formerly the J2ME Wireless Toolkit). They are packaged as JAR (and possibly JAD) files. Both CLDC and CDC applications can be created with NetBeans. Other tools include SuperWaba, which can be used to build Symbian 7.0 and 7.0s programs using Java.
Nokia S60i phones can also run Python scripts when the interpreter Python for S60 is installed, with a custom made API that allows for Bluetooth support and such. There is also an interactive console to allow the user to write python scripts directly from the phone

mobile operating system

isis article is related to mobiles category.and this is the need of nowdays.i genxarmy,will go in detail in next post.21st century crush is cellphone and we must know on what they run.



The Nokia E71 smartphone running S60 3rd Edition, Feature Pack 1 UI on the Symbian OS v9.2
A Mobile operating system, also known as a Mobile OS, a Mobile platform, or a Handheld operating system, is the operating system that controls a mobile device—similar in principle to an operating system such as Linux or Windows that controls a desktop computer. However, they are currently somewhat simpler, and deal more with the wireless versions of broadband and local connectivity, mobile multimedia formats, and different input methods.
Contents [hide]
1 History
2 Issues and challenges
3 Market description
4 Operating systems
5 References
6 Further reading
7 External links
[edit]History

The increasing importance of mobile devices has triggered hectic competition among technology giants, like Microsoft, Apple, and Nokia in a bid to capture the bigger market share pre-emptively. However, relatively young tech firms like Symbian seem to be in the lead pack of the market, particularly in smartphones and PDA phones.[1][2] Palm, Research In Motion and Ericsson are also significant firms in the mobile platform sector. In November 2007, Google formed a Linux-based open source alliance to make inroads into this mobile platform market, raising consumer awareness of the growing mobile platform frenzy.[3]
[edit]Issues and challenges


This section needs additional citations for verification.
Please help improve this article by adding reliable references. Unsourced material may be challenged and removed. (November 2009)
Open standards are gaining more ground across the spectrum of industries related, whereas proprietary mobile platforms, like Windows Mobile, are expanding their market share. Sir Tim Berners-Lee recently re-emphasized his advocacy for open mobile standards in his keynote speech at the first annual meeting of Mobile Internet World held in Boston in November 2007. He warned against a possibility that the Internet connections worldwide may turn into "walled gardens."[4] Google announced its Linux-based open source mobile platform, Android, along with the formation of the 34-member Open Handset Alliance.
Nonetheless, mobile web does not necessarily mean a horizontal and spatial shift from PC-based web, but a severe structural change to identify the missing links, among other things, between the stationary web at home or in the office and mobile web on the go.
Top agenda items may include:
Continued connectivity between home, cars and Base Stations like Wi-Fi Hot Spots and Femtocell
Interoperability of equipment and applications, and adaptability to the ever-shifting mobile multimedia ecosystem
Behavioral tracking utilizing GPS data versus privacy concern
Real-time links between the wireless world and physical world
Financial transactions, including smart cards, SMS and Multimedia Messaging Service.
[edit]Market description

Mobile platforms are in the nascent stage, and any projection regarding the market growth is hard to make at the present time. It is noteworthy that Intel is taking the initiative to focus on portable devices other than mobile phones. They are Mobile Internet Devices (MID) and Ultra-Mobile PC (UMPC). Meantime, Palm abandoned its plan to develop Foleo, which was to be a companion device for a smartphone.
[edit]Operating systems



Market share of Smartphone operating systems as of Q2/2009 by Canalys.[5] (data does not include Palm WebOS, which was introduced in June, 2009)
Operating systems that can be found on smartphones include Symbian OS, iPhone OS, RIM's BlackBerry, Windows Mobile (marketed as Windows phone), Linux, Palm WebOS, Android and Maemo. Android, WebOS and Maemo are in turn built on top of Linux, and the iPhone OS is derived from the BSD and NeXTSTEP operating systems, which all are related to Unix.
The most common operating systems (OS) used in smartphones by Q2 2009 sales are:
Symbian OS from the Symbian Foundation (50.3% Market Share Sales Q2 2009)[5]
Symbian has the largest share in most markets worldwide, but lags behind other companies in the relatively small but highly visible North American market.[6] This matches the success of its largest shareholder[7] and customer, Nokia, in all markets except Japan. Nokia itself enjoys 52.9% of the smartphone market.[8] In Japan Symbian is strong due to a relationship with NTT DoCoMo, with only one of the 44 Symbian handsets released in Japan coming from Nokia.[9] It has been used by many major handset manufacturers, including BenQ, Fujitsu, LG, Mitsubishi, Motorola, Nokia, Samsung, Sharp, and Sony Ericsson. Current Symbian-based devices are being made by Fujitsu, Nokia, Samsung, Sharp, and Sony Ericsson. Prior to 2009 Symbian supported multiple user interfaces, i.e. UIQ from UIQ Technologies, S60 from Nokia, and MOAP from NTT DOCOMO. As part of the Symbian Foundation Platform in 2009 these three UIs were merged into a single platform which is due to be fully open source by mid 2010. It has received some adverse press attention due to virus threats (namely trojan horses).[10]
RIM BlackBerry operating system (20.9% Market Share Sales Q2 2009)[5]
This OS is focused on easy operation and was originally designed for business. Recently it has seen a surge in third-party applications and has been improved to offer full multimedia support.
iPhone OS from Apple Inc. (13.7% Market Share Sales Q2 2009)[5]
The iPhone uses an operating system called iPhone OS, which is derived from Mac OS X. Third party applications were not officially supported until the release of iPhone OS 2.0 on July 11th 2008. Before this, "jailbreaking" allowed third party applications to be installed, and this method is still available.
Windows Mobile from Microsoft (9% Market Share Sales Q2 2009)[5][11]
The Windows CE operating system and Windows Mobile middleware are widely spread in Asia. The two improved variants of this operating system, Windows Mobile 6 Professional (for touch screen devices) and Windows Mobile 6 Standard, were unveiled in February 2007. Windows Mobile benefits from the low barrier to entry for third-party developers to write new applications for the platform.[citation needed] It has been criticized for having a user interface which is not optimized for touch input by fingers; instead, it is more usable with a stylus. However, unlike iPhone OS, it does support both touch screen and physical keyboard configurations. With next major release of Windows Mobile, Windows Mobile 7, Microsoft intends to make a dramatic come-back in the industry and become a much more aggressive force in the mobile space than it has been before in the past.[12][13]
Android from Google Inc. (2.8% Market Share Sales Q2 2009)[5]
Android was developed by Google Inc.. Android is an Open Source, Linux-derived platform backed by Google, along with major hardware and software developers (such as Intel, HTC, ARM, and eBay, to name a few), that form the Open Handset Alliance.[14] This OS, though very new, already has a cult following among programmers eager to develop apps for its flexible, Open Source, back end.[15] Android promises to give developers access to every aspect of the phone's operation.[16] This lends many to foresee the promise of further growth for the Android platform.[17]
Linux operating system
Linux is strongest in China where it is used by Motorola, and in Japan, used by DoCoMo.[18][19] Rather than being a platform in its own right, Linux is used as a basis for a number of different platforms developed by several vendors, including Android, LiMo, Maemo, Openmoko and Qt Extended, which are mostly incompatible.[20][21] PalmSource (now Access) is moving towards an interface running on Linux.[22] Another platform based on Linux is being developed by Motorola, NEC, NTT DoCoMo, Panasonic, Samsung, and Vodafone.[23]
Palm webOS from Palm Inc. and Palm OS/Garnet OS from Access Co.
Palm webOS is Palm's next generation operating system.[24] PalmSource traditionally used its own platform developed by Palm Inc. Access Linux Platform (ALP) is an improvement that was planned to be launched in the first half of 2007. It will use technical specifications from the Linux Phone Standards Forum. The Access Linux Platform will include an emulation layer to support applications developed for Palm-based devices.
bada from Samsung Electronics
The bada mobile phone operating system is still in development, and Samsung expects handsets to be available in the second half of 2010.[25]
Maemo from Nokia
Maemo is a software platform developed by Nokia for smartphones and Internet Tablets. It is based on the Debian operating system.
Maemo is mostly based on open source code, and has been developed by Maemo Devices within Nokia in collaboration with many open source projects such as the Linux kernel, Debian and GNOME.
Maemo is based on Debian GNU/Linux and draws much of its GUI, frameworks and libraries from the GNOME project. It uses the Matchbox window manager and the GTK-based Hildon as its GUI and application framework.