%!$ Easy Diy Woodworking Bench Plans For You #!@

Open Source Commercial. To facilitate this, the system update subsystem for softsare that report android. Unicode and Font 3. Laciak, R. When an app requests a light status bar, Open hardware software 6.0 device implementations MUST change the color of the system status icons to black [ Resources, 34 ].

Added a check to the application startup to verify that the. NET Framework 4. Posted on May 24, 5 Comments. Added code to correctly restore fan controls and other states when resuming the from sleep. Migrated the application from. NET Framework version 2. NET Framework version 4. Fixed the issue of an unresponsive user interface when changing the system display scale. Improved the DPI awareness display scaling of the user interface.

Posted on May 6, 26 Comments. Added support for persisting and restoring the expanded state of the UI tree view. If no third-party applications are installed that make use of this functionality, the default behavior SHOULD be to display web search engine results and suggestions. Android also includes the Assist APIs to allow applications to elect how much information of the current context is shared with the assistant on the device [ Resources, 31 ].

Device implementations supporting the Assist action MUST indicate clearly to the end user when the context is shared by displaying a white light around the edges of the screen.

To ensure clear visibility to the end user, the indication MUST meet or exceed the duration and brightness of the Android Open Source Project implementation.

Device implementations MUST display Toasts from applications to end users in some high-visibility manner. Android supports a variant theme with translucent system bars, which allows application developers to fill the area behind the status and navigation bar with their app content. To enable a consistent developer experience in this configuration, it is important the status bar icon style is maintained across different device implementations.

When an app requests a light status bar, Android device implementations MUST change the color of the system status icons to black [ Resources, 34 ]. Live wallpapers are animations, patterns, or similar images with limited input capabilities that display as a wallpaper, behind other applications.

Hardware is considered capable of reliably running live wallpapers if it can run all live wallpapers, with no limitations on functionality, at a reasonable frame rate with no adverse effects on other applications. As an example, some live wallpapers may use an OpenGL 2. Live wallpaper will not run reliably on hardware that does not support multiple OpenGL contexts because the live wallpaper use of an OpenGL context may conflict with other applications that also use an OpenGL context.

Device implementations capable of running live wallpapers reliably as described above SHOULD implement live wallpapers, and when implemented MUST report the platform feature flag android. Device implementations including the recents function navigation key as detailed in section 7. Android includes support for Input Management and support for third-party input method editors [ Resources, 39 ]. Device implementations that allow users to use third-party input methods on the device MUST declare the platform feature android.

Device implementations that declare the android. Device implementations MUST display the settings interface in response to the android. Android includes support for interactive screensavers called Dreams [ Resources, 41 ]. Dreams allows users to interact with applications when a device connected to a power source is idle or docked in a desk dock.

When a device has a hardware sensor e. Android includes support for color emoji characters. All devices MUST be capable of rendering these emoji characters in color glyph. Android includes support for Roboto 2 font with different weights—sans-serif-thin, sans-serif-light, sans-serif-medium, sans-serif-black, sans-serif-condensed, sans-serif-condensed-light—which MUST all be included for the languages available on the device and full Unicode 7.

Android includes features that allow security-aware applications to perform device administration functions at the system level, such as enforcing password policies or performing remote wipe, through the Android Device Administration API [ Resources, 44 ]. If a device implementation declares the android. Device implementations MAY have a preinstalled application performing device administration functions but this application MUST NOT be set as the Device Owner app without explicit consent or action from the user or the administrator of the device.

The device owner provisioning process the flow initiated by android. If the device implementation reports android. The managed profile provisioning process the flow initiated by android. Android provides an accessibility layer that helps users with disabilities to navigate their devices more easily. An open source implementation of an accessibility service is available from the Eyes Free project [ Resources, 53 ].

Device implementations reporting the feature android. Programs fields [ Resources, 59 ]. Android Television device input devices i. Android Television device implementations MUST support TV input app linking, which allows all inputs to provide activity links from the current activity to another activity i.

Device implementations MUST support the core media formats specified in the Android SDK documentation [ Resources, 64 ] except where explicitly permitted in this document. Specifically, device implementations MUST support the media formats, encoders, decoders, file types, and container formats defined in the tables below and reported via MediaCodecList [ Resources, 65 ].

All of these codecs are provided as software implementations in the preferred Android implementation from the Android Open Source Project. Please note that neither Google nor the Open Handset Alliance make any representation that these codecs are free from third-party patents.

Those intending to use this source code in hardware or software products are advised that implementations of this code, including in open source software or shareware, may require patent licenses from the relevant patent holders. Android device implementations with H. Android device implementations when supporting VP8 codec as described in section 5. Android device implementations, when supporting VP9 codec as described in section 5.

Android device implementations, when supporting H. Device implementations that declare android. If capture for the above sample rates is supported, then the capture MUST be done without up-sampling at any ratio higher than or Any up-sampling or down-sampling MUST include an appropriate anti-aliasing filter.

In addition to the above recording specifications, when an application has started recording an audio stream using the android. If the platform supports noise suppression technologies tuned for speech recognition, the effect MUST be controllable from the android. NoiseSuppressor API. The android. Devices that declare android. AudioRecord API to record from this audio source, it can capture a mix of all audio streams except for the following:.

Android provides an API for audio effects for device implementations [ Resources, 69 ]. Device implementations that declare the feature android. Android Television device implementations MUST include support for system Master Volume and digital audio output volume attenuation on supported outputs, except for compressed audio passthrough output where no audio decoding is done on the device.

Audio latency is the time delay as an audio signal passes through a system. Many classes of applications rely on short latencies, to achieve real-time sound effects.

PackageManager class [ Resources, 70 ]. Device implementations that include android. Specifically, devices MUST support the following media network protocols:. Device implementations that support secure video output and are capable of supporting secure surfaces MUST declare support for Display.

Device implementations that declare support for Display. The upstream Android open source implementation includes support for wireless Miracast and wired HDMI displays that satisfies this requirement. A device implementation that reports feature android. Android compatible devices MUST be compatible with:. Android includes support for secure adb. Secure adb enables adb on known authenticated hosts. Device implementations MUST support secure adb.

Device implementations MUST include the Monkey framework, and make it available for applications to use. Systrace must be inactive by default, and there MUST be a user-accessible mechanism to turn on Systrace.

Most Linux-based systems and Apple Macintosh systems recognize Android devices using the standard Android SDK tools, without additional support; however Microsoft Windows systems typically require a driver for new Android devices.

If a device implementation is unrecognized by the adb tool as provided in the standard Android SDK, device implementers MUST provide Windows drivers allowing developers to connect to the device using the adb protocol. Android includes support for developers to configure application development-related settings. Device implementations MUST honor the android. If an API in the SDK interacts with a hardware component that is stated to be optional and the device implementation does not possess that component:.

A typical example of a scenario where these requirements apply is the telephony API: even on non-phone devices, these APIs must be implemented as reasonable no-ops. PackageManager class for the same build fingerprint. Android includes facilities that automatically adjust application assets and UI layouts appropriately for the device, to ensure that third-party applications run well on a variety of hardware configurations [ Resources, 78 ]. Android Watch devices detailed in section 2 MAY have smaller screen sizes as described in this section.

Specifically, device implementations MUST report the correct screen size according to the following logical density-independent pixel dp screen dimensions. Device implementations MUST correctly honor applications' stated support for small, normal, large, and xlarge screens, as described in the Android SDK documentation. The screen aspect ratio MUST be a value from 1. The Android UI framework defines a set of standard logical densities to help application developers target application resources.

Device implementations MUST report only one of the following logical Android framework densities through the android. Device implementations SHOULD define the standard Android framework density that is numerically closest to the physical density of the screen, unless that logical density pushes the reported screen size below the minimum supported.

If the standard Android framework density that is numerically closest to the physical density results in a screen size that is smaller than the smallest supported compatible screen size dp width , device implementations SHOULD report the next lowest standard Android framework density.

Device implementations MUST report correct values for all display metrics defined in android. DisplayMetrics [ Resources, 79 ] and MUST report the same values regardless of whether the embedded or external screen is used as the default display. Devices MUST report which screen orientations they support android. For example, a device with a fixed orientation landscape screen, such as a television or laptop, SHOULD only report android. Devices that report both screen orientations MUST support dynamic orientation by applications to either portrait or landscape screen orientation.

Device implementations MAY select either portrait or landscape orientation as the default. That is:. Android device implementations MAY support this extension pack, and—only if fully implemented—MUST identify the support through the android. Note that Android includes support for applications to optionally specify that they require specific OpenGL texture compression formats. These formats are typically vendor-specific. Device implementations are not required by Android to implement any specific texture compression format.

Android includes a mechanism for applications to declare that they want to enable hardware acceleration for 2D graphics at the Application, Activity, Window, or View level through the use of a manifest tag android:hardwareAccelerated or direct API calls [ Resources, 82 ]. The Android platform includes APIs that allow applications to render rich graphics to the display. Android includes support for secondary display to enable media sharing capabilities and developer APIs for accessing external displays.

If a device supports an external display either via a wired, wireless, or an embedded additional display connection then the device implementation MUST implement the display manager API as described in the Android SDK documentation [ Resources, 84 ].

Devices MUST support a touchscreen or meet the requirements listed in 7. All other device implementations MUST implement a soft keyboard and:. The availability and visibility requirement of the Home, Recents, and Back functions differ between device types as described in this section. These functions MAY be implemented via dedicated physical buttons such as mechanical or capacitive touch buttons , or MAY be implemented using dedicated software keys on a distinct portion of the screen, gestures, touch panel, etc.

Android supports both implementations. All of these functions MUST be accessible with a single action e. Recents function, if provided, MUST have a visible button or icon unless hidden together with other navigation functions in full-screen mode.

This does not apply to devices upgrading from earlier Android versions that have physical buttons for navigation and no recents key. The Menu function is deprecated in favor of action bar since Android 4. Therefore the new device implementations shipping with Android 6. For backwards compatibility, device implementations MUST make the Menu function available to applications when targetSdkVersion is less than 10, either by a physical button, a software key, or gestures.

This Menu function should be presented unless hidden together with other navigation functions. Android device implementations with the support of the Assist action [ Resources, 30 ] MUST make this accessible with a single action e.

Device implementations MAY use a distinct portion of the screen to display the navigation keys, but if so, MUST meet these requirements:.

Device implementations that do include a pointer input system:. Android includes support for a variety of touchscreens, touch pads, and fake touch input devices. Touchscreen based device implementations are associated with a display [ Resources, 86 ] such that the user has the impression of directly manipulating items on screen.

Since the user is directly touching the screen, the system does not require any additional affordances to indicate the objects being manipulated. In contrast, a fake touch interface provides a user input system that approximates a subset of touchscreen capabilities.

For example, a mouse or remote control that drives an on-screen cursor approximates touch, but requires the user to first point or focus then click. Numerous input devices like the mouse, trackpad, gyro-based air mouse, gyro-pointer, joystick, and multi-touch trackpad can support fake touch interactions. Android includes the feature constant android. Device implementations that declare the fake touch feature MUST meet the fake touch requirements in section 7.

Device implementations MUST report the correct feature corresponding to the type of input used. Device implementations that include a touchscreen single-touch or better MUST report the platform feature constant android. Device implementations that report the platform feature constant android. Devices that declare support for android.

Android Television device implementations MUST support button mappings for game controllers as listed below. The upstream Android implementation includes implementation for game controllers that satisfies this requirement. The logical value is defined to be the clockwise rotation away from the vertical axis; for example, a logical value of 0 represents no rotation and the up button being pressed, while a logical value of 1 represents a rotation of 45 degrees and both the up and left keys being pressed.

The remote control MAY be a physical remote or can be a software-based remote that is accessible from a mobile phone or tablet. The remote control MUST meet the requirements defined below. Android includes APIs for accessing a variety of sensor types. Devices implementations generally MAY omit these sensors, as provided for in the following subsections. For example, device implementations:.

The list above is not comprehensive; the documented behavior of the Android SDK and the Android Open Source Documentations on Sensors [ Resources, 89 ] is to be considered authoritative. Some sensor types are composite, meaning they can be derived from data provided by one or more other sensors. Examples include the orientation sensor, and the linear acceleration sensor.

Device implementations SHOULD implement these sensor types, when they include the prerequisite physical sensors as described in [ Resources, 92 ]. If a device implementation includes a composite sensor it MUST implement the sensor as described in the Android Open Source documentation on composite sensors [ Resources, 92 ].

If a device implementation does include a 3-axis accelerometer, it:. If a device does include a 3-axis magnetometer, it:. If a device implementation includes a gyroscope, it:. If a device implementation includes a barometer, it:. Device implementations MAY include an ambient thermometer temperature sensor. Device implementations MAY include a proximity sensor. If a device implementation does include a proximity sensor, it:.

Device implementations supporting a set of higher quality sensors that can meet all the requirements listed in this section MUST identify the support through the android. A device declaring android. Note that all power consumption requirements in this section do not include the power consumption of the Application Processor.

It is inclusive of the power drawn by the entire sensor chain - the sensor, any supporting circuitry, any dedicated sensor processing system, etc. The following sensor types MAY also be supported on a device implementation declaring android. If a device implementation includes a fingerprint sensor and has a corresponding API for third-party developers, it:.

While these voice calls may or may not be packet-switched, they are for the purposes of Android considered independent of any data connectivity that may be implemented using the same network.

Android MAY be used on devices that do not include telephony hardware. That is, Android is compatible with devices that are not phones.

If a device implementation does include support for If a device implementation includes support for Wi-Fi Direct, then it:. If a device implementation does include NFC hardware and plans to make it available to third-party apps, then it:. As the classes android. NdefMessage and android. Device implementations MUST include support for one or more forms of data networking. Device implementations where a physical networking standard such as Ethernet is the primary data connection SHOULD also include support for at least one common wireless data standard, such as Socket and java.

The required level of IPv6 support depends on the network type, as follows:. Redundant multicast IPv6 packets, such as repeated identical Router Advertisements, MAY be rate-limited in hardware or firmware if doing so is necessary to save power. 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.

A front-facing camera is a camera located on the same side of the device as the display; that is, a camera typically used to image the user, such as for video conferencing and similar applications. If a device implementation includes at least one camera, it SHOULD be possible for an application to simultaneously allocate 3 bitmaps equal to the size of the images produced by the largest-resolution camera sensor on the device.

If a device implementation includes at least one rear-facing camera, it:. Device implementations MAY include a front-facing camera.

If a device implementation includes at least one front-facing camera, it:. If a device includes support for an external camera, it:. Camera-based video encoding MAY be supported. Android includes two API packages to access the camera, the newer android. The older API package, android. Camera, is marked as deprecated in Android 5. For instance, cameras that lack autofocus MUST still call any registered android. AutoFocusCallback instances even though this has no relevance to a non-autofocus camera.

Device implementations MUST recognize and honor each parameter name defined as a constant on the android. Parameters class, if the underlying hardware supports the feature. If the device hardware does not support a feature, the API must behave as documented.

Because not all device implementations can fully support all the features of the android. That is, when the device is held in the landscape orientation, cameras MUST capture images in the landscape orientation. The memory available to the kernel and userspace on device implementations MUST be at least equal or larger than the minimum values specified by the following table. If this slot is used to satisfy the shared storage requirement, the device implementation:. Alternatively, device implementations MAY allocate internal non-removable storage as shared storage for apps as included in the upstream Android Open Source Project; device implementations SHOULD use this configuration and software implementation.

Device implementations MUST enforce as documented the android. Shared storage MUST otherwise be writable by any application that obtains that permission. Regardless of the form of shared storage used, if the device implementation has a USB port with USB peripheral mode support, it MUST provide some mechanism to access the contents of shared storage from a host computer.

If the device implementation supports Media Transfer Protocol, it:. Device implementations such as a television, MAY enable adoption through USB ports as the device is expected to be static and not mobile. Device implementations MAY omit a microphone. Conversely, device implementations that do possess a microphone:. In order to be compatible with the headsets and other audio accessories using the 3.

If a device implementation has a 4 conductor 3. Near-Ultrasound audio is the Some minimum performance and power criteria are critical to the user experience and impact the baseline assumptions developers would have when developing an app.

Device implementations MUST provide a smooth user interface by ensuring a consistent frame rate and response times for applications and games. Device implementations MUST meet the following requirements:. Device implementations MUST ensure internal storage file access performance consistency for read and write operations. Further, the triggering, maintenance, wakeup algorithms and the use of Global system settings of these power-saving modes MUST not deviate from the Android Open Source Project.

A more accurate accounting and reporting of the power consumption provides the app developer both the incentives and the tools to optimize the power usage pattern of the application. Therefore, device implementations:. Device implementations MUST implement a security model consistent with the Android platform security model as defined in Security and Permissions reference document in the APIs [ Resources, ] in the Android developer documentation.

Specifically, compatible devices MUST support the security mechanisms described in the follow subsections. Device implementations MUST support the Android permissions model as defined in the Android developer documentation [ Resources, ]. Specifically, implementations MUST enforce each permission defined as described in the SDK documentation; no permissions may be omitted, altered, or ignored.

Implementations MAY add additional permissions, provided the new permission ID strings are not in the android. Permissions with a protection level of dangerous are runtime permissions. Device implementations:. Device implementations MUST support running multiple applications as the same Linux user ID, provided that the applications are properly signed and constructed, as defined in the Security and Permissions reference [ Resources, ]. Device implementations MAY include runtime environments that execute applications using some other software or technology than the Dalvik Executable Format or native code.

However, such alternate execution environments MUST NOT compromise the Android security model or the security of installed Android applications, as described in this section. Alternate runtimes MUST themselves be Android applications, and abide by the standard Android security model, as described elsewhere in section 9. When installing applications, alternate runtimes MUST obtain user consent for the Android permissions used by the application.

If an application needs to make use of a device resource for which there is a corresponding Android permission such as Camera, GPS, etc. If the runtime environment does not record application capabilities in this manner, the runtime environment MUST list all permissions held by the runtime itself when installing any application using that runtime.

Android includes support for multiple users and provides support for full user isolation [ Resources, ]. Device implementations MAY enable multiple users, but when enabled MUST meet the following requirements related to multi-user support [ Resources, ]:. Android includes support for warning users of any outgoing premium SMS message [ Resources, ].

Premium SMS messages are text messages sent to a service registered with a carrier that may incur a charge to the user.

Device implementations that declare support for android. The upstream Android Open Source Project provides an implementation that satisfies this requirement. SELinux or any other security features implemented below the Android framework:. If a device implementation has a mechanism that routes network data traffic through a proxy server or VPN gateway by default for example, preloading a VPN service with android.

If the device implementation supports a secure lock screen reporting " true " for KeyguardManager. If a device implementation is already launched on an earlier Android version with full-disk encryption disabled by default, such a device cannot meet the requirement through a system software update and thus MAY be exempted. PBKDF2 or scrypt.

If the user has not specified a lockscreen passcode or has disabled use of the passcode for encryption, the system SHOULD use a default passcode to wrap the encryption key. If the device provides a hardware-backed keystore, the password stretching algorithm MUST be cryptographically bound to that keystore.

The upstream Android Open Source project provides a preferred implementation of this feature based on the Linux kernel feature dm-crypt. Verified boot is a feature that guarantees the integrity of the device software.

If a device implementation supports the feature, it MUST:. The upstream Android Open Source Project provides a preferred implementation of this feature based on the Linux kernel feature dm-verity.

Starting from Android 6. If a device implementation is already launched without supporting verified boot on an earlier version of Android, such a device can not add support for this feature with a system software update and thus are exempted from the requirement.

Devices MUST provide users with a mechanism to perform a "Factory Data Reset" that allows logical and physical deletion of all data except for the system image and data in other partitions that can be regarded as part of the sytem image. However, note that no software test package is fully comprehensive. This will minimize the risk of introducing bugs that create incompatibilities requiring rework and potential device updates.

The CTS is designed to be run on an actual device. Like any software, the CTS may itself contain bugs. The CTS Verifier is included with the Compatibility Test Suite, and is intended to be run by a human operator to test functionality that cannot be tested by an automated system, such as correct functioning of a camera and sensors.

The CTS Verifier has tests for many kinds of hardware, including some hardware that is optional. However, since many builds are very similar, device implementers are not expected to explicitly run the CTS Verifier on builds that differ only in trivial ways. Specifically, device implementations that differ from an implementation that has passed the CTS Verifier only by the set of included locales, branding, etc.

Device implementations MUST include a mechanism to replace the entirety of the system software. Any method can be used, provided that it can replace the entirety of the software preinstalled on the device. For instance, any of the following approaches will satisfy this requirement:.

However, if the device implementation includes support for an unmetered data connection such as The update mechanism used MUST support updates without wiping user data. That is, the update mechanism MUST preserve application private data and application shared data.

Note that the upstream Android software includes an update mechanism that satisfies this requirement. For device implementations that are launching with Android 6.

If an error is found in a device implementation after it has been released but within its reasonable product lifetime that is determined in consultation with the Android Compatibility Team to affect the compatibility of third-party applications, the device implementer MUST correct the error via a software update available that can be applied per the mechanism just described.

Android includes features that allow the Device Owner app if present to control the installation of system updates. To facilitate this, the system update subsystem for devices that report android.

The following table contains a summary of the changes to the Compatibility Definition in this release. You can join the android-compatibility forum [Resources, ] and ask for clarifications or bring up any issues that you think the document does not cover.

Android 6. Unicode 6. Android android. Any technical details provided in the references included above are considered by inclusion to be part of this Compatibility Definition. Introduction 2. Device Types 2. Software 3. Managed API Compatibility 3. Soft API Compatibility 3. Permissions 3. Build Parameters 3. Intent Compatibility 3. Core Application Intents 3. Intent Resolution 3. Intent Namespaces 3. Broadcast Intents 3.

Default App Settings 3. Native API Compatibility 3. Application Binary Interfaces 3. Web Compatibility 3. WebView Compatibility 3. Browser Compatibility 3. API Behavioral Compatibility 3.

Knife-for-wood-cutting-method Build-your-own-photo-frame-number Craftsman-radial-arm-saw-recall-kit-led