Timeout getting device list

[GoogleCodeExporter]

Device name : Nexus One
Device rooted (yes/no) : No
Device OS version (1.5/1.6/2.0,...) : 2.1

Computer OS and version (Mac,Win,Linux,...) : Windows 7
Java version (java -version from command line) : 1.6.0_18
ADB version (adb version from command line) : 1.0.25
AndroidScreencast version : 2010.04.07

What steps will reproduce the problem?
1. run javaws androidscreencast.jnlp
2. you get the following exception
java.lang.RuntimeException: Timeout getting device list!
    at net.srcz.android.screencast.Main.waitDeviceList(Main.java:86)
    at net.srcz.android.screencast.Main.initialize(Main.java:37)
    at net.srcz.android.screencast.Main.<init>(Main.java:25)
    at net.srcz.android.screencast.Main.main(Main.java:107)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.sun.javaws.Launcher.executeApplication(Unknown Source)
    at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
    at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
    at com.sun.javaws.Launcher.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)

What is the expected output? What do you see instead?

Please provide any additional information below.

Original issue reported on code.google.com by alexda...@gmail.com on 6 Apr 2010 at 11:54

[GoogleCodeExporter]

I am encountering the same issue on Windows XP when attempting to connect with 
my 2.1 
droid.  It seemed to occur after installed the Motoral USB driver.  Before I 
installed 
that driver it would at least bring up the screen that showed the device list.  
I have 
uninstalled the driver but still no luck.

Original comment by tim.chap...@gmail.com on 9 Apr 2010 at 6:55

[GoogleCodeExporter]

Somehow this problem was resolved for me when I installed the application / 
driver that 
comes with EasyTether.  (EasyTether is also a bad A$$ way to get internet to 
your 
laptop).  

Original comment by tim.chap...@gmail.com on 9 Apr 2010 at 9:42

[GoogleCodeExporter]

have you tried updating sdk : specially  usb driver package revision 3 ?

Original comment by cools.jo...@gmail.com on 22 Apr 2010 at 8:57

[GoogleCodeExporter]

Same issue:
Device name : HTC Hero
Device rooted (yes/no) : Yes
Device OS version (1.5/1.6/2.0,...) : 2.1

Computer OS and version (Mac,Win,Linux,...) : Windows 7 x64
Java version (java -version from command line) : 1.6.0_17 (& _20)
ADB version (adb version from command line) : 1.0.25
AndroidScreencast version : 2010.04.07

Also have usb driver package revision 3 - reinstalled driver just to be sure 
and same
output

Original comment by bobthede...@gmail.com on 28 Apr 2010 at 5:51

[GoogleCodeExporter]

yeah same here on droid eris, this doesnt seem to work..

Original comment by william....@gmail.com on 29 Apr 2010 at 11:23

[GoogleCodeExporter]

My computer OS is Ubuntu 10.04.
I can launch the jnlp file at the first time,but after i restart my computer, i 
just
can not launch it again when attempting to connect with the emulator.
Also the same problem!

Original comment by Janet.W...@technicolor.com on 21 May 2010 at 7:13

Attachments:

• snapshot17.jpeg

[GoogleCodeExporter]

Oh,Yeah!!! I had solved the problem!
I use ./adb devices to check the devices status.
I use the command twice and when the attached change from offline to device, the
problem just solved, just as follow picture:

Original comment by Janet.W...@technicolor.com on 21 May 2010 at 7:59

Attachments:

• snapshot18.jpeg

[GoogleCodeExporter]

and on windows ? xD

Original comment by neoproph...@gmail.com on 1 Aug 2010 at 3:22

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

How do you restart the server in windows CMD

Original comment by AAMi...@gmail.com on 12 Aug 2010 at 9:36

[GoogleCodeExporter]

In the cmd window u must be in the tools folder for any adb commands to work.
I had the sdk folder on my desktop so i ran cmd then "cd desktop" then "cd 
android-sdk_r06-windows" then "cd android-sdk_r06-windows" then "cd tools"
Now you will be in the tools directory.
Just type "adb usb" this will reset the server and everything works great.

Original comment by AAMi...@gmail.com on 18 Aug 2010 at 12:02

[GoogleCodeExporter]

Thank you for the "adb usb" command, that did the trick! 

Original comment by dramo...@gmail.com on 5 Apr 2011 at 8:45

[GoogleCodeExporter]

that did the trick for me too!  Also, rebooting phone works too but I wanted to 
avoid that.  Thanks!

Original comment by drummy....@gmail.com on 23 Sep 2011 at 3:35

[GoogleCodeExporter]

Thanks for your comment. It works with me. :)
Thanks!

Original comment by nhuy...@gmail.com on 5 Jul 2012 at 6:56

[GoogleCodeExporter]

thank u very much....worked for me too

Original comment by chetanun...@gmail.com on 26 Oct 2012 at 11:51

[GoogleCodeExporter]

cd C:\android-sdk-windows\tools didn't work for me, it looks like the file was 
moved to \sdk\platform-tools - after switching there the adb command worked and 
i was no longer getting a timeout error.

Original comment by Surfin....@gmail.com on 3 Dec 2012 at 5:34

[GoogleCodeExporter]

ADB USB worked fine here too

Original comment by maycke...@gmail.com on 15 Apr 2013 at 11:37

[GoogleCodeExporter]

This worked great for me as well.  Helpful hint.  If you left-shift + 
right-click on the tools folder you can open the command prompt right in that 
folder instead of all the steps to get to it within the command prompt.

Original comment by sheryl.h...@gmail.com on 13 Jun 2013 at 2:06

[GoogleCodeExporter]

Thank you. "adb usb" worked.

Original comment by giuliano...@gmail.com on 13 Dec 2013 at 5:40