Re: Android keyboard: your choice.

Andy Burns wrote on Thu, 27 Jun 2024 08:52:49 +0100 :

Don't get confused by the naming of the permissions.

 
A good reason for f-droid to be consistent in providing them *all* in
recognisable android.permission.XXXXX_YYYYY_ZZZZZ format, as well as
their "cuddly" interpretation ...

I agree with both Arno (that they're all there on F-Droid -only scattered)
and with Andy (that F-Droid made some of them cuddly, which is confusing).

Luckily, more than one tool can be used to reporter permissions on an app;
however, most require the app APK to already be installed on Android.

The tools Arno & Andy are discussing I think can be used BEFORE the APKs
are installed (such as the F-Droid description and the output from ).
 <https://developer.android.com/tools/aapt2>

I have Android Studio installed from years ago, but I couldn't figure out
how to install aapt2 so I gave up at this point below in the maven repo.
 <https://maven.google.com/web/index.html?q=aa#com.android.tools.build:aapt2>
 <https://maven.google.com/web/index.html?q=aa#com.android.tools.build:aapt2:8.6.0-alpha08-11315950>

It's simpler to use permission-reporting tools AFTER the APK is installed.
1. PMX
   <https://f-droid.org/de/packages/com.mirfatif.permissionmanagerx/>

2. Permission Manager
   <https://github.com/YourStreet/android-permission-manager> 
   <https://play.google.com/store/apps/details?id=in.yourstreet.permissionmanager>
   (I have this installed but I don't see an APK there anymore.)

3. Muntashirakon App Manager
   <https://github.com/MuntashirAkon/AppManager/releases>

If someone can explain how to install aapt2 to run on an APK,
let me know; otherwise I'll stick with the three tools above.