I've been using ADT for about a year now.
We have a Git project on bitbucket.
Just before Christmas I started having some performance issues when pulling/fetching from our repository.
What appears to happen is that the fetch downloads the changes, but then my PC runs for hours resolving the deltas.
Looking at the task manager shows javaw.exe using a single core, and nearly a Gig of memory. It will eventually complete, but this process used to only take minutes. Here's a screenshot:
This is where it's "stuck"
As you can see, it's not the worlds largest update.
My Eclipse version is 4.2.1.v20130118-173121-9MF7GHYdG0B5kx4E_SkfZV-1mNjVATf67ZAb7.
My ADT version is 23.0.2.1259578.
JDK is now 1.7u75, it was 1.7u55 before I updated it.
I know this is a pretty random question, but I have no idea what else to try.
Any help greatly appreciated.
It seems more a stability problem of your pc. However if your problem seems to be on javaw.exe i suggest to update to last JDK jdk-8u31 you can find it for all platform on http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html.
If is not a problem for your project try to change version of Eclipse switching to
Eclipse Java EE IDE for Web Developers.
Version: Luna Service Release 1a (4.4.1)
Build id: 20150109-0600
This is the last Eclipse version, code name Luna and supports well JDK 8.
Related
I am a new Android developer (4 weeks into porting my iPhone app to Android). I have 8 projects (the app, and 6 small UI experiments, and a vanilla Hello World project that I just created with Eclipse). All fail to compile, and the issue is that every reference to the generated file R is flagged as "R cannot be resolved to a variable".
Up until yesterday afternoon -- every project compiled and ran (albeit very slowly) in the Android emulator. I've changed something, and since yesterday, all projects fail to compile, all in the exact same manner "R cannot be resolved to a variable". I every case, the generated files are missing. I believe they disappeared as I tried to clean and rebuild each project in the course of debugging this problem.
Two things that I know changed when this problem started, but that I can't say caused the problem, were: 1) shifting to debugging on a real Android device (a Samsung Galaxy Tab 2, which worked like a champ after struggling with the slow emulators), and 2) allowing Android (and perhaps Eclipse) to update themselves from the web.
I've spent many hours trying other user's suggestions and none have helped. Most suggestions refer to file naming issues, xml syntax errors, but I haven't changed these files and filenames since compilation was working. I have tried:
cleaning and rebuilding the projects
checking for subsequent updates to the Android SDK (and there were 2 subsequent ones)
Eclipse->File->Android Tools->Fix Project Properties
making small source changes to force rebuilding
rebooting Eclipse, as well as the Mac host, adb, the emulator, the Android SDK Manager
deleting a project, restarting Eclipse, and adding the project back in (bad idea - this fails with an error "Failed to load properties file for project 'ListViewFragmentTest'"
creating a brand new Android App project, which has worked many times before, but now fails
There's something going systematically wrong, and while I won't claim all these projects are bug-free, they did run up until 6pm yesterday, and then all stopped compiling thereafter.
I wonder if anyone has other suggestions, before I embarking with a complete reinstall of the development environment?
My environment is:
Macbook Pro (OS X 10.7.5, 8GB RAM, 2.53GHx Core i5)
Eclipse (Indigo Service Release 2, Build: 20120216-1857) (too old?)
Android SDK Manager Rev 22
Android SDK Tools (22), Platform Tools (17), Build Tools (17)
API's 11-17, all up-to-date
Seems like lots of people experience trouble with missing generated files (R), and I have had trouble when I've had layout XML errors as well, but that doesn't seem to be causing this problem. Thanks in advance for your help!
I am not sure but you are facing issue of R.java file is not getting generated after updated with ADT rev 22.
If this is the case then here is the solution:
Hope you know Android studio has gradle building tool. Same as in eclipse they have given new component in the Tools folder called Android SDK Build-tools that needs to be installed. Open the Android SDK Manager, select the newly added build tools, install it, restart the SDK Manager after the update.
Check in the Java build path library, whether "src" check box is checked or not.
If you are using any additional Libraries then make sure libs/android-support-v4.jar is same for project as well as the Libraries.
Thanks everyone. None of these suggestions resolved my problem. And while I'm curious as to why it happened, I was more impatient with not making any progress. I've reloaded Eclipse and the Android tools (this time with the bundled version from developer.android.com), and everything is working smoothly again.
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!
About 2 months ago I was setting up an Android development environment, and noticed a warning on the Android SDK page that stated "There are known issues with the ADT plugin running with Eclipse 3.6. Please stay on 3.5 until further notice." - so
I posted a question here about this and from the responses decided, to install Eclipse ver 3.5
I never saw a notice that it was safe to upgrade, but...
- The warning is now missing from the Android SDK page
- I thought I read (maybe I'm wrong, because I can't find it now) a comment that some of the Android tutorials were now assuming Eclipse ver 3.6.1
Can I assume it is now safe to upgrade to Android 3.6.1 ?
The Eclipse IDE for Java Developers download page still seems to be at 3.6.0 ?
Comments Welcome
I believe it is fine, i upgraded my desktop environment to 3.6.1 and everything seems to be running fine.
Confirmed: Here is the link to the requirements page. It now says anything greater than 3.4 will work.
Eclipse 3.4 (Ganymede) or greater
Eclipse Link Requirements
I upgraded to the latest 3.6 and it was OK except that the content assist for the Android classes was very slow, i.e you would type 'textView.' (where textView is a TextView) and wait for ages for all the available methods to be shown.
This issue is a known bug reported at
Code Assist still Slow
Down near the bottom of this thread, someone identified a fix:
*https://bugs.eclipse.org/bugs/show_bug.cgi?id=329288 contains patch
that fixes this issue.
Unfortunately patch is applied only in 3.7 branch.
I have patched org.eclipse.jdt.core from Helios 3.6.1 with the patch
attached in this bug and create a patched plugin.
You can replace your /plugins/
org.eclipse.jdt.core_3.6.1.v_A68_R36x.jar plugin with one from
http://adt-addons.googlecode.com/svn/patches/org.eclipse.jdt.core_3.6...
and restart Eclipse. Content Assists will be much better. Just try it.
Don't forget backup your original plugins.
Peco*
I applied this patch and everything works fine now.
I always used Eclipse Helios 3.6.1 for my android programming and I never had any problems, I don't know what the problems were but I didn't find any. Sometimes my R.java doesn't seem to connect with my other classes but I solve that by either restarting my Eclipse of just clean my project, most of the times clean project works perfectly.
The ADT plugin also works fine. It upgrades correctly and I can see all my versions when I create a new project
I did see people having project to even install the google ADT plugin when looking for new software but I didn't come accross that problem. It just installed the first time. with the new update however it seems that my adb.exe doesn't seem to be in my tools folder and Eclipse looks there, so I just copied it from my platform-tools to my tools folder and got it working.
When I tried to update the 2.3 sdk to 2.3.1 in Eclipse 3.6.1, I had to clean all my projects as well as start Eclipse several times before everything could be installed successfully. Other than that, I've had no problems at all.
I recently installed a fresh copy of Motodev. When I type the name of object and a period after it a popup comes up with a list of all of the methods available to that object. Ever since I started using this new copy of Motodev if I have an object with a very large amount of available methods this process freezes the whole program for several seconds.
RelativeLayout and EditText are the two that I have personally noticed that this is a problem with, but I suspect any object that has a large number of methods will cause this. It was never a problem before. Has anyone else seen this issue and if so how did you fix it? I do like having the list pop up so that I can see all of the methods available to me so I'd like to leave that feature turned on if at all possible.
Looks like you figured this out already, but I'll say it for future readers. There is an update to MOTODEV Studio specifically to work with ADT 8.0.1. There were some API changes in ADT that required us to update Studio also. ADT 8.0.1 requires Studio 2.0.1, which is based on Eclipse Helios. There are installers on the MOTODEV site as well as an updater for Eclipse.
Because of the complexity of dependencies with all the Eclipse plugins, I suggest to download the .zip archive at MOTODEV rather than using the "Install Updates" method. I find that I get timeouts quite often at home on broadband that don't happen at work with a bigger pipe.
Also, Studio 2.1 will be available some time within the next week (~Jan 25) and will work with the 2.3 SDK and ADT 8.0.1.
UPDATE: 2/14/11 - It would appear that the correct answer is found at comment #8 in this link: http://code.google.com/p/android/issues/detail?id=7850
Tim will need to formally accept this answer at some point...
Which is as follows:
For those of you with this problem, here's what you can do until the fix is publicly available:
1. Download https://android.googlesource.com/platform/frameworks/base/+archive/<branch>.tar.gz where is one of those listed here (froyo-release for 2.2, the file is about 113MB): https://android.googlesource.com/platform/frameworks/base/+refs
2. Extract the contents of base/ in the tar into "/platforms/android-/sources" where is 8 for froyo, 7 for eclair, etc.
3. Enjoy fast content assist in 3.6!
If you are using eclipse v3.6 (Helios) this is a known issue with ADT - the android dev site recommends using v3.5 or v3.4 of eclipse until the problem is resolved.
EDIT: It might be dependent on the version of ADT you are using - I can't find the recommendation to use v3.4 or v3.5 anymore. Perhaps things were fixed with ADT 8.0.x Check which versions you are using anyway.
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