我刚刚在linux上安装了SDK。我之前使用过它,因为去年我做了一些Android工作,当时我对这些工具没有任何问题。adb永远等待运行模拟器
但是当前安装不会安装到仿真器上。 avd
被激发起来的模拟器运行:
> adb devices
List of devices attached
emulator-5554 device
> adb install blahblah.apk
error: protocol fault (no status)
- waiting for device -
挂起,直到我杀了它。然后:
> adb devices
List of devices attached
> adb kill-server
> adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
> adb devices
List of devices attached
emulator-5554 device
> adb -s emulator-5554 install blahblah.adk
error: protocol fault (no status)
- waiting for device -
我一定经历了十几次这样的正常用户和root用户。我读this Q&A,并尝试与ADB_TRACE
相同的东西。当杀死并重新启动服务器这使得一个奇怪的差异:在没有跟踪
> adb start-server
system/core/adb/adb.c::main():Handling commandline()
system/core/adb/adb_client.c::_adb_connect():_adb_connect: host:version
system/core/adb/adb_client.c::adb_connect():adb_connect: service host:start-server
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
,它总是“守护进程启动成功”。但随后的adb devices
再次显示模拟器。 “:协议故障(无状态)错误”:
system/core/adb/transport.c::readx():readx: fd=3 disconnected
system/core/adb/adb_client.c::adb_connect():adb_connect: return fd -1
error: protocol fault (no status)
然后“等待装置”之前:现在试图adb install
的之前产生丰富的调试输出,和右
system/core/adb/transport.c::readx():readx: fd=3 wanted=4 got=4
4641494c FAIL
system/core/adb/transport.c::readx():readx: fd=3 wanted=4
system/core/adb/transport.c::readx():readx: fd=3 wanted=4 got=4
30303130 0010
system/core/adb/transport.c::readx():readx: fd=3 wanted=16
system/core/adb/transport.c::readx():readx: fd=3 wanted=16 got=16
646576696365206e6f7420666f756e64 device not found
system/core/adb/adb_client.c::switch_socket_transport():Switch transport failed
system/core/adb/adb_client.c::adb_connect():adb_connect: return fd -1
我还没有发现任何类似报道上线。
只是一个旁注:你试过genymotion?如果它工作,你可以节省时间修复这个问题+有一个更好的AVD! – bofredo
您可以尝试使用sudo运行启动服务器。 – skywall
正如前面提到的,我试图以普通用户和root用户身份进行操作。 @bofredo感谢您的提示。 – delicateLatticeworkFever