Re: cannot connect to freerunner android
On Wed, Sep 16, 2009 at 11:17 AM, Vimal Joseph wrote: > On Tue, 2009-09-15 at 13:49 -0400, François-Léonard Gilbert wrote: > > Android has no SSH server. It is possible that you could access your > > phone using adb, wich is part of the Android dev kit. Since it does > > not work well in OS X I couldn't try it, so YMMV. > > Thanks, i tried adb, but i cannot even ping to 192.168.0.202 (which is > suppose to be the phone IP). The Debian detects the phone and load the > usb eth module properly and showed the device eth1. > > Thanks and regards, > > ~vimal > Have you done this - 3 adb connects to Android but you need to set up Android on FreeRunner first, otherwise you may skip this step. This will not work on other distributions. Make sure your FreeRunner was booted while being plugged in to a USB port. If you have flashed a *Uboot*, run the following commands in Terminal: # ifconfig usb0 192.168.0.200 netmask 255.255.255.0 # adb kill-server # ADBHOST=192.168.0.202 adb devices If you have installed Qi loader, find on which eth device the FreeRunner is located (for me, it is eth2). # ifconfig -a Then, issue the following (if you have *Qi*, and whether you found your eth for FreeRunner. For me it is eth2): # ifconfig eth2 192.168.0.200 netmask 255.255.255.0 # adb kill-server # ADBHOST=192.168.0.202 adb devices Note the part about booting with USB plugged in. Last time i tried beta 7 adb worked fine. Rakshat > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > > -- -- Please use Firefox as your web browser. Its protects you from spyware and is also a very feature rich browser. www.firefox.com ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: cannot connect to freerunner android
On Tue, 2009-09-15 at 13:49 -0400, François-Léonard Gilbert wrote: > Android has no SSH server. It is possible that you could access your > phone using adb, wich is part of the Android dev kit. Since it does > not work well in OS X I couldn't try it, so YMMV. Thanks, i tried adb, but i cannot even ping to 192.168.0.202 (which is suppose to be the phone IP). The Debian detects the phone and load the usb eth module properly and showed the device eth1. Thanks and regards, ~vimal signature.asc Description: This is a digitally signed message part ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: cannot connect to freerunner android
Android has no SSH server. It is possible that you could access your phone using adb, wich is part of the Android dev kit. Since it does not work well in OS X I couldn't try it, so YMMV. On Tue, Sep 15, 2009 at 12:31 PM, Vimal Joseph wrote: > Hi, > > I installed the beta 7 of koolu android. When connecting to the usb, it > shows as eth1. I set the IP of eth1 as 192.168.0.200 but i cant connect > to 192.168.0.202 as mentioned > http://wiki.openmoko.org/wiki/Android_on_Freerunner > > Is there anything to do on the phone settings? I'm using debian lenny > and neo freerunner. > > thanks and regards, > > ~vimal > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
cannot connect to freerunner android
Hi, I installed the beta 7 of koolu android. When connecting to the usb, it shows as eth1. I set the IP of eth1 as 192.168.0.200 but i cant connect to 192.168.0.202 as mentioned http://wiki.openmoko.org/wiki/Android_on_Freerunner Is there anything to do on the phone settings? I'm using debian lenny and neo freerunner. thanks and regards, ~vimal signature.asc Description: This is a digitally signed message part ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
