I'm not entirely sure about what I'm reading in the documentation. Is it ok to leave a bunch of log.d pieces of code scattered about, or should I comment them out so that they don't impact my app's performance.

Thanks,

I'm a little confused because if you read about the log object (http://developer.android.com/reference/android/util/Log.html) you see this:

"The order in terms of verbosity, from least to most is ERROR, WARN, INFO, DEBUG, VERBOSE. Verbose should never be compiled into an application except during development. Debug logs are compiled in but stripped at runtime. Error, warning and info logs are always kept. "

It almost sounded like it's ok to leave debug messages in there because they are "stripped." Anyway, thanks for the answers, I'll comment them out when I'm done. Not like I need them in there once the app is completed.

Besides impacting your app's performance, they potentially make it harder for other people to debug their stuff. The log is only 64KB, so every time you add a log message some other message gets pushed off the top.
–
faddenSep 22 '10 at 20:35

@anticafe Because if for example you do a concatenation in a Log statement, it will still run (causing unnecessary allocations). Settings debuggable = false only ensures that it won't end up in the log. The methods will still get called.
–
yydlDec 25 '11 at 7:40

Even better, use Proguard to strip out all the logs from the code.
–
Christopher PerryAug 12 '13 at 18:30