cannot connect to freerunner android

[Vimal Joseph]

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
[hidden email]
https://lists.openmoko.org/mailman/listinfo/support

[ran]

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
[e-mail]
https://lists.openmoko.org/mailman/listinfo/support

I have dual-boot ( SHR/Android ) system and I am using eth1 for connection in SHR and eth2 for connection in Android. Check, please, may be you will be able do same.

[François-Léonard Gilbert]

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 <[hidden email]> 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
[hidden email]
https://lists.openmoko.org/mailman/listinfo/support

_______________________________________________
support mailing list
[hidden email]
https://lists.openmoko.org/mailman/listinfo/support

[Vimal Joseph]

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


_______________________________________________
support mailing list
[hidden email]
https://lists.openmoko.org/mailman/listinfo/support

[rakshat]

On Wed, Sep 16, 2009 at 11:17 AM, Vimal Joseph <[hidden email]> 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
[hidden email]
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
[hidden email]
https://lists.openmoko.org/mailman/listinfo/support

[Vimal Joseph]

On Wed, 2009-09-16 at 11:32 +0530, rakshat hooja wrote:

>
>
> # 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

I tried this, but no results:

root@gnubox:~# ifconfig eth2 192.168.0.200 netmask 255.255.255.0
root@gnubox:~# adb kill-server
root@gnubox:~# ADBHOST=192.168.0.202 adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached

root@gnubox:~# ADBHOST=192.168.0.202 adb shell
error: device not found


regards,

~vimal


_______________________________________________
support mailing list
[hidden email]
https://lists.openmoko.org/mailman/listinfo/support

[Fabian Rami]

Some javascript/style in this post has been disabled (why?)

I have had similar problem on Gentoo.
try this :

export ADBHOST=192.168.0.202

adb kill-server
adb devices

Vimal Joseph a écrit :

On Wed, 2009-09-16 at 11:32 +0530, rakshat hooja wrote:

  

# 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
    

I tried this, but no results:

root@gnubox:~# ifconfig eth2 192.168.0.200 netmask 255.255.255.0
root@gnubox:~# adb kill-server
root@gnubox:~# ADBHOST=192.168.0.202 adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached 

root@gnubox:~# ADBHOST=192.168.0.202 adb shell
error: device not found


regards,

~vimal
  

_______________________________________________
support mailing list
[hidden email]
https://lists.openmoko.org/mailman/listinfo/support
  

_______________________________________________
support mailing list
[hidden email]
https://lists.openmoko.org/mailman/listinfo/support

[raghav.moko]

The key thing is to have the USB cable connected to the Freerunner before you start booting the Freerunner.

So,
1. Connect the USB cable to the FR.
2. Boot the FR into Android.
3. Try the ADBHOST thing.

-raghav

On Wed, Sep 16, 2009 at 1:44 PM, Fabian Rami (via Nabble) <[hidden email]> wrote:

I have had similar problem on Gentoo.
try this :

export ADBHOST=192.168.0.202

adb kill-server
adb devices

Vimal Joseph a écrit :

On Wed, 2009-09-16 at 11:32 +0530, rakshat hooja wrote:

  

# 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
    

I tried this, but no results:

root@gnubox:~# ifconfig eth2 192.168.0.200 netmask 255.255.255.0
root@gnubox:~# adb kill-server
root@gnubox:~# ADBHOST=192.168.0.202 adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached 

root@gnubox:~# ADBHOST=192.168.0.202 adb shell
error: device not found


regards,

~vimal
  

_______________________________________________
support mailing list
[hidden email]
https://lists.openmoko.org/mailman/listinfo/support
  

-- 
______________________
Fabian Rami
Département WebMobile
Ligne dir : [phone]
http://www.webmobile.be

WOW Company
Rue Pieds d'Alouette 18
5100 NANINNE (Belgique)
Tel :  [phone]
Fax : [phone]
http://www.wowcompany.com
______________________ 

_______________________________________________
support mailing list
[hidden email]
https://lists.openmoko.org/mailman/listinfo/support

[telpe]

raghav.moko wrote:

The key thing is to have the USB cable connected to the Freerunner before
you start booting the Freerunner.

So,
1. Connect the USB cable to the FR.
2. Boot the FR into Android.
3. Try the ADBHOST thing.

-raghav

On Wed, Sep 16, 2009 at 1:44 PM, Fabian Rami (via Nabble) <
[e-mail]<[e-mail]>
> wrote:

> I have had similar problem on Gentoo.
> try this :
>
> export ADBHOST=192.168.0.202
>
> adb kill-server
> adb devices
>
>
>
>
>
> Vimal Joseph a écrit :
>
> On Wed, 2009-09-16 at 11:32 +0530, rakshat hooja wrote:
>
>
>
>  # 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
>
>
>  I tried this, but no results:
>
> root@gnubox:~# ifconfig eth2 192.168.0.200 netmask 255.255.255.0
> root@gnubox:~# adb kill-server
> root@gnubox:~# ADBHOST=192.168.0.202 adb devices
> * daemon not running. starting it now *
> * daemon started successfully *
> List of devices attached
>
> root@gnubox:~# ADBHOST=192.168.0.202 adb shell
> error: device not found
>
>
> regards,
>
> ~vimal
>
>
> ------------------------------
>
> _______________________________________________
> support mailing list[hidden email] <http://n2.nabble.com/user/SendEmail.jtp?type=node&node=3654786&i=0>https://lists.openmoko.org/mailman/listinfo/support
>
>
>
> --
> ______________________
> Fabian Rami
> Département WebMobile
> Ligne dir : [phone]http://www.webmobile.be
>
> WOW Company
> Rue Pieds d'Alouette 18
> 5100 NANINNE (Belgique)
> Tel :  [phone]
> Fax : [phone]http://www.wowcompany.com
> ______________________
>
>
>
>
> _______________________________________________
> support mailing list
> [hidden email]<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=3654786&i=1>
> https://lists.openmoko.org/mailman/listinfo/support
>
>
> ------------------------------
>  View message @
> http://n2.nabble.com/cannot-connect-to-freerunner-android-tp3650157p3654786.html
> To unsubscribe from Openmoko Public Mailinglists, click here< (link removed) =>.
>
>
>

 # ifconfig eth2 192.168.0.200 netmask 255.255.255.0
 # ./adb kill-server
 # ADBHOST=192.168.0.202 ./adb devices