I wasn't worried about checking the log level before logging.... that's a given and well know performance enhancement (although I usually subscribe to the now old agile "make it work, make it right, make it fast" paradigm).
I was wanting to know how to control the log level for different components without having to root the phone and modify the /data/local.prop file. I'm kind of surprised to find that there seem to be no way to do that in the app itself. Looking at the Log class shows that its pretty much all native calls, which is fine, but it really need to check the app itself for logging information so it can be controlled by the developer not just the platform. Though it does explain why some android phones are so much noisier than others in the logging department. It looks like the advice is to wrap Log in a customer logging component so that you *can* control the log levels... and its certainly a workable solution... I just question why its needed at all. I guess this is an RFE that should going into the platform issues list. I do notice that there is a java.util.logging package that looks pretty complete. Does anyone know if its worth investigating or not? - Brill Pappin -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
