Mention that the android/qa/sc test has not been maintained lately

Change-Id: I78108f44bad1da0143f2849aa98a2ddf1b13fc1d

1 files changed, 10 insertions, 6 deletions

diff --git a/README.cross b/README.cross
index 63dc9cf48067..7dcb03c00367 100644
--- a/README.cross
+++ b/README.cross
@@ -386,12 +386,13 @@ them...
 The activity used for these apps is in android/Bootstrap. See
 README.Android.
 
-To build the complex unit test (for Calc functionality; invokes the
-"ucalc" unit test code from sc) setup your environment (make cmd cmd=bash)
-and cd to android/qa/sc and run a "make". The Makefile here is
-completely manually written, this stuff is so experimental it doesn't
-make sense yet to try to integrate with the normal gbuild
-mechanism.
+To build the complex unit test for Calc functionality which invokes the
+"ucalc" unit test code from sc, cd to android/qa/sc and run a "make". The
+Makefile here is completely manually written, this stuff is so experimental it
+doesn't make sense yet to try to integrate with the normal gbuild mechanism.
+
+Note that lately (as of May 2012) the android/qa/sc test has not been
+maintained, and might not build cleanly.
 
 Then to run the unit test, do "make install" followed by "make
 run". You most likely want to have an "adb logcat" running in another
@@ -408,6 +409,9 @@ out what is going wrong. Pass something like -e lo-strace '-tt -f -e
 trace=file,process,network -o /system/sc/strace.out' to the am start
 command line.
 
+The Android test app which has been exercised lately is in
+android/experimental/DocumentLoader.
+
 
 PowerPC Mac OS X
 ----------------