Getting error message “Android sdk content loader stuck at 0%”

Question

When I open Eclipse it shows the message Android sdk content loader 0%. How to solve this? I have turned off project build automaticaly and cleaned all

Answer 1

I've had this problem and the solution for me was the same as the answer I posted here:

Eclipse hangs at the Android SDK Content Loader

which is to delete this file:

 /workspace/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi

Your workbench starts over (return to default layout, settings for AVD's are gone, path to keystores, etc.) but that's not a big deal compared to getting back to work...

Answer 2

Tried all of the suggestions but none seemed to work. This is the workflow that ultimately fixed it for me, not sure why, but it did (finally!). Hope it helps some one!

1. Open Eclipse
2. Go to Preferences->General->Workspace->Startup and Shutdown->Unselect 'Android Development Kit'
3. Restart Eclipse completely
4. File->Switch Workspace (select a new empty folder as the new workspace)
5. Restart Eclipse completely
6. Go to Preferences->General->Workspace->Startup and Shutdown->Select 'Android Development Kit'
7. Restart Eclipse completely
8. File->Switch Workspace (select your previous workspace).

Answer 3

Have you tried deleting your debug keystore?

%USERPROFILE%/.androidon Windows
~/.android/debug.keystore on Linux and Mac OS X

Answer 4

This has been a frequent, yet inconsistent problem for me lately. For a while I was turning off the Build Automatically option and closing/re-opening projects. But I also ran into cases where it would lock up before I could change settings.

Ultimately I discovered that switching workspaces (temporarily) would get it going again. I now have a dummy workspace with a Hello World project in it. So now I:

1. Kill Eclipse
2. Open Eclipse to the dummy workspace.
3. Switch workspaces to your desired workspace.

This is the most efficient way I've found to work-around this.

Answer 5

After trying all options here, 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.