Where this definition or the software tests described in - section 10 is silent, ambiguous, or incomplete, it -is the responsibility of the device implementer to ensure compatibility with -existing implementations. To be considered compatible with Android 7.1, device -implementations MUST meet the requirements presented in this Compatibility -Definition, including any documents incorporated via reference. A “device implementation” or “implementation is the -hardware/software solution so developed. As used in this document, a “device implementer” or “implementer” is a person -or organization developing a hardware/software solution running Android -7.1. The use of “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, -“SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” is per the IETF standard -defined in - RFC2119. Introduction - This document enumerates the requirements that must be met in order for devices -to be compatible with Android 7.1. Automotive Vehicle System Isolation - 10. Wi-Fi Tunneled Direct Link Setup - 7.4.3. Android Automotive-only sensors - 7.3.11.1. Legacy Application Compatibility Mode - 7.1.6. Developer Tools and Options Compatibility - 6.1. Musical Instrument Digital Interface (MIDI) - 5.10. Device Administration - 3.9.1 Device Provisioning - 3.9.1.1 Device owner provisioning - 3.9.1.2 Managed profile provisioning - 3.9.2 Managed Profile Support - 3.10. Screen savers (previously Dreams) - 3.8.12. 32-bit ARM Native Code Compatibility - 3.4. Device Types - 2.1 Device Configurations - 3. +++ -1,10702 +1,7077 - Android 7.1 Compatibility Definition - Android 7.1 Compatibility Definition - Table of Contents - 1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |