@grote Thanks for the link. So it seems to be specific to F-Droid, right? I'm puzzled about someone saying Obtainium doesn't auto update on GrapheneOS cause it has been for me. Then again, its developer isn't an Android developer and it's known the the Flutter plugins used for it aren't the most reliable.

It's also worth noting that it's not just GrapheneOS that adds the sensors permission. Unless I'm severely mistaken, DivestOS does too, as do other projects based on GrapheneOS, so it would be good to get this fixed for people not using GrapheneOS as well. It sounds like the check in question might not be necessary at all?

I don't see a reason for the modern installer and for auto updates to not be used by default. The way to differentiate whether the OS the app is running on should be done by checking the Android version, right?

@grote I also wanted to additionally comment on "thanks! The log shows, that every app automatically gets the android.permission.OTHER_SENSORS permission without even asking for it which is a weird thing to do as it is isn't how permissions in Android work and may break other things."

The reason why the permission is granted to apps by default is for app compatibility. Since this permission isn't a regular one, apps expect to be able to use sensors. There is a setting that can deny this permission to apps by default, in which case when an app tries to access the device's sensors covered by that permission, the user is notified and can optionally grant sensors access to that specific app.