Why doesn't logcat show anything in my Android?

Question

Why doesn't logcat show anything in my Android (while developing apps with Eclipse)?

It just doesn't print anything. It's empty.

Is it the logcat View in Eclipse that's blank, the output of the `adb logcat` command, or both? — David Webb, Feb 12 '10 at 08:10
It may also happen when debugging Android 7 (or higher) devices. [See this topic](http://stackoverflow.com/questions/39351106/eclipse-empty-logcat-with-android-7) — Geoffrey VL, Jan 27 '17 at 11:32
What do you mean by *"in my Android"*? Do you mean *"on my Android device"*? Or *"in Android Studio"*? Or something else? Please respond by [editing (changing) your question](https://stackoverflow.com/posts/2250112/edit), not here in comments (***without*** "Edit:", "Update:", or similar - the question should appear as if it was written today). — Peter Mortensen, Aug 30 '21 at 21:23

MoMo · Answer 1 · 2014-10-10T14:25:13.617

521

I had this same issue but my fix was much more basic:

If the LogCat panel is empty in Eclipse the emulator doesn't have the focus. Go to the DDMS perspective and try clicking on the 'emulator' entry in the Devices panel (top-left screen).

edited Oct 10 '14 at 14:25

answered May 31 '10 at 18:31

MoMo

8,149
3
35
31

66

Same thing happens with a physical device. You just have to click on the entry representing that device and the log messages suddenly come flooding in. – Tyler Jul 13 '10 at 04:10
25

If this doesn't work right away, restart eclipse, then it works, thanks @MoMo – Sam Sussman Jan 05 '12 at 17:07
1

On my target device, it showed my activity, click on it and then click on **Start Tracking** on the next window. – Radu Mar 27 '12 at 16:25
from last month I restart the eclipse as solution, you make it more faster :) – daksh21ubuntu Jun 24 '13 at 11:11
I have no idea where the "device tab" is supposed to be - someone has a picture? – newnewbie Sep 21 '14 at 21:20
**Window** / **Show View** / **Other...** / **Devices**. I've just upvoted this answer to 500. ;-) – Quip11 Jul 29 '15 at 18:56
@Tyler 12 years later and I have the same problem but this time clicking on the entry representing that (physical) device does not solve the issue. OTOH, every now and then I see all LogCat messages in one single long line. Could the problem be my el-cheapo Redmi 6A phone? – WebViewer Dec 06 '22 at 14:27

score 83 · Answer 2 · edited Dec 30 '16 at 07:32

83

Dial

*#*#2846579#*#*

and you will see a hidden menu. Go to the Project Menu > Background Setting > Log setting and define the log availability (log switch) and level (log level setting).

Please note this may apply to Huawei phones only as is stated for an Ideos X3 (here) and is tested at a Honor U8860.

edited Dec 30 '16 at 07:32

Pang

9,564
146
81
122

answered Jun 09 '12 at 17:28

denispyr

1,403
3
21
34

To tell the truth, my Honor starts showing log in LogCat and then it may stop. I don't rely on LogCat with *this* device. You may install CatLog (https://play.google.com/store/apps/details?id=com.nolanlawson.logcat) or a similar tool - that one always works! Good luck. – denispyr Aug 08 '13 at 11:14
4

Make sure you restart your phone after setting the log. – William Aug 23 '13 at 05:02
Works on Huawei P7-L07 – Nick Dong Sep 23 '14 at 09:29
Works on Huawei Ascend Y300. Thanks a lot – chinthana Dec 28 '14 at 08:15
Worked for Huawei P8 Lite - ALE L21 ! Thank you ! – nightfixed Mar 24 '17 at 10:15
Worked for Huawei MediaPad M2 8.0 M2-801L Tablet. – enreas Apr 20 '17 at 09:17
There isn't any hidden many. It showing "VersionInfoQuery" activity. And also in that UI only provide information about version, Device ext.. Need help – E J Chathuranga Sep 27 '17 at 08:05
this solution did worked for me https://stackoverflow.com/questions/42691076/logcat-not-showing-errors-from-my-huawei-p9-phone – surhidamatya Jan 17 '18 at 04:59

Fyodor · Answer 3 · 2012-05-26T21:13:47.347

71

If clicking in Devices panel doesn't bring the spam, use reset adb in dropout menu from triangle on the right of the snapshot button.

edited May 26 '12 at 21:13

answered Feb 02 '12 at 15:44

Fyodor

2,793
4
21
24

2

Watch out because Console will spit out [YYYY-MM-DD HH:MM:SS - DeviceMonitor] Adb connection Error:EOF... Connection attempts: 1. As posted elsewhere on SO (http://stackoverflow.com/questions/1997474/android-eclipse-plugin-reset-adb-gives-adb-connection-erroreof-error-not-b), this is benign but you will have to unplug/reconnect your devices so they show up. – paulrehkugler Nov 30 '12 at 19:27
This fixed it, and I didn't have to reconnect my device for it to show up, fwiw – Achal Dave Oct 29 '13 at 03:50
Just found it, but I only get message that Adb connection was forcebly close and no reconnection. – Johnny_D Feb 09 '14 at 23:10

score 41 · Answer 4 · edited Aug 30 '21 at 21:28

41

I have the same problem on/off and the way I solved is by menu File → Restart (restart Eclipse).

edited Aug 30 '21 at 21:28

Peter Mortensen

30,738
21
105
131

answered Mar 01 '12 at 04:49

Nick Kahn

19,652
91
275
406

1

No need restart eclipse > just select your emulator or device from DDMS – Mahesh Nov 22 '12 at 11:55
2

We dont have time to restart the eclipse as it takes 5-10 minutes :( – Vivek Warde Jan 29 '14 at 16:07

Nikola Smiljanić · Accepted Answer · 2021-08-31T23:20:04.713

33

Maybe you have Mylyn installed?

http://code.google.com/p/android/issues/detail?id=1808

edited Aug 31 '21 at 23:20

answered Feb 12 '10 at 07:42

Nikola Smiljanić

26,745
6
48
60

2

That doesn't matter. I removed my Mylyn plugins, and the issue persisted. – IgorGanapolsky Mar 13 '12 at 17:52
71

I don't think there is any reason to down-vote this answer, it's the accepted answer because it solved the problem for TIMEX. If this is not your issue then feel free to up-vote another answer. – Nikola Smiljanić Mar 18 '12 at 18:33
What is "Mylyn"? Can you add a link (or similar) to your answer? (But ***without*** "Edit:", "Update:", or similar - the answer should appear as if it was written today.) – Peter Mortensen Aug 30 '21 at 21:24
@PeterMortensen I had trouble remembering what it was myself ;) – Nikola Smiljanić Aug 31 '21 at 23:21

score 11 · Answer 6 · edited Aug 30 '21 at 21:29

11

While the answer provided by MoMo will resolve the problem temporarily it will most likely reoccur the next time you launch Eclipse, or launch on a different Emulator/Device.

Instead of always having to select my device in the devices view I've found a better solution is to go into your Eclipse preferences and navigate to Android -> LogCat in the list on the left and then enable "Monitor logcat for messages from applications in workspace".

This way no matter what device you are using logcat will automatically start showing output from it as soon as the application launches.

It will also setup a filter that ensures that only output from your application is displayed, which you can reuse / disable as needed.

Logcat application output enabling setting

edited Aug 30 '21 at 21:29

Peter Mortensen

30,738
21
105
131

answered Aug 27 '12 at 14:10

Justin Buser

2,813
25
32

"Window" -> Android -> ... etc. – basickarl Mar 12 '14 at 15:08
INFO: This fixed LogCat on Blackberry Priv Android 5.1.1 Only when I press RUN and this is enough – BIOHAZARD Jul 28 '16 at 20:22

Roland · Answer 7 · 2012-06-07T02:55:19.837

10

Maybe the log is not enabled in your device. Try to run the following command.

adb shell
echo 1 > /sys/kernel/logger/log_main/enable

edited Jun 07 '12 at 02:55

answered Nov 30 '10 at 09:08

Roland

1,109
13
15

1

That was the problem in my Huawei U8500. Neither adb logcat nor eclipse were showing anything. Thanks! – hectorct Sep 10 '11 at 11:22
19

What does it mean if there is no 'logger' directory inside of `/sys/kernel`? – aroth Jan 16 '12 at 06:50
1

Try in another directory: echo 1 > /sys/kernel/logger_mode/logger_mode – AK87 Jul 08 '15 at 07:48
That directory is not there either. There is a config directory, but it is empty. – Raja Apr 24 '17 at 18:44
@Roland There is no `/sys/kernel/logger` in Redmi 6A (the device I use for debugging). – WebViewer Dec 06 '22 at 14:36

score 6 · Answer 8 · edited Aug 30 '21 at 22:22

OK. This is how I got it to work. I first followed MoMo's advice, that is...

If the LogCat panel is empty in Eclipse the emulator doesn't have the focus. Go to the DDMS perspective and try clicking on the 'emulator' entry in the Devices panel (top-left screen).

But to no avail.

I then attempted to reset adb (Android Debug Bridge) as suggested by fyodorananiev. How? Menu Window → Devices → upside down triangle menu button → Reset adb.

It also didn't work, but I did get the following message:

Android hierarchyviewer: Unable to get the focused window from device

This meant that MoMo was right in that my Android device or emulator didn't have focus. However, the solution I did in my case is different.

What worked for me:

Replugged my Android device, which was connected to my computer via USB.
Restarted Eclipse, as mentioned by Abu Hamzah (although since I didn't know I can do menu File → Restart, I manually closed down Eclipse, and then restarted the application again.)

I can now see logs in my logcat.

What worked for you is waaaay too cumbersome and time consuming. It used to work for me without a hitch on a Nexsus One and LG LS670 and Samsung Galaxy S. I have no idea what happened the current state of Eclipse+ADT development (other than that it is no longer supported by Google). — WebViewer, Dec 06 '22 at 14:44

score 3 · Answer 9 · edited Aug 30 '21 at 22:21

3

If you are using a device, the simplest check is to restart Eclipse.

You don't have to shutdown Eclipse

Use menu File → Restart

In a quick second or two you should see your LogCat return.

edited Aug 30 '21 at 22:21

Peter Mortensen

30,738
21
105
131

answered Oct 22 '13 at 17:13

seth yount

132
6

1

it is as long as shutdown eclipse, I don't see the difference. – LeSam Mar 17 '14 at 02:34
@LeSam, yeah, the only difference is that Eclipse is re-started automatically. – Jack Miller Jan 28 '15 at 07:25

score 3 · Answer 10 · answered Aug 29 '16 at 12:58

3

Go to Developer settings and check that for Debugging\Select App for Debugging is empty

answered Aug 29 '16 at 12:58

Henadzi Rabkin

6,834
3
32
39

I have a BLU Dash XL. I couldn't see the log and tried this solution. BAM! Worked!! Thanks! – Grace Huang Apr 11 '17 at 21:26
Unfortunately, `Select debug app` does not solve my problem. – WebViewer Dec 06 '22 at 14:47

score 2 · Answer 11 · answered Jun 28 '12 at 22:45

2

The simplest solution worked for me: Shutdown and restart my phone and Eclipse alike.

answered Jun 28 '12 at 22:45

Chris Lacy

4,222
3
35
33

1

No need restart eclipse > just select your emulator or device from DDMS – Mahesh Nov 22 '12 at 11:55

score 2 · Answer 12 · edited Aug 30 '21 at 21:30

2

I think you haven't selected the device or emulator, on which running your application.

In Eclipse, go to DDMS Perspective and select the device or emulator on which you are running your application.

(Note: No need to restart Eclipse)

edited Aug 30 '21 at 21:30

Peter Mortensen

30,738
21
105
131

answered Nov 22 '12 at 11:02

Mahesh

2,862
2
31
41

score 2 · Answer 13 · edited Aug 30 '21 at 22:43

It gets interesting when you find out that none of all the answers in for this question were helpful.

And then you find out that in your version of ADT 22.6.3.v201404151837-1123206 if you add two filters with the same package name (application name) then the log will not appear.

It was weird, because the log was there two seconds ago, and launching the app in debug mode adds a default filter for the app which collides with the filter I've setup manually, and then ADT magically removes all the logs, and none of the filter worked including the all messages (no filters)!

But it was masking another issue...

I'm working with dual screens. The second one is connected via VGA/RGB - (not really sure what it's called) and what can I do. I'm a ton more comfortable with the logcat away from my code editors, so I've placed it in another window, and as it turns out that is the main reason for the disappearing logs for me.

score 2 · Answer 14 · edited Aug 30 '21 at 22:40

2

In case if you are using CyanogenMod in your mobile, it will disable logging by default. Try this method:

In your device, open "/system/etc/init.d/" folder If there are many files, try opening each file and find for this line:

rm /dev/log/main

Now, comment this line like this: # rm /dev/log/main

Save the file and reboot.

edited Aug 30 '21 at 22:40

Peter Mortensen

30,738
21
105
131

answered Oct 09 '14 at 18:44

Jaswanth Kumar

3,531
3
23
26

score 2 · Answer 15 · answered Feb 28 '17 at 06:02

2

I had faced the same issue but in my case logs are shown when other devices are connected and not shown when my device is connected.

It took me days and finally, the issue resolved when I restarted my phone.

answered Feb 28 '17 at 06:02

Srikar Reddy

3,650
4
36
58

Happened to me too – AlvaroSantisteban Apr 09 '20 at 10:08

score 2 · Answer 16 · answered Aug 10 '21 at 16:16

Below: Really dumb answer, but it happens!

My cat stepped on the space button while I was away and [SPACE]xN was typed in the search bar.

That resulted in an empty Log Cat. I tried restarting and wasted like 1 hour before I realized I should clear my search bar.

TLDR; CLEAR YOUR LOG CAT SEARCH BAR!

score 1 · Answer 17 · answered Apr 09 '13 at 20:17

1

If using the DDMS to refocus doesn't work, try closing and restarting LogCat. That helped me.

answered Apr 09 '13 at 20:17

lorless

4,126
8
30
41

score 1 · Answer 18 · answered Nov 04 '13 at 23:11

1

I've had this happen occasionally. Closing and re-opening Eclipse seems to fix it.

answered Nov 04 '13 at 23:11

Lars

9,976
4
34
40

score 1 · Answer 19 · edited Aug 30 '21 at 22:47

1

If you tried all of the others, and still got losing on an empty logcat. I got another simple way.

Download an old version of ADB, and try again. It might be working, at least working for me with Android 7.0 phone (vendor stopped updating).

Here is the useful link for old versions.

edited Aug 30 '21 at 22:47

Peter Mortensen

30,738
21
105
131

answered Jun 07 '19 at 16:20

Tokenyet

4,063
2
27
43

score 0 · Answer 20 · edited Aug 30 '21 at 21:32

0

Check if the Console is telling you something. Usually this happens when the project could not be installed in the device, and just shows the previous one.

The most common case I have seen this is when there are different signatures in the project, and is not running at all. Please, read all the red letters you see. If the LogCat does not show anything, take for sure that the Console will do.

edited Aug 30 '21 at 21:32

Peter Mortensen

30,738
21
105
131

answered Dec 17 '12 at 05:53

Sterling Diaz

3,789
2
31
35

score 0 · Answer 21 · answered Aug 27 '13 at 04:35

I had the same issue. No need to restart Eclipse or clean your project. You may follow:

Click on LogCat icon on bottom right corner of eclipse.
In Saved Filter Pane (Left side), double click package of your project (in my case it's com.apps..*).
In Logcate Message Filter Settings popup, select desired option of "by Log Level". You can select verbose, info, error etc.
Click Ok.
Run/Debug your project.

score 0 · Answer 22 · edited Aug 30 '21 at 22:38

0

What worked for me besides restarting Eclipse was:

Remove custom filters

After removing all filters, logcat was filled with text again

edited Aug 30 '21 at 22:38

Peter Mortensen

30,738
21
105
131

answered Mar 23 '15 at 12:13

sam

4,357
5
29
34

score 0 · Answer 23 · edited Aug 30 '21 at 22:44

0

Close logcat and then reopen it from Window → Show View → Others.

edited Aug 30 '21 at 22:44

Peter Mortensen

30,738
21
105
131

answered Nov 03 '15 at 12:11

score 0 · Answer 24 · edited Aug 30 '21 at 22:45

0

If you're using Eclipse v4.5 (Mars) (at least, Mars.1 or Mars.2), try the solution described here: Logcat show invisible messages in Eclipse Mars.

It helped in my case.

edited Aug 30 '21 at 22:45

Peter Mortensen

30,738
21
105
131

answered Mar 27 '16 at 08:54

Dmitry Frank

10,417
10
64
114

score 0 · Answer 25 · answered Jun 07 '16 at 05:22

0

This is simple.

Just close the Logcat from eclipse.

Then reopen it by following steps in Eclipse.

Window - Show View - Other - Android - LogCat - ok

Hope this solves your problem.

answered Jun 07 '16 at 05:22

DevGo

1,045
1
16
42

score 0 · Answer 26 · edited Aug 30 '21 at 22:19

0

Set the same date and time in your Android phone and in your laptop.

I had a similar problem of logs not showing, and when I set the correct date in the phone I started seeing the logs (I restarted the phone and the hour was completely wrong!).

edited Aug 30 '21 at 22:19

Peter Mortensen

30,738
21
105
131

answered Aug 08 '16 at 18:30

Marc Cayuela

1,504
13
26

score 0 · Answer 27 · edited Nov 30 '18 at 09:49

0

Many times when I switched to a new Android device, I do see no more logcat messages. Unfortunately, none of the above suggestions worked for me (Eclipse Photon 4.8.0).

I am now using this . It seems to work for different devices.

edited Nov 30 '18 at 09:49

Gihan Saranga Siriwardhana

891
9
27

answered Nov 30 '18 at 08:09

AMRAY

21
3

score 0 · Answer 28 · edited Aug 30 '21 at 22:16

For OnePlus devices and Ubuntu OS:

Install Wine on Ubuntu

Install ADB tools on Ubuntu

 sudo apt-get install android-tools-adb

Now, attach your device to PC with USB.
Open mounted "One Plus Drivers". A disc like icon
Right click on OnePlus_USB_Drivers_setup.exe and run with Wine
Then open the terminal in the present drive where your "OnePlus_USB_Drivers_setup.exe" and other driver files exists. And run
```
 ./adb_config_Linux_OSX.sh or sh adb_config_Linux_OSX.sh
```
Close this terminal
Open a new terminal and run
```
 adb server-start
```

Your OnePlus device should prompt you to recognise your PC as a debugging agent.

Now, run on the terminal. It should show your device.

adb devices

Reference: [SOLVED] Android Studio does not recognise my One Plus Two in Linux

WebViewer · Answer 29 · 2022-12-07T17:15:11.300

In my case (after trying all the answers provided here to no avail), the problem (and solution) has to do with port 8700:

What I needed to do is:

Exit "Android Device Monitor" (monitor.bat)
Exit all instances of Eclipse.
C:\adt-bundle-windows-x86_64\sdk\tools>..\platform-tools\adb.exe kill-server
C:\adt-bundle-windows-x86_64\sdk\tools>..\platform-tools\adb.exe start-server
C:\adt-bundle-windows-x86_64\sdk\tools> monitor.bat

Also, the Scroll Lock button, needs to be "pressed/active":

Not the other way:

Why doesn't logcat show anything in my Android?

29 Answers29

Linked

Related