Lines Matching refs:StrictMode
48 * <p>StrictMode is a developer tool which detects things you might be
52 * <p>StrictMode is most commonly used to catch accidental disk or
77 * StrictMode.setThreadPolicy(new {@link ThreadPolicy.Builder StrictMode.ThreadPolicy.Builder}()
83 * StrictMode.setVmPolicy(new {@link VmPolicy.Builder StrictMode.VmPolicy.Builder}()
102 * But don't feel compelled to fix everything that StrictMode finds. In particular,
104 * StrictMode to find things you did by accident. Network requests on the UI thread
107 * <p class="note">StrictMode is not a security mechanism and is not
113 * more (or fewer) operations, so you should never leave StrictMode
116 public final class StrictMode {
117 private static final String TAG = "StrictMode";
129 public static final String DISABLE_PROPERTY = "persist.sys.strictmode.disable";
136 public static final String VISUAL_PROPERTY = "persist.sys.strictmode.visual";
169 * For StrictMode.noteSlowCall()
302 private StrictMode() {}
305 * {@link StrictMode} policy applied to a certain thread.
329 return "[StrictMode.ThreadPolicy; mask=" + mask + "]";
344 * StrictMode.ThreadPolicy policy = new StrictMode.ThreadPolicy.Builder()
348 * StrictMode.setThreadPolicy(policy);
532 * {@link StrictMode} policy applied to all threads in the virtual machine's process.
557 return "[StrictMode.VmPolicy; mask=" + mask + "]";
572 * StrictMode.VmPolicy policy = new StrictMode.VmPolicy.Builder()
576 * StrictMode.setVmPolicy(policy);
959 int threadPolicyMask = StrictMode.DETECT_DISK_WRITE |
960 StrictMode.DETECT_DISK_READ |
961 StrictMode.DETECT_NETWORK;
964 threadPolicyMask |= StrictMode.PENALTY_DROPBOX;
967 threadPolicyMask |= StrictMode.PENALTY_FLASH;
970 StrictMode.setThreadPolicyMask(threadPolicyMask);
1113 // Not part of BlockGuard.Policy; just part of StrictMode:
1310 Log.d(TAG, "StrictMode policy violation; ~duration=" +
1313 Log.d(TAG, "StrictMode policy violation: " + info.crashInfo.stackTrace);
1318 // subset of the original StrictMode policy bitmask, with
1362 Log.e(TAG, "RemoteException trying to handle StrictMode violation", e);
1414 Log.e(TAG, "RemoteException handling StrictMode violation", e);
1467 private static boolean sIsIdlerRegistered = false; // guarded by StrictMode.class
1488 synchronized (StrictMode.class) {
1512 synchronized (StrictMode.class) {
1518 * Enable the recommended StrictMode defaults, with violations just being logged.
1526 StrictMode.setThreadPolicy(new StrictMode.ThreadPolicy.Builder()
1530 StrictMode.setVmPolicy(new StrictMode.VmPolicy.Builder()
1647 // subset of the original StrictMode policy bitmask, with
1663 Log.e(TAG, "RemoteException trying to handle StrictMode violation", e);
1671 System.err.println("StrictMode VmPolicy violation with POLICY_DEATH; shutting down.");
1727 * requires changing the StrictMode policy mask. The role of this
1851 * to any strictmode violation that happens while this span is
1896 * current thread's {@link android.os.StrictMode.ThreadPolicy} has
1897 * {@link android.os.StrictMode.ThreadPolicy.Builder#detectCustomSlowCalls}
1906 // StrictMode not enabled.
1918 // StrictMode not enabled.
1930 // StrictMode not enabled.
1936 // Guarded by StrictMode.class
1957 synchronized (StrictMode.class) {
1977 synchronized (StrictMode.class) {
2006 // being restarted. Granted, it is only a problem when StrictMode is enabled
2225 new StackTraceElement("android.os.StrictMode", "setClassInstanceLimit",
2226 "StrictMode.java", 1)
