Now with in-process redirection, the adb shell setprop thing is not needed

Change-Id: Ibfda0e6e65d0834cffdd95d4c6d87d07644088f6

1 files changed, 8 insertions, 8 deletions

diff --git a/README.Android b/README.Android
index be1d765d734a..633ec52f2f35 100644
--- a/README.Android
+++ b/README.Android
@@ -9,9 +9,6 @@ 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:
 
@@ -20,12 +17,15 @@ Then it is necessary to get stdout/err to go to somewhere we can find it:
 	make clean all install
 	make run ; adb shell logcat
 
-	And if all goes well - you should have some nice unit
-test output to enjoy. After a while of this loop you'll probably
-find that android has lost a lot of space on your device at
-this point:
+	And if all goes well - you should have some nice unit test output to
+enjoy. After a while of this loop you might find that you have lost a lot of
+space on your emulator's or device's /data volume. If using the emulator, you
+can do:
+
+	adb shell stop; adb shell start
 
-	adb shell stop; adb shell setprop log.redirect-stdio true; adb shell start
+but on a (non-rooted) device you probably just need to reboot it. On the other
+hand, this phenomenon might not happen on actual devices.
 
 	and continue onwards & upwards.