phone-as-client Socket connections time out in 3GS mode, but work fine in wifi

by Samsyn » Mon, 15 Mar 2010 09:03:13 GMT


Sponsored Links
 I wonder if this could be a Verizon thing.  What strikes me as odd is
that the UrlConnection works fine, and that must also be using tcp, so
is fundamentally the same as my subsequent Socket connection, which
fails.

The differences are:

* different server.. .MAYBE my server doesn't like the 3gs 'ip'
address of the client...
* server port 80.. MAYBE android or verizon is making a special
exemption for what looks like a web request, while applying extra
'security' for the more generic tcp connection
* maybe I need to do something to enable the socket-over-3gs (bind to
a nic?)  That UrlCconnection is smartly doing, but I am dumbly not.






--



phone-as-client Socket connections time out in 3GS mode, but work fine in wifi

by Samsyn » Thu, 18 Mar 2010 08:13:16 GMT


 adly, no joy.  I get the same behaviour trying to connect to three
different non-port-80 servers.

Recapping

* using Socket, TCP connection, originated by phone
* Have the "INTERNET" privilege

code section:

[code]

try {
mServerSocket = new Socket( );
SocketAddress adr = new InetSocketAddress( (String)
mServerAddr, mServerPort );
mServerSocket.connect(adr, 30*1000);
} catch (UnknownHostException e) {
Log.v(TAG, "Unknown host" + mServerAddr );
mLastError = "host: " + e.getMessage();
failed = true;
} catch (IOException e) {
Log.v(TAG, "Couldn't get I/O for the connection to: " +
mServerAddr );
mLastError = "IO: " + e.getMessage();
failed = true;
}
[/code]


* Emulator connects just fine,whether wifi is on or off (though
obviously the emulator uses host internet in both cases)
* Real-Phone connects fine, in WIFI mode
* Real-Phone fails, in MOBILE (3gs) mode, on verizon.

Failure is the IOException "Socket is not connected" (and appears
after the expected timeout)

--- However, THIS works on both WIFI and MOBILE connections (initiated
by real-phone on verizon)

[code]
URL myURL = new URL( "http://..." + mUrlArgs );
// Open a connection to that URL.
URLConnection ucon = myURL.openConnection();
[/code]

even to the same machine as the server that I can't connect to, but
this is a port 80 http request.

----

I'm not sure how to get deeper logging from the phone (and it only
fails on the phone) on the off chance that some logging would actually
tell me what it was complaining about.



On Mar 15, 9:26pm, Samsyn <d...@synthetic-reality.com> wrote:

--


Sponsored Links


phone-as-client Socket connections time out in 3GS mode, but work fine in wifi

by Samsyn » Fri, 19 Mar 2010 11:11:18 GMT


 K, some success, as it were.

Let the wookiie win

--

I changed my server to listen on port 80 instead and now it works fine
in both WIFI and MOBILE modes.

* server ping is now 800ms instead of 100ms
* I can not, of course, run a web server on the same machine now,
which is a small pain.

But hey, if it works for port 80, maybe it will work for some other
ports, and maybe I just was using the One Illegal Verizon Port In the
Entire World.

ooo. 950 ms ping... I can see why people say "plays better over wifi"

Well, at least I wasn't crazy, they really WERE blocking me.

- Dan


On Mar 17, 5:13pm, Samsyn <d...@synthetic-reality.com> wrote:

--



phone-as-client Socket connections time out in 3GS mode, but work fine in wifi

by Samsyn » Sat, 20 Mar 2010 10:17:45 GMT


 n Mar 18, 8:11pm, Samsyn <d...@synthetic-reality.com> wrote:
OK OK, apparently I just picked the world's worst port number (4444)
and was SO SURE that was an innocent number that I didn't even try any
others. Well, 4444 is apparently blocked by verizon/android (looks
like Oracle and others use it for admin ports)

So I will just use a nice high number that isn't on any lists I can
find.

So, my apologies for spamming the forum, but if this helps anyone
else, avoid port 4444 :-)

I hereby mark this issue resolved.


--



phone-as-client Socket connections time out in 3GS mode, but work fine in wifi

by Carlo » Thu, 22 Apr 2010 09:51:35 GMT


 i,

Any chance you have succeeded with another port than port 80 ?

We are also receiving report from user not able to reach our server
running on port 8080 from their mobile network, is there any
(recommended) list of server port that can be use ?

thanks


On Mar 20, 11:17am, Samsyn <d...@synthetic-reality.com> wrote:

--



Other Threads

1. HttpPost fileupload data loss

The app sends up a data file to our server, using this code.

            HttpParams params = new BasicHttpParams();
            HttpConnectionParams.setConnectionTimeout(params, 15000);
            HttpConnectionParams.setSoTimeout(params, 5 * 60 * 1000);
            HttpClient client = new DefaultHttpClient(params);
 HttpPost post = new HttpPost(MyActivity.HOST + "track/sync-
compare.html");
            FileEntity e = new FileEntity(tmp, getContentType());
            e.setChunked(true);
            HttpEntity requestEntity = (e);
            post.setEntity(requestEntity);
        }
        if (Util.LOG) debug("about to execute");
        response = (HttpResponse) client.execute(post);
The file that is received on our server is different than the file
that is sent.

-- 

2. Changing UI activity in runtime

Hi. I need to change the UI of an activity in runtime. In onCreate()
method, I write setContentView(R.layout.m1), but in runtime I need to
change R.layout.m1 by R.layout.m2 depends on a flag.

Any ideas?

-- 

3. Changing flash light brightness

4. Caching of sensor events

5. android.pim.vcard

6. Getting internet from PC via USB

7. Regarding Deployment