From 0129ed269e9c576c31bc90ff7b5a6274481e0cce Mon Sep 17 00:00:00 2001 From: Anirudh Sevugan Date: Mon, 30 Dec 2024 20:10:58 -0600 Subject: [PATCH] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 2624d4e..9b2f82c 100644 --- a/README.md +++ b/README.md @@ -18,7 +18,7 @@ ExoPlayer Creator has been tested on the following devices with the following re | Android 15 | Yes | VM | | Android 14 | Yes | Real Device | | Android 8 | Yes | VM | -| Android 5 | **No** | VM | +| Android 5 | **Partially** | VM | Compatibility-wise, **most versions of Android work just fine with the app**, but if you're using Android 7 or below, note that I either haven't tested the app on those devices or the app failed to function as intended. @@ -26,7 +26,7 @@ Compatibility-wise, **most versions of Android work just fine with the app**, bu Make sure you **have a WebView installed**, or else the HTML5 player won't work because it relies on a WebView to display the player. This is important in VMs since unlike commercial devices they are meant more for developer purposes and thus lack some important tools, like the Play Store (some Android SDKs do not include it), WebViews, etc. ### Issues (that can't really be fixed) -On Android 5, a severe codec issue happens when loading any video, in both ExoPlayer *and* the HTML5 player. This is most likely due to the fact that **Android 5 does not support the latest video codecs**. +On Android 5, a severe codec issue happens when loading most videos (unless recorded with device camera), in both ExoPlayer *and* the HTML5 player. This is most likely due to the fact that **Android 5 does not support the latest video codecs**. And on any Android version, URLs that are signed using self-signed certificates return a source error in any video player in the app that supports using video URLs, **this is normal behavior in Android** and it ***cannot* be fixed** because Android does not allow bypassing this check.