It is still in developer options, because less technical users turn that option on and forget about it. Later they find out that certain apps don't work properly anymore and then don't know how to fix it.
nostr:npub1uyj8kkqtcs20wj00t5drdwhqq8zfp0vhlsfnxuxgdr2ay7sd7vpsctlx7k nostr:npub1hxx76n82ags8jrduk0p3gqrfyqyaxnrlnynu9p5rt2vmwjq6ts3q4sg75y nostr:npub1mnwqngttz2xxpt8znsk565sl4q9mvtdere5mtp4l3622gel3e40s9fvu52 However, for nearly all apps, Sensors can simply be disabled and left disabled. Very few apps need access to the sensors.
The Sensors Off quick tile from developer options has some strange quirks and doesn't necessarily work the way you actually expect. It's still in developer options for a reason.
Discussion
nostr:npub1uyj8kkqtcs20wj00t5drdwhqq8zfp0vhlsfnxuxgdr2ay7sd7vpsctlx7k nostr:npub1hxx76n82ags8jrduk0p3gqrfyqyaxnrlnynu9p5rt2vmwjq6ts3q4sg75y nostr:npub1mnwqngttz2xxpt8znsk565sl4q9mvtdere5mtp4l3622gel3e40s9fvu52 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.
Thanks a lot for your replies nostr:npub1235tem4hfn34edqh8hxfja9amty73998f0eagnuu4zm423s9e8ksdg0ht5, highly appreciated!
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. 👍🏻