This is just a collection of useful information and tricks that I used during the time I was developing on the android ADP1. In some cases the information might be a little old and new and easier ways to do the same things might be available. Please let me know if you find something like this so that, I can update this document. This is not original work and neither do I claim so. This is just a collection of references that you may find useful. This is in no way a definitive guide and there is much more information out there.
Part 1: Activating your android ADP 1 without the sim card
- Plug your Android Dev Phone into your computer via USB if you are using windows 64 bit as your OS you will need additional instructions about the driver*.
- Get into the Phone’s OS… Open up a terminal and type:
adb -d shell
- Now, change to the Phone’s settings database directory, type:
- Give yourself admin permissions by typing:
- Now, you are going to use sqlite to alter the phone setting database, and turn provisioning on, so type:
- Use this SQL command to alter the settings database:
INSERT INTO system (name, value) VALUES (‘device_provisioned’, 1);
- Now, exit sqlite by typing this (don’t forget the “.”): .quit
- Reboot the Phone by typing: reboot
- When the phone reboots, you need to open up the settings screen to activate your WiFi settings.
- First, get back into the Phone’s OS by typing: adb shell
- Now, run this command to open up the settings screen on the Phone, which will allow you to turn on WiFi:
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
*Windows Vista 64 bit Driver Issue:
At the time of writing this document windows vista 64 bit did not have a driver for android platform, so there is an unsigned driver that is available for the phone. However the issue with windows Vista is that it won’t allow you to install unsigned drivers without some hacks. ( I have attached the driver in the tar file
- Type “bcdedit /set testsigning on” at an admin command prompt
- Check to see if the desktop says “Test Mode” on the corners after reboot.
- Install the given driver now.
Part 2: Installing the Developing Environment
Once you have installed the android phone and looked around in the interface and checked out the command prompt emulator installed skype to make free calls over wifi and got the hang of the device, its time to get down to serious business.
The android development environment is basically a Stripped down version of J2ME environment.
2.1 Installing Android SDK:
1. Download Eclipse(3.4) from :
2. Install Jdk6 preferably if you don’t have it already installed.
3. Download the Android SDK for your eclipse version and OS from
4. Installing the ADT Plugin for Eclipse
Android offers a custom plugin for the Eclipse IDE, called Android Development Tools (ADT), that is designed to give you a powerful, integrated environment in which to build Android applications. It extends the capabilites of Eclipse to let you quickly set up new Android projects, create an application UI, add components based on the Android Framework API, and debug using the Android SDK tools.
Eclipse 3.4 (Ganymede)
- Start Eclipse, then select Help > Software Updates….
- In the dialog that appears, click the Available Software tab.
- Click Add Site…
- Enter this as the Location:
Alternatively, you can use http in the Location URL, if you are having trouble with https
- Back in the Available Software view, you should see the plugin. Select the checkbox next to Developer Tools and click Install…
- On the subsequent Install window, “Android Developer Tools”, and “Android Editors” should both be checked. The Android Editors feature is optional, but recommended. If you choose to install it, you need the WST plugin mentioned earlier in this page. Click Next.
- Accept the license agreement and click Finish.
Now, you just need to modify your Eclipse preferences to point to the Android SDK directory:
- Select Window > Preferences… to open the Preferences panel. (Mac OS X: Eclipse > Preferences)
- Select Android from the left panel.
- For the SDK Location in the main panel, click Browse… and locate the SDK directory.
- Click Apply, and then OK.
- Hello World for Android: Go through the helloworld(s) give on this page to get a feel of the developing environment.
- Go through
Part 3: Updating your Android phone to the latest Firmware
Please go through the useful ADB Commands before you move any further: http://developer.android.com/guide/developing/tools/adb.html
Flashing the phone:
The ADP1 phones given in class need to be updated first before you could try and work with them, I found this out because some of the code that I wrote was working on the simulator but not on the phone, hence the flashing.
It is also necessary to flash the phone in order to run Android Scripting Environment.
This is a long process and the best post I could find on this was:
Please go through all steps carefully.
Part 4: APIs and links to code reference and sample code for accessing onboard Hard
Hardware Device API CLASS Reference Links GPS android.location http://developer.android.com/reference/android/location/LocationManager.html
GSM Telephony android.telephony http://developer.android.com/reference/android/telephony/package-summary.html
Listen to incoming SMS Application
Get notification about incoming calls
Access Cell Details such as cell id, signal strength etc
Wifi android.net.wifi http://developer.android.com/reference/android/net/wifi/package-summary.html
Wifi Social Networking using maps and wifi
XML Parsing android.sax http://developer.android.com/reference/android/sax/package-descr.html Sensors: Get information about the sensors present on the device. Sensor http://developer.android.com/reference/android/hardware/Sensor.html Accelerometer, Compass SensorManager http://developer.android.com/reference/android/hardware/SensorManager.html Camera android.hardware http://developer.android.com/reference/android/hardware/package-summary.html
Part 5: Scripting on Android
Android Scripting allows development of applications on the phone itself, without the need to be tied to a computer. ASE or android scripting environment allows you to edit and execute scripts and interactive interpreters directly on the Android device.
Languages supported currently:
Python, Lua, Perl, Jruby, Beanshell.
You can download ASE on the phone from:
Install it as an apk package on the phone:
adb install <source>/AndroidScriptingEnvironment-0.11-alpha.apk /<destination>
Open application & select your favorite interpreter and you will get a few sample scripts you can use these scripts and create your own script, either directly in the phone or on a computer on your favourite IDE and use adb push to push the script to the phone.
adb push myscript.py /sdcard/ase/scripts/myscript.py
For details on scripting you can visit the following links:
Part 6: Compiling and Installing Linux Binaries for Android
Note: Your Development Environment for this should be Linux to setup the tool chain compiler
I have had some success with the process given at
apt-get install emdebian-tools
emsetup –arch armel
To compile simple static applications:
arm-linux-gnueabi-gcc -static -o myapp myapp.c
So the limitation here is that the application is statically linked. A nicer setup would give us dynamically linked applications. One of the trickier aspects here is that Android uses a custom, tiny libc, (bionic). Here are some instructions on getting a working setup for compiling a dynamically-linked program with the prebuilt Android toolchain. Perhaps someone can use these instructions to create a simpler process using the emdebian toolchain.
To get the Android prebuilt toolchain:
1. First download the Android source.
2. That ships with a prebuilt toolchain with a compiler named something like arm-eabi-gcc . It’s convenient to get that onto your PATH with something like the following (assuming Android source in $HOME/src/android):
3. Next you’ll actually need to compile at least the bionic libc. Without having gone through the effort of doing a minimal compile here, you can do just “make” and wait quite a while for all of Android to get compiled. Note that early on the Makefile will abort if it can’t find a JDK that it likes. Presumably no Java is actually needed for the native compilation we’re doing here, but again, without having wrestled that out of the Makefiles yet, you can satisfy that requirement with packages from Debian’s main repository:
apt-get install openjdk-6-jdk
4. Next, there are various flags and things needed to cross-compile an application and properly link it to bionic. Andrew Ross has written a perl script to take the pain away here and with the android toolchain in your PATH you’re ready to go. Grab his agcc script and put it into your PATH somewhere, (perhaps in $HOME/bin or so).
5. With all those steps done you can now cross-compile an application dynamically linked to bionic
agcc -o myapp myapp.c
Agcc perl wrapper can be found at:
You can then push myapp using adb on to the android device,
I used it to port and run iptables on android, however this was not very stable when I did it maybe this can be improved upon.