Eclipse hangs while changing properties [duplicate] - android

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.

Related

Why android studio crashes automatically?

My studio's current version is 0.9.9 (recently updated), now here is the history:
There was some problems when I shifted eclipse to studio. The last problem happened when I updated it. My app became full of error. One of them was cannot resolve Symbol ActionbarActivity. And so many others. I spend a day behind it and gave up. I recreated my app from first to last with the same resources, then it became totally good to go. Three days later(today) again another problem raised. I turned on my laptop, opened Android studio and it says Rendering problem No Android SDK found. Please configure an Android SDK. But last night it was running fine. Now there is no design window.
I am wondering that why the errors come automatically. I don't do anythings in the settings stuff of the studio. I just develop my app. I just write code and make my app. So whats wrong with the studio. It crashes without any reason and I have to waste the half of the time. Is this a kind of jokes? It too much irritating. Updating latest version is not the reason. The problem is occurring from whenever I downloaded the Android Studio and shifted from Eclipse to it. With 2 or 3 days intervals it comes with new problem.
I suggest you to try fresh Installation or, As it happens because of some internal Intellij's libraries problem.

Where is the graphical UI layout on Eclipse?

This is my first time writing Android app. When I downloaded the ADT bundle for the first time, everything went as planned according to the tutorial I followed. I was able to connect to my device and run my "hello world" app. Then, I closed Eclipse and later I came back to play around with Eclipse ide.
Now, I don't see any activity layout at all. I deleted my previous projects and created a new project hoping to see the activity layout or GUI for my device. I can't find it. I was planning on adding buttons or labels.
All I see is this message in the bottom:
This version of the rendering library is more recent than your version of ADT plug-in. Please update ADT plug-in
So, how do you enable or bring back the Activity layout.
Here is the screenshot:
You need to update your ADT Plugin in your Android SDK Manager to solve this problem.
These tools should be up to date

New Android Eclipse version won't get to workspace

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.

Android: Graphical Layout not working - doesn't show anything

My situation is: I once made an android project(2.2 version) but soon needed to format my computer. After formatting, I downloaded eclipse again but when I imported my project, I wasn't able to use the 'graphical layout' menu for xml. It doesn't show me anything like the picture below.
http://img525.imageshack.us/img525/3586/19978552.png
I cleaned the project and updated the Android SDK, however, none of these seemed to work well. What could be causing this?
Try restarting Eclipse. Usually that solves the problem for me when that happens.
Right click on your layout xml file and select Open With -> Android Layout Editor. It will force eclipse to open file in android's layout editor mode
None of above worked for me. what worked for me is:
1- Select a Google APIs Project Build Target rather than one of the Android X.X ones. This setting is in right click on project -> Properties->Android.
2- Make a change in XML and save it. Now switch back to "Graphical Layout" and it will show the layout.
For some, only 2nd step works.
This Question was asked 3 year ago, I am sure that you have get your solution, however i was also facing the same problem but got the solution in eclipse, here it is:-
1)Goto help->AboutEclipse->Installation details.
2)check the version of Android DDMS, Android development tool, Android hierarchy viewer, Android native development tool, Android trace view and tracer for openGl ES in installed software tab.
3)If they have different version than you have to update all of them.
4)Goto help->check for update in eclipse and follow the instruction.
5)Then restart eclipse.
This solve my problem.
The topic seems a little bit cold, but I wanted to add it nonetheless.
I had a similar problem with my layouts recently. When i create a project it automatically creates the layouts in the latest version of Android (eclipse shows it as version 22 of android as of today). But i can't see anything. So i just change the version to, say 18, and it shows ok. Furthermore if i want to change it back to version 22 it throws and exception, saying that a class can't be instantiated. (I am probably missing a class or a library on my system.)
Therefore if you cant see the layout it might be a good idea to switch back to earlier versions for development. cheers.

Can't preview Android XML layout - LayoutLib is too recent. Update your tool?

After upgrading the Android SDK through the AVD manager, I cannot preview XML layouts any longer in eclipse for Android 2.2 previews. Eclipse says, "LayoutLib is too recent. Update your tool!"
Using the drop-down and choosing any other platform works fine. Why is this happening for Android 2.2 previews?
I have also updated the ADT plugin for ecplise as well. Any suggestions?
This is a bug: http://code.google.com/p/android/issues/detail?id=17369
Updating from 10.0.1 to 12.0.0 resolved this issue for me.
In Eclipse, Help --> Check for updates
You'll likely see three items to be updated to 12.0.0+. Install, restart Eclipse, and the layout view should display without error.
More of a fix than an answer, or a fix with no explanation: r-click on the res\layout*.xml file you want to open, select Open with, then select Android Layout Editor. That should open the .xml in the graphical layout/design view you're used to.
For whatever reason, after updating from 10.0.1 to 12.0.0, my layout viewer default changed to XML Editor (one of the options under the context menu referenced above), and I have to manually open with different editor. Opening manually selecting Android Layout Editor seems to set ALE as the default for that .xml file going forward.
I had the same issue. Went in Eclipse->Help->CheckforUpdates. Selected everything there and hit next. Keep hitting next until finish. The update will start at the bottom right hand corner. Will also ask for permission. Press "OK". Will restart eclipse and problem is solved. I guess there was a bug with ADT but whatever this update fixed it.

Categories

Resources