Excessive WakeUps Feature Alerted by Android Vitals for Google Play Services

Question

I am currently working on an example Android application that uses geofence to monitor location and it is difficult for me to comply with the Android Vitals background wakeup restriction ( https://developer.android.com/topic/performance/vitals/wakeup. HTML ).

I use Battery Historian to monitor awakenings, and although our own alarms have a frequency of less than one per hour, both com.google.android.location.ALARM_WAKEUP_ACTIVITY_DETECTION and com.google.android.location.ALARM_WAKEUP_LOCATOR activate at a much faster rate. I experimented by setting the geofence response delay to 5 minutes, and the WAKEUP_LOCATOR signal was significantly reduced. However, the ALARM_WAKEUP_ACTIVITY_DETECTION alarm is still well beyond 10 / hour.

We use geofences with a radius of 100 m and monitor the exit crossing, as recommended here . I also use a large geofence with a radius of up to 2 km to determine when I need to reload geofences so as not to load too many geofences at a time.

Recent tests were conducted on Android 7.1 on the Galaxy S8, but on other devices the scenario is common. Does anyone have a similar problem? Google recommends using Geofences, especially in light of Oreo’s restrictions on background location requests, so it’s strange that the system monitoring tool takes into account so many awakenings when it offers a way to avoid this.

PS: I read the answer here on Yvette Colomb, and I do not use Location Updates , only Geofence services. Should I give it up?

[Edit] The documentation on Android geofences can be viewed here: https://developer.android.com/training/location/geofencing.html

[ 2] Android, ,

[ 3]: Google. ~ 22/08/2018

,

Answer 1

. .

Answer 2

, com.google.android.location.ALARM_WAKEUP_LOCATOR 60 15 , .

.. , .

 private long UPDATE_INTERVAL = 5 * 6000;
    private long FASTEST_INTERVAL = 6000;
//Set max update intervel for remove excessive wakeups...
        mLocationRequest.setInterval(UPDATE_INTERVAL);
        mLocationRequest.setFastestInterval(FASTEST_INTERVAL);
        mLocationRequest.setMaxWaitTime(30 * 60000);
        mLocationRequest.setPriority(LocationRequest.PRIORITY_BALANCED_POWER_ACCURACY);