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 projects in workspace too.

Could someone tell me why I am getting this error?

This is not fun. Possibly try exiting eclipse and re-starting. Worst case, deleting the metadata from the workspace and recreating the project(s) does it, perhaps someone knows something more precisely targeted. — Chris Stratton, Apr 28 '12 at 05:32
I have found that the solution here worked for me: http://stackoverflow.com/questions/13489141/eclipse-hangs-at-the-android-sdk-content-loader/15670474#15670474 — MikeR, Jul 18 '13 at 19:00
The above link did not solve, So I found this http://stackoverflow.com/a/23251804/756218 , and trust me , the easiest and a working solution — Abhiram mishra, Apr 23 '14 at 18:09

Hulk · Answer 1 · 2014-04-02T06:19:22.163

23

Go in the task manager and delete the adb process..then restart you eclipse...

OR

Open adb shell with path: sdk/plateform-tools/

Give command: SDK\android-sdk-windows\platform-tools>adb kill-server

press enter

Again give command: SDK\android-sdk-windows\platform-tools>adb start-server

press enter

This will restart your adb..Good luck!!

edited Apr 02 '14 at 06:19

answered Apr 28 '12 at 05:42

Hulk

2,565
16
24

2

This corrected this issue for me! I would select this answer as the solution to my problem. – HeatfanJohn Feb 06 '13 at 17:13

score 23 · Answer 2 · answered Feb 28 '13 at 06:46

23

I too faced similar issue.. I tried many things but none worked.. But then I tried deleting cache folder & ddms.cfg file from %USERPROFILE%/.android folder and from then on it started working properly..

answered Feb 28 '13 at 06:46

Veer

2,071
19
24

1

This should be marked as answer. After so many "eclipse -clean", remove debug.keystore, restarts, adb kills, etc.. only this worked – Miguel Ribeiro Apr 24 '13 at 09:28
Yeah, this is the perfect solution for this issue. – roy mathew Oct 11 '13 at 08:49
I did not try other solutions, but this one seemed to be a shorter one, and it worked for me too! – Akash Saikia Apr 09 '14 at 06:21

score 16 · Accepted Answer · answered Apr 28 '12 at 05:47

16

Have you tried deleting your debug keystore?

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

answered Apr 28 '12 at 05:47

choop

921
2
9
28

No i dint do anything !!! but some how its working now..weired!! Thanks for all repliys – Apr 28 '12 at 07:43
1

After this, I had to start eclipse twice, create a new project (importing failed), then I can finally see my older projects. – Stephen J Jun 09 '14 at 07:24
Really nice. after have tried all solution this only works for me. – Pratik Butani Dec 13 '14 at 05:02
Eclipse is like an old dog from the streets. If you clean (bathe) it, it may die. – Josh Sep 10 '15 at 08:49

score 14 · Answer 4 · answered Sep 19 '13 at 09:57

None of the above worked for me - but I found another way to get around this.

In eclipse preferences, go to General/Workspace and click the 'Startup and Shutdown' option. In the dialog that opens unselect 'Android Development Toolkit' (and while you're at it maybe uncheck all the other annoying things eclipse does at start up).
Restart eclipse and you'll find your Android projects don't work but you don't get the non=progressing content loader initialization.
Go back to the General/Workspace/'Startupand shutdown' dialog and enable it again.
Restart eclipse once more and after cleaning and rebuilding you may find its all okay for again (was for me).

Worked for me! in addition to this i close most of the open projects and all opened classes after the first run without the 'android development toolkit'. then i restarted eclipse still without the toolkit to see if my closed projects will be saved. they were saved then i re-enable the 'android development toolkit' and worked just fine again — r_19, Oct 30 '14 at 23:22

score 4 · Answer 5 · answered Apr 16 '13 at 10:08

4

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.

answered Apr 16 '13 at 10:08

scar

191
1
2
8

score 3 · Answer 6 · answered Jul 01 '14 at 12:48

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).

score 2 · Answer 7 · edited May 23 '17 at 11:44

2

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...

edited May 23 '17 at 11:44

Community

1
1

answered Oct 09 '14 at 21:31

Jim

10,172
1
27
36

Worked for me on Eclipse Juno 4.2.2 with ADT, no problems with stuck SDK content loader since then. – user1398498 Mar 06 '15 at 17:05

score 1 · Answer 8 · answered Jan 02 '13 at 19:58

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:

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

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

score 1 · Answer 9 · answered Jan 30 '13 at 20:51

1

Maybe this would be helpful for someone.

If you cannot kill the adb process in Windows Manager, unplug your phone from the usb port. Then you can stop adb, restart Eclipse and everything works again :) at least in my case.

answered Jan 30 '13 at 20:51

Pablo

9
4

score 0 · Answer 10 · answered Nov 23 '12 at 05:11

0

I had the same problem after I tried to add a project from existing code. I shut the eclipse down and removed the project to another address. I don't know what the problem was but it solved it!

answered Nov 23 '12 at 05:11

ANemati

4,766
3
20
13

score 0 · Answer 11 · answered Dec 20 '12 at 14:27

In my case I renamed every project folder in the workspace (suffixed folder names with _), then opened workspace and it finished its stupid tasks, then closed eclipse, then renamed the few project folders I really need back to their original folder names, then File > Refresh (keeping the projects that still had renamed folders), then right-click on each project and 'Open Project...'. Saved the day.

Getting error message "Android sdk content loader stuck at 0%"

11 Answers11

Linked