diff options
| author | 2018-07-20 16:06:50 -0700 | |
|---|---|---|
| committer | 2018-07-23 11:06:31 -0700 | |
| commit | a9b72b30eb62815d0c2cb7b16c0d191f78c892e5 (patch) | |
| tree | 086380d4175f02d6919b8eea176fdc06c9121021 | |
| parent | 4c436c0f4d6bdea6f4d285b627a4f5618eaffab3 (diff) | |
Update JavaDoc of LocationManager#requestLocationUpdates
Bug: 111522117
Change-Id: If92dd8b2517769ef2964c671fcbd41b58e8727f2
Fixes: 111522117
Test: n/a (javadoc only)
| -rw-r--r-- | location/java/android/location/LocationManager.java | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/location/java/android/location/LocationManager.java b/location/java/android/location/LocationManager.java index ee9e732c88a8..30a07ef94b06 100644 --- a/location/java/android/location/LocationManager.java +++ b/location/java/android/location/LocationManager.java @@ -734,6 +734,11 @@ public class LocationManager { * calling Activity. If a Looper is specified with a {@link LocationListener} * then callbacks are made on the supplied Looper thread. * + * <p> When location callbacks are invoked, the system will hold a wakelock + * on your application's behalf for some period of time, but not + * indefinitely. If your application requires a long running wakelock + * within the location callback, you should acquire it yourself. + * * <p class="note"> Prior to Jellybean, the minTime parameter was * only a hint, and some location provider implementations ignored it. * From Jellybean and onwards it is mandatory for Android compatible |