ANDROID

AN OPEN HANDSET ALLIANCE

PROJECT
OVERVIEW
3.Open Handset Alliance
4.Introduction To Android
5.Introduction To The Platform
6.Android Architecture

College Of Engineering Chengannur

7.Anatomy Of An Android Application
8.Android Building Blocks
9.Development Tools
10.Life Cycle Of An Android Application
11.Conclusion

2
Open Handset Alliance

 Est. 2007, led by

Google,open source

College Of Engineering Chengannur

 Main product: Android
Platform

 Enthusiastic support from

Industry : both equipment
makers and network operators

HTC to deliver Android

capable device soon! 3
 College Of Engineering Chengannur
4
Open Handset Alliance Members
College Of Engineering Chengannur
5
INTRODUCTION

ANDROID
TO
WHAT IS ANDROID?

o A complete & modern embedded operating

system

College Of Engineering Chengannur

o A cutting-edge mobile user experience

o A world-class software stack for building

applications

o An open platform for developers, users &

industry 6
Why Android Was
Created?
 Full phone software stack including applications
 Designed as a platform for software development

College Of Engineering Chengannur

 Android is open
 Android is free
 Community support
 100% Java Phone

7
HISTORY
 July 2005
Google acquired Android Inc.

College Of Engineering Chengannur

 5 Nov 2007

Open HandSet Alliance formed-

Google, HTC, Intel, Motorola, Qualcomm,T-Mobile
 Android is the OHA first product

 12 Nov 2007

OHA released a preview of the Android OHA

8
 INTRODUCTION

College Of Engineering Chengannur

TO
THE PLATFORM : ANDROID

9
Android Features

Integrated browser based on the open source WebKit engine

SQLite for relational data storage
Media support for common audio, video, and still image formats

College Of Engineering Chengannur

(MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, GIF)
Dalvik Virtual Machine optimized for mobile devices

Cellular networking : GSM, EDGE, 3G (hardware dependent)

LAN : Bluetooth, and Wi-Fi (hardware dependent)
Graphics Hardware Acceleration
Camera, GPS and Compass (hardware dependent)
Touch screen and accelerometer for motion sensing 10
 College Of Engineering Chengannur
11
ANDROID ARCHITECTURE
Application Framework

Enable applications access data from other applications ,sharing

College Of Engineering Chengannur

Providing access to non-code resources

Enables all applications to display alerts in the status bar

Manages the lifecycle of applications

12
Libraries

 Written in C/C++ - System C Library(libc)

Display/Graphics(SGL)

College Of Engineering Chengannur



 Media Libraries

 SQLite –RDB engine-light weight

 LibWebCore–web browser engine–embeddable

web view
13
Linux Kernel

 Linux Version 2.6

College Of Engineering Chengannur

 Security, Memory & Process Management
 Proven driver model
 Efficient computing resource management
 Stable and proven OS for mobile platform

14
Android Runtime

 Includes a set of core libraries that provides most

of the functionality-JAVA

College Of Engineering Chengannur

 Every Android application runs in its own process

 Dalvik VM executes files in the (.dex) format

 Device can run multiple VMs efficiently

15
Anatomy of an Android
Application

College Of Engineering Chengannur

There are four building blocks for an Android application:

Activity
-a single screen

Intent Receiver
-to execute in reaction to an external event(Phone Ring)
Service
-code that is long-lived and runs without a UI(Media Player)

Content Provider
-an application's data to be shared with other applications
16
Android Building Blocks
These are the most important parts of the Android APIs:

AndroidManifest.xml
-the control file-tells the system what to do with the top-level
components

College Of Engineering Chengannur

Activities
-an object that has a life cycle-is a chunk of code that does some
work

Views
-an object that knows how to draw itself to the screen

Intents
-a simple message object that represents an "intention" to do
something

Notifications
-is a small icon that appears in the status bar(SMS messages) 17
-for alerting the user

Services
Development Tools
The Android SDK includes a variety of custom tools that help you
develop mobile applications on the Android platform.Three of the
most significant tools are:

•Android Emulator -A virtual mobile device that runs on our

College Of Engineering Chengannur

computer -use to design, debug, and test our applications in an
actual Android run-time environment

•Android Development Tools Plugin -for the Eclipse IDE - adds

powerful extensions to the Eclipse integrated environment

•Dalvik Debug Monitor Service (DDMS) -Integrated with Dalvik

-this tool let us manage processes on an emulator and assists in
debugging

18
Life Cycle of an Android
Application

An unusual and fundamental feature - process's lifetime is

College Of Engineering Chengannur

not directly controlled by the application itself

Deciding factors:
how important
overall memory available

To determine which processes should be killed when low on

memory: "importance hierarchy“

19
“Importance Hierarchy”(in Order Of Importance)
Foreground Process -required for what the user is currently doing

Visible Process -holding an Activity - visible to the user on-screen

College Of Engineering Chengannur

but not in the foreground(on pause)

Service Process -holding a Service - not directly visible to the

user- relevant tasks

Background Process -holding an Activity - not visible to the user -

can kill at any time(stopped)

Empty Process -doesn't hold any active application components(as

a cache to improve start-up time)

20
 College Of Engineering Chengannur
21
Applications
 College Of Engineering Chengannur
22
Browser
Map
Initial screen
CONCLUSION
 Android is open to all: industry, developers and
users

College Of Engineering Chengannur

 Participating in many of the successful open
source projects

 Aims to be as easy to build for as the web.

 Google Android is stepping into the next level

of Mobile Internet

23
THANK YOU