Updating and diagnosing adb

[Michael Wallstedt]

We're running into a couple of issues with adb:

1) We're attempting to forward the adb port over ssh between machines. This works in most cases, but sometimes it fails, and in the process brings down the adb process on the receiving machine. Are there any logs we could look at (on a linux environment) to get more detail?

2) Some users have version 1.0.32 while others have 1.0.31. Attempts to upgrade to 1.0.32 haven't worked. The SDK manager believes there are no updates, even if we completely shutdown adb before launching the SDK manager.

Any help is appreciated.

[Siva Velusamy]

On Wed, Jan 21, 2015 at 6:15 PM, Michael Wallstedt <mikewa...@google.com> wrote:

We're running into a couple of issues with adb:

1) We're attempting to forward the adb port over ssh between machines. This works in most cases, but sometimes it fails, and in the process brings down the adb process on the receiving machine. Are there any logs we could look at (on a linux environment) to get more detail?

$ adb kill-server

$ export ADB_TRACE=all

$ adb server nodaemon 2>&1 | tee /tmp/log

 

2) Some users have version 1.0.32 while others have 1.0.31. Attempts to upgrade to 1.0.32 haven't worked. The SDK manager believes there are no updates, even if we completely shutdown adb before launching the SDK manager.

$ grep Pkg.Revision ~/android/sdk/platform-tools/source.properties

and make sure it returns 21, which is the latest as of now. In the worst case, just "rm -rf $sdk/platform-tools", then relaunch sdk manager and install platform-tools 21.

 

Any help is appreciated.

--
You received this message because you are subscribed to the Google Groups "adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to adt-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.