Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community!
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.Start your free trial
SZE SZE XU9,759 Points
what is log.v
Generally, use the Log.v() Log.d() Log.i() Log.w() and Log.e() methods.
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.
Tip: A good convention is to declare a TAG constant in your class:
private static final String TAG = "MyActivity"; and use that in subsequent calls to the log methods. Tip: Don't forget that when you make a call like
Log.v(TAG, "index=" + i); that when you're building the string to pass into Log.d, the compiler uses a StringBuilder and at least three allocations occur: the StringBuilder itself, the buffer, and the String object. Realistically, there is also another buffer allocation and copy, and even more pressure on the gc. That means that if your log message is filtered out, you might be doing significant work and incurring significant overhead.
I dont get this, what is log.v and what does verbose mean?
Timothy Boland18,237 Points
VERBOSE means to use more words than needed. in terms of Log.v, it means print to the log EVERYTHING that happens. which you dont want to do in your application because it will create a text file that will get bigger and Bigger and BIGGER and use up to much disk space.