Enable and Use Android Developer Options for Advanced Debugging (No Root)

Before you start

Preparing your device and PC makes the whole process smoother and prevents accidental data loss. You will need:

• A USB‑C or micro‑USB cable that can transfer data (charging‑only cables won’t work).
• A computer running Windows, macOS, or Linux with administrator rights.
• Wi‑Fi or a stable power source for the phone – debugging can be power‑hungry.
• Optional but recommended: a recent backup of your important data (Settings > System > Backup).

Step 1 – Activate Developer Options

Developer Options are hidden by default. The activation method is stable across most Android versions, though the exact wording may vary slightly between manufacturers.

1. Open Settings on your phone.
2. Scroll to About phone (sometimes under System > About phone).
3. Find the entry named Build number. Tap it seven times. You may be prompted to enter your lock screen PIN or pattern.
4. After the seventh tap you should see a toast message: "You are now a developer!"
5. Return to the main Settings screen. A new menu entry called Developer options will appear, usually under System.

Step 2 – Turn on USB Debugging

USB debugging is the bridge that lets your computer issue ADB commands to the phone.

1. Open Settings > System > Developer options. (On some devices it may be directly under Settings.)
2. Scroll to the Debugging section.
3. Toggle USB debugging to ON.
4. When you connect the phone to a PC for the first time, a dialog appears: "Allow USB debugging?" Check Always allow from this computer and tap OK.

Step 3 – Install the Android Debug Bridge (ADB) on your computer

ADB is part of the Android SDK Platform‑Tools package. You only need the platform‑tools, not the full SDK.

Windows

1. Download the latest platform-tools.zip from the official Android developer site (search “Android SDK Platform‑Tools”).
2. Extract the zip to a folder, e.g., C:\adb.
3. Open Command Prompt as Administrator, then run cd C:\adb.
4. Test the installation by typing adb version. You should see the version number.

macOS

1. Open Terminal.
2. Use Homebrew (if installed) – run brew install --cask android-platform-tools. Otherwise, download the zip as for Windows and extract to /usr/local/adb.
3. Add the folder to your PATH by editing ~/.zshrc or ~/.bash_profile:

   export PATH=$PATH:/usr/local/adb

4. Run adb version to confirm.

Linux

1. On Debian/Ubuntu, install via apt: sudo apt update && sudo apt install android-tools-adb.
2. On Fedora: sudo dnf install android-tools.
3. Verify with adb version.

Step 4 – Verify the ADB connection

1. Connect the phone to the computer with the data cable.
2. On the computer, run adb devices.
3. You should see a line similar to xxxxxxxxxxxx device. If the status reads unauthorized, check the phone for the USB‑debugging permission dialog and grant access.

Step 5 – Capture a live log with Logcat

Logcat streams the system and app logs in real time. It is the primary tool for diagnosing crashes, ANR (Application Not Responding) events, and permission issues.

1. Open a terminal/command prompt where ADB is available.
2. Run adb logcat to start streaming all logs to the console.
3. To filter for a specific app, first find its package name (e.g., com.example.app) and then run:

   adb logcat | grep com.example.app

4. To save the output to a file for later analysis, use:

   adb logcat -d > mylog.txt

   The -d flag dumps the current buffer and exits.

adb logcat -v threadtime > detailed_log.txt

Step 6 – Generate a full bug report

Android can produce a comprehensive bug report that includes logs, system properties, and UI hierarchy snapshots.

1. In Developer options, scroll to Bug report and tap Take bug report.
2. Select Full report (or Interactive report** if you need UI state). The device will collect data for a few seconds.
3. When the notification appears, tap it and choose Share > USB (or email yourself). The report is saved as a .zip file.
4. On your computer, unzip the file. Inside you’ll find logcat.txt, system.log, and a bugreport.txt that aggregates everything.