Merge "docs: Can leave StrictMode enabled in prod" (968ba926) · Commits · e / os / android_frameworks_base

core/java/android/os/StrictMode.java

+13 −17

Original line number	Diff line number	Diff line
		@@ -114,7 +114,6 @@ import java.util.function.Consumer;
		*
		* <pre>
		* public void onCreate() {
		* if (DEVELOPER_MODE) {
		* StrictMode.setThreadPolicy(new {@link ThreadPolicy.Builder StrictMode.ThreadPolicy.Builder}()
		* .detectDiskReads()
		* .detectDiskWrites()
		@@ -127,7 +126,6 @@ import java.util.function.Consumer;
		* .penaltyLog()
		* .penaltyDeath()
		* .build());
		* }
		* super.onCreate();
		* }
		* </pre>
		@@ -146,9 +144,7 @@ import java.util.function.Consumer;
		* <p class="note">StrictMode is not a security mechanism and is not guaranteed to find all disk or
		* network accesses. While it does propagate its state across process boundaries when doing {@link
		* android.os.Binder} calls, it's still ultimately a best effort mechanism. Notably, disk or network
		* access from JNI calls won't necessarily trigger it. Future versions of Android may catch more (or
		* fewer) operations, so you should never leave StrictMode enabled in applications distributed on
		* Google Play.
		* access from JNI calls won't necessarily trigger it.
		*/
		public final class StrictMode {
		private static final String TAG = "StrictMode";