Android sdk content loader at 0%... and nothing works

Question

Sorry if I'm asking this the wrong way (if I am, let me know what I should be doing instead.) The site warned me not to leave this as an answer and I don't have enough rep to add a comment, so I'm doing a new post.

Basically, I am having the exact same problem as this poster: Getting error message "Android sdk content loader stuck at 0%"

That is, when I open Eclipse it shows the message "Android sdk content loader 0%", and so my projects refuse to build. But I have tried ALL the responses listed there: turning off build automatically, cleaning all projects, deleting my debug keystore, deleting the adb process in the Activity Monitor (I'm on a Mac), switching workspaces, renaming projects, shutting Eclipse down and restarting it. I also made sure to install the latest version of the SDK (4.2, API 17, Jelly Bean). My phone was not plugged into the computer in the first place. I even deleted and reinstalled the ADT. And I STILL get the same problem. Please, somebody, tell me what's going wrong and how I can fix it.

Answer 1

Below scenario will work.

Go to your workspace directory \workspace\.metadata\.plugins\org.eclipse.core.resources\\.projects

1. Copy .projects folder and take backup for temporary.
2. Now Delete .projects folder from workspace directory. (you will not loose your projects)
3. Start Eclipse and wait for all progress ends at right/bottom corner. Once completed all processes, shutdown Eclipse.
4. Paste .projects folder which you have backup earlier to \workspace\.metadata\.plugins\org.eclipse.core.resources\ directory. Overwrite existing .projects folder.
5. Start Eclipse again. And all will work.

In above scenario Eclipse will automatically finds your projects as earlier. You do not have to import manually.

Working for me.

Answer 2

this worked for me: (the third one always works but its possible the first two work too)

first try this approach:

shut down eclipse then go to YourWorkSpace\\.metadata\\.plugins\org.eclipse.e4.workbench and remove "workbench.xmi", now restart eclipse.

if the previous approach did not work try this one:

go to Users\YOUR_USER_NAME\\.android and then delete "ddms.cfg" and then restart eclipse.

if this one did not work either the final approach will help you which is:

1- before running eclipse go to your workspace and remove one project that is no longer needed (if you face this problem frequently try to import a project before closing the eclipse in order to remove it the next time you want to use eclipse again)

2-go to Users\YOUR_USER_NAME\\.android and then delete "ddms.cfg"

3- run eclipse and you are good to go

Answer 3

I myself ran into this issue, and what have I not tried, all the possible stackoverflow links. None helped.

While eclipse is running and showing me the stupid "Android content (killing me:)".I started the task manager , and I saw adb, cmd.exe is running. Killed it. And voila!.

Answer 4

I closed all open projects before the progress status could get to "Android sdk content loader 0%" and then opened them one by one. Fortunately the problem got resolved.

Answer 5

As others have noted there is a couple other answers which may solve your problem. However they did not work for me but I did manage to find a work around for my particular issue which may help someone.

I believe my issue was with the proxy server at work. While you can configure the proxy in the SDK manager you can't enter the credentials for it to save.

My workaround was to tether my work laptop to my phone WiFi hotspot when I started up Eclipse so it could bypass the work proxy, then use the normal work network after that.