Thinking about battery life: strategies for location monitoring (Geofence)
summary
Compares a custom geofence implementation (using the Fused Location Provider and haversine formula to compute distance) with Google Mobile Services (GMS) Geofence. Measures battery use and accuracy on a walk in Shibuya with 500 m radius and 5 s updates: custom geofence uses about twice the idle power (~269 mA) and supports polygon regions and lower latency, while GMS Geofence uses much less power (~152 mA) but has delayed triggers (~300 m late, ~20% error) and occasional missed events; also notes a 100-geofence limit in GMS.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:31Geofencing use cases
- 6:26Geofence algorithms
- 15:38Location accuracy
- 16:43DIY geofence
- 22:35Battery optimization
- 31:44Geofencing with GMS
- 35:50Geofence power comparison
- 37:42Geofence pros and cons
- 38:46Q&A
related talks
19mFind Yourself! Navigating the World of Android Location
39mBeyond the Blue Dot: New Features in Android Location
41mWhat's New in Google Play Services
14mThe Future of Android Location Services
59mDon't Get Lost with the Android Localization Framework
22mPower optimization for Android
26mMaking Sense The Road to mobile Awareness
21mImproving battery life with restrictions