Menu
If my Eclipse works for over 3 or 4 hours, and I want to debug my Android app after that time, Logcat literlly dies. Only when I restart my Eclipse LogCat reborns.
I have searched but it doesn't seem that I found any solutions to these.
Any ideas?
Thanks in advance.
452
You need to press Alt + 6 twice to restart the Logcat. Restarting logcat often helps when it becomes irresponsive.
Logcat is a command-line tool that dumps a log of system messages, including stack traces when the device throws an error and messages that you have written from your app with the Log class. This page is about the command-line logcat tool, but you can also view log messages from the Logcat window in Android Studio.
Prevent clearing the log when the app crashes By default when the app got crashed the logcat clear's in the android studio. To prevent this, click the right end chooser(Filter Configuration chooser) in the logcat tab then select Edit Filter Configuration option and enter current app name and package name.
Yes, it's a known problem which time to time could appears in Eclipse. My investigation lead me to suggestion that a problem could be in synchronization of ADB with IDE Eclipse. Mostly was helpful a restart of ADB.
1) go to command line (console mode)
2) change dir to ...sdk\platform-tools
3) type "adb kill-server" in command prompt and execute
4) type "adb start-server" in command prompt and execute
Then check the LogCat, most likely you will see that logs running again
The last way to resolve it - just restart an Eclipse, but this way is not comfortable
125
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
