eos-stop-app

Stop an Android app on a connected device via adb shell am force-stop.

1|Updated Jul 31, 2025
One-click install
npx skills add https://github.com/asnar00/miso --skill eos-stop-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eos-stop-app
Source: https://github.com/asnar00/miso/tree/main/.claude/skills/eos-stop-app
Command: npx skills add https://github.com/asnar00/miso --skill eos-stop-app

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires android-platform-tools, and includes scripts (resource) components.

What problem does it solve?

This Skill provides a reliable and clean way to stop an Android/e/OS app running on a connected device. It automates the adb shell am force-stop command, ensuring the app terminates gracefully without losing data, which is crucial for debugging and testing workflows.

Core Features & Use Cases

  • Graceful App Termination: Uses force-stop to cleanly shut down all app processes, clearing memory while preserving app data and settings.
  • Pre-Deployment Cleanup: Ensures a fresh state before deploying new versions or running tests, preventing conflicts or stale data issues.
  • Use Case: Before deploying a new build of your Android app, use this skill to stop the currently running version, ensuring a clean installation and test environment.

Quick Start

Stop the Android app running on my connected device.

Frequently Asked Questions about eos-stop-app

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop an Android app running on a connected device?

Stop an Android app by using ADB to execute the force-stop command, which terminates all app processes while preserving app data. Requires a USB-connected device with USB debugging enabled, ADB installed, and the app currently running.

What's the difference between stopping and uninstalling an Android app via ADB?

Stopping an app halts running processes and clears memory while preserving all app data and settings; uninstalling removes the app entirely. Use force-stop for debugging, testing, and pre-deployment cleanup workflows.

Can I stop an e/OS app the same way I stop Android apps?

Yes, e/OS apps stop using the same ADB force-stop mechanism as Android apps. Both platforms support USB debugging and the `adb shell am force-stop` command for graceful app termination.

Why would I stop an app before deploying a new build?

Stopping the running version before deployment ensures a clean installation environment, prevents conflicts with stale data, and guarantees the new build installs and runs fresh without residual state from the previous version.

Do I need any special setup to stop apps on my Android device?

Enable USB debugging on your device, connect it via USB, install Android Platform Tools with ADB, and authorize the connection when prompted. The app must be running for force-stop to take effect.

What happens to app data when I force-stop an Android app?

Force-stopping terminates all running processes and clears app memory, but all stored data, settings, and preferences are preserved. The app retains its state for the next launch.