nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpquyj8kkqtcs20wj00t5drdwhqq8zfp0vhlsfnxuxgdr2ay7sd7vpsy2w96p nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqhxx76n82ags8jrduk0p3gqrfyqyaxnrlnynu9p5rt2vmwjq6ts3qf3easn nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqmnwqngttz2xxpt8znsk565sl4q9mvtdere5mtp4l3622gel3e40segalsa No, that's not why. There are standard Camera and Microphone toggles which function differently than the Sensors Off toggle. There will be a separate one added by GrapheneOS for other sensors too but there's rarely ever a reason to grant the Sensors permission we add to user installed apps.

Reply to this note

Please Login to reply.

Discussion

So here are examples of apps where the phone sensors are used:

Accelerometer:

- fitnessapps

- Snapchat (with mapping)

- driving apps (in order to show your current speed)

Gyroscope:

- gaming apps (for instance racing)

Magnetometer:

- Google maps and other mapping apps (compass mode)

- Compass apps

- metal detector apps.

I'd say that the sensors are widely used in apps. But I do appreciate that GrapheneOS is intending to make a Sensors Off toggle as well. 👍🏻