Change Can be Good: The New World of Android Oreo
summary
Android Oreo enforces real background and location limits: background services throw IllegalStateException unless moved to startForegroundService and promoted, so work shifts to JobScheduler / JobIntentService or high‑priority FCM (which is exempt). Location is throttled system‑wide (use batching, passive listeners, geofences — limit ~100 geofences — or beacons), and wake locks get cleared when no active components exist. Surprising stat: one in three users cite battery as top problem. New tools mentioned include Oboe for low‑latency audio, Neural Networks API and a shared memory API; samples exist on Google’s GitHub.
AI-written summary · about
chapters (8)
- 0:00Introduction to Android Oreo
- 5:54Why Android Oreo changes matter
- 6:58Background and location limits explained
- 12:56Foreground vs background services
- 18:55Job scheduler and background work
- 22:24Manifest broadcast restrictions
- 25:11Location gathering in background
- 30:49Impact and future of changes
related talks
32mBuilding for Android Oreo
42mBuilding for Android O
34mDoo z z z z z e
28mBest practices for running background work on Android
50mWTF with Android Background Restrictions
37mA guide to using foreground services and background work in Android 14
11mEffective background tasks on Android
26mMigrate your existing app to target Android Oreo and above