adb服务器版本与此客户端不匹配 [英] adb server version doesn't match this client
本文介绍了adb服务器版本与此客户端不匹配的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！
问题描述
每当我尝试运行 adb设备：
$ adb设备
*守护程序未运行。立即启动*
*守护程序成功启动*
连接的设备列表
HT0ANRV05740设备
它表示守护程序未运行，然后重新启动该守护程序。
然后，如果我再次运行adb设备，它也会做同样的事情-
$ adb设备
adb服务器已过期。杀死...
*守护程序成功启动*
连接的设备列表
HT0ANRV05740设备
然后，如果我再次运行它，它将再次执行完全相同的操作-
$ adb devices
adb服务器已过期。杀死...
*守护程序成功启动*
连接的设备列表
HT0ANRV05740设备
请帮忙！
此外，我的DDMS不断给我以下消息-
[2011-02-23 16:17:05-DeviceMonitor] Adb连接错误：远程主机<已强制关闭现有连接/ pre>
以下是adb重新启动之前的日志-
1291 locapi_rpc_glue V loc_ioctl
1291 RPC D写入的RPC数据包大小：[480]
1291 RPC D读取的RPC数据包
1291 RPC D读取的RPC数据包大小：[28]
1291 lib_locapi V qct_loc_eng_inject_xtra_data，注入部分= 100，len = 167，len = 167
1291 lib_locapi V qct_loc_eng_inject_xtra _data，总部分数= 100，len = 167
1291 locapi_rpc_glue V loc_ioctl
1291 RPC D写入的RPC数据包大小：[248]
1291 RPC D读取RPC数据包
1291 RPC D读取RPC数据包大小：[28]
1291 lib_locapi D qct_loc_eng_inject_xtra_data：注入39767，成功
1291 lib_locapi V inject_xtra_waiting = flase
1291 GpsLocationProvider D释放唤醒锁
1291 WifiService D releaseWifiLocked： {NetworkLocationProvider type=2inder=android.os.Binder@47aead50}
1291 WifiService D由于updateWifiState
而启用并启动wifi $ 12 $ 1218 rmt_storage我rmt_storage打开事件
1218 rmt_storage我rmt_storage客户端线程已启动
1218 rmt_storage我完成了rmt_storage事件处理
1218 rmt_storage我完成了rmt_storage寄存器cb事件
1218 rmt_storage我rmt_storage状态ID = 2
1218 rmt_storage我rmt_storage事件处理了
1218 rmt_storage我完成了事件
1218 rmt_storage我rmt_storage客户端线程已启动
1218 rmt_storage我rmt_storage事件处理完成
1218 rmt_storage我rmt_storage寄存器cb事件
1218 rmt_storage我rmt_storage状态ID = 2
1218 rmt_storage我完成了rmt_storage事件处理
1218 rmt_storage我完成了rmt_storage写事件
1218 rmt_storage我取消了rmt_storage客户端线程
1218 rmt_s torage我rmt_storage事件处理完成
1218 rmt_storage我rmt_storage写：写入的字节= 3145216
1218 rmt_storage我rmt_storage写入：字节= 512
1218 rmt_storage我rmt_storage状态句柄= 1
1291 BatteryStatsImpl I notePhoneSignalStrengthLocked：4-> 3
1218 rmt_storage我rmt_storage写事件
1218 rmt_storage我rmt_storage事件处理完成
1218 rmt_storage我取消阻止rmt_storage客户端线程
1291 PowerManager lightsensor值：40，lcdValue：143
1291 PowerManagerService D lightSensorChangedLocked，buttonValue> = 0，mPowerState = 3
1218 rmt_storage我rmt_storage写：写的字节= 3145216
1218 rmt_storage I rmt_存储写入：字节写入= 512
1218 rmt_storage I rmt_storage状态句柄= 2
1291 RPC D读取RPC数据包
1291 RPC D读取RPC数据包大小：[80]
1291 locapi_rpc_glue V收到的回调：80（cb_id = 0x50B0000处理= 1）
1291 RPC D写入的RPC数据包大小：[28]
1470 usicWidgetController D unbindMusicPlaybackService（）
1707 MediaPlaybackService E BadQueue mPlayListLen：0 mAlbumListLen ：0 mShrinkAlbumListLen：0
1291 NotificationService V电池已满，正在充电
1291灯E写入ok字符串= 0，len = 1
1291灯E写入ok字符串= 0，len = 1
1291灯E写入ok字符串= 0 0，len = 3
1291灯E写入o k字符串= 1，len = 1
1707 MediaPlayer.java D setOnCompletionListener被清除为空
1291灯E写入ok字符串= 0，len = 1
1291灯E写入ok字符串= 0 0，len = 3
1291 NotificationService V关闭Jogball / OJ LED
1291 NotificationService D cancelNotification，ACTION_NOTIFICATION_REMOVE，pkg = com.htc.music，id = 1
1291 AudioService I AudioFocus abandonAudioFocus（ ）从android.media.AudioManager @ 476ddee0com.htc.music.MediaPlaybackService $ 5 @ 476dd838
解决方案您是否在虚拟设备上使用Genymotion？
如果是，此错误可能是由于Genymotion的ADB与Android SDK的ADB冲突（使用相同的端口号），要解决此问题，只需转到
设置=>选择ADB选项卡=>单击选项使用c ustom Android SDK工具并设置您的SDK文件夹
配置此选项后，尝试进入文件夹
platform-tools放置adb并执行以下命令：
-
./ adb kill-server -
./ adb启动服务器
*提示：您可以在运行上述命令之前关闭Genymotion进程
希望获得帮助。
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
解决方案
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.
这篇关于adb服务器版本与此客户端不匹配的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
查看全文
