實際的Android設備找不到adb設備

Question

我已經寫了一個簡單的應用程序，並想在我的三星Galaxy i9000上試用它。在找到合適的USB驅動程序後，我終於在設備管理器的Android Phone/Android Composite ADB Interface下顯示設備。我運行的是Vista SP1，我的手機是2.1-update1的三星Galaxy i9000。

我遇到的問題是在cmd中運行「adb servies」設備列表爲空，並且設備未在Eclipse中顯示。

• 這款手機使用的是開發（調試）模式
• 我已經加入的android：可調試=「真」在清單文件的應用程序
• 我曾多次試圖殺死並重新啓動亞行沒有結果的CMD提示符
• 我已經重新啓動這兩個手機和計算機幾次
• 使用usddeview安裝了正確的人

之前完全刪除以前的驅動器

我跑在commandprompt如下：

• ADB殺服務器
• 集ADB_TRACE =所有
• ADB nodaemon服務器

然後我跑Eclipse和得到這個（從不介意wierd sdk-path：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更新過程已取代adb_usb.ini文件，該文件位於.android文件夾中的用戶配置文件文件夾中。然後，我已將我的設備（驅動程序安裝程序文件夾附帶的）的USB驅動程序密鑰添加到該adb_usb.ini文件。然後我用以下命令重新啓動了adb服務器。

ADB殺服務器

亞行啓動服務器

然後設備檢測，我已經解決了我的問題。我希望這可以解決你的問題。