All geek questions in one place

Logcat data does not appear on Eclipse DDMS Log Tab

  • the log tab is visible in DDMS, and I am logging data using Log.v (...) after a week without any problems.
  • Today, log data is more displayed in the log window. While working, then programming was changed to track the error, and now the log data is no longer displayed.
  • We tried to run the application on an external Android phone, on an Android simulator, and it does not matter.
  • Closed Eclipse, rebooted and still not changed.
  • The console displays activity, but only until the moment the action begins.
  • An external phone is set up for debugging - not that it could be a problem, since I have the same problem with a simulator

It looks like I did something wrong wrong, but I can’t change anything: - (

Has anyone encountered this problem before - looked at previous posts, but none of them seem relevant.

Hello,

Oliver

+4
source share
6 answers

I had the same problem. I used an emulator and a debugging device. Obviously, you need to select the device specified in the DDMS view whose logs you want to see. My logs were empty because the device that I expected from the logs was not selected.

Hope that helps

+11
source

Tried this: fooobar.com/questions/51929 / ...

Go into the logcat window - RETURN RIGHT PAUSE || (Pause receiving new logcat messages)

A few clicks + eventually restarting eclipse (usually works in my case)

+1
source

Check the LogCat window to see if you are filtering and setting the debug level in Verbose.

0
source

Possible reasons and solutions:

  • LogCat may have to cache a lot, clear the log and see if the problem is fixed.
  • You may need to select a device in the device view (even if it is already selected, try clicking on it).
  • adb does not work correctly, try to kill and run it again

Check if output is displayed if you use adb logcat command line

0
source

Just go into DDMS mode and click on the device name in the upper left corner and make your log cat. Start with BOOm: P

0
source

In Android Studio , which turned out to be more reliable and intuitive than Eclipse, I found this to be a common problem. For me, what solves it (the device is automatically installed when your application starts), in addition to checking the code, it is Shut down and restart the emulator or Shut down Android Studio and the emulator and reopen / restart

0
source

Source: https://habr.com/ru/post/1347566/

More articles:


All Articles