Re: Android: can't connect to adb
you didn't forget enabling usb debugging? Greetings Serdar Am 10.05.10 08:40, schrieb Radek Polak: > On Saturday 08 May 2010 04:32:22 Leonti Bielski wrote: > > >> To summarize - I get a couple of seconds of using the ADB before >> connection is lost again :( >> >> Has anyone experienced this weird problem? >> > Just general help: > > - Try another cable > - Try another USB port - USB ports soldered on motherboard work better. > > Maybe it helps, > > Radek > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Android: can't connect to adb
On Saturday 08 May 2010 04:32:22 Leonti Bielski wrote: > To summarize - I get a couple of seconds of using the ADB before > connection is lost again :( > > Has anyone experienced this weird problem? Just general help: - Try another cable - Try another USB port - USB ports soldered on motherboard work better. Maybe it helps, Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Android: can't connect to adb
I'm taking my words back about good ping to 192.168.0.202 :( Turns out the connection is extremely unstable. I can ping the phone just after I connect to it or reconnect the cable. I get a couple of pings and than "Destination Host Unreachable". For example: From 192.168.0.200 icmp_seq=5 Destination Host Unreachable From 192.168.0.200 icmp_seq=6 Destination Host Unreachable 64 bytes from 192.168.0.202: icmp_seq=16 ttl=64 time=5.20 ms From 192.168.0.200 icmp_seq=70 Destination Host Unreachable From 192.168.0.200 icmp_seq=71 Destination Host Unreachable From 192.168.0.200 icmp_seq=72 Destination Host Unreachable From 192.168.0.200 icmp_seq=73 Destination Host Unreachable That time when I received data from phone I replugged the cable. To summarize - I get a couple of seconds of using the ADB before connection is lost again :( Has anyone experienced this weird problem? Leonti On Sat, May 8, 2010 at 2:34 AM, Leonti Bielski wrote: > Hello! > > I've just installed Android 0.2.0RC1 from: > > http://code.google.com/p/android-on-freerunner/downloads/list > > I can ping 192.168.0.202 alright. > > I enabled adb access on the phone using the guide: > http://code.google.com/p/android-on-freerunner/wiki/AndroidDebugBridge > > But when I run: > ADBHOST=192.168.0.202 adb devices > List of devices attached > > List is empty. > > Are there any additional steps to get ADB working? > > Thanks, > Leonti > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Android: can't connect to adb
Hello! I've just installed Android 0.2.0RC1 from: http://code.google.com/p/android-on-freerunner/downloads/list I can ping 192.168.0.202 alright. I enabled adb access on the phone using the guide: http://code.google.com/p/android-on-freerunner/wiki/AndroidDebugBridge But when I run: ADBHOST=192.168.0.202 adb devices List of devices attached List is empty. Are there any additional steps to get ADB working? Thanks, Leonti ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
