This document provides an overview of Android internals through a series of topics:
1. It describes key Android concepts like components, intents, and the manifest file.
2. It outlines the overall Android architecture including system startup processes like the bootloader, kernel, init, zygote and system server.
3. It covers various aspects of the Android system like the Linux kernel customizations, native user-space environment, Dalvik VM, and Java Native Interface.
4. It also profiles important system-level components like the system server, activity manager, and Binder IPC mechanism.
This presentation covers the working model about Process, Thread, system call, Memory operations, Binder IPC, and interactions with Android frameworks.
Binder is what differentiates Android from Linux, it is most important internal building block of Android, it is a subject every Android programmer should be familiar with
This presentation covers the working model about Process, Thread, system call, Memory operations, Binder IPC, and interactions with Android frameworks.
Binder is what differentiates Android from Linux, it is most important internal building block of Android, it is a subject every Android programmer should be familiar with
I have tried to present maximum detail on android booting sequence in a very abstract way. I hope it would be useful. If you find any correction needed please mention it on comments. Happy Coding :)
For new age touch-based embedded devices, Android is becoming a popular OS going beyond mobile phones. With its roots from Embedded Linux, Android framework offers benefits in terms of rich libraries, open-source and multi-device support. Emertxe’s hands-on Embedded Android Training Course is designed to customize, build and deploy custom Embedded OS on ARM target. Rich set of projects will make your learning complete.
Android is a Linux-based architecture. In addition to the original Linux driver, Android need other additional device driver, like Android Logger, Binder, Low Memory killer, Power Management for android(wakelock), ASHMEM, etc out of which ashmem ,logger and binder are all character device drivers.
Android Things is the latest attempt from Google to connect the dots between the cloud and devices by introducing an OS that is exclusively built for IoT devices. Initially announced as project Brillo, Android Things helps developers to build devices faster and enable them integrate with cloud services. This presentation traces the architectural aspects of Android Things by connecting it back with Embedded Linux, Embedded Android and Brillo.
There is a surge in number of sensors / devices that are getting connected under the umbrella of Internet-Of-Things (IoT). These devices need to be integrated into the Android system and accessed via applications, which is covered in the course. Our Android system development course curriculum over weekends with practicals ensures you learn all critical components to get started.
Slides from Android Builder's Summit 2014 in San Jose, CA
In this talk I describe the internal workings of the Android graphics stack from the Application layer down through the stack to pixels on the screen. It is a fairly complex journey, taking in two different 2D rendering engines, applications calling OpenGL ES directory, passing buffers on to the system compositor, SurfaceFlinger, and then down to the display controller or frame buffer.
There are many books, articles and paper publications about Android and related applications but only a few are related to how Android operating system works internally.In this talk we will see how android boots up , an overview of zygote , how system server and package manager works. This talk will be extremely helpful to foster understanding among android developers about Android Internals as well as everybody else who desires a general understanding of the internal working of Android powered devices.
I have tried to present maximum detail on android booting sequence in a very abstract way. I hope it would be useful. If you find any correction needed please mention it on comments. Happy Coding :)
For new age touch-based embedded devices, Android is becoming a popular OS going beyond mobile phones. With its roots from Embedded Linux, Android framework offers benefits in terms of rich libraries, open-source and multi-device support. Emertxe’s hands-on Embedded Android Training Course is designed to customize, build and deploy custom Embedded OS on ARM target. Rich set of projects will make your learning complete.
Android is a Linux-based architecture. In addition to the original Linux driver, Android need other additional device driver, like Android Logger, Binder, Low Memory killer, Power Management for android(wakelock), ASHMEM, etc out of which ashmem ,logger and binder are all character device drivers.
Android Things is the latest attempt from Google to connect the dots between the cloud and devices by introducing an OS that is exclusively built for IoT devices. Initially announced as project Brillo, Android Things helps developers to build devices faster and enable them integrate with cloud services. This presentation traces the architectural aspects of Android Things by connecting it back with Embedded Linux, Embedded Android and Brillo.
There is a surge in number of sensors / devices that are getting connected under the umbrella of Internet-Of-Things (IoT). These devices need to be integrated into the Android system and accessed via applications, which is covered in the course. Our Android system development course curriculum over weekends with practicals ensures you learn all critical components to get started.
Slides from Android Builder's Summit 2014 in San Jose, CA
In this talk I describe the internal workings of the Android graphics stack from the Application layer down through the stack to pixels on the screen. It is a fairly complex journey, taking in two different 2D rendering engines, applications calling OpenGL ES directory, passing buffers on to the system compositor, SurfaceFlinger, and then down to the display controller or frame buffer.
There are many books, articles and paper publications about Android and related applications but only a few are related to how Android operating system works internally.In this talk we will see how android boots up , an overview of zygote , how system server and package manager works. This talk will be extremely helpful to foster understanding among android developers about Android Internals as well as everybody else who desires a general understanding of the internal working of Android powered devices.
A talk presented at the Automotive Grade Linux All-Members meeting on September 8, 2015. The focus on why AGL should adopt systemd, and highlights two of the more difficult integration issues that may arise while doing so. The embedded SVG image, courtesy Marko Hoyer of ADIT, is at http://she-devel.com/2015-07-23_amm_demo.svg
Android è un argomento di grande interesse nel mondo dell'informatica ma lavorare sulla piattaforma non è semplice.
Questo intervento avrà un taglio pratico e spiegherà come procurarsi gli strumenti per compilare un modulo kernel su android, come sviluppare un semplice modulo e come caricarlo sul dispositivo. Infine, si presenterà come creare un modulo più complesso usando delle API specifiche del kernel di Android.
I sorgenti del workshop sono reperibili qui:
https://github.com/arighi/mysuspend
5. 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
6. 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
7. 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
8. 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
9. 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
10. 1.6. Remote procedure calls
● Apparently System V IPC is evil ...
● Android RPCs = Binder mechanism
● 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
11. 1.7. Development tools
● SDK:
● android – manage AVDs and SDK components
● apkbuilder – creating .apk packages
● dx – converting .jar to .dex
● adb – debug bridge
● emulator – QEMU-based ARM emulator
● ...
● Eclipse w/ ADT plugin
● NDK: GNU toolchain for native binaries
14. 3. System Startup
● Bootloader
● Kernel
● Init
● Zygote
● System Server
● Activity Manager
● Launcher (Home)
15. 3.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
17. 3.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
18. 3.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
– ...
23. 5. 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
24. 6. Native User-Space
● Mainly
● /data => User data
● /system => System components
● Also found:
● /cache
● /mnt
● /sbin
● Etc.
26. 7. 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
27. 7.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
28. 8. 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
29. 9. 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
35. 11. 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.