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

Commit 6b3be41e authored by Soonil Nagarkar's avatar Soonil Nagarkar
Browse files

Fix foreground importance bug in LocationManagerService. 

Bug: 37121975
Test: tested locally
Change-Id: I2563408d10edfac74d04d68116cbf2a2ac66e9a3
(cherry picked from commit ebda0286)
parent f4077aa3

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

+5 −2
Original line number Diff line number Diff line
@@ -146,6 +146,9 @@ public class LocationManagerService extends ILocationManager.Stub { 
    // The maximum interval a location request can have and still be considered "high power".

    private static final long HIGH_POWER_INTERVAL_MS = 5 * 60 * 1000;



    private static final int FOREGROUND_IMPORTANCE_CUTOFF

        = ActivityManager.RunningAppProcessInfo.IMPORTANCE_FOREGROUND_SERVICE;



    // default background throttling interval if not overriden in settings

    private static final long DEFAULT_BACKGROUND_THROTTLE_INTERVAL_MS = 30 * 60 * 1000;
@@ -375,7 +378,7 @@ public class LocationManagerService extends ILocationManager.Stub { 
                }

            };

            mActivityManager.addOnUidImportanceListener(uidImportanceListener,

                    ActivityManager.RunningAppProcessInfo.IMPORTANCE_PERCEPTIBLE);

                    FOREGROUND_IMPORTANCE_CUTOFF);



            mUserManager = (UserManager) mContext.getSystemService(Context.USER_SERVICE);

            updateUserProfiles(mCurrentUserId);
@@ -452,7 +455,7 @@ public class LocationManagerService extends ILocationManager.Stub { 
    }



    private static boolean isImportanceForeground(int importance) {

        return importance <= ActivityManager.RunningAppProcessInfo.IMPORTANCE_FOREGROUND_SERVICE;

        return importance <= FOREGROUND_IMPORTANCE_CUTOFF;

    }



    /**