Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 0312a345 authored by Lee Shombert's avatar Lee Shombert
Browse files

Comment the freezer debounce default 

Add a comment on the freezer debounce default pointing out that
lowering the default is risky without good testing.  The CTS test
accepts values down to 5s but that is not mentioned here.

Flag: EXEMPT comment-only
Bug: 409219690
Test: atest
 * CtsAppExitTestCases
Change-Id: I64874f8f7b587be270920dd8172b413d2453b984
parent 10c3d590

services/core/java/com/android/server/am/CachedAppOptimizer.java

+6 −0
Original line number Diff line number Diff line
@@ -287,6 +287,12 @@ public class CachedAppOptimizer { 
    // Format of this string should be a comma separated list of integers.

    @VisibleForTesting static final String DEFAULT_COMPACT_PROC_STATE_THROTTLE =

            String.valueOf(ActivityManager.PROCESS_STATE_RECEIVER);

    // The debounce timeout is a grace period for apps that run background cleanup operations

    // outside their valid lifecycles.  A too-aggressive value (that is, a too-low value) may

    // freeze these apps before the operations complete.  The default has been found to work on

    // phones.  (A lower default has been found to work on Wear).  However, once these apps have

    // been corrected to honor their valid lifecycles, this debounce default may be lowerered or

    // set to zero.

    @VisibleForTesting static final long DEFAULT_FREEZER_DEBOUNCE_TIMEOUT = 10_000L;

    @VisibleForTesting static final boolean DEFAULT_FREEZER_EXEMPT_INST_PKG = false;

    @VisibleForTesting static final boolean DEFAULT_FREEZER_BINDER_ENABLED = true;