There is very awkward thing I am facing logcat is shown in debugging application but while running(not debugging) application it is not showing logcat .
I tried rest
Check you don't have something in the logcat search that returns no matches, for example a non existent package name.
I had renamed my packages, but left an old name in the logcat search field. Result: No logcat output visible
I had the same problem. I tried killing and restarting the adb-server, but it didn't help. I deleted the debug apk of the app in the path:
<your_app>/<your_app>_app/build/outputs/apk/debug/
And run the project again. It solved the problem for me.
In Logcat window reselect your device then reselect your app
if it didn't appear restart adb using two commands:
adb kill-server
adb start-server
Happy debugging :)
I tried to switch "Extended log" in my device settings from "Selectivly" to "Allowed" and it helped. Now debug info appears in LogCat.
I found the following worked for me.
First, my problem: i was testing an app on a Samsung Galaxy A3 attached via usb cable. I was getting the usual logCat messages, including the filtered ones then all of a sudden the logCat stopped displaying filtered messages. Setting it to Verbose displayed a continues stream of messages with a mesage at the top left corner of the lagCat stating "too much output to display".
I tried restarting Android Studio (with and without clearing the cache) but no luck. I then rebooted my phone and everything was back to normal. So it appeared that the attached phone was the problem, sending too much info to the logCat.
Hope this helps someone.
In my case in Android 2.2, for some reason, Firebase was selected by default in the dropdown box marked above. So logs didn't drop. I just needed to change it to No Filters
. Then it worked.
I even tried restarting the logcat, that didn't work too. No Filters
did the magic.
Hope this helps someone.
Edit:
You can as well select Show only selected application
for logcat to show only the current debugging process, i.e your app.