I have the same problem and on my phones, it seems to be related to
the absence of a SIM card on the phone. I am using two development
phones, without SIM cards in them. On these phones, I have No route
to host exception. I then put SIM cards in the phones, and the
problem disappeared. I am still
yup..you can refer to the localhost by this ip--10.0.2.2
This is because when you are specifying localhost to the device/
emulator it is a reference to the phone\emulator itself and not the
local machine
read this too--http://developer.android.com/guide/appendix/faq/
Mine is happening on Live devices so I guess I spoke too soon.
On Thu, Jan 7, 2010 at 3:27 AM, g...@devicedriven ginokur...@gmail.comwrote:
yup..you can refer to the localhost by this ip--10.0.2.2
This is because when you are specifying localhost to the device/
emulator it is a reference to
I don't get it. I'm having this issue in the emulator. Is this an
emulator only issue or it affects real devices too? This used to not
do this, did a recent SDK update break this functionality?
On Jan 6, 8:28 pm, Wayne Wenthin wa...@fuligin.com wrote:
You are not alone. I have this every once
OKOK, I think I found out what the issue is, but can't explain why. I
was trying to connect to a webservice located on the same machine as
the emulator was running. I tried referring to the local machine by IP
and by name, but I always get the no route to host error. But when I
connect to the same
For connecting to the localhost of your machine, you should not use
127.0.0.1
You can use the IP instead, or Please read up the docs.
http://developer.android.com/guide/developing/tools/emulator.html#networkinglimitations
Check for the section.Network Address Space
Thanks and Regards,
Kumar
6 matches
Mail list logo
