Introduction

When Logcat shows nothing, the problem is usually not "Android stopped logging." It is almost always one of four things: the wrong device, an over-restrictive filter, missing app output, or an adb connection problem.

Start with the ADB Connection

If the device is not connected correctly, Logcat has nothing to read from. Check the connection first:

adb devices

You should see a device listed as device. If you see unauthorized, confirm the USB debugging prompt on the phone. If you see nothing, verify the cable, the emulator state, or wireless debugging setup.

Restarting the bridge is also worth trying when Logcat suddenly goes silent:

adb kill-server
adb start-server
adb devices

That sequence fixes a surprising number of stale connection issues.

Check the Selected Process and Filters

Android Studio Logcat often appears empty because the UI is filtering out the messages you expect. Common filter mistakes include:

• the wrong device is selected
• the wrong app process is selected
• log level is set to Warn or Error
• a custom tag filter excludes your messages

When in doubt, reset to the broadest view: select the device, choose "No Filters" or the equivalent broad mode, and lower the level to Verbose. Then generate a fresh log line from the app.

From the terminal, you can bypass the IDE completely:

adb logcat

If that shows logs but Android Studio does not, the problem is usually the IDE filter state rather than the device.

Make Sure the App Is Actually Logging

Sometimes Logcat is working correctly and the app simply never writes a line. Add an explicit test log in a code path you know will run:

1import android.util.Log
2
3class MainActivity : AppCompatActivity() {
4    override fun onStart() {
5        super.onStart()
6        Log.d("MainActivity", "onStart reached")
7    }
8}

Then filter by that tag:

adb logcat MainActivity:D *:S

This command shows DEBUG messages for MainActivity and silences most unrelated output. If even that test line does not appear, focus on process selection, deployment, or whether the activity is actually running.

Understand Build-Type Effects

Logs can disappear in release builds or minified builds for reasons that are easy to miss. Some teams route logging through wrappers that disable output outside debug builds. ProGuard or R8 rules can also affect custom logging frameworks.

For example:

1object AppLog {
2    fun d(tag: String, message: String) {
3        if (BuildConfig.DEBUG) {
4            Log.d(tag, message)
5        }
6    }
7}

If you install a release variant, this wrapper may intentionally produce nothing. That is not a Logcat problem. It is application behavior.

Buffer and Timing Issues

Logcat uses ring buffers. If you attach late and the device is noisy, important lines may already be gone. Clearing the buffer and then reproducing the bug can help:

adb logcat -c
adb logcat

You can also narrow the output to the current app process in Android Studio or by tag in the terminal. That reduces the chance that important lines are buried under system noise.

Common Pitfalls

• Looking only inside Android Studio can hide the fact that adb logcat itself is working fine.
• Forgetting to select the current device or emulator is a routine cause of an empty Logcat window.
• Leaving a restrictive tag or package filter enabled makes Logcat look broken when it is only filtered.
• Testing a release build while expecting debug-only logs leads to the wrong diagnosis.
• Assuming the app emitted logs at all is risky; add one explicit Log.d in a known lifecycle method and verify from there.

Summary

• Empty Logcat usually comes from device connection issues, filters, or missing app log output.
• Start by checking adb devices, then reset filters and test with adb logcat.
• Add one explicit log statement in a guaranteed code path before debugging anything more complex.
• If terminal Logcat works but Android Studio does not, the IDE filter state is the likely cause.