What is USB Debugging on Android?

If you are trying to use Andora (or any ADB-based tool) with your Android device, USB debugging is the one prerequisite you cannot skip. This guide explains exactly what it does, how to turn it on for every major Android version, what happens after you connect, and whether it is safe to leave enabled.

What USB Debugging Actually Enables

USB debugging opens a channel — specifically, it starts the ADB daemon (adbd) on your device and lets it accept connections. Without this setting enabled, plugging your phone into a PC only gives the PC access to MTP file transfer or charging. The ADB channel remains closed.

Once USB debugging is on and the device is connected to an authorized computer, that computer can:

• Install and uninstall APKs — including apps from outside the Play Store
• Push and pull files anywhere the app-level permissions allow
• Read live system logs via adb logcat
• Run shell commands on the device
• Mirror the screen and relay touch input (used by Andora Pro's screen mirroring)
• Control developer settings like animation speed, GPU rendering options, and mock locations
• Automate UI interactions for testing

This is why USB debugging is a Developer Option — it exposes capabilities that are powerful and intentional for development but not something average users need active day-to-day.

How to Enable USB Debugging: Step-by-Step

USB debugging is hidden behind Developer Options, which itself is hidden by default. You need to unlock Developer Options before you can find the USB debugging toggle.

Step 1: Unlock Developer Options

1. Open Settings on your Android device.
2. Scroll down and tap About Phone (on some devices it is under General Management or System).
3. Find Build Number and tap it seven times in quick succession.
4. You will see a toast message: "You are now a developer!"

On some manufacturer skins the path is slightly different:

• Samsung (One UI) — Settings > About Phone > Software Information > Build Number
• Xiaomi (MIUI/HyperOS) — Settings > About Phone > All Specs > MIUI Version (tap that, not Build Number)
• OnePlus (OxygenOS) — Settings > About Device > Build Number
• Pixel / Stock Android — Settings > About Phone > Build Number

Step 2: Enable USB Debugging

1. Go back to the main Settings menu.
2. Tap Developer Options (now visible, usually near the bottom of Settings or under System).
3. Make sure Developer Options is toggled On at the top of the page.
4. Scroll down and find USB Debugging.
5. Toggle it On. Confirm any warning dialog that appears.

What Happens When You Connect to a PC

The first time you connect your device to a new computer after enabling USB debugging, Android will display an authorization prompt:

"Allow USB debugging? The computer's RSA key fingerprint is: [fingerprint]. Always allow from this computer?"

This RSA key fingerprint is unique to each computer. When you tap Allow, Android saves that fingerprint and will automatically authorize that specific computer in the future. If you tap Always allow from this computer, you will not be prompted again for that PC.

If you revoke all USB debugging authorizations (there is a button for this in Developer Options — "Revoke USB debugging authorizations"), every computer will need to be re-approved on the next connection.

Why Andora Needs USB Debugging

Andora communicates with your Android device through ADB, which requires USB debugging to be active. When you launch Andora and plug in your device, it automatically detects the ADB daemon and establishes a connection.

For the free features — APK installation, file browsing, logcat, device info — USB debugging over a cable is all you need. For wireless ADB (Andora Pro), you start with a USB connection to pair once, then can disconnect the cable and continue using Andora over WiFi for the rest of the session.

Is It Safe to Leave USB Debugging On?

The short answer: at home, on your own computer, yes — it is safe to leave on. The longer answer involves understanding what the actual risks are:

The real risk: untrusted USB connections

The danger with USB debugging is that any computer you plug into could theoretically try to initiate an ADB connection. If you plug into a public USB charging station (a "juice jacking" scenario), a compromised port could attempt to access your device via ADB. However, the RSA key authorization prompt means a connection cannot be established without you tapping Allow on your device screen — and only if your screen is unlocked when the connection is made.

What protects you

• The RSA key fingerprint system ensures only previously authorized computers can connect without interaction.
• Android requires the device screen to be unlocked for a new ADB connection to be authorized.
• If your screen is locked and you plug into an unknown computer, ADB will not be accessible.

Best practice

Leave USB debugging on if you use it regularly — the convenience is worth it for developers and power users. If you carry your device frequently and plug into public or shared USB ports, consider turning it off between sessions. You can toggle it in seconds from Developer Options whenever you need it.

Troubleshooting Common Issues

If your device is not showing up in Andora or in adb devices after enabling USB debugging:

• USB mode — pull down the notification shade and check that the USB connection mode is set to "File Transfer" or "MTP," not "Charging only." Some devices hide ADB behind certain USB modes.
• Missing driver (Windows) — some Android devices need a manufacturer USB driver for ADB to work on Windows. Search for "[your device brand] ADB driver Windows."
• RSA prompt missed — if you did not see the authorization prompt, try unplugging and replugging. Make sure the device screen is unlocked when you do.
• Revoked authorizations — if you revoked authorizations, you need to re-authorize. The prompt should appear on the next connection.

If you cannot find USB debugging in your settings at all, see our guide on USB debugging not showing for manufacturer-specific solutions.