Path: ...!news.misty.com!weretis.net!feeder9.news.weretis.net!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!nnrp.usenet.blueworldhosting.com!.POSTED!not-for-mail
From: Andrew <andrew@spam.net>
Newsgroups: comp.mobile.android
Subject: Re: Android keyboard: your choice.
Date: Thu, 27 Jun 2024 21:21:48 -0000 (UTC)
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID: <v5kl5b$1n6d$1@nnrp.usenet.blueworldhosting.com>
References: <20240617114559.a2970ac2923facc44a2ec355@gmail.com> <v4ov83$j5oj$1@dont-email.me> <v4sojj$1gqik$1@dont-email.me> <ldfbncFe5o7U1@mid.individual.net> <ldfc9cFe3usU2@mid.individual.net> <ldia8bFrps7U8@mid.individual.net> <ldii1sFt40eU1@mid.individual.net> <ldj2gdFs5uU3@mid.individual.net> <v53gbf$33j85$3@dont-email.me> <ldpc2vFtm5tU6@mid.individual.net> <ldq4gfF29flU2@mid.individual.net> <v5b4lo$2tun$1@nnrp.usenet.blueworldhosting.com> <ldslpbFemdhU1@mid.individual.net> <ldsvu4Fg66eU1@mid.individual.net> <ldt1maFge9lU1@mid.individual.net> <le4ihiFkc6dU5@mid.individual.net> <le4k2iFkce9U1@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 27 Jun 2024 21:21:48 -0000 (UTC)
Injection-Info: nnrp.usenet.blueworldhosting.com;
	logging-data="56525"; mail-complaints-to="usenet@blueworldhosting.com"
Cancel-Lock: sha1:/+s6LDanlSQyIFCoVqAOLdg9jzc= sha256:/MoI4sHmBOLhp9RGgQd6B/cUYBtV6AzWE0dCpoB0lwQ=
	sha1:MdoEs1IPP3SRmzhgbwnvBGbqOR0= sha256:96Z8zuEgD19owJCPXj/BPJdmCkhNIg6K2nOLvXOu+Ds=
X-Newsreader: PiaoHong.Usenet.Client.Free:1.65
Bytes: 3395
Lines: 36

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.