I do not own an Android phone and am working exclusively in the Eclipse/emulator environment on my laptop.
When I type in the "adb shell" cmd from the tools directory I get very inconsistent results.
Sometimes it says "error: device not found".
Sometimes it says "error: device offline".
If I start a small application and continue to type in the "adb shell" command until the emulator starts I get the 2 errors I just mentioned in that order and then the "adb shell" command actually works and I can see the "#" prompt, and type in commands such as "ls -l" and see the results.
Then as I'm working in the shell it suddenly ends and I'm back at the Windows prompt.
I am running on Windows XP Pro Version 2002 Service Pack 3.
I would very much appreciate some help with this situation.
I think you should get those messages only when there are no instances of emulator or device running and talking with adb. Even with the device/emulator connected, chances are that adb is losing connection with them. Usually, I do one of adb reset/Kill-server/start-server to restore normalcy.
Chris Trout wrote:I'm also wondering if I have the most current versions of "adb" and the other tools.
Do you know how I can ensure that I do?
You should periodically run the "android" executable in the tools folder of the SDK. Click on "Available Packages" and then select the Google server - that will start a search for updates. There was an update of the Android 2.2 API just this week, but the last Tools update was a couple of months ago, along with the original Android 2.2 release.
Ping & DNS - updated with new look and Ping home screen widget