Whenever I try to run adb devices
:
$ adb devices * daemon not running. starting it now * * daemon started successfully * List of devices attached HT0ANRV05740 device
It says daemon is not running and restarts the daemon.
Then, if I run adb devices again, it does the same thing -
$ adb devices adb server is out of date. killing... * daemon started successfully * List of devices attached HT0ANRV05740 device
Then, if I run it again, it again does the exact same thing -
$ adb devices adb server is out of date. killing... * daemon started successfully * List of devices attached HT0ANRV05740 device
Please help!!
Also, my DDMS keeps giving me the following message -
[2011-02-23 16:17:05 - DeviceMonitor]Adb connection Error:An existing connection was forcibly closed by the remote host
Here are the logs from just before adb restarts -
1291 locapi_rpc_glue V loc_ioctl 1291 RPC D written RPC packet size: [480] 1291 RPC D read RPC packet 1291 RPC D read RPC packet size: [28] 1291 lib_locapi V qct_loc_eng_inject_xtra_data, inject part = 100, len = 167, len = 167 1291 lib_locapi V qct_loc_eng_inject_xtra_data, total part = 100, len = 167 1291 locapi_rpc_glue V loc_ioctl 1291 RPC D written RPC packet size: [248] 1291 RPC D read RPC packet 1291 RPC D read RPC packet size: [28] 1291 lib_locapi D qct_loc_eng_inject_xtra_data: injected 39767, SUCCESS 1291 lib_locapi V inject_xtra_waiting = flase 1291 GpsLocationProvider D Releasing wakelock 1291 WifiService D releaseWifiLockLocked: WifiLock{NetworkLocationProvider type=2 binder=android.os.Binder@47aead50} 1291 WifiService D enable and start wifi due to updateWifiState 1218 rmt_storage I rmt_storage open event 1218 rmt_storage I rmt_storage client thread started 1218 rmt_storage I rmt_storage events processing done 1218 rmt_storage I rmt_storage register cb event 1218 rmt_storage I rmt_storage status id = 2 1218 rmt_storage I rmt_storage events processing done 1218 rmt_storage I rmt_storage open event 1218 rmt_storage I rmt_storage client thread started 1218 rmt_storage I rmt_storage events processing done 1218 rmt_storage I rmt_storage register cb event 1218 rmt_storage I rmt_storage status id = 2 1218 rmt_storage I rmt_storage events processing done 1218 rmt_storage I rmt_storage write event 1218 rmt_storage I unblock rmt_storage client thread 1218 rmt_storage I rmt_storage events processing done 1218 rmt_storage I rmt_storage write: bytes written = 3145216 1218 rmt_storage I rmt_storage write: bytes written = 512 1218 rmt_storage I rmt_storage status handle = 1 1291 BatteryStatsImpl I notePhoneSignalStrengthLocked: 4->3 1218 rmt_storage I rmt_storage write event 1218 rmt_storage I rmt_storage events processing done 1218 rmt_storage I unblock rmt_storage client thread 1291 PowerManagerService D New lightsensor value:40, lcdValue:143 1291 PowerManagerService D lightSensorChangedLocked, buttonValue >= 0, mPowerState = 3 1218 rmt_storage I rmt_storage write: bytes written = 3145216 1218 rmt_storage I rmt_storage write: bytes written = 512 1218 rmt_storage I rmt_storage status handle = 2 1291 RPC D read RPC packet 1291 RPC D read RPC packet size: [80] 1291 locapi_rpc_glue V Callback received: 80 (cb_id=0x50B0000 handle=1) 1291 RPC D written RPC packet size: [28] 1470 usicWidgetController D unbindMusicPlaybackService() 1707 MediaPlaybackService E BadQueue mPlayListLen : 0 mAlbumListLen : 0 mShrinkAlbumListLen : 0 1291 NotificationService V Battery Full, Charging 1291 lights E write ok string=0,len=1 1291 lights E write ok string=0,len=1 1291 lights E write ok string=0 0,len=3 1291 lights E write ok string=1,len=1 1707 MediaPlayer.java D setOnCompletionListener being cleaned to null 1291 lights E write ok string=0,len=1 1291 lights E write ok string=0 0,len=3 1291 NotificationService V Turn off Jogball/OJ LED 1291 NotificationService D cancelNotification, ACTION_NOTIFICATION_REMOVE,pkg=com.htc.music,id=1 1291 AudioService I AudioFocus abandonAudioFocus() from android.media.AudioManager@476ddee0com.htc.music.MediaPlaybackService$5@476dd838
The adb command facilitates a variety of device actions, such as installing and debugging apps, and it provides access to a Unix shell that you can use to run a variety of commands on a device. It is a client-server program that includes three components: A client, which sends commands.
In tools menu,Android-> untick enable adb Integration and Then OPEN widows task manager n manually end process adb.exe This also solved my issue as der were multiple adb.exe running. Show activity on this post. Restart the computer. Now, disconnect the device, connect it, Make sure USB debugging Option is enabled.
Are you using Genymotion for a virtual device?
if yes this error probably came out because ADB from Genymotion conflicted with your ADB from Android SDK(using same port number), to fix this simply go to settings
=> choose ADB
tab => click on the option Use custom Android SDK Tools
and set your SDK folder
after you configure this, try to restart your adb by going into folder platform-tools
which adb
placed and do this command:
./adb kill-server
./adb start-server
*tips: You may close the process of Genymotion before running the command above
Hope this help.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With