Month: February 2014

How to launch AVD from Eclipse in Fedora 19

Image Posted on Updated on

In the previous blog post I had shown HOW TO Setup Android Development in Fedora 19
and I will assume you will have a AVD ready.

Now how to launch this from eclipse (which will be helpful while production codes for apps).

1. Start your eclipse (installed in the earlier blog), and see if you can find the two icons marked in Red below.


if these are present then you don’t have to worry about anything, if not follow the below mentioned steps.

2. Click Window>>Customize Perspective.


In the Toolbar visiblity select AndroidSDK and AVD Manager.

you are done.

Now AVDs are very slow, unless you have super fast computer with best(est) configuration [see this discussion] But if possess a android phone, you can test the apps on it.

For more information read this post. Testing apps on phone instead of AVD



HOW TO Setup Android Development in Fedora 19

Posted on Updated on


Before heading towards Android SDK you must have few dependencies installed such as:
Java development kit (JDK) and Eclipse IDE.

Install JDK:

$sudo yum install java-1.7.0-openjdk-devel

Install Eclipse IDE:

$sudo yum install eclipse-jdt

For Android SDK :

Download SDK from page –
In the linux section download SDK tools for 32 and 64 bit version of linux.
Go to the downloads directory of your system

$cd Downloads

Unpack it in your home directory, then rename it to ~/AndroidSDK

Add into path environment variable ~/AndroidSDK in .bash_profile file in your home directory.

$sudo vim .bash_profile

export PATH

# For SDK version r_08 and higher, also add this for adb:
export PATH

you need to logout and login again to make the changes but if you are too lazy to do the former, here is what you can try:

$export PATH=PATH:$HOME/AndroidSDK:$HOME/AndroidSDK/tools

This will help you to access AndroidSDK from anywhere in your system directory.

Android Emulator
For 32 bit machines:

$yum install glibc.i686 glibc-devel.i686 libstdc++.i686 zlib-devel.i686 ncurses-devel.i686 libX11-devel.i686 libXrender.i686 libXrandr.i686

If you possess a 64-bit system, follow the instruction mentioned here ( )

Install ADT plugin for Eclipse (the following steps are for eclipse 4.3 and above)

Start Eclipse, then select Help > Install new software…

  1. Click on the Available Software sites under “ADD” option.

  2. In Preferences window, click Add….

  3. In the Add dialog box that appears, enter a name for the site (for ex: “Eclipse Update”) in the “Name” field. In the Location field, enter one of these URLs, depending on your version of Eclipse.For Eclipse version 4.3 (Fedora 19 (as of Jun. 5, 2013) ), use:

If you’re unsure which version of Eclipse you are using, check it at Help > About Eclipse.

This will add dependency which are required for ADT plugin.

4. Again click on Add button and add a name for another remote site (for ex, “Android Plugin”) in the “Name”. In the “Location”, enter this URL:

If you have trouble acquiring the plugin, you can use “http” in the URL, instead of “https” (https is preferred for security reasons). Then Click OK.

5. Click on each of the added sites and click Reload

6. Back in the Available Software view, next to “Work with:”, you should now in see in drop down list “Android Plugin”, select it and in box below see “Developer Tools” added to the list. Select the checkbox next to Developer Tools, which will automatically select the nested tools Android DDMS and Android Development Tools. Click Next.

7. In the resulting Install Details dialog, the Android DDMS and Android Development Tools features are listed. Click Next to read and accept the license agreement and install any dependencies, then click Finish.

Restart Eclipse.

Configure Android in Eclipse

  1. Go to Window -> Preferences, click on Android and set SDK location to directory. (for example /home/user/AndroidSDK) and click on Apply.
  2. Click on apply to reload available targets
  3. choose target android SDK
  4. click on OK

AVD device

$cd ~/AndroidSDK


this will launch Android SDK Manager

1. To configure and create your first Android Virtual Device.


2. Go to “Packages”, select components for just those versions of Android you want to work with. For example:

  • SDK Platform Android 2.3/4.1
  • Documentation for Android SDK
  • (SDK version r_08) For the adb tool, make sure you also select:
  • Platform Tools

3. Click on “Install packages”, then click on “accept all” and confirm with clicking on “Install”. This will start component installation, when it will be done, click on close. When this will be done, we could proceed with creation of AVD device itself.

4. Go to “tools>>manage AVDs”, Click on “New”, this will open screen. (I already have some AVDs installed previously, ignore that)


5. here you need to specify SD card size (I will use 100MiB), name of device (I will use “android_dev”, target (Android 2.3/4.4). If you want to work with different targets, you will have to repeat Step 1. and install appropriate versions.


6. Add appropriate settings for RAM, internal storage. Typical will be: Ram – 512, internal – 100. Click OK. This will create a AVD for you, you can test your production apps.

In the post I will show how to start the AVD (that you created above) from Eclipse IDE (also installed above). Also I add details as how to test your development apps on a real Android device.

Reference fedora

Project bus-routes-3

Image Posted on Updated on

work on web app is in progress, I have replaced the drop-down menu with jQuery auto-complete widget. The result:

  • the home page loads in quickly also searching is lot simpler now. Just type the respective stop name and the auto-complete function will find it for you.
  • The api call is also reduced which has contributed to the speed.

Now I will be working on other functionality, such as in this window


the bus number will be clickable, which will in turn show all the details associated with it. Also on the home page


I will add few more options in the navbar and probably take care of the alignment of the elements.

Also by tomorrow I have to start working on the mobile aspect of the site.