@@ -332,22 +332,39 @@ LocationServices.GeofencingApi.removeGeofences(
332332<p>This section outlines recommendations for using geofencing with the location
333333APIs for Android.</p>
334334
335- <h3>Reduce power consumption</h3>
335+ <h3>
336+ Reduce power consumption
337+ </h3>
336338
337- <p>You can use the following techniques to optimize power consumption in your apps that use geofencing:</p>
339+ <p>
340+ You can use the following techniques to optimize power consumption in your
341+ apps that use geofencing:
342+ </p>
338343
339344<ul>
340- <li><p>Set the <a href="{@docRoot}android/reference/com/google/android/gms/location/Geofence.Builder.html#setNotificationResponsiveness(int)">
341- notification responsiveness</a> to a higher value. Doing so improves power consumption by
342- increasing the latency of geofence alerts. For example, if you set a responsiveness value of five
343- minutes your app only checks for an entrance or exit alert once every five minutes.
344- Setting lower values does not necessarily mean that users will be notified within that time period
345- (for example, if you set a value of 5 seconds it may take a bit longer than that to receive the
346- alert).</p></li>
347- <li><p>Use a larger geofence radius for locations where a user spends a significant amount of time,
348- such as home or work. While a larger radius doesn't directly reduce power consumption, it reduces
349- the frequency at which the app checks for entrance or exit, effectively lowering overall power
350- consumption.</p></li>
345+ <li>
346+ <p>
347+ Set the <a href=
348+ "https://developers.google.com/android/reference/com/google/android/gms/location/Geofence.Builder.html#setNotificationResponsiveness(int)">
349+ notification responsiveness</a> to a higher value. Doing so improves
350+ power consumption by increasing the latency of geofence alerts. For
351+ example, if you set a responsiveness value of five minutes your app only
352+ checks for an entrance or exit alert once every five minutes. Setting
353+ lower values does not necessarily mean that users will be notified
354+ within that time period (for example, if you set a value of 5 seconds it
355+ may take a bit longer than that to receive the alert).
356+ </p>
357+ </li>
358+
359+ <li>
360+ <p>
361+ Use a larger geofence radius for locations where a user spends a
362+ significant amount of time, such as home or work. While a larger radius
363+ doesn't directly reduce power consumption, it reduces the frequency at
364+ which the app checks for entrance or exit, effectively lowering overall
365+ power consumption.
366+ </p>
367+ </li>
351368</ul>
352369
353370<h3>Choose the optimal radius for your geofence</h3>
0 commit comments