Android Variants, Hacks, Tricks and Resources

Android Hacks,
Variants, Tricks and
Resources

About me
● Author of:

● Introduced Linux Trace Toolkit in 1999
● Originated Adeos and relayfs (kernel/relay.c)

2

Agenda
● AOSP's limitations
● Tearing AOSP apart
● Forks
● Ports
● Mods
● Melds

3

AOSP's limits
● Rigid
● Closed dev model
● Fits Google's prerogatives
● Excludes a lot of stuff
● ... IOW, doesn't always fit what you need

4

Tearing AOSP apart
● Forks
● Ports
● Mods
● Melds

5

Forks
● Cyanogenmod
● Replicant
● MIUI

6

Cyanogenmod
● After-market handset firmware
● Requires rooted phone
● http://www.cyanogenmod.com
● Advertized features:
● Lockscreen Gestures
● Phone Goggles
● OpenVPN
● Incognito mode
● Themes support
● DSP Equalizer
7

● More interestingly:
● http://wiki.cyanogenmod.com/
● https://github.com/CyanogenMod
● Includes Busybox
● Custom Launcher (ADWLauncher)
● Lots of tiny tweaks and mods ... worth doing a “diff”

9

Replicant
● Android distro that is 100% Free Software
● http://replicant.us/
● Includes FDroid free software app store

10

MIUI
● Closed-source fork with slick UI enhancements
● Many translations
● http://en.miui.com/
● Advertized features:
● Home screen
● Dialer
● SMS
● Contacts
● Themes
● Camera
● Gallery
● Net disk, File manager, Traffic monitor, Backup, Notes, ...
11

Ports
● RIM Playbook
● BlueStacks
● Alien Dalvik

13

Alien Dalvik (Myriad Group)

16

Mods
● XDA Developers
● ...

17

Melds
● Stock glibc stack
● Custom stacks

18

Melding with glibc stack

1.Rationale
2.Architecture
3.Tools
4.Embedded Linux Workspace
5.Basic root filesystem structure
6.Libraries
7.Kernel modules
8.Device files
9.Main system applications
10. Auto-generating filesystems
19

1. Rationale
● Port existing Linux apps
● Create glibc-based apps to coexist with
Android's Bionic-based user-space
● Avoid having to deal with AOSP's build system
● Avoid having having to deal w/ Bionic's quirks
and limitations
● Benefit from standard GNU world

20

3. Tools
● GNU cross-development toolchain:
● gcc - compiler
● as - assembler
● ld - linker
● gdb/gdbserver - debugger
● etc.
● C library: uClibc, eglibc or glibc

23

4. Embedded Linux Workspace
● Need to organize the components used during
cross-platform development. Workspace layout:
bootldr: target bootloader (s)
build-tools: toolchain build packages and sources
debug: debugging tools
doc: project documentation
images: binary images ready to be used on target
kernel: sources and build directories for target kernels
project: your own custom code for the target
rootfs: root filesystem as seen on the target
sysapps: sources for target's system applications
tmp: temporary data and experiments
tools: toolchain and all other tools required to build
software for the target.

24

4.1. Workspace env. vars. script
● Complete workspace script (devex)
export PROJECT=emblinux
export PRJROOT=/home/karim/${PROJECT}
export TARGET=armnonelinuxgnueabi
export PATH=${PATH}:[CODESOURCERY_DIR]/bin
cd $PRJROOT
● To use this script:
$ .⌴ devex
● Possible values for $TARGET:
● ARM: arm-linux, arm-unknown-linux-gnueabi
● MIPS: mips-linux, mipsel-unknown-linux-gnu
● I386: i386-linux, i586-geode-linux-uclibc
25

5. Basic root filesystem structure
● Unix FS structured for multi-user systems
● Some directories not necessary for embedded
● Filesystem Hierarchy Standard (FHS):
● /bin => Essential user binaries
● /boot => Bootloader and kernel images
● /dev => Device files
● /etc => System configuration
● /home => User home directories
● /lib => Essential shared libs and kernel modules
● /mnt => Temporary mount point
● /opt => Add-on software packages
● /sbin => Essential system binaries
● /tmp => Temporary files
● /usr => Secondary hierarchy (mostly user apps)
● /var => Variable data generated by daemons
26

● Non-essential multi-user dirs:
● /home, /mnt, /opt, /root
● Depends on bootloader:
● /boot
● Traditionally “essential”:
● /bin, /dev, /etc, /lib, /proc, /sbin, /usr, /tmp, /var
● Careful with “/etc”, Android needs it to point to
“/system/etc” for Dbus config ... Just hack it.
● Contain their own hierarchy:
● /usr, /var 27

● What are all these binaries directories for?
● /bin => Essential binaries for user and admin
● /sbin => Essential binaries for admin
● /usr/bin => Non-essential user and admin binaries
● /usr/sbin=> Non-essential admin binaries
● What are all those libraries directories for?
● /lib => Essential system libraries
● /usr/lib => Non-essential libraries
● The kernel does not force FS layout. Layout is
“universally” agree upon (i.e. FHS.)

28

● To start working on rootfs:
$ cd ${PRJROOT}/rootfs
● Create core rootfs directories:
$ mkdir bin lib sbin usr var
● Create the /usr hierarchy:
$ mkdir usr/{bin,lib,sbin}
● Create the /var hierarchy:
$ mkdir var/{lib,lock,log,run,tmp}
$ chmod 1777 var/tmp

29

6. Libraries
1.glibc
2.uClibc

30

6.1. glibc
● glibc components:
● Actual shared libraries:
– Format: libLIB_NAME-GLIBC_VER.so
– Examples: libm-2.3.2.so, libc-2.3.2.so
● Major revision version symbolic links:
– Format: libLIB_NAME.so.MAJOR_REV_VER
– Examples: libdl.so.2, libc.so.6
● Version-independent symbolic links to the major
revision version symbolic links:
– Format: libLIB_NAME.so
– Examples: libdl.so, libm.so
● Static library archives:
– Format: libLIB_NAME.a
– Examples: libdl.a, libm.a
31

● For target, need:
● The actual shared libs
● The major revision version symbolic links
● Also need dynamic linker:
● Actual linker: ld-GLIBC_VER.so
● Symbolic link to linker:
– x86, ARM, SH, m68k => ld-linux.so.MAJOR_REV_VER
– MIPS, PPC => ld.so.MAJOR_REV_VER
● Must determine exact library components required.
● BELS table 6.2 contains complete list

32

● Most important components:
● ld => the dynamic linker
● libc => the C library
● libm => the math library
● libdl => the shared objects manipulation library
● Must determine exact dependencies of your
applications.
● Native ldd is not cross-platform-capable
● Can use readelf or uclibcldd:
33

● Using readelf:
$ armlinuxreadelf a ${PRJROOT}/rootfs/bin/busybox
> | grep "Shared library"
0x00000001 (NEEDED) Shared library: [libc.so.0]
● Using uclibc-ldd:
$ armuclibcldd ${PRJROOT}/rootfs/bin/busybox
libc.so.0 => /home/karim/examplesys/tools/uclibc/lib/libc.so.0
/lib/lduClibc.so.0 => /lib/lduClibc.so.0
● Copying important libraries to target rootfs:
$ cd ${TARGET_PREFIX}/lib
$ for file in libc libcrypt libdl libm
> libpthread libresolv libutil
> do
> cp $file*.so ${PRJROOT}/rootfs/lib
> cp d $file.so.[*09] ${PRJROOT}/rootfs/lib
> done
$ cp d ld*.so* ${PRJROOT}/rootfs/lib

34

● Copying all libraries:
$ cp d [CODESOURCERY_DIR]/armnonelinuxgnueabi/libc/lib/*
> ${PRJROOT}/rootfs/lib

● Stripping all target libraries for space efficiency:
$ armnonelinuxgnueabistrip ${PRJROOT}/rootfs/lib/*.so*

35

6.2. uClibc
● Same naming conventions as glibc
● Implements most of the glibc components:
● ld, libc, libcrypt, libdl, libm, libpthread, libresolv, libutil.
● uClibc libraries can coexist with glibc libraries in
target's /lib directory.
● Copying important libraries to target rootfs:
$ cd ${PREFIX}/uclibc/lib
$ for file in libuClibc lduClibc libc libdl
> libcrypt libm libresolv libutil
> do
> cp $file*.so ${PRJROOT}/rootfs/lib
> cp d $file.so.[*09] ${PRJROOT}/rootfs/lib
> done

36

● Copying all uClibc components:
$ cd ${PREFIX}/uclibc/lib
$ cp **.so ${PRJROOT}/rootfs/lib
$ cp d *.so.[*09] ${PRJROOT}/rootfs/lib
● No need to strip uClibc libraries, they are stripped
by the uClibc build script.

37

7. Kernel modules
● Kernel modules are located in /lib/modules, so they
must be installed in $
{PRJROOT}/rootfs/lib/modules.
● Copying modules built earlier:
$ cp a ${PRJROOT}/images/modules2.6.37/*
> ${PRJROOT}/rootfs
● Module loading customization (/etc/modprobe.conf
or /etc/modprobe.d/)

38

8. Device files
● All devices in Linux are seen as files (except
Ethernet interfaces.)
● Typical workstation distros use udev
● Keep a copy of Documentation/devices.txt handy
● See BELS table 6.3 for core set of /dev entries
● Properties of each /dev node:
● Filename (node name)
● Type (char / block)
● Major number (What type of device?)
● Minor number (Which instance of the device?)
● Permission bits
● No need to create these entries since AOSP does
it for us 39

9. Main system applications
● Unix systems rely on a common set of commands
● Standard distros have one binary per command
● May compile each relevant command one-by-one
or use packages that provide many commands in
a single binary:
1.Busybox
2.Distro

40

9.1. BusyBox
● Main package used in embedded Linux to provide
core set of Unix commands: busybox.net
[, [[, acpid, add-shell, addgroup, adduser, adjtimex, arp, arping, ash, awk, base64, basename, beep, blkid, blockdev,
bootchartd, brctl, bunzip2, bzcat, bzip2, cal, cat, catv, chat, chattr, chgrp, chmod, chown, chpasswd, chpst, chroot, chrt,
chvt, cksum, clear, cmp, comm, cp, cpio, crond, crontab, cryptpw, cttyhack, cut, date, dc, dd, deallocvt, delgroup, deluser,
depmod, devmem, df, dhcprelay, diff, dirname, dmesg, dnsd, dnsdomainname, dos2unix, du, dumpkmap, dumpleases,
echo, ed, egrep, eject, env, envdir, envuidgid, ether-wake, expand, expr, fakeidentd, false, fbset, fbsplash, fdflush, fdformat,
fdisk, fgconsole, fgrep, find, findfs, flock, fold, free, freeramdisk, fsck, fsck.minix, fsync, ftpd, ftpget, ftpput, fuser, getopt,
getty, grep, gunzip, gzip, halt, hd, hdparm, head, hexdump, hostid, hostname, httpd, hush, hwclock, id, ifconfig, ifdown,
ifenslave, ifplugd, ifup, inetd, init, insmod, install, ionice, iostat, ip, ipaddr, ipcalc, ipcrm, ipcs, iplink, iproute, iprule, iptunnel,
kbd_mode, kill, killall, killall5, klogd, last, length, less, linux32, linux64, linuxrc, ln, loadfont, loadkmap, logger, login,
logname, logread, losetup, lpd, lpq, lpr, ls, lsattr, lsmod, lspci, lsusb, lzcat, lzma, lzop, lzopcat, makedevs, makemime, man,
md5sum, mdev, mesg, microcom, mkdir, mkdosfs, mke2fs, mkfifo, mkfs.ext2, mkfs.minix, mkfs.vfat, mknod, mkpasswd,
mkswap, mktemp, modinfo, modprobe, more, mount, mountpoint, mpstat, mt, mv, nameif, nbd-client, nc, netstat, nice,
nmeter, nohup, nslookup, ntpd, od, openvt, passwd, patch, pgrep, pidof, ping, ping6, pipe_progress, pivot_root, pkill, pmap,
popmaildir, poweroff, powertop, printenv, printf, ps, pscan, pwd, raidautorun, rdate, rdev, readahead, readlink, readprofile,
realpath, reboot, reformime, remove-shell, renice, reset, resize, rev, rm, rmdir, rmmod, route, rpm, rpm2cpio, rtcwake, run-
parts, runlevel, runsv, runsvdir, rx, script, scriptreplay, sed, sendmail, seq, setarch, setconsole, setfont, setkeycodes,
setlogcons, setsid, setuidgid, sh, sha1sum, sha256sum, sha512sum, showkey, slattach, sleep, smemcap, softlimit, sort,
split, start-stop-daemon, stat, strings, stty, su, sulogin, sum, sv, svlogd, swapoff, swapon, switch_root, sync, sysctl, syslogd,
tac, tail, tar, tcpsvd, tee, telnet, telnetd, test, tftp, tftpd, time, timeout, top, touch, tr, traceroute, traceroute6, true, tty, ttysize,
tunctl, udhcpc, udhcpd, udpsvd, umount, uname, unexpand, uniq, unix2dos, unlzma, unlzop, unxz, unzip, uptime, usleep,
uudecode, uuencode, vconfig, vi, vlock, volname, wall, watch, watchdog, wc, wget, which, who, whoami, xargs, xz, xzcat,
yes, zcat, zcip

41

● Download BusyBox (1.18.3) to your $
{PRJROOT}/sysapps directory and extract it there.
● Move to the directory for the rest of the setup:
$ cd ${PRJROOT}/sysapps/busybox1.18.3

● Configuration of BusyBox's options:
$ make menuconfig

42

● “Busybox Settings”:
● “Build Options” -> Cross-compiler prefix:
${TARGET}
● “Installation Options” -> Installation prefix:
${PRJROOT}/rootfs
● Build:
$ make

● Install:
$ make install

44

● Only one binary has been installed: /bin/busybox
● All commands are symbolic links to /bin/busybox
● Determining the command issued done through
main's argv[] and argc.
● Creating arbitrary links doesn't work
● BusyBox can be told to create hard-links
● Full command doc on web and in package
● Customizing the paths for the various shells:
# Set path
PATH=/bin:/sbin:/usr/bin:/usr/sbin
export PATH

45

10. Auto-generating FSes/distros
● Yocto
● Buildroot
● PTXdist
● OpenWRT
● LTIB
● OpenEmbedded
● Gentoo

46

Thank you ...

karim.yaghmour@opersys.com

Android Variants, Hacks, Tricks and Resources

More Related Content

What's hot (20)

Viewers also liked (19)

Similar to Android Variants, Hacks, Tricks and Resources (20)

More from Opersys inc. (19)

Recently uploaded (20)

Android Variants, Hacks, Tricks and Resources