android-strictmode

I have started using the Android StrictMode and find that it would be great to have it always running during development and not just on a special branch I created in git. The reason I did this is my apps requirement to run with 1.6 and up. I read on the android developer blog that you can set it up so that you activate it via reflection. I was just wondering how that would actually look like and if it might be possible to have this documented here (or somewhere else) rather than having everybody that wants to use it work out themselves. pixel I've read Manfred's blog post but it doesn't work

i am getting this message in logcat A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks. where to look for leak and what does it meant by " See java.io.Closeable" That means you have opened something but never close them. Closable have a method close which you must call to release the resources associated with the component when you no longer need it. To look for the leak, you can try MAT , I often use it to find memory leaks(static data holding a reference to Activity, etc). For me the problem happened because I

With the release of Gingerbread, I have been experimenting with some of the new API's, one of them being StrictMode . I noticed that one of the warnings is for getSharedPreferences() . This is the warning: StrictMode policy violation; ~duration=1949 ms: android.os.StrictMode$StrictModeDiskReadViolation: policy=23 violation=2 and it's being given for a getSharedPreferences() call being made on the UI thread. Should SharedPreferences access and changes really be made off the UI thread? I'm glad you're already playing with it! Some things to note: (in lazy bullet form) if this is the worst of