Ancestors

Toot

Written by matchboxbananasynergy on 2024-07-13 at 16:05

@grote I've had a chat with the team about this.

This check is likely to break regardless of OTHER_SENSORS or any GrapheneOS-specific change.

POST_NOTIFICATIONS permission must be broken too, unless it's special cased when app repo database is generated.

This applies to apps with a targetSdk < 33.

https://github.com/aosp-mirror/platform_frameworks_base/blob/4d553c25adcf35ceaee3368f4b44444cb7146798/core/java/com/android/internal/pm/permission/CompatibilityPermissionInfo.java#L24

OTHER_SENSORS is implemented in basically the same way.

Before 14 QPR3, OTHER_SENSORS didn't show up when APKs were parsed inside an app, which seems to be what F-Droid is doing. OTHER_SENSORS showed up if app was queried after it was installed.

OTHER_SENSORS can likely be hidden the same way it was before Android 14 QPR3, but it's not clear if that is the right way to approach it at this time.

The check that F-Droid is doing as it currently exists doesn't make a lot of sense, and it likely breaks with a lot more things, including things that AOSP itself does, unless those things are somehow being special-cased.

=> More informations about this toot | More toots from matchboxbananasynergy@infosec.exchange

Descendants