diff --git a/android/README.ANDROID b/android/README.ANDROID
index 689d09928..4dda16985 100644
--- a/android/README.ANDROID
+++ b/android/README.ANDROID
@@ -143,38 +143,3 @@ you have to run:
 and then:
 
     zipalign -v 4 SuperTuxKart-release-unsigned.apk SuperTuxKart-release.apk
-
-
-
---------------------------------------------------------------------------------
- KNOWN ISSUES
---------------------------------------------------------------------------------
-
-1.  It's not possible to compile STK for Android < 4.4 due to missing GLES 3.0
-    functions. It is technically possible to do - check GLES context version, 
-    load OpenGL functions dynamically using EGL, and if they are not loaded 
-    properly, then fallback to GLES 2.0.
-
-2.  It never ocurred for me, but it's possible that EGL context is lost in some
-    cases. SuperTuxKart is not designed to re-create all textures at any moment,
-    so this is a "Wontfix", at least for now.
-
-3.  We use "exit(0)" at the end of main function. We shouldn't do it and we
-    should just return from the main function. But STK uses some global
-    variables and their values are remembered when the game is restarted. We
-    should properly clear them or re-initialize on startup. Using the "exit(0)"
-    is not-that-bad workaround, but it may cause a crash on exit sometimes.
-    It seems to affect only Android 5.0. More information about the crash:
-    https://code.google.com/p/android/issues/detail?id=160824
-
-4.  STK crashes on startup on some devices when aarch64 build is made using
-    Android r13 NDK. The r13 version has rather big modifications (it uses clang
-    instead of gcc by default). This is probably a bug in NDK/compiler/OS, but
-    for this reason using NDK r12 for 64-bit arm compilation is preferred.
-
-5.  Angelscript doesn't have full support for aarch64 builds, so that scripting
-    won't work on this platform.
-    
-6.  Turning left/right using accelerometer is available, but at this stage the
-    default screen orientation is not automatically detected and user must 
-    manually choose if he needs "phone" or "tablet" accelerometer.