From ef5c94bb814900c97a98cfb07ee2516651d7b775 Mon Sep 17 00:00:00 2001
From: Dirk Hohndel <dirk@hohndel.org>
Date: Mon, 18 Oct 2021 20:01:25 +0000
Subject: [PATCH] Android: fix broken permissions

In trying to avoid the wrath of the Google Play police I ended up giving
up too many permissions. And while in my test installs things continued
to work, in new installs on Android 10 or newer the lack of
FINE_LOCATION permission resulted in BLE scans no longer working.

The frustrating thing is that apparently installing an update with a
different set of permissions isn't enough to trigger either the bug or
the fix (at least not reliably). What appears to work is to uninstall
the existing app and then do a fresh install of a new app with the
correct permissions.

Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
---
 android-mobile/AndroidManifest.xml | 11 +----------
 1 file changed, 1 insertion(+), 10 deletions(-)

diff --git a/android-mobile/AndroidManifest.xml b/android-mobile/AndroidManifest.xml
index 67ce4bc8d..d7c933547 100644
--- a/android-mobile/AndroidManifest.xml
+++ b/android-mobile/AndroidManifest.xml
@@ -92,17 +92,8 @@
     <!--
          The following comment will be replaced upon deployment with default permissions based on the dependencies of the application.
          Remove the comment if you do not require these default permissions.
-         %% no space here INSERT_PERMISSIONS
-
-	 this always requests FINE_LOCATION which I no longer want to deal with - so instead manually request what we know we need.
-	 stupidly COARSE LOCATION appears to be necessary for BLE
     -->
-    <uses-permission android:name="android.permission.INTERNET" />
-    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
-    <uses-permission android:name="android.permission.BLUETOOTH" />
-    <uses-permission android:name="android.permission.BLUETOOTH_ADMIN" />
-    <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
-    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
+    <!-- %%INSERT_PERMISSIONS -->
 
     <!--
          The following comment will be replaced upon deployment with default features based on the dependencies of the application.