Reputation: 10102

Why are Log.d() and Log.v() not printing

I have the following test code in my Activity:

@Override
public void onStart() {
    super.onStart();
    Log.e(CLASS_NAME, "ERROR onStart()");
    Log.w(CLASS_NAME, "WARN onStart()");
    Log.i(CLASS_NAME, "INFO onStart()");
    Log.d(CLASS_NAME, "DEBUG onStart()");
    Log.v(CLASS_NAME, "VERBOSE onStart()");

On the logcat view in Android Studio, it only prints:

02-10 15:56:10.190    6194-6194/org.example.my_app E/MyActivity﹕ ERROR onStart()
02-10 15:56:10.190    6194-6194/org.example.my_app W/MyActivity﹕ WARN onStart()
02-10 15:56:10.190    6194-6194/org.example.my_app I/MyActivity﹕ INFO onStart()

On top of the box, the menu is set to Log level: “Verbose”, and if I go into the menu next to it, choose “Edit filter configuration”, “by Log Level” is also set to “Verbose”. Why are the Log.d() and Log.v() not printing anything? What might I am missing? Any suggestions would be appreciated.

Upvotes: 37

Answers (10)

dev

Reputation: 1

i had the same problem. I switched off and on developer options and usb debugging and all logs worked. i also enabled gpu debug layers in developer options(i dont think that helped).

Upvotes: 0

Apollo

Reputation: 131

I had similar problem to this one. However in my case the problem was empty first string. It worked in older version of Android Studio, but stopped working in Android Studio ver 5.6 after update. When I used: Log.d(string1, string2); in my logging wrapper class, then whenever string1 was "", the logcat would ignore it. The solution was to add

if(string1 == null || string1 == "") {
    string1 = "defaultString";
}

before

Log.d(string1, string2);

I hope this helps anyone with this problem.

Upvotes: 2

Serge Kishiko

Reputation: 486

I've faced also to the same issue. Even following the previous answers, I didn't find the way to show logs in the Logcat.

After many tries done on my own, here is the (other) way to get logs shown:

Just selecting "Show only selected application" in the combobox did the job. Priorly, it was "Firebase" which was selected.

Hopefully, you will see your logs ;-)

Upvotes: 9

Stephen Hosking

Reputation: 1465

This started happening with me in Android Studio 3. I was getting old Log.v's printing, but when I added a new one nothing happened. Ditto with debugger breakpoints.

Cleaning the solution and restarting Android Studio worked for me, but there was a simpler solution.

Disable Instant Run. It seems that Instant Run doesn't recognise new Log.v's or breakpoints.

Along the way I also added Gradle-aware Make to my Run/Debug configuration for the main activity. I don't know whether that was necessary, but I'm keeping it. ([Main Menu] Run -> Edit Configurations...)

Upvotes: 0

Fortran

Reputation: 2336

Fix For meizu phone

Settings -> Accessibility -> Developer options -> advanced logging->set "Allow all"

For Meizu MX4(Flyme 6.1.0.0), M2(Flyme 6.1.0.0G), M5(Flyme 6.3.0.0G) :

Settings->Accessibility - > Developer Options -> Performance optimization -> Advanced logging -> set "Allow all"

Huawei, logcat not showing the log for my app?

For other phone search in "developers options": option "logging" and set "all".

Upvotes: 13

0x777C

Reputation: 1047

For me the issue was that I had actually disabled the logger buffer in my developer settings so go to Settings -> Developer options -> Logger buffer size and set it to anything that isn't 'off'.

Upvotes: 3