Back to feed
Dev.to
Dev.to
7/21/2026
Keeping Android Background Services Alive in a World of OEM Battery Optimizations

Keeping Android Background Services Alive in a World of OEM Battery Optimizations

Short summary

A developer shares lessons from building Muffle, an Android app that automates phone silencing based on calendar and location triggers. The core challenge is keeping background services alive despite aggressive OEM battery optimizations from Samsung, Xiaomi, and OnePlus that kill non-UI processes. The solution uses a persistent Foreground Service with START_STICKY, a BroadcastReceiver for system state changes, and careful handling of AudioManager and Do Not Disturb permissions.

  • •OEM battery optimizations from Samsung, Xiaomi, and OnePlus aggressively kill background services
  • •Solution: persistent Foreground Service with visible notification plus START_STICKY and BroadcastReceiver
  • •GPS geofencing can fail when OEMs freeze location providers after screen-off; workarounds require device-specific handling

Generated with AI, which can make mistakes.

Read full article at Dev.to

Is this a good recommendation for you?

Comments

Failed to load comments. Please try again.

Explore more

The original title is "Keeping background services alive: Lessons from building Muffle"
Dev.to
Architecting a background-controlled sound manager that actually survives Doze mode
Dev.to
The original title is "Architecting Location Based Automation without Killing Android Battery Life"
Dev.to
The original title is "Architecting a Location Aware Foreground Service Without Battery Drain"
Dev.to