Doo z z z z z e
summary
Explains how Doze and App Standby change exact timing and background execution and why Android O blocks many implicit broadcasts so apps relying on manifest-registered receivers break unless replaced or wrapped with a custom permission workaround. Shows concrete APIs: use setExactAndAllowWhileIdle for precise alarms, prefer JobScheduler with the JobScheduler flex parameter for periodic, fall back to GCMNetworkManager or AlarmManager, and avoid background services on Android O by using foreground services. Demonstrates an Android-Job library that auto-selects engines, reschedules after reboot, and reduces boilerplate.
AI-written summary · about
chapters (14)
- 0:00Introduction and speaker intro
- 0:55Background work and power saving modes
- 3:28Doze mode and app standby explained
- 5:12Android O background execution limits
- 7:00Broadcast removals and white lists
- 9:04Reminder app requirements and AlarmManager
- 14:26AlarmManager API changes across Android versions
- 15:29JobScheduler for sync jobs
- 18:59GCM Network Manager alternative
- 21:09Fallback strategies for older devices
- 23:36Introducing Android-Job library
- 26:47Implementing jobs with Android-Job
- 29:40FAQ and library usage details
- 32:55Testing and troubleshooting jobs
related talks
42mBuilding for Android O
28mBest practices for running background work on Android
50mWTF with Android Background Restrictions
30mApp Standby vs. Doze: Understanding System Sleep
34mChange Can be Good: The New World of Android Oreo
33mAndroid 5.0 internals and our inferiority complex
36mBackground Work in Android: Strategies and Best Practices
33mIs my application taking up too much power?