Optimizing Kotlin Foreground Services for Location Polling

Writing background tracking applications for Android has become increasingly complex. Google's aggressive battery optimizations (Doze mode, App Standby Buckets, and strict Foreground Service permissions) are designed to prevent rogue developers from draining device batteries. However, for an emergency responder app like **ABHAYASTRA**, a silent service termination is unacceptable.

Here is how we solved background persistence while remaining Google Play Store compliant.

The FService Type Restriction Starting in Android 14, apps must declare specific foreground service types. For our client engine, we utilize: ```xml <service android:name=".services.EmergencyTrackingService" android:foregroundServiceType="specialUse|location|camera|microphone" /> ``` This lets the system know that our application needs foreground status specifically to fetch locations and streams during emergency states.

Battery Optimization & Fused Location provider To prevent battery drain, we programmatically toggle polling configurations. - **Standby Mode**: 1-hour interval heartbeat checks. Uses minimal power, relying on cell tower changes. - **Active Crisis Mode**: 2-second interval GPS updates. We request high-accuracy, low-latency updates from the `FusedLocationProviderClient`: ```kotlin val locationRequest = LocationRequest.Builder( Priority.PRIORITY_HIGH_ACCURACY, 2000 ).apply { setMinUpdateIntervalMillis(1000) setMaxUpdateDelayMillis(0) }.build() ```

By requesting high priority only during a verified emergency trigger, we ensure the device maintains long battery lives during daily standby operations while providing pin-point accuracy during crisis.