@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 | View the thread
If you're using the alpha or beta channels for OS and app updates and want to help out with testing and providing feedback, most of that happens in the project's testing chat rooms. They are bridged between Discord, Telegram, and Matrix.
Details here: https://grapheneos.org/contact#community-chat
Helping out with testing new releases before they make it to the stable channel would be very much appreciated!
[#]GrapheneOS #testing
=> More informations about this toot | View the thread
Initial Android Auto support is here! Our community has already helped us with testing and a lot of additional fixes have been merged, with a new release with the appropriate fixes coming very soon! If GrapheneOS not supporting Android Auto was the reason for not giving it a shot, now's the time!
https://grapheneos.social/@GrapheneOS/111672743880310535
[#]GrapheneOS #AndroidAuto
=> More informations about this toot | View the thread
Another instance, another #introduction - here's hoping that I'll settle here for good!
I'm matchboxbananasynergy, AKA Banana, That Banana Guy, Bananaman... you get the point.
My main interests are #privacy and #security - with an extra focus on #android
I've previously contributed to privacy and security resources, and I am currently doing community moderation for various privacy and security related open-source projects.
Feel free to say hi! 👋
=> More informations about this toot | View the thread
=> This profile with reblog | Go to matchboxbananasynergy@infosec.exchange account This content has been proxied by September (ba2dc).Proxy Information
text/gemini