Ok I have eclipse Galileo Build id: 20100218-1602, I was having a problem with my Logcat, and seen a post that recommended updating the SDK, so I updated the SDK to the latest version. This made the eclipse program give me a message saying this SDK needs ADT 14 or higher. I have tried to update the ADT without success. At this point, I've tried to delete and uninstall everything, and that has been impossible. There is no uninstall program and the eclipse folder will not delete. Does anyone have a recommendation on how to delete eclipse from my Window 7 computer? Or a way to revert back to my old SDK? This is driving me nuts. Thanks!
ADT 14 works only with Eclipse Indigo version.
Eclipse does not need any installation it contains a direct runnable exe. If you are unable to delete the folder then try restart your PC or try a software that will unlock the folder or atleast show you the processes that have a lock on that particular folder. You can close these processes on your own.
Once you install ADT 14 with eclipse indigo update the Android SDK. It should be straight forward.
i recommend a new install. while an update will easily take 2 to 4 hours (from rev 15 to rev21, with appropriate sdks, etc), you can download the complete ADT ECLIPSE bundle in much less time (410 MB) on regular 10Mb broadband.
i tried updating on Java EE Indigo from rev 15 to rev 21 (sdk tools) and ran into a big, big mess. not worth it. gave up and reinstalled eclipse. faster process and much sturdier result.
Download ADT bundle here, then
follow these instructions
since ECLIPSE is an executable that uses java virtual machine to run, it does NOT need to be installed (especially handy on windows). just unpack the bundle into your Program Files folder and execute the file eclipse.exe (if running under Vista / 7, you MAY need to run always as Administrator, i have a published recipe for Admin installing here).
after installing and checking if everything is OK, rename or delete your OLD eclipse folder.
if you use the same workspace that you were using previously, you should not miss a beat: the same projects will be open as when you last left your workspace, and your run and debug configs should be there, too.
ECLIPSE ROCKS!
Related
I don't have the rep to post screenshots but I'm not able to install ADT on Eclipse. I have "unclicked" the "check updates" box but I am still told that the operation can't be completed. I did go back and delete the whole ADT folder which had been working up 'til Friday; I reinstalled all of Eclipse. In all seriousness, I guess my real question is: is my best next step to get a big fast flash drive and install everything there, even if it works more slowly?
Delete eclipse and ADT then go to this site (http://developer.android.com/sdk/index.html) and download eclipse with sdk. Then go to download manager, download things you need and you're ready to go.
Hope this helps
You can download the Android ADT Bundle from this following links
64 Bit - https://docs.google.com/file/d/0B5JTI8WeLk_dZWs0YzVja1R3U3c/edit?usp=drive_web
32 Bit - https://docs.google.com/file/d/0B5JTI8WeLk_dS1Rucmc4SVFqTjg/edit?usp=drive_web
You shoudl consider this warning seriously, If you're a new Android developer, you should consider starting with Android Studio, because the ADT plugin for Eclipse is no longer in active development. If you still want to proceed, visit Installing Android Plugin in Eclipse Offline & Online
Note: That links to my own blog.
This problem sounds similar to a few others, except in my case the OK button is not grey-ed out. But for those who would rather not click the links...
Trying to create or edit an AVD from within Eclipse, after entering my settings, the "OK" button seems to be "clickable", but when I click it absolutely nothing happens.
I've made sure I have the appropriate system images installed, and that the target platform matches the API being used. Clearly a CPU has been chosen, skin set, etc... all the things that would make the OK button greyed out, which it's not.
I can create/edit AVDs if I run the AVD manager from outside eclipse, so this isn't the end of the world, but I feel there's a solution to this particular problem and I want to help solve it.
I've tried running eclipse as an administrator (that's what stopped the AVD manager from crashing outside of eclipse). I've tried just waiting around, or clicking multiple times. Looking at the Task Manager, no new processes begin when I click OK, nor does eclipse's CPU or RAM usage increase at all. The "Edit Android Virtual Device" window doesn't even go away.
Any clues?
(Running Indigo with the ADT plugin, btw, not the bundled version, which failed to work in a different way. Java 1.6.0 45. Windows 8, unfortunately. Plenty of RAM etc)
THIS IS A POSSIBLE WORKAROUND FOR BUGS IN ADT 22.6.0 ONLY, THESE BUGS SUBSEQUENTLY FIXED IN FOLLOWING BUILDS
Download and install new ADT v22.6.1 from here (zip) or use SDK manager to update
Seems like some bug from Google side, this problem found after "ADT 22.6" update. Widely reported on "Android Open Source Project - Issue Tracker" and nobody properly answered it yet.
However I was partially successful to create an AVD by opening "AVD manager.exe" from "Android SDK" for creating new AVD try to open directly AVD Manager.exe in SDK folder.
May be we have to wait for any conformation from Android community
Worked for me, sort of.. .
(Windows 8.1 Pro 64 Bit, Java JDK 1.7 Update 25, Eclipse Standard Kepler Service Release 1, Android Development Toolkit 22.6.0.v201403010043-1049357)
Update 1
Further research revealed that launching AVD Manager from SDK Manager (Tools --> Manage AVDs...) also works without any problems.
Update 2
More bad news is AVD creation not working from command line tool too.
Update 3
Assuming some parameter passed during launching AVD manager from Eclipse causes these problems
Update 4
Updated Java to JDK 1.7 Update 51 and Eclipse Standard SDK to Kepler Service Release 2 their latest and no resolution to the problems. Also tested under Debian and same results obtained.
Update 5
At https://code.google.com/p/android/issues/detail?id=66661 android project members conforms the problems and promises to fix by upcoming versions of ADT (22.6.1 - 22.6.3). At the mean time I would suggest to roll-back ADT to a lower version version 22.3.0
To uninstall current ADT go to
Help --> About Eclipse --> Installation Details --> Android Development Tools --> Uninstall
I may suggest uninstalling whole packages from Android (DDMS, Hierarchy Viewer, NDT, Traceview, OpenGL ES..etc..) to avoid any possible compatibility issues and install a fresh new ADT from above link through archive installation method.
Hope this will solve this problem temporarily. And wait for new release of ADT here.
Update 6
New ADT, version 22.6.1 is out now which will solve these problems
To elaborate on the statement "I can create/edit AVDs if I run the AVD manager from outside eclipse" in the OP:
Run the following on the command line
<android-sdk-location>/tools/android avd (on Linux in this case)
This launches the same AVD window you see when you click the AVD Manager icon in the eclipse toolbar. But this instance of the AVD manager does not have the bug, and you can create and run emulators as you did before the bug was introduced.
1 minute solution
I used a quick workaround where I cloned a device that already existed. The Clone button worked and I was able to successfully edit the clone.
Steps:
Select a Device by Google
Click the "Clone..." button
A window will pop up, click "Clone device"
Select the newly cloned Device, it should say "... by User"
Click the "Edit" button on the side
There you have it, you now have your own custom virtual device
Update and Solution: AsYashwanth Krishnan said, The bug in question is now fixed in later versions. I tried ADT 222.6.1 and ADT 22.6.2 , and they did not suffer from the bug of not not being able to create or edit Android Virtual Devices. The direct solution is to update you ADT to latest version, The workaround written below is left only for historical purposes.
Historical Workaround As #Yashwanth Krishnan said, this is a bug in ADT plugin 22.6; so best workaround is to rollback. for those asking how to rollback, here is a step-by-step guide:
First: Uninstall ADT plugin and all related plugins for android:
help->about
Installation details
Select android plugins and press uninstall button
Restart
Second: Download ADT 22.3.0 Archive from https://dl.google.com/android/ADT-22.3.0.zip
and install it
add repository from archive on local disk
Select android plugins
INFO:
I WAS able to create an AVD successfully after clicking OK several times and modifying some of my settings as a test.
I tried yashwanth krishnan solution and tried to open the AVD Manageer.exe directly without success. The manager will not open directly for me on Windows 8 x64. It tries to open, then shuts down immediately...
I met this issue too . The issue occurs in the latest version 22.6 which was released in March . Meanwhile I did the testing in 22.3 , the issue was not found .
So that I suggest that rollback the ADT to 22.3 and wait the new fix for 22.6
I banged my head on this for several hours until I found out that the default location was C:\username path\SDKs or something, where Android was installed on my system to D:\sdks\android_sdk_windows. So, changing the Eclipse Android directory to D:\sdks\android_sdk_windows fixed it.
I also heard that it may help things if you install the Android SDK to a path without spaces.
Hope this helps someone keep some hair.
Today I ran into the same problem after installing Maven. I messed around with different Path settings to get it to work and I ran into issues. I was also trying to install the google server for GCM. Somewhere in what I was doing I corrupted the Android Virtual Device Manager. I searched S.O. for an answer, then I decided to follow the first rule of TechSupport. I reinstalled the tool kit!
I went into the SDK manager and I uninstalled the tools (by clicking the Tool checkbox). It took several minutes to delete them all. Then I reinstalled the Tools which took about ten minutes. I rebooted Eclipse and the AVD and worked just like it did yesterday!
This time it only took a total of twenty minutes to fix.
Per the release notes, this problem has been resolved in revision 22.6.1, which is now available for download.
Updated your Android SDK Tools to 22.6.1 in Eclipse by selecting Window > Android SDK Manager and follow the prompts to install the update.
After that update finishes, select Help > Check for Updates and follow the prompts to update the appropriate Eclipse components.
After completing these updates, I tested the AVD functionality and it appears to be working properly.
i just copied the avds from a different system as descriped here:
Android - How to copy the emulator to a friend for testing
I faced the similar issue. I am using 23.0.2 version of android SDK.
"OK" button was disabled, but then I went to the path where android SDK was installed. In my case:
C:\Program Files\Android\android-sdk\
and executed AVD-Manager.exe by right clicking and selecting Run as an Administrator, and it worked like a charm.
Sometimes the AVD cannot be created because of this following error while starting:
x86 emulation currently requires hardware acceleration!
I was also facing this same issue. If u are facing the same, then it can be resolved by opening SDK Manager -> Under Extra -> Installed "Intel x86 Emulator Accelerator (HAXM Installer). Then when creating the AVD, select the proper CPU. This should work. :-)
For those posting that we need to set the sdcard size: I tried that and many other settings, and none of that helps. I get the NoClassDefFound Exception mentioned by mogilka, in the Error view. No configuration settings are going to fix that. It seems a bad update was pushed
Give some value for your sd card. May be something like 100 or 200
I'm developing for Android with Eclipse, and all was working well until yesterday. I used Ninite to update all my stuff, including JREs and everything (pro tip: do not do that), and it restarted my computer without asking in the middle of editing my workspace.
This caused all kinds of filthy problems, but now it all works, except for Android. I've updated Android SDK and the eclipse ADT, then when I try to tell Eclipse the SDK location, it gives this error:
This Android SDK requires Android Developer Toolkit version 14.0.0 or
above. Current version is 12.0.0.v201106281929-138431. Please update
ADT to the latest version.
Now, this is an outright lie. My ADT is version 14.0.something. I've tried Help>Check for updates, it says there are no updates. I've tried Help>Install new software...>Available Software Sites and removing the ADT repo, then reinstalling ADT, and it says it failed because I already have version 14.0.whatever.
How do I convince eclipse that my ADT is up to date??
I found the answer to the problem. (I'm using Helios, but it should work anyway)
Goto folder /Program Files(x86)/Eclipse/Plugins/ and make sure previous older versions of com.android.ide.eclipse.adt.package_##... are deleted (sometimes update fails to delete because of UAC). Keep the current desired version and complete the following.
Run Eclipse as administrator or disable UAC temporarily. (windows 7)
Go to Help → Install New Software.
On Work with: type https://dl-ssl.google.com/android/eclipse/ and press ENTER.
Wait for Eclipse to fetch the repository. An item named Developer tools will appear in the list.
Mark it for install, press Next and follow the steps to install the ADT tools.
When finished, it will ask to restart Eclipse. Make sure you do this.
When Eclipse restarts, all your Android SDK packages should show up again.
Dont forget to resume UAC if you need it.
An option is to manually download the ADT plugin (ADT archive) required. The page is, http://developer.android.com/sdk/eclipse-adt.html. The page reveals ADT 18 is available at http://dl.google.com/android/ADT-18.0.0.zip. The link is closer to the bottom page. I needed 17 although 18 was the latest, so I modified the download URL, changing 18 to 17.
Select Help → Install New Software → Add → Choose Archive and select the location of the downloaded ADT archieve file, Choose OK.
Select the components required and proceed as required. You may get a message that the software is already installed, proceed with the installation.
Hope this helps.
I had the same problem. My ADT in the eclipse was 8.x version. But my app required version 12 or more. So, I decided to upgrade both the Android SDK and ADT to the latest (at this time latest ADT is 17). I was able to upgrade the SDK but not the ADT. It always complained I got the versions already but I only had 8.x. The new SDK that I just upgraded would function only with ADT 14 and above. So, I had successfully broken my android development!!
The reason why I wasn't able to upgrade my ADT to the latest was because I was using Eclipse 3.5. The newer ADT versions require 3.6 or above. This small but key bit of information was really at the bottom of the error generated by Eclipse which required scrolling down (since only the top few lines of error were displayed). You typically wouldn't scroll down since these top few lines were followed by whitespace lines :). I did not scroll and I guess I wasted about a day trying to rectify this problem. But eventually I saw those 2 up/down arrows at the right of the dialog box and I scrolled down. There it clearly mentioned ADT 17 requires Eclipse runtime 3.6 and over.
So my solution was to find a suitable ADT that would work with Eclipse 3.5. Yes, tomorrow when I am in the mood, I shall upgrade to Eclipse 3.6 or 3.7 and the boat load of plugins I have :)
I've just upgraded my Android SDK version, and had exactly the same issue.
The 'Check For updates' Eclipse command failed because, for some reasons, Android Traceview failed to update.
My solution was to :
* Open Eclipse → Help → About Eclipse .
* Click Installation Details.
* Here select all the android related lines, and update them one by one, restarting eclipse each time.
And finally it worked ( even with Helios ) !
Best option is go to open eclipse ID
Then go to Help → About Eclipse >>
u will find the Installation Details button click on that
And now u can see the all anriod extension installed.
Select all or select one by one and just click the update button.
you will get the latest version from the net.
Hope these will help you all.
In Eclipse:
Help → Check for Updates.
Your ADT and SDK is not up-to-date yet and Eclipse is complaining about the right stuff...
Open Android SDK Manager from toolbar and update your SDK from there. It doesn't help if you are checking Eclipse updates. Because through Eclipse you cannot check SDK updates for Android.
Button looks like this :
I'm hearing a common issue is that newer Android ADK versions require newer eclipse versions. Colleagues who hit this say they installed Indigo in place of older Helios versions and were able to resolve the issue this way. I have not yet done the same myself.
To anyone else with this problem, my solution was just to delete the Eclipse folder, and download a new copy from scratch. I had to then re-download all plugins including adt, which worked this time round.
Im running eclipse on my windows 7 machine, 64bit with 6gb ram and core 2 duo.
Im currently running Eclipse 3.6 and android 2.2 SDK
Im running jdk 1.6
Im noticing that when coding and the context popups to list methods of a class, it hangs Eclipse for up to 15 seconds. This is very frustrating.
One thing to note, when Eclipse hangs, my processor is maxed out, and is being worked by a java process. So its doing something whatever it is. But frequently everytime I finish an object with a period and the context box pops up, its becoming too painful to work with.
I changed some settings in the Eclipse.ini file such as:
-Xms1024m
-Xmx1024m
--launcher.XXMaxPermSize 512m
Is there anything else I should look at:
After a google search
I have been able to find the bug report from Eclipse.
In short:
It is a problem that arises when using Helios with ADT. As the ADT page on android.com says:
Caution: There are known issues with the ADT plugin running with Eclipse 3.6. Please stay on 3.5 until further notice.
To fix it, you will have to use Eclipse 3.5 and put your project in a newly created workspace. (If you keep the workspace from Eclipse 3.6, the problem will occur even on Eclipse 3.5.)
A Work-around procedure is presented in comment#8 at this URL: http://code.google.com/p/android/issues/detail?id=7850
Example:
I'm coding against Froyo, and my target SdkVersion is 7 (AndroidManifest.xml). So for step 1, I downloaded this file:
https://android.googlesource.com/platform/frameworks/base/+archive/froyo-release.tar.gz
And then for step 2, I extracted the base/ directory of that .tgz file into my SDK path, which I install under /opt/android-sdk-linux_x86/. So here's the command I executed against the tgz to put everything where it goes:
tar -vzxf base-froyo.tar.gz -C /opt/android-sdk-linux_x86/platforms/android-7/sources/ base/
The end goal appears to be to place the actual sources into the "sources" folder in the SDK tree, so that when the auto-correct goes out looking for them, they are there.
snpe60 describes it more clearly:
Comment 7 by snpe60, Oct 14, 2010
This issue is happen because the ADT
classpath container have an invalid
source attachment by default. It is
fixed in
https://review.source.android.com/16569.
This change enables changing the ADT
clasppath container's source
attachment and disables setting
invalid source attachment. Hoping it
will be available in ADT 8.0.0.
This is much better Eclipse autocompletion problem
here is a link for the problem you are having
http://aaarkonusurum.blogspot.com/2011/08/eclipse-intelisensein-cldrtan-yavaslgna.html
I'm using Windows 7 and installed the 64 bit version of Eclipse 3.5.2. I then installed the Android ADT plugin, but when I try to configure it in the Windows > Preferences dialog, the Android Plugin doesn't show up in the left pane. Instead I see DDMS. This prevents me from specifying the location of the Android SDK (unless there is another way) to give me the appropriate templates and such.
Someone posted a fix to this that includes setting the permissions of Eclipse, but that didn't work for me. I tried installing the Android Plugin from both online installation (thru the URL install) and the offline Archive method.
If you're running Windows Vista or 7, make sure you right-click Eclipse and RUN AS ADMINISTRATOR. I literally spent six hours figuring this out, and this was what fixed it.
Dear people from the future:
I had roughly the same problem in linux, except that i didn't see anything at all but vanilla eclipse after installing. by combining both previous answers i got it to work:
start eclipse with sudo eclipse -clean, install the plugins and restart eclipse. the plugins showed up including the welcome screen that's supposed to be there.
after that it should work when running as regular user as well.
works for both the android sdk and the gwt sdk. (and probably other eclipse plugins)
Remove the plugin, then restart as follows:
eclipse -clean
Now try reinstalling the ADT from the online installation
For users having similar problem and not luck with other solutions:
I have windows XP but had same problem. I realized that I had JDK5/bin folder in my PATH environment variable (though my JDK_HOME was pointing to JDK6), as soon as I modified the PATH to replace bin of JDK5 with JDK6, the Android buttons on eclipse (after restart with -clean) along with Android option in Preferences & New Project showed up. (Weird eh!)
Also, consider to install the bundle android installation having eclipse with pre-configured Android SDK if a new eclipse installation doesn't matter to you
http://developer.android.com/sdk/installing/bundle.html
The above answers do not confront the heart of the problem. There is a feature in Windows 7 that prevents downloaded files from direct access of local files. All of the state is perfectly maintained in the Eclipse workspace instance. The problem is easily resolved by doing the following:
Find the "Eclipse" executable
Right-click on it.
Click "Properties".
Select the "General" tab.
Look for -> Security: "This file came from another computer and might be blocked..."
Click Unblock.
This is a much better solution than uninstalling and reinstalling the ADT or Eclipse which can be a pain.