ADB fails after sometime while running CTS

```
What steps will reproduce the problem?
1. start adb server (i.e. adb start-server)
2. start cts
3. run cts (i.e. start --plan CTS)

What is the expected output? What do you see instead?
After some tests have been run successfully, CTS lost connectivity
to the target. (see below)
android.view.cts.WindowTest#testSetWindowAnimations....(pass)
android.view.cts.WindowTest#testFinalMethod....(pass)

CTS_INFO >>> Max ADB operations reached. Restarting ADB...

CTS_INFO >>> Restarting device ...

CTS_INFO >>> Restart complete.

CTS_ERROR >>> Installing met timeout due to Unknown reason.

CTS_INFO >>> Max ADB operations reached. Restarting ADB...

CTS_INFO >>> Restarting device ...

CTS_INFO >>> Restart complete.

CTS_ERROR >>> Installing met timeout due to Unknown reason.

CTS_INFO >>> Max ADB operations reached. Restarting ADB...

CTS_INFO >>> Restarting device ...

CTS_INFO >>> Restart complete.

CTS_ERROR >>> Installing met timeout due to Unknown reason.

CTS_INFO >>> Max ADB operations reached. Restarting ADB...

CTS_INFO >>> Restarting device ...

CTS_INFO >>> Restart complete.

What version of the product are you using? On what operating system?
Using Android 2.1 on AM37x EVM

```

Original issue reported on code.google.com by `car...@gmail.com` on 14 Jul 2010 at 3:34

Start by reproducing the failure with `adb start-server`, CTS `start --plan CTS`, and the AM37x EVM setup described in the report. Investigate the CTS output around “Max ADB operations reached” and the installation timeout; done means CTS can continue running without repeatedly losing device connectivity.

Written by the indexing model from the issue text.