Best to run Android SDK as same user you run Eclipse since your AVD are stored in your home directory
Once you get your eclipse and Android SDK development environment going, add a new Motorola Xoom Android Virtual Machine (AVD) to your SDK and start coding.
On-click-root http://androidcommunity.com/motorola-xoom-root-the-easy-way-with-1-click-root-and-overclock-guide-20110331/
Chroot is not required when using [[multilib]]. But this is a nice tutorial on chroot, move to own topic sometime
Unfortunately several parts of the Android SDK do not run properly on 64bit linux. One such part is the mksdcard script used in the Virtual Devices section of the Android GUI, so building Virtual Devices doesn't work, and who knows what else.
So to start developing for android in archlinux 64bit, you must first install the 32 bit libraries. In ubuntu this is a piece of cake, just apt-get install lib32 or something like that. In arch linux its a bit harder. I have taken most of this 32bit guide from https://wiki.archlinux.org/index.php/Install_bundled_32-bit_system_in_Arch64 and I have also contributed back to that wiki. This is a quick and dirty version of that wiki thats geared toward getting the Android SDK running.
Note, this entire section is done as root, and you must chroot into your new /opt/arch32 using root also, chroot does not allow chrooting by a non-root user
#!/bin/bash . /etc/rc.conf . /etc/rc.d/functions dirs=(/dev /dev/pts /dev/shm /tmp /home) case $1 in start) stat_busy "Starting Arch32 chroot" for d in "${dirs[@]}"; do mount -o bind $d /opt/arch32/$d done mount -t proc none /opt/arch32/proc mount -t sysfs none /opt/arch32/sys add_daemon arch32 stat_done ;; stop) stat_busy "Stopping Arch32 chroot" for (( i = ${#dirs[@]} - 1; i >= 0; i-- )); do umount "/opt/arch32${dirs[i]}" done umount /opt/arch32/{proc,sys} rm_daemon arch32 stat_done ;; restart) $0 stop sleep 1 $0 start ;; *) echo "usage: $0 {start|stop|restart}" esac exit 0
cd /opt/arch32/etc ln -f /etc/passwd* . ln -f /etc/shadow* . ln -f /etc/group* . ln -f /etc/sudoers . # note: you'll need to install sudo before creating this entry, or sudo will refuse to install ln -f /etc/rc.conf . ln -f /etc/resolv.conf . ln -f /etc/localtime . ln -f /etc/locale.gen . ln -f /etc/profile.d/locale.sh profile.d cp /etc/vimrc . cp /etc/mtab .
Every command from here on out is after the above chroot /opt/arch32, meaning you are now chrooted into your new 32bit system, not your regular 64bit system
Oh and be sure, when installing things with pacman inside your chroot, that all packages say .i686 as they go flying by, if you see x86_64 on any package, you missed something.
Now that you have a 32bit chroot environment on your 64bit ArchLinux installation, you can install jdk, eclipse and the Android SDK as usual, But you must be inside your chroot. Don't install these packages on your regular 64bit environment, they (Android SDK) won't work.
To install these packages in 32bit, from your standard 64bit system, run as root: chroot /opt/arch32, then follow the ArchLinux Android instrutions below! You won't have to use sudo in the commands below, because your in your chroot as root anyway.