LogCat Stops Startup in Eclipse Needs Restart

Question

Periodically, LogCat stops showing messages, although I'm in debug mode. In other cases, it displays only one line at a time! I have a solution, restart eclipse. But I would like to understand this better. This takes too long to restart eclipse when this happens. I saw this behavior on the emulator and connected to the device. Either LogCat shows a single line without history, or nothing.

Answer 1

Yes, I can return normal logcat by clearing the log. Also uncheck the "Limit console output" checkbox in Run / Debug-> Console.

Answer 2

I had the same problem and the solutions here did not work for me. The solution I found opens the DDMS perspective and selects the device and the current process in the Devices window. After that, LogCat comes back to life.

Answer 3

I solve these problems with LogCat in two ways:

• Clear log to correct one line at a time
• Opening the device window ( Window → Show View → Other → Android → Devices ) and clicking on the device for which I want to view the log. This forces Android to update LogCat on this device.

These are much simpler options than restarting eclipse or messing around with adb.

Answer 4

I had a problem with "one line at a time" several times. I don’t know why this is happening, but there is a very simple fix that works for me every time. Just press the clear button. Simple and easy.

I also had no Logcat messages. Typically, this is due to a problem with the emulator and requires a restart of the emulator.

Answer 5

In eclipse you need to provide more space for the log buffer, the default is 5000, I set it to 50,000 and there were no problems.

Window-> preference-> Android> LogCat maximum number of log messages for buffer __ set some number 50k in order

Answer 6

I would recommend setting the size of the Logcat buffer and enabling monitoring of application messages in the workspace in your preferences, my settings are listed below.

Answer 7

On a real device (my question is HTC Desire) I found just disconnecting, and then ADB does not always solve the problem. What works most often is to disable ADB, close the page (possibly back), then take the development page and turn on debug mode again.

Answer 8

Same! For me, the open perspective of DDMS worked on the device panel, which I clicked on reset adb

Answer 9

Click the "View Saved Filters" button. By showing the two-pane view of your LogCat, you can check the active filter in the left pane. I once installed an empty LogCat by selecting "All Messages".

Answer 10

When logcat stops displaying log entries, I find that closing Eclipse and reopening it solves the problem for me.