Updated android docs

Placeholder-Software · Aug 21, 2023 · 0c128ff · 0c128ff
1 parent c3b7302
commit 0c128ff
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 1 deletion.
diff --git a/.vscode/spellright.dict b/.vscode/spellright.dict
@@ -4,3 +4,4 @@ comms
 preprocessed
 boolean
 Readonly
+LuminOS
diff --git a/docs/Platforms/Android.md b/docs/Platforms/Android.md
@@ -1,3 +1,7 @@
 # Android (Including Oculus Quest)
 
-On Android you must request permission to use the microphone, see the Unity documentation for this [here](https://docs.unity3d.com/Manual/android-manifest.html). If you use `Android 6.0` or greater and `API level 23` or greater there is a runtime permissions system which Unity makes available through the Android.Permissions, see the section titled "Runtime permissions in Android 6.0 (Marshmallow)" [on this page](https://docs.unity3d.com/Manual/android-manifest.html).
+On Android the user must grant permission before the Microphone is accessed. Since Dissonance uses the Unity `Microphone` class the `Record_Audio` permission should have already been added to the [app manifest](https://docs.unity3d.com/Manual/android-manifest.html). When the application is started the user is asked for all of the permissions in the manifest in one dialog.
+
+If `Microphone` permission is not granted when Dissonance is started it will operate in listen-only mode.
+
+The [Runtime Permission System](https://docs.unity3d.com/Manual/android-RequestingPermissions.html) may be be used to request permission from the user again at any time. If permission is granted after Dissonance has already started you should call [DissonanceComms.ResetMicrophoneCapture](../Reference/Components/Dissonance-Comms.md#resetmicrophonecapture) to restart the microphone recording system.