android-ad-cleaner (rddmwmddr/android-ad-cleaner)Partly tested🇨🇳 CN

@GaoXiaoxiao2022 demonstrates the open-source android-ad-cleaner: with a USB cable and AGENTS.md, Codex / Claude turn off Android OEM ad switches over ADB

Chinese Android skins bury ad, trending-search and feed toggles. Open-source android-ad-cleaner (MIT, ~6.0k★, author rddmwmddr) needs no root or unlock: ADB flips built-in switches, can suspend ad packages (with consent), ships a desktop client and 35+ device recipes. AGENTS.md tells command-capable agents (Codex, Claude Code, WorkBuddy…) the hard rules and standard flow; a separate prompt guides chat-only AIs step by step. @GaoXiaoxiao2022 posted the clone → read AGENTS.md → ask before each change workflow. We read AGENTS.md/README/CHANGELOG and ran device-free unit tests (channel classification, never-suspend, entrypoint refs); this box had no phone or adbutils, so we did not run a recipe on hardware.

Visit site android-ad-cleaner (rddmwmddr/android-ad-cleaner) ↗
Pricing
Free
Region
China
Where it's from
Chinese community
Added
Nov 4, 2026
Tested on
Nov 4, 2026
Version we used
repo main ~ac3e5fa; desktop client docs v0.3.1; 35+ recipes
Categories
Automation & AgentsProductivity
Original author
高胜寒 @GaoXiaoxiao2022 ↗
Our test
Partly tested
Cost / time
Software is free/open source. You need a computer, a USB cable, and either a local coding agent (your Codex/Claude plan) or the official desktop client.
Source
X @GaoXiaoxiao2022 ↗GitHub rddmwmddr/android-ad-cleaner ↗

The task

Without root or unlocking, turn off OEM ads, trending search, minus-one feeds, store promos and marketing notifications—while keeping search, installs/updates, weather/parcel alerts working.

Steps

  1. Enable Developer options + USB debugging, plug in the cable, and always-allow the prompt. Pure HarmonyOS over HDC only is not supported yet.
  2. Pick a path: (A) desktop client from Releases (we saw v0.3.1 Mac/Windows builds)—connect → detect → choose → run; or (B) clone the repo and hand the job to a local agent.
  3. Agent path: `git clone https://github.com/rddmwmddr/android-ad-cleaner`, read AGENTS.md, `pip3 install -r requirements.txt` if needed. Paste the prompt below into Codex / Claude Code / WorkBuddy (anything that can run a shell).
  4. Standard command order (always `-s <serial>`): `run.py devices` → `check` → `backup` → `recipe` → `chan-scan` then edit the list → `chan-off` → after consent `suspend` / `quickapp off` → `finish`. The agent should explain each change before applying it.
  5. Without a shell agent, use `prompts/聊天AI提示词.md`: paste into a chat model, one step at a time, following the brand checklist or screenshots.

Prompt

Find and clone rddmwmddr/android-ad-cleaner on GitHub, read AGENTS.md, then help me remove ads on the Android phone plugged into this computer. Explain every change before you make it and wait for my OK; no root, no uninstalling system apps, and never tap Agree on license prompts for me.

What the author says

@GaoXiaoxiao2022: no root/unlock—one prompt has an AI drive the phone over ADB and flip deep ad toggles. Three steps: USB debugging → open Codex/WorkBuddy etc. → paste the prompt to clone and read AGENTS.md. Claimed results: clear trending search, minus-one feed/promo cards, store short-drama entries and banners, ad tracking and quick-app jumps; non-invasive, ask before changes, restore from the log.

Our test

Cloned rddmwmddr/android-ad-cleaner (mainline docs for client v0.3.1; around commit ac3e5fa). Read README, AGENTS.md, CHANGELOG, prompts chat template; `python3 tool/run.py --help`; ran device-free unittest modules: channel classification, never-suspend, entrypoint refs, doc consistency. No adbutils/phone; did not run check/recipe/chan-off.

What we found when we tried it:CLI help lists the full subcommand set; 35+ recipes on disk. Channel-classification and never-suspend cases passed (including whole-batch refuse when a protected package is mixed in). test_fixtures failed to import without adbutils—environment, not an assert. No device, so UI outcomes (trending search, minus-one, etc.) were not verified.

How to get in

GitHub/Releases; aimed at Chinese Android OEMs (OPPO/vivo/Xiaomi/Honor…). Original post and README primarily Chinese—EN readers can follow AGENTS.md command tables.

Who it suits

People stuck with OEM ads, trending search and marketing pushes; anyone willing to enable USB debugging and let an agent drive Settings.

Pitfalls

  • Pure HarmonyOS (HDC-only) isn't supported yet; with multiple devices you must pass `-s`.
  • AGENTS.md hard rules: no `pm uninstall` / `pm disable-user`, no touching system updates, never tap Agree for you, no account-page screenshots; "limit ad tracking" style switches must stay ON.
  • Search, minus-one and store packages are never-suspend—wrong suspends break features; unit tests cover whole-batch refusal.
  • No phone here: classification/never-suspend tests passed, but adbutils-dependent modules weren't fully installed; real recipe results depend on your OEM/OS build.

More in this category