Q4.11: Porting Android to new Platforms

linaroorg 4,800 views 24 slides Mar 20, 2014
Slide 1
Slide 1 of 24
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8
Slide 9
9
Slide 10
10
Slide 11
11
Slide 12
12
Slide 13
13
Slide 14
14
Slide 15
15
Slide 16
16
Slide 17
17
Slide 18
18
Slide 19
19
Slide 20
20
Slide 21
21
Slide 22
22
Slide 23
23
Slide 24
24

About This Presentation

Resource: Q4.11
Name: Porting Android to new Platforms
Date: 28-11-2011
Speaker: Amit Pundir


Slide Content

Porting Android to new Platforms
Amit Pundir
Android Engineer, Linaro

Android Software Stack

Applications
Applications
Application
Frameworks
Libraries &
Runtime
Linux
Kernel
Audio Display
Hardware
Abstraction
Layers
Firmware Binaries
WiFi BinderCamera Logger ...
GPSRadio (RIL)Camera
Media
NFSSensorsAudio ...
Skia
Core Libraries
Dalvik VM...
SQlite
ALSA
Freetype
Input
Webkit
System Services
Power Manager Activity ManagerPackage Manager
Content ManagerBattery ServiceWindow Manager
Location ManagerAudio Service Alarm Manager
Network ManagerMedia Server ...
Home SettingsMedia PlayerCameraDialer ...

Android Open Source Project

●AOSP is not a single project.
●Hundreds of independent projects having own Git repositories.
●Don't need to pull the projects one by one. Repo tool for the
rescue.
●AOSP manifest file to download a snapshot.
●Android Documentation: Downloading the source tree
http://source.android.com/source/downloading.html

AOSP Code Structure

bionic Android's C library.
bootable Legacy Bootloader/Recovery code for reference
build AOSP Build framework
cts Android's Compatibility Test Suit
dalvik Dalvik Virtual Machine
development Development tools #tutorials #monkey
device Vendor specific configuration files
external External projects used in AOSP
frameworks Android core application framework
hardware Hardware specific libraries/modules #HAL
kernel Linux Kernel
libcore Apache Harmony. Fee Java implementation. Used by
Dalvik.
ndk Native Development Kit
packages AOSP's stock applications
prebuilt Prebuilt binaries such as Toolchain
sdk Android's Software Development Kit
system Android's core system libraries/binaries #init #toolbox #adb

Android Kernel

●Android patches are not available mainline.
●android-common project
→ Android patches on top of Linus's base tree.
●Extract patches and apply them to your Target specific
kernel.

Android Kernel Features

●Binder
→ Android's IPC mechanism. Inspired from Open Binder project.
●Ashmem or Anonymous Shared Memory
→ Shared memory allocator. Discards shared units under memory pressure.
●Logger
→ Android's driver which logs data from user space.
●Wakelocks
→ Prevents a system to enter suspend or low power states.
●Out Of Memory handler
→ Aggressive OOM handler. Triggers before Kernel's default
implementation.
●Alarm
→ Android's alarm timer implementation on top of Kernel's RTC
implementation.
●RAM console
→ Logs last Kernel log. Accessible through /proc/last_kmsg
●Paranoid network
→ Network administration through uid/pid e.g AID_NET_*

Common Android Hardware
Abstraction Layers

libaudio.so AudioHardwareInterface implementation.
libgralloc.so Graphics Buffer Allocator
“hardware/libhardware/modules/gralloc/”
libsensor.so Sensor modules.
libcamera.so CameraHardwareInterface implementation.
libgps.so GPS module.
libstagefrighthw.soStagefright implementation for h/w codecs.
libril.so Radio interface layer module
... ...

HAL Module/Library loaders

●Run time loading
●hw_get_module()
●libgps, liblights, libgralloc, libsensors,
liboverlays etc
●dlopen()
●libstagefrighthw, libril etc
●Build time linking
●libaudio, libcamera etc
●Linux standard sysfs and /dev nodes
●Power management, Input devices etc

Device/Vendor specific
configuration files

● Build config files
●Target build requirements are set by build/core/{main.mk,
config.mk, product.mk, product_config.mk}
●Build process looks for target specific config file
BoardConfig.mk at device/*/$(TARGET_DEVICE) or vendor/*/$
(TARGET_DEVICE)
●TARGET_PRODUCT = TARGET_DEVICE =
PRODUCT_DEVICE, where PRODUCT_DEVICE is defined in
AndroidProducts.mk
● Android Run time config files init.rc, init.TARGET_PRODUCT.rc,
ueventd.rc, ueventd.TARGET_PRODUCT.rc, vold.fstab etc
● Set optional PRODUCT_PACKAGES for Pre-loaded applications.
● Generate Project manifest file. It is different from an Android
Application Manifest file.

AOSP Build Process

●Android Documentation: Building the system
http://source.android.com/source/building.html
●$ . build/envsetup.sh
→ Setting up build environment
●$ lunch
→ Choose correct TARGET_PRODUCT
●$ export USE_CCACHE = 1
→ will cache object files generated by the C/C++ compiler which can
be used to speed up next build.
●$ make -jX
→ where X = “the number of CPU cores in your build machine” + 1.
OR
●$ mm
→ make alias which is handy while building AOSP projects
independently.

Android Boot Process

Kernel
Init
Service
Manager
system
server
Zygote... ...
binder
System Services
Activity Manager Power ManagerPackage Manager
Content Manager Battery ServiceWindow Manager
Location Manager Audio ServiceAlarm Manager
Network Manager Media Server...
System
Server
Android
Application

Android Debugging

●Increase loglevel in init.rc
●dmesg
→ Dump Kernel logs
●logcat
→ Dump System logs
●adb and ddms
→ Android debug bridge and tool for remote debugging.
●dumpsys and dumpstate
→ Dump system services meminfo
●/proc/last_kmsg
→ Last dmesg or kernel log to debug random crashes.
●Traceview ?
→ http://android-developers.blogspot.com/2010/10/traceview-
war-story.html

Thank You