Home » Android » android – Logcat not displaying my log calls

android – Logcat not displaying my log calls

Posted by: admin March 11, 2020 Leave a comment


I’m a total noob at Android programming, and wanted to learn how to debug my apps. I can’t seem to have my Log.i|d|v calls displayed in the LogCat.

Here’s the code that I’m using. As you can see I have defined a LOG_TAG constant, but can’t seem to find it in the LogCat. I have also imported android.util.Log AND I have made sure that in my AndroidManifest I have “debuggable” set to TRUE.

I have also checked http://developer.android.com/reference/android/util/Log.html w/o any luck resolving this issue.

What am I doing wrong? Am I even looking in the right place? I’ve tried using the DDMS and Debug perspective as well w/o any luck. Any help to this noob would be greatly appreciated. Thanks.

My environment:
Windows XP
IDE = Eclipse Version: 3.6.1, Build id: M20100909-0800
Emulator = having it point to android sdk 2.1 api 7

//very basic HELLO World code with a couple of Log.i calls

import android.app.Activity;
import android.os.Bundle;
import android.util.Log;

public class debugger extends Activity {
    private static final String LOG_TAG = "debugger";

    /** Called when the activity is first created. */
    public void onCreate(Bundle savedInstanceState) {
        Log.i(LOG_TAG, "line 13");

        Log.i(LOG_TAG, "CREATING NOW");
How to&Answers:

When using Eclipse, in the DDMS perspective, make sure the correct device (propably emulator-xxxx) is selected and highlighted. Only then will you get the logcat output in the logcat view.

Also, the Android plugin is a bit quircky, and sometimes only shows the last line in the logcat view. If this happens, try to clear the log. After that, you should get all the log entries again (works for me anyway).


If all else fails:

I did all the above things and couldn’t figure out what was wrong,

Test with:

adb logcat

to figure out that my entries were infact in logcat, but twas adt’s quirks.


Restart eclipse

This was the only thing that fixed it.


I’ve had the same problem using Android Studio and managed to get around by selecting No Filters in the select box in the top right corner of LogCat. By doing this I started receiving everything Android logs in the background into LogCat including my missing Log calls.

enter image description here


Restart Eclipse and check log cat will be displayed.


I figured out I was automatically importing com.sileria.Log (from some library project) instead of android.util.Log, where the latter was the correct one. Check your imports as well.


I’ve noticed that Eclipse will sometimes throw an exception upon starting an Android app, then LogCat stops updating. I’ve corrected that by simply restarting Eclipse. I’m not sure if you’ve tried that and I know it’s far from an optimal solution, but I suspect that the Eclipse plugin still has a few bugs to iron out.


Easiest way:

Check in your logcat window – TOP RIGHT corner PAUSE button || (Pause receiving new logcat messages)

Few clicks + eventually restart eclipse (usually works in my case)


I needed to restart the adb service with the command adb usb

Prior to this I was getting all logging and able to debug, but wasn’t getting my own log lines (yes, I was getting system logging associated with my application).


There are a number of reasons why you might not see logs, most of which are listed below. Here are some steps to check most reasons:

  1. Make sure you don’t have ‘android:debuggable=”false”‘ in your
  2. Make sure your logcat isn’t paused and make sure you are scrolled to the bottom
  3. Your filters should either be ‘no filters’ or your current app
  4. You have the correct device selected in your logcat devices list
  5. If you’re not getting any messages, try restarting adb. You can do that from Android Studio by clicking on the ‘restart’ icon, it’s right after the print icon for logcat and it looks like a green curved arrow coming out of a box. If you don’t see it, mouse over the ‘>>’ that continues the icon menu when the logcat is too small.


On Android Studio:
Click on the green arrow pointing to the right to restart the logging; if it is not visible, click on the >> icons to locate it.


I’m a newb as well to Android-Eclipse. Here’s what it took for me to get LogCat messages to display in Eclipse:
1: add this to the class in which the logcat message is called:
private static final String TAG = “MyActivity”; (per the documentation here)

2: add this Log.i(TAG, “inLayout – finished”); when you where you want to display a message

If the above doesn’t work, then shutdonw Eclipse and restart it and rerun your project.

It should then work.


There is one more thing to watch for:

On the top right side of the logcat there is a dropdown table for filtering messages by type. Make sure it’s on the level you are looking for (if it will be on the assert level, it will likely leave your logcat empty).


Please go to Task Manager and kill the adb.exe process. Restart your eclipse again.


try adb kill-server and then adb start-server command.


Probably it’s not be correct, and a little bit longer, but I solved this problem (Android Studio) by using this:

System.out.println("Some text here");

Like this:

try {
       ...code here...
} catch(Exception e) {
  System.out.println("Error desc: " + e.getMessage());


I spent several hours on such case. I saw only touch keys logs. Nothing more. Problem was… smarthphone. After restarting was OK. Disconnecting cable caused problem returned. Had to restart it again.
Looks like the Android USB communication is not well designed.



Just restart the eclipse

Works Perfect.


Using the SDK 4.0.3 you have to explicitly select it on debug configurations > project > target or else it will never show using Eclipse Indigo (3.7). Of course an eclipse restart ensues.


I had a problem seeing simple log output in logcat as well. My problem was solved when I installed the latest JDK. I just setup a new development machine and only had the JRE installed and instaling the JDK worked for me.


None of the other answers worked for me, but this did:

I removed my project from my workspace, then deleted anything that started with a dot (.settings, .project, etc.) from the project folder. Then I re-imported the projected. I’m missing some settings and breakpoints but at least it works.


I had been experiencing this problem and nothing seemed to work until I moved the log call into a handler. Now it works every time, no matter where you are at.


I made the mistake of typing in a search term in the logcat search box.
I forgot to delete it and hence couldn’t see the new logs. Since they didn’t match my search term and weren’t displayed.


In my case, I had to remove this line:

         android:debuggable="false"  <!-- Remove this line -->

From Application tag in my Manifest file.


Best solution for me was restart adb server (while I have Enabled ADB integration in Android studio – Tools – Android – checked). To do this quickly I created adbr.bat file inside android-sdk\platform-tools directory (where is adb.exe located) with this inside:

adb kill-server
adb start-server

Because I have this folder in PATH system variable, always when I need restart adb from Android studio, I can write only into terminal adbr and it is done.

Another option to do this is through Android Device Monitor in Devices tab – Menu after click on small arrow right – Reset adb.


For eclipse:
1) Go to ddms perspective.
2) Make sure that correct device is selected.
3) If already selected and not displaying logs, then restart ABD.
* Hope this will solve.


I restarted the ADB service as well with “adb usb” and fixes the problem for me. In fact, only one of my activities didn’t log anymore. All the others did log stuff. After restart adb everything works like a charm again. For the other people who’re searching for another solution: adb kill-server, adb start-server in CLI will often fix your problem aswell.


make your app force close once
this will start LogCat again …

use this for force close 😀



some times the problem is not from pc on the other hand IDE,ADB etc, but it arises from your device that doesn’t send logs to ADB so if you tried all the ways mentioned before and still your logcat is empty try to restart your device and try again.I tried all the ways mentioned above and neither of them worked but after a restart on my phone logcat worked like magic


I have this problems and fixed, String TAG without space:

“my tag” // noting show
“my_tag” // is ok


In my case I just had to add a name to the String. In first instance I just had a space in between the brackets

private static final String TAG = " ";

but after adding a name it worked perfectly.

private static final String TAG = "oncreate";


You’re trying to put Running Code on Working space.. so try to put your code on running code..