Android SDK via the Command Line

Mucking around with a build / Continuous Integration server on DigitalOcean. Here’s the command to get the Android SDK installed:

./android update sdk --no-ui --filter tools,platform-tools,build-tools-23.0.1,android-23,extra-android-m2repository,extra-android-support,extra-google-m2repository --dry-mode

Which says:

# ./android update sdk --no-ui --filter tools,plattory --dry-mode
Refresh Sources:
  Validate XML
  Parse XML
  Fetched Add-ons List successfully
  Refresh Sources
  Fetching URL:
Packages selected for install:
- Android SDK Tools, revision 24.4
- Android SDK Platform-tools, revision 23.0.1
- Android SDK Build-tools, revision 23.0.1
- SDK Platform Android 6.0, API 23, revision 1
- Android Support Repository, revision 22
- Android Support Library, revision 23.0.1
- Google Repository, revision 22

Dry mode is on so nothing is actually being installed.

Remove the --dry-mode flag, and it should be good to go.

Notable Quotes From Non-Programmers

Nokia just announced a line of phones running Android, which don’t actually make use of Google services. It’s a pretty bad idea, but I like the quote coming from the management suite:

“While apps that use only AOSP should run on the X phones directly, any apps that for example integrate with location or store services will need porting, a process that Stephen Elop said should take a few hours.”

It’s this kind of detachment from developers that got Microsoft into trouble in the first place with all of their attempts to develop and to capture smartphone mindshare. With a divorced-from-reality quote like that, who would actually want to bother porting their app to the “Microsoft Android App Store”? It’s like Captain Picard saying “Make it so.”, except in that case, shit actually gets done.

Go big or go home, make the Windows Phone platform strong enough and big enough to compete for app revenue, or don’t bother. A move like this is just reheated Symbian strategy. I do not see how this is competitive at all, in a market flooded with low- and mid-range Chinese competitors that do already access the full range of Google services.

A way to run GNU autoconf configure scripts using the Android NDK platform headers and libraries, improving on this:


Ubuntu 13.10 chroot on Android


Old smartphones make the perfect microservers, they’ve got more than enough horsepower for server tasks, plenty of RAM, and once rooted, full configurability. They’re durable embedded systems, honed to perfection by being produced for the mass-market, with no moving parts and the possibility of decent storage expansion. They’re extremely resource-light, usually utilizing only a few watt-hours per hour, meaning they’ve got battery-backup built right in.

Ubuntu 13.10 on an old smartphone

I had some problems getting various chroot instructions to work completely smoothly on my phone. This writeup is a synthesis of instructions from the references listed at the bottom of this post.

I used gparted to create a clean ext3-formatted Linux partition on an 8 gigabyte SD card. I mounted that partition on the host machine under /mnt and ran the debootstrap command:

HOSTNAME=ubuntu-armhf sudo debootstrap --arch=armhf --variant=minbase --foreign saucy /mnt

Then, I installed the rest of the system in emulation:

sudo apt-get install qemu-user-static qemu-system
sudo cp /usr/bin/qemu-arm-static /mnt/usr/bin
LANG=C sudo chroot mnt /usr/bin/qemu-arm-static -cpu cortex-a9 /bin/bash ./debootstrap/debootstrap --second-stage

After putting the SD card back into the smartphone, Android complained that the card was messed up:

Damaged SD Card

Which was fixable by logging into the phone’s shell as root and running e2fsck, which checked and fixed filesystem issues it detected on the card:

localhost block # e2fsck /dev/block/mmcblk0p1
e2fsck 1.41.12 (17-May-2010)
chroot-drive contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
chroot-drive: 8180/489600 files (1.2% non-contiguous), 100332/1957120 blocks
localhost block # e2fsck /dev/block/mmcblk0p1
e2fsck 1.41.12 (17-May-2010)
chroot-drive: clean, 8180/489600 files, 100332/1957120 blocks

After doing this once, the Android system checked the SD card again at the next reboot, and added the following mounts to the /proc/mounts table after each subsequent reboot:

/dev/block/vold/179:1 on /mnt/sdcard type ext4 (rw,dirsync,nosuid,nodev,noexec,relatime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/vold/179:1 on /mnt/secure/asec type ext4 (rw,dirsync,nosuid,nodev,noexec,relatime,barrier=1,data=ordered,noauto_da_alloc)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)

Then I set up a script to log into the chroot environment:

This worked fine, but when running inside the chroot environment the apt-get and apt-key commands didn’t work, because the Domain Name Servers were not specified. (Note: The mount command in the for loop probably also needs some work, as it will mount things multiple times when I leave and reenter the chroot environment.)

I edited the /etc/resolv.conf file and pointed it to Google’s nameservers:

The sources.list file uses, which might be because the other archive servers don’t have armhf packages to offer. It wasn’t quite clear to me how Ubuntu manages their ports across the various versions.

Once the APT source has been added, apt-get update and apt-get install will work fine. It’s a blank slate from there.


For the initial downloads, the following setting can be placed in the APT configuration folder to manually specify an APT package proxy, which might speed up installations:

# vi /mnt/sdcard/etc/apt/apt.conf.d/30proxy
Acquire::http { Proxy ""; };

If the proxy address never changes, you can just leave it at that. If the address does change, you’ll probably want to install the squid-deb-proxy-client package.


1. ChrootOnAndroid
2. How to install Ubuntu 13.04 on your Android phone
3. DebootstrapChroot
4. Raspbian Benchmarking – armel vs armhf
5. Installation mit debootstrap
6. Index of /dists/saucy/main
7. Best way to cache apt downloads on a LAN?