Add support for background execution limits on Android 8+
See original GitHub issueSee https://developer.android.com/about/versions/oreo/background
For minimal support we could make MailService
and PushService
foreground services. We also need to make sure at least one of them is started whenever we perform a background operation.
For a nicer solution we could look into making periodic syncs use JobIntentService. For Push we still need to use a foreground service. We probably want to create a separate notification channel. That way users will be able hide the ongoing notification required for a foreground service.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Background Execution Limits - Android Developers
Background Service Limitations : While an app is idle, there are limits to its use of background services. This does not apply to...
Read more >Exploring Background Execution Limits on Android Oreo
Starting a service in the foreground · First using the startForegroundService() method, passing an intent for our service task to be carried out....
Read more >Add support for background execution limits on Android 8+
For a nicer solution we could look into making periodic syncs use JobIntentService. For Push we still need to use a foreground service....
Read more >Android Oreo background execution limits - YouTube
Android Oreo introduces important background execution limits that all developers should be aware of, such as not being able to freely ...
Read more >Background services Android oreo (limitation) - Stack Overflow
For example, if an app used a service to compact its storage, that would usually be a background service. If your app targets...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
No. We still need to fix or disable Push.
Thoughts on using WorkManager for this?