First off, you need a system where you can download the android sources from the web and compile. There are several platforms which are supported for the build process – Ubuntu 32 bit, 64bit and Mac OS X. My personal view being 32 bit OS is the best as it requires least modifications. If you have a ubuntu box sitting around you can start-off right away. If not, I suggest using a virtual machine instead of installing an OS. You can install the free vmware player from vmware and use a prebuilt ubuntu 32 bit virtual appliance for compiling Android. Either way, apply all pending security and software updates before setting up the Android development tool chain.

Your starting point for android system development is Android source website. Follow the instructions there to the dot. The “repo sync” or download process should take less than a hour if you are on a good broadband connection. The “make” will take nearly 3 hours on a raw metal machine. On a virtual machine based ubuntu system it might take more time. The compilation will produce 4 img files – boot, userdata, ramdisk, and recovery.

Now, before you flash the binary img files you need to take care of few more details. Follow the dream aka dev phone 1 instructions as we are compiling for the google dev phone 1. In step 5, you may get a error. This is just a path issue. Setup your path and you should be fine. Once you run the repo sync & make again, it will get some updates from the web and build the img files suitable for the dev phone.

Google website doesn’t tell you how to get the img files into the developer phone. You need to use two tools ‘fastboot’ and ‘adb’ to get the images into the phones. They are located in the folder “out/target/product/dream/” relative to the code branch you checked out – either main or cupcake. Add that directory to the path variable. Connect dev phone 1 to the PC and verify through ‘abd devices’ from the terminal. Adb will start a daemon on first run. Some users have reported that they problems identifying the devices. This seems to be mainly the case if you are using a VM. If this is the case, ’sudo’ all your commands. Once you have verified the device is identified by adb, next boot the phone into fastboot mode. For this, switch off your phone and then press and hold both the poweroff+back until you see the 3 Androids on skates and the words “fastboot” in the middle of the screen. Now issue “fastboot devices”. You should be able to see your phone and it should say it is in fastboot model. At this stage, you need to issue the following commands

fastboot flash boot boot.img

fastboot flash userdata userdata.img

fastboot flash system system.img

and finally fastboot reboot and you are done getting a new OS on the phone

ps: feel free to drop a comment or question

Here is my experience building libjingle** in my Ubuntu Linux 5.10. I spent nearly a day building it (including many u-turns). I am writing this how-to in the hope you will spend much less time. YMMV.

Contents:

1. Hardware tried on
2. Installation
   1. Download
   2. Installing dependencies using
      1. Synaptic package manager
      2. Direct compilation
3. Installing lilbjingle
4. Future Goodies

I am using Ubuntu 5.10 with all updates as of this day of posting. I have installed libjingle in the following hardware.
* Fujitsu lifebook S7021
* DELL Precision 670
* Assembled PIV system

First, Install the following packages using Synaptic Package Manager.
* libexpat1-dev
* libglib2.0-dev
* libogg-dev
* libssl-dev
* libasound2-dev

If some configure script later-on is unhappy with the env, installing the following may help. These are few of the u-turns I experimented with. These are not required per se.
* libspeex-dev
* openssl

Dowload the following external packages:
* ortp, speex, iLBC, libjingle

I have created a parent folder “libjingle” and downloaded the packges there.
Now CD to that folder and do the following instructions:

tar zxvf ortp-0.7.1.tar.gz
tar zxvf speex-1.0.5.tar.gz
tar zxvf ilbc-rfc3951.tar.gz
tar zxvf libjingle-0.2.1.tar.gz

cd ortp-0.7.1
./configure
make
sudo make install
cd ..

cd speex-1.0.5
./configure
make
sudo make install
cd ..

cd ilbc-rfc3951
./configure
make
sudo make install
cd ..

cd libjingle-0.2.1
./configure –with-ilbc=/usr/local
make
sudo make install

That’s it, your libjingle library is now inside the talk folder. Enjoy.
There are 3 examples included in the package. I am yet to try out.

Future Goodies:

I have proposed using libjingle for my Real-Time Systems course module project in NUS, Singapore where I am doing my part-time PhD in Computer Science. The Professor instantly accepted it with an additional “Wow” factor.

We believe we have come-up with an innovate RTS application using Google’s Talk infrastructure. Once we bring it to realiy, which is scheduled for completion by end March 2006, we will release it the community including code. My motto: take from community; give back to community.

** libjingle is an implementation of proposed jingle and jingle-audio extensions to XMPP (an IM) protocol.