Find Yourself! Navigating the World of Android Location
summary
Compares Google’s Fused Location Provider (fast last location but opaque and needs Play Services) with raw Android providers where you manage GPS, network and passive sources and balance battery vs accuracy. Recommends a 30 second warm-up and burst strategy (30s on, 10s off, short on cycles) to halve battery use, discards points >100m (aims for ~30m), uses JobScheduler for background sampling (example: periodic 5–10 minute job piggybacks foreground location), suggests averaging 5–10 samples and geodetic→Cartesian transforms to fix urban canyon error. Mapbox SDK combines Fused + Android and currently lacks interpolation.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:42Location providers overview
- 3:55Fuse location provider pros and cons
- 4:39Android built-in APIs control
- 5:22Battery vs accuracy balance
- 7:50Background location on Oreo
- 8:52Foreground services and value
- 9:13Geo-fences limitations
- 10:37Job scheduler benefits
- 12:45Urban canyon effect
- 13:46Cleaning location data
- 16:36Q&A session
related talks
39mBeyond the Blue Dot: New Features in Android Location
59mDon't Get Lost with the Android Localization Framework
14mThe Future of Android Location Services
39mThinking about battery life: strategies for location monitoring (Geofence)
38mWhen Android Meets Maps
20mOverview of different geo APIs
41mBuilding Exceptional Android Location Experiences with Mapbox
37mWhere the Heck Am I? Understanding and Managing Location in Your Application