can you disable the motion permission in the OS settings?
Under AOSP and most customs OSes, no. It’s not a standard, exposed permission. GrapheneOS does have a toggle for it, though, and I’ve found most apps don’t need sensors.
Sensors permission toggle: disallow access to all other sensors not covered by existing Android permissions (Camera, Microphone, Body Sensors, Activity Recognition) including an accelerometer, gyroscope, compass, barometer, thermometer and any other sensors present on a given device.
I use a Proton mail account just for this concern. All I did was offer how to get a bug documented in the right place to be fixed. Take it or leave it.
Report it on the Github. Also, can you disable the motion permission in the OS settings? I’m not an Android user, so I’m not familiar.
https://github.com/aeharding/voyager/issues
Under AOSP and most customs OSes, no. It’s not a standard, exposed permission. GrapheneOS does have a toggle for it, though, and I’ve found most apps don’t need sensors.
https://grapheneos.org/features#sensors-permission-toggle
I don’t have a GitHub account. But it’s this git version in using. Maybe the playstote version/fdroid build don’t have the issue?
GitHub is free to sign up
Unless you don’t want to send Microsoft your personal information.
I use a Proton mail account just for this concern. All I did was offer how to get a bug documented in the right place to be fixed. Take it or leave it.