Android Phone "dcd On" Error, Constantly Running In Logcat

I am trying to run and test my app, but in my LogCat (besides the usual stacktrace from my app), I get all this weird extra red errors, and have no idea what it is from. It is frus

Solution 1:

I hate it when tools don't do what you need them to do. I struggled for a long time with issues just like you are having. Originally I tried using the command-line and chaining grep's together but it seems you can only chain a few before you loose all your output. I wasted so much time on that.

DCD ON is produced by /system/bin/smdexe. You could try to filter out the PID that smdexe is running on.

If you are on a Mac I think your best bet is to use LogRabbit (I am the creator of the tool so of course I am biased).

View only your messages in LogRabbit by starting the logger and then right click on your applications name. Select "Add Filter...". Save the filter and select from the list. Now you will see only your apps data. You can do a lot more but that is a great starting point.

Here are some tutorials of what you can do: https://www.youtube.com/watch?v=HeildKynnuc&list=PLZVr2R6DumNZUoMZRndqM7cL63gp2NTYE

I hope this helps you.

By the way this is an animated GIF that I think explains what scroll lock is like for logcat in Android Studio and Eclipse: http://imgur.com/q8q0pJC

Solution 2:

To getting things done (see "To get all logs from your application only") you have to filter logcat output by tag or by package name:

tag:MyTag

or

app:com.myapplicationpackage

Edit: If you want to get all logcat errors and first filtering solution doesn't sound suitable to you, You can still get rid of the problem by printing logcat in terminal with excluded "DCD ON" error lines:

adb logcat *:E | grep -v "DCD ON"

or

adb logcat | grep -e "E/" | grep -v "DCD ON"

Update (about "DCD ON"): It seems message E/SMD﹕ DCD ON is a part of inter process communication which is issued by SMD port due to DCD (data carrier detect) online status. For more precise information you can contact Qualcomm Developers Forum.

Solution 3:

On Mac

Quit Android Studio and run it again. That fixed my issue.