To support running apps before the user provides the credentials needed to unlock private app data, all Android N devices now provide two storage locations for data: All apps will still receive Intent.ACTION_BOOT_COMPLETED after the user unlocks the device. You can pick the subset of your app components that need to be Direct Boot aware, but if you are using a custom Application class, it is assumed to be Direct Boot aware if any component inside your app is marked as Direct Boot aware.įor apps that need to run as soon as the system starts in Direct Boot mode, there is a new Intent.ACTION_LOCKED_BOOT_COMPLETED broadcast. In order to let your app run before the user unlocks the device, you have to explicitly mark components as being Direct Boot aware in the manifest: Please note that this is not an exhaustive list and we look forward to seeing what other kinds of apps can benefit from Direct Boot. Apps that provide services to other apps or the system, such as Accessibility Services.
Apps that provide important and timely notifications, like messaging apps.Apps that schedule alarms, such as alarm clocks.Not every app should run in Direct Boot mode, so before you start coding check if your app fits these common use cases: In this mode, the operating system is fully operational, but access to private app data is limited and only apps that have been updated to be Direct Boot aware can run. Starting with Android N, a device that has been powered on can boot into a new mode called Direct Boot before the user has a chance to unlock it for the first time. Posted by Wojtek Kaliciński, Developer Advocate
0 kommentar(er)
