Open GoogleCodeExporter opened 9 years ago
I can confirm this same error on Kaiser natively running OpenEclair 1.2.2 with
our
2.6.25 kernel.
Original comment by doublere...@gmail.com
on 19 Mar 2010 at 4:44
This has nothing to do with androidscreencast -- adb itself cannot connect to
the device, and so cannot execute anything there etc. You need to first make
sure that e.g. the following works by itself:
adb -s <device-id> shell ls
If someone somehow built Android for that device, there has to be a working adb
for it. Reboot everything, download the latest adb from the HTC site, or get
adb from someone who is known to develop for the device. You may also need to
install special USB drivers on your computer for that type of device.
Original comment by k...@google.com
on 23 Jul 2010 at 11:45
Adb works great on that device, the only problem is it identifies it as ??????,
but it works.
andrea@aolivato:~$ adb devices
List of devices attached
???????????? device
andrea@aolivato:~$ adb shell uptime
11:49:56 up 17:31, load average: 7.61, 7.62, 7.81
Original comment by embrace....@gmail.com
on 23 Jul 2010 at 11:50
Is there (after one year) any possibility to rename a device or specifty a name
for the device?
Original comment by friehm...@googlemail.com
on 14 Mar 2011 at 4:59
Im using a Huawei u8220. I can connect to the phone with ./adb shell
but i get this when i try ./adb devices:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
???????????? device
Then when i try to open adroidScreencast i get this:
10:33 E/DeviceMonitor: Connection attempts: 1
10:34 E/DeviceMonitor: Connection attempts: 2
10:35 E/DeviceMonitor: Connection attempts: 3
10:36 E/DeviceMonitor: Connection attempts: 4
10:37 E/DeviceMonitor: Connection attempts: 5
10:38 E/DeviceMonitor: Connection attempts: 6
10:39 E/DeviceMonitor: Connection attempts: 7
10:40 E/DeviceMonitor: Connection attempts: 8
10:41 E/DeviceMonitor: Connection attempts: 9
10:42 E/DeviceMonitor: Connection attempts: 10
10:43 E/DeviceMonitor: Connection attempts: 11
10:43 E/adb: Cannot start adb when AndroidDebugBridge is created without the
location of adb.
10:43 E/DeviceMonitor: adb restart attempts: 1
net.sourceforge.jnlp.LaunchException: Fatal: Launch Error: Could not launch
JNLP file.
at net.sourceforge.jnlp.Launcher.launchApplication(Launcher.java:469)
at net.sourceforge.jnlp.Launcher$TgThread.run(Launcher.java:732)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at net.sourceforge.jnlp.Launcher.launchApplication(Launcher.java:461)
... 1 more
Caused by: 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)
... 6 more
Caused by:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at net.sourceforge.jnlp.Launcher.launchApplication(Launcher.java:461)
at net.sourceforge.jnlp.Launcher$TgThread.run(Launcher.java:732)
Caused by: 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)
... 6 more
cleaning up...
cleanup done, exiting...
Any Help?
Original comment by macha...@gmail.com
on 10 Apr 2011 at 7:09
Original issue reported on code.google.com by
embrace....@gmail.com
on 9 Mar 2010 at 4:58