Version 1.93.3

 * Note for users on Android Oreo (8.x): I reverted some changes (new library versions mainly) and forcibly disabled the animations preference to make sure moving between articles works again. This currently is the only solution I have for #374.
 * Fix issue #371: feedname not shown and empty in overview
 * Fix issue #376: Trust anchor for certification path not found
 * Fix issue #372: Add option for disable feed icons downloading
 * Fixed some preferences not saved

ttrssreader/src/main/AndroidManifest.xml

@@ -20,8 +20,8 @@
     xmlns:android="http://schemas.android.com/apk/res/android"
     xmlns:tools="http://schemas.android.com/tools"
     android:installLocation="internalOnly"
-    android:versionCode="1932"
-    android:versionName="1.93.2">
+    android:versionCode="1933"
+    android:versionName="1.93.3">
 
     <!-- Check connectivity -->
     <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>

ttrssreader/src/main/res/values/update.xml

@@ -18,7 +18,14 @@
 <resources>
 
     <string-array name="updates">
-		<item>Version 1.93.2
+		<item>Version 1.93.3
+			 * Note for users on Android Oreo (8.x): I reverted some changes (new library versions mainly) and forcibly disabled the animations preference to make sure moving between articles works again. This currently is the only solution I have for #374.
+			 * Fix issue #371: feedname not shown and empty in overview
+			 * Fix issue #376: Trust anchor for certification path not found
+			 * Fix issue #372: Add option for disable feed icons downloading
+			 * Fixed some preferences not saved
+		</item>
+        <item>Version 1.93.2
 			 * Debug-build to test client-certificates
 		</item>
         <item>Version 1.93.1
@@ -138,7 +145,7 @@
 			 * Fixed  Issue #253: \"Adding a new feed will put it in a random category\"
 			 * Fixed some FCs (Issue #266)</item>
         <item>Version 1.80
-			 * Revert to default implementation of SecureRandom because the suggested bugfix from Google (http://android-developers.blogspot.de/2013/08/some-securerandom-thoughts.html) seems to crash on some devices. Due to this the SSL implementation \"may not receive cryptographically strong values\". I\'m investigating solutions for this. Thank you for your patience. :)
+			 * Revert to default implementation of SecureRandom because the suggested bugfix from Google seems to crash on some devices. Due to this the SSL implementation \"may not receive cryptographically strong values\". I\'m investigating solutions for this. Thank you for your patience. :)
 			 * Another thing I would like to mention: Thank you all for reporting bugs through the play store and/or by mail. I don\'t answer most of the time and have been made aware that this might be considered unthankful by some. Please know that your support is appreciated!\n</item>
         <item>Version 1.79
 			 * Flash screen when notify is necessary and device has no vibrator