Is there any way to disable automatic Android Library Update when starting Eclipse?
The one related to the "Android Library Update" message shown in the progressbar at the bottom when starting Eclipse
AFAIK, there is no way to disable it, and even if there is, your projects probably would not work afterwards.
However, you can reduce the amount of time spent on this and other startup tasks. Simply close projects that you do not need to have open. You can leave the projects in the workspace, but just close them via right-clicking on the project in the Package Explorer and choosing "Close Project".
My Eclipse workspace has ~350 Android projects. It used to take a minor eternity to fire up Eclipse in the morning. I switched to keeping most projects closed, leaving open only:
stuff I am working on
all Android library projects (in case stuff I am working on, now or later, depends upon them)
stuff I opened earlier and haven't gotten around to closing again yet
I have a few dozen projects open at the moment. Now, Eclipse starts up fairly quickly.
Related
I have a lot of issues with the Facebook Android SDK 3.0 — a lot. Here's one which is particularly annoying: I have added the Facebook project to my workspace and linked it to my Android application. Now when I export my application (by right clicking on the project in Eclipse, selecting the Android Tools option and then clicking Export Signed Application Package), my signed application package exports okay. I notice however that around 50% of the time I export my APK, when I then make any Facebook SDK request using this APK (like opening a session or requesting additional permissions or anything of the like), I just get a white screen showing a progress bar which hangs indefinitely, as follows...
It hangs there until I press the device's Back button, at which point I get a SessionState.CLOSED_LOGIN_FAILED session callback. Basically, it builds badly on almost every other export. Is anyone else experiencing this or know how I can stop this from happening? It's very very time-consuming having to build two or three times until I get a good APK. I am refreshing the projects in my workspace and doing a Project -> Clean -> Clean all projects every time and even that doesn't do the trick.
What I've done the last few times I've had to export my signed application package is to go to my project's properties, open the Android option, remove the Facebook library reference and then re-add it. I've had five consecutive good exports doing this so I'm guessing this does the trick!
I'm trying to start out with Android programming (I'm running Mac OS X Lion). I had an old version of Eclipse and installed ADT version 20 in it, and code didn't compile properly. Fine; I hadn't done much in there, and after reading some stuff here it sounded like the easiest thing for the long run would be to put together a completely new installation.
So I downloaded the latest version of Android, with the SDK, from the Android developer Getting Started site, and ran it (in its own directory). I loaded one of my previous workspaces and it said that one wouldn't work because the ADT was version 20 and it needs 21. I figured fine, there wasn't much in there and I'd just start a new workspace.
So I started a new workspace, and here's where the real trouble came: It gives me the start screen with newbie welcome instructions but won't go any further than that. When I try to create a new Android Application Project, it goes through the menus but as soon as I click Finish I get a please-wait circular icon, and little happens. There's a line at the bottom that says "66M of 142M" - it increases slowly into the 80s and then drops back down into the 60s, endlessly. And the links provided on the welcome page (Building Your First App, etc.) don't work - I click on them and nothing happens.
Any idea what's going wrong here? Is there some cruft left over in my system from older versions, which I should delete? If so, how should I go about doing that? If not, what else might I try to get it working?
I can't comment beneath yours because of my level, but you can help Eclipse run faster by giving it more memory. Doing this speeds things up quite a bit.
As far as installations go, maybe try Google's packaged version of Eclipse + Android SDK. The whole package is available here. It's already preconfigured to work and provides eclipse with ADT installed by default. Of course, if you already have an existing Eclipse you want to modify this won't help you too much. But if you're new to Eclipse it's a good way to get started with Android development.
Like the question says, no mater what project i try this on, old or brand new, when I right click on the project and go to properties, then select the Android tab (I want to add a library), Eclipse freezes. I have to kill it. Has anyone run into this problem or know how I might fix it?
Thanks
EDIT:
Eclipse SDK
Version: 3.6.2
Build id: M20110210-1200
EDIT:
Or is there another way to add a library. I want to try out ActionbarSherlock :)
Ok, so I don't claim to understand it, but I've tried it more than once and confirmed it. When I'd go to the Android tab in Properties, the window automatically stretches the full height of my monitor and freezes. So, I killed it and went back in, but this time, starting on a different category ("Resource" in this case), I squashed the window height down to almost as small as it could get and clicked on Android. It worked. Didn't freeze. Then I was able to expand the window to see the list of libraries. No idea what it is, but I did it several times...recreating the freeze and then the fix. Hopefully this will save someone else...
i have found the reason ,because the list of available Android sdk is too long ,the window of the property can't be drawn immediately ,so it has no response.
the solution is open the SDK Manager ,delete the old sdk platform ,such as 1.5 1.6 3.0 3.1 3.2
those are not used usualy.then restart the eclipse .it works now .
For these kind of problems you have to try the following (in the same order) and stop when it works.
Play around inside eclipse by closing and opening project, deleting and reimporting projects etc.,
Restart eclipse
Restart system
Upgrade to the latest android SDK
Upgrade to the latest eclipse version
Usually you should stop at 2. Sometimes you need to stop at 3. Occasionally at 4 and Rarely at 5.
Good luck.
I'm a .NET developer but I like JAVA so in my free time I play around with that. I don't normally use Eclipse but I installed the ADT eclipse plugin and Andriod SDK and I started learning and I made a new project with a TableLayout and it kinda looks good, and it runs ok on the emulator.
However... there a few things that drive me absolutely catatonic and perhaps I am doing something wrong so please help me out.
Firstly, if I change the main.xml file in whatever way, even by adding what is supposedly a correct parameter, it will start freaking out and will generate an error that just says "error" without specifying what that is, it will then generate a main.out.xml and then report an error that the main.out.xml is empty. It later won't let me delete that and will start generating a main.out.out.xml and so forth, even after I correct that original xml that caused the error.
The only way to get things going is to delete the bin folder, restart Eclipse, delete all the out xml files and then sometimes it will run the application or some other times it will start generating those 'out' files again and the loop goes on.
That way it takes hours to run a simple app even one without errors that used to run before.
Surely that was NOT how they intended it to work, is it??
Also.. there is no "Rebuild" button that will flush all files out automatically, or is it hidden somewhere? I am tired of manually deleting those automatically generated files and the build folder and all those out.xml files.
Also, while I'm at it, I also want to point out that the designer view sometimes disappears and there is nothing on earth that will bring it back, the only way is to create a new project and copy the main.xml to it and then it shows up again. Another bug?
I have the latest eclipse version:
Version: Indigo Service Release 2
Build id: 20120216-1857
If you have any clues how to get this to work, I will appreciate it!
Many thanks in advance
When you click the Run button with an XML file selected, Eclipse is running an XSL Transformation on that XML and producing the .out.xml file as the result. This is a feature of the Eclipse Web Tools feature, which you'll have if you installed the Eclipse for Java EE Developers package (it may be included in other packages, too).
As others have said above in the comments, to run your Android app, select the Project, right-click, and choose Run As > Android App. Once you've done that once, it will create a Launch Configuration that you can launch from the Run or Debug toolbar buttons (pressing the small down-arrow on the Run or Debug buttons brings up a list of Launch Configurations that you can select from, as well as an option to manage them).
There is a Preference that will make Eclipse always launch the last thing you ran or debugged, instead of trying to be smart about what is currently selected. Open the Preferences and navigate to Run/Debug > Launching; there you'll find the option under Launch Operation at the bottom of the window.
I am a newbie to Android development, and am using Eclipse 3.7 Indigo on Ubuntu 11.10. I have the SDK and the ADT installed. I have two problems.
An Android project takes an awfully long time to get created.
When I restart Eclipse, all previously built Projects (even simple Hello World ones) have to be rebuilt, and this takes a really long time to build. While building the "details" dialog box shows
Loading data for Android 2.3.3
Android 2.3.3: Widgets and Layouts
then,
Building Workspace (where the progress bar seems to remain halted for eternity). At times it gets built after this. At other times, the first line in the HelloAndroid.java file shows an error, which when rebuilt yet again disappears.
So when I restart Eclipse, it takes approximately 10 minutes to get previously built projects running on the Emulator.
Any fixes to this?
Hard telling what the issue is without more information, but here are some thoughts:
Your machine may be underpowered. What OS, processor speed, RAM do you have?
If you have a very large amount of projects, or have some very large projects, then it can take a long time to build them when Eclipse starts. You can close a project (right-click the project in Package Explorer and click Close Project) so it will not be built and is not accessible until you open it later. Close projects you aren't actively working on, but may want to use again someday in the future.
The ADV (emulator) takes a long, long time to start up, yes. When you start it, make sure to select the option to start from snapshot and save to snapshot to save time starting it in the future.
And yes, you may want to reinstall everything again. Sometimes Eclipse just gets screwy.
It sounds like any of several items were improperly installed. Consequently, the directories of where your compiled libraries can't be found and must be regenerated each time. That is why it takes ten minutes or more: you're recompiling everything!
The time it will take for you to track everything down and repair the settings will be MUCH longer than the time to just do a fresh install.
Really.