Actual Android device not found adb devices -


i have written simple app , try out on samsung galaxy i9000. after trouble finding proper usb-driver have device show in device manager under android phone/android composite adb interface. running vista sp1 , phone samsung galaxy i9000 2.1-update1.

the problem i'm having when running "adb servies" in cmd device list empty, , device not showing in eclipse.

  • the phone in developer (debug) mode
  • i have added android:debuggable="true" app in manifest-file
  • i have tried several times kill , restart adb in cmd-prompt without result
  • i have rebooted both phone , computer several times
  • used usddeview remove previous drives before installing proper ones

i ran following in commandprompt:

  • adb kill-server
  • set adb_trace=all
  • adb nodaemon server

then ran eclipse , got (never mind 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 101 event_looper_hook: call hook 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 102 event_looper_hook: call hook 102 (new=0, old=1) _event_socketpair_start: hook 101(pair:100) 65 wanted=1 _event_socket_start: hooking 102(lo-server:5037) 1 (flags 41) adb_win32: waiting 2 events socket_loopback_client: not connect tcp:5555 socket_loopback_client: not connect tcp:5557 socket_loopback_client: not connect tcp:5559 socket_loopback_client: not connect tcp:5561 socket_loopback_client: not connect tcp:5563 socket_loopback_client: not connect tcp:5565 socket_loopback_client: not connect tcp:5567 socket_loopback_client: not connect tcp:5569 socket_loopback_client: not connect tcp:5571 socket_loopback_client: not connect tcp:5573 socket_loopback_client: not connect tcp:5575 socket_loopback_client: not connect tcp:5577 socket_loopback_client: not connect tcp:5579 socket_loopback_client: not connect tcp:5581 socket_loopback_client: not connect tcp:5583 socket_loopback_client: not connect tcp:5585 adb_win32: got 1 (index 1) _event_socket_check 102(lo-server:5037) returns 1 adb_win32: signaling 102(lo-server:5037) 1 adb_socket_accept on fd 102 returns fd 119 ls(1): created (fd=119) connecting smart socket creating smart socket ss(0): created 00407e60 fdevent_update: add 1 119 event_looper_hook: call hook 119 (new=0, old=1) ss(0): enqueue 16 ss(0): len 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) 65 wanted=1 adb_win32: waiting 2 events adb_win32: got 1 (index 1) _event_socket_check 102(lo-server:5037) returns 0 adb_win32: waiting 2 events adb_win32: got 1 (index 1) _event_socket_check 102(lo-server:5037) returns 1 adb_win32: signaling 102(lo-server:5037) 1 adb_socket_accept on fd 102 returns fd 120 ls(2): created (fd=120) connecting smart socket creating smart socket ss(0): created 00407e60 fdevent_update: add 1 120 event_looper_hook: call hook 120 (new=0, old=1) _event_socketpair_start: hook 101(pair:100) 65 wanted=1 _event_socket_start: hooking 120(accept:102(lo-server:5037)) 1 (flags 41) adb_win32: waiting 3 events adb_win32: got 1 (index 1) _event_socket_check 102(lo-server:5037) returns 0 adb_win32: waiting 3 events adb_win32: got 1 (index 2) _event_socket_check 120(accept:102(lo-server:5037)) returns 1 adb_win32: signaling 120(accept:102(lo-server:5037)) 1 ss(0): enqueue 22 ss(0): len 18 ss(0): 'host:track-devices' device tracker 002a6d98 created ls(0) bound 'track-devices' ss(0): okay ss(0): closed ls(2): enqueue 4 _event_socketpair_start: hook 101(pair:100) 65 wanted=1 adb_win32: waiting 3 events 

this make sense? i've spent hours trying figure out suggestion @ appreciated.

/johan

i had same kind of device not detecting issue when have updated android sdk tools. after searching internet , referring other resources, found sdk update process had replaced adb_usb.ini file located in .android folder on user profile folder. have added usb driver keys device ( came driver installer folder ) adb_usb.ini file. have restarted adb server following commands.

adb kill-server

adb start-server

then device detected , have solved issue. hope fix issue..


Comments

Popular posts from this blog

android - Spacing between the stars of a rating bar? -

html - Instapaper-like algorithm -

c# - How to execute a particular part of code asynchronously in a class -