Android < 4.1 doesn't properly support TLS 1.2.

PayPal were originally going to stop supporting non TLS 1.2 (TLS 1.1, 1.0, SSL 2, SSL3) connections in June - they've now pushed this to next year: https://devblog.paypal.com/upcoming-security-changes-notice/

Its only fairly recently that Android got TLS 1.2 support with 4.1 in 2012. The problem is that for years budget Chinese android phones were shipping with 2.3, which was very light on resources and good for low powered phones with minimal ram.

I believe this changed with an effort to use less ram and cpu with 4.4 or 5.0, but by then millions of these phones were sold and are still out there. Heck, up until a year or two ago, these were on shelves in the US at budget places like Cricket. I think almost 10% of Androids in the wild still don't support 1.2. Maybe more considering Google has limited snooping abilities in China and may not fully know the extent of these installs.

IE7/IE8/IE9 have a combined global marketshare of about 8% also.

> The problem is that for years budget Chinese android phones were shipping with 2.3, which was very light on resources and good for low powered phones with minimal ram.

Not just budget Chinese phones. Low-end Samsung phones and such, too.

Android 2.3 doesn't even support SNI for virtual hosts on SSL.

On the desktop side, IE9, the last version on Vista, which is in extended support until April 11, 2017, only supports up to TLS 1.0.

My NAS has security settings for modern, intermediate and old browsers that says it's to do with cipher suites they support -

https://imgur.com/a/PmaUE

Those settings are likely to be derived from Mozilla's recommendations with the same names:

https://wiki.mozilla.org/Security/Server_Side_TLS

You can read the details, rationale, and information about supported clients there.

Love, love love love love LOVE my Synology!