Instructions on avoiding exception when running mojo on Marshmallow.

README.md

Index: README.md
diff --git a/README.md b/README.md
index a9dd13dfc7553606993a04e5f51440bc5f73d8be..4e2e02b5dad4513d0594d8f79eb1dc75bd73aaeb 100644
--- a/README.md
+++ b/README.md
@@ -110,6 +110,21 @@ $ mojo/tools/mojob.py build --android
 The result will be in out/android_Debug. If you see javac compile errors,
 [make sure you have an up-to-date JDK](https://code.google.com/p/chromium/wiki/AndroidBuildInstructions#Install_Java_JDK)
 
+#### Marshmallow
+Running mojo on Marshmallow might raise an Exception `"Unable to find fifo"`. As
+a temporary solution, you can go to `Settings` -> `Apps` -> `Mojo Shell (dev)`
+-> `Permissions` and allow for `Storage`.
+
+*Explanation*: Starting in API level 23 (Marshmallow) the applications need to

[etiennej, 2015/10/30 16:20:28]

I don't think you should put explanation here. I suggest you put the explanation
in the bug, and put a link to the bug here ("see this bug for more
information").

+request read/write permissions at runtime. An exception to this rule is for
+files stored in the folder returned by method [Context.getExternalFilesDir(String)](http://developer.android.com/reference/android/content/Context.html#getExternalFilesDir(java.lang.String))
+which can be used without permissions. This folder looks like 
+`"/storage/emulated/0/Android/data/org.chromium.mojo.shell/files"`. Ideally we
+should write files (e.g. the argument's file, used when starting the application)
+in this directory. However, for some reasons, we cannot do it for now when the
+phone is not rooted. As a temporary fix, you can manually add storage permissions
+for the Mojo Shell app the exception should disappear.
+
 ### Goma (Googlers only)
 
 If you're a Googler, you can use Goma, a distributed compiler service for