This is my first step in the development of Android, so we apologize for any stupid question.
I used the Windows installer to install the Android SDK Manager. After installation, it looks like my initial menu.
And here is what the SDK manager looks like:
When I try to use the Eclipse pluggin, I get the following error.
[2012-01-13 16:29:10 - DDMS] DDMS files not found: C: \ Program Files \ Android \ android-sdk \ platform-tools \ adb.exe
So, I thought, maybe I need to update the SDK manager, but updating the SDK Manager does nothing.
I searched through forums and documentation. People keep saying that I have to use the SDK and AVD Manager. I just can't find the tool by that name. Is this a separate installation? I can find the SDK manager and the separate AVD manager and do not look anything like the screenshots presented on the forums / documentation. Maybe I'm using the wrong version! I downloaded the SDK from here .
UPDATE 1:13 Jan 2012
Here is something more that I thought. When I try to update my SDK manager, this is what I see in the log:
Fetching http://dl-ssl.google.com/android/repository/addons_list-1.xml Failed to fetch URL http://dl-ssl.google.com/android/repository/addons_list-1.xml, reason: Connection to http://dl-ssl.google.com refused Fetched Add-ons List successfully Fetching URL: http://dl-ssl.google.com/android/repository/repository-5.xml Failed to fetch URL http://dl-ssl.google.com/android/repository/repository-5.xml, reason: Connection to http://dl-ssl.google.com refused Fetching URL: http://dl-ssl.google.com/android/repository/addon.xml Failed to fetch URL http://dl-ssl.google.com/android/repository/addon.xml, reason: Connection to http://dl-ssl.google.com refused Fetching URL: http://dl-ssl.google.com/android/repository/addon.xml
For some reason, the connection to http://dl-ssl.google.com is rejected, and maybe that’s why I can’t update anything.
UPDATE 2: January 16, 2012
Well, I have no answer, I'm going to write down everything I do before I forget. Maybe it will be useful for someone else ...
I had a lot of problems setting up my Android development environment. So far, I have identified a solution for a couple of questions. Maybe I'll make out the rest soon!
Used environment: Windows XP 32 bit Eclipse Helios
Problem 1: Could not find the SDK and AVD Manager after installing the Android SDK.
Solution 1 Despite the lack of proper documentation, it took me a while to realize that the latest version of the Android SDK had separated the SDK from AVD Management. Therefore, as soon as you install the Android SDK, you expect to see two components - 1) SDK Manager, 2) AVD Manager. I'm not sure what features have changed from the previous version, but if this is your first time developing Android, this change can put you nuts, because all the documents speak from the previous versions - bad GOOGLE!
Problem 2 During the installation of the SDK, .exe for Windows cannot detect the JDK.
Solution 2 Again, the old documents and forum posts seem to indicate that a defeat from behind, and then re-defeat, should again solve the problem. Not so with the latest version. Google came up with fun work to defeat this flaw. You now have a small "Report a bug" button. Click this button and the next button will be turned on. This will allow you to continue the installation.
Problem 3: Installing the Eclipse ADT plugin causes the following error:
Cannot complete the install because of a conflicting dependency. Software being installed: Android Hierarchy Viewer 16.0.1.v201112150204-238534 (com.android.ide.eclipse.hierarchyviewer.feature.group 16.0.1.v201112150204-238534) Software currently installed: Eclipse IDE for Java EE Developers 1.3.0.20100617-0521 (epp.package.jee 1.3.0.20100617-0521) Only one of the following can be installed at once: Eclipse UI 3.6.1.M20100826-1330 (org.eclipse.ui 3.6.1.M20100826-1330) Eclipse UI 3.6.2.M20110203-1100 (org.eclipse.ui 3.6.2.M20110203-1100) Eclipse UI 3.6.0.I20100603-1100 (org.eclipse.ui 3.6.0.I20100603-1100) Cannot satisfy dependency: From: Android Hierarchy Viewer 16.0.1.v201112150204-238534 (com.android.ide.eclipse.hierarchyviewer.feature.group 16.0.1.v201112150204-238534) To: org.eclipse.ui 3.6.2 Cannot satisfy dependency: From: Eclipse IDE for Java EE Developers 1.3.0.20100617-0521 (epp.package.jee 1.3.0.20100617-0521) To: org.eclipse.epp.package.jee.feature.feature.group [1.3.0.20100617-0521] Cannot satisfy dependency: From: Java EE IDE Feature 1.3.0.20100617-0521 (org.eclipse.epp.package.jee.feature.feature.group 1.3.0.20100617-0521) To: org.eclipse.platform.feature.group [3.6.0.v20100602-9gF78GpqFt6trOGhL60z0oEx3fz-JKNwxPY] Cannot satisfy dependency: From: Eclipse Platform 3.6.0.v20100602-9gF78GpqFt6trOGhL60z0oEx3fz-JKNwxPY (org.eclipse.platform.feature.group 3.6.0.v20100602-9gF78GpqFt6trOGhL60z0oEx3fz-JKNwxPY) To: org.eclipse.rcp.feature.group [3.6.0.v20100519-9OArFKvFtsd7WLUKh-DcYTS] Cannot satisfy dependency: From: Eclipse RCP 3.6.0.v20100519-9OArFKvFtsd7WLUKh-DcYTS (org.eclipse.rcp.feature.group 3.6.0.v20100519-9OArFKvFtsd7WLUKh-DcYTS) To: org.eclipse.ui [3.6.0.I20100603-1100]
Solution 3: This is because the Eclipse IDE for Java EE Developers is an older version. So, in Eclipse, go to Help → Update Software. This will display the latest Eclipse IDE for Java EE Developer. Install it. Then repeat the steps to install the Android ADT pluggin. This solved the problem for me.
Problem 4: When you open eclipse after installing the ADT plugin, the following error message appears: [2012-01-16 16:00:10 - DDMS] DDMS files not found: C: \ Program Files \ Android \ android-sdk \ platform -tools \ adb.exe
Solution 4: This issue was fixed with the Nandeesh add-on (see comments below). I download the platform platform tool directory from the following location ( http://dl-ssl.google.com/android/repository/platform-tools_r10-windows.zip ) and unzip it into the platform tools directory in my installation directory. This fixed the error from Eclipse ADT.
Problem 5: The following error occurs when updating using the SDK Manager
Failed to fetch URL http://dl-ssl.google.com/android/repository/addons_list-1.xml, reason: Connection to http://dl-ssl.google.com refused
Partial Solution to Problem 5: I am stuck with this problem and have not yet found a solution. Here is what I learned.
All messages about this error state that this is due to the proxy server settings. This is what I did: I found out my proxy settings by going to my Internet Explorer → Internet Options → Connections → Lan Settings. We copied the proxy data and installed in Eclipse → Windows → Preferences → General → Network Connections. After that, I went to the SDK manager → Tools → Options and entered the proxy data in the HTTP Proxy Server field and checked the https force parameter. Tried to refresh - no luck. Then, in desperation, I tried all combinations of Proxy and force https. Nothing is working. So, in accordance with the proposal made by Nandeesh (see comments below), I started downloading files directly based on repository.xml, found here, ssl.google.com/android/repository/repository-5.xml. So far so good.
Problem 6: Failed to detect target SDK in eclipse ADT
Solution for Problem 6: This is what I did. Download the latest version of Eclipse. Now I am using Eclipse Indigo. Then I checked the SDK directory structure. I installed it under C: / Android / android-sdk. Avoid spaces in the file path (this may cause a problem). The Android / android-sdk directory should contain the following directories: platforms, platform tools, tools, add-ons. Inside the platforms directory, I see the android-4.0.3 directory. This directory must have a version number as part of the directory name. If you do not see this directory, download the appropriate platform from https://dl-ssl.google.com/android/repository/ . The version you should use depends on your environment. A list of all directories is available in this XML http://dl-ssl.google.com/android/repository/repository-5.xml . Download the appropriate platform and unzip all the contents to C: / Android / android-sdk / platform. Also download the appropriate platform tools and unzip all the contents to the platform directory. Restart the eclipse. SDK should be automatically detected. If not, go to Windows -> Preference -> Android and set the SDK installation directory. The hit applies and it should list the available targets. Please note that goals will be displayed if and only the SDK installation is correct. Therefore, make sure that the platform directory inside the SDK installation is correct.
Problem 7 I see this when I open an eclipse 
I don’t know what went wrong. Again, suspecting that this is because I manually copied the files :(
Solving Problem 7: Read the solution to Problem 6. It will also solve Problem 7. The only thing that is important is to make sure your SDK is installed correctly. If you do not manually copy the appropriate platforms and platform tools and try again. Ensure that the file structure is correct and that the file names do not exist.
Having done all this, I can now say that I have set up my environment, and now I am ready to code! This problem is SOLVED :)