luisfvmartins/clean-my-android

Clean My Android is designed to be used preferably with the help of an AI assistant of the user's choice. The AI guides the investigation, interprets device-specific data, explains risks, organizes evidence, and prepares the report. You remain in control: no device changes may be made without your explicit authorization.

You are not tied to a provider. You may use ChatGPT, Claude, Gemini, Antigravity, Codex, or another assistant capable of working with the project files. To run commands and collect data directly, choose an agent with access to your computer's terminal and ADB. A chat without device access can still guide the analysis, but it cannot inspect the device directly.

Recommended workflow

1. Prepare the environment: install ADB, enable USB or wireless debugging, and authorize the computer on the device.
2. Open the project in your assistant: clone the repository and open its folder in your AI agent.
3. Load the instructions: ask the assistant to read AI_INSTRUCTIONS.md and follow the individual device audit guide.
4. Inspect first: the AI identifies the device and collects the initial state without making changes.
5. Review the plan: examine package analysis, risks, proposed commands, and rollback methods.
6. Authorize deliberately: changes may only happen after your explicit approval, in controlled steps.
7. Compare and document: the AI repeats data collection, records tests and limitations, and prepares the before/after report.
8. Contribute: review and sanitize the files and, if you choose, submit the audit through a Pull Request.

Requirements

• Linux, macOS, or Windows with Android Debug Bridge (ADB) installed.
• USB or wireless debugging enabled on the device.
• Computer authorized by Android.
• A connected device identified as the target.
• An assistant with access to the project folder and terminal/ADB for direct automation.

Which assistant should you use?

Use the assistant you prefer. The project does not require a subscription, model, or specific service. To perform the audit directly, the agent must be able to read repository files and access the terminal where ADB is available. Review the permissions granted to the agent and do not enable unnecessary access.

Manual execution (advanced alternative)

Users experienced with Android, ADB, permissions, services, and package management may follow the procedure manually without AI. The same safety and documentation workflow applies; only the person performing the analysis and organizing the results changes.

Clone the project:

git clone https://github.com/luisfvmartins/clean-my-android.git
cd clean-my-android

Run an initial inspection:

adb devices -l
./scripts/debloat.sh

The default mode identifies the device and lists packages disabled for the primary user. It makes no changes.

Changes: only when explicitly supported

The script's apply mode is restricted to the Motorola Moto G54 5G running Android 15, requires typed confirmation, and acts on one package per execution:

./scripts/debloat.sh --apply package.name

Do not use this command on another model or Android version. The protected-components list is an additional safeguard, not a guarantee that every package outside it is safe to disable.

To re-enable an individually disabled package:

./scripts/restore.sh package.name

Before making any change, read the individual device audit guide and follow its safety rules. Manual execution does not remove the need for evidence, authorization, reversibility, and testing.