blob: f54e932ec373926c43f5dbc87c6c11bbdfdd8818 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
Copyright 2016 The Android Open Source Project
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.
<group>Security</group> <!-- This field will be deprecated in the future
and replaced with the "categories" tags below. -->
<!-- Include additional dependencies here.-->
<!-- dependency></dependency -->
<template src="base" />
This sample demonstrates how to store/access data in a device protected storage
which is always available while the device is booted.
This sample works as a simple alarm clock. On > Android N devices, the scheduled alarms
go off after reboot even before the user enters their credentials.
<!-- List of APIs that this sample should be cross-referenced under. Use <android>
for fully-qualified Framework class names ("android:" namespace).
Use <ext> for custom namespaces, if needed. See "Samples Index API" documentation
for more details. -->
<!-- 1-3 line description of the sample here.
Avoid simply rearranging the sample's title. What does this sample actually
accomplish, and how does it do it? -->
Sample demonstrating how to store data in a device protected storage which
is always available while the device is booted both before and after any
user credentials(PIN/Pattern/Password) are entered.
<!-- Multi-paragraph introduction to sample, from an educational point-of-view.
Makrdown formatting allowed. This will be used to generate a mini-article for the
sample on DAC. -->
This sample demonstrates how to store and access data in a device protected
storage which is always available while the device is booted.
Starting from Android N, the system provides two storage locations for user data:
- Credential protected:
- The default storage location for all apps, available only after the user has entered their pattern/password
- Device protected:
- A new storage location which is always available while the device is booted, both before and after any user credentials are entered
Apps can mark individual components as being direct boot aware which indicates to the system that they can safely run when
Credential protected storage is unavailable (an direct boot aware component primarily relies on data stored in the new Device protected storage area,
but they may access Credential protected data when unlocked) by adding `directBootAware="true"` in the manifest.
<activity|provider|receiver|service ...
Components marked as directBoot aware are normal components that will continue to be available after the
Credential protected storage becomes available. The storage APIs on the Context supplied to these components will always point to Credential protected storage by default.
To access Device protected storage, you can create a secondary Context using this API
All of the storage APIs on this returned Context will be redirected to point at Device protected storage.
You need to be careful what data is stored/moved to a device protected storage
because the storage isn't protected by the user's credential (PIN/Pattern/Password)
You shouldn't store sensitive data (such as user's emails, auth tokens) in a
device protected storage.