android: update startup details of README

Change-Id: I88a0483e96f2de38ae3c1bc6f707e3b5b504bbac

1 files changed, 2 insertions, 20 deletions

diff --git a/android/README b/android/README
index c0a7e934c625..48c3d6ea69b9 100644
--- a/android/README
+++ b/android/README
@@ -249,30 +249,12 @@ lo_dlneeds: Could not read ELF header of /data/data/org.libreoffice...libfoo.so
         This (most likely) means that the install quietly failed, and that
 the file is truncated; check it out with adb shell ls -l /data/data/....
 
-* Detailed explanation
-
-Note: the below talk about unit tests is obsolete; we no longer have
-any makefilery etc to build unit tests for Android.
-
-Unit tests are the first thing we want to run on Android, to get some
-idea how well, if at all, the basic LO libraries work. We want to
-build even unit tests as normal Android apps, i.e. packaged as .apk
-files, so that they run in a sandboxed environment like that of
-whatever eventual end-user Android apps there will be that use LO
-code.
-
-Sure, we could quite easily build unit tests as plain Linux
-executables (built against the Android libraries, of course, not
-GNU/Linux ones), push them to the device or emulator with adb and run
-them from adb shell, but that would not be a good test as the
-environment such processs run in is completely different from that in
-which real end-user apps with GUI etc run. We have no intent to
-require LibreOffice code to be used only on "rooted" devices etc.
+* Startup details
 
 All Android apps are basically Java programs. They run "in" a Dalvik
 (or on Android 5 or newer - ART) virtual machine. Yes, you can also
 have apps where all *your* code is native code, written in a compiled
-language like C or C++. But also also such apps are actually started
+language like C or C++. But also such apps are actually started
 by system-provided Java bootstrapping code (NativeActivity) running
 in a Dalvik VM.