summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorHemal Patel <hemalp@google.com>2016-10-18 23:23:38 +0000
committerandroid-build-merger <android-build-merger@google.com>2016-10-18 23:23:38 +0000
commitacaeb097153b6c7792c0348b8ba8e25d0b31021c (patch)
tree0064dba5919ad1c25c06b2bb3d8c7c0f8d644b88 /docs
parentc31b8c95ad2ac7cc3cc41cb1eb798d09d780ae59 (diff)
parentc9f68a8be3bb4ac2d35907dad8483b6515844c0a (diff)
Docs: Fixed a broken link am: 9a641b6989 am: 40aaf53920 am: 8068fdca0c
am: c9f68a8be3 Change-Id: I9636eef5a4cfeb8ab875aa15cbfaba20a1c80dcb
Diffstat (limited to 'docs')
-rw-r--r--docs/html/training/location/geofencing.jd43
1 files changed, 30 insertions, 13 deletions
diff --git a/docs/html/training/location/geofencing.jd b/docs/html/training/location/geofencing.jd
index ce6ad55ad889..046e99e9bed1 100644
--- a/docs/html/training/location/geofencing.jd
+++ b/docs/html/training/location/geofencing.jd
@@ -332,22 +332,39 @@ LocationServices.GeofencingApi.removeGeofences(
<p>This section outlines recommendations for using geofencing with the location
APIs for Android.</p>
-<h3>Reduce power consumption</h3>
+<h3>
+ Reduce power consumption
+</h3>
-<p>You can use the following techniques to optimize power consumption in your apps that use geofencing:</p>
+<p>
+ You can use the following techniques to optimize power consumption in your
+ apps that use geofencing:
+</p>
<ul>
-<li><p>Set the <a href="{@docRoot}android/reference/com/google/android/gms/location/Geofence.Builder.html#setNotificationResponsiveness(int)">
-notification responsiveness</a> to a higher value. Doing so improves power consumption by
-increasing the latency of geofence alerts. For example, if you set a responsiveness value of five
-minutes your app only checks for an entrance or exit alert once every five minutes.
-Setting lower values does not necessarily mean that users will be notified within that time period
-(for example, if you set a value of 5 seconds it may take a bit longer than that to receive the
-alert).</p></li>
-<li><p>Use a larger geofence radius for locations where a user spends a significant amount of time,
-such as home or work. While a larger radius doesn't directly reduce power consumption, it reduces
-the frequency at which the app checks for entrance or exit, effectively lowering overall power
-consumption.</p></li>
+ <li>
+ <p>
+ Set the <a href=
+ "https://developers.google.com/android/reference/com/google/android/gms/location/Geofence.Builder.html#setNotificationResponsiveness(int)">
+ notification responsiveness</a> to a higher value. Doing so improves
+ power consumption by increasing the latency of geofence alerts. For
+ example, if you set a responsiveness value of five minutes your app only
+ checks for an entrance or exit alert once every five minutes. Setting
+ lower values does not necessarily mean that users will be notified
+ within that time period (for example, if you set a value of 5 seconds it
+ may take a bit longer than that to receive the alert).
+ </p>
+ </li>
+
+ <li>
+ <p>
+ Use a larger geofence radius for locations where a user spends a
+ significant amount of time, such as home or work. While a larger radius
+ doesn't directly reduce power consumption, it reduces the frequency at
+ which the app checks for entrance or exit, effectively lowering overall
+ power consumption.
+ </p>
+ </li>
</ul>
<h3>Choose the optimal radius for your geofence</h3>