Welcome to Our Eclipse/Android Studio Website!

Trying to get some 'Proper' Documentation on Eclipse. Setup and Using. Yes there is stuff all over the Web -but- I am having a hard time finding what I want. So, I will document it here and then I won't have to look all over. IF anyone else is looking maybe this will help them.

I became the 'OP' for the HTC ReZound, a Smartphone. This "Modified Documentation" is primarily for use on the ReZound code.

 November 14th, 2017   However, as of this day, it will be changed to concentrating on my 'New' (1½ year old) HTC M10. I like the 'M' in the name. They were gonna call it that but changed their minds. However, NOT before they put the M10 name deep inside the build.prop file inside the  ROM  code:  ro.product.name=HTCOneM10vzw 
And please notice that the date is almost two years later than the one that follows. My 'Puppy' became a little more than I could handle. I still got him, and wouldn't part with him for a million dollars. Just now he is maturing and I am getting a little more time.

 June 23, 2015/5:40pm   Now then, this is going to get interesting. I'm trying to get back into my
Android Programming and building AFTER all this time off to take care of my new Puppy. Dakotah is now 17½ weeks old and a 'little' more reserved. We still have our moments -and- IF you own a dog, especially a Puppy, then you know that they require time... lot's of yours... annnndddd... already I am getting interrupted!!

Now then, the interesting part, besides the Puppy is... I have Android Studio setup on my newest PC -and- I have my Web Pages on my oldest PC. But becuase I have a KVM (Keyboard/Video/Mouse) switch between the old and the new, I can not edit these Web Pages on the old whilst on the new. Therefore, I am editing the Web Pages on the old via the Laptop. So, I have all three of my 'puters in use at the same time... Proud?? Yep!!

 June 17th, 2016/9:04pm  OK... another new computer. Just finished setting up  Android Studio  on it. Still have the dog and he is now 15½ mos old -and- still requires more attention than I expected -but- he is fun... most of the time. I got this newest one on Feb 24th, 2016 and it has taken me this long to get things setup. Dog and work and just getting everything needed... and remembering!!


  My Android Studio 3.x Docs

We are trying again. It has been so long that all the stuff I have is obsolete. I gots version  1.0.1  and the  Studio  is up to  3.0  and starting  3.1 Beta !! As usual, I am going to leave the stuff further down that is for  Android Studio 1 , both for reference and nostalgia. And there might be something benificial. I don't know, it's only been two years!! And besides... it took some time to research and create it.

Refer:  Android Studio 3.0 Development Essentials - Android 8 Edition Book  
   and  Create an Android Project  

Now then, as I mentioned, I have the first version of the above book. Only reason I don't have this one is cause they evidentially don't have it in print yet!! They have the 'e-book', which I will get -but- you can get it for free IF you purchase the book. Otherwise it is $24.99. So I am using the 'second' reference to get started and I will wait until they 'officially' publish the book.(I like the cover)
 November 20th, 2017  Finlly got it ordered and got the PDF version for 'free'. All I had to do was show proof that I ordered the Print Version... from Amazon

 Remove a Project  

  1. First close the project
  2. On the Welcome Screen, move the mouse cursor over the hi-lighted project and press the keyboard DEL key, Viola, it is gone.
  3. Go to folder: "AndroidStudioProjects"
  4. Then delete project folder that you don't want
  5. Reopen the android studio.
Why is this here??? Cause I played with it before I knew what I was doing, and before I got the new book, and I wanted to start over.


  My Android Studio 1.x Docs

I have tried, sporatically and ineffectively, to use Eclipse as an IDE for my Android Development. Now I am switching to Android Studio. They(Google) have completed a lot more -and- they have incorporated the use of the NDK... which was missing... well, according to what I just read on the Web, it technically still is. But, so far, there have been no complaints. (March 22nd, 2015) At least not from the code I have been working with so far. In fact, some of this, NO, most of this was/is copied from the Web. The 'main changes' I have made are ... making all this, more or less, HTC ReZound specific.

 March 25th, 2015 / 1:30pm  Ok, I'm bad, I'm bad... Started writing this up -AND- I already have most of it installed. So, when I go to the references, they point out some of the steps that I have already performed. IF some of my steps look out of place... that's cause they probably are. Like I have said a gazillion times... these WebPages are for meself more than anything. IF you can benefit from them ... then GREAT!!

  Some Install Steps  

 Cyanogen on our System   In order to work with the code, we need to install it on "our system". This is accomplished via the following commands:
$ md ~/Android
$ cd ~/Android
$ md cm11.0-rezound
$ cd cm11.0-rezound

The following is an exact copy of the script that I use to get my intial setup. NO, I did not write it. I wasn't that smart, in the beginning. One of my "Team Mates" wrote it.

# Notes have been added by me cause... I don't remember things well anymore.
# -And- as it turned out... helped with this writeup.

# Is there a .repo dir?? IF not create one.
# Then put it on top of the stack. ie; cd into it.
[ -d .repo ] || mkdir .repo
pushd .repo

# Is there a local_manifests dir in .repo??  IF not create one.
# Then put it on top of the stack. ie; cd into it
[ -d local_manifests ] || mkdir local_manifests
pushd local_manifests

# If there is a local_manifest.xml, remove it.
# Get the latest one from github.. rename it and cd back to the root
# with the 'popd' commands.
rm -f local_manifest.xml
wget https://raw.github.com/vigor/android/cm-11.0/local_manifests/local_manifest_hybrid.xml
mv local_manifest_hybrid.xml local_manifest.xml

# To initialize your local repository using the CyanogenMod tree
#  -u: specify a URL from which to retrieve a manifest repository.
#  -b: specify a revision, i.e., a particular manifest-branch.
repo init -u https://github.com/CyanogenMod/android.git -b cm-11.0

# Theoretically a stable version versus the "Bleeding Edge" version.
# repo init -u https://github.com/CyanogenMod/android.git -b stable/cm-11.0

# Now cd into .repo. Edit manifest file. Remove sync-c="true"
pushd .repo
    sed -i "s/sync-c=\"true\"//g" manifest.xml

# Now get the code tree...
repo sync -j8

# Get the vendor specific stuff...
pushd vendor/cm
"repo help manifest" is the command to get more info on the manifest file.
And of course there is documentation in: ".repo/repo/docs/manifest-format.txt"
Thanks to  StackOverflow  

Now, as root, we check our 32-bit libs: ( ia32-libs in openSuSE 13.2 )

 # zypper install -t pattern 32bit
Loading repository data...
Reading installed packages...
'pattern:32bit' is already installed.
No update candidate for '32bit-20141007-5.1.x86_64'. The highest available version is already installed.
Resolving package dependencies...

Nothing to do.

 June 17th, 2016/9:16pm  Ok... on the newest machine we got the same results.

 Android Studio Install  Android Studio, is an IntelliJ IDEA-based Android development environment.
Download from  Here   either to the dir you are going to put it in -or- a temporary one. The extraction process will let you pick where you want it. I bring things down to my Download dir and then do the extraction to the real place.
Now then, I am not only being specific to the ReZ but also to openSuSE 13.2. Using Dolphin, go to the Download dir and click on android-studio-ide-135.1740770-linux.zip -or- whatever version you got. It will expand and show its contents. Along the top are some commands. One of them is 'Extract'. Click on it and you will be presented with your directory structure. Default is where you are. IF you want to place it somewhere else, move to it by clicking on the dirs presented. UNLESS you change it, it will create a default "android-studio" dir where ever you click. I chose my 'home' dir. When you are finished execute these commands --- making changes where appropriate. The dirs.
$ cd ~/android-studio/bin
$ ./studio.sh

On the first execution of this command, it will finish the install and setup. Thereafter, it will startup the Studio.

 Resolve SDK not included in Studio  


  End Install Steps  

Is Android Studio a fork of IntelliJ IDEA?
No. Android Studio and the Android plugin for IntelliJ IDEA are built from the same code, and all of the changes in Android Studio are, and will continue to be, available in IntelliJ IDEA releases.
 IntelliJ IDEA and Android Studio FAQ  

Development Information
 Android Studio for Beginners: Part 1    Part 2    Part 3  
   Setting up Intellij with CyanogenMod/AOSP development  
 Develop AOSP on Android Studio: Part 1    Part 2    Part 3  
 Tips of the Day  <- On GitHub      Theme Manager    Simple Theme Guide  
  *   *   *  NDK support deprecated for Android Studio 1.1.0   *   *   *
 Android Studio Overview    Using Eclipse  

Does Android Studio have a Heirarchy Viewer?
  DDMS, Hierarchy Viewer, openGL Tracer etc all moved into Android Device Monitor. To access:

  1. In Android Studio(the app)  on menu Bar Select: Tools > Android > Android Device Monitor
  2. In ADM: Window > Perspective
  3. Click on Hierarchy Viewer.
  From:  StackOverflow   and  Developer Phil  

Setting Up for CyanogenMod Development
Before starting, I'm sure that you must understand that the computer/PC you are going to use should be fairly powerful -and- have a substantial amount of RAM and HDD space available... the more the merrier.
You first need to make sure that your IDE has lots of RAM allocated to it.
Change ../android-studio/bin/studio.vmoptions & ../android-studio/bin/studio64.vmoptions
Those values are in BOTH files.
Next, you need to open up idea.properties and change idea.max.intellisense.filesize to something like '5000' or more. If we don't do this IntelliJ won't parse some R.java files generated.
Note: these files are located in the ~/android-studio/bin/

Now we go to our android root directory. The android root directory is ~/Android/cm11.0-rezound.

$ cd ~/Android/cm11.0-rezound

Need to execute "build/envsetup.sh". After it is setup execute 'hmm' from the command line to see what it did and what you have available. Since we are working on the ReZound it might be to our advantage to also execute: "lunch cm_vigor-userdebug" So the source knows which device to attempt building a boot for. Not totally sure that last item is needed for this part -but- it is needed if/when you build a "BootImage".

From the the Android root dir:

$ . build/envsetup.sh
$ lunch cm_vigor-userdebug
> . build/envsetup.sh 
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/goldfish/vendorsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/htc/vigor/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/bash_completion/git.bash
including vendor/cm/bash_completion/repo.bash
> lunch cm_vigor-userdebug
Trying dependencies-only mode on a non-existing device tree?

Now Compile the idegen tools:

$ cd development/tools/idegen
$ mm

Well... all did not go well:
       warning: [options] bootstrap class path not set in conjunction with -source 1.5    
Now we have to find out what that means!!

Well, we did: (click on error message above for full description)

This warning is emitted if you are using JDK 7 Build 121 or later (earlier versions of the compiler would not issue a warning).

It is warning you that your Java compiler version and the version of Java you are compiling for are different. For example, you may have version 7 of the compiler installed, but are choosing to compile for Java version 5.0. While the compiler is capable of emitting code for different versions, it needs to use the correct startup libraries (bootstrap) in order to guarantee it will function correctly.

Well, it is only a Warning and it is because we have 'old' code in here -and- I'm not gona re-write the whole thing. It happens to be mostly in Java. In fact everything except the kernel is in Java. So, we will just continue for now. Your Java version: Version 7 Update 71

Go back to the root directory and run the tool:

$ cd ~/Android/cm11.0-rezound
$ development/tools/idegen/idegen.sh
Read excludes: 44ms
Traversed tree: 101073ms

Looks like it just read the whole 'Cyanogen Tree'.

 April 16th, 2015 / 5:31pm  Files created by the above:

 April 29th, 2015  Received my copy of "Android Studio Development Essentials" that I had ordered. I got both the printed and e-book PDF forms.

 June 18th, 2016/5:52pm   Well, we have gotten this far with the Newest HP i7-2 Machine. Have installed and fired up the  Studio .

    Now We Use It

 May 11th, 2015 / 3:54am  I have been interrupted on this so many times it isn't even funny. Interruptions have been for tons of reasons and my latest is, Dakotah. He is my new Husky/Shepherd puppy and I had forgotten how much time and attention a new puppy requires. We are going to get the carpets thoroughly cleaned -OR- maybe even replaced AFTER he is house broken. Those "Training Pads" only half work. -BUT- in their defense they do help. Annndd... not to put all the blame on the new puppy, I also got a part time job at McDonalds. Which has been more hours than I expected. There are others -but- those are the two main ones.

I had this all setup and then destroyed it and I don't remember why NOR do I remeber what I did to get it to work. Reason for book purchase. I have my CM11 as the only project, at this time, but when I click on it I get a message about missing files. The ones listed above (April 16th) were the first ones listed and now after executing the idegen they are not complained about any more. New complaint;
        "Cannot load /home/ctaylor/Android/cm11.0-rezound/.idea. The file does not exist."
annnddd... I have no 'idea' how it gets created!! Guess I'll read my new book!! Well, that was a disappointment. Nothing in the book on this file!!
However, I did find an answer on the Net. I had to RE-import my project.  Could not open project  

-BUT- (that word again) the folders were not listed like they were the last time. I stumbled through this the first time and got something that looked useable. Now following all the directions... it doesn't!! So... we will start again.

 Remove a Project   First close the project, then move the mouse cursor over the hi-lighted project and press the keyboard DEL key.    Viola, it is gone.  May 31st  Starting again and it looks like the project is still gone, so I guess I removed it.

 June 18th, 2016/6:02pm   Starting again... almost. I copied over the dir/project from the previous HP i7-1. It works and I got a successful compile. Just need to get all the stuff for this Studio set up on the New HP i7-2

 May 16th, 2015 / 5:05am | May 31st  First thing we are gona do is ruin the whole mess. Updates!!! It is claiming multiple times that there are some updates.
OK. I let it do the updates and it removed a PDF that I had in the dir plus a .directory file. It is only allowing what it wants to allow. Then AFTER the UpDate was finished it claimed there were more UpDates!! So, what the heck, we did these UpDates too!
 May 31st  , checking UpDates again. It replied that I have the latest Android Studio installed.
Allllrighty now... we got a clean Welcome window.
 May 31st  Had problems getting the Android Studio png icon to show up on my Desktop when I linked the app to it. Had to finally use the ico icon.

 Import Eclipse  Like we did in our first stumblings, we are trying to import our Eclipse project. It said that the .idea project already existed and asked IF we wanted to replace it. We said yes. It 'fastly' went through all the dirs... then it listed them. We clicked on Next and it said: 6:34am Searching for libraries. 2-3min Please wait. then it changed to: 6:36am Searching for modules. Please wait. Took a long time but finally finished. Got a couple more screens -but- I forgot to write them down here and now I forgot what they were. One of them listed all my dirs and files. I clicked on OK -or- Next to accept them.

 June 18th, 2016/6:13pm   Did NOT import Eclipse this time. I imported the one from the previous machine. Which was imported from Eclipse so, I guess round aboutly I did it again.

6:15:40 PM Migrate Project to Gradle?
           This project does not use the Gradle build system. We recommend that you migrate to using the Gradle build system.
           More Information about migrating to Gradle
           Don't show this message again.
6:15:47 PM Unregistered VCS roots detected
           The following directories are roots of VCS repositories, but they are not registered in the Settings: 
		      ---  ---   --- more files ---
           /home/ctaylor/An... (show balloon)
6:18:02 PM Frameworks detected: Android framework is detected in the project Configure

The above is what we ended up with here initially. Gona check out that Gradle first. And I did. Gradle is recommended over IntelliJ cause that is what Google is focusing on and they want you to use. So we will "Migrate" over to Gradle.

  We Have Success...? May 31st thru June 3rd, 2015

 May 31st, 2015  I re-tried Eclipse and was as unsuccessful this time as before. So, once again we are trying Android Studio. Gona see IF I can stumble into a working environment like the last time.

 June 2nd, 2015 / 6:44am  Inconsistent!! My time for this keeps getting interrupted!! In my most recent setup I have "cleaned" up my environment... I hope... and have the proper paths to the proper items. At one place/time they say the SDK is NOT included with Android Studio and then in others they say it is. Well, in my most recent installation, it was/is included. So, I had to fix the PATH so that it would NOT use the 'old' one that I had setup for Eclipse!! Upset??? Yes!! It just shouldn't be this hard!!

 June 2nd, 2015 / 8:47am  Allllllrighty Now...Got it to work!! What?? Android Studio!! Now then, I tried to get everything straight before trying to "Load Up CM11". Then I had to decide on the "Load Up" type. My last "successful" Load Up was a crazy mixed up import of an Eclipse version. Upon looking around I decided to use the one suggested by Cyanogen themselves:  import to intellij   The following is a copy of theirs "modified" to meet our needs.

  1. This part you should have done above. It will create the android.ipr file plus 2 others.
    make idegen && development/tools/idegen/idegen.sh
  2. Open Intellij Android Studio
    1. Click Open an existing Project
    2. Navigate to ~/android/system
    3. Choose android.ipr
    4. Finish

 June 23rd, 2015 / 8:37pm  I decided to test my Android Studio with the test app in my copy of "Android Studio Development Essentials". I had started this once before -but- got interrupted -and- things did not go like the book.

  1. Open Android Studio. The Welcome Screen is ok and the same as book.
  2. Because I had started this once before, parts of it are still there. So it may not mess up like it did the first time... which is what I was trying to document WITHOUT destroying all that I have installed. Just believe, that IF you have a brand new install it will be different.
  3. The Phone and Tablet option is selected. As stated in the book, we will not be dealing with TV or Wearables,so leave them blan or un-checked.
  4. We are going to create a Blank Activity.
  5. Customize the Activity: Name it "AndroidSampleActivity".
  6. After clicking on "Finish" it creates the project.
    Ah, with "Rendering Problems". Must 'UpDate' Android Studio.
    And, naturally, AFTER the UpDate we have "Rendering failed with a known bug.
    Please try a rebuild.
    " We did annndddd....
    Allllllrighty now!!! We have created a minimal example project -AND- I see a Cell Phone image in the Main Project tool window!!! This is the best I have had with anything.
    And naturally my dog is up and needs attention and then I will have to get ready and go to work. -BUT- we have something!!! June 24, 2015 / 3:54am
  7. Now we want to modify the User Interface which is contained in:
    Which as it turns out was what was showing on my screen anyway. A Nexus 4.
    No ReZounds in the selections.
  8. Cool... you can switch between Portait and Landscape mode views.
  9. In this 'Layout' they have the usual 'Hello World'. We are going to change that to larger text and some different wording: 'Welcome to Android Studio'.
  10. Well now, not mentioned in the book. After changing the text and creating the 'new resource' we got an error message about Rendering. Unfortunately, we got it corrected before writing down exactly what the message said. -But- the point is... we got an error. We believe that the error was nothing more than a 'Timming Error'. It was complaing about the 'new message'. A refresh of the screen cleared the error. Prior to the Refresh we had examined the code and stuff ... and the book. Found nothing and just did a Refresh ... because. It cleared the error and showed the Nexus 4 image with the new message. Success!!
  11.  Managing/Creating AVD's   This is in here ... because. Really I would like to create one for the ReZ -but- that will probably be later.
  12.  July 10, 2015/4:03am - Need the Gradle.  We have Migrating from Eclipse and Migrating from IntelliJ -to- Android Studio. The second one is a little strange cause... Android Studio is built from, -or- on, IntelliJ. Now I keep getting this message that my project is NOT a Gradle-based project... do I want to migrate? Well, yes I do -but- all the info is based on 'apps' NOT the 'platform'. Finding this info is a bitch!! Either I just am not using the correct words in my search -or- I am to stupid -or- both.
    The following 'build.gradle' file is a copy of the example at:  Migrating from IntelliJ   -and- modified by me to fit my needs... eventually. Need to figure out/learn what all this means.
    See below this...
    // =====================================================================================
    // build.gradle - Copied/Created july 8th, 2015 - 7:53am
    // =====================================================================================
    buildscript {
        repositories {
        dependencies {
            classpath 'com.android.tools.build:gradle:0.12.+'
    apply plugin: 'android'
    dependencies {
        compile fileTree(dir: 'libs', include: '*.jar')
    android {
        compileSdkVersion 19
        buildToolsVersion '19.1.0'
        sourceSets {
            main {
                manifest.srcFile 'AndroidManifest.xml'
                java.srcDirs = ['src']
                resources.srcDirs = ['src']
                aidl.srcDirs = ['src']
                renderscript.srcDirs = ['src']
                res.srcDirs = ['res']
                assets.srcDirs = ['assets']
            // Move the tests to tests/java, tests/res, etc...
            // Move the build types to build-types/
            // For instance, build-types/debug/java, build-types/debug/AndroidManifest.xml, ...
            // This moves them out of them default location under src//... which would
            // conflict with src/ being used by the main source set.
            // Adding new build types or product flavors should be accompanied
            // by a similar customization.
  13.  Continuing on in the Gradle:  As mentioned, the above build.gradle file was/is and example from the IntelliJ Migrating docs. Now then, the versions ... the versions ... need to have a proper relationship with each other. What?? Well, I found this fact when searching for information on the build.gradle file(s) to be used in CyanogenMod. The gradle version -and- the gradle build tool version MUST have a proper relationship. This is described more at:  StackOverFlow   which is where I first found it. I blindly changed the classpath in the above build.gradle file to make it UpToDate. Then found this.
  14. Again from  StackOverFlow  
          File->Project Structure->Project pane->"Android plugin version".
    Make sure you don't confuse the Gradle version with the Android plugin version. The former is the build system itself, the latter is the plugin to the build system that knows how to build Android projects.
Manufacturer Model Diagonal Generalized size Density bucket Width (px) Height (px) Density Bucket dpi Width (dp) Height (db)
HTC Rezound 4.3 normal xhdpi 720 1280 341.54 320 360 640


 July 7th, 2015/3:57pm  My how time flies.... Allllrighty now we have the Studio installed -AND- working -and- we have loaded up our CM11.


This little section will contain references to WebPages, on which, I have found some kind of interesting information -and- I don't want to loose it. Many times I find something else when I'm searching for something else.
 android-studio-vs-eclipse    Exporting from Eclipse to Android Studio    Google Launches Android Studio  
 IntelliJ IDEA and Android Studio FAQ    JetBrains IntelliJ IDEA Blog     *   Android Tools project site   *
 Boot Animations Change    Android CyanogenMod Diffs      

  Removing Android Studio

These are default locations as of Android Studio 1.0.2 and it is possible to change them by editing ~/android-studio/bin/idea.properties.

  1. Delete the android-studio folder;
  2. Delete the sdk folder if it is in not inside the android-studio directory;
  3. Delete ~/.AndroidStudio, which contains config and system;
  4. Delete ~/.android;
  5. Delete ~/.local/share/applications/jetbrains-android-studio.desktop, if you created a shortcut using Configure->Create Desktop Entry.
  6. Delete ~/AndroidStudioProjects

Refer:  Ask Ubuntu  


  My Eclipse Docs

The following was copied from the Web at:  Installing the Eclipse Plugin   and modified to suit the requirements for my ReZound Operations.

 May 19th, 2015 / 8:38am  At this later date I have found that my suspicions about missing libs are correct. How I found that out was through searching the Web and an 'accidental' find of the "Master' .classpath. I looked -and- there are differences so I decided to bring down the on from the Web and try it. Got different messages and NONE of them were about "Could not resolve type or var". -But- they were all concerned with missing libraries. Now then, is this change cause of the missing libs??? Need to print out each list and compare them.

Installing the Eclipse Plugin

Android offers a custom plugin for the Eclipse IDE, called Android Development Tools (ADT). This plugin provides a powerful, integrated environment in which to develop Android apps. It extends the capabilities of Eclipse to let you quickly set up new Android projects, build an app UI, debug your app, and export signed (or unsigned) app packages (APKs) for distribution.

Note: If you have been using Eclipse with ADT, be aware that Android Studio is now the official IDE for Android, so you should migrate to Android Studio to receive all the latest IDE updates. For help moving projects, see Migrating to Android Studio.

You should install the ADT plugin only if you already have an Eclipse installation that you want to continue using. Your existing Eclipse installation must meet these requirements:

  • Eclipse 3.7.2 (Indigo) or greater (we have Luna 4.4.4 installed)

    Note: Eclipse 3.6 (Helios) is no longer supported with the latest version of ADT.

  • Eclipse JDT plugin (included in most Eclipse IDE packages)
  • JDK 6 (JRE alone is not sufficient) (we have JDK 7)
  • Not compatible with GNU Compiler for Java (gcj)(Using normal GCC)

Download the ADT Plugin

To add the ADT plugin to Eclipse:

  1. Start Eclipse, then select Help > Install New Software.
  2. Click Add, in the top-right corner.
  3. In the Add Repository dialog that appears, enter "ADT Plugin" for the Name and the following URL for the Location:

    Note: The Android Developer Tools update site requires a secure connection. Make sure the update site URL you enter starts with HTTPS.

  4. Click OK.
  5. In the Available Software dialog, select the checkbox next to Developer Tools and click Next.
  6. In the next window, you'll see a list of the tools to be downloaded. Click Next.
  7. Read and accept the license agreements, then click Finish.

    If you get a security warning saying that the authenticity or validity of the software can't be established, click OK.

  8. When the installation completes, restart Eclipse.

Configure the ADT Plugin

Once Eclipse restarts, you must specify the location of your Android SDK directory:

  1. In the "Welcome to Android Development" window that appears, select Use existing SDKs.
  2. Browse and select the location of the Android SDK directory you recently downloaded and unpacked.
  3. Click Next.

Your Eclipse IDE is now set up to develop Android apps, but you need to add the latest SDK platform tools and an Android platform to your environment. To get these packages for your SDK, continue to Adding Platforms and Packages.

Troubleshooting ADT Installation

If you are having trouble downloading the ADT plugin after following the steps above and you are behind a firewall (such as a corporate firewall), make sure that you have properly configured your proxy settings in Eclipse. In Eclipse, you can configure proxy information from the main Eclipse menu in Window (on Mac OS X, Eclipse) > Preferences > General > Network Connections.

If you are still unable to use Eclipse to download the ADT plugin as a remote update site, you can download the ADT zip file to your local machine and manually install it:

  1. Download the ADT Plugin zip file (do not unpack it):
    Package Size MD5 Checksum
    ADT-23.0.4.zip 103336810 bytes 91a43dcf686ab73dec2c08b77243492b
  2. Start Eclipse, then select Help > Install New Software.
  3. Click Add, in the top-right corner.
  4. In the Add Repository dialog, click Archive.
  5. Select the downloaded ADT-23.0.4.zip file and click OK.
  6. Enter "ADT Plugin" for the name and click OK.
  7. In the Available Software dialog, select the checkbox next to Developer Tools and click Next.
  8. In the next window, you'll see a list of the tools to be downloaded. Click Next.
  9. Read and accept the license agreements, then click Finish.

    If you get a security warning saying that the authenticity or validity of the software can't be established, click OK.

  10. When the installation completes, restart Eclipse.

To update your plugin once you've installed using the zip file, you will have to follow these steps again instead of the default update instructions.

Other install errors

Note that there are features of ADT that require some optional Eclipse packages (for example, WST). If you encounter an error when installing ADT, your Eclipse installion might not include these packages. For information about how to quickly add the necessary packages to your Eclipse installation, see the troubleshooting topic ADT Installation Error: "requires plug-in org.eclipse.wst.sse.ui".

For Linux users

If you encounter this error when installing the ADT Plugin for Eclipse:

An error occurred during provisioning.
Cannot connect to keystore.

...then your development machine lacks a suitable Java VM. Installing Sun Java 6 will resolve this issue and you can then reinstall the ADT Plugin.


  Navigate the Kernel

 Navigate Kernel Source  

HowTo use the CDT to navigate Linux kernel source

Here are some steps that I've found to get the CDT to work well with the Linux kernel source. If you exclude some of these steps, it may still work to a large degree, but some things may not work exactly right; for example it may find the wrong include file for a C file.

Anyway, as you do these steps, I think you may understand how they assist the indexer to do a good job for the Linux kernel source.

Disclaimer: these steps were last updated for Eclipse Juno 4.2.2 + CDT 8.1.2, and originally developed for Eclipse 3.5.1 + CDT 6.0.0.

  1. Download and install Eclipse plus the CDT.
  2. Configure and build your kernel to define CONFIG_* and generate autoconf.h. This can be done before or after downloading and installing Eclipse.
  3. Ensure that you have the right kernel source (e.g. make sure you are on the right git branch). If you check out another branch later, that's ok, but you will need to re-index the source, and that takes about 20 minutes.
  4. Start up Eclipse.
  5. Click File->New->C Project
  6. Fill in a project name like my_kernel
  7. Uncheck the Use default location box and type in the root directory of your kernel into the Location box.
  8. In the Project type: pane, click the Makefile project and select Empty Project
  9. On the right side, select Linux GCC
  10. Click Advanced settings... and a Properties dialog will pop up.
  11. Open the C/C++ General selection on the left.
  12. Click on Preprocessor Include Paths
  13. Select GNU C in the Languages list
  14. Select CDT User Setting Entries in the Setting Entries list
  15. Click on Add.... Choose Preprocessor Macros File from the top left dropdown, Project Path from the top right dropdown, and enter "include/generated/autoconf.h" into the File text box. (Note: For kernels older than 2.6.33, the location of autoconf.h is include/linux/autoconf.h)
  16. Also add any other macros files you are using.
  17. Click on Indexer
  18. Checkmark the Enable project specific setttings box.
  19. Uncheck Index source files not included in the build
  20. Click on Paths and Symbols on the left.
  21. Select the Includes tab and then select GNU C
  22. Click Add...
  23. Click Workspace... then select your kernel's include, and include/uapi directories
  24. Do another Add, Workspace and add both arch/architecture/include, and arch/architecture/include/uapi directories. e.g., arch/powerpc/include and arch/powerpc/include/uapi (The UAPI directories are due to the kernel's user/kernel header split covered here in-detail)
  25. Click the # Symbols tab
  26. Click Add...
  27. Set the name to __KERNEL__
  28. Set the value to 1 and click OK
  29. Click the Source Location tab
  30. Click the plus sign next to your project name.
  31. Select the Filter item and click Edit Filter...
  32. Click Add Multiple... and then select all of the arch/* directories in your kernel source that will not be used (i.e. all the ones that are not for the architecture you are using)
  33. Click OK and OK again to dismiss that dialog.
  34. Under C/C++ General, select Preprocessor Include Paths, Macros etc.
  35. Click the Providers tab and select CDT GCC Built-in Compiler Settings
  36. Uncheck Use global provider shared between projects
  37. Add -nostdinc to the Command to get compiler specs
  38. Check Allocate console in the Console View so you can see that this is working
  39. Click OK on the Properties dialog.
  40. Click Finish on the C Project dialog.
  41. The Project will index automatically.
  42. On a platter drive indexing will take upwards of 20 minutes to complete, on a SSD indexing will take about 5 minutes to complete.


  1. Adding include and arch/architecture/include only gets you a couple of the common include paths. To fully index all of the kernel, you would have to add dozens of paths, unfortunately. For this reason, I advise against using PTP's remote indexing capability for the linux kernel, because what happens is that it will report thousands of errors in locating header files, and the process of reporting those errors over a possibly long-latency link, will cause the indexing to take many hours.
  2. If you change any of your CONFIG_* settings, in order for Eclipse to recognize those changes, you may need to do a "build" from within Eclipse. Note, this does not mean to re-build the index; this means to build the kernel, by having Eclipse invoke make (this is normally bound to the Ctrl-B key in Eclipse). Eclipse should automatically detect changes to include/generated/autoconf.h, reread the compilation #defines it uses, and reindex.
  3. The background color of "Quick Context View" will be dark if the Ambiance theme in Ubuntu is selected.
  4. For some people, Eclipse may fail to index the kernel with a out of memory error. The fix seems to be to start eclipse with the arguments: eclipse -vmargs -Xmx650M

Corey Ashford cjashfor@us.ibm.com Updated by Adam Duskett Aduskett@gmail.com


  Blend Credit

Blend is a free, fully standards-compliant CSS template designed by Free CSS Templates. This free template is released under a Creative Commons Attributions 2.5 license, so you're pretty much free to do whatever you want with it (even use it commercially) provided you keep the links in the footer intact. Have fun with it :)

This template is also available as a WordPress theme at Free WordPress Themes.