Home » Android » httpurlconnection is very slow on Android 4.2

httpurlconnection is very slow on Android 4.2

Posted by: admin May 14, 2020 Leave a comment


I can succesfully connect, send and receive data by using httpurlconnection. But it takes very long time to load all the data on my phone (Samsung s4, 4.2) and on android 4.2 emulator.
But it takes almost 1-2 seconds (which is very fast) to load pics on Android 2.3.x emulator. Faster than my galaxy s4 on http connection.

I’m using AsyncTask and my code works fine on both. It is just slow on android 4.2s.
I tried removing chunkedStreaming, keep alive, changing timeout values etc. but still no success

Here is my code

HttpURLConnection urlConnection = (HttpURLConnection) url.openConnection();

                 urlConnection.setRequestProperty("Connection", "Keep-Alive");
                 urlConnection.setRequestProperty("Content-Type", "multipart/form-data;charset=UTF-8;boundary="+boundary);


Are there any differences between 4.2’s and 2.3.x’s httpurlconnections? Whats wrong here


I tested by using Log.e() to see which line takes most time.

///// other staff

                 if (isCancelled())
                        return (null); // don't forget to terminate this method
                    DataOutputStream outputStream = new DataOutputStream( urlConnection.getOutputStream() );
                    //Send Passcode

Between 3 and 4, 5-6 second passes on the line

DataOutputStream outputStream = new DataOutputStream( urlConnection.getOutputStream() );


That waiting time (see previous update) is related to the urlConnection.setConnectTimeout(6000);

When I make Timeout 1000, then connection responses quickly (waiting 1 second for the line)

DataOutputStream outputStream = new DataOutputStream( urlConnection.getOutputStream() );

No idea why this is happening

How to&Answers:

Set urlConnection.setConnectTimeout() to a lower timeout.

The class documentation for URLConnection.setConnectTimeout() says:

Sets the maximum time in milliseconds to wait while connecting. Connecting to a server will fail with a SocketTimeoutException if the timeout elapses before a connection is established. The default value of 0 causes us to do a blocking connect. This does not mean we will never time out, but it probably means you’ll get a TCP timeout after several minutes.

Warning: if the hostname resolves to multiple IP addresses, this
client will try each in RFC 3484 order. If connecting to each of these
addresses fails, multiple timeouts will elapse before the connect
attempt throws an exception. Host names that support both IPv6 and
IPv4 always have at least 2 IP addresses.

I originally had mine set to urlConnection.setConnectTimeout(30000); and then changed it to urlConnection.setConnectTimeout(1000). Immediately, I saw quicker results.

Hope this helps!


You mentionned you are using AsyncTask, are you trying to run several tasks at the same time ?

If that’s the case, you should be aware that starting with Android 4.0, AsyncTasks are serialized by default. That means the executor will run one task at a time.

If you want to keep the previous behavior, you can use the following construct:

else {

See this blog post for more information: