os-issue-tracker
os-issue-tracker copied to clipboard
GrapheneOS
Lock device based on movement
automatically lock your phone based on movement force, or the acceleration to be more accurate.
As you doesn't provide any code I guess this is a feature request?
Then: Private Lock (Lock your phone from its movement force) - https://f-droid.org/app/com.wesaphzt.privatelock
@beerisgood it makes use of device admin. Not wanted by the lead developer.
See https://github.com/GrapheneOS/os_issue_tracker/issues/160
I don't say that this app should be included in GrapheneOS. I post that as solution to you, because you don't provide any code to get that done in GrapheneOS
This likely would make sense with two separate modes:
- Lock device when sensor threshold is reached.
- Reboot device when sensor threshold is reached.
The former is meant to conform to a threat model where you're defending against the device being snatched by a non-technical adversary who's interested in selling off the device. Since the device is locked, the device will eventually reboot if auto reboot hasn't been disabled by the user.
With the second option, you're assuming a much higher threat model in which you want the device to immediately reboot in case it's forcefully taken in order to significantly reduce the chances that exploiting it will yield anything. Instead of relying on the auto reboot timer getting the device back at rest, it gets it back at rest immediately, thus protecting all data no matter how quickly after the device is forcefully taken exploitation attempts are made.
As this is a feature which doesn't make sense to enable by default (people are likely to start wondering why their device was locked for "no reason", or even worse, why they're getting random reboots), it could be disabled by default and exposed in an optional setup wizard step for configuring defaults and enabling optional security features. The new setup wizard providing an expandable base for that makes it easier to do that.
