Adb server is out of date killing как исправить

If you are debugging your Android app on a phone or a tablet
over USB, you might get
the following message shown every time you (or your debugging
tool) runs ADB:

adb server is out
of date. killing…
* daemon started successfully *

Or even worse:

adb server is out
of date. killing…
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon

The message will make every small operation involving ADB
last 3-5 seconds, making deployment annoyingly slow and failing
most of the times.

This happens because your phone sync application (e.g. HTC
Sync) has its own version of
adb.exe that is incompatible with Android SDK. Every
time you connect your phone to a USB port, the sync application will try to
start its own version of adb.exe interfering
with your one.

The solution

A trivial solution would be to find the old adb.exe
(e.g.
C:Program Files (x86)HTCHTC Sync 3.0adb.exe) and
delete it.
However, this would break the sync application functionality.

To make things better we have developed ADBFix — a small tool
that you can download from this page. The tool
will detect the older instances of adb.exe that
are conflicting with Android SDK and replace them with a stub.
The stub will always run the adb.exe from
Android SDK instead, so no conflicts will arise.

To fix the «adb server is out of date» bug, please follow
these steps:

1. Connect your device to the USB port
2. Download and run ADBFix.
3. Specify the location of your Android SDK.
4. Ensure that ADBFix finds the conflicting version of
   adb.exe:
5. Press «Fix all». Ensure that the conflict is marked as
   «fixed»:
6. Note that you can always roll back the fix by selecting
   an ADB instance and pressing «Restore original ADB».

The internals

When you start the tool, it will search for all instances of
adb.exe running (and potentially causing future
«adb server out of date» messages) and compare their versions
with the version of adb.exe from Android SDK. If a version
mismatch is found, the tool will rename the old adb.exe
to adb_conflicting_backup.exe and put a
shortcut to the adb.exe from SDK in place of the old adb.exe.

Thus, both Android SDK and your sync application (e.g. HTC
Sync) will use the same version of adb.exe causing no more
conflicts.

Note that when you click «Fix All» you will see the «adb
server is out of date» message, as adbfix will have to stop the
old adb.exe. Once it’s successfully stopped, the the new version
will be used and the annoying message won’t bother you again.

Download

License

ADBFix is free for commercial and non-commercial use.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS «AS IS» AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.

Popular posts from this blog

Introduction

If you have been debugging some Android apps on an HTC phone, you have probably noticed the annoying message that is shown when you try to debug a phone over USB on a computer running HTC Sync:

adb server is out of date. killing...
* daemon started successfully * 

The message is usually accompanied by 3-5 seconds of waiting time and can appear several times before you manage to start debugging. The worst thing is that sometimes it does not manage to restart  the daemon and aborts the launching after 10-20 seconds of waiting with a message like that:

adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon

Although the problem seems almost random, there is a simple explanation to it and a clean way of fixing it.

ADB stands for Android Debug Bridge. It is a tool that is used by Android environment to do a variety of tasks: list connected devices, transfer files between them, establish TCP/IP connections… The last feature is directly used by the HTC Sync application to communicate with the phone over USB.

Let’s now see what exactly happens when you connect your phone and try to debug it.

1. HTC Sync (more specifically, htcUPCTLoader.exe continuously running in the background) detects that you have connected a device and tries to forward a TCP/IP port to it. To do so, it runs the adb.exe from its own folder and tells it to start mapping the port. The adb.exe keeps on running in the background providing the port map for HTC Sync.
2. When you start debugging with the Android SDK, it does several minor jobs (e.g. lists devices, deploys your App, etc) each involving a call to its own adb.exe. When this happens, the newer adb.exe detects that the older adb.exe from HTC Sync is running and terminates it, then it runs its own instance.
3. The HTC Sync running in the background detects that the port mapping has been broken and tries to restart it. What happens then? Right, adb.exe from Android SDK gets kicked off. If this happens before the adb.exe from SDK manages to complete, you get an error message and your debugging fails. 

The Solution 

First of all, we need to find the old instance of adb.exe that interferes with Android SDK. This can be done by opening Task Manager, finding adb.exe there and selecting “Properties”. Do not forget to connect your phone to USB before doing that.

A trivial solution then would be to delete/rename the adb.exe used by HTC Sync. However, this would break HTC Sync.

Another one is to kill or suspend htcUPCTLoader.exe for the time you are debugging your app. This will prevent it from interfering with the adb.exe from the Android SDK.

Finally, you can make a simple stub that reads the location of the real ADB.exe from the Registry and runs it with the original command line:

#include "stdafx.h"
#include <bzscore/Win32/registry.h>

using namespace BazisLib;

int _tmain(int argc, _TCHAR* argv[])
{
    wchar_t *p = GetCommandLineW();
    if (p[0] == '"')
        p = wcschr(p+1,'"');
    else
        p = wcschr(p, ' ');

    if (!p)
        p = L"";
    else
        p+=2;

    wchar_t *pwsz = new wchar_t[512 + wcslen(p)];

    String ADBPath = RegistryKey(HKEY_CURRENT_USER, 
      L"SOFTWARE\Sysprogs\ADBFix", 0, false)[L"SDKPath"];

    if (ADBPath.empty())
        ADBPath = L"adb_noadbfix.exe";
    else
        ADBPath += L"\platform-tools\adb.exe";

    swprintf(pwsz, L""%s" %s", ADBPath.c_str(), p);
    STARTUPINFO info = {sizeof(info), };
    PROCESS_INFORMATION PI;
    CreateProcess(0, pwsz, 0, 0, 0, 0, 0, 0, &info, &PI);
    WaitForSingleObject(PI.hProcess, INFINITE);
    DWORD exitCode = -1;
    GetExitCodeProcess(PI.hProcess, &exitCode);
    return exitCode;
}

You can rename the adb.exe in the HTC Sync directory to adb_noadbfix.exe and put the stub instead of the original file.