adb always showing device is offline

[DigitalVision]

Hi There

I dn loaded the latest android-x86 and build and install the iso_img
using qemu, I am having 2 problems

1. My browser is connecting any websites(if I run android from
hardisk, if I use run android with out installing, i can browse any
websites).
2. i ran the adb to tunnel into my device ,but my adb always showing
device offline for
adb devices.

if any one tried the adb with android-x86 image, pls help with some
instructions on HOW TO use adb with android-x86.

Thanks
Srini

[beyounn]

On Sep 22, 9:06 am, DigitalVision <samgo1...@gmail.com> wrote:
> Hi There
>
> I dn loaded the latest android-x86 and build and install the iso_img
> using qemu, I am having 2 problems
>
> 1. My browser is connecting any websites(if I run android from
> hardisk, if I use run android with out installing, i can browse any
> websites).

What is the problem?

> 2. i ran the adb to tunnel into my device ,but my adb always showing
> device offline for
>        adb devices.
>

Have you do adb kill-server? And if you are running ubuntu, you need
to use sudo

[DigitalVision]

On Sep 22, 9:43 am, beyounn <beyo...@gmail.com> wrote:
> On Sep 22, 9:06 am, DigitalVision <samgo1...@gmail.com> wrote:> Hi There
>
> > I dn loaded the latest android-x86 and build and install the iso_img
> > using qemu, I am having 2 problems
>
> > 1. My browser is connecting any websites(if I run android from
> > hardisk, if I use run android with out installing, i can browse any
> > websites).
>
> What is the problem

srini : When launch the browser, a pop-up message box comming up with
" No network connection" message.

[beyounn]

1. were you be able to access internet after dismissed the error
message?
2. which build are you using (the build number)
3. could you send me the logcat output after boot up?
Yi

[DigitalVision]

On Sep 22, 11:02 am, beyounn <beyo...@gmail.com> wrote:
> 1. were you be able to access internet after dismissed the error
> message?

No, I am not able to access the internet, after I dismiss the error.

> 2. which build are you using (the build number)

I dont know the build #, but I dn loaded the code from android-x86.org
on Sep 21,2009(i.e y'day)

> 3. could you send me the logcat output after boot up?

I am not able connect my device thru adb, how can I get the logcat.

[beyounn]

You have a network issue here. Be cause the network issue, you can not
run adb anyway.

Can you go to alt-f1 to see if you have a correct network device by
runing netcfg? It seems that ethernet code can not handle your
ethernet device correct.

[DigitalVision]

Hi beyounn

when run netcfg i see only

lo UP 1127.0.x.x does it mean it is not configured properly, sorry I
dont have much knowledge with network.

[Yi Sun]

It seems that you don't have ethernet device at all. Have you passed -net options to qemu? Please take a look at http://www.android-x86.org/documents/qemuhowto for detail

--
Android-x86
http://www.android-x86.org

[DigitalVision]

Yes I tried with -net option, I still see the same problem.

On Sep 22, 1:34 pm, Yi Sun <beyo...@gmail.com> wrote:
> It seems that you don't have ethernet device at all. Have you passed -net

> options to qemu? Please take a look athttp://www.android-x86.org/documents/qemuhowtofor detail

[beyounn]

Could you try VirtualBox? I don't have a Qemu installed, but ethernet
works very well on virtualbox

[DigitalVision]

HI

Yes I tried the virtualBox and ethernet work fine with virtualbox, I
can even ping my device from my host console, but still adb is not
working.

this is what I have

export ADBHOST=<ip address>
adb shell
error: device not found.

[beyounn]

adb kill-server before you do anything else.Also, may sure you are
using 1.6 sdk.

BTW-- I had some issues sometime to connect to my device even I can
see it and I don't have time to debug it yet.

[DigitalVision]

I did tried adb kill-server and adb devices, and I am using 1.6 ,
still I see the same problem.

[Yi Sun]

A basic question, can you really ping your virtualbox machine?

--
Android-x86
http://www.android-x86.org

[Yi Sun]

For everyone's benefit, here is the steps I did to hook up the adb:
1. start VirtualBox and config the network to host interface
2. boot up the android
3. you should see your ip address in the notification bar is your ethernet started in the Android
4. ping the ipaddress of android from your host machine
5. you should be able to ping it.
6. on your host machine (assume it is the machine you build android-x86), go to android-x86-build-dir/out/host/linux-x86/bin/
7. ./adb kill-server
8. ./adb connect <ipaddress of android>:5555, you should see something below:
yisun@ysun-desktop:~/android/0911/out/host/linux-x86/bin$ ./adb connect 192.168.0.158:5555
* daemon not running. starting it now *
* daemon started successfully *
connected to 192.168.0.158:5555

9. ./adb shell
Yi

--
Android-x86
http://www.android-x86.org

[DigitalVision]

Hi Yi

Sorry for the late reply, i am having typical problem, I am not able
to ping my virtual device from my host, but I can ping my host from my
Android device(with virtualbox).

Here is the what I am using:
host os : ubuntu 9.04(32bit)
VirtualBox : 2.1.4
Android distro : Android-x86(1.6 based)

As you said in the instructions I tried to install my device with
HostInterface as network option in virtualbox,but if I do this my
there is no network connection in my Android & if I open browser it is
saying there is " No netwrok connection"

On Sep 23, 11:11 am, Yi Sun <beyo...@gmail.com> wrote:
> For everyone's benefit, here is the steps I did to hook up the adb:
> 1. start VirtualBox and config the network to host interface
> 2. boot up the android
> 3. you should see your ip address in the notification bar is your ethernet
> started in the Android
> 4. ping the ipaddress of android from your host machine
> 5. you should be able to ping it.
> 6. on your host machine (assume it is the machine you build android-x86), go
> to android-x86-build-dir/out/host/linux-x86/bin/
> 7. ./adb kill-server
> 8. ./adb connect <ipaddress of android>:5555, you should see something
> below:
> yisun@ysun-desktop:~/android/0911/out/host/linux-x86/bin$ ./adb connect
> 192.168.0.158:5555
> * daemon not running. starting it now *
> * daemon started successfully *
> connected to 192.168.0.158:5555
>
> 9. ./adb shell
> Yi
>
>
>
> On Wed, Sep 23, 2009 at 11:02 AM, Yi Sun <beyo...@gmail.com> wrote:
>
> > A basic question, can you really ping your virtualbox machine?
>

[beyounn]

Another basic question:
do you have a DHCP server in the network that your ubuntu connected
to?

[DigitalVision]

I am using my personal laptop & it is not connected to any network.

[beyounn]

Then you need to manually configure your ethernet to an address that
is in the same subnet as your host.

[DigitalVision]

Thanks for all the help, it works fine now.