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

Commit 10fc5bc9 authored by Jeff Sharkey's avatar Jeff Sharkey
Browse files

Update language to comply with Android's inclusive language guidance 

See https://source.android.com/setup/contribute/respectful-code for reference

Test: none
Bug: 168334533
Exempt-From-Owner-Approval: docs updates
Change-Id: Ic93fe142433b1aa9035a72031b80e875d14c9cc0
parent 9b37625b

services/accessibility/java/com/android/server/accessibility/AccessibilityWindowManager.java

+1 −1
Original line number Diff line number Diff line
@@ -1338,7 +1338,7 @@ public class AccessibilityWindowManager { 
            mTouchInteractionInProgress = false;

            // We want to set the active window to be current immediately

            // after the user has stopped touching the screen since if the

            // user types with the IME he should get a feedback for the

            // user types with the IME they should get a feedback for the

            // letter typed in the text view which is in the input focused

            // window. Note that we always deliver hover accessibility events

            // (they are a result of user touching the screen) so change of

services/accessibility/java/com/android/server/accessibility/gestures/TouchExplorer.java

+1 −1
Original line number Diff line number Diff line
@@ -637,7 +637,7 @@ public class TouchExplorer extends BaseEventStreamTransformation 
                }

                // If the user is touch exploring the second pointer may be

                // performing a double tap to activate an item without need

                // for the user to lift his exploring finger.

                // for the user to lift their exploring finger.

                // It is *important* to use the distance traveled by the pointers

                // on the screen which may or may not be magnified.

                final float deltaX =

services/core/java/com/android/server/EntropyMixer.java

+3 −3
Original line number Diff line number Diff line
@@ -52,9 +52,9 @@ import android.util.Slog; 
 * entropy estimate is not increased. This is to avoid having to trust/verify

 * the quality and authenticity of the "randomness" of the HW RNG.

 *

 * <p>This class was modeled after the script in

 * <a href="http://www.kernel.org/doc/man-pages/online/pages/man4/random.4.html">man

 * 4 random</a>.

 * <p>This class was modeled after the script in the

 * <a href="http://www.kernel.org/doc/man-pages/online/pages/man4/random.4.html">

 * random(4) manual page</a>.

 */

public class EntropyMixer extends Binder {

    private static final String TAG = "EntropyMixer";

services/core/java/com/android/server/display/AutomaticBrightnessController.java

+1 −1
Original line number Diff line number Diff line
@@ -190,7 +190,7 @@ class AutomaticBrightnessController { 


    // When the short term model is invalidated, we don't necessarily reset it (i.e. clear the

    // user's adjustment) immediately, but wait for a drastic enough change in the ambient light.

    // The anchor determines what were the light levels when the user has set her preference, and

    // The anchor determines what were the light levels when the user has set their preference, and

    // we use a relative threshold to determine when to revert to the OEM curve.

    private boolean mShortTermModelValid;

    private float mShortTermModelAnchor;

services/core/java/com/android/server/locksettings/LockSettingsService.java

+2 −2
Original line number Diff line number Diff line
@@ -2590,11 +2590,11 @@ public class LockSettingsService extends ILockSettings.Stub { 
     *     make it consistent with current behaviour. It also allows ActivityManager to call

     *     unlockUser() with empty secret.

     * 3. Once a user is migrated to have synthetic password, its value will never change, no matter

     *     whether the user changes his lockscreen PIN or clear/reset it. When the user clears its

     *     whether the user changes their lockscreen PIN or clear/reset it. When the user clears its

     *     lockscreen PIN, we still maintain the existing synthetic password in a password blob

     *     protected by a default PIN.

     * 4. The user SID is linked with synthetic password, but its cleared/re-created when the user

     *     clears/re-creates his lockscreen PIN.

     *     clears/re-creates their lockscreen PIN.

     *

     *

     * Different cases of calling this method: