我写了一个简单的应用程序,想在我的三星Galaxy i9000上试用一下。经过一番找寻正确的USB驱动程序后,我终于在设备管理器中找到了Android Phone/Android Composite ADB Interface下的设备。我正在运行Vista SP1,我的手机是一个带有2.1-update1的三星Galaxy i9000。
我的问题是,在cmd中运行“adb services”时,设备列表为空,并且该设备没有出现在Eclipse中。
以下是我已经尝试过的解决方法:
- 手机处于开发者(调试)模式 - 我已经在清单文件中为应用程序添加了android:debuggable="true" - 我已经尝试了多次在cmd提示符中杀死并重新启动adb,但没有结果 - 我已经多次重启手机和电脑 - 在安装正确的驱动程序之前,使用了ussdeview彻底删除了先前的驱动程序
我在命令提示符中运行了以下命令:
- adb kill-server - set ADB_TRACE=all - adb nodaemon server 然后我运行了Eclipse,并得到了以下结果(不要在意奇怪的sdk路径:P):
这有意义吗?我已经花了数小时来尝试弄清楚这个问题,所以非常感谢您的任何建议。
/Johan
我的问题是,在cmd中运行“adb services”时,设备列表为空,并且该设备没有出现在Eclipse中。
以下是我已经尝试过的解决方法:
- 手机处于开发者(调试)模式 - 我已经在清单文件中为应用程序添加了android:debuggable="true" - 我已经尝试了多次在cmd提示符中杀死并重新启动adb,但没有结果 - 我已经多次重启手机和电脑 - 在安装正确的驱动程序之前,使用了ussdeview彻底删除了先前的驱动程序
我在命令提示符中运行了以下命令:
- adb kill-server - set ADB_TRACE=all - adb nodaemon server 然后我运行了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
这有意义吗?我已经花了数小时来尝试弄清楚这个问题,所以非常感谢您的任何建议。
/Johan