SlideShare a Scribd company logo

Embedded Android Workshop at Android Open 2011

Opersys inc., profile picture
Opersys inc.

This document provides an overview of embedded Android. It discusses the basics of Android including features, user experience concepts, and app concepts. It covers the history and ecosystem of Android. It also describes the legal framework, platform requirements, and development tools for Android. Key topics include components, intents, permissions, and the application framework.

TechnologyArt & Photos
1 of 159
Downloaded 201 times
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
Embedded Android Workshop 1
About â—Ź Author of: â—Ź Introduced Linux Trace Toolkit in 1999 â—Ź Originated Adeos and relayfs (kernel/relay.c) 2
About Android â—Ź Huge â—Ź Fast moving â—Ź Stealthy 3
Introduction to Embedded Android â—Ź Basics â—Ź History â—Ź Ecosystem â—Ź Legal framework â—Ź Platform and hardware requirements â—Ź Development tools 4
1. Basics â—Ź Features â—Ź UX Concepts â—Ź App Concepts 5
1.1. Features â—Ź Application framework enabling reuse and replacement of components â—Ź Dalvik virtual machine optimized for mobile devices â—Ź Integrated browser based on the open source WebKit engine â—Ź Optimized graphics powered by a custom 2D graphics library; 3D graphics based on the OpenGL ES 1.0 specification (hardware acceleration optional) â—Ź SQLite for structured data storage â—Ź Media support for common audio, video, and still image formats (MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, GIF) â—Ź GSM Telephony (hardware dependent) â—Ź Bluetooth, EDGE, 3G, and WiFi (hardware dependent) â—Ź Camera, GPS, compass, and accelerometer (hardware dependent) â—Ź Rich development environment including a device emulator, tools for debugging, memory and performance profiling, and a plugin for the Eclipse IDE 6
1.2. UX Concepts ● Browser-like ● iPhone-ish ● No user-concept of “task” ● Main keys: ● HOME ● SEARCH ● BACK ● MENU ● App-model allows users to safely install/test almost anything 7
“Click” Activity #1 Activity “Back” “Click” Activity #2 Activity #1 “Click” “Home” “Back” Activity #3 Activity #2 Activity #1 Home Menu Back 8
1.3. App Concepts ● No single entry point (No main() !?!?) ● Unlike Windows or Unix API/semantics in many ways ● Processes and apps will be killed at random: developer must code accordingly ● UI disintermediated from app “brains” ● Apps are isolated, very ● Behavior predicated on low-memory conditions 9
2. History ● 2002: ● Sergey Brin and Larry Page started using Sidekick smartphone ● Sidekick one of 1st smartphones integrating web, IM, mail, etc. ● Sidekick was made by Danger inc., co-founded by Andy Rubin (CEO) ● Brin/Page met Rubin at Stanford talk he gave on Sidekick’s development ● Google was default search engine on Sidekick ● 2004: ● Despite cult following, Sidekick wasn’t making $ ● Danger inc. board decided to replace Rubin ● Rubin left. Got seed $. Started Android inc. Started looking for VCs. ● Goal: Open mobile hand-set platform ● 2005 - July: ● Got bought by Google for undisclosed sum :) ● 2007 - November: ● Open Handset Alliance announced along with Android 10
● 2008 - Sept.: Android 1.0 is released ● 2009 - Feb.: Android 1.1 ● 2009 - Apr.: Android 1.5 / Cupcake ● 2009 - Sept.: Android 1.6 / Donut ● 2009 - Oct.: Android 2.0/2.1 / Eclair ● 2010 - May: Android 2.2 / Froyo ● 2010 - Dec.: Android 2.3 / Gingerbread ● 2011 - Jan : Android 3.0 / Honeycomb – Tablet-optimized ● 2011 – May: Android 3.1 – USB host support ● 2011 – Dec: Android 4.0 / Ice-Cream Sandwich – merge Gingerbread and Honeycomb 11
3. Ecosystem â—Ź 350k phone activations per day â—Ź 150k apps (vs. 350k for Apple's app store) â—Ź 1/3 of new smartphones sold in US â—Ź ... 12
3.1. Who's playing? â—Ź Leading IP: â—Ź Google â—Ź Semiconductor manufacturers: â—Ź ARM, Intel, Freescale, TI, Qualcomm, NVIDIA, ... â—Ź Handset manufacturers: â—Ź Motorola, Samsung, HTC, LG, Sony-Ericsson, ... â—Ź Tablet manufacturers: â—Ź Motorola, Samsung, Archos, DELL, ASUS, ... â—Ź Special-purpose devices: â—Ź Nook, Joint Battle Command-Platform, ... â—Ź App stores: â—Ź Android Market, Amazon App Store, V CAST Apps, B&N NOOK Apps, ... 13
3.2. Open Handset Alliance ● “... a group of 80 technology and mobile companies who have come together to accelerate innovation in mobile and offer consumers a richer, less expensive, and better mobile experience. Together we have developed Android™, the first complete, open, and free mobile platform.” ● Unclear what OHA does or what benefits, if any, members derive ● Not an organization with board members, staff, etc. ... just an “Alliance” ● Google's Android team are the lead on all bleeding edge dev, all else tag along ● OHA is largely inactive / absent ● Comprised of: ● Mobile Operators: Sprint, T-Mobile, Vodafone, NTT Docomo, ... ● Handset Manufacturers: HTC, Motorola, LG, Samsung, Sony Ericsson, ... ● Semiconductor Companies: ARM, Freescale, Intel, NVIDIA, Qualcomm, TI, ... ● Software Companies: Google, ... ● Commercialization Companies: ... 14
4. Legal Framework â—Ź Code access â—Ź Code licenses â—Ź Branding use â—Ź Google's own Android Apps â—Ź Alternative App stores â—Ź Oracle v. Google 15
4.1. Code Access ● Parts: ● Kernel ● Android Open Source Project (AOSP) ● Kernel: ● Should have access to latest shipped version => GPL requirement ● Google-maintained forks at android.git.kernel.org ● AOSP: ● Usually Code-drops every 6 months ● Official AOSP branches at android.git.kernel.org ● Managed by “repo” tool, an overlay to “git” ● Honeycomb (3.0) code requires talking to Google ● ... which hasn't precluded moders from lifting binaries off the SDK and putting Honeycomb on all sorts of devices, including B&N's Nook ... 16
4.2. Code Licenses ● Kernel: ● GNU General Public License (a.k.a. GPL) ● AOSP: ● Mostly Apache License 2.0 (a.k.a. ASL) ● Having GPL-free user-space was a design goal ● A few GPL and LGPL parts: mainly BlueZ and DBUS ● Some key components in BSD: Bionic and Toolbox ● “external/” directory contains a mixed bag of licenses, incl. lots of GPL ● May be desirable to add GPL/LGPL components: ● BusyBox ● uClibc / eglibc / glibc 17
4.3. Branding Use ● Android Robot: ● Very much like the Linux penguin ● Android Logo (A-N-D-R-O-I-D w/ typeface): ● Cannot be used ● Android Custom Typeface: ● Cannot be used ● Android in Official Names: ● As descriptor only: “for Android” ● Most other uses require approval ● Android in Messaging: ● Allowed if followed by a generic: “Android Application” ● Compliance through CDD/CTS involved in “approval” 18
4.4. Google's own Android Apps â—Ź The non-AOSP apps: â—Ź Android Market â—Ź YouTube â—Ź Maps and Navigation â—Ź Gmail â—Ź Voice â—Ź SkyMap â—Ź ... â—Ź Require: â—Ź CTS/CDD Compliance â—Ź Signed agreement w/ Google â—Ź Inquiries: android-partnerships@google.com 19
4.5. Alternative “App Stores” ● A couple of stores are already public: ● Android Market ● Amazon App Store ● V CAST Apps ● B&N NOOK Apps ● ... ● Nothing precluding you from having your own 20
4.6. Oracle v. Google â—Ź Filed August 2010 â—Ź Patent infringement: â—Ź 6,125,447; 6,192,476; 5,966,702; 7,426,720; RE38,104; 6,910,205; and 6,061,520 â—Ź Copyright infringement: â—Ź Android does not use any Oracle Java libraries or JVM in the final product. â—Ź Android relies on Apache Harmony and Dalvik instead. â—Ź In October 2010, IBM left Apache Harmony to join work on Oracle's OpenJDK, leaving the project practically orphaned. â—Ź In May 2011, judge orders claims cut from 132 to 3 and prior art references cut from hundreds to 8 21
5. Platform and Hardware requirements â—Ź In principle: â—Ź Android runs on top of Linux â—Ź Therefore: if it runs Linux, it can run Android â—Ź Known to have been made to work on: â—Ź ARM â—Ź x86 â—Ź MIPS â—Ź SuperH â—Ź Put in all sort of devices: â—Ź Washers, micro-wave ovens, car systems, etc. 22
5.1. Compliance Definition Document ● Software: MUST conform to AOSP ● Application Packaging Compatibility: support “.apk” files ● Multimedia Compatibility: decoders, encoders, recording, ... ● Developer Tool Compatibility: adb, ddms, Monkey ● Hardware compatibility: ● Display and Graphics ● Input Devices ● Data Connectivity ● Cameras ● Memory and Storage ● USB ● Performance Compatibility ● Security Model Compatibility ● Software Compatibility Testing ● Updatable Software: MUST include mechanism to update 23
5.2. Compatibility Test Suite 24
6. Development tools â—Ź Requirements â—Ź App dev tools and resources â—Ź App debugging 25
6.1. Requirements â—Ź App development and debugging: â—Ź Windows / Mac / Linux workstation â—Ź JDK â—Ź Eclipse w/ ADT plugin â—Ź Highly recommended: real device(S) â—Ź Platform development: â—Ź GNU cross-dev toolchain â—Ź JTAG debugger â—Ź ... more on this later 26
6.2. App dev tools and resources ● SDK: ● android – manage AVDs and SDK components ● apkbuilder – creating .apk packages ● dx – converting .jar to .dex ● adb – debug bridge ● ... ● Emulator – QEMU-based ARM emulator ● Use KVM for x86 instead ● NDK: GNU toolchain for native binaries ● Documentation: developer.android.com 27
28
29
6.3. App debugging â—Ź adb â—Ź ddms â—Ź monkeyrunner â—Ź traceview â—Ź logcat â—Ź Eclipse integration (ADT plugin) 30
Concepts and Internals 1. Android Concepts 9. Dalvik 2. Framework Intro 10.JNI 3. Native Development 11.System Server 4. Overall Architecture 12.Calling on Services 5. System startup 13.Activity Manager 6. Linux Kernel 14.Binder 7. Hardware Support 15.Stock AOSP Apps 8. Native User-Space 31
1. Android Concepts â—Ź Components â—Ź Intents â—Ź Component lifecycle â—Ź Manifest file â—Ź Processes and threads â—Ź Remote procedure calls 32
1.1. Components â—Ź 1 App = N Components â—Ź Apps can use components of other applications â—Ź App processes are automagically started whenever any part is needed â—Ź Ergo: N entry points, !1, and !main() â—Ź Components: â—Ź Activities â—Ź Services â—Ź Broadcast Receivers â—Ź Content Providers 33
1.2. Intents ● Intent = asynchronous message w/ or w/o designated target ● Like a polymorphic Unix signal, but w/o required target ● Intents “payload” held in Intent Object ● Intent Filters specified in Manifest file 34
1.3. Component lifecycle â—Ź System automagically starts/stops/kills processes: â—Ź Entire system behaviour predicated on low memory â—Ź System triggers Lifecycle callbacks when relevant â—Ź Ergo: Must manage Component Lifecycle â—Ź Some Components are more complex to manage than others 35
36
1.4. Manifest file ● Informs system about app’s components ● XML format ● Always called AndroidManifest.xml ● Activity = <activity> ... static ● Service = <service> ... static ● Broadcast Receiver: ● Static = <receiver> ● Dynamic = Context.registerReceiver() ● Content Provider = <provider> ... static 37
1.5. Processes and threads ● Processes ● Default: all callbacks to any app Component are issued to the main process thread ● <activity>—<service>—<recipient>—<provider> have process attribute to override default ● Do NOT perform blocking/long operations in main process thread: – Spawn threads instead ● Process termination/restart is at system’s discretion ● Therefore: – Must manage Component Lifecycle ● Threads: ● Create using the regular Java Thread Object ● Android API provides thread helper classes: – Looper: for running a message loop with a thread – Handler: for processing messages – HandlerThread: for setting up a thread with a message loop 38
1.6. Remote procedure calls â—Ź Android RPCs = Binder mechanism â—Ź No Sys V IPC due to in-kernel resource leakage â—Ź Binder is a low-level functionality, not used as-is â—Ź Instead: must define interface using Interface Definition Language (IDL) â—Ź IDL fed to aidl Tool to generate Java interface definitions 39
2. Framework Introduction â—Ź UI â—Ź Data storage â—Ź Security/Permissions â—Ź ... and much more ... : â—Ź Graphics â—Ź Audio and Video â—Ź Location and Maps â—Ź Bluetooth â—Ź NFC 40
2.1. UI â—Ź Everything based on hierarchy of Views and ViewGroups (layouts) â—Ź Declared in XML or dynamically through Java â—Ź UI components: â—Ź Widgets â—Ź Event handlers â—Ź Menus â—Ź Dialogs â—Ź Notifications â—Ź ... 41
2.2. Data storage â—Ź Shared preferences â—Ź Private primitive key-pair values â—Ź Internal storage â—Ź Private data on device memory â—Ź External storage â—Ź Public data on shared external device (SD) â—Ź SQLite DB â—Ź Private DB â—Ź Network connection â—Ź Web-based storage (REST) 42
2.3. Security/Permissions ● Most security enforced at process level: UID, GID ● Permissions enforce restrictions on: ● Per-process operations ● Per-URI access ● Applications are sandboxed ● Specific permissions required to “exit” sandbox ● Decision to grant access based on: ● Certificates ● User prompts ● All permissions must be declared statically 43
3. Native development â—Ź What it can and cannot do â—Ź Getting and installing the NDK â—Ź Using the NDK â—Ź Implementing fully native apps 44
3.1. What it can and cannot do â—Ź Useful for: â—Ź Porting existing body of code to Android â—Ź Developing optimized native apps, especially for gaming â—Ź Provides: â—Ź Tools and build files to generate native code libraries from C/C++ â—Ź Way to embed native libs into .apk â—Ź Set of stable (forward-compatible) native libs â—Ź Documentation, samples and tutorials â—Ź Enables: â—Ź Calling native code from Java using JNI â—Ź Implementing fully native apps (since 2.3) â—Ź Doesn't allow you to: â—Ź Compile traditional Linux/Unix apps as-is 45
3.2. Getting and installing the NDK ● What’s in the NDK? ● Development tools ● Stable native APIs system headers ● Documentation - IMPORTANT ● Samples ● Getting the NDK ● http://developer.android.com/sdk/ndk/index.html ● Prerequisites ● Windows, Mac or Linux ● Complete SDK ● make (GNU’s) and awk ● For Windows, Cygwin 1.7 or higher ● NDK set up: ● Make sure prerequisites are installed ● Download and install NDK 46
3.3. Using the NDK 1.Place native code under <project>/jni/... 2.Create <project>/jni/Android.mk to describe native code to NDK 3.Optional: create <project>/jni/Application.mk for describing which natives sources are required by app 4.Build native code: • cd <project> • <ndk>/ndk-build 5.Compile app with SDK. Native code will be shared lib in .apk file. 47
3.4. Implementing fully native apps ● Android 2.3 and up ● Native lifecycle management ● Still runs within context of dedicated Dalvik VM ● Can use JNI to call on Java functions ● Limited API: ● Activity lifecycle management ● Input events and sensors ● Window management ● Direct access to assets ● Make sure your activity is called: “android.app.NativeActivity” 48
4.1. Overall Architecture - EL 49
4.2. Overall Architecture - Android 50
5. System Startup â—Ź Bootloader â—Ź Kernel â—Ź Init â—Ź Zygote â—Ź System Server â—Ź Activity Manager â—Ź Launcher (Home) 51
5.1. Bootloader ● aosp/bootable/bootloader ● Custom bootloader for Android ● USB-based ● Implements the “fastboot” protocol ● Controlled via “fastboot” cli tool on host ● aosp/bootable/recovery ● UI-based recovery boot program ● Accessed through magic key sequence at boot ● Usually manufacturer specific variant 52
● Flash layout: 0x000003860000­0x000003900000 : "misc" 0x000003900000­0x000003e00000 : "recovery" 0x000003e00000­0x000004300000 : "boot" Kernel 0x000004300000­0x00000c300000 : "system" /system 0x00000c300000­0x0000183c0000 : "userdata" /data 0x0000183c0000­0x00001dd20000 : "cache" /cache 0x00001dd20000­0x00001df20000 : "kpanic" 0x00001df20000­0x00001df60000 : "dinfo" 0x00001df60000­0x00001dfc0000 : "setupdata" 0x00001dfc0000­0x00001e040000 : "splash1" 0x000000300000­0x000001680000 : "modem" From Acer Liquid-E 53
5.2. Kernel â—Ź Early startup code is very hardware dependent â—Ź Initializes environment for the running of C code â—Ź Jumps to the architecture-independent start_kernel() function. â—Ź Initializes high-level kernel subsystems â—Ź Mounts root filesystem â—Ź Starts the init process 54
5.3. Android Init ● Open, parses, and runs /init.rc: ● Create mountpoints and mount filesystems ● Set up filesystem permissions ● Set OOM adjustments properties ● Start daemons: – adbd – servicemanager (binder context manager) – vold – netd – rild – app_process -Xzygote (Zygote) – mediaserver – ... 55
5.4. Zygote, etc. ● Init: ● app_process -Xzygote (Zygote) ● frameworks/base/cmds/app_process/app_main.cpp: ● runtime.start(“com.android.internal.os.Zygote”, ... ● frameworks/base/core/jni/AndroidRuntime.cpp: ● startVM() ● Call Zygote's main() ● frameworks/base/core/java/com/android/internal/os/Zy goteInit.java: ● ... 56
● preloadClasses() ● startSystemServer() ● ... magic ... ● Call SystemServer's run() ● frameworks/base/services/java/com/android/server /SystemServer.java: ● Start all system services/managers ● Start ActivityManager: – Send Intent.CATEGORY_HOME – Launcher2 kicks in 57
6. Linux Kernel 58
6.1. Androidisms ● Wakelocks ● lowmem handler ● Binder ● ashmem – Anonymous Shared Memory ● RAM console ● Logger ● ... 59
7. Hardware support Bluetooth BlueZ through D-BUS IPC (to avoid GPL contamination it seems) GPS Manufacturer-provided libgps.so Wifi wpa_supplicant Display Std framebuffer driver (/dev/fb0) Keymaps and Keyboards Std input event (/dev/event0) Lights Manufacturer-provided liblights.so Backlight Keyboard Buttons Battery Notifications Attention Audio Manufacturer-provided libaudio.so (could use ALSA underneath ... at least as illustrated in their porting guide) Camera Manufacturer-provided libcamera.so (could use V4L2 kernel driver underneath ... as illustrated in porting guide) Power Management “Wakelocks” kernel patch Sensors Manufacturer-provided libsensors.so Accelerometer Magnetic Field Orientation Gyroscope Light Pressure Temperature Proximity Radio Layer Interface Manufacturer-provided libril-<companyname>-<RIL version>.so 60
8. Native User-Space â—Ź Mainly â—Ź /data => User data â—Ź /system => System components â—Ź Also found: â—Ź /dev â—Ź /proc â—Ź /sys â—Ź /sbin â—Ź /mnt â—Ź /cache â—Ź Etc. 61
â—Ź Libs: Bionic, SQLite, SSL, OpenGL|ES, Non-Posix: limited Pthreads support, no SysV IPC â—Ź Toolbox â—Ź Daemons: servicemanager, vold, rild, netd, adbd, ... 62
9. Dalvik â—Ź Sun-Java = Java language + JVM + JDK libs â—Ź Android Java = Java language + Dalvik + Apache Harmony â—Ź Target: â—Ź Slow CPU â—Ź Relatively low RAM â—Ź OS without swap space â—Ź Battery powered â—Ź Now has JIT 63
9.1. Dalvik's .dex files ● JVM munches on “.class” files ● Dalvik munches on “.dex” files ● .dex file = .class files post-processed by “dx” utility ● Uncompressed .dex = 0.5 * Uncompressed .jar 64
10. JNI – Java Native Interface ● Call gate for other languages, such as C, C++ ● Equivalent to .NET's pinvoke ● Usage: include and call native code from App ● Tools = NDK ... samples included ● Check out “JNI Programmer's Guide and Specification” - freely available PDF 65
11. System Server Entropy Service Device Policy Audio Service Power Manager Status Bar Headset Observer Activity Manager Clipboard Service Dock Observer Telephone Registry Input Method Service UI Mode Manager Service Package Manager NetStat Service Backup Service Account Manager NetworkManagement Service AppWidget Service Content Manager Connectivity Service Recognition Service System Content Providers Throttle Service Status Bar Icons Battery Service Accessibility Manager DiskStats Service Lights Service Mount Service ADB Settings Observer Vibrator Service Notification Manager Alarm Manager Device Storage Monitor Init Watchdog Location Manager Sensor Service Search Service Window Manager DropBox Service Bluetooth Service Wallpaper Service 66
12. Calling on System Services â—Ź Use getSystemService â—Ź Ex: NotificationManager Object reference: String ns = Context.NOTIFICATION_SERVICE; NotificationManager mNotificationManager = (NotificationManager) getSystemService(ns); â—Ź Prepare your content â—Ź Call on the object: mNotificationManager.notify(HELLO_ID, notification); 67
13. ActivityManager â—Ź Start new Activities, Services â—Ź Fetch Content Providers â—Ź Intent broadcasting â—Ź OOM adj. maintenance â—Ź Application Not Responding â—Ź Permissions â—Ź Task management â—Ź Lifecycle management 68
â—Ź Ex. starting new app from Launcher: â—Ź onClick(Launcher) â—Ź startActivity(Activity.java) â—Ź <Binder> â—Ź ActivityManagerService â—Ź startViaZygote(Process.java) â—Ź <Socket> â—Ź Zygote 69
14. Binder ● CORBA/COM-like IPC ● Data sent through “parcels” in “transactions” ● Kernel-supported mechanism ● /dev/binder ● Check /proc/binder/* ● android.* API connected to System Server through binder. 70
71
15. Stock AOSP Apps /packages/apps /packages/providers /packages/inputmethods AccountsAndSettings Launcher2 ApplicationProvider LatinIME AlarmClock Mms CalendarProvider OpenWnn Bluetooth Music ContactsProvider PinyinIME Browser PackageInstaller DownloadProvider Calculator Protips DrmProvider Calendar Provision GoogleContactsProvider Camera QuickSearchBox MediaProvider CertInstaller Settings TelephonyProvider Contacts SoundRecorder UserDictionaryProvider DeskClock SpeechRecorder Email Stk Gallery VoiceDialer HTMLViewer 72
Android Open Source Project â—Ź Tools and location â—Ź Content â—Ź Building â—Ź Build system â—Ź Adding new applications â—Ź Images â—Ź Using adb 73
1. Tools and location ● Location: ● http://android.git.kernel.org/ ● Get “repo”: $ curl http://android.git.kernel.org/repo > ~/bin/repo $ chmod a+x ~/bin/repo ● Fetch the AOSP: ● Make sure you fetch a tagged release ● Gingerbread: $ repo init -u git://android.git.kernel.org/platform/manifest.git -b gingerbread $ repo sync 74
2. Content bionic C library replacement bootable Reference bootloader build Build system cts Compatibility Test Suite dalvik Dalvik VM development Development tools device Device-specific files and components external Copy of external projects used by AOSP frameworks System services, android.*, Android-related cmds, etc. hardware Hardware support libs libcore Apache Harmony ndk The NDK packages Stock Android apps, providers, etc. prebuilt Prebuilt binaries sdk The SDK system pieces of the world that are the core of the embedded linux platform at the heart of Android. 75
3. Building ● Requires 64-bit Ubuntu 10.04 ● Packages required: $ sudo⌴ apt-get⌴ install⌴ build-essential⌴ libc6-dev⌴ > ia32-libs⌴ lib32z1⌴ bison⌴ flex⌴ gperf⌴ git-core⌴ > g++⌴ libc6-dev-i386⌴ libz-dev⌴ libx11-dev⌴ > libstdc++6⌴ lib32ncurses5⌴ lib32ncurses5-dev⌴ > g++-multilib ● Possibly fix a few symbolic links: $ sudo ln⌴ -s⌴ /usr/lib32/libstdc++.so.6⌴ /usr/lib32/libstdc++.so $ sudo ln⌴ -s⌴ /usr/lib32/libz.so.1⌴ /usr/lib32/libz.so 76
● Set up build environment: $ .⌴ build/envsetup.sh $ lunch ● Launch build and go watch tonight's hockey game: $ make -j2 ● ... though you should check your screen at breaks ... ● Just launch emulator when it's done: $ emulator & 77
● Some nice tricks: ● See build/envsetup.sh for commands ● Do use ccache (compiler cache): $ export USE_CCACHE=1 ● Use “lunch” from AOSP root to set env vars – You'll need that if you come back later and want to relaunch emulator from AOSP root: $ . build/envsetup.sh $ lunch $ emulator 78
4. Build system ● Non-Recursive ● “Modules” build predicated on Android.mk 79
5. Adding new applications â—Ź Add application in [aosp]/packages/apps â—Ź Can use Eclipse to create initial version â—Ź Copy Eclipse project to packages/apps â—Ź Add an appropriate Android.mk file to project â—Ź Add project to PRODUCT_PACKAGES in [aosp]/build/target/product/core.mk 80
6. Images â—Ź All output and build in [aosp]/out/ â—Ź Images at [aosp]/out/target/product/generic/: â—Ź ramdisk.img â—Ź system.img â—Ź userdata-qemu.img â—Ź Kernel is in: â—Ź prebuilt/android-arm/kernel/kernel-qemu â—Ź Emulator overrides: â—Ź -kernel â—Ź -initrd 81
7. Using adb â—Ź Can use to control/interface w/ running AOSP, including emulator. â—Ź Shell: Host $ adb shell Target # â—Ź Dumping the log: $ adb logcat â—Ź Copying files to/from target: $ adb push foo /data/local $ adb pull /proc/config.gz 82
Kernel Selection â—Ź Google: â—Ź http://android.git.kernel.org/ â—Ź Vanilla: â—Ź http://www.kernel.org â—Ź Either way ... you're screwed: â—Ź Android kernel is a fork â—Ź No resolution in sight â—Ź Cannot use vanilla kernel as-is ... androidisms 83
Native Android User-Space â—Ź Filesystem layout â—Ź Bionic â—Ź Toolbox â—Ź Init â—Ź Native daemons â—Ź Power tools 84
1. Filesystem layout ● /acct => Control Group mount point (Documentation/cgroups.txt) ● /cache => cache flash partition ● /d => Symlink to /sys/kernel/debug ● /data => Android's “/data” filesystem ● /dev => Device nodes ● /etc => Symlink to /system/etc ● /mnt => Temporary mount point ● /proc => procfs ● /root => unused ● /sbin => eventd and adbd ● /sdcard => SD card mountpoint ● /sys => sysfs ● /system => Android's “/system” filesystem ● /vendor => Symlink to /system/vendor 85
1.1. /system ● /app => Stock apps installed ● /bin => Native binaries and daemons ● /etc => Configuration files ● /fonts => TTFs ● /framework => Android framework .jar files ● /lib => Native libraries ● /usr => Miniature “/usr” ● /xbin => Optional/Extra binaries 86
1.2. /data ● /anr => ANR traces ● /app => App install location ● /app-private => Protected apps ● /backup => For Backup Manager ● /dalvik-cache => Dalvik DEX cache ● /data => App data ● /dontpanic => Last panic output (console + threads) for “dumpstate” ● /local => Shell-writable space ● /misc => Misc. data (wifi, vpn, bluetooth, ...) ● /property => Persistent system properties (country, lang., ...) ● /secure => Secure Android data available ● /system => System data 87
2. Bionic â—Ź In aosp: â—Ź /bionic â—Ź In filesystem: â—Ź /system/lib â—Ź Provides: â—Ź libc â—Ź libm â—Ź libdl â—Ź libstd++ â—Ź libthread_db â—Ź linker 88
3. Toolbox â—Ź In aosp: â—Ź /system/core/toolbox â—Ź In filesystem: â—Ź /system/bin/toolbox â—Ź Provides alarm date getevent insmod ls mv powerd renice schedtop smd top dd getprop ioctl lsmod nandread printenv rm sendevent start umount cat hd ionice lsof netstat ps rmdir setconsole stop uptime chmod df id kill mkdir newfs_msdos r rmmod setkey sync vmstat chown dmesg ifconfig ln readtty rotatefb setprop syren watchprops cmp exists iftop log mount notify reboot route sleep wipe 89
4. Init â—Ź In aosp: â—Ź /system/core/init â—Ź In filesystem: â—Ź /init â—Ź Relies on: â—Ź /init.rc â—Ź /init.[board].rc â—Ź /ueventd.rc â—Ź /ueventd.[board].rc â—Ź /system/etc/init.[board].sh 90
5. Native daemons â—Ź servicemanager â—Ź vold â—Ź rild â—Ź netd â—Ź adbd â—Ź installd 91
5.1. servicemanager â—Ź In aosp: â—Ź /frameworks/base/cmds/servicemanager/ â—Ź In filesystem: â—Ź /system/bin/ â—Ź Provides: â—Ź Context management for binder â—Ź Service index for entire system 92
5.2. vold â—Ź In aosp: â—Ź /system/vold/ â—Ź In filesystem: â—Ź /system/bin/ â—Ź Provides: â—Ź Volume mounter â—Ź Auto-mount â—Ź Auto-format mounted devices 93
5.3. rild ● In aosp: ● /hardware/ril/mock-ril/ ● In filesystem: ● /system/bin/ ● Provides: ● “Radio Interface Layer” to phone hardware 94
5.4. netd â—Ź In aosp: â—Ź /system/netd/ â—Ź In filesystem: â—Ź /system/bin/ â—Ź Provides: â—Ź Management of aspects of networking â—Ź Interfaces with Network Management service 95
5.5. adbd ● In aosp: ● /system/core/adb/ ● In filesystem: ● /sbin ● Provides: ● Interfaces with host “adb” command ● Remote debugging capabilities ● Access to shell ● Package install/uninstall ● ... see “adb help” on host for full detail 96
5.6. installd â—Ź In aosp: â—Ź /frameworks/base/cmds/installd â—Ź In filesystem: â—Ź /system/bin/ â—Ź Provides: â—Ź Package install/uninstall â—Ź Sanity checks and verifications â—Ź Interfaces with Package Manager service 97
6. Power tools â—Ź dumpstate â—Ź dumpsys â—Ź service â—Ź logcat 98
System Server â—Ź Services run by System Server â—Ź Observing the System Server â—Ź Calling on system services â—Ź Inside a few system services â—Ź Creating your own system service 99
1. Services run by the System Server Entropy Service Device Policy Audio Service Power Manager Status Bar Headset Observer Activity Manager Clipboard Service Dock Observer Telephone Registry Input Method Service UI Mode Manager Service Package Manager NetStat Service Backup Service Account Manager NetworkManagement Service AppWidget Service Content Manager Connectivity Service Recognition Service System Content Providers Throttle Service Status Bar Icons Battery Service Accessibility Manager DiskStats Service Lights Service Mount Service ADB Settings Observer Vibrator Service Notification Manager Alarm Manager Device Storage Monitor Init Watchdog Location Manager Sensor Service Search Service Window Manager DropBox Service Bluetooth Service Wallpaper Service 100
1.1. Some stats â—Ź frameworks/base/services/java/com/android/ser ver: â—Ź 3.5 M â—Ź ~100 files â—Ź 85 kloc â—Ź Activity manager: â—Ź 920K â—Ź 30+ files â—Ź 20 kloc 101
2. Observing the System Server â—Ź Logcat â—Ź dumpsys 102
2.1. logcat ● Find the System Server's PID $ adb shell ps | grep system_server system 63 32 120160 35408 ffffffff afd0c738 S system_server ● Look for its output: $ adb logcat | grep “63)” ... D/PowerManagerService( 63): bootCompleted I/TelephonyRegistry( 63): notifyServiceState: 0 home Android Android 310260 UMTS CSS not supp... I/TelephonyRegistry( 63): notifyDataConnection: state=0 isDataConnectivityPossible=false reason=null interfaceName=null networkType=3 I/SearchManagerService( 63): Building list of searchable activities I/WifiService( 63): WifiService trying to setNumAllowed to 11 with persist set to true I/ActivityManager( 63): Config changed: { scale=1.0 imsi=310/260 loc=en_US touch=3 keys=2/1/2 nav=3/1 ... I/TelephonyRegistry( 63): notifyMessageWaitingChanged: false I/TelephonyRegistry( 63): notifyCallForwardingChanged: false I/TelephonyRegistry( 63): notifyDataConnection: state=1 isDataConnectivityPossible=true reason=simL... I/TelephonyRegistry( 63): notifyDataConnection: state=2 isDataConnectivityPossible=true reason=simL... D/Tethering( 63): MasterInitialState.processMessage what=3 I/ActivityManager( 63): Start proc android.process.media for broadcast com.android.providers.downloads/.DownloadReceiver: pid=223 uid=10002 gids={1015, 2001, 3003} I/RecoverySystem( 63): No recovery log file W/WindowManager( 63): App freeze timeout expired. ... 103
2.2. dumpsys Currently running services: SurfaceFlinger accessibility account activity alarm appwidget audio backup ... wifi window ------------------------------------------------------------------------------- DUMP OF SERVICE SurfaceFlinger: + Layer 0x396b90 z= 21000, pos=( 0, 0), size=( 480, 800), needsBlending=1, needsDithering=1, invalidat ... 0] name=com.android.launcher/com.android.launcher2.Launcher client=0x391e48, identity=6 [ head= 1, available= 2, queued= 0 ] reallocMask=00000000, inUse=-1, identity=6, status=0 format= 1, [480x800:480] [480x800:480], freezeLock=0x0, dq-q-time=53756 us ... 104
3. Calling on System Services â—Ź Use getSystemService â—Ź Ex: NotificationManager Object reference: String ns = Context.NOTIFICATION_SERVICE; NotificationManager mNotificationManager = (NotificationManager) getSystemService(ns); â—Ź Prepare your content â—Ź Call on the object: mNotificationManager.notify(HELLO_ID, notification); 105
4. Inside a few System Services ● Get the AOSP ... repo, etc. ● Tricks: ● Import into Eclipse and collapse methods ● Use reverse-engineering tools: – Imagix – Rationale – Lattix – Scitools – ... ● Be patient, this isn't documented anywhere ... 106
4.1. ActivityManager â—Ź Start new Activities, Services â—Ź Fetch Content Providers â—Ź Intent broadcasting â—Ź OOM adj. maintenance â—Ź Application Not Responding â—Ź Permissions â—Ź Task management â—Ź Lifecycle management 107
â—Ź Ex. starting new app from Launcher: â—Ź onClick(Launcher) â—Ź startActivity(Activity.java) â—Ź <Binder> â—Ź ActivityManagerService â—Ź startViaZygote(Process.java) â—Ź <Socket> â—Ź Zygote 108
4.2. Package Manager â—Ź 10 kloc â—Ź 450 K â—Ź Installation / removal â—Ź Permissions â—Ź Intent resolution (also IntentResolver.java) â—Ź Called by Activity Manager 109
4.3. Window Manager â—Ź Main thread â—Ź Window manipulation â—Ź Wallpaper handling â—Ź Orientation â—Ź Focus â—Ź Layering â—Ź Input event management 110
4.4. Notification Manager â—Ź Toasts â—Ź Notifications â—Ź Sound playback (see NotificationPlayer.java) 111
4.5. Power Manager â—Ź Wakelocks â—Ź Sleep â—Ź Brightness â—Ź Lock 112
4.6. Network Management Service ● Talks to “netd” /system/netd ● Interface configuration ● Tethering ● DNS 113
4.7. Mount Service â—Ź Mount / Unmount â—Ź Format â—Ź USB mass storage â—Ź OBB 114
4.8. Location Manager â—Ź Manage location providers â—Ź getBestProvider() â—Ź Proximity alerts â—Ź Last known location 115
4.9. Status Bar Manager â—Ź Expand / collapse â—Ź Icon visibility â—Ź Reveal callbacks â—Ź Callbacks for notification manager 116
4.10. Backup Manager â—Ź Enable / disable â—Ź Transport management â—Ź backupNow() â—Ź ... 117
5. Creating your own System Service ● Add your code to: frameworks/base/services/java/com/android/server/ ● Have the SystemServer.java init+reg. your service ● Define hardware API for apps ● Expose through: ● frameworks/base/core/java/android/os/[server].aidl ● Call on native “driver” code through JNI ● Implement or connect to appropriate driver ● Create an app that calls on service ● May need to create new SDK ... 118
5.1. OpersysService.java package com.android.server; import android.content.Context; import android.os.Handler; import android.os.IOpersysService; import android.os.Looper; import android.os.Message; import android.os.Process; import android.util.Log; public class OpersysService extends IOpersysService.Stub {     private static final String TAG = "OpersysService";     private OpersysWorkerThread mWorker;     private OpersysWorkerHandler mHandler;     private Context mContext;     public OpersysService(Context context) { super(); mContext = context; mWorker = new OpersysWorkerThread("OpersysServiceWorker"); mWorker.start(); Log.i(TAG, "Spawned worker thread");     }     public void setValue(int val) { Log.i(TAG, "setValue " + val); Message msg = Message.obtain(); msg.what = OpersysWorkerHandler.MESSAGE_SET; msg.arg1 = val; mHandler.sendMessage(msg); 119     }
    private class OpersysWorkerThread extends Thread{ public OpersysWorkerThread(String name) {     super(name); } public void run() {     Looper.prepare();     mHandler = new OpersysWorkerHandler();     Looper.loop(); }     }     private class OpersysWorkerHandler extends Handler { private static final int MESSAGE_SET = 0; @Override public void handleMessage(Message msg) {     try { if (msg.what == MESSAGE_SET) {     Log.i(TAG, "set message received: " + msg.arg1); }     }     catch (Exception e) { // Log, don't crash! Log.e(TAG, "Exception in OpersysWorkerHandler.handleMessage:", e);      } }     } } 120
5.2. IOpersysService.aidl package android.os; interface IOpersysService { /** * {@hide} */ void setValue(int val); } 121
5.3. frameworks/base/Android.mk ... core/java/android/os/IPowerManager.aidl core/java/android/os/IOpersysService.aidl core/java/android/os/IRemoteCallback.aidl ... 122
5.4. SystemServer.java Should eventually be Context.OPERSYS_SERVICE ...    try {                 Slog.i(TAG, "Opersys Service");                 ServiceManager.addService(“opersys”, new OpersysService(context));             } catch (Throwable e) {                 Slog.e(TAG, "Failure starting OpersysService Service", e);             } ... 123
5.5. HelloServer.java package com.opersys.helloserver; import android.app.Activity; import android.os.Bundle; import android.os.ServiceManager; import android.os.IOpersysService; import android.util.Log; public class HelloServer extends Activity {     private static final String DTAG = "HelloServer";     /** Called when the activity is first created. */     @Override     public void onCreate(Bundle savedInstanceState) {         super.onCreate(savedInstanceState);         setContentView(R.layout.main);                  IOpersysService om =  IOpersysService.Stub.asInterface(ServiceManager.getService("opersys"));         try {     Log.d(DTAG, "Going to call service");     om.setValue(20);     Log.d(DTAG, "Service called succesfully");         }         catch (Exception e) {     Log.d(DTAG, "FAILED to call service");     e.printStackTrace();         }     } 124 }
Hardware Abstraction Layer /frameworks/base/core/... /frameworks/base/services/java/... AOSP-provided ASL /frameworks/base/services/jni/ /hardware/libhardware/ /device/[MANUF.]/[DEVICE] Manuf.-provided /sdk/emulator/ Manuf. license Kernel or module Manuf.-provided GPL-license 125
â—Ź [aosp]/hardware/libhardware/include/hardware â—Ź gps.h â—Ź lights.h â—Ź sensors.h â—Ź [aosp]/hardware/ril/include/telephony/ â—Ź ril.h â—Ź Examples in [aosp]/device/samsung/crespo/ â—Ź libaudio â—Ź libcamera â—Ź liblight â—Ź libsensors â—Ź Using JNI to call C functions 126
1. Call to JNI public class HelloJni extends Activity {     /** Called when the activity is first created. */     @Override     public void onCreate(Bundle savedInstanceState)     {         super.onCreate(savedInstanceState);         /* Create a TextView and set its content.          * the text is retrieved by calling a native          * function.          */         TextView  tv = new TextView(this);         tv.setText( stringFromJNI() + " " + pid() );         setContentView(tv);     }     /* A native method that is implemented by the      * 'hello­jni' native library, which is packaged      * with this application.      */     public native String  stringFromJNI(); ...     /* this is used to load the 'hello­jni' library on application      * startup. The library has already been unpacked into      * /data/data/com.example.HelloJni/lib/libhello­jni.so at      * installation time by the package manager.      */     static {         System.loadLibrary("hello­jni");     } } 127
2. JNI function in C jstring Java_com_example_hellojni_HelloJni_stringFromJNI( JNIEnv* env,                                                   jobject thiz ) {     return (*env)­>NewStringUTF(env, "Hello from JNI !"); } 128
Android Framework â—Ź Location and components â—Ź android.* â—Ź Customization 129
1. Location and components ● [aosp]/frameworks/base ● /cmds => native cmds and daemons ● /core => android.* and com.android.* ● /data => Fonts and sounds ● /graphics => 2D & Renderscript ● /include => “C” includes ● /keystore => security key store ● /libs => “C” libraries ● /location => Location provider ● /media => Stagefright, codecs, etc. ● /native => Native code for some frameworks components ● /obex => Bluetooth obex ● /opengl => GL library and java code ● /packages => A few core packages (Status Bar) ● /services => System server ● /telephony => Phone related functionality ● /tools => A few core tools (aapt, aidl, ...) ● /voip => RTP & SIP interfaces ● /vpn => VPN functionality ● /wifi => Wifi manager, monitor, etc. 130
2. android.* accessibilityservice  content   hardware            pim         speech   accounts              database  inputmethodservice  preference  test annotation            ddm       net                 provider    text app                   debug     nfc                 security    util appwidget             emoji     os                  server      view bluetooth             gesture   service             webkit      widget 131
3. Customization â—Ź Extending API â—Ź Boot screen â—Ź Status bar â—Ź Network â—Ź Preloaded apps â—Ź Browser bookmarks â—Ź Email provider customization â—Ź Themes 132
3.1. Extending API – System service ● frameworks/base/core/java/android/ ● app/ContextImpl.java ● content/Context.java ● os/OpersysManager.java 133
3.1.1. app/ContextImpl.java ... import android.os.IOpersysService; import android.os.OpersysManager; ...     private DownloadManager mDownloadManager = null;     private NfcManager mNfcManager = null;     private OpersysManager mOpersysManager = null; ...             return getDownloadManager();         } else if (NFC_SERVICE.equals(name)) {             return getNfcManager();         } else if (OPERSYS_SERVICE.equals(name)) {             return getOpersysManager();         } ... 134
    private OpersysManager getOpersysManager() {         synchronized (mSync) {             if (mOpersysManager == null) {                 IBinder b = ServiceManager.getService(OPERSYS_SERVICE);                 IOpersysService service = IOpersysService.Stub.asInterface(b);                 mOpersysManager = new OpersysManager(service);             }         }         return mOpersysManager;     } 135
3.1.2. content/Context.java ...     /**      * Use with {@link #getSystemService} to retrieve a      * {@link android.nfc.NfcManager} for using NFC.      *      * @see #getSystemService      */     public static final String NFC_SERVICE = "nfc";     /** The Opersys service **/     public static final String OPERSYS_SERVICE = "opersys"; ... 136
3.1.3. os/OpersysManager.java package android.os; import android.os.IOpersysService public class OpersysManager {     public void setValue(int value)     {         try {             mService.setValue(value);         } catch (RemoteException e) {         }     }     public OpersysManager(IOpersysService service)     {         mService = service;     }     IOpersysService mService; } 137
3.2. Boot screen â—Ź Create 320x480 image â—Ź Install imagemagick $ sudo apt-get install imagemagick â—Ź Convert image to .r format $ convert screen.jpg screen.r â—Ź Convert image to 565 format $ rgb2565 < screen.r > screen.565 â—Ź Write image to flash $ fastboot flash splash1 screen.565 138
3.3. Status bar ● Location: ● frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar ● Look for: ● mService.setIcon(...) ● Disable icons with: ● mService.setIconVisibility(“[ICON_NAME]", false); 139
3.4. Network ● Locations: ● Global static: – frameworks/base/core/res/res/xml/apns.xml ● Device static: – PRODUCT_COPY_FILES := vendor/acme/etc/apns-conf-us.xml:system/etc/apns-conf.xml ● Dynamic: – system/etc/apns-conf.xml ● Format: <apn carrier="T-Mobile US" mcc="310" mnc="260" apn=" wap.voicestream.com" user="none" server="*" password="none" proxy=" 216.155.165.50" port="8080" mmsc="http://216.155.174.84/servlets/mms" /> 140
3.5. Preloaded apps â—Ź See build/target/products PRODUCT_PACKAGES := bouncycastle com.android.location.provider com.android.location.provider.xml core core-junit create_test_dmtrace dalvikvm dexdeps ... 141
3.6. Browser bookmarks â—Ź See packages/apps/Browser/res/values/strings.xml <!-- Bookmarks --> <string-array name="bookmarks"> <item>Google</item> <item>http://www.google.com/</item> <item>Yahoo!</item> <item>http://www.yahoo.com/</item> <item>MSN</item> <item>http://www.msn.com/</item> <item>MySpace</item> <item>http://www.myspace.com/</item> ... 142
3.7. Email provider customization â—Ź See packages/apps/Email/res/xml/providers.xml <!-- Gmail variants --> <provider id="gmail" label="Gmail" domain="gmail.com"> <incoming uri="imap+ssl+://imap.gmail.com" username="$email"/> <outgoing uri="smtp+ssl+://smtp.gmail.com" username="$email"/> </provider> <provider id="googlemail" label="Google Mail" domain="googlemail.com"> <incoming uri="imap+ssl+://imap.googlemail.com" username="$email"/> <outgoing uri="smtp+ssl+://smtp.googlemail.com" username="$email"/> </provider> ... <!-- Common US providers --> <provider id="aim" label="AIM" domain="aim.com"> <incoming uri="imap://imap.aim.com" label="IMAP" username="$email"/> <outgoing uri="smtp://smtp.aim.com:587" username="$email"/> </provider> <provider id="aol" label="AOL" domain="aol.com"> <incoming uri="imap://imap.aol.com" label="IMAP" username="$email"/> <outgoing uri="smtp://smtp.aol.com:587" username="$email"/> </provider> ... 143
3.8. Themes â—Ź See framework/base/core/res/res/values/styles.xml 144
Custom Toolchains and Dev Kits â—Ź Rationale â—Ź SDK generation â—Ź NDK generation â—Ź Creating a cross-dev toolchain 145
1. Rationale â—Ź SDK: â—Ź Providing other internal teams or external developers access to your modified/custom Android APIs. â—Ź NDK: â—Ź Same as SDK rationale â—Ź Custom cross-dev toolchain: â—Ź To avoid having to use a binary toolchain from 3rd party. â—Ź To control the build parameters used to create the toolchain. Ex.: use uClibc instead of glibc. 146
2. SDK generation ● Building the SDK: $ . build/envsetup.sh $ lunch sdk-eng $ make sdk ● If API modified, do this before make: $ make update-api ● Location: [aosp]/out/host/linux-x86/sdk/ ● Using a custom SDK: ● Eclipse->Window->Preferences->Android->”SDK Location” ● Eclipse->Window->"Android SDK and AVD Manager"- >"Installed Packages"->"Update All..." 147
3. NDK generation â—Ź Build $ cd ndk/build/tools $ export ANDROID_NDK_ROOT=[aosp]/ndk $ ./make-release --help $ ./make-release IMPORTANT WARNING !! This script is used to generate an NDK release package from scratch for the following host platforms: linux-x86 This process is EXTREMELY LONG and may take SEVERAL HOURS on a dual-core machine. If you plan to do that often, please read docs/DEVELOPMENT.TXT that provides instructions on how to do that more easily. Are you sure you want to do that [y/N] 148
4. Creating a cross-dev toolchain ● crosstool-ng: successor to crosstool ● Available at: http://ymorin.is-a-geek.org/projects/crosstool ● Downloads, patches, builds, installs, etc. ● Comprises 23 steps ● Menuconfig-based ● Supports uClibc, glibc and eglibc ● Supports ARM, Blackfin, MIPS, PowerPC, SH, … ● Fairly well maintained 149
● Must make sure the following are installed on Ubuntu in order to use crosstool-ng: ● gawk ● texinfo ● automake ● libtool ● cvs ● libncurses5-dev ● Use “sudo apt-get install” to get those 150
â—Ź Download and extract to ${PRJROOT}/build-tools â—Ź Configure crosstool: $ cd crosstool-ng-1.10.0/ $ ./configure â—Ź Build and install crosstool-ng: $ make $ make install â—Ź Configure crosstool: $ cd ${PRJROOT}/build-tools $ ct-ng menuconfig 151
â—Ź Options: â—Ź Paths->Prefix directory: ${PREFIX}/${CT_TARGET} â—Ź Target options->architecture: powerpc â—Ź OS->Target OS: linux â—Ź C library->C library: glibc â—Ź C library->Extra flags: -U_FORTIFY_SOURCE â—Ź Debug facilities: gdb & strace â—Ź Build the toolchain: $ ct-ng build 152
Compatibility Test Suite ● Android Compatibility Program: ● Source code to Android stack ● Compatibility Definition Document (CDD) – Policy ● Compatibility Test Suite (CTS) – Mechanism ● Each Android version has own CDD & CTS ● CTS: ● Part of AOSP ● Run from host using USB over to attached device ● Based on JUnit ● Runs various test apps on target ● Relies on ADB ● Provides report to be be analyzed and/or sent back to Google 153
154
â—Ź Report: â—Ź .zip file containing XML files and screen-shots â—Ź Sent to: cts@android.com â—Ź Building the CTS: $ . build/envsetup.sh $ make cts â—Ź Launching the CTS: $ cd out/host/linux-x86/bin/ $ ./cts $ cts_host > $ cts_host > help ... 155
â—Ź Using the CTS: $ cts_host > ls --plan List of plans (8 in total): Signature RefApp VM Performance AppSecurity Android Java CTS $ ./cts start --plan CTS 156
â—Ź Areas covered: â—Ź Signature tests â—Ź Platform API tests â—Ź Dalvik VM tests â—Ź Platform Data Model â—Ź Platform Intents â—Ź Platform Permissions â—Ź Platform Resources 157
Thank you ... karim.yaghmour@opersys.com 158
Acknowledgements: ● Some figures and snippets taken from Google's Android “Dev Guide” at developer.android.com distributed under the Apache 2.0 license. 159

More Related Content

PDF
Embedded Android Workshop at Embedded Linux Conference Europe 2011
Opersys inc.
 
PDF
Leveraging Android's Linux Heritage at Android Open 2011
Opersys inc.
 
PDF
Leveraging Android's Linux Heritage at ELC-E 2011
Opersys inc.
 
PDF
Embedded Android Workshop
Opersys inc.
 
PDF
Android jumpstart at ESC Boston 2011
Opersys inc.
 
PDF
Embedded Android Workshop at AnDevConII
Opersys inc.
 
PDF
Embedded Android Workshop at ELC Europe
Opersys inc.
 
PDF
BeagleBoard Workshop ESC Boston 2011
Opersys inc.
 
Embedded Android Workshop at Embedded Linux Conference Europe 2011
Opersys inc.
 
Leveraging Android's Linux Heritage at Android Open 2011
Opersys inc.
 
Leveraging Android's Linux Heritage at ELC-E 2011
Opersys inc.
 
Embedded Android Workshop
Opersys inc.
 
Android jumpstart at ESC Boston 2011
Opersys inc.
 
Embedded Android Workshop at AnDevConII
Opersys inc.
 
Embedded Android Workshop at ELC Europe
Opersys inc.
 
BeagleBoard Workshop ESC Boston 2011
Opersys inc.
 

What's hot (20)

PDF
Leveraging Android's Linux Heritage at AnDevCon3
Opersys inc.
 
PDF
Android Jumpstart ESC SV 2012 Part I
Opersys inc.
 
PDF
Leveraging Android's Linux Heritage
Opersys inc.
 
PDF
Headless Android
Opersys inc.
 
PDF
Embedded Android Workshop / ELC 2013
Opersys inc.
 
PDF
Headless Android at AnDevCon3
Opersys inc.
 
PDF
Memory Management in Android
Opersys inc.
 
PDF
Cyborgstack
Opersys inc.
 
PDF
Embedded Android Workshop at Embedded World Conference 2013
Opersys inc.
 
PDF
Is Android the New Embedded Linux? at AnDevCon IV
Opersys inc.
 
PDF
Embedded Android Workshop part I ESC SV 2012
Opersys inc.
 
PDF
Android Hacks, Variants, Tricks and Resources ESC SV 2012
Opersys inc.
 
PDF
Android Variants, Hacks, Tricks and Resources
Opersys inc.
 
PDF
Developing Android Platform Tools
Opersys inc.
 
PDF
Android Things Internals
Opersys inc.
 
PDF
Embedded Android Workshop with Nougat
Opersys inc.
 
PDF
Embedded Android Workshop with Nougat
Opersys inc.
 
PDF
Is Android the New Embedded Linux? at AnDevCon V
Opersys inc.
 
PDF
Android Platform Debugging and Development
Opersys inc.
 
PDF
Android Internals at Linaro Connect Asia 2013
Opersys inc.
 
Leveraging Android's Linux Heritage at AnDevCon3
Opersys inc.
 
Android Jumpstart ESC SV 2012 Part I
Opersys inc.
 
Leveraging Android's Linux Heritage
Opersys inc.
 
Headless Android
Opersys inc.
 
Embedded Android Workshop / ELC 2013
Opersys inc.
 
Headless Android at AnDevCon3
Opersys inc.
 
Memory Management in Android
Opersys inc.
 
Cyborgstack
Opersys inc.
 
Embedded Android Workshop at Embedded World Conference 2013
Opersys inc.
 
Is Android the New Embedded Linux? at AnDevCon IV
Opersys inc.
 
Embedded Android Workshop part I ESC SV 2012
Opersys inc.
 
Android Hacks, Variants, Tricks and Resources ESC SV 2012
Opersys inc.
 
Android Variants, Hacks, Tricks and Resources
Opersys inc.
 
Developing Android Platform Tools
Opersys inc.
 
Android Things Internals
Opersys inc.
 
Embedded Android Workshop with Nougat
Opersys inc.
 
Embedded Android Workshop with Nougat
Opersys inc.
 
Is Android the New Embedded Linux? at AnDevCon V
Opersys inc.
 
Android Platform Debugging and Development
Opersys inc.
 
Android Internals at Linaro Connect Asia 2013
Opersys inc.
 
Ad

Similar to Embedded Android Workshop at Android Open 2011 (20)

PDF
Embedded Android Workshop at AnDevCon IV
Opersys inc.
 
PDF
Embedded Android Workshop at AnDevCon V
Opersys inc.
 
PDF
Embedded Android Workshop at ABS 2014
Opersys inc.
 
PDF
Embedded Android Workshop at AnDevCon VI
Opersys inc.
 
PDF
Embedded Android Workshop with Lollipop
Opersys inc.
 
PDF
Embedded Android Workshop at Embedded World 2014
Opersys inc.
 
PDF
Embedded Android Workshop
Opersys inc.
 
PDF
Embedded Android Workshop
Opersys inc.
 
PDF
Embedded Android Workshop
Opersys inc.
 
PDF
Embedded Android Workshop with Lollipop
Opersys inc.
 
PDF
Embedded Android Workshop with Marshmallow
Opersys inc.
 
PDF
Embedded Android Workshop with Marshmallow
Karim Yaghmour
 
PDF
Embedded Android Workshop with Marshmallow
Opersys inc.
 
PDF
Embedded Android Workshop with Marshmallow
Opersys inc.
 
PDF
Embedded Android Workshop with Oreo
Opersys inc.
 
PDF
Embedded Android Workshop with Nougat
Opersys inc.
 
PDF
Embedded Android Workshop with Pie
Opersys inc.
 
PPTX
Android presantation
UdayJethva
 
PDF
PRESENTATION ON ANDROID
Rajat Kumar
 
PDF
Android beyond the smartphone
Chris Simmonds
 
Embedded Android Workshop at AnDevCon IV
Opersys inc.
 
Embedded Android Workshop at AnDevCon V
Opersys inc.
 
Embedded Android Workshop at ABS 2014
Opersys inc.
 
Embedded Android Workshop at AnDevCon VI
Opersys inc.
 
Embedded Android Workshop with Lollipop
Opersys inc.
 
Embedded Android Workshop at Embedded World 2014
Opersys inc.
 
Embedded Android Workshop
Opersys inc.
 
Embedded Android Workshop
Opersys inc.
 
Embedded Android Workshop
Opersys inc.
 
Embedded Android Workshop with Lollipop
Opersys inc.
 
Embedded Android Workshop with Marshmallow
Opersys inc.
 
Embedded Android Workshop with Marshmallow
Karim Yaghmour
 
Embedded Android Workshop with Marshmallow
Opersys inc.
 
Embedded Android Workshop with Marshmallow
Opersys inc.
 
Embedded Android Workshop with Oreo
Opersys inc.
 
Embedded Android Workshop with Nougat
Opersys inc.
 
Embedded Android Workshop with Pie
Opersys inc.
 
Android presantation
UdayJethva
 
PRESENTATION ON ANDROID
Rajat Kumar
 
Android beyond the smartphone
Chris Simmonds
 
Ad

More from Opersys inc. (20)

PDF
Android Automotive
Opersys inc.
 
PDF
Android 10 Internals Update
Opersys inc.
 
PDF
Android Security Internals
Opersys inc.
 
PDF
Android's HIDL: Treble in the HAL
Opersys inc.
 
PDF
Android Treble: Blessing or Trouble?
Opersys inc.
 
PDF
Scheduling in Android
Opersys inc.
 
PDF
Android Things Internals
Opersys inc.
 
PDF
Android Things: Android for IoT
Opersys inc.
 
PDF
Scheduling in Android
Opersys inc.
 
PDF
Brillo / Weave Internals
Opersys inc.
 
PDF
Android Platform Debugging and Development
Opersys inc.
 
PDF
Memory Management in Android
Opersys inc.
 
PDF
Brillo / Weave Internals
Opersys inc.
 
PDF
Project Ara
Opersys inc.
 
PDF
Android Platform Debugging and Development
Opersys inc.
 
PDF
Memory Management in Android
Opersys inc.
 
PDF
Brillo/Weave Internals
Opersys inc.
 
PDF
Android Platform Debugging and Development
Opersys inc.
 
PDF
Memory Management in Android
Opersys inc.
 
PDF
Android Platform Debugging and Development
Opersys inc.
 
Android Automotive
Opersys inc.
 
Android 10 Internals Update
Opersys inc.
 
Android Security Internals
Opersys inc.
 
Android's HIDL: Treble in the HAL
Opersys inc.
 
Android Treble: Blessing or Trouble?
Opersys inc.
 
Scheduling in Android
Opersys inc.
 
Android Things Internals
Opersys inc.
 
Android Things: Android for IoT
Opersys inc.
 
Scheduling in Android
Opersys inc.
 
Brillo / Weave Internals
Opersys inc.
 
Android Platform Debugging and Development
Opersys inc.
 
Memory Management in Android
Opersys inc.
 
Brillo / Weave Internals
Opersys inc.
 
Project Ara
Opersys inc.
 
Android Platform Debugging and Development
Opersys inc.
 
Memory Management in Android
Opersys inc.
 
Brillo/Weave Internals
Opersys inc.
 
Android Platform Debugging and Development
Opersys inc.
 
Memory Management in Android
Opersys inc.
 
Android Platform Debugging and Development
Opersys inc.
 

Recently uploaded (20)

PDF
Agricultural_Statistics_at_a_Glance_2022_0.pdf
SandeepSingh286037
 
PPTX
MYSQL Presentation for SQL database connectivity
Swati270511
 
PPTX
Effective Security Operations Center (SOC) A Modern, Strategic, and Threat-In...
ReZa AdineH
 
PDF
Per capita expenditure prediction using model stacking based on satellite ima...
IAESIJAI
 
PDF
cuic standard and advanced reporting.pdf
SimoneTitaniumTomase
 
PPTX
Understanding_Digital_Forensics_Presentation.pptx
ImranKhan423233
 
PDF
TokAI - TikTok AI Agent : The First AI Application That Analyzes 10,000+ Vira...
SOFTTECHHUB
 
PPTX
PA Analog/Digital System: The Backbone of Modern Surveillance and Communication
AVTRON Technologies LLC
 
PDF
Advanced methodologies resolving dimensionality complications for autism neur...
IAESIJAI
 
PDF
How UI/UX Design Impacts User Retention in Mobile Apps.pdf
SynapseIndia
 
PDF
7 ChatGPT Prompts to Help You Define Your Ideal Customer Profile.pdf
SOFTTECHHUB
 
PDF
Encapsulation theory and applications.pdf
gurumoop
 
PPTX
KOM of Painting work and Equipment Insulation REV00 update 25-dec.pptx
muhammadmuneebnaeem7
 
PDF
Build a system with the filesystem maintained by OSTree @ COSCUP 2025
Jian-Hong Pan
 
PPTX
Big Data Technologies - Introduction.pptx
kuthubussaman1
 
PDF
Architecting across the Boundaries of two Complex Domains - Healthcare & Tech...
Peter Tan
 
PDF
Blue Purple Modern Animated Computer Science Presentation.pdf.pdf
Akar16
 
PDF
Mobile App Security Testing_ A Comprehensive Guide.pdf
flufftailshop
 
PDF
CIFDAQ's Market Insight: SEC Turns Pro Crypto
CIFDAQ
 
PDF
Machine learning based COVID-19 study performance prediction
IAESIJAI
 
Agricultural_Statistics_at_a_Glance_2022_0.pdf
SandeepSingh286037
 
MYSQL Presentation for SQL database connectivity
Swati270511
 
Effective Security Operations Center (SOC) A Modern, Strategic, and Threat-In...
ReZa AdineH
 
Per capita expenditure prediction using model stacking based on satellite ima...
IAESIJAI
 
cuic standard and advanced reporting.pdf
SimoneTitaniumTomase
 
Understanding_Digital_Forensics_Presentation.pptx
ImranKhan423233
 
TokAI - TikTok AI Agent : The First AI Application That Analyzes 10,000+ Vira...
SOFTTECHHUB
 
PA Analog/Digital System: The Backbone of Modern Surveillance and Communication
AVTRON Technologies LLC
 
Advanced methodologies resolving dimensionality complications for autism neur...
IAESIJAI
 
How UI/UX Design Impacts User Retention in Mobile Apps.pdf
SynapseIndia
 
7 ChatGPT Prompts to Help You Define Your Ideal Customer Profile.pdf
SOFTTECHHUB
 
Encapsulation theory and applications.pdf
gurumoop
 
KOM of Painting work and Equipment Insulation REV00 update 25-dec.pptx
muhammadmuneebnaeem7
 
Build a system with the filesystem maintained by OSTree @ COSCUP 2025
Jian-Hong Pan
 
Big Data Technologies - Introduction.pptx
kuthubussaman1
 
Architecting across the Boundaries of two Complex Domains - Healthcare & Tech...
Peter Tan
 
Blue Purple Modern Animated Computer Science Presentation.pdf.pdf
Akar16
 
Mobile App Security Testing_ A Comprehensive Guide.pdf
flufftailshop
 
CIFDAQ's Market Insight: SEC Turns Pro Crypto
CIFDAQ
 
Machine learning based COVID-19 study performance prediction
IAESIJAI
 

Embedded Android Workshop at Android Open 2011

  • 1. Embedded Android Workshop 1
  • 2. About â—Ź Author of: â—Ź Introduced Linux Trace Toolkit in 1999 â—Ź Originated Adeos and relayfs (kernel/relay.c) 2
  • 3. About Android â—Ź Huge â—Ź Fast moving â—Ź Stealthy 3
  • 4. Introduction to Embedded Android â—Ź Basics â—Ź History â—Ź Ecosystem â—Ź Legal framework â—Ź Platform and hardware requirements â—Ź Development tools 4
  • 5. 1. Basics â—Ź Features â—Ź UX Concepts â—Ź App Concepts 5
  • 6. 1.1. Features â—Ź Application framework enabling reuse and replacement of components â—Ź Dalvik virtual machine optimized for mobile devices â—Ź Integrated browser based on the open source WebKit engine â—Ź Optimized graphics powered by a custom 2D graphics library; 3D graphics based on the OpenGL ES 1.0 specification (hardware acceleration optional) â—Ź SQLite for structured data storage â—Ź Media support for common audio, video, and still image formats (MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, GIF) â—Ź GSM Telephony (hardware dependent) â—Ź Bluetooth, EDGE, 3G, and WiFi (hardware dependent) â—Ź Camera, GPS, compass, and accelerometer (hardware dependent) â—Ź Rich development environment including a device emulator, tools for debugging, memory and performance profiling, and a plugin for the Eclipse IDE 6
  • 7. 1.2. UX Concepts â—Ź Browser-like â—Ź iPhone-ish â—Ź No user-concept of “task” â—Ź Main keys: â—Ź HOME â—Ź SEARCH â—Ź BACK â—Ź MENU â—Ź App-model allows users to safely install/test almost anything 7
  • 8. “Click” Activity #1 Activity “Back” “Click” Activity #2 Activity #1 “Click” “Home” “Back” Activity #3 Activity #2 Activity #1 Home Menu Back 8
  • 9. 1.3. App Concepts â—Ź No single entry point (No main() !?!?) â—Ź Unlike Windows or Unix API/semantics in many ways â—Ź Processes and apps will be killed at random: developer must code accordingly â—Ź UI disintermediated from app “brains” â—Ź Apps are isolated, very â—Ź Behavior predicated on low-memory conditions 9
  • 10. 2. History â—Ź 2002: â—Ź Sergey Brin and Larry Page started using Sidekick smartphone â—Ź Sidekick one of 1st smartphones integrating web, IM, mail, etc. â—Ź Sidekick was made by Danger inc., co-founded by Andy Rubin (CEO) â—Ź Brin/Page met Rubin at Stanford talk he gave on Sidekick’s development â—Ź Google was default search engine on Sidekick â—Ź 2004: â—Ź Despite cult following, Sidekick wasn’t making $ â—Ź Danger inc. board decided to replace Rubin â—Ź Rubin left. Got seed $. Started Android inc. Started looking for VCs. â—Ź Goal: Open mobile hand-set platform â—Ź 2005 - July: â—Ź Got bought by Google for undisclosed sum :) â—Ź 2007 - November: â—Ź Open Handset Alliance announced along with Android 10
  • 11. â—Ź 2008 - Sept.: Android 1.0 is released â—Ź 2009 - Feb.: Android 1.1 â—Ź 2009 - Apr.: Android 1.5 / Cupcake â—Ź 2009 - Sept.: Android 1.6 / Donut â—Ź 2009 - Oct.: Android 2.0/2.1 / Eclair â—Ź 2010 - May: Android 2.2 / Froyo â—Ź 2010 - Dec.: Android 2.3 / Gingerbread â—Ź 2011 - Jan : Android 3.0 / Honeycomb – Tablet-optimized â—Ź 2011 – May: Android 3.1 – USB host support â—Ź 2011 – Dec: Android 4.0 / Ice-Cream Sandwich – merge Gingerbread and Honeycomb 11
  • 12. 3. Ecosystem â—Ź 350k phone activations per day â—Ź 150k apps (vs. 350k for Apple's app store) â—Ź 1/3 of new smartphones sold in US â—Ź ... 12
  • 13. 3.1. Who's playing? â—Ź Leading IP: â—Ź Google â—Ź Semiconductor manufacturers: â—Ź ARM, Intel, Freescale, TI, Qualcomm, NVIDIA, ... â—Ź Handset manufacturers: â—Ź Motorola, Samsung, HTC, LG, Sony-Ericsson, ... â—Ź Tablet manufacturers: â—Ź Motorola, Samsung, Archos, DELL, ASUS, ... â—Ź Special-purpose devices: â—Ź Nook, Joint Battle Command-Platform, ... â—Ź App stores: â—Ź Android Market, Amazon App Store, V CAST Apps, B&N NOOK Apps, ... 13
  • 14. 3.2. Open Handset Alliance â—Ź “... a group of 80 technology and mobile companies who have come together to accelerate innovation in mobile and offer consumers a richer, less expensive, and better mobile experience. Together we have developed Android™, the first complete, open, and free mobile platform.” â—Ź Unclear what OHA does or what benefits, if any, members derive â—Ź Not an organization with board members, staff, etc. ... just an “Alliance” â—Ź Google's Android team are the lead on all bleeding edge dev, all else tag along â—Ź OHA is largely inactive / absent â—Ź Comprised of: â—Ź Mobile Operators: Sprint, T-Mobile, Vodafone, NTT Docomo, ... â—Ź Handset Manufacturers: HTC, Motorola, LG, Samsung, Sony Ericsson, ... â—Ź Semiconductor Companies: ARM, Freescale, Intel, NVIDIA, Qualcomm, TI, ... â—Ź Software Companies: Google, ... â—Ź Commercialization Companies: ... 14
  • 15. 4. Legal Framework â—Ź Code access â—Ź Code licenses â—Ź Branding use â—Ź Google's own Android Apps â—Ź Alternative App stores â—Ź Oracle v. Google 15
  • 16. 4.1. Code Access â—Ź Parts: â—Ź Kernel â—Ź Android Open Source Project (AOSP) â—Ź Kernel: â—Ź Should have access to latest shipped version => GPL requirement â—Ź Google-maintained forks at android.git.kernel.org â—Ź AOSP: â—Ź Usually Code-drops every 6 months â—Ź Official AOSP branches at android.git.kernel.org â—Ź Managed by “repo” tool, an overlay to “git” â—Ź Honeycomb (3.0) code requires talking to Google â—Ź ... which hasn't precluded moders from lifting binaries off the SDK and putting Honeycomb on all sorts of devices, including B&N's Nook ... 16
  • 17. 4.2. Code Licenses â—Ź Kernel: â—Ź GNU General Public License (a.k.a. GPL) â—Ź AOSP: â—Ź Mostly Apache License 2.0 (a.k.a. ASL) â—Ź Having GPL-free user-space was a design goal â—Ź A few GPL and LGPL parts: mainly BlueZ and DBUS â—Ź Some key components in BSD: Bionic and Toolbox â—Ź “external/” directory contains a mixed bag of licenses, incl. lots of GPL â—Ź May be desirable to add GPL/LGPL components: â—Ź BusyBox â—Ź uClibc / eglibc / glibc 17
  • 18. 4.3. Branding Use â—Ź Android Robot: â—Ź Very much like the Linux penguin â—Ź Android Logo (A-N-D-R-O-I-D w/ typeface): â—Ź Cannot be used â—Ź Android Custom Typeface: â—Ź Cannot be used â—Ź Android in Official Names: â—Ź As descriptor only: “for Android” â—Ź Most other uses require approval â—Ź Android in Messaging: â—Ź Allowed if followed by a generic: “Android Application” â—Ź Compliance through CDD/CTS involved in “approval” 18
  • 19. 4.4. Google's own Android Apps â—Ź The non-AOSP apps: â—Ź Android Market â—Ź YouTube â—Ź Maps and Navigation â—Ź Gmail â—Ź Voice â—Ź SkyMap â—Ź ... â—Ź Require: â—Ź CTS/CDD Compliance â—Ź Signed agreement w/ Google â—Ź Inquiries: android-partnerships@google.com 19
  • 20. 4.5. Alternative “App Stores” â—Ź A couple of stores are already public: â—Ź Android Market â—Ź Amazon App Store â—Ź V CAST Apps â—Ź B&N NOOK Apps â—Ź ... â—Ź Nothing precluding you from having your own 20
  • 21. 4.6. Oracle v. Google â—Ź Filed August 2010 â—Ź Patent infringement: â—Ź 6,125,447; 6,192,476; 5,966,702; 7,426,720; RE38,104; 6,910,205; and 6,061,520 â—Ź Copyright infringement: â—Ź Android does not use any Oracle Java libraries or JVM in the final product. â—Ź Android relies on Apache Harmony and Dalvik instead. â—Ź In October 2010, IBM left Apache Harmony to join work on Oracle's OpenJDK, leaving the project practically orphaned. â—Ź In May 2011, judge orders claims cut from 132 to 3 and prior art references cut from hundreds to 8 21
  • 22. 5. Platform and Hardware requirements â—Ź In principle: â—Ź Android runs on top of Linux â—Ź Therefore: if it runs Linux, it can run Android â—Ź Known to have been made to work on: â—Ź ARM â—Ź x86 â—Ź MIPS â—Ź SuperH â—Ź Put in all sort of devices: â—Ź Washers, micro-wave ovens, car systems, etc. 22
  • 23. 5.1. Compliance Definition Document â—Ź Software: MUST conform to AOSP â—Ź Application Packaging Compatibility: support “.apk” files â—Ź Multimedia Compatibility: decoders, encoders, recording, ... â—Ź Developer Tool Compatibility: adb, ddms, Monkey â—Ź Hardware compatibility: â—Ź Display and Graphics â—Ź Input Devices â—Ź Data Connectivity â—Ź Cameras â—Ź Memory and Storage â—Ź USB â—Ź Performance Compatibility â—Ź Security Model Compatibility â—Ź Software Compatibility Testing â—Ź Updatable Software: MUST include mechanism to update 23
  • 25. 6. Development tools â—Ź Requirements â—Ź App dev tools and resources â—Ź App debugging 25
  • 26. 6.1. Requirements â—Ź App development and debugging: â—Ź Windows / Mac / Linux workstation â—Ź JDK â—Ź Eclipse w/ ADT plugin â—Ź Highly recommended: real device(S) â—Ź Platform development: â—Ź GNU cross-dev toolchain â—Ź JTAG debugger â—Ź ... more on this later 26
  • 27. 6.2. App dev tools and resources â—Ź SDK: â—Ź android – manage AVDs and SDK components â—Ź apkbuilder – creating .apk packages â—Ź dx – converting .jar to .dex â—Ź adb – debug bridge â—Ź ... â—Ź Emulator – QEMU-based ARM emulator â—Ź Use KVM for x86 instead â—Ź NDK: GNU toolchain for native binaries â—Ź Documentation: developer.android.com 27
  • 28. 28
  • 29. 29
  • 30. 6.3. App debugging â—Ź adb â—Ź ddms â—Ź monkeyrunner â—Ź traceview â—Ź logcat â—Ź Eclipse integration (ADT plugin) 30
  • 31. Concepts and Internals 1. Android Concepts 9. Dalvik 2. Framework Intro 10.JNI 3. Native Development 11.System Server 4. Overall Architecture 12.Calling on Services 5. System startup 13.Activity Manager 6. Linux Kernel 14.Binder 7. Hardware Support 15.Stock AOSP Apps 8. Native User-Space 31
  • 32. 1. Android Concepts â—Ź Components â—Ź Intents â—Ź Component lifecycle â—Ź Manifest file â—Ź Processes and threads â—Ź Remote procedure calls 32
  • 33. 1.1. Components â—Ź 1 App = N Components â—Ź Apps can use components of other applications â—Ź App processes are automagically started whenever any part is needed â—Ź Ergo: N entry points, !1, and !main() â—Ź Components: â—Ź Activities â—Ź Services â—Ź Broadcast Receivers â—Ź Content Providers 33
  • 34. 1.2. Intents â—Ź Intent = asynchronous message w/ or w/o designated target â—Ź Like a polymorphic Unix signal, but w/o required target â—Ź Intents “payload” held in Intent Object â—Ź Intent Filters specified in Manifest file 34
  • 35. 1.3. Component lifecycle â—Ź System automagically starts/stops/kills processes: â—Ź Entire system behaviour predicated on low memory â—Ź System triggers Lifecycle callbacks when relevant â—Ź Ergo: Must manage Component Lifecycle â—Ź Some Components are more complex to manage than others 35
  • 36. 36
  • 37. 1.4. Manifest file â—Ź Informs system about app’s components â—Ź XML format â—Ź Always called AndroidManifest.xml â—Ź Activity = <activity> ... static â—Ź Service = <service> ... static â—Ź Broadcast Receiver: â—Ź Static = <receiver> â—Ź Dynamic = Context.registerReceiver() â—Ź Content Provider = <provider> ... static 37
  • 38. 1.5. Processes and threads â—Ź Processes â—Ź Default: all callbacks to any app Component are issued to the main process thread â—Ź <activity>—<service>—<recipient>—<provider> have process attribute to override default â—Ź Do NOT perform blocking/long operations in main process thread: – Spawn threads instead â—Ź Process termination/restart is at system’s discretion â—Ź Therefore: – Must manage Component Lifecycle â—Ź Threads: â—Ź Create using the regular Java Thread Object â—Ź Android API provides thread helper classes: – Looper: for running a message loop with a thread – Handler: for processing messages – HandlerThread: for setting up a thread with a message loop 38
  • 39. 1.6. Remote procedure calls â—Ź Android RPCs = Binder mechanism â—Ź No Sys V IPC due to in-kernel resource leakage â—Ź Binder is a low-level functionality, not used as-is â—Ź Instead: must define interface using Interface Definition Language (IDL) â—Ź IDL fed to aidl Tool to generate Java interface definitions 39
  • 40. 2. Framework Introduction â—Ź UI â—Ź Data storage â—Ź Security/Permissions â—Ź ... and much more ... : â—Ź Graphics â—Ź Audio and Video â—Ź Location and Maps â—Ź Bluetooth â—Ź NFC 40
  • 41. 2.1. UI â—Ź Everything based on hierarchy of Views and ViewGroups (layouts) â—Ź Declared in XML or dynamically through Java â—Ź UI components: â—Ź Widgets â—Ź Event handlers â—Ź Menus â—Ź Dialogs â—Ź Notifications â—Ź ... 41
  • 42. 2.2. Data storage â—Ź Shared preferences â—Ź Private primitive key-pair values â—Ź Internal storage â—Ź Private data on device memory â—Ź External storage â—Ź Public data on shared external device (SD) â—Ź SQLite DB â—Ź Private DB â—Ź Network connection â—Ź Web-based storage (REST) 42
  • 43. 2.3. Security/Permissions â—Ź Most security enforced at process level: UID, GID â—Ź Permissions enforce restrictions on: â—Ź Per-process operations â—Ź Per-URI access â—Ź Applications are sandboxed â—Ź Specific permissions required to “exit” sandbox â—Ź Decision to grant access based on: â—Ź Certificates â—Ź User prompts â—Ź All permissions must be declared statically 43
  • 44. 3. Native development â—Ź What it can and cannot do â—Ź Getting and installing the NDK â—Ź Using the NDK â—Ź Implementing fully native apps 44
  • 45. 3.1. What it can and cannot do â—Ź Useful for: â—Ź Porting existing body of code to Android â—Ź Developing optimized native apps, especially for gaming â—Ź Provides: â—Ź Tools and build files to generate native code libraries from C/C++ â—Ź Way to embed native libs into .apk â—Ź Set of stable (forward-compatible) native libs â—Ź Documentation, samples and tutorials â—Ź Enables: â—Ź Calling native code from Java using JNI â—Ź Implementing fully native apps (since 2.3) â—Ź Doesn't allow you to: â—Ź Compile traditional Linux/Unix apps as-is 45
  • 46. 3.2. Getting and installing the NDK â—Ź What’s in the NDK? â—Ź Development tools â—Ź Stable native APIs system headers â—Ź Documentation - IMPORTANT â—Ź Samples â—Ź Getting the NDK â—Ź http://developer.android.com/sdk/ndk/index.html â—Ź Prerequisites â—Ź Windows, Mac or Linux â—Ź Complete SDK â—Ź make (GNU’s) and awk â—Ź For Windows, Cygwin 1.7 or higher â—Ź NDK set up: â—Ź Make sure prerequisites are installed â—Ź Download and install NDK 46
  • 47. 3.3. Using the NDK 1.Place native code under <project>/jni/... 2.Create <project>/jni/Android.mk to describe native code to NDK 3.Optional: create <project>/jni/Application.mk for describing which natives sources are required by app 4.Build native code: • cd <project> • <ndk>/ndk-build 5.Compile app with SDK. Native code will be shared lib in .apk file. 47
  • 48. 3.4. Implementing fully native apps â—Ź Android 2.3 and up â—Ź Native lifecycle management â—Ź Still runs within context of dedicated Dalvik VM â—Ź Can use JNI to call on Java functions â—Ź Limited API: â—Ź Activity lifecycle management â—Ź Input events and sensors â—Ź Window management â—Ź Direct access to assets â—Ź Make sure your activity is called: “android.app.NativeActivity” 48
  • 51. 5. System Startup â—Ź Bootloader â—Ź Kernel â—Ź Init â—Ź Zygote â—Ź System Server â—Ź Activity Manager â—Ź Launcher (Home) 51
  • 52. 5.1. Bootloader â—Ź aosp/bootable/bootloader â—Ź Custom bootloader for Android â—Ź USB-based â—Ź Implements the “fastboot” protocol â—Ź Controlled via “fastboot” cli tool on host â—Ź aosp/bootable/recovery â—Ź UI-based recovery boot program â—Ź Accessed through magic key sequence at boot â—Ź Usually manufacturer specific variant 52
  • 53. â—Ź Flash layout: 0x000003860000­0x000003900000 : "misc" 0x000003900000­0x000003e00000 : "recovery" 0x000003e00000­0x000004300000 : "boot" Kernel 0x000004300000­0x00000c300000 : "system" /system 0x00000c300000­0x0000183c0000 : "userdata" /data 0x0000183c0000­0x00001dd20000 : "cache" /cache 0x00001dd20000­0x00001df20000 : "kpanic" 0x00001df20000­0x00001df60000 : "dinfo" 0x00001df60000­0x00001dfc0000 : "setupdata" 0x00001dfc0000­0x00001e040000 : "splash1" 0x000000300000­0x000001680000 : "modem" From Acer Liquid-E 53
  • 54. 5.2. Kernel â—Ź Early startup code is very hardware dependent â—Ź Initializes environment for the running of C code â—Ź Jumps to the architecture-independent start_kernel() function. â—Ź Initializes high-level kernel subsystems â—Ź Mounts root filesystem â—Ź Starts the init process 54
  • 55. 5.3. Android Init â—Ź Open, parses, and runs /init.rc: â—Ź Create mountpoints and mount filesystems â—Ź Set up filesystem permissions â—Ź Set OOM adjustments properties â—Ź Start daemons: – adbd – servicemanager (binder context manager) – vold – netd – rild – app_process -Xzygote (Zygote) – mediaserver – ... 55
  • 56. 5.4. Zygote, etc. â—Ź Init: â—Ź app_process -Xzygote (Zygote) â—Ź frameworks/base/cmds/app_process/app_main.cpp: â—Ź runtime.start(“com.android.internal.os.Zygote”, ... â—Ź frameworks/base/core/jni/AndroidRuntime.cpp: â—Ź startVM() â—Ź Call Zygote's main() â—Ź frameworks/base/core/java/com/android/internal/os/Zy goteInit.java: â—Ź ... 56
  • 57. â—Ź preloadClasses() â—Ź startSystemServer() â—Ź ... magic ... â—Ź Call SystemServer's run() â—Ź frameworks/base/services/java/com/android/server /SystemServer.java: â—Ź Start all system services/managers â—Ź Start ActivityManager: – Send Intent.CATEGORY_HOME – Launcher2 kicks in 57
  • 59. 6.1. Androidisms â—Ź Wakelocks â—Ź lowmem handler â—Ź Binder â—Ź ashmem – Anonymous Shared Memory â—Ź RAM console â—Ź Logger â—Ź ... 59
  • 60. 7. Hardware support Bluetooth BlueZ through D-BUS IPC (to avoid GPL contamination it seems) GPS Manufacturer-provided libgps.so Wifi wpa_supplicant Display Std framebuffer driver (/dev/fb0) Keymaps and Keyboards Std input event (/dev/event0) Lights Manufacturer-provided liblights.so Backlight Keyboard Buttons Battery Notifications Attention Audio Manufacturer-provided libaudio.so (could use ALSA underneath ... at least as illustrated in their porting guide) Camera Manufacturer-provided libcamera.so (could use V4L2 kernel driver underneath ... as illustrated in porting guide) Power Management “Wakelocks” kernel patch Sensors Manufacturer-provided libsensors.so Accelerometer Magnetic Field Orientation Gyroscope Light Pressure Temperature Proximity Radio Layer Interface Manufacturer-provided libril-<companyname>-<RIL version>.so 60
  • 61. 8. Native User-Space â—Ź Mainly â—Ź /data => User data â—Ź /system => System components â—Ź Also found: â—Ź /dev â—Ź /proc â—Ź /sys â—Ź /sbin â—Ź /mnt â—Ź /cache â—Ź Etc. 61
  • 62. â—Ź Libs: Bionic, SQLite, SSL, OpenGL|ES, Non-Posix: limited Pthreads support, no SysV IPC â—Ź Toolbox â—Ź Daemons: servicemanager, vold, rild, netd, adbd, ... 62
  • 63. 9. Dalvik â—Ź Sun-Java = Java language + JVM + JDK libs â—Ź Android Java = Java language + Dalvik + Apache Harmony â—Ź Target: â—Ź Slow CPU â—Ź Relatively low RAM â—Ź OS without swap space â—Ź Battery powered â—Ź Now has JIT 63
  • 64. 9.1. Dalvik's .dex files â—Ź JVM munches on “.class” files â—Ź Dalvik munches on “.dex” files â—Ź .dex file = .class files post-processed by “dx” utility â—Ź Uncompressed .dex = 0.5 * Uncompressed .jar 64
  • 65. 10. JNI – Java Native Interface â—Ź Call gate for other languages, such as C, C++ â—Ź Equivalent to .NET's pinvoke â—Ź Usage: include and call native code from App â—Ź Tools = NDK ... samples included â—Ź Check out “JNI Programmer's Guide and Specification” - freely available PDF 65
  • 66. 11. System Server Entropy Service Device Policy Audio Service Power Manager Status Bar Headset Observer Activity Manager Clipboard Service Dock Observer Telephone Registry Input Method Service UI Mode Manager Service Package Manager NetStat Service Backup Service Account Manager NetworkManagement Service AppWidget Service Content Manager Connectivity Service Recognition Service System Content Providers Throttle Service Status Bar Icons Battery Service Accessibility Manager DiskStats Service Lights Service Mount Service ADB Settings Observer Vibrator Service Notification Manager Alarm Manager Device Storage Monitor Init Watchdog Location Manager Sensor Service Search Service Window Manager DropBox Service Bluetooth Service Wallpaper Service 66
  • 67. 12. Calling on System Services â—Ź Use getSystemService â—Ź Ex: NotificationManager Object reference: String ns = Context.NOTIFICATION_SERVICE; NotificationManager mNotificationManager = (NotificationManager) getSystemService(ns); â—Ź Prepare your content â—Ź Call on the object: mNotificationManager.notify(HELLO_ID, notification); 67
  • 68. 13. ActivityManager â—Ź Start new Activities, Services â—Ź Fetch Content Providers â—Ź Intent broadcasting â—Ź OOM adj. maintenance â—Ź Application Not Responding â—Ź Permissions â—Ź Task management â—Ź Lifecycle management 68
  • 69. â—Ź Ex. starting new app from Launcher: â—Ź onClick(Launcher) â—Ź startActivity(Activity.java) â—Ź <Binder> â—Ź ActivityManagerService â—Ź startViaZygote(Process.java) â—Ź <Socket> â—Ź Zygote 69
  • 70. 14. Binder â—Ź CORBA/COM-like IPC â—Ź Data sent through “parcels” in “transactions” â—Ź Kernel-supported mechanism â—Ź /dev/binder â—Ź Check /proc/binder/* â—Ź android.* API connected to System Server through binder. 70
  • 71. 71
  • 72. 15. Stock AOSP Apps /packages/apps /packages/providers /packages/inputmethods AccountsAndSettings Launcher2 ApplicationProvider LatinIME AlarmClock Mms CalendarProvider OpenWnn Bluetooth Music ContactsProvider PinyinIME Browser PackageInstaller DownloadProvider Calculator Protips DrmProvider Calendar Provision GoogleContactsProvider Camera QuickSearchBox MediaProvider CertInstaller Settings TelephonyProvider Contacts SoundRecorder UserDictionaryProvider DeskClock SpeechRecorder Email Stk Gallery VoiceDialer HTMLViewer 72
  • 73. Android Open Source Project â—Ź Tools and location â—Ź Content â—Ź Building â—Ź Build system â—Ź Adding new applications â—Ź Images â—Ź Using adb 73
  • 74. 1. Tools and location â—Ź Location: â—Ź http://android.git.kernel.org/ â—Ź Get “repo”: $ curl http://android.git.kernel.org/repo > ~/bin/repo $ chmod a+x ~/bin/repo â—Ź Fetch the AOSP: â—Ź Make sure you fetch a tagged release â—Ź Gingerbread: $ repo init -u git://android.git.kernel.org/platform/manifest.git -b gingerbread $ repo sync 74
  • 75. 2. Content bionic C library replacement bootable Reference bootloader build Build system cts Compatibility Test Suite dalvik Dalvik VM development Development tools device Device-specific files and components external Copy of external projects used by AOSP frameworks System services, android.*, Android-related cmds, etc. hardware Hardware support libs libcore Apache Harmony ndk The NDK packages Stock Android apps, providers, etc. prebuilt Prebuilt binaries sdk The SDK system pieces of the world that are the core of the embedded linux platform at the heart of Android. 75
  • 76. 3. Building â—Ź Requires 64-bit Ubuntu 10.04 â—Ź Packages required: $ sudo⌴ apt-get⌴ install⌴ build-essential⌴ libc6-dev⌴ > ia32-libs⌴ lib32z1⌴ bison⌴ flex⌴ gperf⌴ git-core⌴ > g++⌴ libc6-dev-i386⌴ libz-dev⌴ libx11-dev⌴ > libstdc++6⌴ lib32ncurses5⌴ lib32ncurses5-dev⌴ > g++-multilib â—Ź Possibly fix a few symbolic links: $ sudo ln⌴ -s⌴ /usr/lib32/libstdc++.so.6⌴ /usr/lib32/libstdc++.so $ sudo ln⌴ -s⌴ /usr/lib32/libz.so.1⌴ /usr/lib32/libz.so 76
  • 77. â—Ź Set up build environment: $ .⌴ build/envsetup.sh $ lunch â—Ź Launch build and go watch tonight's hockey game: $ make -j2 â—Ź ... though you should check your screen at breaks ... â—Ź Just launch emulator when it's done: $ emulator & 77
  • 78. â—Ź Some nice tricks: â—Ź See build/envsetup.sh for commands â—Ź Do use ccache (compiler cache): $ export USE_CCACHE=1 â—Ź Use “lunch” from AOSP root to set env vars – You'll need that if you come back later and want to relaunch emulator from AOSP root: $ . build/envsetup.sh $ lunch $ emulator 78
  • 79. 4. Build system â—Ź Non-Recursive â—Ź “Modules” build predicated on Android.mk 79
  • 80. 5. Adding new applications â—Ź Add application in [aosp]/packages/apps â—Ź Can use Eclipse to create initial version â—Ź Copy Eclipse project to packages/apps â—Ź Add an appropriate Android.mk file to project â—Ź Add project to PRODUCT_PACKAGES in [aosp]/build/target/product/core.mk 80
  • 81. 6. Images â—Ź All output and build in [aosp]/out/ â—Ź Images at [aosp]/out/target/product/generic/: â—Ź ramdisk.img â—Ź system.img â—Ź userdata-qemu.img â—Ź Kernel is in: â—Ź prebuilt/android-arm/kernel/kernel-qemu â—Ź Emulator overrides: â—Ź -kernel â—Ź -initrd 81
  • 82. 7. Using adb â—Ź Can use to control/interface w/ running AOSP, including emulator. â—Ź Shell: Host $ adb shell Target # â—Ź Dumping the log: $ adb logcat â—Ź Copying files to/from target: $ adb push foo /data/local $ adb pull /proc/config.gz 82
  • 83. Kernel Selection â—Ź Google: â—Ź http://android.git.kernel.org/ â—Ź Vanilla: â—Ź http://www.kernel.org â—Ź Either way ... you're screwed: â—Ź Android kernel is a fork â—Ź No resolution in sight â—Ź Cannot use vanilla kernel as-is ... androidisms 83
  • 84. Native Android User-Space â—Ź Filesystem layout â—Ź Bionic â—Ź Toolbox â—Ź Init â—Ź Native daemons â—Ź Power tools 84
  • 85. 1. Filesystem layout â—Ź /acct => Control Group mount point (Documentation/cgroups.txt) â—Ź /cache => cache flash partition â—Ź /d => Symlink to /sys/kernel/debug â—Ź /data => Android's “/data” filesystem â—Ź /dev => Device nodes â—Ź /etc => Symlink to /system/etc â—Ź /mnt => Temporary mount point â—Ź /proc => procfs â—Ź /root => unused â—Ź /sbin => eventd and adbd â—Ź /sdcard => SD card mountpoint â—Ź /sys => sysfs â—Ź /system => Android's “/system” filesystem â—Ź /vendor => Symlink to /system/vendor 85
  • 86. 1.1. /system â—Ź /app => Stock apps installed â—Ź /bin => Native binaries and daemons â—Ź /etc => Configuration files â—Ź /fonts => TTFs â—Ź /framework => Android framework .jar files â—Ź /lib => Native libraries â—Ź /usr => Miniature “/usr” â—Ź /xbin => Optional/Extra binaries 86
  • 87. 1.2. /data â—Ź /anr => ANR traces â—Ź /app => App install location â—Ź /app-private => Protected apps â—Ź /backup => For Backup Manager â—Ź /dalvik-cache => Dalvik DEX cache â—Ź /data => App data â—Ź /dontpanic => Last panic output (console + threads) for “dumpstate” â—Ź /local => Shell-writable space â—Ź /misc => Misc. data (wifi, vpn, bluetooth, ...) â—Ź /property => Persistent system properties (country, lang., ...) â—Ź /secure => Secure Android data available â—Ź /system => System data 87
  • 88. 2. Bionic â—Ź In aosp: â—Ź /bionic â—Ź In filesystem: â—Ź /system/lib â—Ź Provides: â—Ź libc â—Ź libm â—Ź libdl â—Ź libstd++ â—Ź libthread_db â—Ź linker 88
  • 89. 3. Toolbox â—Ź In aosp: â—Ź /system/core/toolbox â—Ź In filesystem: â—Ź /system/bin/toolbox â—Ź Provides alarm date getevent insmod ls mv powerd renice schedtop smd top dd getprop ioctl lsmod nandread printenv rm sendevent start umount cat hd ionice lsof netstat ps rmdir setconsole stop uptime chmod df id kill mkdir newfs_msdos r rmmod setkey sync vmstat chown dmesg ifconfig ln readtty rotatefb setprop syren watchprops cmp exists iftop log mount notify reboot route sleep wipe 89
  • 90. 4. Init â—Ź In aosp: â—Ź /system/core/init â—Ź In filesystem: â—Ź /init â—Ź Relies on: â—Ź /init.rc â—Ź /init.[board].rc â—Ź /ueventd.rc â—Ź /ueventd.[board].rc â—Ź /system/etc/init.[board].sh 90
  • 91. 5. Native daemons â—Ź servicemanager â—Ź vold â—Ź rild â—Ź netd â—Ź adbd â—Ź installd 91
  • 92. 5.1. servicemanager â—Ź In aosp: â—Ź /frameworks/base/cmds/servicemanager/ â—Ź In filesystem: â—Ź /system/bin/ â—Ź Provides: â—Ź Context management for binder â—Ź Service index for entire system 92
  • 93. 5.2. vold â—Ź In aosp: â—Ź /system/vold/ â—Ź In filesystem: â—Ź /system/bin/ â—Ź Provides: â—Ź Volume mounter â—Ź Auto-mount â—Ź Auto-format mounted devices 93
  • 94. 5.3. rild â—Ź In aosp: â—Ź /hardware/ril/mock-ril/ â—Ź In filesystem: â—Ź /system/bin/ â—Ź Provides: â—Ź “Radio Interface Layer” to phone hardware 94
  • 95. 5.4. netd â—Ź In aosp: â—Ź /system/netd/ â—Ź In filesystem: â—Ź /system/bin/ â—Ź Provides: â—Ź Management of aspects of networking â—Ź Interfaces with Network Management service 95
  • 96. 5.5. adbd â—Ź In aosp: â—Ź /system/core/adb/ â—Ź In filesystem: â—Ź /sbin â—Ź Provides: â—Ź Interfaces with host “adb” command â—Ź Remote debugging capabilities â—Ź Access to shell â—Ź Package install/uninstall â—Ź ... see “adb help” on host for full detail 96
  • 97. 5.6. installd â—Ź In aosp: â—Ź /frameworks/base/cmds/installd â—Ź In filesystem: â—Ź /system/bin/ â—Ź Provides: â—Ź Package install/uninstall â—Ź Sanity checks and verifications â—Ź Interfaces with Package Manager service 97
  • 98. 6. Power tools â—Ź dumpstate â—Ź dumpsys â—Ź service â—Ź logcat 98
  • 99. System Server â—Ź Services run by System Server â—Ź Observing the System Server â—Ź Calling on system services â—Ź Inside a few system services â—Ź Creating your own system service 99
  • 100. 1. Services run by the System Server Entropy Service Device Policy Audio Service Power Manager Status Bar Headset Observer Activity Manager Clipboard Service Dock Observer Telephone Registry Input Method Service UI Mode Manager Service Package Manager NetStat Service Backup Service Account Manager NetworkManagement Service AppWidget Service Content Manager Connectivity Service Recognition Service System Content Providers Throttle Service Status Bar Icons Battery Service Accessibility Manager DiskStats Service Lights Service Mount Service ADB Settings Observer Vibrator Service Notification Manager Alarm Manager Device Storage Monitor Init Watchdog Location Manager Sensor Service Search Service Window Manager DropBox Service Bluetooth Service Wallpaper Service 100
  • 101. 1.1. Some stats â—Ź frameworks/base/services/java/com/android/ser ver: â—Ź 3.5 M â—Ź ~100 files â—Ź 85 kloc â—Ź Activity manager: â—Ź 920K â—Ź 30+ files â—Ź 20 kloc 101
  • 102. 2. Observing the System Server â—Ź Logcat â—Ź dumpsys 102
  • 103. 2.1. logcat â—Ź Find the System Server's PID $ adb shell ps | grep system_server system 63 32 120160 35408 ffffffff afd0c738 S system_server â—Ź Look for its output: $ adb logcat | grep “63)” ... D/PowerManagerService( 63): bootCompleted I/TelephonyRegistry( 63): notifyServiceState: 0 home Android Android 310260 UMTS CSS not supp... I/TelephonyRegistry( 63): notifyDataConnection: state=0 isDataConnectivityPossible=false reason=null interfaceName=null networkType=3 I/SearchManagerService( 63): Building list of searchable activities I/WifiService( 63): WifiService trying to setNumAllowed to 11 with persist set to true I/ActivityManager( 63): Config changed: { scale=1.0 imsi=310/260 loc=en_US touch=3 keys=2/1/2 nav=3/1 ... I/TelephonyRegistry( 63): notifyMessageWaitingChanged: false I/TelephonyRegistry( 63): notifyCallForwardingChanged: false I/TelephonyRegistry( 63): notifyDataConnection: state=1 isDataConnectivityPossible=true reason=simL... I/TelephonyRegistry( 63): notifyDataConnection: state=2 isDataConnectivityPossible=true reason=simL... D/Tethering( 63): MasterInitialState.processMessage what=3 I/ActivityManager( 63): Start proc android.process.media for broadcast com.android.providers.downloads/.DownloadReceiver: pid=223 uid=10002 gids={1015, 2001, 3003} I/RecoverySystem( 63): No recovery log file W/WindowManager( 63): App freeze timeout expired. ... 103
  • 104. 2.2. dumpsys Currently running services: SurfaceFlinger accessibility account activity alarm appwidget audio backup ... wifi window ------------------------------------------------------------------------------- DUMP OF SERVICE SurfaceFlinger: + Layer 0x396b90 z= 21000, pos=( 0, 0), size=( 480, 800), needsBlending=1, needsDithering=1, invalidat ... 0] name=com.android.launcher/com.android.launcher2.Launcher client=0x391e48, identity=6 [ head= 1, available= 2, queued= 0 ] reallocMask=00000000, inUse=-1, identity=6, status=0 format= 1, [480x800:480] [480x800:480], freezeLock=0x0, dq-q-time=53756 us ... 104
  • 105. 3. Calling on System Services â—Ź Use getSystemService â—Ź Ex: NotificationManager Object reference: String ns = Context.NOTIFICATION_SERVICE; NotificationManager mNotificationManager = (NotificationManager) getSystemService(ns); â—Ź Prepare your content â—Ź Call on the object: mNotificationManager.notify(HELLO_ID, notification); 105
  • 106. 4. Inside a few System Services â—Ź Get the AOSP ... repo, etc. â—Ź Tricks: â—Ź Import into Eclipse and collapse methods â—Ź Use reverse-engineering tools: – Imagix – Rationale – Lattix – Scitools – ... â—Ź Be patient, this isn't documented anywhere ... 106
  • 107. 4.1. ActivityManager â—Ź Start new Activities, Services â—Ź Fetch Content Providers â—Ź Intent broadcasting â—Ź OOM adj. maintenance â—Ź Application Not Responding â—Ź Permissions â—Ź Task management â—Ź Lifecycle management 107
  • 108. â—Ź Ex. starting new app from Launcher: â—Ź onClick(Launcher) â—Ź startActivity(Activity.java) â—Ź <Binder> â—Ź ActivityManagerService â—Ź startViaZygote(Process.java) â—Ź <Socket> â—Ź Zygote 108
  • 109. 4.2. Package Manager â—Ź 10 kloc â—Ź 450 K â—Ź Installation / removal â—Ź Permissions â—Ź Intent resolution (also IntentResolver.java) â—Ź Called by Activity Manager 109
  • 110. 4.3. Window Manager â—Ź Main thread â—Ź Window manipulation â—Ź Wallpaper handling â—Ź Orientation â—Ź Focus â—Ź Layering â—Ź Input event management 110
  • 111. 4.4. Notification Manager â—Ź Toasts â—Ź Notifications â—Ź Sound playback (see NotificationPlayer.java) 111
  • 112. 4.5. Power Manager â—Ź Wakelocks â—Ź Sleep â—Ź Brightness â—Ź Lock 112
  • 113. 4.6. Network Management Service â—Ź Talks to “netd” /system/netd â—Ź Interface configuration â—Ź Tethering â—Ź DNS 113
  • 114. 4.7. Mount Service â—Ź Mount / Unmount â—Ź Format â—Ź USB mass storage â—Ź OBB 114
  • 115. 4.8. Location Manager â—Ź Manage location providers â—Ź getBestProvider() â—Ź Proximity alerts â—Ź Last known location 115
  • 116. 4.9. Status Bar Manager â—Ź Expand / collapse â—Ź Icon visibility â—Ź Reveal callbacks â—Ź Callbacks for notification manager 116
  • 117. 4.10. Backup Manager â—Ź Enable / disable â—Ź Transport management â—Ź backupNow() â—Ź ... 117
  • 118. 5. Creating your own System Service â—Ź Add your code to: frameworks/base/services/java/com/android/server/ â—Ź Have the SystemServer.java init+reg. your service â—Ź Define hardware API for apps â—Ź Expose through: â—Ź frameworks/base/core/java/android/os/[server].aidl â—Ź Call on native “driver” code through JNI â—Ź Implement or connect to appropriate driver â—Ź Create an app that calls on service â—Ź May need to create new SDK ... 118
  • 119. 5.1. OpersysService.java package com.android.server; import android.content.Context; import android.os.Handler; import android.os.IOpersysService; import android.os.Looper; import android.os.Message; import android.os.Process; import android.util.Log; public class OpersysService extends IOpersysService.Stub {     private static final String TAG = "OpersysService";     private OpersysWorkerThread mWorker;     private OpersysWorkerHandler mHandler;     private Context mContext;     public OpersysService(Context context) { super(); mContext = context; mWorker = new OpersysWorkerThread("OpersysServiceWorker"); mWorker.start(); Log.i(TAG, "Spawned worker thread");     }     public void setValue(int val) { Log.i(TAG, "setValue " + val); Message msg = Message.obtain(); msg.what = OpersysWorkerHandler.MESSAGE_SET; msg.arg1 = val; mHandler.sendMessage(msg); 119     }
  • 120.     private class OpersysWorkerThread extends Thread{ public OpersysWorkerThread(String name) {     super(name); } public void run() {     Looper.prepare();     mHandler = new OpersysWorkerHandler();     Looper.loop(); }     }     private class OpersysWorkerHandler extends Handler { private static final int MESSAGE_SET = 0; @Override public void handleMessage(Message msg) {     try { if (msg.what == MESSAGE_SET) {     Log.i(TAG, "set message received: " + msg.arg1); }     }     catch (Exception e) { // Log, don't crash! Log.e(TAG, "Exception in OpersysWorkerHandler.handleMessage:", e);      } }     } } 120
  • 122. 5.3. frameworks/base/Android.mk ... core/java/android/os/IPowerManager.aidl core/java/android/os/IOpersysService.aidl core/java/android/os/IRemoteCallback.aidl ... 122
  • 123. 5.4. SystemServer.java Should eventually be Context.OPERSYS_SERVICE ...    try {                 Slog.i(TAG, "Opersys Service");                 ServiceManager.addService(“opersys”, new OpersysService(context));             } catch (Throwable e) {                 Slog.e(TAG, "Failure starting OpersysService Service", e);             } ... 123
  • 124. 5.5. HelloServer.java package com.opersys.helloserver; import android.app.Activity; import android.os.Bundle; import android.os.ServiceManager; import android.os.IOpersysService; import android.util.Log; public class HelloServer extends Activity {     private static final String DTAG = "HelloServer";     /** Called when the activity is first created. */     @Override     public void onCreate(Bundle savedInstanceState) {         super.onCreate(savedInstanceState);         setContentView(R.layout.main);                  IOpersysService om =  IOpersysService.Stub.asInterface(ServiceManager.getService("opersys"));         try {     Log.d(DTAG, "Going to call service");     om.setValue(20);     Log.d(DTAG, "Service called succesfully");         }         catch (Exception e) {     Log.d(DTAG, "FAILED to call service");     e.printStackTrace();         }     } 124 }
  • 125. Hardware Abstraction Layer /frameworks/base/core/... /frameworks/base/services/java/... AOSP-provided ASL /frameworks/base/services/jni/ /hardware/libhardware/ /device/[MANUF.]/[DEVICE] Manuf.-provided /sdk/emulator/ Manuf. license Kernel or module Manuf.-provided GPL-license 125
  • 126. â—Ź [aosp]/hardware/libhardware/include/hardware â—Ź gps.h â—Ź lights.h â—Ź sensors.h â—Ź [aosp]/hardware/ril/include/telephony/ â—Ź ril.h â—Ź Examples in [aosp]/device/samsung/crespo/ â—Ź libaudio â—Ź libcamera â—Ź liblight â—Ź libsensors â—Ź Using JNI to call C functions 126
  • 127. 1. Call to JNI public class HelloJni extends Activity {     /** Called when the activity is first created. */     @Override     public void onCreate(Bundle savedInstanceState)     {         super.onCreate(savedInstanceState);         /* Create a TextView and set its content.          * the text is retrieved by calling a native          * function.          */         TextView  tv = new TextView(this);         tv.setText( stringFromJNI() + " " + pid() );         setContentView(tv);     }     /* A native method that is implemented by the      * 'hello­jni' native library, which is packaged      * with this application.      */     public native String  stringFromJNI(); ...     /* this is used to load the 'hello­jni' library on application      * startup. The library has already been unpacked into      * /data/data/com.example.HelloJni/lib/libhello­jni.so at      * installation time by the package manager.      */     static {         System.loadLibrary("hello­jni");     } } 127
  • 128. 2. JNI function in C jstring Java_com_example_hellojni_HelloJni_stringFromJNI( JNIEnv* env,                                                   jobject thiz ) {     return (*env)­>NewStringUTF(env, "Hello from JNI !"); } 128
  • 129. Android Framework â—Ź Location and components â—Ź android.* â—Ź Customization 129
  • 130. 1. Location and components â—Ź [aosp]/frameworks/base â—Ź /cmds => native cmds and daemons â—Ź /core => android.* and com.android.* â—Ź /data => Fonts and sounds â—Ź /graphics => 2D & Renderscript â—Ź /include => “C” includes â—Ź /keystore => security key store â—Ź /libs => “C” libraries â—Ź /location => Location provider â—Ź /media => Stagefright, codecs, etc. â—Ź /native => Native code for some frameworks components â—Ź /obex => Bluetooth obex â—Ź /opengl => GL library and java code â—Ź /packages => A few core packages (Status Bar) â—Ź /services => System server â—Ź /telephony => Phone related functionality â—Ź /tools => A few core tools (aapt, aidl, ...) â—Ź /voip => RTP & SIP interfaces â—Ź /vpn => VPN functionality â—Ź /wifi => Wifi manager, monitor, etc. 130
  • 131. 2. android.* accessibilityservice  content   hardware            pim         speech   accounts              database  inputmethodservice  preference  test annotation            ddm       net                 provider    text app                   debug     nfc                 security    util appwidget             emoji     os                  server      view bluetooth             gesture   service             webkit      widget 131
  • 132. 3. Customization â—Ź Extending API â—Ź Boot screen â—Ź Status bar â—Ź Network â—Ź Preloaded apps â—Ź Browser bookmarks â—Ź Email provider customization â—Ź Themes 132
  • 133. 3.1. Extending API – System service â—Ź frameworks/base/core/java/android/ â—Ź app/ContextImpl.java â—Ź content/Context.java â—Ź os/OpersysManager.java 133
  • 138. 3.2. Boot screen â—Ź Create 320x480 image â—Ź Install imagemagick $ sudo apt-get install imagemagick â—Ź Convert image to .r format $ convert screen.jpg screen.r â—Ź Convert image to 565 format $ rgb2565 < screen.r > screen.565 â—Ź Write image to flash $ fastboot flash splash1 screen.565 138
  • 139. 3.3. Status bar â—Ź Location: â—Ź frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar â—Ź Look for: â—Ź mService.setIcon(...) â—Ź Disable icons with: â—Ź mService.setIconVisibility(“[ICON_NAME]", false); 139
  • 140. 3.4. Network â—Ź Locations: â—Ź Global static: – frameworks/base/core/res/res/xml/apns.xml â—Ź Device static: – PRODUCT_COPY_FILES := vendor/acme/etc/apns-conf-us.xml:system/etc/apns-conf.xml â—Ź Dynamic: – system/etc/apns-conf.xml â—Ź Format: <apn carrier="T-Mobile US" mcc="310" mnc="260" apn=" wap.voicestream.com" user="none" server="*" password="none" proxy=" 216.155.165.50" port="8080" mmsc="http://216.155.174.84/servlets/mms" /> 140
  • 141. 3.5. Preloaded apps â—Ź See build/target/products PRODUCT_PACKAGES := bouncycastle com.android.location.provider com.android.location.provider.xml core core-junit create_test_dmtrace dalvikvm dexdeps ... 141
  • 142. 3.6. Browser bookmarks â—Ź See packages/apps/Browser/res/values/strings.xml <!-- Bookmarks --> <string-array name="bookmarks"> <item>Google</item> <item>http://www.google.com/</item> <item>Yahoo!</item> <item>http://www.yahoo.com/</item> <item>MSN</item> <item>http://www.msn.com/</item> <item>MySpace</item> <item>http://www.myspace.com/</item> ... 142
  • 143. 3.7. Email provider customization â—Ź See packages/apps/Email/res/xml/providers.xml <!-- Gmail variants --> <provider id="gmail" label="Gmail" domain="gmail.com"> <incoming uri="imap+ssl+://imap.gmail.com" username="$email"/> <outgoing uri="smtp+ssl+://smtp.gmail.com" username="$email"/> </provider> <provider id="googlemail" label="Google Mail" domain="googlemail.com"> <incoming uri="imap+ssl+://imap.googlemail.com" username="$email"/> <outgoing uri="smtp+ssl+://smtp.googlemail.com" username="$email"/> </provider> ... <!-- Common US providers --> <provider id="aim" label="AIM" domain="aim.com"> <incoming uri="imap://imap.aim.com" label="IMAP" username="$email"/> <outgoing uri="smtp://smtp.aim.com:587" username="$email"/> </provider> <provider id="aol" label="AOL" domain="aol.com"> <incoming uri="imap://imap.aol.com" label="IMAP" username="$email"/> <outgoing uri="smtp://smtp.aol.com:587" username="$email"/> </provider> ... 143
  • 144. 3.8. Themes â—Ź See framework/base/core/res/res/values/styles.xml 144
  • 145. Custom Toolchains and Dev Kits â—Ź Rationale â—Ź SDK generation â—Ź NDK generation â—Ź Creating a cross-dev toolchain 145
  • 146. 1. Rationale â—Ź SDK: â—Ź Providing other internal teams or external developers access to your modified/custom Android APIs. â—Ź NDK: â—Ź Same as SDK rationale â—Ź Custom cross-dev toolchain: â—Ź To avoid having to use a binary toolchain from 3rd party. â—Ź To control the build parameters used to create the toolchain. Ex.: use uClibc instead of glibc. 146
  • 147. 2. SDK generation â—Ź Building the SDK: $ . build/envsetup.sh $ lunch sdk-eng $ make sdk â—Ź If API modified, do this before make: $ make update-api â—Ź Location: [aosp]/out/host/linux-x86/sdk/ â—Ź Using a custom SDK: â—Ź Eclipse->Window->Preferences->Android->”SDK Location” â—Ź Eclipse->Window->"Android SDK and AVD Manager"- >"Installed Packages"->"Update All..." 147
  • 148. 3. NDK generation â—Ź Build $ cd ndk/build/tools $ export ANDROID_NDK_ROOT=[aosp]/ndk $ ./make-release --help $ ./make-release IMPORTANT WARNING !! This script is used to generate an NDK release package from scratch for the following host platforms: linux-x86 This process is EXTREMELY LONG and may take SEVERAL HOURS on a dual-core machine. If you plan to do that often, please read docs/DEVELOPMENT.TXT that provides instructions on how to do that more easily. Are you sure you want to do that [y/N] 148
  • 149. 4. Creating a cross-dev toolchain â—Ź crosstool-ng: successor to crosstool â—Ź Available at: http://ymorin.is-a-geek.org/projects/crosstool â—Ź Downloads, patches, builds, installs, etc. â—Ź Comprises 23 steps â—Ź Menuconfig-based â—Ź Supports uClibc, glibc and eglibc â—Ź Supports ARM, Blackfin, MIPS, PowerPC, SH, … â—Ź Fairly well maintained 149
  • 150. â—Ź Must make sure the following are installed on Ubuntu in order to use crosstool-ng: â—Ź gawk â—Ź texinfo â—Ź automake â—Ź libtool â—Ź cvs â—Ź libncurses5-dev â—Ź Use “sudo apt-get install” to get those 150
  • 151. â—Ź Download and extract to ${PRJROOT}/build-tools â—Ź Configure crosstool: $ cd crosstool-ng-1.10.0/ $ ./configure â—Ź Build and install crosstool-ng: $ make $ make install â—Ź Configure crosstool: $ cd ${PRJROOT}/build-tools $ ct-ng menuconfig 151
  • 152. â—Ź Options: â—Ź Paths->Prefix directory: ${PREFIX}/${CT_TARGET} â—Ź Target options->architecture: powerpc â—Ź OS->Target OS: linux â—Ź C library->C library: glibc â—Ź C library->Extra flags: -U_FORTIFY_SOURCE â—Ź Debug facilities: gdb & strace â—Ź Build the toolchain: $ ct-ng build 152
  • 153. Compatibility Test Suite â—Ź Android Compatibility Program: â—Ź Source code to Android stack â—Ź Compatibility Definition Document (CDD) – Policy â—Ź Compatibility Test Suite (CTS) – Mechanism â—Ź Each Android version has own CDD & CTS â—Ź CTS: â—Ź Part of AOSP â—Ź Run from host using USB over to attached device â—Ź Based on JUnit â—Ź Runs various test apps on target â—Ź Relies on ADB â—Ź Provides report to be be analyzed and/or sent back to Google 153
  • 154. 154
  • 155. â—Ź Report: â—Ź .zip file containing XML files and screen-shots â—Ź Sent to: cts@android.com â—Ź Building the CTS: $ . build/envsetup.sh $ make cts â—Ź Launching the CTS: $ cd out/host/linux-x86/bin/ $ ./cts $ cts_host > $ cts_host > help ... 155
  • 156. â—Ź Using the CTS: $ cts_host > ls --plan List of plans (8 in total): Signature RefApp VM Performance AppSecurity Android Java CTS $ ./cts start --plan CTS 156
  • 157. â—Ź Areas covered: â—Ź Signature tests â—Ź Platform API tests â—Ź Dalvik VM tests â—Ź Platform Data Model â—Ź Platform Intents â—Ź Platform Permissions â—Ź Platform Resources 157
  • 159. Acknowledgements: â—Ź Some figures and snippets taken from Google's Android “Dev Guide” at developer.android.com distributed under the Apache 2.0 license. 159