android - 实际 Android 设备未找到 adb 设备

Question

我编写了一个简单的应用程序，想在我的 Samsung Galaxy i9000 上试用一下。在找到合适的 USB 驱动程序遇到一些麻烦后，我终于让设备显示在设备管理器中的 Android Phone/Android 复合 ADB 接口(interface)下。我运行的是 Vista SP1，我的手机是带有 2.1-update1 的 Samsung Galaxy i9000。

我遇到的问题是在 cmd 中运行“adb servies”时，设备列表为空，并且该设备未显示在 Eclipse 中。

• 手机处于开发者(调试)模式
• 我在 list 文件中为应用程序添加了 android:debuggable="true"
• 我已经多次尝试在 cmd 提示符下终止并重新启动 adb，但没有结果
• 我已经多次重启手机和电脑
• 在安装正确的驱动器之前使用 usddeview 完全删除以前的驱动器

我在命令提示符中运行了以下命令:

• adb kill-server
• 设置 ADB_TRACE=all
• adb 节点守护进程服务器

然后我运行 Eclipse 并得到这个(不要介意奇怪的 sdk 路径 :P):

C:\Program Files\JCreatorV4LE\Android\android-sdk-windows\tools>adb kill-server

C:\Program Files\JCreatorV4LE\Android\android-sdk-windows\tools>set ADB_TRACE=al
l

C:\Program Files\JCreatorV4LE\Android\android-sdk-windows\tools>adb nodaemon ser
ver
bit_buffer_init 002A2780
bit_buffer_init 002A37C0
adb_socketpair: returns (100, 101)
fdevent_update: add 1 to 101
event_looper_hook: call hook for 101 (new=0, old=1)
transport: local client init
Created device thread
transport: client_socket_thread() starting
socket_loopback_server: port 5037 type tcp => fd 102
fdevent_update: add 1 to 102
event_looper_hook: call hook for 102 (new=0, old=1)
_event_socketpair_start: hook 101(pair:100) for 65 wanted=1
_event_socket_start: hooking 102(lo-server:5037) for 1 (flags 41)
adb_win32: waiting for 2 events
socket_loopback_client: could not connect to tcp:5555
socket_loopback_client: could not connect to tcp:5557
socket_loopback_client: could not connect to tcp:5559
socket_loopback_client: could not connect to tcp:5561
socket_loopback_client: could not connect to tcp:5563
socket_loopback_client: could not connect to tcp:5565
socket_loopback_client: could not connect to tcp:5567
socket_loopback_client: could not connect to tcp:5569
socket_loopback_client: could not connect to tcp:5571
socket_loopback_client: could not connect to tcp:5573
socket_loopback_client: could not connect to tcp:5575
socket_loopback_client: could not connect to tcp:5577
socket_loopback_client: could not connect to tcp:5579
socket_loopback_client: could not connect to tcp:5581
socket_loopback_client: could not connect to tcp:5583
socket_loopback_client: could not connect to tcp:5585
adb_win32: got one (index 1)
_event_socket_check 102(lo-server:5037) returns 1
adb_win32: signaling 102(lo-server:5037) for 1
adb_socket_accept on fd 102 returns fd 119
LS(1): created (fd=119)
Connecting to smart socket
Creating smart socket
SS(0): created 00407E60
fdevent_update: add 1 to 119
event_looper_hook: call hook for 119 (new=0, old=1)
SS(0): enqueue 16
SS(0): len is 12
SS(0): 'host:version'
writex: 119 0022CCA8 12: 4f4b41593030303430303161  OKAY0004001a
writex: 119 ok
SS(0): handled host service 'version'
SS(0): closed
adb_close: 119(accept:102(lo-server:5037))
LS(1): closed
_event_socketpair_start: hook 101(pair:100) for 65 wanted=1
adb_win32: waiting for 2 events
adb_win32: got one (index 1)
_event_socket_check 102(lo-server:5037) returns 0
adb_win32: waiting for 2 events
adb_win32: got one (index 1)
_event_socket_check 102(lo-server:5037) returns 1
adb_win32: signaling 102(lo-server:5037) for 1
adb_socket_accept on fd 102 returns fd 120
LS(2): created (fd=120)
Connecting to smart socket
Creating smart socket
SS(0): created 00407E60
fdevent_update: add 1 to 120
event_looper_hook: call hook for 120 (new=0, old=1)
_event_socketpair_start: hook 101(pair:100) for 65 wanted=1
_event_socket_start: hooking 120(accept:102(lo-server:5037)) for 1 (flags 41)
adb_win32: waiting for 3 events
adb_win32: got one (index 1)
_event_socket_check 102(lo-server:5037) returns 0
adb_win32: waiting for 3 events
adb_win32: got one (index 2)
_event_socket_check 120(accept:102(lo-server:5037)) returns 1
adb_win32: signaling 120(accept:102(lo-server:5037)) for 1
SS(0): enqueue 22
SS(0): len is 18
SS(0): 'host:track-devices'
device tracker 002A6D98 created
LS(0) bound to 'track-devices'
SS(0): okay
SS(0): closed
LS(2): enqueue 4
_event_socketpair_start: hook 101(pair:100) for 65 wanted=1
adb_win32: waiting for 3 events

这有什么意义吗？我花了几个小时试图解决这个问题，所以任何建议都是值得赞赏的。

/约翰

Answer 1

当我更新 android sdk 工具时，我有一个相同类型的设备没有检测到问题。在搜索互联网和引用其他资源后，我发现 sdk 更新过程已经替换了位于用户的.android文件夹中的adb_usb.ini文件配置文件 文件夹。然后我将我的设备的 USB 驱动程序 key (随驱动程序安装程序文件夹一起提供)添加到该 adb_usb.ini 文件中。然后我使用以下命令重新启动了 adb 服务器。

adb kill-server

adb 启动服务器

然后检测到设备，我已经解决了我的问题。我希望这会解决您的问题..