Using App Ops with ADB to Fine‑Tune Android App Permissions

Android’s public permission manager hides many of the granular controls that power users and privacy‑conscious folks would like to see. App Ops is a hidden subsystem that records every operation an app requests – from accessing the camera to reading your clipboard – and lets you toggle each operation individually. While the UI is hidden, you can reach it through adb (Android Debug Bridge). This guide walks you through enabling ADB, listing an app’s operations, changing them safely, and handling the most common pitfalls.

Why Use App Ops?

Android’s Settings > Apps > Permissions page shows only the permission groups (e.g., Camera, Location). Within a group, an app may request multiple low‑level operations, some of which you might not need. App Ops exposes those operations, allowing you to:

• Block an app from reading your clipboard while still allowing it to use the camera.
• Prevent background location polling for a navigation app that only needs GPS while active.
• Diagnose why an app is misbehaving by checking which operations are actually denied.

Because App Ops changes are stored in the system’s appops database, they survive reboots and do not require root.

Before You Start

If your device is running Android 12 or newer, the appops command is still present, but the syntax for some operations changed slightly. The steps below cover Android 9–13; later versions are similar.

Step 1 – Verify ADB Connection

Successful connection is essential; otherwise the following commands won’t reach the phone.

Step 2 – Identify the Target App

You need the app’s package name (e.g., com.whatsapp). You can find it in Settings > Apps, tap the app, then scroll to the bottom where the package name is shown, or use ADB:

Step 3 – List All App Ops for the App

Now you can see every operation the app has requested and its current mode.

If you see default for an operation you care about, the app’s permission group is currently granted, but you can still override it.

Step 4 – Change an Operation’s Mode

Use the set sub‑command to override a specific operation.

Replace deny with allow to re‑enable, or ignore to let the system decide based on the app’s foreground/background state (useful for location).

Step 5 – Apply Changes System‑Wide (Optional)

Some devices cache permission decisions until the next reboot. To make sure the new mode takes effect immediately, you can force‑stop the app:

Step 6 – Reset an Operation to Its Default

If you later decide you want the system to manage the operation again, reset it:

Step 7 – Bulk Editing with a Script (Advanced)

For power users who want to apply the same set of overrides to multiple apps, a short Bash script can save time. Below is an example that blocks clipboard access for a list of messaging apps:

#!/bin/bash
APPS=("com.whatsapp" "org.telegram.messenger" "com.facebook.orca")
for pkg in "${APPS[@]}"; do
  echo "Blocking clipboard for $pkg"
  adb shell cmd appops set "$pkg" READ_CLIPBOARD deny
  adb shell cmd appops set "$pkg" WRITE_CLIPBOARD deny
done

Save the script, make it executable (chmod +x block_clipboard.sh), and run it while your phone is connected. The script loops through each package and applies the same deny mode.

Common Mistakes & Troubleshooting

• Operation name typo: App Ops is case‑sensitive. Using read_clipboard instead of READ_CLIPBOARD will return Unknown operation. Double‑check the exact spelling from the get output.
• Permission resets after reboot: On some OEM skins (e.g., Xiaomi, OnePlus), a custom battery‑optimization service may revert App Ops changes. In that case, add the app to the device’s “Do not optimize” list under Settings > Battery > Battery optimization.
• App crashes after denying a critical operation: Some apps assume certain operations are always allowed (e.g., a camera app needing CAMERA). If the app crashes, reset that operation to allow or default.
• “Permission denied” error from ADB: Ensure you are running the terminal with administrator rights (Windows) or using sudo (Linux/macOS). Also verify that USB debugging is still enabled.

Safety Warning

When to Use App Ops vs. Standard Permissions

Use the regular Settings UI for most cases – it’s simpler and less risky. Reserve App Ops for these scenarios:

• You want to block a specific sub‑operation that the UI groups together (e.g., clipboard access while keeping other data‑sharing permissions).
• You are troubleshooting an app that misbehaves after a permission change and need to isolate the offending operation.
• You want a temporary deny that can be toggled without navigating deep menus each time.

Wrapping Up

App Ops gives you a level of control that the standard permission manager hides. By using ADB you can list, modify, and reset individual operations without rooting your device. Remember to test each change, keep a note of the original state, and revert if you notice instability. With this workflow you can tighten privacy, reduce background activity, and gain a deeper understanding of how Android apps interact with your device.