Accepted answer

had the same 27% problem with an emulator. it only got fixed after i deleted the avd and recreated it, so this is very likely device/emulator related (and furthermore restarting the adb did not fix the problem).


found this over at project pages as issue #21073, answered by benpar:

update: this scenario can also be avoided if the avd emulator is launched from the avd manager within eclipse. the issue happens when launching the first emulator from the run button in eclipse.

to avoid:

  1. start eclipse
  2. window -> avd manager
  3. start an emulator
  4. run the project


for me it was the adb which had hung. no amount of quitting either eclipse or the emulator had any effect.

  1. terminate the emulator
  2. terminate the adb, (i simply killed its process using task manager.
  3. start the emulator again, (also causes the adb to restart)
  4. run your program

it should no longer get stuck.


i was using samsung galaxy to run the app. i wasted a lot of time in running app but it was not launching and i had to restart eclipse every time. for me, i just follow these steps and there was no problem any more

  • removed my device from my pc
  • run the app
  • when it asks for attach your device or create avd.
  • i reconnect my device and select for output.
  • finally i resolved the issue


i got the solution of this problem bit silly one. what i did was started emulator from one instance of eclipse.. closed eclipse. closing eclipse wont stop the emulator. now re-launch eclipse. now run your application in the emulator already running.


very annoying problem. i was having to close down eclipse and the emulator and then start up again which became time consuming. came here and read what anna lear and vinay posted. worked! i think in my case this problem happened because i exited eclipse while the emulator was still running. to correct, as anna and vinay posted, do this...

make sure eclipse and emulator are shut down, then...

  1. start elipse
  2. start emulator
  3. quit eclipse (do not quit the emulator)
  4. start eclipse
  5. now run your program (should load 100% and not get stuck)


to get further information, try installing and launching the application from the command line outside of eclipse. you'll find your .apk in the /bin folder of your project, then use:

adb install -r <projectname>.apk

it may work and if not, you may get better information about the cause of the error. my experience with eclipse has shown that it can be finicky at times and this should help you isolate the issue.


i had the same stuck at 27% problem. unplugging the device and plugging it back in fixed it.


i've found that the quickest way is to check with the android debug bridge on the command line. sometimes all it takes is stopping and starting the adb server. that is:

adb kill-server

will stop the server. then:

adb start-server

that should do it. check the attached devices ( but it's not necessary )

adb devices

and it lists the devices attached.
then go back to eclipse and start debugging again.

this can also be done in the devices view through eclipse.


i also had this problem when running an application in the emulator. make sure the emulator is running before launching the app and you wont have this issue.

Related Query

More Query from same tag