尝试启动 Android 应用程序时 Eclipse 被卡住
我正在尝试在 Motorola Milestone A853 上运行 helloandroid 应用程序。我输入“adb devices”，手机被正确识别。然而，当我尝试运行应用程序时，Eclipse 总是停留在 27%“启动委托”。
可能是什么原因？
I'm trying to run helloandroid application on a Motorola Milestone A853. I typed "adb devices" and the mobile is properly recognized. However, when I try to run the application Eclipse always stuck at 27% "Launching delegate".
Which could be the reason?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（9）
使用模拟器也有同样的 27% 问题。它只有在我删除 AVD 并重新创建它后才得到修复，因此这很可能与设备/模拟器相关（而且重新启动 ADB 并没有解决问题）。
编辑：
在项目页面上找到此问题，问题为问题#21073，由 benpar 回答：
更新：如果从 Eclipse 中的 AVD 管理器启动 AVD 模拟器，也可以避免这种情况。从 Eclipse 中的“运行”按钮启动第一个模拟器时会出现此问题。
要避免：
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).
EDIT:
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:
在模拟器中运行应用程序时我也遇到了这个问题。确保模拟器在启动应用程序之前正在运行，这样就不会出现此问题。
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.
要获取更多信息，请尝试从 Eclipse 外部的命令行安装并启动应用程序。您将在项目的 /bin 文件夹中找到您的 .apk，然后使用：
它可能有效，如果无效，您可能会获得有关错误原因的更好信息。我使用 Eclipse 的经验表明，它有时可能很挑剔，这应该可以帮助您隔离问题。
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:
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.
我也遇到了同样的问题，卡在27%。拔下设备插头并将其重新插入即可修复。
I had the same stuck at 27% problem. Unplugging the device and plugging it back in fixed it.
我发现最快的方法是在命令行上检查 Android 调试桥。有时，只需停止并启动 adb 服务器即可。即：
adb Kill-server将停止服务器。然后：
adb start-server就可以了。检查连接的设备（但这不是必需的）
adb devices，它列出了连接的设备。
然后回到eclipse再次开始调试。
这也可以通过 Eclipse 在设备视图中完成。
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-serverWill stop the server. Then:
adb start-serverThat should do it. Check the attached devices ( but it's not necessary )
adb devicesand 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.
我得到了这个问题的解决方案，有点愚蠢。我所做的是从 Eclipse 的一个实例启动模拟器。关闭 Eclipse。关闭 eclipse 不会停止模拟器。现在重新启动 Eclipse。现在在已经运行的模拟器中运行您的应用程序。
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.
非常烦人的问题。我不得不关闭 eclipse 和模拟器，然后再次启动，这变得非常耗时。来到这里阅读安娜·李尔和维奈发布的内容。成功了！我认为就我而言，这个问题发生是因为我在模拟器仍在运行时退出了 eclipse。要更正，正如 Anna 和 Vinay 发布的那样，执行以下操作...
确保 Eclipse 和模拟器已关闭，然后...
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...
对我来说，是亚行挂了。退出 Eclipse 或模拟器的次数没有任何影响。
它应该不再卡住。
For me it was the ADB which had hung. No amount of quitting either eclipse or the emulator had any effect.
It should no longer get stuck.
我使用 Samsung Galaxy 来运行该应用程序。我在运行应用程序上浪费了很多时间，但它没有启动，我每次都必须重新启动 Eclipse。
对我来说，我只需按照这些步骤操作，就没有问题了，
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