Scribd Logo
Upload

Welcome to Scribd!

  • 51 views

    Android: An Open Handset Alliance Project

    Uploaded by

    vishal176
    This document provides an overview of the Android operating system. It describes the Open Handset Alliance that created Android as an open source platform. It then discusses the introduction and architecture of Android, including its application framework, libraries, Linux kernel, Dalvik virtual machine, and execution environment. The document also outlines the core building blocks of Android applications and development tools. Finally, it briefly touches on application lifecycles and security architecture for data storage in Android.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd

    Android: An Open Handset Alliance Project

    Uploaded by

    vishal176
    51 views28 pages
    This document provides an overview of the Android operating system. It describes the Open Handset Alliance that created Android as an open source platform. It then discusses the introduction and architecture of Android, including its application framework, libraries, Linux kernel, Dalvik virtual machine, and execution environment. The document also outlines the core building blocks of Android applications and development tools. Finally, it briefly touches on application lifecycles and security architecture for data storage in Android.

    Original Title

    v1

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PPT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document provides an overview of the Android operating system. It describes the Open Handset Alliance that created Android as an open source platform. It then discusses the introduction and architecture of Android, including its application framework, libraries, Linux kernel, Dalvik virtual machine, and execution environment. The document also outlines the core building blocks of Android applications and development tools. Finally, it briefly touches on application lifecycles and security architecture for data storage in Android.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    51 views28 pages

    Android: An Open Handset Alliance Project

    Uploaded by

    vishal176
    This document provides an overview of the Android operating system. It describes the Open Handset Alliance that created Android as an open source platform. It then discusses the introduction and architecture of Android, including its application framework, libraries, Linux kernel, Dalvik virtual machine, and execution environment. The document also outlines the core building blocks of Android applications and development tools. Finally, it briefly touches on application lifecycles and security architecture for data storage in Android.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    You are on page 1of 28

    ANDROID

    AN OPEN HANDSET ALLIANCE


    PROJECT
    OVERVIEW
    1.Open Handset Alliance
    2.Introduction To Android
    3.Introduction To The Platform
    4.Android Architecture
    5.Anatomy Of An Android Application
    6.Android Building Blocks
    7.Development Tools
    8.Life Cycle Of An Android Application
    9.Conclusion
    Open Handset Alliance
     Est. 2007, led by
    Google,open source

     Main product: Android


    Platform

     Enthusiastic support from


    Industry : both equipment
    makers and network
    operators

    HTC to deliver Android


    capable device soon!
    Open Handset Alliance Members
    INTRODUCTION
    TO
    ANDROID
    WHAT IS ANDROID?

    o A complete & modern embedded operating system

    o A cutting-edge mobile user experience

    o A world-class software stack for building applications

    o An open platform for developers, users & industry


    Why Android Was Created?

     Full phone software stack including applications


     Designed as a platform for software development
     Android is open
     Android is free
     Community support
     100% Java Phone
    HISTORY
     July 2005
    Google acquired Android Inc.
     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


    INTRODUCTION
    TO
    THE PLATFORM : ANDROID
    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
     (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
    ANDROID ARCHITECTURE
    Application Framework

    Enable applications access data from other applications ,sharing

    Providing access to non-code resources

    Enables all applications to display alerts in the status bar

    Manages the lifecycle of applications


    Libraries

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

    o Display/Graphics(SGL)

    o Media Libraries

    o SQLite –RDB engine-light weight

    o LibWebCore–web browser engine–embeddable web view


    Linux Kernel

     Linux Version 2.6


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

     Includes a set of core libraries that provides most of the


    functionality-JAVA

     Every Android application runs in its own process

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

     Device can run multiple VMs efficiently


    Android Applications Are Compiled To Dalvik Bytecode

    Write app in Java

    Compiled
    Compiled in
    in Java
    Java

    Transformed
    Transformed to
    to Dalvik
    Dalvik bytecode
    bytecode
    Execution Environment
    Anatomy of an Android Application
    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
    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

    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)
    -for alerting the user

    Services
    -is a body of code that runs in the background
    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:

    1.Android Emulator -A virtual mobile device that runs on our computer -use to
    design, debug, and test our applications in an actual Android run-time environment

    2.Android Development Tools Plugin -for the Eclipse IDE - adds powerful
    extensions to the Eclipse integrated environment

    3.Dalvik Debug Monitor Service (DDMS) -Integrated with Dalvik -this tool let us
    manage processes on an emulator and assists in debugging
    SECURE DATA ARCHITECTURE FOR STORAGE
    The public/private key pair of the user is generated directly on the handset at install
    time.

    The certificate of the user must at least be registered once in the SSO application.
    This could be done at install time of the handset application

    “Man-in-the-middle”38 attacks are not possible since the application is deployed with
    the CA certificate of the company that will be hosting the web services.

    If the device is lost, all the locally cached data is completely unreadable. The
    symmetric key that encrypted this data is also unreadable. The public/private keys that
    are central to the security architecture are protected by a passphrase.

    It is also possible to enforce a strong password policy directly from the handset
    application.
    Life Cycle of an Android Application

    An unusual and fundamental feature - process's lifetime is 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“
    “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 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)
    Applications
    Initial screen Map Browser
    CONCLUSION
     Android is open to all: industry, developers and users

     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
    THANK YOU

    You might also like

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy