termux / termux/termux-api

Create a lock device API call

Open
#403 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

API command request help wanted
Dominant language
Java
Stars
4.3k
Forks
920
PR merge metrics
No merged PRs in 30d

Description

Feature description
Allow Termux to immediately lock the device upon calling a termux-* command. Not sure if it's possible, but it would be a nice addition.
The main use could be in case the phone gets stolen and loses connectivity with a BLE device (like a smart watch) or some app that allows to call Termux scripts requires it, the device could be locked. It would also be nice if the "Lockdown Mode" could be activated.

Background information
Have you checked if the feature is accessible through the android API?
This post from 10 years ago describes how to do it. Not sure if the current API still supports it and the security implications of allowing this.
Do you know of other open-source apps that has a similar feature as the one you want? (Provide links)
I don't 🙁

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by checking whether the current Android API supports locking the device, using the linked Stack Overflow reference as background. Review the security implications and related behavior requested, including Lockdown Mode; the issue does not identify project files, tests, or a settled definition of done.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.