Under some circumstances, certain TLS connections are dropped by certain

README.chromium

 Name: openssl
 URL: http://openssl.org/source/
 Version: 1.0.1e
 License: BSDish
 License File: openssl/NOTICE
 License Android Compatible: yes
 Security Critical: yes
 
 Description:
 This is OpenSSL, the standard SSL/TLS library, which is used *only* in
@@ skipping 158 matching lines @@
     to track this issue.
 
   enable-dtls1.patch:
     Enable DTLSv1, which is disabled by default in the Android platform
     configuration.
 
   x86_64_source_excludes.patch
     Exclude the source files bn_asm.c and rc4_skey.c for x86_64 because
     they are replaced by x86_64-gcc.c and rc4-x86_64.S.
 
+  z_reduce_client_hello_size.patch
+    Advertise support of only the NIST curves P-521, P-384, and P-256,
+    as well as only uncompressed points, to keep ClientHello small.
+
 **************************************************************************
 Adding new Chromium patches:
 
 In the event you need to add a new Chromium-specific patch, follow this
 procedure:
 
   1) Use the --temp-dir option to download everything to a known directory
      (by default, import_from_android.sh downloads everything into a
      temporary directory that is erased when the script exits, even in
      case of error).
@@ skipping 12 matching lines @@
      (cd /tmp/aaa/build && diff -burN android-openssl.orig android-openssl) > patches.chromium/my-new-change.patch
 
   5) Re-run the script:
 
       ./import_from_android.sh
 
 Generally speaking, consider sending your patch directly to the Android
 open-source review servers too. Once submitted there, you can update
 the git commit in openssl-chromium.org and remove your local patch in
 one new CL.