Bug report for android < 4.4 "Using conscrypt (via Play Services) forces SSLv3 on Android 4.0 to 4.3": https://code.google.com/p/android/issues/detail?id=78187

IETF RFC to deprecate SSLv3: https://tools.ietf.org/html/rfc7568

SSLv3 MUST NOT be used.  Negotiation of SSLv3 from any version of TLS
MUST NOT be permitted.

Any version of TLS is more secure than SSLv3, though the highest
version available is preferable.

Fairphone's opinion as of recently:

While this situation is very frustrating for us at Fairphone as well as for many of our Fairphone owners, practically-speaking, we’re confident that this won’t impact the overall usefulness of our first Fairphones in the near future.

But it does. For example here is my previous thread I created because thanks to Android 4.2.2 I can't use the owncloud app to connect to our owncloud server that is configured with SSLv3 disabled and TLS 1.2 with up to date algorithms enabled: https://np.reddit.com/r/fairphone/comments/32jz47/old_android_versions_and_ssltls_functionality/

Another one I recently encountered is that I can't use KDE Connect to view the fairphone's notifications on my computer, because Android 4.2.2 doesn't support the notification API.

The hardware of my Fairphone is still fine, but thanks to the software it's getting less and less useful over time. Not some time in the future. It's happening right Now. We're already in the process of losing crucial functionality. What is fairphone's opinion: What should I do with it?