Rather than taking an action at every CONNECTIVITY_ACTION, ACTION_NEW_PICTURE, or ACTION_NEW_VIDEO broadcast, apps will wait for the JobScheduler API to tell them when it's time to act.

Android 16 introduces JobScheduler which can return multiple reasons why a job is pending, due to both explicit constraints set by the developer and implicit constraints set by the system.

The JobScheduler class is only available in the Android L Developer Preview, but I'm hopeful that it will turn up in the Android compatibility library, as well.