path: root/README.Android
diff options
authorMichael Meeks <>2012-01-20 09:44:00 +0000
committerMichael Meeks <>2012-01-20 10:20:13 +0000
commita0ce2a2f7a8533fd2ea6cd4a05e250a32f609ed7 (patch)
treeaccd82f3fa06a2f6261397846cc4e4580a68ba56 /README.Android
parent32d4f05c022d785a86c6b0c39c74bc1ad46f6e61 (diff)
android: more notes on running the test
Diffstat (limited to 'README.Android')
1 files changed, 24 insertions, 0 deletions
diff --git a/README.Android b/README.Android
index e58c811a279e..503b50b2df8f 100644
--- a/README.Android
+++ b/README.Android
@@ -1,5 +1,29 @@
Android-specific notes
+* Getting something running
+ Create an AVD in the android UI, don't even try to get
+the data partition size right in the GUI, that is doomed to producing
+and AVD that doesn't work. Instead start it from the console:
+ emulator-arm -avd <Name> -partition-size 500
+ Where <Name> is the literal name of the AVD that you entered.
+Then it is necessary to get stdout/err to go to somewhere we can find it:
+ adb shell stop; adb shell setprop log.redirect-stdio true; adb shell start
+ Then:
+ cd android/qa/sc
+ make clean all install
+ make run ; adb shell logcat
+ And if all goes well - you should have some nice unit
+test output to enjoy.
+* Detailed explanation
Unit tests are the first thing we want to run on Android, to get some
idea how well, if at all, the basic LO libraraies work. We want to
build even unit tests as normal Android apps, i.e. packaged as .apk