blocks|key|1365923|text|最简单的方法可能是在部署之前通过ProGuard运行编译后的JAR，配置如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1365924|-assumenosideeffects+class+android.util.Log+{
++++public+static+int+v(...);
}|code-block|syntax|javascript|1365925|除了所有其他ProGuard优化之外，这将直接从字节码中删除任何冗长的日志语句。|1365926|entityMap|0|LINK|mutability|MUTABLE|url|http://proguard.sourceforge.net/^0|G|8|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

The easiest way is probably to run your compiled JAR through <a href="http://proguard.sourceforge.net/" rel="noreferrer">ProGuard</a> before deployment, with a config like:

<pre><code>-assumenosideeffects class android.util.Log {
 public static int v(...);
}
</code></pre>

That will &mdash; aside from all the other ProGuard optimisations &mdash; remove any verbose log statements directly from the bytecode.

blocks|key|1150850|text|一种常见的方法是创建一个名为loglevel的int，并根据loglevel定义它的调试级别。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1150851|public+static+int+LOGLEVEL+=+2;
public+static+boolean+ERROR+=+LOGLEVEL+>+0;
public+static+boolean+WARN+=+LOGLEVEL+>+1;
...
public+static+boolean+VERBOSE+=+LOGLEVEL+>+4;

++++if+(VERBOSE)+Log.v(TAG,+"Message+here");+//+Won't+be+shown
++++if+(WARN)+Log.w(TAG,+"WARNING+HERE");++++//+Still+goes+through|code-block|syntax|javascript|1150852|稍后，您可以只更改所有调试输出级别的LOGLEVEL。|1150853|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

A common way is to make an int named loglevel, and define its debug level based on loglevel.

<pre><code>public static int LOGLEVEL = 2;
public static boolean ERROR = LOGLEVEL &gt; 0;
public static boolean WARN = LOGLEVEL &gt; 1;
...
public static boolean VERBOSE = LOGLEVEL &gt; 4;

 if (VERBOSE) Log.v(TAG, "Message here"); // Won't be shown
 if (WARN) Log.w(TAG, "WARNING HERE"); // Still goes through
</code></pre>

Later, you can just change the LOGLEVEL for all debug output level.

blocks|key|1150865|text|你应该使用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1150866|++++if+(Log.isLoggable(TAG,+Log.VERBOSE))+{
++++++++Log.v(TAG,+"my+log+message");
++++}|code-block|syntax|javascript|1150867|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You should use

<pre><code> if (Log.isLoggable(TAG, Log.VERBOSE)) {
 Log.v(TAG, "my log message");
 }
</code></pre>

blocks|key|1366011|text|我采用了一种简单的方法--创建一个包装类，它也使用了可变参数列表。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1366012|+public+class+Log{
++++++++public+static+int+LEVEL+=+android.util.Log.WARN;


++++static+public+void+d(String+tag,+String+msgFormat,+Object...args)
++++{
++++++++if+(LEVEL<=android.util.Log.DEBUG)
++++++++{
++++++++++++android.util.Log.d(tag,+String.format(msgFormat,+args));
++++++++}
++++}

++++static+public+void+d(String+tag,+Throwable+t,+String+msgFormat,+Object...args)
++++{
++++++++if+(LEVEL<=android.util.Log.DEBUG)
++++++++{
++++++++++++android.util.Log.d(tag,+String.format(msgFormat,+args),+t);
++++++++}
++++}

++++//...other+level+logging+functions+snipped|code-block|syntax|javascript|1366013|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I took a simple route - creating a wrapper class that also makes use of variable parameter lists.

<pre><code> public class Log{
 public static int LEVEL = android.util.Log.WARN;


 static public void d(String tag, String msgFormat, Object...args)
 {
 if (LEVEL&lt;=android.util.Log.DEBUG)
 {
 android.util.Log.d(tag, String.format(msgFormat, args));
 }
 }

 static public void d(String tag, Throwable t, String msgFormat, Object...args)
 {
 if (LEVEL&lt;=android.util.Log.DEBUG)
 {
 android.util.Log.d(tag, String.format(msgFormat, args), t);
 }
 }

 //...other level logging functions snipped
</code></pre>

blocks|key|1366117|text|使用proguard剥离日志记录(参见@Christopher的答案)是简单而快速的，但如果文件中有任何调试日志记录，它会导致生产环境中的堆栈跟踪与源文件不匹配。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1366118|相反，这里有一种技术，它在开发和生产中使用不同的日志记录级别，假设proguard只在生产中使用。它通过查看proguard是否重命名了给定的类名来识别结果(在本例中，我使用了“com.foo.Bar”--您可以将其替换为proguard将重命名的全限定类名)。|1366119|该技术利用了commons日志记录。|1366120|private+void+initLogging()+{
++++Level+level+=+Level.WARNING;
++++try+{
++++++++//+in+production,+the+shrinker/obfuscator+proguard+will+change+the
++++++++//+name+of+this+class+(and+many+others)+so+in+development,+this
++++++++//+class+WILL+exist+as+named,+and+we+will+have+debug+level
++++++++Class.forName("com.foo.Bar");
++++++++level+=+Level.FINE;
++++}+catch+(Throwable+t)+{
++++++++//+no+problem,+we+are+in+production+mode
++++}
++++Handler[]+handlers+=+Logger.getLogger("").getHandlers();
++++for+(Handler+handler+:+handlers)+{
++++++++Log.d("log+init",+"handler:+"+%2B+handler.getClass().getName());
++++++++handler.setLevel(level);
++++}
}|code-block|syntax|javascript|1366121|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|P|8|@]|9|@]|A|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Stripping out the logging with proguard (see answer from @Christopher ) was easy and fast, but it caused stack traces from production to mismatch the source if there was any debug logging in the file.

Instead, here's a technique that uses different logging levels in development vs. production, assuming that proguard is used only in production. It recognizes production by seeing if proguard has renamed a given class name (in the example, I use "com.foo.Bar"--you would replace this with a fully-qualified class name that you know will be renamed by proguard).

This technique makes use of commons logging.

<pre><code>private void initLogging() {
 Level level = Level.WARNING;
 try {
 // in production, the shrinker/obfuscator proguard will change the
 // name of this class (and many others) so in development, this
 // class WILL exist as named, and we will have debug level
 Class.forName("com.foo.Bar");
 level = Level.FINE;
 } catch (Throwable t) {
 // no problem, we are in production mode
 }
 Handler[] handlers = Logger.getLogger("").getHandlers();
 for (Handler handler : handlers) {
 Log.d("log init", "handler: " + handler.getClass().getName());
 handler.setLevel(level);
 }
}
</code></pre>

blocks|key|1366170|text|在Android中，Log4j或slf4j也可以和logcat一起用作日志框架。请参阅项目android-logging-log4j或log4j+support+in+android|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1366171|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/android-logging-log4j/|1|https://stackoverflow.com/a/8200138/1113228^0|19|L|0|1V|O|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

Log4j or slf4j can also be used as logging frameworks in Android together with logcat. See the project <a href="http://code.google.com/p/android-logging-log4j/" rel="nofollow noreferrer">android-logging-log4j</a> or <a href="https://stackoverflow.com/a/8200138/1113228">log4j support in android</a>

blocks|key|1151182|text|在一个非常简单的日志记录场景中，您实际上只是为了调试目的而在开发期间尝试写入控制台，最简单的方法可能是在您的生产构建之前进行搜索和替换，并注释掉对日志或System.out.println的所有调用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1151183|例如，假设您没有使用“Log”。除了调用Log.d或Log.e之外的任何地方，您可以简单地在整个解决方案中执行查找和替换，以替换“Log”。带有"//Log.“注释掉所有的日志调用，或者在我的例子中，我只是到处使用System.out.println，所以在投入生产之前，我将简单地做一个完整的搜索并替换"System.out.println“，并替换为"//System.out.println”。|1151184|我知道这并不理想，如果Eclipse中内置了查找和注释掉对日志和System.out.println的调用的功能，那就太好了，但在此之前，最简单、最快、最好的方法是通过搜索和替换将其注释掉。如果这样做，就不必担心堆栈跟踪行号不匹配，因为您正在编辑源代码，并且不会通过检查一些日志级别的配置等来增加任何开销。|1151185|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

In a very simple logging scenario, where you're literally just trying to write to console during development for debugging purposes, it might be easiest to just do a search and replace before your production build and comment out all the calls to Log or System.out.println.

For example, assuming you didn't use the "Log." anywhere outside of a call to Log.d or Log.e, etc, you could simply do a find and replace across the entire solution to replace "Log." with "//Log." to comment out all your logging calls, or in my case I'm just using System.out.println everywhere, so before going to production I'll simply do a full search and replace for "System.out.println" and replace with "//System.out.println".

I know this isn't ideal, and it would be nice if the ability to find and comment out calls to Log and System.out.println were built into Eclipse, but until that happens the easiest and fastest and best way to do this is to comment out by search and replace. If you do this, you don't have to worry about mismatching stack trace line numbers, because you're editing your source code, and you're not adding any overhead by checking some log level configuration, etc.

blocks|key|1151233|text|也许你可以看到这个日志扩展类：https://github.com/dbauduin/Android-Tools/tree/master/logs。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1151234|它使您能够对日志进行精细控制。例如，您可以禁用所有日志，或者只禁用某些包或类的日志。|1151235|此外，它还添加了一些有用的功能(例如，您不必为每个日志传递一个标记)。|1151236|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/dbauduin/Android-Tools/tree/master/logs^0|F|1M|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

May be you can see this Log extension class: <a href="https://github.com/dbauduin/Android-Tools/tree/master/logs" rel="nofollow">https://github.com/dbauduin/Android-Tools/tree/master/logs</a>.

It enables you to have a fine control on logs.
You can for example disable all logs or just the logs of some packages or classes.

Moreover, it adds some useful functionalities (for instance you don't have to pass a tag for each log).

blocks|key|1366433|text|这里有一个更复杂的解决方案。您将获得完整的堆栈跟踪，并且只有在需要时(性能)才会调用toString()方法。在生产模式下，属性BuildConfig.DEBUG将为false，因此所有跟踪和调试日志都将被删除。热点编译器有机会删除调用，因为提供了最终的静态属性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1366434|import+java.io.ByteArrayOutputStream;
import+java.io.PrintStream;
import+android.util.Log;

public+class+Logger+{

++++public+enum+Level+{
++++++++error,+warn,+info,+debug,+trace
++++}

++++private+static+final+String+DEFAULT_TAG+=+"Project";

++++private+static+final+Level+CURRENT_LEVEL+=+BuildConfig.DEBUG+?+Level.trace+:+Level.info;

++++private+static+boolean+isEnabled(Level+l)+{
++++++++return+CURRENT_LEVEL.compareTo(l)+>=+0;
++++}

++++static+{
++++++++Log.i(DEFAULT_TAG,+"log+level:+"+%2B+CURRENT_LEVEL.name());
++++}

++++private+String+classname+=+DEFAULT_TAG;

++++public+void+setClassName(Class<?>+c)+{
++++++++classname+=+c.getSimpleName();
++++}

++++public+String+getClassname()+{
++++++++return+classname;
++++}

++++public+boolean+isError()+{
++++++++return+isEnabled(Level.error);
++++}

++++public+boolean+isWarn()+{
++++++++return+isEnabled(Level.warn);
++++}

++++public+boolean+isInfo()+{
++++++++return+isEnabled(Level.info);
++++}

++++public+boolean+isDebug()+{
++++++++return+isEnabled(Level.debug);
++++}

++++public+boolean+isTrace()+{
++++++++return+isEnabled(Level.trace);
++++}

++++public+void+error(Object...+args)+{
++++++++if+(isError())+Log.e(buildTag(),+build(args));
++++}

++++public+void+warn(Object...+args)+{
++++++++if+(isWarn())+Log.w(buildTag(),+build(args));
++++}

++++public+void+info(Object...+args)+{
++++++++if+(isInfo())+Log.i(buildTag(),+build(args));
++++}

++++public+void+debug(Object...+args)+{
++++++++if+(isDebug())+Log.d(buildTag(),+build(args));
++++}

++++public+void+trace(Object...+args)+{
++++++++if+(isTrace())+Log.v(buildTag(),+build(args));
++++}

++++public+void+error(String+msg,+Throwable+t)+{
++++++++if+(isError())+error(buildTag(),+msg,+stackToString(t));
++++}

++++public+void+warn(String+msg,+Throwable+t)+{
++++++++if+(isWarn())+warn(buildTag(),+msg,+stackToString(t));
++++}

++++public+void+info(String+msg,+Throwable+t)+{
++++++++if+(isInfo())+info(buildTag(),+msg,+stackToString(t));
++++}

++++public+void+debug(String+msg,+Throwable+t)+{
++++++++if+(isDebug())+debug(buildTag(),+msg,+stackToString(t));
++++}

++++public+void+trace(String+msg,+Throwable+t)+{
++++++++if+(isTrace())+trace(buildTag(),+msg,+stackToString(t));
++++}

++++private+String+buildTag()+{
++++++++String+tag+;
++++++++if+(BuildConfig.DEBUG)+{
++++++++++++StringBuilder+b+=+new+StringBuilder(20);
++++++++++++b.append(getClassname());

++++++++++++StackTraceElement+stackEntry+=+Thread.currentThread().getStackTrace()[4];
++++++++++++if+(stackEntry+!=+null)+{
++++++++++++++++b.append('.');
++++++++++++++++b.append(stackEntry.getMethodName());
++++++++++++++++b.append(':');
++++++++++++++++b.append(stackEntry.getLineNumber());
++++++++++++}
++++++++++++tag+=+b.toString();
++++++++}+else+{
++++++++++++tag+=+DEFAULT_TAG;
++++++++}
++++}

++++private+String+build(Object...+args)+{
++++++++if+(args+==+null)+{
++++++++++++return+"null";
++++++++}+else+{
++++++++++++StringBuilder+b+=+new+StringBuilder(args.length+*+10);
++++++++++++for+(Object+arg+:+args)+{
++++++++++++++++if+(arg+==+null)+{
++++++++++++++++++++b.append("null");
++++++++++++++++}+else+{
++++++++++++++++++++b.append(arg);
++++++++++++++++}
++++++++++++}
++++++++++++return+b.toString();
++++++++}
++++}

++++private+String+stackToString(Throwable+t)+{
++++++++ByteArrayOutputStream+baos+=+new+ByteArrayOutputStream(500);
++++++++baos.toString();
++++++++t.printStackTrace(new+PrintStream(baos));
++++++++return+baos.toString();
++++}
}|code-block|syntax|javascript|1366435|像这样使用：|1366436|Loggor+log+=+new+Logger();
Map+foo+=+...
List+bar+=+...
log.error("Foo:",+foo,+"bar:",+bar);
//+bad+example+(avoid+something+like+this)
//+log.error("Foo:"+%2B+"+foo.toString()+%2B+"bar:"+%2B+bar);+|1366437|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Here is a more complex solution. You will get full stack trace and the method toString() will be called only if needed(Performance). The attribute BuildConfig.DEBUG will be false in the production mode so all trace and debug logs will be removed. The hot spot compiler has the chance to remove the calls because off final static properties. 

<pre><code>import java.io.ByteArrayOutputStream;
import java.io.PrintStream;
import android.util.Log;

public class Logger {

 public enum Level {
 error, warn, info, debug, trace
 }

 private static final String DEFAULT_TAG = "Project";

 private static final Level CURRENT_LEVEL = BuildConfig.DEBUG ? Level.trace : Level.info;

 private static boolean isEnabled(Level l) {
 return CURRENT_LEVEL.compareTo(l) &gt;= 0;
 }

 static {
 Log.i(DEFAULT_TAG, "log level: " + CURRENT_LEVEL.name());
 }

 private String classname = DEFAULT_TAG;

 public void setClassName(Class&lt;?&gt; c) {
 classname = c.getSimpleName();
 }

 public String getClassname() {
 return classname;
 }

 public boolean isError() {
 return isEnabled(Level.error);
 }

 public boolean isWarn() {
 return isEnabled(Level.warn);
 }

 public boolean isInfo() {
 return isEnabled(Level.info);
 }

 public boolean isDebug() {
 return isEnabled(Level.debug);
 }

 public boolean isTrace() {
 return isEnabled(Level.trace);
 }

 public void error(Object... args) {
 if (isError()) Log.e(buildTag(), build(args));
 }

 public void warn(Object... args) {
 if (isWarn()) Log.w(buildTag(), build(args));
 }

 public void info(Object... args) {
 if (isInfo()) Log.i(buildTag(), build(args));
 }

 public void debug(Object... args) {
 if (isDebug()) Log.d(buildTag(), build(args));
 }

 public void trace(Object... args) {
 if (isTrace()) Log.v(buildTag(), build(args));
 }

 public void error(String msg, Throwable t) {
 if (isError()) error(buildTag(), msg, stackToString(t));
 }

 public void warn(String msg, Throwable t) {
 if (isWarn()) warn(buildTag(), msg, stackToString(t));
 }

 public void info(String msg, Throwable t) {
 if (isInfo()) info(buildTag(), msg, stackToString(t));
 }

 public void debug(String msg, Throwable t) {
 if (isDebug()) debug(buildTag(), msg, stackToString(t));
 }

 public void trace(String msg, Throwable t) {
 if (isTrace()) trace(buildTag(), msg, stackToString(t));
 }

 private String buildTag() {
 String tag ;
 if (BuildConfig.DEBUG) {
 StringBuilder b = new StringBuilder(20);
 b.append(getClassname());

 StackTraceElement stackEntry = Thread.currentThread().getStackTrace()[4];
 if (stackEntry != null) {
 b.append('.');
 b.append(stackEntry.getMethodName());
 b.append(':');
 b.append(stackEntry.getLineNumber());
 }
 tag = b.toString();
 } else {
 tag = DEFAULT_TAG;
 }
 }

 private String build(Object... args) {
 if (args == null) {
 return "null";
 } else {
 StringBuilder b = new StringBuilder(args.length * 10);
 for (Object arg : args) {
 if (arg == null) {
 b.append("null");
 } else {
 b.append(arg);
 }
 }
 return b.toString();
 }
 }

 private String stackToString(Throwable t) {
 ByteArrayOutputStream baos = new ByteArrayOutputStream(500);
 baos.toString();
 t.printStackTrace(new PrintStream(baos));
 return baos.toString();
 }
}
</code></pre>

use like this:

<pre><code>Loggor log = new Logger();
Map foo = ...
List bar = ...
log.error("Foo:", foo, "bar:", bar);
// bad example (avoid something like this)
// log.error("Foo:" + " foo.toString() + "bar:" + bar); 
</code></pre>

blocks|key|1151411|text|在我的应用程序中，我有一个类，它包装了Log类，这个类有一个静态的布尔变量"state“。在我的整个代码中，我使用静态方法检查"state“变量的值，然后再实际写入Log。然后我有一个静态方法来设置"state“变量，以确保该值在应用程序创建的所有实例中都是通用的。这意味着我可以在一次调用中启用或禁用应用程序的所有日志记录-即使应用程序正在运行。对支持电话很有用...这意味着你在调试时必须坚持下去，而不是退回到使用标准的Log类……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1151412|如果布尔变量没有赋值，Java将其解释为false也很有用(方便)，这意味着可以将其保留为false，直到您需要打开日志记录:-)|1151413|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

In my apps I have a class which wraps the Log class which has a static boolean var called "state". Throughout my code I check the value of the "state" variable using a static method before actually writing to the Log. I then have a static method to set the "state" variable which ensures the value is common across all instances created by the app. This means I can enable or disable all logging for the App in one call - even when the App is running. Useful for support calls... It does mean that you have to stick to your guns when debugging and not regress to using the standard Log class though...

It's also useful (convenient) that Java interprets a boolean var as false if it hasn't been assigned a value, which means it can be left as false until you need to turn on logging :-)

blocks|key|1151456|text|对我来说，能够为每个标签设置不同的日志级别通常是有用的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1151457|我使用了这个非常简单的包装类：|1151458|public+class+Log2+{

++++public+enum+LogLevels+{
++++++++VERBOSE(android.util.Log.VERBOSE),+DEBUG(android.util.Log.DEBUG),+INFO(android.util.Log.INFO),+WARN(
++++++++++++++++android.util.Log.WARN),+ERROR(android.util.Log.ERROR);

++++++++int+level;

++++++++private+LogLevels(int+logLevel)+{
++++++++++++level+=+logLevel;
++++++++}

++++++++public+int+getLevel()+{
++++++++++++return+level;
++++++++}
++++};

++++static+private+HashMap<String,+Integer>+logLevels+=+new+HashMap<String,+Integer>();

++++public+static+void+setLogLevel(String+tag,+LogLevels+level)+{
++++++++logLevels.put(tag,+level.getLevel());
++++}

++++public+static+int+v(String+tag,+String+msg)+{
++++++++return+Log2.v(tag,+msg,+null);
++++}

++++public+static+int+v(String+tag,+String+msg,+Throwable+tr)+{
++++++++if+(logLevels.containsKey(tag))+{
++++++++++++if+(logLevels.get(tag)+>+android.util.Log.VERBOSE)+{
++++++++++++++++return+-1;
++++++++++++}
++++++++}
++++++++return+Log.v(tag,+msg,+tr);
++++}

++++public+static+int+d(String+tag,+String+msg)+{
++++++++return+Log2.d(tag,+msg,+null);
++++}

++++public+static+int+d(String+tag,+String+msg,+Throwable+tr)+{
++++++++if+(logLevels.containsKey(tag))+{
++++++++++++if+(logLevels.get(tag)+>+android.util.Log.DEBUG)+{
++++++++++++++++return+-1;
++++++++++++}
++++++++}
++++++++return+Log.d(tag,+msg);
++++}

++++public+static+int+i(String+tag,+String+msg)+{
++++++++return+Log2.i(tag,+msg,+null);
++++}

++++public+static+int+i(String+tag,+String+msg,+Throwable+tr)+{
++++++++if+(logLevels.containsKey(tag))+{
++++++++++++if+(logLevels.get(tag)+>+android.util.Log.INFO)+{
++++++++++++++++return+-1;
++++++++++++}
++++++++}
++++++++return+Log.i(tag,+msg);
++++}

++++public+static+int+w(String+tag,+String+msg)+{
++++++++return+Log2.w(tag,+msg,+null);
++++}

++++public+static+int+w(String+tag,+String+msg,+Throwable+tr)+{
++++++++if+(logLevels.containsKey(tag))+{
++++++++++++if+(logLevels.get(tag)+>+android.util.Log.WARN)+{
++++++++++++++++return+-1;
++++++++++++}
++++++++}
++++++++return+Log.w(tag,+msg,+tr);
++++}

++++public+static+int+e(String+tag,+String+msg)+{
++++++++return+Log2.e(tag,+msg,+null);
++++}

++++public+static+int+e(String+tag,+String+msg,+Throwable+tr)+{
++++++++if+(logLevels.containsKey(tag))+{
++++++++++++if+(logLevels.get(tag)+>+android.util.Log.ERROR)+{
++++++++++++++++return+-1;
++++++++++++}
++++++++}
++++++++return+Log.e(tag,+msg,+tr);
++++}

}|code-block|syntax|javascript|1151459|现在只需在每个类的开头设置每个标记的日志级别：|1151460|Log2.setLogLevel(TAG,+LogLevels.INFO);|1151461|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

For me it is often useful being able to set different log levels for each TAG.

I am using this very simple wrapper class:

<pre><code>public class Log2 {

 public enum LogLevels {
 VERBOSE(android.util.Log.VERBOSE), DEBUG(android.util.Log.DEBUG), INFO(android.util.Log.INFO), WARN(
 android.util.Log.WARN), ERROR(android.util.Log.ERROR);

 int level;

 private LogLevels(int logLevel) {
 level = logLevel;
 }

 public int getLevel() {
 return level;
 }
 };

 static private HashMap&lt;String, Integer&gt; logLevels = new HashMap&lt;String, Integer&gt;();

 public static void setLogLevel(String tag, LogLevels level) {
 logLevels.put(tag, level.getLevel());
 }

 public static int v(String tag, String msg) {
 return Log2.v(tag, msg, null);
 }

 public static int v(String tag, String msg, Throwable tr) {
 if (logLevels.containsKey(tag)) {
 if (logLevels.get(tag) &gt; android.util.Log.VERBOSE) {
 return -1;
 }
 }
 return Log.v(tag, msg, tr);
 }

 public static int d(String tag, String msg) {
 return Log2.d(tag, msg, null);
 }

 public static int d(String tag, String msg, Throwable tr) {
 if (logLevels.containsKey(tag)) {
 if (logLevels.get(tag) &gt; android.util.Log.DEBUG) {
 return -1;
 }
 }
 return Log.d(tag, msg);
 }

 public static int i(String tag, String msg) {
 return Log2.i(tag, msg, null);
 }

 public static int i(String tag, String msg, Throwable tr) {
 if (logLevels.containsKey(tag)) {
 if (logLevels.get(tag) &gt; android.util.Log.INFO) {
 return -1;
 }
 }
 return Log.i(tag, msg);
 }

 public static int w(String tag, String msg) {
 return Log2.w(tag, msg, null);
 }

 public static int w(String tag, String msg, Throwable tr) {
 if (logLevels.containsKey(tag)) {
 if (logLevels.get(tag) &gt; android.util.Log.WARN) {
 return -1;
 }
 }
 return Log.w(tag, msg, tr);
 }

 public static int e(String tag, String msg) {
 return Log2.e(tag, msg, null);
 }

 public static int e(String tag, String msg, Throwable tr) {
 if (logLevels.containsKey(tag)) {
 if (logLevels.get(tag) &gt; android.util.Log.ERROR) {
 return -1;
 }
 }
 return Log.e(tag, msg, tr);
 }

}
</code></pre>

Now just set the log level per TAG at the beginning of each class:

<pre><code>Log2.setLogLevel(TAG, LogLevels.INFO);
</code></pre>

blocks|key|1366608|text|标准的android+Log类有一个很小的临时替代品--+https://github.com/zserge/log|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1366609|基本上，您所要做的就是替换从android.util.Log到trikita.log.Log的导入。然后，在您的Application.onCreate()或一些静态初始化器中，检查BuilConfig.DEBUG或任何其他标志，并使用Log.level(Log.D)或Log.level(Log.E)更改最低日志级别。您可以使用Log.useLog(false)完全禁用日志记录。|style|CODE|1366610|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/zserge/log^0|T|T|0|0|E|G|V|F|1K|M|2J|G|3A|G|3R|G|4L|H|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@$A|U|B|V|F|G]|$A|W|B|X|F|G]|$A|Y|B|Z|F|G]|$A|10|B|11|F|G]|$A|12|B|13|F|G]|$A|14|B|15|F|G]|$A|16|B|17|F|G]]|9|@]|C|$]]|$1|H|3|-4|5|6|7|18|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

There is a tiny drop-in replacement for the standard android Log class - <a href="https://github.com/zserge/log" rel="nofollow">https://github.com/zserge/log</a>

Basically all you have to do is to replace imports from <code>android.util.Log</code> to <code>trikita.log.Log</code>. Then in your <code>Application.onCreate()</code> or in some static initalizer check for the <code>BuilConfig.DEBUG</code> or any other flag and use <code>Log.level(Log.D)</code> or <code>Log.level(Log.E)</code> to change the minimal log level. You can use <code>Log.useLog(false)</code> to disable logging at all.

blocks|key|1151544|text|我们可以在本地组件中使用Log类，并将方法定义为v/i/e/d。根据需要，我们可以进一步调用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1151545|示例如下所示。|1151546|++++public+class+Log{
++++++++private+static+boolean+TAG+=+false;
++++++++public+static+void+d(String+enable_tag,+String+message,Object...args){
++++++++++++if(TAG)
++++++++++++android.util.Log.d(enable_tag,+message%2Bargs);
++++++++}
++++++++public+static+void+e(String+enable_tag,+String+message,Object...args){
++++++++++++if(TAG)
++++++++++++android.util.Log.e(enable_tag,+message%2Bargs);
++++++++}
++++++++public+static+void+v(String+enable_tag,+String+message,Object...args){
++++++++++++if(TAG)
++++++++++++android.util.Log.v(enable_tag,+message%2Bargs);
++++++++}
++++}
++++if+we+do+not+need+any+print(s),+at-all+make+TAG+as+false+for+all+else+
++++remove+the+check+for+type+of+Log+(say+Log.d).
++++as+
++++public+static+void+i(String+enable_tag,+String+message,Object...args){
++++//++++++if(TAG)
++++++++++++android.util.Log.i(enable_tag,+message%2Bargs);
++++}|code-block|syntax|javascript|1151547|这里的消息是针对string的，而args是您想要打印的值。|1151548|entityMap^0|C|3|0|0|0|8|6|H|4|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|V|8|@$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|P|$]]

We can use class <code>Log</code> in our local component and define the methods as v/i/e/d.
Based on the need of we can make call further. 
example is shown below.

<pre><code> public class Log{
 private static boolean TAG = false;
 public static void d(String enable_tag, String message,Object...args){
 if(TAG)
 android.util.Log.d(enable_tag, message+args);
 }
 public static void e(String enable_tag, String message,Object...args){
 if(TAG)
 android.util.Log.e(enable_tag, message+args);
 }
 public static void v(String enable_tag, String message,Object...args){
 if(TAG)
 android.util.Log.v(enable_tag, message+args);
 }
 }
 if we do not need any print(s), at-all make TAG as false for all else 
 remove the check for type of Log (say Log.d).
 as 
 public static void i(String enable_tag, String message,Object...args){
 // if(TAG)
 android.util.Log.i(enable_tag, message+args);
 }
</code></pre>

here message is for <code>string</code> and and <code>args</code> is the value you want to print.

I am having lots of logging statements to debug for example.

<pre><code>Log.v(TAG, "Message here");
Log.w(TAG, " WARNING HERE");
</code></pre>

while deploying this application on device phone i want to turn off the verbose logging from where i can enable/disable logging.

How do I enable/disable log levels in Android?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

例如，我有很多日志语句要调试。Log.v(TAG, "Message here");Log.w(TAG, " WARNING HERE");在设备电话上部署此应用程序时，我想关闭详细日志记录，从中我可以启用/禁用日志记录。

问如何在Android中开启/关闭日志级别？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Android中开启/关闭日志级别？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Android中开启/关闭日志级别？
EN