Path: ...!weretis.net!feeder8.news.weretis.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Arno Welzel Newsgroups: comp.mobile.android Subject: Re: Android keyboard: your choice. Date: Thu, 20 Jun 2024 11:19:13 +0200 Lines: 38 Message-ID: References: <20240617114559.a2970ac2923facc44a2ec355@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: individual.net mgha/s/wmROcvPJhxaNkKge9rCvszF5Bk0zFhrx0WkWc6abp7J Cancel-Lock: sha1:Ks/0FsVpMEXMmKDp04jGSPkwM88= sha256:0g1C/os3jz8OTixMQvogT8A79XkODxLvyENeMgbtngM= Content-Language: de-DE In-Reply-To: Bytes: 2225 Andrew, 2024-06-19 20:45: [...] > HeliBoard: > 1. android.permission.READ_CONTACTS > 2. android.permission.READ_USER_DICTIONARY > 3. android.permission.RECEIVE_BOOT_COMPLETED > 4. android.permission.VIBRATE > 5. android.permission.WRITE_USER_DICTIONARY > 6. helium314.keyboard.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION > > OpenBoard: > 1. android.permission.POST_NOTIFICATIONS > 2. android.permission.READ_USER_DICTIONARY > 3. android.permission.RECEIVE_BOOT_COMPLETED > 4. android.permission.VIBRATE > 5. android.permission.WRITE_USER_DICTIONARY > > Does anyone have a logical explanation of why this difference? Heliboard supports a registered broadcast runtime reciever for Adroid 13 and above - see here: Quote: "To help make runtime receivers safer, Android 13 introduces the ability for your app to specify whether a registered broadcast receiver should be exported and visible to other apps on the device. On previous versions of Android, any app on the device could send an unprotected broadcast to a dynamically-registered receiver unless that receiver was guarded by a signature permission." -- Arno Welzel https://arnowelzel.de