Why is logcat not showing anything?

Question

I am using Eclipse classic to develop my Android applications. But I am not able to see any messages in the LogCat. Till yesterday it was showing each and every message, but now it is not showing anything. I have written a lot of log statements to trace my program, but because of this I am not able to trace.

Where is the problem?

have you cleared the adb logcat command, adb logcat -c? – NyanLH Mar 02 '12 at 07:55 — NyanLH, Mar 02 '12 at 07:55
I just re-connect my device, It's running. – Dec 19 '17 at 06:35 — , Dec 19 '17 at 06:35

score 70 · Accepted Answer · edited Mar 20 '14 at 13:34

70

Try these first

Go to the device tab, click your device. and go back to the logcat tab
You might have filter set.
You are probably viewing the wrong package.

edited Mar 20 '14 at 13:34

Not a bug

4,286
2
40
80

answered Mar 02 '12 at 07:44

CChi

3,054
1
20
15

5

+1 and reloading the Eclipse helped – Sydwell Mar 29 '14 at 15:51
Clicking on the device solved it for me. – cmarcelk Jun 04 '14 at 20:38
1

This was driving me absolutely mental, cos it was working last night and then not this morning! Thank you! – BSnapZ Jul 01 '14 at 23:15
2

Android Studio added a dummy listener interface to one of my fragments when I used the IDE template. This was throwing a class cast exception that was outside my current project filters. – Justin Wiseman Feb 10 '15 at 20:53
1

Package name is correct, Device is correct, I set "no filter" to check if anything is there ... but nothing is getting printed ! I have used Nexus 9 api 17 ARM based emulator ??!?!?!?!? – Bhuro Sep 02 '16 at 12:58
2

Restarting studio has worked for me ... – Bhuro Sep 02 '16 at 13:25
None of these 3 tips worked for me. Oh well. – WebViewer Dec 05 '22 at 12:36

score 36 · Answer 2 · edited Aug 08 '18 at 10:41

36

I've got it solved by:

Closing the logcat window
Running the following in command prompt:

adb kill-server
adb start-server

Opening logcat again

edited Aug 08 '18 at 10:41

André

4,417
4
29
56

answered Nov 25 '13 at 12:48

vijeth.ag

515
5
8

I tried all the above answers, only this works with me, thanks. Note: Instead of command prompt task manager can be used to kill adb, and then run the app again. – user2814778 Apr 20 '15 at 09:39
Cheers. It's only fix that worked for me. – Adam Maloney Sep 05 '18 at 08:04
only this works me. its really frustating.why logs are suddenly not showing. Tried everything. Its was like only at the mercy we can see sometimes. now this solves the problem – Santhosh Aug 16 '20 at 05:58
This didn't work for me either (in addition to 1st trying the accepted answer (https://stackoverflow.com/a/9529698/2597758) – WebViewer Dec 05 '22 at 12:44

score 10 · Answer 3 · answered Jan 11 '14 at 15:46

10

Go to Window - Preferences - Android - Logcat . On that page "Show logcat view if message priority is at least " select VERBOSE.

Preferences-Android_logcat

answered Jan 11 '14 at 15:46

Burhan ARAS

2,517
25
19

2

Please always explain in your answer what this does and how it solves the problem. That would be very helpful. – Benjamin Basmaci May 14 '19 at 07:56
This didn't work for me either -- in addition to trying https://stackoverflow.com/a/9529698/2597758 and https://stackoverflow.com/a/20193542/2597758 -- it appears the making LogCat work has lots of preconditions. – WebViewer Dec 05 '22 at 12:50

score 10 · Answer 4 · answered Mar 02 '12 at 07:56

Every now and then I experience that the logcat output in Eclipse stops showing any logs. It doesn't matter if I unplug and plug the device. It seems like the issue occurs if the logcat gets a ton of messages, and is unable to handle the amount.

The only thing working is restarting Eclipse or use DDMS directly (which also suffers from the same problem).

score 9 · Answer 5 · answered May 04 '14 at 14:43

9

This happens when you don't close eclipse for a long duration, just close eclipse and reopen it, your problem should be solved.

answered May 04 '14 at 14:43

Giridhar Karnik

2,213
4
27
47

1

its not resolving yet – Yogesh Seralia Jan 19 '16 at 05:30

score 7 · Answer 6 · answered Aug 16 '13 at 15:02

7

Correct answer: it is/was a bug in Eclipse. All I did to trigger it was to rename one of the filter and pressing the Run button.

Restarting Eclipse fixes it.

answered Aug 16 '13 at 15:02

Henrik Erlandsson

3,797
5
43
63

score 6 · Answer 7 · answered Mar 02 '12 at 08:05

In eclipse, go to: windows->preferences
Then go to Android->logcat and make sure you have the following setup:
1. double-click action: "go to problem (error line)
2. switch to: java
3. both checkboxes are checked

if your setup is fine, clean the project and restart eclipse

good luck!

score 4 · Answer 8 · answered Mar 02 '12 at 08:32

Some times it does happen on a slower machine that eclipse waits for emulator HOME screen and after waiting too long it shows that the emulator is offline. Secondly Make sure that you are looking in the correct filter or in all messages part.

Also you can do the following :

select the device and find your process (e.g. "com.android.myapp")
Look for its process id written to its left (eg. 17260)
Now go to logcat and add a new filter by witting a particular name and the specific Pid (say 17260)
Now select that filter and you'l be able to see your log messages

Good Luck!

score 3 · Answer 9 · answered Apr 02 '14 at 23:54

3

I had the same issue, but gave up on eclipse logcat panel and switched to cygwin+adb:

make sure the app is running and launch cygwin
cd /cygdrive/c/android_sdk/sdk/platform-tools #go to where adb.exe is
[optional] ./adb logcat -c #clean the log, obviously don't do this if you want to see some old messages
./adb logcat #see all messages

or

./adb logcat | grep "whatever" #look only for whatever you want to look for

answered Apr 02 '14 at 23:54

alexey

453
6
15

Tried every other solution listed to no avail. Although, I'd still rather it show up in Eclipse logcat panel, at least this command line option gave me access to the info I needed. Thanks for the idea. – Alex Sep 05 '14 at 00:11

score 1 · Answer 10 · answered Feb 07 '13 at 05:54

1

Go to Device from DDMS and open it.
Select your device from which device your application is running
Select your project which you run on this device

answered Feb 07 '13 at 05:54

Krunal Shah

1,438
1
17
29

Steps 1 & 2 are clear enough. Step 3 -- **where** do you "select your project"? – WebViewer Dec 05 '22 at 12:55

score 1 · Answer 11 · answered Feb 26 '13 at 03:06

I had this issue for the last few days and tried everything above.

As it turned out, my problem was that all my log statements were in a class that was not being reached. I thought it had because of what was being displayed but that was not the case.

So in short, check with the following

Post log statements at the beginning of every method.

score 1 · Answer 12 · answered Aug 26 '13 at 09:30

1

I too had the same problem , and I solved the issue by -> restart the eclipse -> go to ddms -> click on the emulator

answered Aug 26 '13 at 09:30

Jyotika Pandey

233
3
5
12

score 1 · Answer 13 · edited Nov 11 '13 at 17:52

I tried all the above solutions, but nothing did work. Then, I saw I had a button named "R", then something clicked in my mind, I renamed it to:

R1=(Button) findViewById(R.id.button1);

So maybe it was conflicting with R of Android and Java name of a button "R".
Hurray error got resolved.

Let us conclude with the following steps:

Check if u have any variable(button,textview) name which is “R”
Save your project, close Eclipse and then open it again.
Project --> clean
import android.R; remove this.
Correct answer: it is/was a bug in Eclipse. All I did to trigger it was to rename one of the filter and pressing the Run button. Restarting Eclipse fixes it.

score 1 · Answer 14 · answered Dec 12 '13 at 22:38

You might have switched off LogCat by Mistake

Go to Preferences>Android
Click LogCat and make sure there is a check next to "Monitor logcat for messages from applications in workspace"
Then select the dropdown "Show logcat view if message priority is at least" and choose "VERBOSE" (or depending on how you tag your Logs, but VERBOSE will get all output)
Click "Apply" and you should start seeing your messages again

score 1 · Answer 15 · answered Jul 22 '14 at 08:49

1

Make sure that you set

android:debuggable="true"

in your manifest file.

answered Jul 22 '14 at 08:49

molu2008

1,237
2
15
20

3

Warning: `Avoid hardcoding the debug mode; leaving it out allows debug and release builds to automatically assign one.` – Lenik Aug 26 '14 at 08:09

score 1 · Answer 16 · edited Oct 19 '14 at 11:12

1

I was facing the same problem and the following steps resolved the issue:

Restart my Eclipse
Restart my Emulator
Select devices tab from DDMS perspective in Eclipse.

edited Oct 19 '14 at 11:12

Chilledrat

2,593
3
28
38

answered Oct 19 '14 at 11:01

Arti

11
1

Already have good and well accepted answer. – tod Oct 19 '14 at 11:33

score 1 · Answer 17 · answered Nov 21 '14 at 18:56

1

Check the device is not at fault. My device was set not to log, accidentally disabled it via boeffla kernel. After turning it back on logcat worked fine.

answered Nov 21 '14 at 18:56

Guernica

246
5
21

Yes, this could be very well my case, testing on a Mi/Xiaomi. – WebViewer Dec 05 '22 at 13:24

score 1 · Answer 18 · edited Dec 05 '14 at 11:55

1

Go to windows->preference->android->logcat

select the option - show logcat if message priority is atleat verbose.

It will show all the events of device and close all the perpestive and open logcat it will be working again.

edited Dec 05 '14 at 11:55

Helping Hands

5,292
9
60
127

answered Dec 05 '14 at 11:04

KlwntSingh

1,084
8
26

Unable to find "Go to windows->preference->android->logcat" on WIndows 10 Android studio 2.1.3 !?!?!?! Which OS ? – Bhuro Sep 02 '16 at 13:01
@Bhuro I used windows 8 and eclipse – KlwntSingh Sep 03 '16 at 15:00

score 0 · Answer 19 · answered Jan 30 '15 at 09:27

0

On right top corner click on "Display Saved Filter View" or if "display saved filter view" is already open then just click on the red - icon to delete selected logcat filter.

answered Jan 30 '15 at 09:27

RichieRich

19
7

Why is logcat not showing anything?

19 Answers19

Linked