QuiteKill is a root module that force-stops running apps after a quick power-button press or a manual WebUI action, with lists for packages to protect or explicitly include.
App Stopping on Demand
Its trigger listens for a short power-key tap; the module action can disable that listener.
User apps
Checks installed user applications and, by default, stops only those detected as running.
Package lists
An ignore list overrides the stop action; a force list adds selected system packages.
WebUI and logs
Offers manual controls and recorded stop results through the module interface.
How the trigger works
The v5 boot service watches /dev/input/event0 for power-key presses shorter than 0.3 seconds and then applies a 60-second cooldown. If /sdcard/search exists, it watches the search key on /dev/input/event1 instead. These device paths are fixed in the release script, so the trigger may fail on phones that expose the key on another event node. A short press can occur outside a deliberate screen-lock action.
Configuration
The module stores options in /data/adb/modules/QuiteKill/config.txt. Defaults enable parallel execution with four jobs, limit the ordinary app scan to running packages, protect a small critical-package list, and save logs. Manage ignore.txt and ForceKill.txt through the WebUI or carefully edit the files. The module action toggles the power-key listener; manual WebUI operation remains available.
The distributed force list already contains several Google and vendor packages, including Play Store and Wallet. Review it before using automatic stopping. Its critical-package guard excludes some entries, such as Google Play services, but does not cover every app that may be important to the user.
Installation
- Install the v5 module ZIP through Magisk, KernelSU, or APatch.
- Reboot, then open the module WebUI. Magisk users need a compatible standalone WebUI host.
- Review the force and ignore lists, then test the manual action before enabling the automatic trigger in daily use.
Trade-offs
am force-stop can suppress notifications, delay synchronization, and make apps reload from scratch. More free RAM after stopping applications does not establish better battery life or responsiveness. Keep messaging, navigation, accessibility, and payment apps in the ignore list when their background operation matters.