Sujet : Re: Android keyboard: your choice.
De : usenet (at) *nospam* andyburns.uk (Andy Burns)
Groupes : comp.mobile.androidDate : 24. Jun 2024, 18:18:52
Autres entêtes
Message-ID : <ldtkjcFikkbU3@mid.individual.net>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
User-Agent : Mozilla Thunderbird
R.Wieser wrote:
Andy Burns wrote:
I did look, which is why I asked ... the f-droid list is not identical to
the aapt2 list.
It would have been nice if you would have mentioned the differences.
The aapt2 permissions
android.permission.READ_USER_DICTIONARY
android.permission.RECEIVE_BOOT_COMPLETED
android.permission.VIBRATE
android.permission.WRITE_USER_DICTIONARY
android.permission.READ_CONTACTS
android.permission.BIND_INPUT_METHOD
android.permission.BIND_TEXT_SERVICE
The f-droid permissions
android.permission.READ_USER_DICTIONARY
run at startup (why not use the proper name android.permission RECEIVE_BOOT_COMPLETED?
control vibration (again call it android.permission.VIBRATE)
android.permission.WRITE_USER_DICTIONARY
helium314.keyboard.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION
Is it possible those are BIND_INPUT_METHOD and BIND_TEXT_SERVICE ?
Yes those are not listed by f-droid
those are not under "uses-permission", but under "service" -> "permission"
Thanks, wasn't aware of the distinction, but it's still "a permission"
Also there's no mention of android.permission.READ_CONTACTS
Regarding the DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION, I found this
<
https://stackoverflow.com/questions/74146297/android-adding-dynamic-receiver-not-exported-permission-in-release-build>