7.4.6. Sync Settings
Device implementations:
[C-0-1] MUST have the master auto-sync setting on by default so that the method
getMasterSyncAutomatically()
returns “true”.
7.4.7. Data Saver
If device implementations include a metered connection, they are:
[SR] STRONGLY RECOMMENDED to provide the data saver mode.
If device implementations provide the data saver mode, they:
[C-1-1] MUST support all the APIs in the
ConnectivityManager
class as described in the
SDK
documentation
[C-1-2] MUST provide a user interface in the settings, that handles the
Settings.ACTION_IGNORE_BACKGROUND_DATA_RESTRICTIONS_SETTINGS
intent, allowing
users to add applications to or remove applications from the whitelist.
If device implementations do not provide the data saver mode, they:
[C-2-1] MUST return the value
RESTRICT_BACKGROUND_STATUS_DISABLED
for
ConnectivityManager.getRestrictBackgroundStatus()
[C-2-2] MUST NOT broadcast
ConnectivityManager.ACTION_RESTRICT_BACKGROUND_CHANGED
.
[C-2-3] MUST have an activity that handles the
Settings.ACTION_IGNORE_BACKGROUND_DATA_RESTRICTIONS_SETTINGS
intent but MAY
implement it as a no-op.
7.4.8. Secure Elements
If device implementations support
Open Mobile API
capable secure elements and make them
available to 3rd-party apps, they:
[C-1-1] MUST enumerate the available Secure Elements readers when
android.se.omapi.SEService.getReaders()
method is called.
7.5. Cameras
If device implementations include at least one camera, they:
[C-1-1] MUST declare the
android.hardware.camera.any
feature flag.
[C-1-2] MUST be possible for an application to simultaneously allocate 3 RGBA_8888
bitmaps equal to the size of the images produced by the largest-resolution camera sensor
on the device, while camera is open for the purpose of basic preview and still capture.
7.5.1. Rear-Facing Camera
A rear-facing camera is a camera located on the side of the device opposite the display; that is, it
images scenes on the far side of the device, like a traditional camera.
Page 101 of 132
