[android-developers] Re: Extremely long DNS lookup (and failure) on T-Mobile network

2009-12-18 Thread Albert
I am experiencing the same issue, i have been testing my app on my phone(HTC Hero 1.5) and it would give me a UnknownHostException from time to time, I can only fix it by restarting the phone. I hope they have a team working on this as this is very critical to the development on Android as it's not

[android-developers] Re: Extremely long DNS lookup (and failure) on T-Mobile network

2009-11-17 Thread Mark Wyszomierski
That's not good! Still hoping it's just something we're doing wrong. I tried using the connectivity manager. It reports that I have an available network etc. I tried running the route tests: ConnectivityManager cm = (ConnectivityManager) mContext.getSystemService(Context.CONNECTIVITY_SERVICE);

Re: [android-developers] Re: Extremely long DNS lookup (and failure) on T-Mobile network

2009-11-16 Thread SoftwareForMe.com SoftwareForMe.com
I have no idea, but I've also noticed the Browser taking an inordinately long time to fetch pages, the Android Market often failing, and other networking issues. I wonder why this doesn't seem to be more well known? Scott SoftwareForMe.com Makers of PhoneMyPC On Mon, Nov 16, 2009 at 3:12 PM, Mark

[android-developers] Re: Extremely long DNS lookup (and failure) on T-Mobile network

2009-11-16 Thread Mark Wyszomierski
I don't understand this - how are people getting around this? Restarting the app probably isn't too pleasant for the user! Thanks On Nov 15, 2:27 pm, "SoftwareForMe.com SoftwareForMe.com" wrote: > I have seen this too, but what's worse, I've found socket connections taking > to long to connect,

Re: [android-developers] Re: Extremely long DNS lookup (and failure) on T-Mobile network

2009-11-15 Thread SoftwareForMe.com SoftwareForMe.com
I have seen this too, but what's worse, I've found socket connections taking to long to connect, even when not using DNS. For example, our software can connect to a PC via LAN using an IP address. Sometimes it will take > 5 seconds, sometimes it will time out. In either case, after such a failure,

[android-developers] Re: Extremely long DNS lookup (and failure) on T-Mobile network

2009-11-15 Thread Mark Wyszomierski
How are you all getting around this issue? I am running into it on some phones given out as demos (G1s running 1.5). About 50% of the time, my network requests will just hang for about two minutes, then throw: java.net.UnknownHostException: Host is unresolved: myapi.me.com:80 this looks embarr

[android-developers] Re: Extremely long DNS lookup (and failure) on T-Mobile network

2009-10-26 Thread purvi
Hello, I am also facing the same problem. I am using a handler to fetch the data coming from the network request. I am thinking to throw an alert message to the user from my app indicating "No Response from Network" or "Network down" or somthing like that so that the user donot see any error and

[android-developers] Re: Extremely long DNS lookup (and failure) on T-Mobile network

2009-10-14 Thread tomei.ninge...@gmail.com
More info: I found out that the web site returns multiple IP addresses on the DNS lookup (see the "Resolving i2.sinaimg.cn line below). This appears to be for load balancing purposes. Could this be the reason that got Android confused? $ wget http://i2.sinaimg.cn/IT/2009/1014/20091014235428.jpg -

[android-developers] Re: Extremely long DNS lookup (and failure) on T-Mobile network

2009-10-14 Thread tomei.ninge...@gmail.com
My problem may not be the same. I got this only on actual G1 device, not on emulator. Also, if G1 is connect to my home WiFi network (comcast), the DNS for i0.sinaimg.cn is resolved without any problem. However, if I disconnect Wifi and use TMO USA 3G network, the DNS never resolves. On Oct 14,

[android-developers] Re: Extremely long DNS lookup (and failure) on T-Mobile network

2009-10-14 Thread for android
http://code.google.com/p/android/issues/detail?id=2764 On Thu, Oct 15, 2009 at 4:40 AM, tomei.ninge...@gmail.com < tomei.ninge...@gmail.com> wrote: > > Hello, > > This happens only when my G1 phone is on T-Mobile network: > > I found that when I try to go to the browser, and type the address >