Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 1 | <!DOCTYPE html> |
| 2 | <head> |
| 3 | <title>Android ANDROID_VERSION Compatibility Definition</title> |
Clay Murphy | b658177 | 2015-08-26 11:11:06 -0700 | [diff] [blame] | 4 | <link rel="stylesheet" type="text/css" href="source/android-cdd.css"/> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 5 | </head> |
| 6 | |
| 7 | <body> |
| 8 | |
| 9 | <h6>Table of Contents</h6> |
| 10 | |
| 11 | <div id="toc"> |
| 12 | |
| 13 | <div id="toc_left"> |
| 14 | |
| 15 | <p class="toc_h1"><a href="#1_introduction">1. Introduction</a></p> |
| 16 | |
| 17 | <p class="toc_h1"><a href="#2_device_types">2. Device Types</a></p> |
| 18 | |
| 19 | <p class="toc_h2"><a href="#2_1_device_configurations">2.1 Device Configurations</a></p> |
| 20 | |
| 21 | <p class="toc_h1"><a href="#3_software">3. Software</a></p> |
| 22 | |
| 23 | <p class="toc_h2"><a href="#3_1_managed_api_compatibility">3.1. Managed API Compatibility</a></p> |
| 24 | |
| 25 | <p class="toc_h2"><a href="#3_2_soft_api_compatibility">3.2. Soft API Compatibility</a></p> |
| 26 | |
| 27 | <p class="toc_h3"><a href="#3_2_1_permissions">3.2.1. Permissions</a></p> |
| 28 | |
| 29 | <p class="toc_h3"><a href="#3_2_2_build_parameters">3.2.2. Build Parameters</a></p> |
| 30 | |
| 31 | <p class="toc_h3"><a href="#3_2_3_intent_compatibility">3.2.3. Intent Compatibility</a></p> |
| 32 | |
| 33 | <p class="toc_h4"><a href="#3_2_3_1_core_application_intents">3.2.3.1. Core Application Intents</a></p> |
| 34 | |
| 35 | <p class="toc_h4"><a href="#3_2_3_2_intent_overrides">3.2.3.2. Intent Overrides</a></p> |
| 36 | |
| 37 | <p class="toc_h4"><a href="#3_2_3_3_intent_namespaces">3.2.3.3. Intent Namespaces</a></p> |
| 38 | |
| 39 | <p class="toc_h4"><a href="#3_2_3_4_broadcast_intents">3.2.3.4. Broadcast Intents</a></p> |
| 40 | |
| 41 | <p class="toc_h4"><a href="#3_2_3_5_default_app_settings">3.2.3.5. Default App Settings</a></p> |
| 42 | |
| 43 | <p class="toc_h2"><a href="#3_3_native_api_compatibility">3.3. Native API Compatibility</a></p> |
| 44 | |
| 45 | <p class="toc_h3"><a href="#3_3_1_application_binary_interfaces">3.3.1. Application Binary Interfaces</a></p> |
| 46 | |
| 47 | <p class="toc_h3"><a href="#3_3_2_32-bit_arm_native_code_compatibility">3.3.2. 32-bit ARM Native Code Compatibility</a></p> |
| 48 | |
| 49 | <p class="toc_h2"><a href="#3_4_web_compatibility">3.4. Web Compatibility</a></p> |
| 50 | |
| 51 | <p class="toc_h3"><a href="#3_4_1_webview_compatibility">3.4.1. WebView Compatibility</a></p> |
| 52 | |
| 53 | <p class="toc_h3"><a href="#3_4_2_browser_compatibility">3.4.2. Browser Compatibility</a></p> |
| 54 | |
| 55 | <p class="toc_h2"><a href="#3_5_api_behavioral_compatibility">3.5. API Behavioral Compatibility</a></p> |
| 56 | |
| 57 | <p class="toc_h2"><a href="#3_6_api_namespaces">3.6. API Namespaces</a></p> |
| 58 | |
| 59 | <p class="toc_h2"><a href="#3_7_runtime_compatibility">3.7. Runtime Compatibility</a></p> |
| 60 | |
| 61 | <p class="toc_h2"><a href="#3_8_user_interface_compatibility">3.8. User Interface Compatibility</a></p> |
| 62 | |
| 63 | <p class="toc_h3"><a href="#3_8_1_launcher_home_screen">3.8.1. Launcher (Home Screen)</a></p> |
| 64 | |
| 65 | <p class="toc_h3"><a href="#3_8_2_widgets">3.8.2. Widgets</a></p> |
| 66 | |
| 67 | <p class="toc_h3"><a href="#3_8_3_notifications">3.8.3. Notifications</a></p> |
| 68 | |
| 69 | <p class="toc_h3"><a href="#3_8_4_search">3.8.4. Search</a></p> |
| 70 | |
| 71 | <p class="toc_h3"><a href="#3_8_5_toasts">3.8.5. Toasts</a></p> |
| 72 | |
| 73 | <p class="toc_h3"><a href="#3_8_6_themes">3.8.6. Themes</a></p> |
| 74 | |
| 75 | <p class="toc_h3"><a href="#3_8_7_live_wallpapers">3.8.7. Live Wallpapers</a></p> |
| 76 | |
| 77 | <p class="toc_h3"><a href="#3_8_8_activity_switching">3.8.8. Activity Switching</a></p> |
| 78 | |
| 79 | <p class="toc_h3"><a href="#3_8_9_input_management">3.8.9. Input Management</a></p> |
| 80 | |
| 81 | <p class="toc_h3"><a href="#3_8_10_lock_screen_media_control">3.8.10. Lock Screen Media Control</a></p> |
| 82 | |
| 83 | <p class="toc_h3"><a href="#3_8_11_dreams">3.8.11. Dreams</a></p> |
| 84 | |
| 85 | <p class="toc_h3"><a href="#3_8_12_location">3.8.12. Location</a></p> |
| 86 | |
| 87 | <p class="toc_h3"><a href="#3_8_13_unicode_and_font">3.8.13. Unicode and Font</a></p> |
| 88 | |
| 89 | |
| 90 | |
| 91 | </div> |
| 92 | |
| 93 | <div id="toc_right"><br> |
| 94 | |
| 95 | |
| 96 | |
| 97 | <p class="toc_h2"><a href="#3_9_device_administration">3.9. Device Administration</a></p> |
| 98 | |
Andy Dyer-smith | 3d24bbe | 2015-09-11 15:35:23 +0100 | [diff] [blame] | 99 | <p class="toc_h3"><a href="#3_9_1_device_provisioning">3.9.1 Device Provisioning</a></p> |
| 100 | |
| 101 | <p class="toc_h4"><a href="#3_9_1_2_device_owner_provisioning">3.9.1.1 Device Owner provisioning</a></p> |
| 102 | |
| 103 | <p class="toc_h4"><a href="#3_9_1_2_managed_profile_provisioning">3.9.1.2 Managed profile provisioning</a></p> |
| 104 | |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 105 | <p class="toc_h2"><a href="#3_10_accessibility">3.10. Accessibility</a></p> |
| 106 | |
| 107 | <p class="toc_h2"><a href="#3_11_text-to-speech">3.11. Text-to-Speech</a></p> |
| 108 | |
| 109 | <p class="toc_h2"><a href="#3_12_tv_input_framework">3.12. TV Input Framework</a></p> |
| 110 | |
| 111 | <p class="toc_h1"><a href="#4_application_packaging_compatibility">4. Application Packaging Compatibility</a></p> |
| 112 | |
| 113 | <p class="toc_h1"><a href="#5_multimedia_compatibility">5. Multimedia Compatibility</a></p> |
| 114 | |
| 115 | <p class="toc_h2"><a href="#5_1_media_codecs">5.1. Media Codecs</a></p> |
| 116 | |
| 117 | <p class="toc_h3"><a href="#5_1_1_audio_codecs">5.1.1. Audio Codecs</a></p> |
| 118 | |
| 119 | <p class="toc_h3"><a href="#5_1_2_image_codecs">5.1.2. Image Codecs</a></p> |
| 120 | |
| 121 | <p class="toc_h3"><a href="#5_1_3_video_codecs">5.1.3. Video Codecs</a></p> |
| 122 | |
| 123 | <p class="toc_h2"><a href="#5_2_video_encoding">5.2. Video Encoding</a></p> |
| 124 | |
| 125 | <p class="toc_h2"><a href="#5_3_video_decoding">5.3. Video Decoding</a></p> |
| 126 | |
| 127 | <p class="toc_h2"><a href="#5_4_audio_recording">5.4. Audio Recording</a></p> |
| 128 | |
| 129 | <p class="toc_h3"><a href="#5_4_1_raw_audio_capture">5.4.1. Raw Audio Capture</a></p> |
| 130 | |
| 131 | <p class="toc_h3"><a href="#5_4_2_capture_for_voice_recognition">5.4.2. Capture for Voice Recognition</a></p> |
| 132 | |
| 133 | <p class="toc_h3"><a href="#5_4_3_capture_for_rerouting_of_playback">5.4.3. Capture for Rerouting of Playback</a></p> |
| 134 | |
| 135 | <p class="toc_h2"><a href="#5_5_audio_playback">5.5. Audio Playback</a></p> |
| 136 | |
| 137 | <p class="toc_h3"><a href="#5_5_1_raw_audio_playback">5.5.1. Raw Audio Playback</a></p> |
| 138 | |
| 139 | <p class="toc_h3"><a href="#5_5_2_audio_effects">5.5.2. Audio Effects</a></p> |
| 140 | |
| 141 | <p class="toc_h3"><a href="#5_5_3_audio_output_volume">5.5.3. Audio Output Volume</a></p> |
| 142 | |
| 143 | <p class="toc_h2"><a href="#5_6_audio_latency">5.6. Audio Latency</a></p> |
| 144 | |
| 145 | <p class="toc_h2"><a href="#5_7_network_protocols">5.7. Network Protocols</a></p> |
| 146 | |
| 147 | <p class="toc_h2"><a href="#5_8_secure_media">5.8. Secure Media</a></p> |
| 148 | |
Glenn Kasten | 87ef61d | 2015-07-29 09:01:36 -0700 | [diff] [blame] | 149 | <p class="toc_h2"><a href="#5_9_midi">5.9. Musical Instrument Digital Interface (MIDI)</a></p> |
| 150 | |
Glenn Kasten | 78eccbd | 2015-08-12 10:18:22 -0700 | [diff] [blame] | 151 | <p class="toc_h2"><a href="#5_10_pro_audio">5.10. Professional Audio</a></p> |
| 152 | |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 153 | <p class="toc_h1"><a href="#6_developer_tools_and_options_compatibility">6. Developer Tools and Options Compatibility</a></p> |
| 154 | |
| 155 | <p class="toc_h2"><a href="#6_1_developer_tools">6.1. Developer Tools</a></p> |
| 156 | |
| 157 | <p class="toc_h2"><a href="#6_2_developer_options">6.2. Developer Options</a></p> |
| 158 | |
| 159 | <p class="toc_h1"><a href="#7_hardware_compatibility">7. Hardware Compatibility</a></p> |
| 160 | |
| 161 | <p class="toc_h2"><a href="#7_1_display_and_graphics">7.1. Display and Graphics</a></p> |
| 162 | |
| 163 | <p class="toc_h3"><a href="#7_1_1_screen_configuration">7.1.1. Screen Configuration</a></p> |
| 164 | |
| 165 | <p class="toc_h4"><a href="#7_1_1_1_screen_size">7.1.1.1. Screen Size</a></p> |
| 166 | |
| 167 | <p class="toc_h4"><a href="#7_1_1_2_screen_aspect_ratio">7.1.1.2. Screen Aspect Ratio</a></p> |
| 168 | |
| 169 | <p class="toc_h4"><a href="#7_1_1_3_screen_density">7.1.1.3. Screen Density</a></p> |
| 170 | |
| 171 | |
| 172 | </div> |
| 173 | |
| 174 | <div style="clear: both; page-break-after:always; height:1px"></div> |
| 175 | |
| 176 | |
| 177 | <div id="toc_left_2"> |
| 178 | |
| 179 | <p class="toc_h3"><a href="#7_1_2_display_metrics">7.1.2. Display Metrics</a></p> |
| 180 | |
| 181 | <p class="toc_h3"><a href="#7_1_3_screen_orientation">7.1.3. Screen Orientation</a></p> |
| 182 | |
| 183 | <p class="toc_h3"><a href="#7_1_4_2d_and_3d_graphics_acceleration">7.1.4. 2D and 3D Graphics Acceleration</a></p> |
| 184 | |
| 185 | <p class="toc_h3"><a href="#7_1_5_legacy_application_compatibility_mode">7.1.5. Legacy Application Compatibility Mode</a></p> |
| 186 | |
| 187 | <p class="toc_h3"><a href="#7_1_6_screen_technology">7.1.6. Screen Technology</a></p> |
| 188 | |
| 189 | <p class="toc_h3"><a href="#7_1_7_external_displays">7.1.7. Secondary Displays</a></p> |
| 190 | |
| 191 | <p class="toc_h2"><a href="#7_2_input_devices">7.2. Input Devices</a></p> |
| 192 | |
| 193 | <p class="toc_h3"><a href="#7_2_1_keyboard">7.2.1. Keyboard</a></p> |
| 194 | |
| 195 | <p class="toc_h3"><a href="#7_2_2_non-touch_navigation">7.2.2. Non-touch Navigation</a></p> |
| 196 | |
| 197 | <p class="toc_h3"><a href="#7_2_3_navigation_keys">7.2.3. Navigation Keys</a></p> |
| 198 | |
| 199 | <p class="toc_h3"><a href="#7_2_4_touchscreen_input">7.2.4. Touchscreen Input</a></p> |
| 200 | |
| 201 | <p class="toc_h3"><a href="#7_2_5_fake_touch_input">7.2.5. Fake Touch Input</a></p> |
| 202 | |
| 203 | <p class="toc_h3"><a href="#7_2_6_game_controller_support">7.2.6. Game Controller Support</a></p> |
| 204 | |
| 205 | <p class="toc_h4"><a href="#7_2_6_1_button_mapping">7.2.6.1. Button Mappings</a></p> |
| 206 | |
| 207 | <p class="toc_h3"><a href="#7_2_7_remote_control">7.2.7. Remote Control</a></p> |
| 208 | |
| 209 | <p class="toc_h2"><a href="#7_3_sensors">7.3. Sensors</a></p> |
| 210 | |
| 211 | <p class="toc_h3"><a href="#7_3_1_accelerometer">7.3.1. Accelerometer</a></p> |
| 212 | |
| 213 | <p class="toc_h3"><a href="#7_3_2_magnetometer">7.3.2. Magnetometer</a></p> |
| 214 | |
| 215 | <p class="toc_h3"><a href="#7_3_3_gps">7.3.3. GPS</a></p> |
| 216 | |
| 217 | <p class="toc_h3"><a href="#7_3_4_gyroscope">7.3.4. Gyroscope</a></p> |
| 218 | |
| 219 | <p class="toc_h3"><a href="#7_3_5_barometer">7.3.5. Barometer</a></p> |
| 220 | |
| 221 | <p class="toc_h3"><a href="#7_3_6_thermometer">7.3.6. Thermometer</a></p> |
| 222 | |
| 223 | <p class="toc_h3"><a href="#7_3_7_photometer">7.3.7. Photometer</a></p> |
| 224 | |
| 225 | <p class="toc_h3"><a href="#7_3_8_proximity_sensor">7.3.8. Proximity Sensor</a></p> |
| 226 | |
| 227 | <p class="toc_h2"><a href="#7_4_data_connectivity">7.4. Data Connectivity</a></p> |
| 228 | |
| 229 | <p class="toc_h3"><a href="#7_4_1_telephony">7.4.1. Telephony</a></p> |
| 230 | |
| 231 | <p class="toc_h3"><a href="#7_4_2_ieee_80211_wi-fi">7.4.2. IEEE 802.11 (Wi-Fi)</a></p> |
| 232 | |
| 233 | <p class="toc_h4"><a href="#7_4_2_1_wi-fi_direct">7.4.2.1. Wi-Fi Direct</a></p> |
| 234 | |
| 235 | <p class="toc_h4"><a href="#7_4_2_2_wi-fi-tunneled-direct-link-setup">7.4.2.2. Wi-Fi Tunneled Direct Link Setup</a></p> |
| 236 | |
| 237 | <p class="toc_h3"><a href="#7_4_3_bluetooth">7.4.3. Bluetooth</a></p> |
| 238 | |
| 239 | <p class="toc_h3"><a href="#7_4_4_near-field_communications">7.4.4. Near-Field Communications</a></p> |
| 240 | |
| 241 | <p class="toc_h3"><a href="#7_4_5_minimum_network_capability">7.4.5. Minimum Network Capability</a></p> |
| 242 | |
| 243 | <p class="toc_h3"><a href="#7_4_6_sync_settings">7.4.6. Sync Settings</a></p> |
| 244 | |
| 245 | <p class="toc_h2"><a href="#7_5_cameras">7.5. Cameras</a></p> |
| 246 | |
| 247 | <p class="toc_h3"><a href="#7_5_1_rear-facing_camera">7.5.1. Rear-Facing Camera</a></p> |
| 248 | |
| 249 | <p class="toc_h3"><a href="#7_5_2_front-facing_camera">7.5.2. Front-Facing Camera</a></p> |
| 250 | |
| 251 | <p class="toc_h3"><a href="#7_5_3_external_camera">7.5.3. External Camera</a></p> |
| 252 | |
| 253 | <p class="toc_h3"><a href="#7_5_4_camera_api_behavior">7.5.4. Camera API Behavior</a></p> |
| 254 | |
| 255 | |
| 256 | |
| 257 | |
| 258 | |
| 259 | </div> |
| 260 | |
| 261 | <div id="toc_right_2"> |
| 262 | |
| 263 | <p class="toc_h3"><a href="#7_5_5_camera_orientation">7.5.5. Camera Orientation</a></p> |
| 264 | |
| 265 | <p class="toc_h2"><a href="#7_6_memory_and_storage">7.6. Memory and Storage</a></p> |
| 266 | |
| 267 | <p class="toc_h3"><a href="#7_6_1_minimum_memory_and_storage">7.6.1. Minimum Memory and Storage</a></p> |
| 268 | |
| 269 | <p class="toc_h3"><a href="#7_6_2_application_shared_storage">7.6.2. Application Shared Storage</a></p> |
| 270 | |
| 271 | <p class="toc_h2"><a href="#7_7_usb">7.7. USB</a></p> |
| 272 | |
| 273 | <p class="toc_h2"><a href="#7_8_audio">7.8. Audio</a></p> |
| 274 | |
| 275 | <p class="toc_h3"><a href="#7_8_1_microphone">7.8.1. Microphone</a></p> |
| 276 | |
| 277 | <p class="toc_h3"><a href="#7_8_2_audio_output">7.8.2. Audio Output</a></p> |
| 278 | |
| 279 | <p class="toc_h4"><a href="#7_8_2_1_analog_audio_ports">7.8.2.1. Analog Audio Ports</a></p> |
| 280 | |
Glenn Kasten | 20cdbb7 | 2015-09-24 11:56:42 -0700 | [diff] [blame^] | 281 | <p class="toc_h3"><a href="#7_8_3_near_ultrasound">7.8.3. Near-Ultrasound</a></p> |
| 282 | |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 283 | <p class="toc_h1"><a href="#8_performance_compatibility">8. Performance Compatibility</a></p> |
| 284 | |
| 285 | <p class="toc_h2"><a href="#8_1_user_experience_consistency">8.1. User Experience Consistency</a></p> |
| 286 | |
| 287 | <p class="toc_h2"><a href="#8_2_memory_performance">8.2. Memory Performance</a></p> |
| 288 | |
| 289 | <p class="toc_h1"><a href="#9_security_model_compatibility">9. Security Model Compatibility</a></p> |
| 290 | |
| 291 | <p class="toc_h2"><a href="#9_1_permissions">9.1. Permissions</a></p> |
| 292 | |
| 293 | <p class="toc_h2"><a href="#9_2_uid_and_process_isolation">9.2. UID and Process Isolation</a></p> |
| 294 | |
| 295 | <p class="toc_h2"><a href="#9_3_filesystem_permissions">9.3. Filesystem Permissions</a></p> |
| 296 | |
| 297 | <p class="toc_h2"><a href="#9_4_alternate_execution_environments">9.4. Alternate Execution Environments</a></p> |
| 298 | |
| 299 | <p class="toc_h2"><a href="#9_5_multi-user_support">9.5. Multi-User Support</a></p> |
| 300 | |
| 301 | <p class="toc_h2"><a href="#9_6_premium_sms_warning">9.6. Premium SMS Warning</a></p> |
| 302 | |
| 303 | <p class="toc_h2"><a href="#9_7_kernel_security_features">9.7. Kernel Security Features</a></p> |
| 304 | |
| 305 | <p class="toc_h2"><a href="#9_8_privacy">9.8. Privacy</a></p> |
| 306 | |
| 307 | <p class="toc_h2"><a href="#9_9_full-disk-encryption">9.9. Full-Disk Encryption</a></p> |
| 308 | |
| 309 | <p class="toc_h2"><a href="#9_10_verified_boot">9.10. Verified Boot</a></p> |
| 310 | |
| 311 | <p class="toc_h1"><a href="#10_software_compatibility_testing">10. Software Compatibility Testing</a></p> |
| 312 | |
| 313 | <p class="toc_h2"><a href="#10_1_compatibility_test_suite">10.1. Compatibility Test Suite</a></p> |
| 314 | |
| 315 | <p class="toc_h2"><a href="#10_2_cts_verifier">10.2. CTS Verifier</a></p> |
| 316 | |
| 317 | <p class="toc_h1"><a href="#11_updatable_software">11. Updatable Software</a></p> |
| 318 | |
| 319 | <p class="toc_h1"><a href="#12_document_changelog">12. Document Changelog</a></p> |
| 320 | |
| 321 | <p class="toc_h1"><a href="#13_contact_us">13. Contact Us</a></p> |
| 322 | |
| 323 | <p class="toc_h1"><a href="#14_resources">14. Resources</a></p> |
| 324 | |
| 325 | </div> |
| 326 | |
| 327 | </div> |
| 328 | |
| 329 | <div style="clear: both"></div> |
| 330 | |
| 331 | <div id="main"> |
| 332 | |
| 333 | <h1 id="1_introduction">1. Introduction</h1> |
| 334 | |
| 335 | |
| 336 | <p>This document enumerates the requirements that must be met in order for devices |
| 337 | to be compatible with Android ANDROID_VERSION.</p> |
| 338 | |
| 339 | <p>The use of “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”,“SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” is per the IETF standard |
| 340 | defined in RFC2119 [<a href="http://www.ietf.org/rfc/rfc2119.txt">Resources, 1</a>].</p> |
| 341 | |
| 342 | <p>As used in this document, a “device implementer” or “implementer” is a person |
| 343 | or organization developing a hardware/software solution running Android ANDROID_VERSION. A |
| 344 | “device implementation” or “implementation is the hardware/software solution |
| 345 | so developed.</p> |
| 346 | |
| 347 | <p>To be considered compatible with Android ANDROID_VERSION, device implementations MUST meet |
| 348 | the requirements presented in this Compatibility Definition, including any |
| 349 | documents incorporated via reference.</p> |
| 350 | |
| 351 | <p>Where this definition or the software tests described in <a href="#10_software_compatibility_testing">section 10</a> is silent, ambiguous, or incomplete, it is the responsibility of the device |
| 352 | implementer to ensure compatibility with existing implementations.</p> |
| 353 | |
| 354 | <p>For this reason, the Android Open Source Project [<a href="http://source.android.com/">Resources, 2</a>] is both the reference and preferred implementation of Android. Device |
Bert McMeen | 816a242 | 2015-09-29 16:33:19 -0700 | [diff] [blame] | 355 | implementers are STRONGLY RECOMMENDED to base their implementations to the |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 356 | greatest extent possible on the “upstream” source code available from the |
| 357 | Android Open Source Project. While some components can hypothetically be |
| 358 | replaced with alternate implementations this practice is strongly discouraged, |
| 359 | as passing the software tests will become substantially more difficult. It is |
| 360 | the implementer’s responsibility to ensure full behavioral compatibility with |
| 361 | the standard Android implementation, including and beyond the Compatibility |
| 362 | Test Suite. Finally, note that certain component substitutions and |
| 363 | modifications are explicitly forbidden by this document.</p> |
| 364 | |
| 365 | <p>Many of the resources listed in <a href="#14_resources">section 14</a> are derived directly or indirectly from the Android SDK, and will be |
| 366 | functionally identical to the information in that SDK’s documentation. For any |
| 367 | case where this Compatibility Definition or the Compatibility Test Suite |
| 368 | disagrees with the SDK documentation, the SDK documentation is considered |
| 369 | authoritative. Any technical details provided in the references included in <a href="#14_resources">section 14</a> are considered by inclusion to be part of this Compatibility Definition. </p> |
| 370 | |
| 371 | <h1 id="2_device_types">2. Device Types</h1> |
| 372 | |
| 373 | |
| 374 | <p>While the Android Open Source Project has been used in the implementation of a |
| 375 | variety of device types and form factors, many aspects of the architecture and |
| 376 | compatibility requirements were optimized for handheld devices. Starting from |
| 377 | Android 5.0, the Android Open Source Project aims to embrace a wider variety of |
| 378 | device types as described in this section.</p> |
| 379 | |
| 380 | <p><strong>Android Handheld device</strong> refers to an Android device implementation that is typically used by holding |
| 381 | it in the hand, such as mp3 players, phones, and tablets. Android Handheld |
| 382 | device implementations:</p> |
| 383 | |
| 384 | <ul> |
| 385 | <li>MUST have a touchscreen embedded in the device.</li> |
| 386 | <li>MUST have a power source that provides mobility, such as a battery.</li> |
| 387 | </ul> |
| 388 | |
| 389 | <p><strong>Android Television device</strong> refers to an Android device implementation that is an entertainment interface |
| 390 | for consuming digital media, movies, games, apps, and/or live TV for users |
| 391 | sitting about ten feet away (a “lean back” or “10-foot user interface”). |
| 392 | Android Television devices:</p> |
| 393 | |
| 394 | <ul> |
| 395 | <li>MUST have an embedded screen OR include a video output port, such as VGA, HDMI, |
| 396 | or a wireless port for display.</li> |
| 397 | <li>MUST declare the features android.software.leanback and |
| 398 | android.hardware.type.television [<a href="http://developer.android.com/reference/android/content/pm/PackageManager.html#FEATURE_LEANBACK">Resources, 3</a>].</li> |
| 399 | </ul> |
| 400 | |
| 401 | <p><strong>Android Watch device</strong> refers to an Android device implementation intended to be worn on the body, |
| 402 | perhaps on the wrist, and:</p> |
| 403 | |
| 404 | <ul> |
| 405 | <li>MUST have a screen with the physical diagonal length in the range from 1.1 to |
| 406 | 2.5 inches.</li> |
| 407 | <li>MUST declare the feature android.hardware.type.watch.</li> |
| 408 | <li>MUST support uiMode = UI_MODE_TYPE_WATCH [<a href="http://developer.android.com/reference/android/content/res/Configuration.html#UI_MODE_TYPE_WATCH">Resources, 4</a>].</li> |
| 409 | </ul> |
| 410 | |
| 411 | <p><strong>Android Automotive implementation</strong> refers to a vehicle head |
| 412 | unit running Android as an operating system for part or all of the system and/or |
| 413 | infotainment functionality. Android Automotive implementations MUST support |
| 414 | uiMode = UI_MODE_TYPE_CAR [<a href="http://developer.android.com/reference/android/content/res/Configuration.html#UI_MODE_TYPE_CAR">Resources, 111</a>].</p> |
| 415 | |
| 416 | <p>All Android device implementations that do not fit into any of the above device |
| 417 | types still MUST meet all requirements in this document to be Android ANDROID_VERSION |
| 418 | compatible, unless the requirement is explicitly described to be only |
| 419 | applicable to a specific Android device type from above.</p> |
| 420 | |
| 421 | <h2 id="2_1_device_configurations">2.1 Device Configurations</h2> |
| 422 | |
| 423 | |
| 424 | <p>This is a summary of major differences in hardware configuration by device |
| 425 | type. (Empty cells denote a “MAY”). Not all configurations are covered in this |
| 426 | table; see relevant hardware sections for more detail.</p> |
| 427 | <table> |
| 428 | <tr> |
| 429 | <th>Category</th> |
| 430 | <th>Feature</th> |
| 431 | <th>Section</th> |
| 432 | <th>Handheld</th> |
| 433 | <th>Television</th> |
| 434 | <th>Watch</th> |
| 435 | <th>Automotive</th> |
| 436 | <th>Other</th> |
| 437 | </tr> |
| 438 | <tr> |
| 439 | <td rowspan="3">Input</td> |
| 440 | <td>D-pad</td> |
| 441 | <td><a href="#7_2_2_non-touch-navigation">7.2.2. Non-touch Navigation</a></td> |
| 442 | <td></td> |
| 443 | <td>MUST</td> |
| 444 | <td></td> |
| 445 | <td></td> |
| 446 | <td></td> |
| 447 | </tr> |
| 448 | <tr> |
| 449 | <td>Touchscreen </td> |
| 450 | <td><a href="#7_2_4_touchscreen_input">7.2.4. Touchscreen input</a></td> |
| 451 | <td>MUST</td> |
| 452 | <td></td> |
| 453 | <td>MUST</td> |
| 454 | <td></td> |
| 455 | <td>SHOULD</td> |
| 456 | </tr> |
| 457 | <tr> |
| 458 | <td>Microphone </td> |
| 459 | <td><a href="#7_8_1_microphone">7.8.1. Microphone</a></td> |
| 460 | <td>MUST</td> |
| 461 | <td>SHOULD </td> |
| 462 | <td>MUST</td> |
| 463 | <td>MUST</td> |
| 464 | <td>SHOULD</td> |
| 465 | </tr> |
| 466 | <tr> |
| 467 | <td rowspan="2">Sensors</td> |
| 468 | <td>Accelerometer </td> |
| 469 | <td><a href="#7_3_1_accelerometer">7.3.1 Accelerometer</a></td> |
| 470 | <td>SHOULD</td> |
| 471 | <td></td> |
| 472 | <td>SHOULD</td> |
| 473 | <td></td> |
| 474 | <td>SHOULD</td> |
| 475 | </tr> |
| 476 | <tr> |
| 477 | <td>GPS</td> |
| 478 | <td><a href="#7_3_3_gps">7.3.3. GPS</a></td> |
| 479 | <td>SHOULD</td> |
| 480 | <td></td> |
| 481 | <td></td> |
| 482 | <td>SHOULD</td> |
| 483 | <td></td> |
| 484 | </tr> |
| 485 | <tr> |
| 486 | <td rowspan="5">Connectivity</td> |
| 487 | <td>Wi-Fi</td> |
| 488 | <td><a href="#7_4_2_ieee_802.11">7.4.2. IEEE 802.11</a></td> |
| 489 | <td>SHOULD</td> |
| 490 | <td> MUST</td> |
| 491 | <td></td> |
| 492 | <td>SHOULD</td> |
| 493 | <td>SHOULD</td> |
| 494 | </tr> |
| 495 | <tr> |
| 496 | <td>Wi-Fi Direct</td> |
| 497 | <td><a href="#7_4_2_1_wi-fi-direct">7.4.2.1. Wi-Fi Direct</a></td> |
| 498 | <td>SHOULD</td> |
| 499 | <td>SHOULD</td> |
| 500 | <td></td> |
| 501 | <td></td> |
| 502 | <td>SHOULD</td> |
| 503 | </tr> |
| 504 | <tr> |
| 505 | <td>Bluetooth</td> |
| 506 | <td><a href="#7_4_3_bluetooth">7.4.3. Bluetooth</a></td> |
| 507 | <td>SHOULD</td> |
| 508 | <td>MUST</td> |
| 509 | <td>MUST</td> |
| 510 | <td>MUST</td> |
| 511 | <td>SHOULD</td> |
| 512 | </tr> |
| 513 | <tr> |
| 514 | <td>Bluetooth Low Energy</td> |
| 515 | <td><a href="#7_4_3_bluetooth">7.4.3. Bluetooth</a></td> |
| 516 | <td>SHOULD</td> |
| 517 | <td>MUST</td> |
| 518 | <td>SHOULD</td> |
| 519 | <td>SHOULD</td> |
| 520 | <td>SHOULD</td> |
| 521 | </tr> |
| 522 | <tr> |
| 523 | <td>USB peripheral/host mode</td> |
| 524 | <td><a href="#7_7_usb">7.7. USB</a></td> |
| 525 | <td>SHOULD</td> |
| 526 | <td></td> |
| 527 | <td></td> |
| 528 | <td>SHOULD</td> |
| 529 | <td>SHOULD</td> |
| 530 | </tr> |
| 531 | <tr> |
| 532 | <td>Output</td> |
| 533 | <td>Speaker and/or Audio output ports</td> |
| 534 | <td><a href="#7_8_2_audio_output">7.8.2. Audio Output</a></td> |
| 535 | <td>MUST</td> |
| 536 | <td>MUST</td> |
| 537 | <td></td> |
| 538 | <td>MUST</td> |
| 539 | <td>MUST</td> |
| 540 | </tr> |
| 541 | </table> |
| 542 | |
| 543 | |
| 544 | <h1 id="3_software">3. Software</h1> |
| 545 | |
| 546 | |
| 547 | <h2 id="3_1_managed_api_compatibility">3.1. Managed API Compatibility</h2> |
| 548 | |
| 549 | |
| 550 | <p>The managed Dalvik bytecode execution environment is the primary vehicle for |
| 551 | Android applications. The Android application programming interface (API) is |
| 552 | the set of Android platform interfaces exposed to applications running in the |
| 553 | managed runtime environment. Device implementations MUST provide complete |
| 554 | implementations, including all documented behaviors, of any documented API |
| 555 | exposed by the Android SDK [<a href="http://developer.android.com/reference/packages.html">Resources, 5</a>] or any API decorated with the “@SystemApi” marker in the upstream Android |
| 556 | source code. </p> |
| 557 | |
| 558 | <p>Device implementations MUST NOT omit any managed APIs, alter API interfaces or |
| 559 | signatures, deviate from the documented behavior, or include no-ops, except |
| 560 | where specifically allowed by this Compatibility Definition.</p> |
| 561 | |
| 562 | <p>This Compatibility Definition permits some types of hardware for which Android |
| 563 | includes APIs to be omitted by device implementations. In such cases, the APIs |
| 564 | MUST still be present and behave in a reasonable way. See <a href="#7_hardware_compatibility">section 7</a> for specific requirements for this scenario.</p> |
| 565 | |
| 566 | <h2 id="3_2_soft_api_compatibility">3.2. Soft API Compatibility</h2> |
| 567 | |
| 568 | |
| 569 | <p>In addition to the managed APIs from <a href="#3_1_managed_api_compatibility">section 3.1</a>, Android also includes a significant runtime-only “soft” API, in the form of |
| 570 | such things as intents, permissions, and similar aspects of Android |
| 571 | applications that cannot be enforced at application compile time.</p> |
| 572 | |
| 573 | <h3 id="3_2_1_permissions">3.2.1. Permissions</h3> |
| 574 | |
| 575 | |
| 576 | <p>Device implementers MUST support and enforce all permission constants as |
| 577 | documented by the Permission reference page [<a href="http://developer.android.com/reference/android/Manifest.permission.html">Resources, 6]</a>. Note that <a href="#9_security_model_compatibility">section 9</a> lists additional requirements related to the Android security model.</p> |
| 578 | |
| 579 | <h3 id="3_2_2_build_parameters">3.2.2. Build Parameters</h3> |
| 580 | |
| 581 | |
| 582 | <p>The Android APIs include a number of constants on the android.os.Build class [<a href="http://developer.android.com/reference/android/os/Build.html">Resources, 7</a>] that are intended to describe the current device. To provide consistent, |
| 583 | meaningful values across device implementations, the table below includes |
| 584 | additional restrictions on the formats of these values to which device |
| 585 | implementations MUST conform.</p> |
| 586 | <table> |
| 587 | <tr> |
| 588 | <th>Parameter</th> |
| 589 | <th>Details</th> |
| 590 | </tr> |
| 591 | <tr> |
| 592 | <td>VERSION.RELEASE</td> |
| 593 | <td>The version of the currently-executing Android system, in human-readable |
| 594 | format. This field MUST have one of the string values defined in [<a href="http://source.android.com/compatibility/ANDROID_VERSION/versions.html">Resources, 8]</a>.</td> |
| 595 | </tr> |
| 596 | <tr> |
| 597 | <td>VERSION.SDK</td> |
| 598 | <td>The version of the currently-executing Android system, in a format accessible |
| 599 | to third-party application code. For Android ANDROID_VERSION, this field MUST have the |
Unsuk Jung | 8bebb3e | 2015-09-29 22:10:23 -0700 | [diff] [blame] | 600 | integer value ANDROID_VERSION_INT.</td> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 601 | </tr> |
| 602 | <tr> |
| 603 | <td>VERSION.SDK_INT</td> |
| 604 | <td>The version of the currently-executing Android system, in a format accessible |
| 605 | to third-party application code. For Android ANDROID_VERSION, this field MUST have the |
Unsuk Jung | 8bebb3e | 2015-09-29 22:10:23 -0700 | [diff] [blame] | 606 | integer value ANDROID_VERSION_INT.</td> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 607 | </tr> |
| 608 | <tr> |
| 609 | <td>VERSION.INCREMENTAL</td> |
| 610 | <td>A value chosen by the device implementer designating the specific build of the |
| 611 | currently-executing Android system, in human-readable format. This value MUST |
| 612 | NOT be reused for different builds made available to end users. A typical use |
| 613 | of this field is to indicate which build number or source-control change |
| 614 | identifier was used to generate the build. There are no requirements on the |
| 615 | specific format of this field, except that it MUST NOT be null or the empty |
| 616 | string ("").</td> |
| 617 | </tr> |
| 618 | <tr> |
| 619 | <td>BOARD</td> |
| 620 | <td>A value chosen by the device implementer identifying the specific internal |
| 621 | hardware used by the device, in human-readable format. A possible use of this |
| 622 | field is to indicate the specific revision of the board powering the device. |
| 623 | The value of this field MUST be encodable as 7-bit ASCII and match the regular |
| 624 | expression “^[a-zA-Z0-9_-]+$”.</td> |
| 625 | </tr> |
| 626 | <tr> |
| 627 | <td>BRAND</td> |
| 628 | <td>A value reflecting the brand name associated with the device as known to the |
| 629 | end users. MUST be in human-readable format and SHOULD represent the |
| 630 | manufacturer of the device or the company brand under which the device is |
| 631 | marketed. The value of this field MUST be encodable as 7-bit ASCII and match |
| 632 | the regular expression “^[a-zA-Z0-9_-]+$”.</td> |
| 633 | </tr> |
| 634 | <tr> |
| 635 | <td>SUPPORTED_ABIS</td> |
| 636 | <td>The name of the instruction set (CPU type + ABI convention) of native code. See <a href="#3_3_native_api_compatibility">section 3.3. Native API Compatibility</a>.</td> |
| 637 | </tr> |
| 638 | <tr> |
| 639 | <td>SUPPORTED_32_BIT_ABIS</td> |
| 640 | <td>The name of the instruction set (CPU type + ABI convention) of native code. See <a href="#3_3_native_api_compatibility">section 3.3. Native API Compatibility</a>.</td> |
| 641 | </tr> |
| 642 | <tr> |
| 643 | <td>SUPPORTED_64_BIT_ABIS</td> |
| 644 | <td>The name of the second instruction set (CPU type + ABI convention) of native |
| 645 | code. See <a href="#3_3_native_api_compatibility">section 3.3. Native API Compatibility</a>.</td> |
| 646 | </tr> |
| 647 | <tr> |
| 648 | <td>CPU_ABI</td> |
| 649 | <td>The name of the instruction set (CPU type + ABI convention) of native code. See <a href="#3_3_native_api_compatibility">section 3.3. Native API Compatibility</a>.</td> |
| 650 | </tr> |
| 651 | <tr> |
| 652 | <td>CPU_ABI2</td> |
| 653 | <td>The name of the second instruction set (CPU type + ABI convention) of native |
| 654 | code. See <a href="#3_3_native_api_compatibility">section 3.3. Native API Compatibility</a>.</td> |
| 655 | </tr> |
| 656 | <tr> |
| 657 | <td>DEVICE</td> |
| 658 | <td>A value chosen by the device implementer containing the development name or |
| 659 | code name identifying the configuration of the hardware features and industrial |
| 660 | design of the device. The value of this field MUST be encodable as 7-bit ASCII |
| 661 | and match the regular expression “^[a-zA-Z0-9_-]+$”.</td> |
| 662 | </tr> |
| 663 | <tr> |
| 664 | <td>FINGERPRINT</td> |
| 665 | <td>A string that uniquely identifies this build. It SHOULD be reasonably |
| 666 | human-readable. It MUST follow this template:</p> |
| 667 | |
| 668 | <p class="small">$(BRAND)/$(PRODUCT)/$(DEVICE):$(VERSION.RELEASE)/$(ID)/$(VERSION.INCREMENTAL):$(TYPE)/$(TAGS)</p> |
| 669 | |
| 670 | <p>For example: acme/myproduct/mydevice:ANDROID_VERSION/LMYXX/3359:userdebug/test-keys</p> |
| 671 | |
| 672 | <p>The fingerprint MUST NOT include whitespace characters. If other fields |
| 673 | included in the template above have whitespace characters, they MUST be |
| 674 | replaced in the build fingerprint with another character, such as the |
| 675 | underscore ("_") character. The value of this field MUST be encodable as 7-bit |
| 676 | ASCII.</td> |
| 677 | </tr> |
| 678 | <tr> |
| 679 | <td>HARDWARE</td> |
| 680 | <td>The name of the hardware (from the kernel command line or /proc). It SHOULD be |
| 681 | reasonably human-readable. The value of this field MUST be encodable as 7-bit |
| 682 | ASCII and match the regular expression “^[a-zA-Z0-9_-]+$”. </td> |
| 683 | </tr> |
| 684 | <tr> |
| 685 | <td>HOST</td> |
| 686 | <td>A string that uniquely identifies the host the build was built on, in |
| 687 | human-readable format. There are no requirements on the specific format of this |
| 688 | field, except that it MUST NOT be null or the empty string ("").</td> |
| 689 | </tr> |
| 690 | <tr> |
| 691 | <td>ID</td> |
| 692 | <td>An identifier chosen by the device implementer to refer to a specific release, |
| 693 | in human-readable format. This field can be the same as |
| 694 | android.os.Build.VERSION.INCREMENTAL, but SHOULD be a value sufficiently |
| 695 | meaningful for end users to distinguish between software builds. The value of |
| 696 | this field MUST be encodable as 7-bit ASCII and match the regular expression “^[a-zA-Z0-9._-]+$”.</td> |
| 697 | </tr> |
| 698 | <tr> |
| 699 | <td>MANUFACTURER</td> |
| 700 | <td>The trade name of the Original Equipment Manufacturer (OEM) of the product. |
| 701 | There are no requirements on the specific format of this field, except that it |
| 702 | MUST NOT be null or the empty string ("").</td> |
| 703 | </tr> |
| 704 | <tr> |
| 705 | <td>MODEL</td> |
| 706 | <td>A value chosen by the device implementer containing the name of the device as |
| 707 | known to the end user. This SHOULD be the same name under which the device is |
| 708 | marketed and sold to end users. There are no requirements on the specific |
| 709 | format of this field, except that it MUST NOT be null or the empty string ("").</td> |
| 710 | </tr> |
| 711 | <tr> |
| 712 | <td>PRODUCT</td> |
| 713 | <td>A value chosen by the device implementer containing the development name or |
| 714 | code name of the specific product (SKU) that MUST be unique within the same |
| 715 | brand. MUST be human-readable, but is not necessarily intended for view by end |
| 716 | users. The value of this field MUST be encodable as 7-bit ASCII and match the |
| 717 | regular expression “^[a-zA-Z0-9_-]+$”.</td> |
| 718 | </tr> |
| 719 | <tr> |
| 720 | <td>SERIAL</td> |
Owain Davies | 4f8796e | 2015-09-24 14:01:26 +0100 | [diff] [blame] | 721 | <td>A hardware serial number, which MUST be available and unique across |
| 722 | devices with the same MODEL and MANUFACTURER. The value of this field MUST |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 723 | be encodable as 7-bit ASCII and match the regular expression “^([a-zA-Z0-9]{6,20})$”.</td> |
| 724 | </tr> |
| 725 | <tr> |
| 726 | <td>TAGS</td> |
| 727 | <td>A comma-separated list of tags chosen by the device implementer that further |
| 728 | distinguishes the build. This field MUST have one of the values corresponding |
| 729 | to the three typical Android platform signing configurations: release-keys, |
| 730 | dev-keys, test-keys. </td> |
| 731 | </tr> |
| 732 | <tr> |
| 733 | <td>TIME</td> |
| 734 | <td>A value representing the timestamp of when the build occurred.</td> |
| 735 | </tr> |
| 736 | <tr> |
| 737 | <td>TYPE</td> |
| 738 | <td>A value chosen by the device implementer specifying the runtime configuration |
| 739 | of the build. This field MUST have one of the values corresponding to the three |
| 740 | typical Android runtime configurations: user, userdebug, or eng.</td> |
| 741 | </tr> |
| 742 | <tr> |
| 743 | <td>USER</td> |
| 744 | <td>A name or user ID of the user (or automated user) that generated the build. |
| 745 | There are no requirements on the specific format of this field, except that it |
| 746 | MUST NOT be null or the empty string ("").</td> |
| 747 | </tr> |
| 748 | </table> |
| 749 | |
| 750 | |
| 751 | <h3 id="3_2_3_intent_compatibility">3.2.3. Intent Compatibility</h3> |
| 752 | |
| 753 | |
| 754 | <p>Device implementations MUST honor Android’s loose-coupling intent system, as |
| 755 | described in the sections below. By“honored ” it is meant that the device |
| 756 | implementer MUST provide an Android Activity or Service that specifies a |
| 757 | matching intent filter that binds to and implements correct behavior for each |
| 758 | specified intent pattern.</p> |
| 759 | |
| 760 | <h4 id="3_2_3_1_core_application_intents">3.2.3.1. Core Application Intents</h4> |
| 761 | |
| 762 | |
| 763 | <p>Android intents allow application components to request functionality from |
| 764 | other Android components. The Android upstream project includes a list of |
| 765 | applications considered core Android applications, which implements several |
| 766 | intent patterns to perform common actions. The core Android applications are:</p> |
| 767 | |
| 768 | <ul> |
| 769 | <li>Desk Clock</li> |
| 770 | <li>Browser</li> |
| 771 | <li>Calendar</li> |
| 772 | <li>Contacts</li> |
| 773 | <li>Gallery</li> |
| 774 | <li>GlobalSearch</li> |
| 775 | <li>Launcher</li> |
| 776 | <li>Music</li> |
| 777 | <li>Settings</li> |
| 778 | </ul> |
| 779 | |
| 780 | <p>Device implementations SHOULD include the core Android applications as |
| 781 | appropriate but MUST include a component implementing the same intent patterns |
| 782 | defined by all the “public” Activity or Service components of these core |
| 783 | Android applications. Note that Activity or Service components are considered |
| 784 | “public” when the attribute android:exported is absent or has the value true.</p> |
| 785 | |
| 786 | <h4 id="3_2_3_2_intent_overrides">3.2.3.2. Intent Overrides</h4> |
| 787 | |
| 788 | |
| 789 | <p>As Android is an extensible platform, device implementations MUST allow each |
| 790 | intent pattern referenced in <a href="#3_2_3_1_core_application_intents">section 3.2.3.1</a> to be overridden by third-party applications. The upstream Android open source |
| 791 | implementation allows this by default; device implementers MUST NOT attach |
| 792 | special privileges to system applications' use of these intent patterns, or |
| 793 | prevent third-party applications from binding to and assuming control of these |
| 794 | patterns. This prohibition specifically includes but is not limited to |
| 795 | disabling the“Chooser” user interface that allows the user to select between |
| 796 | multiple applications that all handle the same intent pattern.</p> |
| 797 | |
| 798 | <p>However, device implementations MAY provide default activities for specific URI |
| 799 | patterns (eg. http://play.google.com) if the default activity provides a more |
| 800 | specific filter for the data URI. For example, an intent filter specifying the |
| 801 | data URI “http://www.android.com” is more specific than the browser filter for“http://”. Device implementations MUST provide a user interface for users to |
| 802 | modify the default activity for intents.</p> |
| 803 | |
| 804 | <h4 id="3_2_3_3_intent_namespaces">3.2.3.3. Intent Namespaces</h4> |
| 805 | |
| 806 | |
| 807 | <p>Device implementations MUST NOT include any Android component that honors any |
| 808 | new intent or broadcast intent patterns using an ACTION, CATEGORY, or other key |
| 809 | string in the android.* or com.android.* namespace. Device implementers MUST |
| 810 | NOT include any Android components that honor any new intent or broadcast |
| 811 | intent patterns using an ACTION, CATEGORY, or other key string in a package |
| 812 | space belonging to another organization. Device implementers MUST NOT alter or |
| 813 | extend any of the intent patterns used by the core apps listed in <a href="#3_2_3_1_core_application_intents">section 3.2.3.1</a>. Device implementations MAY include intent patterns using namespaces clearly |
| 814 | and obviously associated with their own organization. This prohibition is |
| 815 | analogous to that specified for Java language classes in <a href="#3_6_api_namespaces">section 3.6</a>.</p> |
| 816 | |
| 817 | <h4 id="3_2_3_4_broadcast_intents">3.2.3.4. Broadcast Intents</h4> |
| 818 | |
| 819 | |
| 820 | <p>Third-party applications rely on the platform to broadcast certain intents to |
| 821 | notify them of changes in the hardware or software environment. |
| 822 | Android-compatible devices MUST broadcast the public broadcast intents in |
| 823 | response to appropriate system events. Broadcast intents are described in the |
| 824 | SDK documentation.</p> |
| 825 | |
| 826 | <h4 id="3_2_3_5_default_app_settings">3.2.3.5. Default App Settings</h4> |
| 827 | |
| 828 | |
| 829 | <p>Android includes settings that provide users an easy way to select their |
| 830 | default applications, for example for Home screen or SMS. Where it makes sense, |
| 831 | device implementations MUST provide a similar settings menu and be compatible |
| 832 | with the intent filter pattern and API methods described in the SDK |
| 833 | documentation as below.</p> |
| 834 | |
| 835 | <p>Device implementations:</p> |
| 836 | |
| 837 | <ul> |
| 838 | <li>MUST honor the android.settings.HOME_SETTINGS intent to show a default app |
| 839 | settings menu for Home Screen, if the device implementation reports |
| 840 | android.software.home_screen [<a href="http://developer.android.com/reference/android/provider/Settings.html">Resources, 10]</a></li> |
| 841 | <li>MUST provide a settings menu that will call the |
| 842 | android.provider.Telephony.ACTION_CHANGE_DEFAULT intent to show a dialog to |
| 843 | change the default SMS application, if the device implementation reports |
| 844 | android.hardware.telephony [<a href="http://developer.android.com/reference/android/provider/Telephony.Sms.Intents.html">Resources, 9</a>]</li> |
| 845 | <li>MUST honor the android.settings.NFC_PAYMENT_SETTINGS intent to show a default |
| 846 | app settings menu for Tap and Pay, if the device implementation reports |
| 847 | android.hardware.nfc.hce [<a href="http://developer.android.com/reference/android/provider/Settings.html">Resources, 10]</a></li> |
| 848 | </ul> |
| 849 | |
| 850 | <h2 id="3_3_native_api_compatibility">3.3. Native API Compatibility</h2> |
| 851 | |
| 852 | |
| 853 | <h3 id="3_3_1_application_binary_interfaces">3.3.1. Application Binary Interfaces</h3> |
| 854 | |
| 855 | |
| 856 | <p>Managed Dalvik bytecode can call into native code provided in the application |
| 857 | .apk file as an ELF .so file compiled for the appropriate device hardware |
| 858 | architecture. As native code is highly dependent on the underlying processor |
| 859 | technology, Android defines a number of Application Binary Interfaces (ABIs) in |
| 860 | the Android NDK. Device implementations MUST be compatible with one or more |
| 861 | defined ABIs, and MUST implement compatibility with the Android NDK, as below.</p> |
| 862 | |
| 863 | <p>If a device implementation includes support for an Android ABI, it:</p> |
| 864 | |
| 865 | <ul> |
| 866 | <li>MUST include support for code running in the managed environment to call into |
| 867 | native code, using the standard Java Native Interface (JNI) semantics</li> |
| 868 | <li>MUST be source-compatible (i.e. header compatible) and binary-compatible (for |
| 869 | the ABI) with each required library in the list below</li> |
| 870 | <li>MUST support the equivalent 32-bit ABI if any 64-bit ABI is supported</li> |
| 871 | <li>MUST accurately report the native Application Binary Interface (ABI) supported |
| 872 | by the device, via the android.os.Build.SUPPORTED_ABIS, |
| 873 | android.os.Build.SUPPORTED_32_BIT_ABIS, and |
| 874 | android.os.Build.SUPPORTED_64_BIT_ABIS parameters, each a comma separated list |
| 875 | of ABIs ordered from the most to the least preferred one</li> |
Unsuk Jung | 0670643 | 2015-08-31 11:26:13 -0700 | [diff] [blame] | 876 | <li>MUST report, via the above parameters, only those ABIs documented and |
| 877 | described in the latest version of the Android NDK ABI Management documentation |
| 878 | [<a href="https://developer.android.com/ndk/guides/abis.html">Resources, XX</a>], |
| 879 | and MUST include support for the Advanced SIMD (a.k.a. NEON) |
| 880 | [<a href="http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0388f/Beijfcja.html">Resources,XX</a>] |
| 881 | extension |
| 882 | </li> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 883 | <li>SHOULD be built using the source code and header files available in the |
| 884 | upstream Android Open Source Project</li> |
| 885 | </ul> |
| 886 | |
| 887 | <p>The following native code APIs MUST be available to apps that include native |
| 888 | code:</p> |
| 889 | |
| 890 | <ul> |
| 891 | <li>libc (C library)</li> |
| 892 | <li>libm (math library)</li> |
| 893 | <li>Minimal support for C++</li> |
| 894 | <li>JNI interface</li> |
| 895 | <li>liblog (Android logging)</li> |
| 896 | <li>libz (Zlib compression)</li> |
| 897 | <li>libdl (dynamic linker)</li> |
| 898 | <li>libGLESv1_CM.so (OpenGL ES 1.x)</li> |
| 899 | <li>libGLESv2.so (OpenGL ES 2.0)</li> |
| 900 | <li>libGLESv3.so (OpenGL ES 3.x)</li> |
| 901 | <li>libEGL.so (native OpenGL surface management)</li> |
| 902 | <li>libjnigraphics.so</li> |
| 903 | <li>libOpenSLES.so (OpenSL ES 1.0.1 audio support)</li> |
| 904 | <li>libOpenMAXAL.so (OpenMAX AL 1.0.1 support)</li> |
| 905 | <li>libandroid.so (native Android activity support)</li> |
| 906 | <li>libmediandk.so (native media APIs support)</li> |
| 907 | <li>Support for OpenGL, as described below</li> |
| 908 | </ul> |
| 909 | |
| 910 | <p>Note that future releases of the Android NDK may introduce support for |
| 911 | additional ABIs. If a device implementation is not compatible with an existing |
| 912 | predefined ABI, it MUST NOT report support for any ABIs at all.</p> |
| 913 | |
| 914 | <p>Note that device implementations MUST include libGLESv3.so and it MUST symlink |
| 915 | (symbolic link) to libGLESv2.so. in turn, MUST export all the OpenGL ES 3.1 and |
| 916 | Android Extension Pack [<a href="http://developer.android.com/guide/topics/graphics/opengl.html#aep">Resources, 11</a>] function symbols as defined in the NDK release android-21. Although all the |
| 917 | symbols must be present, only the corresponding functions for OpenGL ES |
| 918 | versions and extensions actually supported by the device must be fully |
| 919 | implemented.</p> |
| 920 | |
| 921 | <p>Native code compatibility is challenging. For this reason, device implementers |
Bert McMeen | 816a242 | 2015-09-29 16:33:19 -0700 | [diff] [blame] | 922 | are <strong>STRONGLY RECOMMENDED</strong> to use the implementations of the libraries listed above from the upstream |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 923 | Android Open Source Project. </p> |
| 924 | |
| 925 | <h3 id="3_3_2_32-bit_arm_native_code_compatibility"> |
| 926 | 3.3.2. 32-bit ARM Native Code Compatibility |
| 927 | </h3> |
| 928 | |
| 929 | <p>The ARMv8 architecture deprecates several CPU operations, including some |
| 930 | operations used in existing native code. On 64-bit ARM devices, the following |
| 931 | deprecated operations MUST remain available to 32-bit native ARM code, either |
| 932 | through native CPU support or through software emulation:</p> |
| 933 | |
| 934 | <ul> |
| 935 | <li>SWP and SWPB instructions</li> |
| 936 | <li>SETEND instruction</li> |
| 937 | <li>CP15ISB, CP15DSB, and CP15DMB barrier operations</li> |
| 938 | </ul> |
| 939 | |
| 940 | <p>Legacy versions of the Android NDK used /proc/cpuinfo to discover CPU features |
| 941 | from 32-bit ARM native code. For compatibility with applications built using this |
| 942 | NDK, devices MUST include the following lines in /proc/cpuinfo when it is read |
| 943 | by 32-bit ARM applications:</p> |
| 944 | |
| 945 | <ul> |
| 946 | <li>"Features: ", followed by a list of any optional ARMv7 CPU features |
| 947 | supported by the device</li> |
| 948 | <li>"CPU architecture: ", followed by an integer describing the device's |
| 949 | highest supported ARM architecture (e.g., "8" for ARMv8 devices)</li> |
| 950 | </ul> |
| 951 | |
| 952 | <p>These requirements only apply when /proc/cpuinfo is read by 32-bit ARM |
| 953 | applications. Devices SHOULD not alter /proc/cpuinfo when read by 64-bit ARM or |
| 954 | non-ARM applications.</p> |
| 955 | |
| 956 | <h2 id="3_4_web_compatibility">3.4. Web Compatibility</h2> |
| 957 | |
| 958 | |
| 959 | <h3 id="3_4_1_webview_compatibility">3.4.1. WebView Compatibility</h3> |
| 960 | |
| 961 | <div class="note"> |
| 962 | <p>Android Watch devices MAY, but all other device implementations MUST provide |
| 963 | a complete implementation of the android.webkit.Webview API.</p> |
| 964 | </div> |
| 965 | |
| 966 | |
| 967 | <p>The platform feature android.software.webview MUST be reported on any device |
| 968 | that provides a complete implementation of the android.webkit.WebView API, and |
| 969 | MUST NOT be reported on devices without a complete implementation of the API. |
| 970 | The Android Open Source implementation uses code from the Chromium Project to |
| 971 | implement the android.webkit.WebView [<a href="http://developer.android.com/reference/android/webkit/WebView.html">Resources, 12</a>]. Because it is not feasible to develop a comprehensive test suite for a web |
| 972 | rendering system, device implementers MUST use the specific upstream build of |
| 973 | Chromium in the WebView implementation. Specifically:</p> |
| 974 | |
| 975 | <ul> |
| 976 | <li>Device android.webkit.WebView implementations MUST be based on the Chromium |
| 977 | build from the upstream Android Open Source Project for Android ANDROID_VERSION. This build |
| 978 | includes a specific set of functionality and security fixes for the WebView [<a href="http://www.chromium.org/">Resources, 13</a>].</li> |
| 979 | <li>The user agent string reported by the WebView MUST be in this format: |
Unsuk Jung | 34d4dcb | 2015-09-28 15:41:27 -0700 | [diff] [blame] | 980 | <p>Mozilla/5.0 (Linux; Android $(VERSION); $(MODEL) Build/$(BUILD); wv) |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 981 | AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 $(CHROMIUM_VER) Mobile |
| 982 | Safari/537.36</p> |
| 983 | <ul> |
| 984 | <li>The value of the $(VERSION) string MUST be the same as the value for |
| 985 | android.os.Build.VERSION.RELEASE.</li> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 986 | <li>The value of the $(MODEL) string MUST be the same as the value for |
| 987 | android.os.Build.MODEL.</li> |
| 988 | <li>The value of the $(BUILD) string MUST be the same as the value for |
| 989 | android.os.Build.ID.</li> |
| 990 | <li>The value of the $(CHROMIUM_VER) string MUST be the version of Chromium in the |
| 991 | upstream Android Open Source Project.</li> |
| 992 | <li>Device implementations MAY omit Mobile in the user agent string.</li> |
| 993 | </ul></li></ul> |
| 994 | |
| 995 | <p>The WebView component SHOULD include support for as many HTML5 features as |
| 996 | possible and if it supports the feature SHOULD conform to the HTML5 |
| 997 | specification [<a href="http://html.spec.whatwg.org/multipage/">Resources, 14</a>].</p> |
| 998 | |
| 999 | <h3 id="3_4_2_browser_compatibility">3.4.2. Browser Compatibility</h3> |
| 1000 | |
| 1001 | <div class="note"> |
| 1002 | <p>Android Television, Watch, and Android Automotive implementations MAY omit a |
| 1003 | browser application, but MUST support the public intent patterns as described in |
| 1004 | <a href="#3_2_3_1_core_application_intents">section 3.2.3.1</a>. All other types |
| 1005 | of device implementations MUST include a standalone Browser application for |
| 1006 | general user web browsing.</p> |
| 1007 | </div> |
| 1008 | |
| 1009 | <p>The standalone Browser MAY be based on a browser technology other than WebKit. |
| 1010 | However, even if an alternate Browser application is used, the |
| 1011 | android.webkit.WebView component provided to third-party applications MUST be |
| 1012 | based on WebKit, as described in <a href="#3_4_1_webview_compatibility">section 3.4.1</a>.</p> |
| 1013 | |
| 1014 | <p>Implementations MAY ship a custom user agent string in the standalone Browser |
| 1015 | application.</p> |
| 1016 | |
| 1017 | <p>The standalone Browser application (whether based on the upstream WebKit |
| 1018 | Browser application or a third-party replacement) SHOULD include support for as |
| 1019 | much of HTML5 [<a href="http://html.spec.whatwg.org/multipage/">Resources, 14</a>] as possible. Minimally, device implementations MUST support each of these |
| 1020 | APIs associated with HTML5:</p> |
| 1021 | |
| 1022 | <ul> |
| 1023 | <li>application cache/offline operation [<a href="http://www.w3.org/html/wg/drafts/html/master/browsers.html#offline">Resources, 15</a>]</li> |
| 1024 | <li>the <video> tag [<a href="http://www.w3.org/html/wg/drafts/html/master/semantics.html#video">Resources, 16</a>]</li> |
| 1025 | <li>geolocation [<a href="http://www.w3.org/TR/geolocation-API/">Resources, 17</a>]</li> |
| 1026 | </ul> |
| 1027 | |
| 1028 | <p>Additionally, device implementations MUST support the HTML5/W3C webstorage API |
| 1029 | [<a href="http://www.w3.org/TR/webstorage/">Resources, 18</a>], and SHOULD support the HTML5/W3C IndexedDB API [<a href="http://www.w3.org/TR/IndexedDB/">Resources, 19</a>]. Note that as the web development standards bodies are transitioning to favor |
| 1030 | IndexedDB over webstorage, IndexedDB is expected to become a required component |
| 1031 | in a future version of Android.</p> |
| 1032 | |
| 1033 | <h2 id="3_5_api_behavioral_compatibility">3.5. API Behavioral Compatibility</h2> |
| 1034 | |
| 1035 | |
| 1036 | <p>The behaviors of each of the API types (managed, soft, native, and web) must be |
| 1037 | consistent with the preferred implementation of the upstream Android Open |
| 1038 | Source Project [<a href="http://source.android.com/">Resources, 2</a>]. Some specific areas of compatibility are:</p> |
| 1039 | |
| 1040 | <ul> |
| 1041 | <li>Devices MUST NOT change the behavior or semantics of a standard intent.</li> |
| 1042 | <li>Devices MUST NOT alter the lifecycle or lifecycle semantics of a particular |
| 1043 | type of system component (such as Service, Activity, ContentProvider, etc.).</li> |
| 1044 | <li>Devices MUST NOT change the semantics of a standard permission.</li> |
| 1045 | </ul> |
| 1046 | |
| 1047 | <p>The above list is not comprehensive. The Compatibility Test Suite (CTS) tests |
| 1048 | significant portions of the platform for behavioral compatibility, but not all. |
| 1049 | It is the responsibility of the implementer to ensure behavioral compatibility |
| 1050 | with the Android Open Source Project. For this reason, device implementers |
| 1051 | SHOULD use the source code available via the Android Open Source Project where |
| 1052 | possible, rather than re-implement significant parts of the system.</p> |
| 1053 | |
| 1054 | <h2 id="3_6_api_namespaces">3.6. API Namespaces</h2> |
| 1055 | |
| 1056 | |
| 1057 | <p>Android follows the package and class namespace conventions defined by the Java |
| 1058 | programming language. To ensure compatibility with third-party applications, |
| 1059 | device implementers MUST NOT make any prohibited modifications (see below) to |
| 1060 | these package namespaces:</p> |
| 1061 | |
| 1062 | <ul> |
| 1063 | <li>java.*</li> |
| 1064 | <li>javax.*</li> |
| 1065 | <li>sun.*</li> |
| 1066 | <li>android.*</li> |
| 1067 | <li>com.android.*</li> |
| 1068 | </ul> |
| 1069 | |
| 1070 | <p><strong>Prohibited modifications include</strong>:</p> |
| 1071 | |
| 1072 | <ul> |
| 1073 | <li>Device implementations MUST NOT modify the publicly exposed APIs on the Android |
| 1074 | platform by changing any method or class signatures, or by removing classes or |
| 1075 | class fields.</li> |
| 1076 | <li>Device implementers MAY modify the underlying implementation of the APIs, but |
| 1077 | such modifications MUST NOT impact the stated behavior and Java-language |
| 1078 | signature of any publicly exposed APIs.</li> |
| 1079 | <li>Device implementers MUST NOT add any publicly exposed elements (such as classes |
| 1080 | or interfaces, or fields or methods to existing classes or interfaces) to the |
| 1081 | APIs above.</li> |
| 1082 | </ul> |
| 1083 | |
| 1084 | <p>A “publicly exposed element” is any construct which is not decorated with the“@hide” marker as used in the upstream Android source code. In other words, |
| 1085 | device implementers MUST NOT expose new APIs or alter existing APIs in the |
| 1086 | namespaces noted above. Device implementers MAY make internal-only |
| 1087 | modifications, but those modifications MUST NOT be advertised or otherwise |
| 1088 | exposed to developers.</p> |
| 1089 | |
| 1090 | <p>Device implementers MAY add custom APIs, but any such APIs MUST NOT be in a |
| 1091 | namespace owned by or referring to another organization. For instance, device |
| 1092 | implementers MUST NOT add APIs to the com.google.* or similar namespace: only |
| 1093 | Google may do so. Similarly, Google MUST NOT add APIs to other companies' |
| 1094 | namespaces. Additionally, if a device implementation includes custom APIs |
| 1095 | outside the standard Android namespace, those APIs MUST be packaged in an |
| 1096 | Android shared library so that only apps that explicitly use them (via the |
Unsuk Jung | 2e62f9a | 2015-07-16 23:01:44 -0700 | [diff] [blame] | 1097 | lt;uses-librarygt; mechanism) are affected by the increased memory usage of such |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 1098 | APIs.</p> |
| 1099 | |
| 1100 | <p>If a device implementer proposes to improve one of the package namespaces above |
| 1101 | (such as by adding useful new functionality to an existing API, or adding a new |
| 1102 | API), the implementer SHOULD visit <a href="http://source.android.com/">source.android.com</a> and begin the process for contributing changes and code, according to the |
| 1103 | information on that site.</p> |
| 1104 | |
| 1105 | <p>Note that the restrictions above correspond to standard conventions for naming |
| 1106 | APIs in the Java programming language; this section simply aims to reinforce |
| 1107 | those conventions and make them binding through inclusion in this Compatibility |
| 1108 | Definition.</p> |
| 1109 | |
| 1110 | <h2 id="3_7_runtime_compatibility">3.7. Runtime Compatibility</h2> |
| 1111 | |
| 1112 | |
| 1113 | <p>Device implementations MUST support the full Dalvik Executable (DEX) format and |
| 1114 | Dalvik bytecode specification and semantics [<a href="https://android.googlesource.com/platform/dalvik/+/lollipop-release/docs/">Resources, 20</a>]. Device implementers SHOULD use ART, the reference upstream implementation of |
| 1115 | the Dalvik Executable Format, and the reference implementation’s package |
| 1116 | management system.</p> |
| 1117 | |
| 1118 | <p>Device implementations MUST configure Dalvik runtimes to allocate memory in |
| 1119 | accordance with the upstream Android platform, and as specified by the |
| 1120 | following table. (See <a href="#7_1_1_screen_configuration">section 7.1.1</a> for screen size and screen density definitions.)</p> |
| 1121 | |
| 1122 | <p>Note that memory values specified below are considered minimum values and |
| 1123 | device implementations MAY allocate more memory per application.</p> |
| 1124 | |
| 1125 | <table> |
| 1126 | <tr> |
| 1127 | <th>Screen Layout</th> |
| 1128 | <th>Screen Density</th> |
| 1129 | <th>Minimum Application Memory</th> |
| 1130 | </tr> |
| 1131 | <tr> |
| 1132 | <td rowspan="10">small/normal</td> |
| 1133 | <td>120 dpi (ldpi)</td> |
| 1134 | <td rowspan="2">32MB</td> |
| 1135 | </tr> |
| 1136 | <tr> |
| 1137 | <td>160 dpi (mdpi)</td> |
| 1138 | </tr> |
| 1139 | <tr> |
| 1140 | <td>213 dpi (tvdpi)</td> |
| 1141 | <td rowspan="3">48MB</td> |
| 1142 | </tr> |
| 1143 | <tr> |
| 1144 | <td>240 dpi (hdpi)</td> |
| 1145 | </tr> |
| 1146 | <tr> |
| 1147 | <td>280 dpi (280dpi)</td> |
| 1148 | </tr> |
| 1149 | <tr> |
| 1150 | <td>320 dpi (xhdpi)</td> |
| 1151 | <td>80MB</td> |
| 1152 | </tr> |
| 1153 | <tr> |
| 1154 | <td>400 dpi (400dpi)</td> |
| 1155 | <td>96MB</td> |
| 1156 | </tr> |
| 1157 | <tr> |
| 1158 | <td>480 dpi (xxhdpi)</td> |
| 1159 | <td>128MB</td> |
| 1160 | </tr> |
| 1161 | <tr> |
| 1162 | <td>560 dpi (560dpi)</td> |
| 1163 | <td>192MB</td> |
| 1164 | </tr> |
| 1165 | <tr> |
| 1166 | <td>640 dpi (xxxhdpi)</td> |
| 1167 | <td>256MB</td> |
| 1168 | </tr> |
| 1169 | <tr> |
| 1170 | <td rowspan="10">large</td> |
| 1171 | <td>120 dpi (ldpi)</td> |
| 1172 | <td>32MB</td> |
| 1173 | </tr> |
| 1174 | <tr> |
| 1175 | <td>160 dpi (mdpi)</td> |
| 1176 | <td>48MB</td> |
| 1177 | </tr> |
| 1178 | <tr> |
| 1179 | <td>213 dpi (tvdpi)</td> |
| 1180 | <td rowspan="2">80MB</td> |
| 1181 | </tr> |
| 1182 | <tr> |
| 1183 | <td>240 dpi (hdpi)</td> |
| 1184 | </tr> |
| 1185 | <tr> |
| 1186 | <td>280 dpi (280dpi)</td> |
| 1187 | <td>96MB</td> |
| 1188 | </tr> |
| 1189 | <tr> |
| 1190 | <td>320 dpi (xhdpi)</td> |
| 1191 | <td>128MB</td> |
| 1192 | </tr> |
| 1193 | <tr> |
| 1194 | <td>400 dpi (400dpi)</td> |
| 1195 | <td>192MB</td> |
| 1196 | </tr> |
| 1197 | <tr> |
| 1198 | <td>480 dpi (xxhdpi)</td> |
| 1199 | <td>256MB</td> |
| 1200 | </tr> |
| 1201 | <tr> |
| 1202 | <td>560 dpi (560dpi)</td> |
| 1203 | <td>384MB</td> |
| 1204 | </tr> |
| 1205 | <tr> |
| 1206 | <td>640 dpi (xxxhdpi)</td> |
| 1207 | <td>512MB</td> |
| 1208 | </tr> |
| 1209 | <tr> |
| 1210 | <td rowspan="10">xlarge</td> |
| 1211 | <td>120 dpi (ldpi)</td> |
| 1212 | <td>48MB</td> |
| 1213 | </tr> |
| 1214 | <tr> |
| 1215 | <td>160 dpi (mdpi)</td> |
| 1216 | <td>80MB</td> |
| 1217 | </tr> |
| 1218 | <tr> |
| 1219 | <td>213 dpi (tvdpi)</td> |
| 1220 | <td rowspan="2">96MB</td> |
| 1221 | </tr> |
| 1222 | <tr> |
| 1223 | <td>240 dpi (hdpi)</td> |
| 1224 | </tr> |
| 1225 | <tr> |
| 1226 | <td>280 dpi (280dpi)</td> |
| 1227 | <td>144MB</td> |
| 1228 | </tr> |
| 1229 | <tr> |
| 1230 | <td>320 dpi (xhdpi)</td> |
| 1231 | <td>192MB</td> |
| 1232 | </tr> |
| 1233 | <tr> |
| 1234 | <td>400 dpi (400dpi)</td> |
| 1235 | <td>288MB</td> |
| 1236 | </tr> |
| 1237 | <tr> |
| 1238 | <td>480 dpi (xxhdpi)</td> |
| 1239 | <td>384MB</td> |
| 1240 | </tr> |
| 1241 | <tr> |
| 1242 | <td>560 dpi (560dpi)</td> |
| 1243 | <td>576MB</td> |
| 1244 | </tr> |
| 1245 | <tr> |
| 1246 | <td>640 dpi (xxxhdpi)</td> |
| 1247 | <td>768MB</td> |
| 1248 | </tr> |
| 1249 | </table> |
| 1250 | |
| 1251 | |
| 1252 | <h2 id="3_8_user_interface_compatibility">3.8. User Interface Compatibility</h2> |
| 1253 | |
| 1254 | |
| 1255 | <h3 id="3_8_1_launcher_home_screen">3.8.1. Launcher (Home Screen)</h3> |
| 1256 | |
| 1257 | |
| 1258 | <p>Android includes a launcher application (home screen) and support for |
| 1259 | third-party applications to replace the device launcher (home screen). Device |
| 1260 | implementations that allow third-party applications to replace the device home |
| 1261 | screen MUST declare the platform feature android.software.home_screen.</p> |
| 1262 | |
| 1263 | <h3 id="3_8_2_widgets">3.8.2. Widgets</h3> |
| 1264 | |
| 1265 | <div class="note"> |
| 1266 | <p>Widgets are optional for all Android device implementations, but SHOULD be |
| 1267 | supported on Android Handheld devices.</p> |
| 1268 | </div> |
| 1269 | |
| 1270 | |
| 1271 | <p>Android defines a component type and corresponding API and lifecycle that |
| 1272 | allows applications to expose an “AppWidget” to the end user [<a href="http://developer.android.com/guide/practices/ui_guidelines/widget_design.html">Resources, 21</a>] a feature that is strongly RECOMMENDED to be supported on Handheld Device |
| 1273 | implementations. Device implementations that support embedding widgets on the |
| 1274 | home screen MUST meet the following requirements and declare support for |
| 1275 | platform feature android.software.app_widgets.</p> |
| 1276 | |
| 1277 | <ul> |
| 1278 | <li>Device launchers MUST include built-in support for AppWidgets, and expose user |
| 1279 | interface affordances to add, configure, view, and remove AppWidgets directly |
| 1280 | within the Launcher.</li> |
| 1281 | <li>Device implementations MUST be capable of rendering widgets that are 4 x 4 in |
| 1282 | the standard grid size. See the App Widget Design Guidelines in the Android SDK |
| 1283 | documentation [<a href="http://developer.android.com/guide/practices/ui_guidelines/widget_design.html">Resources, 21</a>] for details.</li> |
| 1284 | <li>Device implementations that include support for lock screen MAY support |
| 1285 | application widgets on the lock screen.</li> |
| 1286 | </ul> |
| 1287 | |
| 1288 | <h3 id="3_8_3_notifications">3.8.3. Notifications</h3> |
| 1289 | |
| 1290 | |
| 1291 | <p>Android includes APIs that allow developers to notify users of notable events [<a href="http://developer.android.com/guide/topics/ui/notifiers/notifications.html">Resources, 22</a>], using hardware and software features of the device.</p> |
| 1292 | |
| 1293 | <p>Some APIs allow applications to perform notifications or attract attention |
| 1294 | using hardware—specifically sound, vibration, and light. Device implementations |
| 1295 | MUST support notifications that use hardware features, as described in the SDK |
| 1296 | documentation, and to the extent possible with the device implementation |
| 1297 | hardware. For instance, if a device implementation includes a vibrator, it MUST |
| 1298 | correctly implement the vibration APIs. If a device implementation lacks |
| 1299 | hardware, the corresponding APIs MUST be implemented as no-ops. This behavior |
| 1300 | is further detailed in <a href="#7_hardware_compatibility">section 7</a>.</p> |
| 1301 | |
| 1302 | <p>Additionally, the implementation MUST correctly render all resources (icons, animation files |
| 1303 | etc.) provided for in the APIs |
| 1304 | [<a href="https://developer.android.com/guide/topics/resources/available-resources.html">Resources, 23</a>], |
| 1305 | or in the Status/System Bar icon style guide |
| 1306 | [<a href="http://developer.android.com/design/style/iconography.html">Resources, 24</a>], |
| 1307 | which in the case of an Android Television device includes the possibility to not display the |
| 1308 | notifications. Device implementers MAY provide an alternative user experience for |
| 1309 | notifications than that provided by the reference Android Open Source |
| 1310 | implementation; however, such alternative notification systems MUST support |
| 1311 | existing notification resources, as above. </p> |
| 1312 | |
| 1313 | <p>Android includes support for various notifications, such as:</p> |
| 1314 | |
| 1315 | <ul> |
| 1316 | <li><strong>Rich notifications</strong>. Interactive Views for ongoing notifications.</li> |
| 1317 | <li><strong>Heads-up notifications</strong>. Interactive Views users can act on or dismiss without leaving the current app.</li> |
| 1318 | <li><strong>Lockscreen notifications</strong>. Notifications shown over a lock screen with granular control on visibility.</li> |
| 1319 | </ul> |
| 1320 | |
| 1321 | <p>Android device implementations, when such notifications are made visible, MUST properly execute |
| 1322 | Rich and Heads-up notifications and include the title/name, icon, text as documented in the Android |
| 1323 | APIs <a href="https://developer.android.com/design/patterns/notifications.html">[Resources, 25]</a>. |
| 1324 | </p> |
| 1325 | |
| 1326 | <p>Android includes Notification Listener Service APIs that allow apps (once |
| 1327 | explicitly enabled by the user) to receive a copy of all notifications as they |
| 1328 | are posted or updated. Device implementations MUST correctly and promptly send |
| 1329 | notifications in their entirety to all such installed and user-enabled listener |
| 1330 | services, including any and all metadata attached to the Notification object.</p> |
| 1331 | |
| 1332 | <h3 id="3_8_4_search">3.8.4. Search</h3> |
| 1333 | |
| 1334 | |
| 1335 | <p>Android includes APIs [<a href="http://developer.android.com/reference/android/app/SearchManager.html">Resources, 26</a>] that allow developers to incorporate search into their applications, and |
| 1336 | expose their application’s data into the global system search. Generally |
| 1337 | speaking, this functionality consists of a single, system-wide user interface |
| 1338 | that allows users to enter queries, displays suggestions as users type, and |
| 1339 | displays results. The Android APIs allow developers to reuse this interface to |
| 1340 | provide search within their own apps, and allow developers to supply results to |
| 1341 | the common global search user interface.</p> |
| 1342 | |
| 1343 | <p>Android device implementations SHOULD include global search, a single, shared, |
| 1344 | system-wide search user interface capable of real-time suggestions in response |
| 1345 | to user input. Device implementations SHOULD implement the APIs that allow |
| 1346 | developers to reuse this user interface to provide search within their own |
| 1347 | applications. Device implementations that implement the global search interface |
| 1348 | MUST implement the APIs that allow third-party applications to add suggestions |
| 1349 | to the search box when it is run in global search mode. If no third-party |
| 1350 | applications are installed that make use of this functionality, the default |
| 1351 | behavior SHOULD be to display web search engine results and suggestions.</p> |
| 1352 | |
| 1353 | <h3 id="3_8_5_toasts">3.8.5. Toasts</h3> |
| 1354 | |
| 1355 | |
| 1356 | <p>Applications can use the “Toast” API to display short non-modal strings to the |
| 1357 | end user, that disappear after a brief period of time [<a href="http://developer.android.com/reference/android/widget/Toast.html">Resources, 27</a>]. Device implementations MUST display Toasts from applications to end users in |
| 1358 | some high-visibility manner.</p> |
| 1359 | |
| 1360 | <h3 id="3_8_6_themes">3.8.6. Themes</h3> |
| 1361 | |
| 1362 | |
| 1363 | <p>Android provides “themes” as a mechanism for applications to apply styles |
| 1364 | across an entire Activity or application.</p> |
| 1365 | |
| 1366 | <p>Android includes a “Holo” theme family as a set of defined styles for |
| 1367 | application developers to use if they want to match the Holo theme look and |
| 1368 | feel as defined by the Android SDK [<a href="http://developer.android.com/guide/topics/ui/themes.html">Resources, 28</a>]. Device implementations MUST NOT alter any of the Holo theme attributes |
| 1369 | exposed to applications [<a href="http://developer.android.com/reference/android/R.style.html">Resources, 29</a>].</p> |
| 1370 | |
| 1371 | <p>Android includes a “Material” theme family as a set of defined styles for |
| 1372 | application developers to use if they want to match the design theme’s look and |
| 1373 | feel across the wide variety of different Android device types. Device |
| 1374 | implementations MUST support the “Material” theme family and MUST NOT alter any |
| 1375 | of the Material theme attributes or their assets exposed to applications [<a href="http://developer.android.com/reference/android/R.style.html#Theme_Material">Resources, 30</a>].</p> |
| 1376 | |
| 1377 | <p>Android also includes a “Device Default” theme family as a set of defined |
| 1378 | styles for application developers to use if they want to match the look and |
| 1379 | feel of the device theme as defined by the device implementer. Device |
| 1380 | implementations MAY modify the Device Default theme attributes exposed to |
| 1381 | applications [<a href="http://developer.android.com/reference/android/R.style.html">Resources, 29</a>].</p> |
| 1382 | |
| 1383 | <p>Android supports a new variant theme with translucent system bars, which allows |
| 1384 | application developers to fill the area behind the status and navigation bar |
| 1385 | with their app content. To enable a consistent developer experience in this |
| 1386 | configuration, it is important the status bar icon style is maintained across |
| 1387 | different device implementations. Therefore, Android device implementations |
| 1388 | MUST use white for system status icons (such as signal strength and battery |
| 1389 | level) and notifications issued by the system, unless the icon is indicating a |
| 1390 | problematic status [<a href="http://developer.android.com/reference/android/R.style.html">Resources, 29</a>].</p> |
| 1391 | |
| 1392 | <h3 id="3_8_7_live_wallpapers">3.8.7. Live Wallpapers</h3> |
| 1393 | |
| 1394 | |
| 1395 | <p>Android defines a component type and corresponding API and lifecycle that |
| 1396 | allows applications to expose one or more “Live Wallpapers” to the end user [<a href="http://developer.android.com/reference/android/service/wallpaper/WallpaperService.html">Resources, 31</a>]. Live wallpapers are animations, patterns, or similar images with limited |
| 1397 | input capabilities that display as a wallpaper, behind other applications.</p> |
| 1398 | |
| 1399 | <p>Hardware is considered capable of reliably running live wallpapers if it can |
| 1400 | run all live wallpapers, with no limitations on functionality, at a reasonable |
| 1401 | frame rate with no adverse effects on other applications. If limitations in the |
| 1402 | hardware cause wallpapers and/or applications to crash, malfunction, consume |
| 1403 | excessive CPU or battery power, or run at unacceptably low frame rates, the |
| 1404 | hardware is considered incapable of running live wallpaper. As an example, some |
| 1405 | live wallpapers may use an OpenGL 2.0 or 3.x context to render their content. |
| 1406 | Live wallpaper will not run reliably on hardware that does not support multiple |
| 1407 | OpenGL contexts because the live wallpaper use of an OpenGL context may |
| 1408 | conflict with other applications that also use an OpenGL context.</p> |
| 1409 | |
| 1410 | <p>Device implementations capable of running live wallpapers reliably as described |
| 1411 | above SHOULD implement live wallpapers, and when implemented MUST report the |
| 1412 | platform feature flag android.software.live_wallpaper.</p> |
| 1413 | |
| 1414 | <h3 id="3_8_8_activity_switching">3.8.8. Activity Switching</h3> |
| 1415 | |
| 1416 | <div class="note"> |
| 1417 | <p>As the Recent function navigation key is OPTIONAL, the requirements to |
| 1418 | implement the overview screen is OPTIONAL for Android Television devices and |
| 1419 | Android Watch devices.</p> |
| 1420 | </div> |
| 1421 | |
| 1422 | |
| 1423 | <p>The upstream Android source code includes the overview screen [<a href="http://developer.android.com/guide/components/recents.html">Resources, 32</a>], a system-level user interface for task switching and displaying recently |
| 1424 | accessed activities and tasks using a thumbnail image of the application’s |
| 1425 | graphical state at the moment the user last left the application. Device |
| 1426 | implementations including the recents function navigation key as detailed in <a href="#7_2_3_navigation_keys">section 7.2.3</a>, MAY alter the interface but MUST meet the following requirements:</p> |
| 1427 | |
| 1428 | <ul> |
| 1429 | <li>MUST display affiliated recents as a group that moves together.</li> |
| 1430 | <li>MUST support at least up to 20 displayed activities.</li> |
| 1431 | <li>MUST at least display the title of 4 activities at a time.</li> |
| 1432 | <li>SHOULD display highlight color, icon, screen title in recents.</li> |
| 1433 | <li>MUST implement the screen pinning behavior [<a href="http://developer.android.com/about/versions/android-5.0.html#ScreenPinning">Resources, 33</a>] and provide the user with a settings menu to toggle the feature.</li> |
| 1434 | <li>SHOULD display a closing affordance ("x") but MAY delay this until user |
| 1435 | interacts with screens.</li> |
| 1436 | </ul> |
| 1437 | |
Bert McMeen | 816a242 | 2015-09-29 16:33:19 -0700 | [diff] [blame] | 1438 | <p>Device implementations are STRONGLY RECOMMENDED to use the upstream Android user |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 1439 | interface (or a similar thumbnail-based interface) for the overview screen.</p> |
| 1440 | |
| 1441 | <h3 id="3_8_9_input_management">3.8.9. Input Management</h3> |
| 1442 | |
| 1443 | |
| 1444 | <p>Android includes support for Input Management and support for third-party input |
| 1445 | method editors [<a href="http://developer.android.com/guide/topics/text/creating-input-method.html">Resources, 34</a>]. Device implementations that allow users to use third-party input methods on |
| 1446 | the device MUST declare the platform feature android.software.input_methods and |
| 1447 | support IME APIs as defined in the Android SDK documentation.</p> |
| 1448 | |
| 1449 | <p>Device implementations that declare the android.software.input_methods feature |
| 1450 | MUST provide a user-accessible mechanism to add and configure third-party input |
| 1451 | methods. Device implementations MUST display the settings interface in response |
| 1452 | to the android.settings.INPUT_METHOD_SETTINGS intent.</p> |
| 1453 | |
| 1454 | <h3 id="3_8_10_lock_screen_media_control">3.8.10. Lock Screen Media Control</h3> |
| 1455 | |
| 1456 | |
| 1457 | <p>The Remote Control Client API is deprecated from Android 5.0 in favor of the |
| 1458 | Media Notification Template that allows media applications to integrate with |
| 1459 | playback controls that are displayed on the lock screen [<a href="http://developer.android.com/reference/android/app/Notification.MediaStyle.html">Resources, 35</a>]. |
| 1460 | Device implementations that support a lock screen, unless an Android Automotive or Watch |
| 1461 | implementation, MUST display the Lockscreen Notifications including the Media Notification |
| 1462 | Template.</p> |
| 1463 | |
| 1464 | <h3 id="3_8_11_dreams">3.8.11. Dreams</h3> |
| 1465 | |
| 1466 | |
| 1467 | <p>Android includes support for interactive screensavers called Dreams [<a href="http://developer.android.com/reference/android/service/dreams/DreamService.html">Resources, 36</a>]. Dreams allows users to interact with applications when a device connected to |
| 1468 | a power source is idle or docked in a desk dock. Android Watch devices MAY |
| 1469 | implement Dreams, but other types of device implementations SHOULD include |
| 1470 | support for Dreams and provide a settings option for users to configure Dreams |
| 1471 | in response to the android.settings.DREAM_SETTINGS intent.</p> |
| 1472 | |
| 1473 | <h3 id="3_8_12_location">3.8.12. Location</h3> |
| 1474 | |
| 1475 | |
| 1476 | <p>When a device has a hardware sensor (e.g. GPS) that is capable of providing the |
| 1477 | location coordinates, location modes MUST be displayed in the Location menu |
| 1478 | within Settings [<a href="http://developer.android.com/reference/android/provider/Settings.Secure.html#LOCATION_MODE">Resources, 37</a>].</p> |
| 1479 | |
| 1480 | <h3 id="3_8_13_unicode_and_font">3.8.13. Unicode and Font</h3> |
| 1481 | |
| 1482 | |
| 1483 | <p>Android includes support for color emoji characters. When Android device |
| 1484 | implementations include an IME, devices SHOULD provide an input method to the |
| 1485 | user for the Emoji characters defined in Unicode 6.1 [<a href="http://www.unicode.org/versions/Unicode6.1.0/">Resources, 38</a>]. All devices MUST be capable of rendering these emoji characters in color glyph.</p> |
| 1486 | |
| 1487 | <p>Android includes support for Roboto 2 font with different |
| 1488 | weights—sans-serif-thin, sans-serif-light, sans-serif-medium, sans-serif-black, |
| 1489 | sans-serif-condensed, sans-serif-condensed-light—which MUST all be included for |
| 1490 | the languages available on the device and full Unicode 7.0 coverage of Latin, |
| 1491 | Greek, and Cyrillic, including the Latin Extended A, B, C, and D ranges, and |
| 1492 | all glyphs in the currency symbols block of Unicode 7.0.</p> |
| 1493 | |
| 1494 | <h2 id="3_9_device_administration">3.9. Device Administration</h2> |
| 1495 | |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 1496 | <p>Android includes features that allow security-aware applications to perform |
| 1497 | device administration functions at the system level, such as enforcing password |
| 1498 | policies or performing remote wipe, through the Android Device Administration |
| 1499 | API [<a href="http://developer.android.com/guide/topics/admin/device-admin.html">Resources, 39</a>]. |
| 1500 | Device implementations MUST provide an implementation of the DevicePolicyManager class |
| 1501 | [<a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html">Resources, 40</a>]. |
| 1502 | Device implementations that include support for PIN (numeric) or PASSWORD |
| 1503 | (alphanumeric) based lock screens MUST support the full range of device |
| 1504 | administration policies defined in the Android SDK documentation |
| 1505 | [<a href="http://developer.android.com/guide/topics/admin/device-admin.html">Resources, 39</a>] |
| 1506 | and report the platform feature android.software.device_admin.</p> |
| 1507 | |
Andy Dyer-smith | 3d24bbe | 2015-09-11 15:35:23 +0100 | [diff] [blame] | 1508 | <h3 id="3_9_1_device_provisioning">3.9.1 Device Provisioning</h3> |
| 1509 | <h4 id="3_9_1_1_device_owner_provisioning">3.9.1.1 Device owner provisioning</h4> |
| 1510 | <p>If a device implementation declares the android.software.device_admin feature, |
| 1511 | the out of box setup flow MUST make it possible to enroll a Device Policy |
| 1512 | Controller (DPC) application as the Device Owner app |
| 1513 | [<a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#isDeviceOwnerApp(java.lang.String)"> |
| 1514 | Resources, XX</a>]. Device implementations MAY have a preinstalled application |
| 1515 | performing device administration functions but this application MUST NOT be set |
| 1516 | as the Device Owner app without explicit consent or action from the user or the |
| 1517 | administrator of the device.</p> |
| 1518 | |
| 1519 | <p>The device owner provisioning process (the flow initiated by |
| 1520 | android.app.action.PROVISION_MANAGED_DEVICE |
| 1521 | [<a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#ACTION_PROVISION_MANAGED_DEVICE"> |
| 1522 | Resources, XX</a>]) user experience MUST align with the AOSP implementation</p> |
| 1523 | |
| 1524 | <p>If the device implementation reports android.hardware.nfc, it MUST have NFC |
| 1525 | enabled, even during the out-of-box setup flow, in order to allow for NFC |
| 1526 | provisioning of Device owners |
| 1527 | <a href="https://source.android.com/devices/tech/admin/provision.html#device_owner_provisioning_via_nfc">[Resources, XX]</a>. |
| 1528 | </p> |
| 1529 | |
| 1530 | <h4 id="3_9_1_2_managed_profile_provisioning">3.9.1.2 Managed profile provisioning</h4> |
| 1531 | <p>If a device implementation declares the android.software.managed_users, |
| 1532 | it MUST be possible to enroll a Device Policy Controller (DPC) application |
| 1533 | as the owner of a new Managed Profile |
| 1534 | [<a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#isProfileOwnerApp(java.lang.String)"> |
| 1535 | Resources, XX</a>]</p> |
| 1536 | |
| 1537 | <p>The managed profile provisioning process (the flow initiated by |
| 1538 | android.app.action.PROVISION_MANAGED_PROFILE |
| 1539 | [<a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#ACTION_PROVISION_MANAGED_PROFILE"> |
| 1540 | Resources, XX</a>]) user experience MUST align with the AOSP implementation |
| 1541 | </p> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 1542 | |
| 1543 | <h2 id="3_10_accessibility">3.10. Accessibility</h2> |
| 1544 | |
| 1545 | |
| 1546 | <p>Android provides an accessibility layer that helps users with disabilities to |
| 1547 | navigate their devices more easily. In addition, Android provides platform APIs |
| 1548 | that enable accessibility service implementations to receive callbacks for user |
| 1549 | and system events and generate alternate feedback mechanisms, such as |
| 1550 | text-to-speech, haptic feedback, and trackball/d-pad navigation [<a href="http://developer.android.com/reference/android/accessibilityservice/AccessibilityService.html">Resources, 42</a>].</p> |
| 1551 | |
| 1552 | <p>Device implementations include the following requirements:</p> |
| 1553 | |
| 1554 | <ul> |
| 1555 | <li>Android Automotive implementations SHOULD provide an implementation of the |
| 1556 | Android accessibility framework consistent with the default Android |
| 1557 | implementation.</li> |
| 1558 | <li>Device implementations (Android Automotive excluded) MUST provide an |
| 1559 | implementation of the Android accessibility framework consistent with the |
| 1560 | default Android implementation.</li> |
| 1561 | <li>Device implementations (Android Automotive excluded) MUST support |
| 1562 | third-party accessibility service implementations through the |
| 1563 | android.accessibilityservice APIs |
| 1564 | [<a href="http://developer.android.com/reference/android/view/accessibility/package-summary.html">Resources, 43</a>]</li> |
| 1565 | <li>Device implementations (Android Automotive excluded) MUST generate |
| 1566 | AccessibilityEvents and deliver these events to all registered |
| 1567 | AccessibilityService implementations in a manner consistent with the default |
| 1568 | Android implementation</li> |
| 1569 | <li> Device implementations (Android Automotive and Android Watch devices with |
| 1570 | no audio output excluded), MUST provide a user-accessible mechanism to enable |
| 1571 | and disable accessibility services, and MUST display this interface in response |
| 1572 | to the android.provider.Settings.ACTION_ACCESSIBILITY_SETTINGS intent.</li> |
| 1573 | </ul> |
| 1574 | |
| 1575 | <p>Additionally, device implementations SHOULD provide an implementation of an |
| 1576 | accessibility service on the device, and SHOULD provide a mechanism for users |
| 1577 | to enable the accessibility service during device setup. An open source |
| 1578 | implementation of an accessibility service is available from the Eyes Free |
| 1579 | project [<a href="http://code.google.com/p/eyes-free/">Resources, 44</a>].</p> |
| 1580 | |
| 1581 | <h2 id="3_11_text-to-speech">3.11. Text-to-Speech</h2> |
| 1582 | |
| 1583 | |
| 1584 | <p>Android includes APIs that allow applications to make use of text-to-speech |
| 1585 | (TTS) services and allows service providers to provide implementations of TTS |
| 1586 | services [<a href="http://developer.android.com/reference/android/speech/tts/package-summary.html">Resources, 45</a>]. Device implementations reporting the feature android.hardware.audio.output |
| 1587 | MUST meet these requirements related to the Android TTS framework. </p> |
| 1588 | |
| 1589 | <p>Android Automotive implementations:</p> |
| 1590 | <ul> |
| 1591 | <li>MUST support the Android TTS framework APIs.</li> |
| 1592 | <li>MAY support installation of third-party TTS engines. If supported, partners |
| 1593 | MUST provide a user-accessible interface that allows the user to select a TTS |
| 1594 | engine for use at system level.</li> |
| 1595 | </ul> |
| 1596 | |
| 1597 | <p>All other device implementations:</p> |
| 1598 | |
| 1599 | <ul> |
| 1600 | <li> MUST support the Android TTS framework APIs and SHOULD include a TTS engine |
| 1601 | supporting the languages available on the device. Note that the upstream |
| 1602 | Android open source software includes a full-featured TTS engine |
| 1603 | implementation. |
| 1604 | <li> MUST support installation of third-party TTS engines |
| 1605 | <li> MUST provide a user-accessible interface that allows users to select a TTS |
| 1606 | engine for use at the system level |
| 1607 | </ul> |
| 1608 | |
| 1609 | <h2 id="3_12_tv_input_framework">3.12. TV Input Framework</h2> |
| 1610 | |
| 1611 | |
| 1612 | <p>The Android Television Input Framework (TIF) simplifies the delivery of live |
| 1613 | content to Android Television devices. TIF provides a standard API to create |
| 1614 | input modules that control Android Television devices. Android Television |
| 1615 | device implementations MUST support Television Input Framework [<a href="http://source.android.com/devices/tv/index.html">Resources, 46</a>].</p> |
| 1616 | |
| 1617 | <p>Device implementations that support TIF MUST declare the platform feature |
| 1618 | android.software.live_tv.</p> |
| 1619 | |
| 1620 | <h1 id="4_application_packaging_compatibility">4. Application Packaging Compatibility</h1> |
| 1621 | |
| 1622 | |
| 1623 | <p>Device implementations MUST install and run Android “.apk” files as generated |
| 1624 | by the “aapt” tool included in the official Android SDK [<a href="http://developer.android.com/tools/help/index.html">Resources, 47</a>].</p> |
| 1625 | |
| 1626 | <p>Devices implementations MUST NOT extend either the .apk [<a href="http://developer.android.com/guide/components/fundamentals.html">Resources, 48</a>], Android Manifest [<a href="http://developer.android.com/guide/topics/manifest/manifest-intro.html">Resources, 49</a>], Dalvik bytecode [<a href="https://android.googlesource.com/platform/dalvik/+/lollipop-release/docs/">Resources, 20</a>], or RenderScript bytecode formats in such a way that would prevent those |
| 1627 | files from installing and running correctly on other compatible devices.</p> |
| 1628 | |
| 1629 | <h1 id="5_multimedia_compatibility">5. Multimedia Compatibility</h1> |
| 1630 | |
| 1631 | |
| 1632 | <h2 id="5_1_media_codecs">5.1. Media Codecs</h2> |
| 1633 | |
| 1634 | |
| 1635 | <p>Device implementations MUST support the core media formats specified in the |
| 1636 | Android SDK documentation [<a href="http://developer.android.com/guide/appendix/media-formats.html">Resources, 50</a>] except where explicitly permitted in this document. Specifically, device |
| 1637 | implementations MUST support the media formats, encoders, decoders, file types, |
| 1638 | and container formats defined in the tables below and reported via MediaCodecList |
| 1639 | [<a href="http://developer.android.com/reference/android/media/MediaCodecList.html">Resources,112</a>]. |
| 1640 | Device implementations MUST also be able to decode all profiles reported in its CamcorderProfile |
| 1641 | [<a href="http://developer.android.com/reference/android/media/CamcorderProfile.html">Resources, |
| 1642 | 113</a>]. |
| 1643 | |
| 1644 | All of these codecs are |
| 1645 | provided as software implementations in the preferred Android implementation |
| 1646 | from the Android Open Source Project.</p> |
| 1647 | |
| 1648 | <p>Please note that neither Google nor the Open Handset Alliance make any |
| 1649 | representation that these codecs are free from third-party patents. Those |
| 1650 | intending to use this source code in hardware or software products are advised |
| 1651 | that implementations of this code, including in open source software or |
| 1652 | shareware, may require patent licenses from the relevant patent holders.</p> |
| 1653 | |
| 1654 | <h3 id="5_1_1_audio_codecs">5.1.1. Audio Codecs</h3> |
| 1655 | |
| 1656 | <table> |
| 1657 | <tr> |
| 1658 | <th>Format/Codec</th> |
| 1659 | <th>Encoder</th> |
| 1660 | <th>Decoder</th> |
| 1661 | <th>Details</th> |
| 1662 | <th>Supported File Types/Container Formats</th> |
| 1663 | </tr> |
| 1664 | <tr> |
| 1665 | <td>MPEG-4 AAC Profile</p> |
| 1666 | |
| 1667 | <p>(AAC LC)</td> |
| 1668 | <td>REQUIRED<sup>1</sup></td> |
| 1669 | <td>REQUIRED</td> |
Unsuk Jung | 2e62f9a | 2015-07-16 23:01:44 -0700 | [diff] [blame] | 1670 | <td>Support for mono/stereo/5.0/5.1<sup>2</sup> content with standard sampling rates from 8 to |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 1671 | 48 kHz.</td> |
| 1672 | <td> |
| 1673 | <ul> |
| 1674 | <li class="table_list">3GPP (.3gp)</li> |
| 1675 | <li class="table_list">MPEG-4 (.mp4, .m4a)</li> |
| 1676 | <li class="table_list">ADTS raw AAC (.aac, decode in Android 3.1+, encode in Android 4.0+, ADIF not |
| 1677 | supported)</li> |
| 1678 | <li class="table_list">MPEG-TS (.ts, not seekable, Android 3.0+)</li></ul></td> |
| 1679 | </tr> |
| 1680 | <tr> |
| 1681 | <td>MPEG-4 HE AAC Profile (AAC+)</td> |
| 1682 | <td>REQUIRED<sup>1</sup><br>(Android 4.1+)</td> |
| 1683 | <td>REQUIRED</td> |
Unsuk Jung | 2e62f9a | 2015-07-16 23:01:44 -0700 | [diff] [blame] | 1684 | <td>Support for mono/stereo/5.0/5.1<sup>2</sup> content with standard sampling rates from 16 |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 1685 | to 48 kHz.</td> |
| 1686 | <td></td> |
| 1687 | </tr> |
| 1688 | <tr> |
| 1689 | <td>MPEG-4 HE AACv2</p> |
| 1690 | |
| 1691 | <p>Profile (enhanced AAC+)</td> |
| 1692 | <td> </td> |
| 1693 | <td>REQUIRED</td> |
Unsuk Jung | 2e62f9a | 2015-07-16 23:01:44 -0700 | [diff] [blame] | 1694 | <td>Support for mono/stereo/5.0/5.1<sup>2</sup> content with standard sampling rates from 16 |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 1695 | to 48 kHz.</td> |
| 1696 | <td></td> |
| 1697 | </tr> |
| 1698 | <tr> |
| 1699 | <td>AAC ELD (enhanced low delay AAC)</td> |
| 1700 | <td>REQUIRED<sup>1</sup> </p> |
| 1701 | |
| 1702 | <p>(Android 4.1+)</td> |
| 1703 | <td>REQUIRED</p> |
| 1704 | |
| 1705 | <p>(Android 4.1+)</td> |
| 1706 | <td>Support for mono/stereo content with standard sampling rates from 16 to 48 kHz.</td> |
| 1707 | <td></td> |
| 1708 | </tr> |
| 1709 | <tr> |
| 1710 | <td>AMR-NB</td> |
| 1711 | <td>REQUIRED<sup>3</sup></td> |
| 1712 | <td>REQUIRED<sup>3</sup></td> |
Glenn Kasten | 20cdbb7 | 2015-09-24 11:56:42 -0700 | [diff] [blame^] | 1713 | <td>4.75 to 12.2 kbps sampled @ 8 kHz</td> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 1714 | <td>3GPP (.3gp)</td> |
| 1715 | </tr> |
| 1716 | <tr> |
| 1717 | <td>AMR-WB</td> |
| 1718 | <td>REQUIRED<sup>3</sup></td> |
| 1719 | <td>REQUIRED<sup>3</sup></td> |
Glenn Kasten | 20cdbb7 | 2015-09-24 11:56:42 -0700 | [diff] [blame^] | 1720 | <td>9 rates from 6.60 kbit/s to 23.85 kbit/s sampled @ 16 kHz</td> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 1721 | <td></td> |
| 1722 | </tr> |
| 1723 | <tr> |
| 1724 | <td>FLAC</td> |
| 1725 | <td></td> |
| 1726 | <td>REQUIRED <br>(Android 3.1+)</td> |
| 1727 | <td>Mono/Stereo (no multichannel). Sample rates up to 48 kHz (but up to 44.1 kHz is |
Bert McMeen | 816a242 | 2015-09-29 16:33:19 -0700 | [diff] [blame] | 1728 | RECOMMENDED on devices with 44.1 kHz output, as the 48 to 44.1 kHz downsampler |
| 1729 | does not include a low-pass filter). 16-bit RECOMMENDED; no dither applied for |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 1730 | 24-bit.</td> |
| 1731 | <td>FLAC (.flac) only</td> |
| 1732 | </tr> |
| 1733 | <tr> |
| 1734 | <td>MP3</td> |
| 1735 | <td></td> |
| 1736 | <td>REQUIRED</td> |
| 1737 | <td>Mono/Stereo 8-320Kbps constant (CBR) or variable bitrate (VBR)</td> |
| 1738 | <td>MP3 (.mp3)</td> |
| 1739 | </tr> |
| 1740 | <tr> |
| 1741 | <td>MIDI</td> |
| 1742 | <td></td> |
| 1743 | <td>REQUIRED</td> |
| 1744 | <td>MIDI Type 0 and 1. DLS Version 1 and 2. XMF and Mobile XMF. Support for |
| 1745 | ringtone formats RTTTL/RTX, OTA, and iMelody</td> |
| 1746 | <td><ul> |
| 1747 | <li class="table_list">Type 0 and 1 (.mid, .xmf, .mxmf)</li> |
| 1748 | <li class="table_list">RTTTL/RTX (.rtttl, .rtx)</li> |
| 1749 | <li class="table_list">OTA (.ota)</li> |
| 1750 | <li class="table_list">iMelody (.imy)</li></ul></td> |
| 1751 | </tr> |
| 1752 | <tr> |
| 1753 | <td>Vorbis</td> |
| 1754 | <td></td> |
| 1755 | <td>REQUIRED</td> |
| 1756 | <td></td> |
| 1757 | <td><ul> |
| 1758 | <li class="table_list">Ogg (.ogg)</li> |
| 1759 | <li class="table_list">Matroska (.mkv, Android 4.0+)</li></ul></td> |
| 1760 | </tr> |
| 1761 | <tr> |
| 1762 | <td>PCM/WAVE</td> |
| 1763 | <td>REQUIRED<sup>4</sup><br> (Android 4.1+)</td> |
| 1764 | <td>REQUIRED</td> |
| 1765 | <td>16-bit linear PCM (rates up to limit of hardware). Devices MUST support |
| 1766 | sampling rates for raw PCM recording at 8000, 11025, 16000, and 44100 Hz |
| 1767 | frequencies.</td> |
| 1768 | <td>WAVE (.wav)</td> |
| 1769 | </tr> |
| 1770 | <tr> |
| 1771 | <td>Opus</td> |
| 1772 | <td></td> |
| 1773 | <td>REQUIRED<br> (Android 5.0+)</td> |
| 1774 | <td></td> |
| 1775 | <td>Matroska (.mkv)</td> |
| 1776 | </tr> |
| 1777 | </table> |
| 1778 | |
| 1779 | |
| 1780 | <p class="table_footnote"> 1 Required for device implementations that define android.hardware.microphone |
| 1781 | but optional for Android Watch device implementations.</p> |
| 1782 | |
| 1783 | <p class="table_footnote">2 Only downmix of 5.0/5.1 content is required; recording or rendering more than |
| 1784 | 2 channels is optional.</p> |
| 1785 | |
| 1786 | <p class="table_footnote">3 Required for Android Handheld device implementations. </p> |
| 1787 | |
| 1788 | <p class="table_footnote">4 Required for device implementations that define android.hardware.microphone, |
| 1789 | including Android Watch device implementations.</p> |
| 1790 | |
| 1791 | <h3 id="5_1_2_image_codecs">5.1.2. Image Codecs</h3> |
| 1792 | |
| 1793 | <table> |
| 1794 | <tr> |
| 1795 | <th>Format/Codec</th> |
| 1796 | <th>Encoder</th> |
| 1797 | <th>Decoder</th> |
| 1798 | <th>Details</th> |
| 1799 | <th>Supported File Types/Container Formats</th> |
| 1800 | </tr> |
| 1801 | <tr> |
| 1802 | <td>JPEG</td> |
| 1803 | <td>REQUIRED</td> |
| 1804 | <td>REQUIRED</td> |
| 1805 | <td>Base+progressive</td> |
| 1806 | <td>JPEG (.jpg)</td> |
| 1807 | </tr> |
| 1808 | <tr> |
| 1809 | <td>GIF</td> |
| 1810 | <td></td> |
| 1811 | <td>REQUIRED</td> |
| 1812 | <td></td> |
| 1813 | <td>GIF (.gif)</td> |
| 1814 | </tr> |
| 1815 | <tr> |
| 1816 | <td>PNG</td> |
| 1817 | <td>REQUIRED</td> |
| 1818 | <td>REQUIRED</td> |
| 1819 | <td></td> |
| 1820 | <td>PNG (.png)</td> |
| 1821 | </tr> |
| 1822 | <tr> |
| 1823 | <td>BMP</td> |
| 1824 | <td></td> |
| 1825 | <td>REQUIRED</td> |
| 1826 | <td></td> |
| 1827 | <td>BMP (.bmp)</td> |
| 1828 | </tr> |
| 1829 | <tr> |
| 1830 | <td>WebP</td> |
| 1831 | <td>REQUIRED</td> |
| 1832 | <td>REQUIRED</td> |
| 1833 | <td></td> |
| 1834 | <td>WebP (.webp)</td> |
| 1835 | </tr> |
| 1836 | </table> |
| 1837 | |
| 1838 | |
| 1839 | <h3 id="5_1_3_video_codecs">5.1.3. Video Codecs</h3> |
| 1840 | |
| 1841 | <p>Video codecs are optional for Android Watch device implementations.</p> |
| 1842 | |
| 1843 | <table> |
| 1844 | <tr> |
| 1845 | <th>Format/Codec</th> |
| 1846 | <th>Encoder</th> |
| 1847 | <th>Decoder</th> |
| 1848 | <th>Details</th> |
| 1849 | <th>Supported File Types/<br>Container Formats</th> |
| 1850 | </tr> |
| 1851 | <tr> |
| 1852 | <td>H.263</td> |
| 1853 | <td>REQUIRED<sup>1</sup></td> |
| 1854 | <td>REQUIRED<sup>2</sup></td> |
| 1855 | <td></td> |
| 1856 | <td><ul> |
| 1857 | <li class="table_list">3GPP (.3gp)</li> |
| 1858 | <li class="table_list">MPEG-4 (.mp4)</li></ul></td> |
| 1859 | </tr> |
| 1860 | <tr> |
| 1861 | <td>H.264 AVC</td> |
| 1862 | <td>REQUIRED<sup>2</sup></td> |
| 1863 | <td>REQUIRED<sup>2</sup></td> |
| 1864 | <td>See <a href="#5_2_video_encoding">section 5.2 </a>and <a href="#5_3_video_decoding">5.3</a> for details</td> |
| 1865 | <td><ul> |
| 1866 | <li class="table_list">3GPP (.3gp)</li> |
| 1867 | <li class="table_list">MPEG-4 (.mp4)</li> |
| 1868 | <li class="table_list">MPEG-TS (.ts, AAC audio only, not seekable, Android 3.0+)</li></ul></td> |
| 1869 | </tr> |
| 1870 | <tr> |
| 1871 | <td>H.265 HEVC</td> |
| 1872 | <td></td> |
| 1873 | <td>REQUIRED<sup>5</sup></td> |
| 1874 | <td>See <a href="#5_3_video_decoding">section 5.3</a> for details</td> |
| 1875 | <td>MPEG-4 (.mp4)</td> |
| 1876 | </tr> |
| 1877 | <tr> |
| 1878 | <td>MPEG-4 SP</td> |
| 1879 | <td></td> |
| 1880 | <td>REQUIRED<sup>2</sup></td> |
| 1881 | <td></td> |
| 1882 | <td>3GPP (.3gp)</td> |
| 1883 | </tr> |
| 1884 | <tr> |
Unsuk Jung | 2e62f9a | 2015-07-16 23:01:44 -0700 | [diff] [blame] | 1885 | <td>VP8<sup>3</sup></td> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 1886 | <td>REQUIRED<sup>2</sup></p> |
| 1887 | |
| 1888 | <p>(Android 4.3+)</td> |
| 1889 | <td>REQUIRED<sup>2</sup></p> |
| 1890 | |
| 1891 | <p>(Android 2.3.3+)</td> |
| 1892 | <td>See <a href="#5_2_video_encoding">section 5.2</a> and <a href="#5_3_video_decoding">5.3</a> for details</td> |
| 1893 | <td><ul> |
| 1894 | <li class="table_list">WebM (.webm) [<a href="http://www.webmproject.org/">Resources, 110</a></li> |
Unsuk Jung | 2e62f9a | 2015-07-16 23:01:44 -0700 | [diff] [blame] | 1895 | <li class="table_list">Matroska (.mkv, Android 4.0+)<sup>4</sup></li></ul></td> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 1896 | </tr> |
| 1897 | <tr> |
| 1898 | <td>VP9</td> |
| 1899 | <td></td> |
| 1900 | <td>REQUIRED<sup>2</sup><br> (Android 4.4+)</td> |
| 1901 | <td>See <a href="#5_3_video_decoding">section 5.3</a> for details</td> |
| 1902 | <td><ul> |
| 1903 | <li class="table_list">WebM (.webm) [<a href="http://www.webmproject.org/">Resources, 110</a>]</li> |
Unsuk Jung | 2e62f9a | 2015-07-16 23:01:44 -0700 | [diff] [blame] | 1904 | <li class="table_list">Matroska (.mkv, Android 4.0+)<sup>4</sup></li></ul></td> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 1905 | </tr> |
| 1906 | </table> |
| 1907 | |
| 1908 | |
| 1909 | <p class="table_footnote">1 Required for device implementations that include camera hardware and define |
| 1910 | android.hardware.camera or android.hardware.camera.front.</p> |
| 1911 | |
| 1912 | <p class="table_footnote">2 Required for device implementations except Android Watch devices. </p> |
| 1913 | |
| 1914 | <p class="table_footnote">3 For acceptable quality of web video streaming and video-conference services, |
| 1915 | device implementations SHOULD use a hardware VP8 codec that meets the |
| 1916 | requirements in [<a href="http://www.webmproject.org/hardware/rtc-coding-requirements/">Resources, 51</a>].</p> |
| 1917 | |
| 1918 | <p class="table_footnote">4 Device implementations SHOULD support writing Matroska WebM files.</p> |
| 1919 | |
Bert McMeen | 816a242 | 2015-09-29 16:33:19 -0700 | [diff] [blame] | 1920 | <p class="table_footnote">5 STRONGLY RECOMMENDED for Android Automotive, optional for Android Watch, and required for all other device types.</p> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 1921 | |
| 1922 | <h2 id="5_2_video_encoding">5.2. Video Encoding</h2> |
| 1923 | |
| 1924 | <div class="note"> |
| 1925 | <p>Video codecs are optional for Android Watch device implementations.</p> |
| 1926 | </div> |
| 1927 | |
| 1928 | |
| 1929 | <p>Android device implementations with H.264 codec support, MUST support Baseline |
| 1930 | Profile Level 3 and the following SD (Standard Definition) video encoding |
| 1931 | profiles and SHOULD support Main Profile Level 4 and the following HD (High |
| 1932 | Definition) video encoding profiles. Android Television devices are STRONGLY |
| 1933 | RECOMMENDED to encode HD 1080p video at 30 fps.</p> |
| 1934 | <table> |
| 1935 | <tr> |
| 1936 | <th></th> |
| 1937 | <th>SD (Low quality)</th> |
| 1938 | <th>SD (High quality)</th> |
| 1939 | <th>HD 720p1</th> |
| 1940 | <th>HD 1080p1</th> |
| 1941 | </tr> |
| 1942 | <tr> |
| 1943 | <th>Video resolution</th> |
| 1944 | <td>320 x 240 px</td> |
| 1945 | <td>720 x 480 px</td> |
| 1946 | <td>1280 x 720 px</td> |
| 1947 | <td>1920 x 1080 px</td> |
| 1948 | </tr> |
| 1949 | <tr> |
| 1950 | <th>Video frame rate</th> |
| 1951 | <td>20 fps</td> |
| 1952 | <td>30 fps</td> |
| 1953 | <td>30 fps</td> |
| 1954 | <td>30 fps</td> |
| 1955 | </tr> |
| 1956 | <tr> |
| 1957 | <th>Video bitrate</th> |
| 1958 | <td>384 Kbps</td> |
| 1959 | <td>2 Mbps</td> |
| 1960 | <td>4 Mbps</td> |
| 1961 | <td>10 Mbps</td> |
| 1962 | </tr> |
| 1963 | </table> |
| 1964 | |
| 1965 | |
| 1966 | <p class="table_footnote">1 When supported by hardware, but STRONGLY RECOMMENDED for Android Television |
| 1967 | devices.</p> |
| 1968 | |
| 1969 | <p>Android device implementations with VP8 codec support MUST support the SD video |
| 1970 | encoding profiles and SHOULD support the following HD (High Definition) video |
| 1971 | encoding profiles.</p> |
| 1972 | <table> |
| 1973 | <tr> |
| 1974 | <th></th> |
| 1975 | <th>SD (Low quality)</th> |
| 1976 | <th>SD (High quality)</th> |
| 1977 | <th>HD 720p1</th> |
| 1978 | <th>HD 1080p1</th> |
| 1979 | </tr> |
| 1980 | <tr> |
| 1981 | <th>Video resolution</th> |
| 1982 | <td>320 x 180 px</td> |
| 1983 | <td>640 x 360 px</td> |
| 1984 | <td>1280 x 720 px</td> |
| 1985 | <td>1920 x 1080 px</td> |
| 1986 | </tr> |
| 1987 | <tr> |
| 1988 | <th>Video frame rate</th> |
| 1989 | <td>30 fps</td> |
| 1990 | <td>30 fps</td> |
| 1991 | <td>30 fps</td> |
| 1992 | <td>30 fps</td> |
| 1993 | </tr> |
| 1994 | <tr> |
| 1995 | <th>Video bitrate</th> |
| 1996 | <td>800 Kbps </td> |
| 1997 | <td>2 Mbps</td> |
| 1998 | <td>4 Mbps</td> |
| 1999 | <td>10 Mbps</td> |
| 2000 | </tr> |
| 2001 | </table> |
| 2002 | |
| 2003 | <p class="table_footnote">1 When supported by hardware.</p> |
| 2004 | |
| 2005 | <h2 id="5_3_video_decoding">5.3. Video Decoding</h2> |
| 2006 | |
| 2007 | <div class="note"> |
| 2008 | <p>Video codecs are optional for Android Watch device implementations.</p> |
| 2009 | </div> |
| 2010 | |
| 2011 | |
| 2012 | <p>Device implementations MUST support dynamic video resolution switching within |
Unsuk Jung | 2e62f9a | 2015-07-16 23:01:44 -0700 | [diff] [blame] | 2013 | the same stream for all VP8, VP9, H.264, and H.265 codecs exposed through the |
| 2014 | standard Android APIs.</p> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 2015 | |
| 2016 | <p>Android device implementations with H.264 decoders, MUST support Baseline |
| 2017 | Profile Level 3 and the following SD video decoding profiles and SHOULD support |
| 2018 | the HD decoding profiles. Android Television devices MUST support High Profile |
| 2019 | Level 4.2 and the HD 1080p decoding profile.</p> |
| 2020 | <table> |
| 2021 | <tr> |
| 2022 | <th></th> |
| 2023 | <th>SD (Low quality)</th> |
| 2024 | <th>SD (High quality)</th> |
| 2025 | <th>HD 720p1</th> |
| 2026 | <th>HD 1080p1</th> |
| 2027 | </tr> |
| 2028 | <tr> |
| 2029 | <th>Video resolution</th> |
| 2030 | <td>320 x 240 px</td> |
| 2031 | <td>720 x 480 px</td> |
| 2032 | <td>1280 x 720 px</td> |
| 2033 | <td>1920 x 1080 px</td> |
| 2034 | </tr> |
| 2035 | <tr> |
| 2036 | <th>Video frame rate</th> |
| 2037 | <td>30 fps</td> |
| 2038 | <td>30 fps</td> |
| 2039 | <td>30 fps / 60 fps2</td> |
| 2040 | <td>30 fps / 60 fps2</td> |
| 2041 | </tr> |
| 2042 | <tr> |
| 2043 | <th>Video bitrate</th> |
| 2044 | <td>800 Kbps </td> |
| 2045 | <td>2 Mbps</td> |
| 2046 | <td>8 Mbps</td> |
| 2047 | <td>20 Mbps</td> |
| 2048 | </tr> |
| 2049 | </table> |
| 2050 | |
| 2051 | |
| 2052 | <p class="table_footnote">1 Required for Android Television device implementations, but for other device |
| 2053 | types only when supported by hardware.</p> |
| 2054 | |
| 2055 | <p class="table_footnote">2 Required for Android Television device implementations.</p> |
| 2056 | |
| 2057 | <p>Android device implementations when supporting VP8 codec as described in <a href="#5_1_3_video_codecs">section 5.1.3</a>, MUST support the following SD decoding profiles and SHOULD support the HD |
| 2058 | decoding profiles. Android Television devices MUST support the HD 1080p |
| 2059 | decoding profile. </p> |
| 2060 | <table> |
| 2061 | <tr> |
| 2062 | <th></th> |
| 2063 | <th>SD (Low quality)</th> |
| 2064 | <th>SD (High quality)</th> |
| 2065 | <th>HD 720p1</th> |
| 2066 | <th>HD 1080p1</th> |
| 2067 | </tr> |
| 2068 | <tr> |
| 2069 | <th>Video resolution</th> |
| 2070 | <td>320 x 180 px</td> |
| 2071 | <td>640 x 360 px</td> |
| 2072 | <td>1280 x 720 px</td> |
| 2073 | <td>1920 x 1080 px</td> |
| 2074 | </tr> |
| 2075 | <tr> |
| 2076 | <th>Video frame rate</th> |
| 2077 | <td>30 fps</td> |
| 2078 | <td>30 fps</td> |
| 2079 | <td>30 fps / 60 fps2</td> |
| 2080 | <td>30 / 60 fps2</td> |
| 2081 | </tr> |
| 2082 | <tr> |
| 2083 | <th>Video bitrate</th> |
| 2084 | <td>800 Kbps </td> |
| 2085 | <td>2 Mbps</td> |
| 2086 | <td>8 Mbps</td> |
| 2087 | <td>20 Mbps</td> |
| 2088 | </tr> |
| 2089 | </table> |
| 2090 | |
| 2091 | |
| 2092 | <p class="table_footnote">1 Required for Android Television device implementations, but for other type of |
| 2093 | devices only when supported by hardware.</p> |
| 2094 | |
| 2095 | <p class="table_footnote">2 Required for Android Television device implementations.</p> |
| 2096 | |
| 2097 | <p>Android device implementations, when supporting VP9 codec as described in <a href="#5_1_3_video_codecs">section 5.1.3</a>, MUST support the following SD video decoding profiles and SHOULD support the |
| 2098 | HD decoding profiles. Android Television devices are STRONGLY RECOMMENDED to |
| 2099 | support the HD 1080p decoding profile and SHOULD support the UHD decoding |
| 2100 | profile. When the UHD video decoding profile is supported, it MUST support 8 |
| 2101 | bit color depth.</p> |
| 2102 | <table> |
| 2103 | <tr> |
| 2104 | <th></th> |
| 2105 | <th>SD (Low quality)</th> |
| 2106 | <th>SD (High quality)</th> |
| 2107 | <th>HD 720p 1</th> |
| 2108 | <th>HD 1080p 2</th> |
| 2109 | <th>UHD 2</th> |
| 2110 | </tr> |
| 2111 | <tr> |
| 2112 | <th>Video resolution</th> |
| 2113 | <td>320 x 180 px</td> |
| 2114 | <td>640 x 360 px</td> |
| 2115 | <td>1280 x 720 px</td> |
| 2116 | <td>1920 x 1080 px</td> |
| 2117 | <td>3840 x 2160 px</td> |
| 2118 | </tr> |
| 2119 | <tr> |
| 2120 | <th>Video frame rate</th> |
| 2121 | <td>30 fps</td> |
| 2122 | <td>30 fps</td> |
| 2123 | <td>30 fps</td> |
| 2124 | <td>30 fps</td> |
| 2125 | <td>30 fps</td> |
| 2126 | </tr> |
| 2127 | <tr> |
| 2128 | <th>Video bitrate</th> |
| 2129 | <td>600 Kbps </td> |
| 2130 | <td>1.6 Mbps</td> |
| 2131 | <td>4 Mbps</td> |
| 2132 | <td>10 Mbps</td> |
| 2133 | <td>20 Mbps</td> |
| 2134 | </tr> |
| 2135 | </table> |
| 2136 | |
| 2137 | |
| 2138 | <p class="table_footnote">1 Required for Android Television device implementations, but for other type of |
| 2139 | devices only when supported by hardware.</p> |
| 2140 | |
| 2141 | <p class="table_footnote">2 STRONGLY RECOMMENDED for Android Television device implementations when |
| 2142 | supported by hardware.</p> |
| 2143 | |
| 2144 | <p>Android device implementations, when supporting H.265 codec as described in <a href="#5_1_3_video_codecs">section 5.1.3</a>, MUST support the Main Profile Level 3 Main tier and the following SD video |
| 2145 | decoding profiles and SHOULD support the HD decoding profiles. Android |
| 2146 | Television devices MUST support the Main Profile Level 4.1 Main tier and the HD |
| 2147 | 1080p decoding profile and SHOULD support Main10 Level 5 Main Tier profile and |
| 2148 | the UHD decoding profile.</p> |
| 2149 | <table> |
| 2150 | <tr> |
| 2151 | <th></th> |
| 2152 | <th>SD (Low quality)</th> |
| 2153 | <th>SD (High quality)</th> |
| 2154 | <th>HD 720p </strong>1 </td> |
| 2155 | <th>HD 1080p </strong>1 </td> |
| 2156 | <th>UHD </strong>2</td> |
| 2157 | </tr> |
| 2158 | <tr> |
| 2159 | <th>Video resolution</th> |
| 2160 | <td>352 x 288 px</td> |
| 2161 | <td>640 x 360 px</td> |
| 2162 | <td>1280 x 720 px</td> |
| 2163 | <td>1920 x 1080 px</td> |
| 2164 | <td>3840 x 2160 px</td> |
| 2165 | </tr> |
| 2166 | <tr> |
| 2167 | <th>Video frame rate</th> |
| 2168 | <td>30 fps</td> |
| 2169 | <td>30 fps</td> |
| 2170 | <td>30 fps</td> |
| 2171 | <td>30 fps</td> |
| 2172 | <td>30 fps</td> |
| 2173 | </tr> |
| 2174 | <tr> |
| 2175 | <th>Video bitrate</th> |
| 2176 | <td>600 Kbps </td> |
| 2177 | <td>1.6 Mbps</td> |
| 2178 | <td>4 Mbps</td> |
| 2179 | <td>10 Mbps</td> |
| 2180 | <td>20 Mbps</td> |
| 2181 | </tr> |
| 2182 | </table> |
| 2183 | |
| 2184 | |
| 2185 | <p class="table_footnote">1 Required for Android Television device implementation, but for other type of |
| 2186 | devices only when supported by hardware.</p> |
| 2187 | |
| 2188 | <p class="table_footnote">2 Required for Android Television device implementations when supported by |
| 2189 | hardware.</p> |
| 2190 | |
| 2191 | <h2 id="5_4_audio_recording">5.4. Audio Recording</h2> |
| 2192 | |
| 2193 | |
| 2194 | <p>While some of the requirements outlined in this section are stated as SHOULD |
| 2195 | since Android 4.3, the Compatibility Definition for a future version is planned |
Glenn Kasten | 20cdbb7 | 2015-09-24 11:56:42 -0700 | [diff] [blame^] | 2196 | to change these to MUST. Existing and new Android devices are <strong>STRONGLY ENCOURAGED</strong> |
| 2197 | to meet these requirements, or they will not be able to attain Android compatibility when upgraded |
| 2198 | to the future version.</p> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 2199 | |
| 2200 | <h3 id="5_4_1_raw_audio_capture">5.4.1. Raw Audio Capture</h3> |
| 2201 | |
| 2202 | |
| 2203 | <p>Device implementations that declare android.hardware.microphone MUST allow |
| 2204 | capture of raw audio content with the following characteristics:</p> |
| 2205 | |
| 2206 | <ul> |
| 2207 | <li><strong>Format</strong>: Linear PCM, 16-bit |
| 2208 | <li><strong>Sampling rates</strong>: 8000, 11025, 16000, 44100 |
| 2209 | <li><strong>Channels</strong>: Mono |
| 2210 | </ul> |
| 2211 | |
Glenn Kasten | 20cdbb7 | 2015-09-24 11:56:42 -0700 | [diff] [blame^] | 2212 | <p>The capture for the above sample rates MUST be done without up-sampling, and |
| 2213 | any down-sampling MUST include an appropriate anti-aliasing filter.</p> |
| 2214 | |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 2215 | <p>Device implementations that declare android.hardware.microphone SHOULD allow |
| 2216 | capture of raw audio content with the following characteristics:</p> |
| 2217 | |
| 2218 | <ul> |
| 2219 | <li><strong>Format</strong>: Linear PCM, 16-bit |
| 2220 | <li><strong>Sampling rates</strong>: 22050, 48000 |
| 2221 | <li><strong>Channels</strong>: Stereo |
| 2222 | </ul> |
| 2223 | |
Glenn Kasten | 20cdbb7 | 2015-09-24 11:56:42 -0700 | [diff] [blame^] | 2224 | <p>If capture for the above sample rates is supported, |
| 2225 | then the capture MUST be done without up-sampling at any ratio higher than 16000:22050 |
| 2226 | or 44100:48000. |
| 2227 | Any up-sampling or down-sampling MUST include an appropriate anti-aliasing filter.</p> |
| 2228 | |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 2229 | <h3 id="5_4_2_capture_for_voice_recognition">5.4.2. Capture for Voice Recognition</h3> |
| 2230 | |
| 2231 | |
| 2232 | <p>In addition to the above recording specifications, when an application has |
| 2233 | started recording an audio stream using the |
| 2234 | android.media.MediaRecorder.AudioSource.VOICE_RECOGNITION audio source:</p> |
| 2235 | |
| 2236 | <ul> |
| 2237 | <li>The device SHOULD exhibit approximately flat amplitude versus frequency |
| 2238 | characteristics: specifically, ±3 dB, from 100 Hz to 4000 Hz. |
| 2239 | <li>Audio input sensitivity SHOULD be set such that a 90 dB sound power level (SPL) |
| 2240 | source at 1000 Hz yields RMS of 2500 for 16-bit samples. |
| 2241 | <li>PCM amplitude levels SHOULD linearly track input SPL changes over at least a 30 |
| 2242 | dB range from -18 dB to +12 dB re 90 dB SPL at the microphone. |
Glenn Kasten | 20cdbb7 | 2015-09-24 11:56:42 -0700 | [diff] [blame^] | 2243 | <li>Total harmonic distortion SHOULD be less than 1% for 1 kHz at 90 dB SPL input |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 2244 | level at the microphone. |
| 2245 | <li>Noise reduction processing, if present, MUST be disabled. |
| 2246 | <li>Automatic gain control, if present, MUST be disabled |
| 2247 | </ul> |
| 2248 | |
| 2249 | <p>If the platform supports noise suppression technologies tuned for speech |
| 2250 | recognition, the effect MUST be controllable from the |
| 2251 | android.media.audiofx.NoiseSuppressor API. Moreover, the UUID field for the |
| 2252 | noise suppressor’s effect descriptor MUST uniquely identify each implementation |
| 2253 | of the noise suppression technology.</p> |
| 2254 | |
| 2255 | <h3 id="5_4_3_capture_for_rerouting_of_playback">5.4.3. Capture for Rerouting of Playback</h3> |
| 2256 | |
| 2257 | |
| 2258 | <p>The android.media.MediaRecorder.AudioSource class includes the REMOTE_SUBMIX |
| 2259 | audio source. Devices that declare android.hardware.audio.output MUST properly |
| 2260 | implement the REMOTE_SUBMIX audio source so that when an application uses the |
| 2261 | android.media.AudioRecord API to record from this audio source, it can capture |
| 2262 | a mix of all audio streams except for the following:</p> |
| 2263 | |
| 2264 | <ul> |
| 2265 | <li>STREAM_RING |
| 2266 | <li>STREAM_ALARM |
| 2267 | <li>STREAM_NOTIFICATION |
| 2268 | </ul> |
| 2269 | |
| 2270 | <h2 id="5_5_audio_playback">5.5. Audio Playback</h2> |
| 2271 | |
| 2272 | |
| 2273 | <p>Device implementations that declare android.hardware.audio.output MUST conform |
| 2274 | to the requirements in this section.</p> |
| 2275 | |
| 2276 | <h3 id="5_5_1_raw_audio_playback">5.5.1. Raw Audio Playback</h3> |
| 2277 | |
| 2278 | |
| 2279 | <p>The device MUST allow playback of raw audio content with the following |
| 2280 | characteristics:</p> |
| 2281 | |
| 2282 | <ul> |
| 2283 | <li><strong>Format</strong>: Linear PCM, 16-bit</li> |
| 2284 | <li><strong>Sampling rates</strong>: 8000, 11025, 16000, 22050, 32000, 44100</li> |
| 2285 | <li><strong>Channels</strong>: Mono, Stereo</li> |
| 2286 | </ul> |
| 2287 | |
| 2288 | <p>The device SHOULD allow playback of raw audio content with the following |
| 2289 | characteristics:</p> |
| 2290 | |
| 2291 | <ul> |
| 2292 | <li><strong>Sampling rates</strong>: 24000, 48000</li> |
| 2293 | </ul> |
| 2294 | |
| 2295 | <h3 id="5_5_2_audio_effects">5.5.2. Audio Effects</h3> |
| 2296 | |
| 2297 | |
| 2298 | <p>Android provides an API for audio effects for device implementations [<a href="http://developer.android.com/reference/android/media/audiofx/AudioEffect.html">Resources, 52</a>]. Device implementations that declare the feature |
| 2299 | android.hardware.audio.output:</p> |
| 2300 | |
| 2301 | <ul> |
| 2302 | <li>MUST support the EFFECT_TYPE_EQUALIZER and EFFECT_TYPE_LOUDNESS_ENHANCER |
| 2303 | implementations controllable through the AudioEffect subclasses Equalizer, |
| 2304 | LoudnessEnhancer.</li> |
| 2305 | <li>MUST support the visualizer API implementation, controllable through the |
| 2306 | Visualizer class.</li> |
| 2307 | <li>SHOULD support the EFFECT_TYPE_BASS_BOOST, EFFECT_TYPE_ENV_REVERB, |
| 2308 | EFFECT_TYPE_PRESET_REVERB, and EFFECT_TYPE_VIRTUALIZER implementations |
| 2309 | controllable through the AudioEffect sub-classes BassBoost, |
| 2310 | EnvironmentalReverb, PresetReverb, and Virtualizer.</li> |
| 2311 | </ul> |
| 2312 | |
| 2313 | <h3 id="5_5_3_audio_output_volume">5.5.3. Audio Output Volume</h3> |
| 2314 | |
| 2315 | |
| 2316 | <p>Android Television device implementations MUST include support for system |
| 2317 | Master Volume and digital audio output volume attenuation on supported outputs, |
| 2318 | except for compressed audio passthrough output (where no audio decoding is done |
| 2319 | on the device).</p> |
| 2320 | |
| 2321 | <h2 id="5_6_audio_latency">5.6. Audio Latency</h2> |
| 2322 | |
| 2323 | |
| 2324 | <p>Audio latency is the time delay as an audio signal passes through a system. |
| 2325 | Many classes of applications rely on short latencies, to achieve real-time |
| 2326 | sound effects.</p> |
| 2327 | |
| 2328 | <p>For the purposes of this section, use the following definitions:</p> |
| 2329 | |
| 2330 | <ul> |
| 2331 | <li><strong>output latency</strong>. The interval between when an application writes a frame of PCM-coded data and |
| 2332 | when the corresponding sound can be heard by an external listener or observed |
| 2333 | by a transducer.</li> |
| 2334 | <li><strong>cold output latency</strong>. The output latency for the first frame, when the audio output system has been |
| 2335 | idle and powered down prior to the request.</li> |
| 2336 | <li><strong>continuous output latency</strong>. The output latency for subsequent frames, after the device is playing audio.</li> |
| 2337 | <li><strong>input latency</strong>. The interval between when an external sound is presented to the device and |
| 2338 | when an application reads the corresponding frame of PCM-coded data.</li> |
| 2339 | <li><strong>cold input latency</strong>. The sum of lost input time and the input latency for the first frame, when the |
| 2340 | audio input system has been idle and powered down prior to the request.</li> |
| 2341 | <li><strong>continuous input latency</strong>. The input latency for subsequent frames, while the device is capturing audio.</li> |
| 2342 | <li><strong>cold output jitter</strong>. The variance among separate measurements of cold output latency values.</li> |
| 2343 | <li><strong>cold input jitter</strong>. The variance among separate measurements of cold input latency values.</li> |
Glenn Kasten | 78eccbd | 2015-08-12 10:18:22 -0700 | [diff] [blame] | 2344 | <li><strong>continuous round-trip latency</strong>. The sum of continuous input latency plus continuous output latency plus |
| 2345 | one buffer period. |
| 2346 | The buffer period term allows processing time for the app and for the app to |
| 2347 | mitigate phase difference between input and output streams. |
| 2348 | </li> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 2349 | <li><strong>OpenSL ES PCM buffer queue API</strong>. The set of PCM-related OpenSL ES APIs within Android NDK; see |
| 2350 | NDK_root/docs/opensles/index.html.</li> |
| 2351 | </ul> |
| 2352 | |
Bert McMeen | 816a242 | 2015-09-29 16:33:19 -0700 | [diff] [blame] | 2353 | <p>Device implementations that declare android.hardware.audio.output are STRONGLY RECOMMENDED to meet |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 2354 | or exceed these audio output requirements:</p> |
| 2355 | |
| 2356 | <ul> |
| 2357 | <li>cold output latency of 100 milliseconds or less</li> |
| 2358 | <li>continuous output latency of 45 milliseconds or less</li> |
| 2359 | <li>minimize the cold output jitter</li> |
| 2360 | </ul> |
| 2361 | |
| 2362 | <p>If a device implementation meets the requirements of this section after any |
| 2363 | initial calibration when using the OpenSL ES PCM buffer queue API, for |
| 2364 | continuous output latency and cold output latency over at least one supported |
| 2365 | audio output device, it MAY report support for low-latency audio, by reporting |
| 2366 | the feature android.hardware.audio.low_latency via the |
| 2367 | android.content.pm.PackageManager class [<a href="http://developer.android.com/reference/android/content/pm/PackageManager.html">Resources, 53</a>]. Conversely, if the device implementation does not meet these requirements it |
| 2368 | MUST NOT report support for low-latency audio.</p> |
| 2369 | |
Bert McMeen | 816a242 | 2015-09-29 16:33:19 -0700 | [diff] [blame] | 2370 | <p>Device implementations that include android.hardware.microphone are STRONGLY RECOMMENDED to meet |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 2371 | these input audio requirements:</p> |
| 2372 | |
| 2373 | <ul> |
| 2374 | <li>cold input latency of 100 milliseconds or less</li> |
| 2375 | <li>continuous input latency of 30 milliseconds or less</li> |
| 2376 | <li>continuous round-trip latency of 50 milliseconds or less</li> |
| 2377 | <li>minimize the cold input jitter</li> |
| 2378 | </ul> |
| 2379 | |
| 2380 | <h2 id="5_7_network_protocols">5.7. Network Protocols</h2> |
| 2381 | |
| 2382 | |
| 2383 | <p>Devices MUST support the media network protocols for audio and video playback |
| 2384 | as specified in the Android SDK documentation [<a href="http://developer.android.com/guide/appendix/media-formats.html">Resources, 50</a>]. Specifically, devices MUST support the following media network protocols:</p> |
| 2385 | |
| 2386 | <ul> |
| 2387 | <li>RTSP (RTP, SDP)</li> |
| 2388 | <li>HTTP(S) progressive streaming</li> |
| 2389 | <li>HTTP(S) Live Streaming draft protocol, Version 3 [<a href="http://tools.ietf.org/html/draft-pantos-http-live-streaming-03">Resources, 54</a>]</li> |
| 2390 | </ul> |
| 2391 | |
| 2392 | <h2 id="5_8_secure_media">5.8. Secure Media</h2> |
| 2393 | |
| 2394 | |
| 2395 | <p>Device implementations that support secure video output and are capable of |
| 2396 | supporting secure surfaces MUST declare support for Display.FLAG_SECURE. Device |
| 2397 | implementations that declare support for Display.FLAG_SECURE, if they support a |
| 2398 | wireless display protocol, MUST secure the link with a cryptographically strong |
| 2399 | mechanism such as HDCP 2.x or higher for Miracast wireless displays. Similarly |
| 2400 | if they support a wired external display, the device implementations MUST |
| 2401 | support HDCP 1.2 or higher. Android Television device implementations MUST |
| 2402 | support HDCP 2.2 for devices supporting 4K resolution and HDCP 1.4 or above for |
| 2403 | lower resolutions. The upstream Android open source implementation includes |
| 2404 | support for wireless (Miracast) and wired (HDMI) displays that satisfies this |
| 2405 | requirement.</p> |
| 2406 | |
Glenn Kasten | 87ef61d | 2015-07-29 09:01:36 -0700 | [diff] [blame] | 2407 | <h2 id="5_9_midi">5.9. Musical Instrument Digital Interface (MIDI)</h2> |
| 2408 | |
| 2409 | <p> |
| 2410 | If a device implementation supports the inter-app MIDI software transport |
| 2411 | (virtual MIDI devices), and it supports MIDI over |
| 2412 | <em>all</em> of the following MIDI-capable hardware transports |
| 2413 | for which it provides generic non-MIDI connectivity, it MAY report |
| 2414 | support for feature android.software.midi via the |
| 2415 | android.content.pm.PackageManager class |
| 2416 | [<a href="http://developer.android.com/reference/android/content/pm/PackageManager.html">Resources, 53</a>]. |
| 2417 | </p> |
| 2418 | |
| 2419 | <p>The MIDI-capable hardware transports are:</p> |
| 2420 | <ul> |
| 2421 | <li>USB host mode (section 7.7 USB)</li> |
| 2422 | <li>USB peripheral mode (section 7.7 USB)</li> |
| 2423 | </ul> |
| 2424 | |
| 2425 | <p> |
| 2426 | Conversely, if the device implementation provides generic non-MIDI connectivity over a particular |
| 2427 | MIDI-capable hardware transport listed above, but does not support MIDI over that hardware transport, |
| 2428 | it MUST NOT report support for feature android.software.midi. |
| 2429 | </p> |
| 2430 | |
| 2431 | <p> |
| 2432 | MIDI over Bluetooth LE acting in central role (section 7.4.3 Bluetooth) |
| 2433 | is in trial use status. A device implementation that reports |
| 2434 | feature android.software.midi, and which provides generic non-MIDI connectivity |
| 2435 | over Bluetooth LE, SHOULD support MIDI over Bluetooth LE. |
| 2436 | </p> |
| 2437 | |
Glenn Kasten | 78eccbd | 2015-08-12 10:18:22 -0700 | [diff] [blame] | 2438 | <h2 id="5_10_pro_audio">5.10. Professional Audio</h2> |
| 2439 | |
| 2440 | <p> |
| 2441 | If a device implementation meets <em>all</em> of the following requirements, |
| 2442 | it MAY report support for feature android.hardware.audio.pro via the |
| 2443 | android.content.pm.PackageManager class |
| 2444 | [<a href="http://developer.android.com/reference/android/content/pm/PackageManager.html">Resources, 53</a>]. |
| 2445 | </p> |
| 2446 | |
| 2447 | <ul> |
| 2448 | |
| 2449 | <li> |
Glenn Kasten | 1578ece | 2015-09-15 13:44:17 -0700 | [diff] [blame] | 2450 | The device implementation MUST report support for feature android.hardware.audio.low_latency. |
Glenn Kasten | 78eccbd | 2015-08-12 10:18:22 -0700 | [diff] [blame] | 2451 | </li> |
| 2452 | |
| 2453 | <li> The continuous round-trip audio latency, as defined in section 5.6 Audio Latency, |
| 2454 | MUST be 20 milliseconds or less and SHOULD be 10 milliseconds or less over at least one |
| 2455 | supported path. |
| 2456 | </li> |
| 2457 | |
| 2458 | <li> |
Glenn Kasten | 1578ece | 2015-09-15 13:44:17 -0700 | [diff] [blame] | 2459 | If the device includes a 4 conductor 3.5mm audio jack, |
Glenn Kasten | 78eccbd | 2015-08-12 10:18:22 -0700 | [diff] [blame] | 2460 | the continuous round-trip audio latency MUST be 20 milliseconds or less over the audio jack path, |
| 2461 | and SHOULD be 10 milliseconds or less over at the audio jack path. |
| 2462 | </li> |
| 2463 | |
| 2464 | <li> |
| 2465 | The device implementation MUST include a USB port(s) supporting USB host mode and |
| 2466 | USB peripheral mode. |
| 2467 | </li> |
| 2468 | |
| 2469 | <li> |
Glenn Kasten | 755f4b2 | 2015-09-25 16:04:23 -0700 | [diff] [blame] | 2470 | The USB host mode MUST implement the USB audio class. |
Glenn Kasten | 78eccbd | 2015-08-12 10:18:22 -0700 | [diff] [blame] | 2471 | </li> |
| 2472 | |
| 2473 | <li> |
| 2474 | If the device includes an HDMI port, the device implementation |
Glenn Kasten | 1578ece | 2015-09-15 13:44:17 -0700 | [diff] [blame] | 2475 | MUST support output in stereo and eight channels |
Glenn Kasten | 78eccbd | 2015-08-12 10:18:22 -0700 | [diff] [blame] | 2476 | at 20-bit or 24-bit depth and 192 kHz without bit-depth loss or resampling. |
| 2477 | </li> |
| 2478 | |
| 2479 | <li> |
| 2480 | The device implementation MUST report support for feature android.software.midi. |
| 2481 | </li> |
| 2482 | |
Glenn Kasten | 1578ece | 2015-09-15 13:44:17 -0700 | [diff] [blame] | 2483 | <li> |
| 2484 | If the device includes a 4 conductor 3.5mm audio jack, |
Bert McMeen | 816a242 | 2015-09-29 16:33:19 -0700 | [diff] [blame] | 2485 | the device implementation is STRONGLY RECOMMENDED to comply with section |
Glenn Kasten | 1578ece | 2015-09-15 13:44:17 -0700 | [diff] [blame] | 2486 | <a href="https://source.android.com/accessories/headset/specification.html#mobile_device_jack_specifications">Mobile device (jack) specifications</a> |
| 2487 | of the |
| 2488 | <a href="https://source.android.com/accessories/headset/specification.html">Wired Audio Headset Specification (v1.1)</a>. |
| 2489 | </li> |
| 2490 | |
Glenn Kasten | 78eccbd | 2015-08-12 10:18:22 -0700 | [diff] [blame] | 2491 | </ul> |
| 2492 | |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 2493 | <h1 id="6_developer_tools_and_options_compatibility">6. Developer Tools and Options Compatibility</h1> |
| 2494 | |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 2495 | <h2 id="6_1_developer_tools">6.1. Developer Tools</h2> |
| 2496 | |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 2497 | <p>Device implementations MUST support the Android Developer Tools provided in the |
| 2498 | Android SDK. Android compatible devices MUST be compatible with:</p> |
| 2499 | |
| 2500 | <ul> |
| 2501 | <li><strong>Android Debug Bridge (adb)</strong> [<a href="http://developer.android.com/tools/help/adb.html">Resources, 55</a>]</li> |
| 2502 | </ul> |
| 2503 | |
| 2504 | <p>Device implementations MUST support all adb functions as documented in the |
| 2505 | Android SDK including dumpsys [<a href="https://source.android.com/devices/input/diagnostics.html">Resources, 56</a>]. The device-side adb daemon MUST be inactive by default and there MUST be a |
| 2506 | user-accessible mechanism to turn on the Android Debug Bridge. If a device |
| 2507 | implementation omits USB peripheral mode, it MUST implement the Android Debug |
| 2508 | Bridge via local-area network (such as Ethernet or 802.11). </p> |
| 2509 | |
| 2510 | <p>Android includes support for secure adb. Secure adb enables adb on known |
| 2511 | authenticated hosts. Device implementations MUST support secure adb.</p> |
| 2512 | |
| 2513 | <ul> |
| 2514 | <li><strong>Dalvik Debug Monitor Service (ddms)</strong> [<a href="http://developer.android.com/tools/debugging/ddms.html">Resources, 57</a>]</li> |
| 2515 | </ul> |
| 2516 | |
| 2517 | <p>Device implementations MUST support all ddms features as documented in the |
| 2518 | Android SDK. As ddms uses adb, support for ddms SHOULD be inactive by default, |
| 2519 | but MUST be supported whenever the user has activated the Android Debug Bridge, |
| 2520 | as above.</p> |
| 2521 | |
| 2522 | <ul> |
| 2523 | <li><strong>Monkey</strong> [<a href="http://developer.android.com/tools/help/monkey.html">Resources, 58</a>]</li> |
| 2524 | </ul> |
| 2525 | |
| 2526 | <p>Device implementations MUST include the Monkey framework, and make it available |
| 2527 | for applications to use.</p> |
| 2528 | |
| 2529 | <ul> |
| 2530 | <li><strong>SysTrace</strong> [<a href="http://developer.android.com/tools/help/systrace.html">Resources, 59</a>]</li> |
| 2531 | </ul> |
| 2532 | |
| 2533 | <p>Device implementations MUST support systrace tool as documented in the Android |
| 2534 | SDK. Systrace must be inactive by default, and there MUST be a user-accessible |
| 2535 | mechanism to turn on Systrace.</p> |
| 2536 | |
| 2537 | <p>Most Linux-based systems and Apple Macintosh systems recognize Android devices |
| 2538 | using the standard Android SDK tools, without additional support; however |
| 2539 | Microsoft Windows systems typically require a driver for new Android devices. |
| 2540 | (For instance, new vendor IDs and sometimes new device IDs require custom USB |
| 2541 | drivers for Windows systems.) If a device implementation is unrecognized by the |
| 2542 | adb tool as provided in the standard Android SDK, device implementers MUST |
| 2543 | provide Windows drivers allowing developers to connect to the device using the |
| 2544 | adb protocol. These drivers MUST be provided for Windows XP, Windows Vista, |
| 2545 | Windows 7, Windows 8, and Windows 9 in both 32-bit and 64-bit versions.</p> |
| 2546 | |
| 2547 | <h2 id="6_2_developer_options">6.2. Developer Options</h2> |
| 2548 | |
| 2549 | |
| 2550 | <p>Android includes support for developers to configure application |
| 2551 | development-related settings. Device implementations MUST honor the |
| 2552 | android.settings.APPLICATION_DEVELOPMENT_SETTINGS intent to show application |
| 2553 | development-related settings [<a href="http://developer.android.com/reference/android/provider/Settings.html#ACTION_APPLICATION_DEVELOPMENT_SETTINGS">Resources, 60</a>]. The upstream Android implementation hides the Developer Options menu by |
| 2554 | default and enables users to launch Developer Options after pressing seven (7) |
| 2555 | times on the <strong>Settings</strong> > <strong>About Device</strong> > <strong>Build Number</strong> menu item. Device implementations MUST provide a consistent experience for |
| 2556 | Developer Options. Specifically, device implementations MUST hide Developer |
| 2557 | Options by default and MUST provide a mechanism to enable Developer Options |
| 2558 | that is consistent with the upstream Android implementation.</p> |
| 2559 | |
| 2560 | <h1 id="7_hardware_compatibility">7. Hardware Compatibility</h1> |
| 2561 | |
| 2562 | |
| 2563 | <p>If a device includes a particular hardware component that has a corresponding |
| 2564 | API for third-party developers, the device implementation MUST implement that |
| 2565 | API as described in the Android SDK documentation. If an API in the SDK |
| 2566 | interacts with a hardware component that is stated to be optional and the |
| 2567 | device implementation does not possess that component:</p> |
| 2568 | |
| 2569 | <ul> |
| 2570 | <li>Complete class definitions (as documented by the SDK) for the component APIs |
| 2571 | MUST still be presented. |
| 2572 | <li>The API’s behaviors MUST be implemented as no-ops in some reasonable fashion. |
| 2573 | <li>API methods MUST return null values where permitted by the SDK documentation. |
| 2574 | <li>API methods MUST return no-op implementations of classes where null values are |
| 2575 | not permitted by the SDK documentation. |
| 2576 | <li>API methods MUST NOT throw exceptions not documented by the SDK documentation. |
| 2577 | </ul> |
| 2578 | |
| 2579 | <p>A typical example of a scenario where these requirements apply is the telephony |
| 2580 | API: even on non-phone devices, these APIs must be implemented as reasonable |
| 2581 | no-ops.</p> |
| 2582 | |
| 2583 | <p>Device implementations MUST consistently report accurate hardware configuration |
| 2584 | information via the getSystemAvailableFeatures() and hasSystemFeature(String) |
| 2585 | methods on the android.content.pm.PackageManager class for the same build |
| 2586 | fingerprint. [<a href="http://developer.android.com/reference/android/content/pm/PackageManager.html">Resources, 53]</a></p> |
| 2587 | |
| 2588 | <h2 id="7_1_display_and_graphics">7.1. Display and Graphics</h2> |
| 2589 | |
| 2590 | |
| 2591 | <p>Android includes facilities that automatically adjust application assets and UI |
| 2592 | layouts appropriately for the device, to ensure that third-party applications |
| 2593 | run well on a variety of hardware configurations [<a href="http://developer.android.com/guide/practices/screens_support.html">Resources, 61</a>]. Devices MUST properly implement these APIs and behaviors, as detailed in |
| 2594 | this section.</p> |
| 2595 | |
| 2596 | <p>The units referenced by the requirements in this section are defined as |
| 2597 | follows:</p> |
| 2598 | |
| 2599 | <ul> |
| 2600 | <li><strong>physical diagonal size</strong>. The distance in inches between two opposing corners of the illuminated portion |
| 2601 | of the display.</li> |
| 2602 | <li><strong>dots per inch (dpi)</strong>. The number of pixels encompassed by a linear horizontal or vertical span of |
| 2603 | 1”. Where dpi values are listed, both horizontal and vertical dpi must fall |
| 2604 | within the range.</li> |
| 2605 | <li><strong>aspect ratio</strong>. The ratio of the pixels of the longer dimension |
| 2606 | to the shorter dimension of the screen. For example, a display of 480x854 pixels |
| 2607 | would be 854/480 = 1.779, or roughly “16:9”.</li> |
| 2608 | <li><strong>density-independent pixel (dp)</strong> The virtual pixel unit normalized to a 160 dpi screen, calculated as: pixels = |
| 2609 | dps * (density/160).</li> |
| 2610 | </ul> |
| 2611 | |
| 2612 | <h3 id="7_1_1_screen_configuration">7.1.1. Screen Configuration</h3> |
| 2613 | |
| 2614 | |
| 2615 | <h4 id="7_1_1_1_screen_size">7.1.1.1. Screen Size</h4> |
| 2616 | |
| 2617 | <div class="note"> |
| 2618 | <p>Android Watch devices (detailed in <a href="#2_device_types">section 2</a>) MAY have smaller screen sizes as described in this section.</p> |
| 2619 | </div> |
| 2620 | |
| 2621 | <p>The Android UI framework supports a variety of different screen sizes, and |
| 2622 | allows applications to query the device screen size (aka “screen layout") via |
| 2623 | android.content.res.Configuration.screenLayout with the SCREENLAYOUT_SIZE_MASK. |
| 2624 | Device implementations MUST report the correct screen size as defined in the |
| 2625 | Android SDK documentation [<a href="http://developer.android.com/guide/practices/screens_support.html">Resources, 61</a>] and determined by the upstream Android platform. Specifically, device |
| 2626 | implementations MUST report the correct screen size according to the following |
| 2627 | logical density-independent pixel (dp) screen dimensions.</p> |
| 2628 | |
| 2629 | <ul> |
| 2630 | <li>Devices MUST have screen sizes of at least 426 dp x 320 dp (‘small’), unless it |
| 2631 | is an Android Watch device.</li> |
| 2632 | <li>Devices that report screen size ‘normal’ MUST have screen sizes of at least 480 |
| 2633 | dp x 320 dp.</li> |
| 2634 | <li>Devices that report screen size ‘large’ MUST have screen sizes of at least 640 |
| 2635 | dp x 480 dp.</li> |
| 2636 | <li>Devices that report screen size ‘xlarge’ MUST have screen sizes of at least 960 |
| 2637 | dp x 720 dp.</li> |
| 2638 | </ul> |
| 2639 | |
| 2640 | <p>In addition, </p> |
| 2641 | |
| 2642 | <ul> |
| 2643 | <li>Android Watch devices MUST have a screen with the physical diagonal size in the |
| 2644 | range from 1.1 to 2.5 inches.</li> |
| 2645 | <li>Other types of Android device implementations, with a physically integrated |
| 2646 | screen, MUST have a screen at least 2.5 inches in physical diagonal size.</li> |
| 2647 | </ul> |
| 2648 | |
| 2649 | <p>Devices MUST NOT change their reported screen size at any time.</p> |
| 2650 | |
| 2651 | <p>Applications optionally indicate which screen sizes they support via the |
Unsuk Jung | 2e62f9a | 2015-07-16 23:01:44 -0700 | [diff] [blame] | 2652 | <supports-screens> attribute in the AndroidManifest.xml file. Device |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 2653 | implementations MUST correctly honor applications' stated support for small, |
| 2654 | normal, large, and xlarge screens, as described in the Android SDK |
| 2655 | documentation.</p> |
| 2656 | |
| 2657 | <h4 id="7_1_1_2_screen_aspect_ratio">7.1.1.2. Screen Aspect Ratio</h4> |
| 2658 | |
| 2659 | <div class="note"> |
| 2660 | <p>Android Watch devices MAY have an aspect ratio of 1.0 (1:1).</p> |
| 2661 | </div> |
| 2662 | |
| 2663 | |
| 2664 | <p>The screen aspect ratio MUST be a value from 1.3333 (4:3) to 1.86 (roughly |
| 2665 | 16:9), but Android Watch devices MAY have an aspect ratio of 1.0 (1:1) because |
| 2666 | such a device implementation will use a UI_MODE_TYPE_WATCH as the |
| 2667 | android.content.res.Configuration.uiMode.</p> |
| 2668 | |
| 2669 | <h4 id="7_1_1_3_screen_density">7.1.1.3. Screen Density</h4> |
| 2670 | |
| 2671 | |
| 2672 | <p>The Android UI framework defines a set of standard logical densities to help |
| 2673 | application developers target application resources. Device implementations |
| 2674 | MUST report only one of the following logical Android framework densities |
| 2675 | through the android.util.DisplayMetrics APIs, and MUST execute applications at |
| 2676 | this standard density and MUST NOT change the value at at any time for the |
| 2677 | default display.</p> |
| 2678 | |
| 2679 | <ul> |
| 2680 | <li>120 dpi (ldpi)</li> |
| 2681 | <li>160 dpi (mdpi)</li> |
| 2682 | <li>213 dpi (tvdpi)</li> |
| 2683 | <li>240 dpi (hdpi)</li> |
| 2684 | <li>280 dpi (280dpi)</li> |
| 2685 | <li>320 dpi (xhdpi)</li> |
| 2686 | <li>400 dpi (400dpi)</li> |
| 2687 | <li>480 dpi (xxhdpi)</li> |
| 2688 | <li>560 dpi (560dpi)</li> |
| 2689 | <li>640 dpi (xxxhdpi)</li> |
| 2690 | </ul> |
| 2691 | |
| 2692 | <p>Device implementations SHOULD define the standard Android framework density |
| 2693 | that is numerically closest to the physical density of the screen, unless that |
| 2694 | logical density pushes the reported screen size below the minimum supported. If |
| 2695 | the standard Android framework density that is numerically closest to the |
| 2696 | physical density results in a screen size that is smaller than the smallest |
| 2697 | supported compatible screen size (320 dp width), device implementations SHOULD |
| 2698 | report the next lowest standard Android framework density.</p> |
| 2699 | |
| 2700 | <h3 id="7_1_2_display_metrics">7.1.2. Display Metrics</h3> |
| 2701 | |
| 2702 | |
| 2703 | <p>Device implementations MUST report correct values for all display metrics |
| 2704 | defined in android.util.DisplayMetrics [<a href="http://developer.android.com/reference/android/util/DisplayMetrics.html">Resources, 62</a>] and MUST report the same values regardless of whether the embedded or |
| 2705 | external screen is used as the default display.</p> |
| 2706 | |
| 2707 | <h3 id="7_1_3_screen_orientation">7.1.3. Screen Orientation</h3> |
| 2708 | |
| 2709 | |
| 2710 | <p>Devices MUST report which screen orientations they support |
| 2711 | (android.hardware.screen.portrait and/or android.hardware.screen.landscape) and |
| 2712 | MUST report at least one supported orientation. For example, a device with a |
| 2713 | fixed orientation landscape screen, such as a television or laptop, SHOULD only |
| 2714 | report android.hardware.screen.landscape.</p> |
| 2715 | |
| 2716 | <p>Devices that report both screen orientations MUST support dynamic orientation |
| 2717 | by applications to either portrait or landscape screen orientation. That is, |
| 2718 | the device must respect the application’s request for a specific screen |
| 2719 | orientation. Device implementations MAY select either portrait or landscape |
| 2720 | orientation as the default.</p> |
| 2721 | |
| 2722 | <p>Devices MUST report the correct value for the device’s current orientation, |
| 2723 | whenever queried via the android.content.res.Configuration.orientation, |
| 2724 | android.view.Display.getOrientation(), or other APIs.</p> |
| 2725 | |
| 2726 | <p>Devices MUST NOT change the reported screen size or density when changing |
| 2727 | orientation.</p> |
| 2728 | |
| 2729 | <h3 id="7_1_4_2d_and_3d_graphics_acceleration">7.1.4. 2D and 3D Graphics Acceleration</h3> |
| 2730 | |
| 2731 | |
| 2732 | <p>Device implementations MUST support both OpenGL ES 1.0 and 2.0, as embodied and |
| 2733 | detailed in the Android SDK documentations. Device implementations SHOULD |
| 2734 | support OpenGL ES 3.0 or 3.1 on devices capable of supporting it. Device |
| 2735 | implementations MUST also support Android RenderScript, as detailed in the |
| 2736 | Android SDK documentation [<a href="http://developer.android.com/guide/topics/renderscript/">Resources, 63</a>].</p> |
| 2737 | |
| 2738 | <p>Device implementations MUST also correctly identify themselves as supporting |
| 2739 | OpenGL ES 1.0, OpenGL ES 2.0, OpenGL ES 3.0 or OpenGL 3.1. That is:</p> |
| 2740 | |
| 2741 | <ul> |
Unsuk Jung | 2e62f9a | 2015-07-16 23:01:44 -0700 | [diff] [blame] | 2742 | <li>The managed APIs (such as via the GLES10.getString() method) MUST report support |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 2743 | for OpenGL ES 1.0 and OpenGL ES 2.0.</li> |
| 2744 | <li>The native C/C++ OpenGL APIs (APIs available to apps via libGLES_v1CM.so, |
| 2745 | libGLES_v2.so, or libEGL.so) MUST report support for OpenGL ES 1.0 and OpenGL |
| 2746 | ES 2.0.</li> |
| 2747 | <li>Device implementations that declare support for OpenGL ES 3.0 or 3.1 MUST |
| 2748 | support the corresponding managed APIs and include support for native C/C++ |
| 2749 | APIs. On device implementations that declare support for OpenGL ES 3.0 or 3.1, |
| 2750 | libGLESv2.so MUST export the corresponding function symbols in addition to the |
| 2751 | OpenGL ES 2.0 function symbols.</li> |
| 2752 | </ul> |
| 2753 | |
| 2754 | <p>In addition to OpenGL ES 3.1, Android provides an extension pack with Java |
| 2755 | interfaces [<a href="https://developer.android.com/reference/android/opengl/GLES31Ext.html">Resources, 64</a>] and native support for advanced graphics functionality such as tessellation |
| 2756 | and the ASTC texture compression format. Android device implementations MAY |
| 2757 | support this extension pack, and—only if fully implemented—MUST identify the |
| 2758 | support through the android.hardware.opengles.aep feature flag.</p> |
| 2759 | |
| 2760 | <p>Also, device implementations MAY implement any desired OpenGL ES extensions. |
| 2761 | However, device implementations MUST report via the OpenGL ES managed and |
| 2762 | native APIs all extension strings that they do support, and conversely MUST NOT |
| 2763 | report extension strings that they do not support.</p> |
| 2764 | |
| 2765 | <p>Note that Android includes support for applications to optionally specify that |
| 2766 | they require specific OpenGL texture compression formats. These formats are |
| 2767 | typically vendor-specific. Device implementations are not required by Android |
| 2768 | to implement any specific texture compression format. However, they SHOULD |
| 2769 | accurately report any texture compression formats that they do support, via the |
| 2770 | getString() method in the OpenGL API.</p> |
| 2771 | |
| 2772 | <p>Android includes a mechanism for applications to declare that they want to |
| 2773 | enable hardware acceleration for 2D graphics at the Application, Activity, |
| 2774 | Window, or View level through the use of a manifest tag |
| 2775 | android:hardwareAccelerated or direct API calls [<a href="http://developer.android.com/guide/topics/graphics/hardware-accel.html">Resources, 65</a>].</p> |
| 2776 | |
| 2777 | <p>Device implementations MUST enable hardware acceleration by default, and MUST |
| 2778 | disable hardware acceleration if the developer so requests by setting |
| 2779 | android:hardwareAccelerated="false” or disabling hardware acceleration directly |
| 2780 | through the Android View APIs.</p> |
| 2781 | |
| 2782 | <p>In addition, device implementations MUST exhibit behavior consistent with the |
| 2783 | Android SDK documentation on hardware acceleration [<a href="http://developer.android.com/guide/topics/graphics/hardware-accel.html">Resources, 65</a>].</p> |
| 2784 | |
| 2785 | <p>Android includes a TextureView object that lets developers directly integrate |
| 2786 | hardware-accelerated OpenGL ES textures as rendering targets in a UI hierarchy. |
| 2787 | Device implementations MUST support the TextureView API, and MUST exhibit |
| 2788 | consistent behavior with the upstream Android implementation.</p> |
| 2789 | |
| 2790 | <p>Android includes support for EGL_ANDROID_RECORDABLE, an EGLConfig attribute |
| 2791 | that indicates whether the EGLConfig supports rendering to an ANativeWindow |
| 2792 | that records images to a video. Device implementations MUST support |
| 2793 | EGL_ANDROID_RECORDABLE extension [<a href="https://www.khronos.org/registry/egl/extensions/ANDROID/EGL_ANDROID_recordable.txt">Resources, 66</a>].</p> |
| 2794 | |
| 2795 | <h3 id="7_1_5_legacy_application_compatibility_mode">7.1.5. Legacy Application Compatibility Mode</h3> |
| 2796 | |
| 2797 | |
| 2798 | <p>Android specifies a “compatibility mode” in which the framework operates in a |
| 2799 | 'normal' screen size equivalent (320dp width) mode for the benefit of legacy |
| 2800 | applications not developed for old versions of Android that pre-date |
| 2801 | screen-size independence.</p> |
| 2802 | |
| 2803 | <ul> |
| 2804 | <li>Android Automotive does not support legacy compatibility mode.</li> |
| 2805 | <li>All other device implementations MUST include support for legacy application |
| 2806 | compatibility mode as implemented by the upstream Android open source code. That |
| 2807 | is, device implementations MUST NOT alter the triggers or thresholds at which |
| 2808 | compatibility mode is activated, and MUST NOT alter the behavior of the |
| 2809 | compatibility mode itself.</li> |
| 2810 | </ul> |
| 2811 | |
| 2812 | <h3 id="7_1_6_screen_technology">7.1.6. Screen Technology</h3> |
| 2813 | |
| 2814 | |
| 2815 | <p>The Android platform includes APIs that allow applications to render rich |
| 2816 | graphics to the display. Devices MUST support all of these APIs as defined by |
| 2817 | the Android SDK unless specifically allowed in this document. </p> |
| 2818 | |
| 2819 | <ul> |
| 2820 | <li>Devices MUST support displays capable of rendering 16-bit color graphics and |
| 2821 | SHOULD support displays capable of 24-bit color graphics.</li> |
| 2822 | <li>Devices MUST support displays capable of rendering animations.</li> |
| 2823 | <li>The display technology used MUST have a pixel aspect ratio (PAR) between 0.9 |
| 2824 | and 1.15. That is, the pixel aspect ratio MUST be near square (1.0) with a 10 ~ |
| 2825 | 15% tolerance.</li> |
| 2826 | </ul> |
| 2827 | |
| 2828 | <h3 id="7_1_7_external_displays">7.1.7. Secondary Displays</h3> |
| 2829 | |
| 2830 | |
| 2831 | <p>Android includes support for secondary display to enable media sharing |
| 2832 | capabilities and developer APIs for accessing external displays. If a device |
| 2833 | supports an external display either via a wired, wireless, or an embedded |
| 2834 | additional display connection then the device implementation MUST implement the |
| 2835 | display manager API as described in the Android SDK documentation [<a href="http://developer.android.com/reference/android/hardware/display/DisplayManager.html">Resources, 67</a>].</p> |
| 2836 | |
| 2837 | <h2 id="7_2_input_devices">7.2. Input Devices</h2> |
| 2838 | |
| 2839 | <p>Devices MUST support a touchscreen or meet the requirements listed in 7.2.2 |
| 2840 | for non-touch navigation.</p> |
| 2841 | |
| 2842 | <h3 id="7_2_1_keyboard">7.2.1. Keyboard</h3> |
| 2843 | |
| 2844 | <div class="note"> |
| 2845 | <p>Android Watch and Android Automotive implementations MAY implement a soft |
| 2846 | keyboard. All other device implementations MUST implement a soft keyboard and:</p> |
| 2847 | </div> |
| 2848 | |
| 2849 | |
| 2850 | <p>Device implementations:</p> |
| 2851 | |
| 2852 | <ul> |
| 2853 | <li>MUST include support for the Input Management Framework (which allows |
| 2854 | third-party developers to create Input Method Editors—i.e. soft keyboard) as |
| 2855 | detailed at <a href="http://developer.android.com">http://developer.android.com</a>.</li> |
| 2856 | <li>MUST provide at least one soft keyboard implementation (regardless of whether a |
| 2857 | hard keyboard is present) except for Android Watch devices where the screen |
| 2858 | size makes it less reasonable to have a soft keyboard.</li> |
| 2859 | <li>MAY include additional soft keyboard implementations.</li> |
| 2860 | <li>MAY include a hardware keyboard.</li> |
| 2861 | <li>MUST NOT include a hardware keyboard that does not match one of the formats |
| 2862 | specified in android.content.res.Configuration.keyboard [<a href="http://developer.android.com/reference/android/content/res/Configuration.html">Resources, 68</a>] (QWERTY or 12-key).</li> |
| 2863 | </ul> |
| 2864 | |
| 2865 | <h3 id="7_2_2_non-touch_navigation">7.2.2. Non-touch Navigation</h3> |
| 2866 | |
| 2867 | <div class="note"> |
| 2868 | <p>Android Television devices MUST support D-pad.</p> |
| 2869 | </div> |
| 2870 | |
| 2871 | <p>Device implementations:</p> |
| 2872 | |
| 2873 | <ul> |
| 2874 | <li>MAY omit a non-touch navigation option (trackball, d-pad, or wheel) if the |
| 2875 | device implementation is not an Android Television device.</li> |
| 2876 | <li>MUST report the correct value for android.content.res.Configuration.navigation |
| 2877 | [<a href="http://developer.android.com/reference/android/content/res/Configuration.html">Resources, 68</a>].</li> |
| 2878 | <li>MUST provide a reasonable alternative user interface mechanism for the |
| 2879 | selection and editing of text, compatible with Input Management Engines. The |
| 2880 | upstream Android open source implementation includes a selection mechanism |
| 2881 | suitable for use with devices that lack non-touch navigation inputs.</li> |
| 2882 | </ul> |
| 2883 | |
| 2884 | <h3 id="7_2_3_navigation_keys">7.2.3. Navigation Keys</h3> |
| 2885 | |
| 2886 | <div class="note"> |
| 2887 | <p>The availability and visibility requirement of the Home, Recents, and Back |
| 2888 | functions differ between device types as described in this section.</p> |
| 2889 | </div> |
| 2890 | |
| 2891 | <p>The Home, Recents, and Back functions (mapped to the key events KEYCODE_HOME, |
| 2892 | KEYCODE_APP_SWITCH, KEYCODE_BACK, respectively) are essential to the Android |
| 2893 | navigation paradigm and therefore:</p> |
| 2894 | |
| 2895 | <ul> |
| 2896 | <li>Android Handheld device implementations MUST provide the Home, Recents, and |
| 2897 | Back functions.</li> |
| 2898 | <li>Android Television device implementations MUST provide the Home and Back |
| 2899 | functions.</li> |
| 2900 | <li>Android Watch device implementations MUST have the Home function available to |
| 2901 | the user, and the Back function except for when it is in UI_MODE_TYPE_WATCH.</li> |
| 2902 | <li>Android Automotive implementations MUST provide the Home function and MAY |
| 2903 | provide Back and Recent functions.</li> |
| 2904 | <li>All other types of device implementations MUST provide the Home and Back |
| 2905 | functions.</li> |
| 2906 | </ul> |
| 2907 | |
| 2908 | <p>These functions MAY be implemented via dedicated physical buttons (such as |
| 2909 | mechanical or capacitive touch buttons), or MAY be implemented using dedicated |
| 2910 | software keys on a distinct portion of the screen, gestures, touch panel, etc. |
| 2911 | Android supports both implementations. All of these functions MUST be |
| 2912 | accessible with a single action (e.g. tap, double-click or gesture) when |
| 2913 | visible.</p> |
| 2914 | |
| 2915 | <p>Recents function, if provided, MUST have a visible button or icon unless hidden |
| 2916 | together with other navigation functions in full-screen mode. This does not |
| 2917 | apply to devices upgrading from earlier Android versions that have physical |
| 2918 | buttons for navigation and no recents key.</p> |
| 2919 | |
| 2920 | <p> The Home and Back functions, if provided, MUST each have a visible button or |
| 2921 | icon unless hidden together with other navigation functions in full-screen mode |
| 2922 | or when the uiMode UI_MODE_TYPE_MASK is set to UI_MODE_TYPE_WATCH.</p> |
| 2923 | |
| 2924 | <p>The Menu function is deprecated in favor of action bar since Android 4.0. |
| 2925 | Therefore the new device implementations shipping with Android ANDROID_VERSION and later MUST NOT |
| 2926 | implement a dedicated physical button for the Menu function. Older device |
| 2927 | implementations SHOULD NOT implement a dedicated physical button for the Menu |
| 2928 | function, but if the physical Menu button is implemented and the device is |
| 2929 | running applications with targetSdkVersion > 10, the device implementation:</p> |
| 2930 | |
| 2931 | <ul> |
| 2932 | <li>MUST display the action overflow button on the action bar when it is visible |
| 2933 | and the resulting action overflow menu popup is not empty. For a device |
| 2934 | implementation launched before Android 4.4 but upgrading to Android ANDROID_VERSION, this |
| 2935 | is RECOMMENDED.</li> |
| 2936 | <li>MUST NOT modify the position of the action overflow popup displayed by |
| 2937 | selecting the overflow button in the action bar.</li> |
| 2938 | <li>MAY render the action overflow popup at a modified position on the screen when |
| 2939 | it is displayed by selecting the physical menu button.</li> |
| 2940 | </ul> |
| 2941 | |
| 2942 | <p>For backwards compatibility, device implementations MUST make the Menu function |
| 2943 | available to applications when targetSdkVersion is less than 10, either by a physical |
| 2944 | button, a software key, or gestures. This Menu function should be presented |
| 2945 | unless hidden together with other navigation functions.</p> |
| 2946 | |
| 2947 | <p>Android supports Assist action [<a href="http://developer.android.com/reference/android/content/Intent.html#ACTION_ASSIST">Resources, 69</a>]. Android device implementations except for Android Watch devices MUST make |
| 2948 | the Assist action available to the user at all times when running applications. |
| 2949 | The Assist action SHOULD be implemented as a long-press on the Home button or a |
| 2950 | swipe-up gesture on the software Home key. This function MAY be implemented via |
| 2951 | another physical button, software key, or gesture, but MUST be accessible with |
| 2952 | a single action (e.g. tap, double-click, or gesture) when other navigation keys |
| 2953 | are visible.</p> |
| 2954 | |
| 2955 | <p>Device implementations MAY use a distinct portion of the screen to display the |
| 2956 | navigation keys, but if so, MUST meet these requirements:</p> |
| 2957 | |
| 2958 | <ul> |
| 2959 | <li>Device implementation navigation keys MUST use a distinct portion of the |
| 2960 | screen, not available to applications, and MUST NOT obscure or otherwise |
| 2961 | interfere with the portion of the screen available to applications.</li> |
| 2962 | <li>Device implementations MUST make available a portion of the display to |
| 2963 | applications that meets the requirements defined in <a href="#7_1_1_screen_configuration">section 7.1.1</a>.</li> |
| 2964 | <li>Device implementations MUST display the navigation keys when applications do |
| 2965 | not specify a system UI mode, or specify SYSTEM_UI_FLAG_VISIBLE.</li> |
| 2966 | <li>Device implementations MUST present the navigation keys in an unobtrusive “low |
| 2967 | profile” (eg. dimmed) mode when applications specify |
| 2968 | SYSTEM_UI_FLAG_LOW_PROFILE.</li> |
| 2969 | <li>Device implementations MUST hide the navigation keys when applications specify |
| 2970 | SYSTEM_UI_FLAG_HIDE_NAVIGATION.</li> |
| 2971 | </ul> |
| 2972 | |
| 2973 | <h3 id="7_2_4_touchscreen_input">7.2.4. Touchscreen Input</h3> |
| 2974 | |
| 2975 | <div class="note"> |
| 2976 | <p>Android Handhelds and Watch Devices MUST support touchscreen input.</p> |
| 2977 | </div> |
| 2978 | |
| 2979 | |
| 2980 | <p>Device implementations SHOULD have a pointer input system of some kind (either |
| 2981 | mouse-like or touch). However, if a device implementation does not support a |
| 2982 | pointer input system, it MUST NOT report the android.hardware.touchscreen or |
| 2983 | android.hardware.faketouch feature constant. Device implementations that do |
| 2984 | include a pointer input system:</p> |
| 2985 | |
| 2986 | <ul> |
| 2987 | <li>SHOULD support fully independently tracked pointers, if the device input system |
| 2988 | supports multiple pointers.</li> |
| 2989 | <li>MUST report the value of android.content.res.Configuration.touchscreen [<a href="http://developer.android.com/reference/android/content/res/Configuration.html">Resources, 68</a>] corresponding to the type of the specific touchscreen on the device.</li> |
| 2990 | </ul> |
| 2991 | |
| 2992 | <p>Android includes support for a variety of touchscreens, touch pads, and fake |
| 2993 | touch input devices. Touchscreen based device implementations are associated |
| 2994 | with a display [<a href="http://source.android.com/devices/tech/input/touch-devices.html">Resources, 70</a>] such that the user has the impression of directly manipulating items on |
| 2995 | screen. Since the user is directly touching the screen, the system does not |
| 2996 | require any additional affordances to indicate the objects being manipulated. |
| 2997 | In contrast, a fake touch interface provides a user input system that |
| 2998 | approximates a subset of touchscreen capabilities. For example, a mouse or |
| 2999 | remote control that drives an on-screen cursor approximates touch, but requires |
| 3000 | the user to first point or focus then click. Numerous input devices like the |
| 3001 | mouse, trackpad, gyro-based air mouse, gyro-pointer, joystick, and multi-touch |
| 3002 | trackpad can support fake touch interactions. Android includes the feature |
| 3003 | constant android.hardware.faketouch, which corresponds to a high-fidelity |
| 3004 | non-touch (pointer-based) input device such as a mouse or trackpad that can |
| 3005 | adequately emulate touch-based input (including basic gesture support), and |
| 3006 | indicates that the device supports an emulated subset of touchscreen |
| 3007 | functionality. Device implementations that declare the fake touch feature MUST |
| 3008 | meet the fake touch requirements in <a href="#7_2_5_fake_touch_input">section 7.2.5</a>.</p> |
| 3009 | |
| 3010 | <p>Device implementations MUST report the correct feature corresponding to the |
| 3011 | type of input used. Device implementations that include a touchscreen |
| 3012 | (single-touch or better) MUST report the platform feature constant |
| 3013 | android.hardware.touchscreen. Device implementations that report the platform |
| 3014 | feature constant android.hardware.touchscreen MUST also report the platform |
| 3015 | feature constant android.hardware.faketouch. Device implementations that do not |
| 3016 | include a touchscreen (and rely on a pointer device only) MUST NOT report any |
| 3017 | touchscreen feature, and MUST report only android.hardware.faketouch if they |
| 3018 | meet the fake touch requirements in <a href="#7_2_5_fake_touch_input">section 7.2.5</a>.</p> |
| 3019 | |
| 3020 | <h3 id="7_2_5_fake_touch_input">7.2.5. Fake Touch Input</h3> |
| 3021 | |
| 3022 | |
| 3023 | <p>Device implementations that declare support for android.hardware.faketouch:</p> |
| 3024 | |
| 3025 | <ul> |
| 3026 | <li>MUST report the absolute X and Y screen positions of the pointer location and |
| 3027 | display a visual pointer on the screen [<a href="http://developer.android.com/reference/android/view/MotionEvent.html">Resources, 71</a>].</li> |
| 3028 | <li>MUST report touch event with the action code that specifies the state change |
| 3029 | that occurs on the pointer going down or up on the screen [<a href="http://developer.android.com/reference/android/view/MotionEvent.html">Resources, 71</a>].</li> |
| 3030 | <li>MUST support pointer down and up on an object on the screen, which allows users |
| 3031 | to emulate tap on an object on the screen.</li> |
| 3032 | <li>MUST support pointer down, pointer up, pointer down then pointer up in the same |
| 3033 | place on an object on the screen within a time threshold, which allows users to |
| 3034 | emulate double tap on an object on the screen [<a href="http://developer.android.com/reference/android/view/MotionEvent.html">Resources, 71</a>].</li> |
| 3035 | <li>MUST support pointer down on an arbitrary point on the screen, pointer move to |
| 3036 | any other arbitrary point on the screen, followed by a pointer up, which allows |
| 3037 | users to emulate a touch drag.</li> |
| 3038 | <li>MUST support pointer down then allow users to quickly move the object to a |
| 3039 | different position on the screen and then pointer up on the screen, which |
| 3040 | allows users to fling an object on the screen.</li> |
| 3041 | </ul> |
| 3042 | |
| 3043 | <p>Devices that declare support for android.hardware.faketouch.multitouch.distinct |
| 3044 | MUST meet the requirements for faketouch above, and MUST also support distinct |
| 3045 | tracking of two or more independent pointer inputs.</p> |
| 3046 | |
| 3047 | <h3 id="7_2_6_game_controller_support">7.2.6. Game Controller Support</h3> |
| 3048 | |
| 3049 | |
| 3050 | <p>Android Television device implementations MUST support button mappings for game |
| 3051 | controllers as listed below. The upstream Android implementation includes |
| 3052 | implementation for game controllers that satisfies this requirement. </p> |
| 3053 | |
| 3054 | <h4 id="7_2_6_1_button_mappings">7.2.6.1. Button Mappings</h4> |
| 3055 | |
| 3056 | |
| 3057 | <p>Android Television device implementations MUST support the following key |
| 3058 | mappings:</p> |
| 3059 | <table> |
| 3060 | <tr> |
| 3061 | <th>Button</th> |
| 3062 | <th>HID Usage</strong><sup>2</sup></td> |
| 3063 | <th>Android Button</th> |
| 3064 | </tr> |
| 3065 | <tr> |
| 3066 | <td><a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BUTTON_A">A</a><sup>1</sup></td> |
| 3067 | <td>0x09 0x0001</td> |
| 3068 | <td>KEYCODE_BUTTON_A (96)</td> |
| 3069 | </tr> |
| 3070 | <tr> |
| 3071 | <td><a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BUTTON_B">B</a><sup>1</sup></td> |
| 3072 | <td>0x09 0x0002</td> |
| 3073 | <td>KEYCODE_BUTTON_B (97)</td> |
| 3074 | </tr> |
| 3075 | <tr> |
| 3076 | <td><a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BUTTON_X">X</a><sup>1</sup></td> |
| 3077 | <td>0x09 0x0004</td> |
| 3078 | <td>KEYCODE_BUTTON_X (99)</td> |
| 3079 | </tr> |
| 3080 | <tr> |
| 3081 | <td><a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BUTTON_Y">Y</a><sup>1</sup></td> |
| 3082 | <td>0x09 0x0005</td> |
| 3083 | <td>KEYCODE_BUTTON_Y (100)</td> |
| 3084 | </tr> |
| 3085 | <tr> |
| 3086 | <td><a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_DPAD_UP">D-pad up</a><sup>1</sup></p> |
| 3087 | |
| 3088 | <p><a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_DPAD_DOWN">D-pad down</a><sup>1</sup></td> |
Unsuk Jung | 2e62f9a | 2015-07-16 23:01:44 -0700 | [diff] [blame] | 3089 | <td>0x01 0x0039<sup>3</sup></td> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 3090 | <td><a href="http://developer.android.com/reference/android/view/MotionEvent.html#AXIS_HAT_Y">AXIS_HAT_Y</a><sup>4</sup></td> |
| 3091 | </tr> |
| 3092 | <tr> |
| 3093 | <td><a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_DPAD_LEFT">D-pad left</a>1</p> |
| 3094 | |
| 3095 | <p><a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_DPAD_RIGHT">D-pad right</a><sup>1</sup></td> |
Unsuk Jung | 2e62f9a | 2015-07-16 23:01:44 -0700 | [diff] [blame] | 3096 | <td>0x01 0x0039<sup>3</sup></td> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 3097 | <td><a href="http://developer.android.com/reference/android/view/MotionEvent.html#AXIS_HAT_X">AXIS_HAT_X</a><sup>4</sup></td> |
| 3098 | </tr> |
| 3099 | <tr> |
| 3100 | <td><a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BUTTON_L1">Left shoulder button</a><sup>1</sup></td> |
| 3101 | <td>0x09 0x0007</td> |
| 3102 | <td>KEYCODE_BUTTON_L1 (102)</td> |
| 3103 | </tr> |
| 3104 | <tr> |
| 3105 | <td><a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BUTTON_R1">Right shoulder button</a><sup>1</sup></td> |
| 3106 | <td>0x09 0x0008</td> |
| 3107 | <td>KEYCODE_BUTTON_R1 (103)</td> |
| 3108 | </tr> |
| 3109 | <tr> |
| 3110 | <td><a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BUTTON_THUMBL">Left stick click</a><sup>1</sup></td> |
| 3111 | <td>0x09 0x000E</td> |
| 3112 | <td>KEYCODE_BUTTON_THUMBL (106)</td> |
| 3113 | </tr> |
| 3114 | <tr> |
| 3115 | <td><a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BUTTON_THUMBR">Right stick click</a><sup>1</sup></td> |
| 3116 | <td>0x09 0x000F</td> |
| 3117 | <td>KEYCODE_BUTTON_THUMBR (107)</td> |
| 3118 | </tr> |
| 3119 | <tr> |
| 3120 | <td><a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_HOME">Home</a><sup>1</sup></td> |
| 3121 | <td>0x0c 0x0223</td> |
| 3122 | <td>KEYCODE_HOME (3)</td> |
| 3123 | </tr> |
| 3124 | <tr> |
| 3125 | <td><a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BACK">Back</a><sup>1</sup></td> |
| 3126 | <td>0x0c 0x0224</td> |
| 3127 | <td>KEYCODE_BACK (4)</td> |
| 3128 | </tr> |
| 3129 | </table> |
| 3130 | |
| 3131 | |
| 3132 | <p class="table_footnote">1 [<a href="http://developer.android.com/reference/android/view/KeyEvent.html">Resources, 72</a>]</p> |
| 3133 | |
| 3134 | <p class="table_footnote">2 The above HID usages must be declared within a Game pad CA (0x01 0x0005).</p> |
| 3135 | |
| 3136 | <p class="table_footnote">3 This usage must have a Logical Minimum of 0, a Logical Maximum of 7, a |
| 3137 | Physical Minimum of 0, a Physical Maximum of 315, Units in Degrees, and a |
| 3138 | Report Size of 4. The logical value is defined to be the clockwise rotation |
| 3139 | away from the vertical axis; for example, a logical value of 0 represents no |
| 3140 | rotation and the up button being pressed, while a logical value of 1 represents |
| 3141 | a rotation of 45 degrees and both the up and left keys being pressed.</p> |
| 3142 | |
| 3143 | <p class="table_footnote">4 [<a href="http://developer.android.com/reference/android/view/MotionEvent.html">Resources, 71</a>]</p> |
| 3144 | |
| 3145 | <table> |
| 3146 | <tr> |
| 3147 | <th>Analog Controls</strong><sup>1</sup></td> |
| 3148 | <th>HID Usage</th> |
| 3149 | <th>Android Button</th> |
| 3150 | </tr> |
| 3151 | <tr> |
| 3152 | <td><a href="http://developer.android.com/reference/android/view/MotionEvent.html#AXIS_LTRIGGER">Left Trigger</a></td> |
| 3153 | <td>0x02 0x00C5</td> |
| 3154 | <td>AXIS_LTRIGGER </td> |
| 3155 | </tr> |
| 3156 | <tr> |
| 3157 | <td><a href="http://developer.android.com/reference/android/view/MotionEvent.html#AXIS_THROTTLE">Right Trigger</a></td> |
| 3158 | <td>0x02 0x00C4</td> |
| 3159 | <td>AXIS_RTRIGGER </td> |
| 3160 | </tr> |
| 3161 | <tr> |
| 3162 | <td><a href="http://developer.android.com/reference/android/view/MotionEvent.html#AXIS_Y">Left Joystick</a></td> |
| 3163 | <td>0x01 0x0030</p> |
| 3164 | |
| 3165 | <p>0x01 0x0031</td> |
| 3166 | <td>AXIS_X</p> |
| 3167 | |
| 3168 | <p>AXIS_Y</td> |
| 3169 | </tr> |
| 3170 | <tr> |
| 3171 | <td><a href="http://developer.android.com/reference/android/view/MotionEvent.html#AXIS_Z">Right Joystick</a></td> |
| 3172 | <td>0x01 0x0032</p> |
| 3173 | |
| 3174 | <p>0x01 0x0035</td> |
| 3175 | <td>AXIS_Z</p> |
| 3176 | |
| 3177 | <p>AXIS_RZ</td> |
| 3178 | </tr> |
| 3179 | </table> |
| 3180 | |
| 3181 | |
| 3182 | <p class="table_footnote">1 [<a href="http://developer.android.com/reference/android/view/MotionEvent.html">Resources, 71</a>]</p> |
| 3183 | |
| 3184 | <h3 id="7_2_7_remote_control">7.2.7. Remote Control</h3> |
| 3185 | |
| 3186 | |
| 3187 | <p>Android Television device implementations SHOULD provide a remote control to |
| 3188 | allow users to access the TV interface. The remote control MAY be a physical |
| 3189 | remote or can be a software-based remote that is accessible from a mobile phone |
| 3190 | or tablet. The remote control MUST meet the requirements defined below.</p> |
| 3191 | |
| 3192 | <ul> |
| 3193 | <li><strong>Search affordance</strong>. Device implementations MUST fire KEYCODE_SEARCH when the user invokes voice search either on the physical or software-based remote.</li> |
| 3194 | <li><strong>Navigation</strong>. All Android Television remotes MUST include Back, Home, and Select buttons and |
| 3195 | support for D-pad events [<a href="http://developer.android.com/reference/android/view/KeyEvent.html">Resources, 72</a>].</li> |
| 3196 | </ul> |
| 3197 | |
| 3198 | <h2 id="7_3_sensors">7.3. Sensors</h2> |
| 3199 | |
| 3200 | |
| 3201 | <p>Android includes APIs for accessing a variety of sensor types. Devices |
| 3202 | implementations generally MAY omit these sensors, as provided for in the |
| 3203 | following subsections. If a device includes a particular sensor type that has a |
| 3204 | corresponding API for third-party developers, the device implementation MUST |
| 3205 | implement that API as described in the Android SDK documentation and the |
| 3206 | Android Open Source documentation on sensors [<a href="http://source.android.com/devices/sensors/">Resources, 73</a>]. For example, device implementations:</p> |
| 3207 | |
| 3208 | <ul> |
| 3209 | <li>MUST accurately report the presence or absence of sensors per the |
| 3210 | android.content.pm.PackageManager class [<a href="http://developer.android.com/reference/android/content/pm/PackageManager.html">Resources, 53]</a>.</li> |
| 3211 | <li>MUST return an accurate list of supported sensors via the |
| 3212 | SensorManager.getSensorList() and similar methods.</li> |
| 3213 | <li>MUST behave reasonably for all other sensor APIs (for example, by returning |
| 3214 | true or false as appropriate when applications attempt to register listeners, |
| 3215 | not calling sensor listeners when the corresponding sensors are not present; |
| 3216 | etc.).</li> |
| 3217 | <li>MUST report all sensor measurements using the relevant International System of |
| 3218 | Units (metric) values for each sensor type as defined in the Android SDK |
| 3219 | documentation [<a href="http://developer.android.com/reference/android/hardware/SensorEvent.html">Resources, 74</a>].</li> |
| 3220 | <li>SHOULD report the event time in nanoseconds as defined in the Android SDK |
| 3221 | documentation, representing the time the event happened and synchronized with |
| 3222 | the SystemClock.elapsedRealtimeNano() clock. Existing and new Android devices |
Bert McMeen | 816a242 | 2015-09-29 16:33:19 -0700 | [diff] [blame] | 3223 | are <strong>STRONGLY RECOMMENDED</strong> to meet these requirement so they will be able to upgrade to the future |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 3224 | platform releases where this might become a REQUIRED component. The |
| 3225 | synchronization error SHOULD be below 100 milliseconds [<a href="http://developer.android.com/reference/android/hardware/SensorEvent.html#timestamp">Resources, 75</a>].</li> |
| 3226 | </ul> |
| 3227 | |
| 3228 | <p>The list above is not comprehensive; the documented behavior of the Android SDK |
| 3229 | and the Android Open Source Documentations on Sensors [<a href="http://source.android.com/devices/sensors/">Resources, 73</a>] is to be considered authoritative.</p> |
| 3230 | |
| 3231 | <p>Some sensor types are composite, meaning they can be derived from data provided |
| 3232 | by one or more other sensors. (Examples include the orientation sensor, and the |
| 3233 | linear acceleration sensor.) Device implementations SHOULD implement these |
| 3234 | sensor types, when they include the prerequisite physical sensors as described |
| 3235 | in [<a href="https://source.android.com/devices/sensors/sensor-types.html">Resources, 76</a>]. |
| 3236 | If a device implementation includes a composite sensor it MUST implement the |
| 3237 | sensor as described in the Android Open Source documentation on composite |
| 3238 | sensors [<a href="https://source.android.com/devices/sensors/sensor-types.html#composite_sensor_type_summary">Resources, 76</a>].</p> |
| 3239 | |
| 3240 | <p>Some Android sensors support a “continuous” trigger mode, which returns data |
| 3241 | continuously [<a href="https://source.android.com/devices/sensors/report-modes.html#continuous">Resources, 77</a>]. For any API indicated by the Android SDK documentation to be a continuous |
| 3242 | sensor, device implementations MUST continuously provide periodic data samples |
| 3243 | that SHOULD have a jitter below 3%, where jitter is defined as the standard |
| 3244 | deviation of the difference of the reported timestamp values between |
| 3245 | consecutive events.</p> |
| 3246 | |
| 3247 | <p>Note that the device implementations MUST ensure that the sensor event stream |
| 3248 | MUST NOT prevent the device CPU from entering a suspend state or waking up from |
| 3249 | a suspend state.</p> |
| 3250 | |
| 3251 | <p>Finally, when several sensors are activated, the power consumption SHOULD NOT |
| 3252 | exceed the sum of the individual sensor’s reported power consumption.</p> |
| 3253 | |
| 3254 | <h3 id="7_3_1_accelerometer">7.3.1. Accelerometer</h3> |
| 3255 | |
| 3256 | |
| 3257 | <p>Device implementations SHOULD include a 3-axis accelerometer. Android Handheld |
Bert McMeen | 816a242 | 2015-09-29 16:33:19 -0700 | [diff] [blame] | 3258 | devices and Android Watch devices are STRONGLY RECOMMENDED to include this |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 3259 | sensor. If a device implementation does include a 3-axis accelerometer, it:</p> |
| 3260 | |
| 3261 | <ul> |
| 3262 | <li>MUST implement and report TYPE_ACCELEROMETER sensor [<a href="http://developer.android.com/reference/android/hardware/Sensor.html#TYPE_ACCELEROMETER">Resources, 78</a>].</li> |
| 3263 | <li>MUST be able to report events up to a frequency of at least 50 Hz for |
| 3264 | Android Watch devices as such devices have a stricter power constraint and |
| 3265 | 100 Hz for all other device types.</li> |
| 3266 | <li>SHOULD report events up to at least 200 Hz.</li> |
| 3267 | <li>MUST comply with the Android sensor coordinate system as detailed in the |
| 3268 | Android APIs [<a href="http://developer.android.com/reference/android/hardware/SensorEvent.html">Resources, 74</a>].</li> |
| 3269 | <li>MUST be capable of measuring from freefall up to four times the gravity (4g) or |
| 3270 | more on any axis.</li> |
| 3271 | <li>MUST have a resolution of at least 8-bits and SHOULD have a resolution of at |
| 3272 | least 16-bits.</li> |
| 3273 | <li>SHOULD be calibrated while in use if the characteristics changes over the life |
| 3274 | cycle and compensated, and preserve the compensation parameters between device |
| 3275 | reboots.</li> |
| 3276 | <li>SHOULD be temperature compensated.</li> |
| 3277 | <li>MUST have a standard deviation no greater than 0.05 m/s^, where the standard |
| 3278 | deviation should be calculated on a per axis basis on samples collected over a |
| 3279 | period of at least 3 seconds at the fastest sampling rate.</li> |
| 3280 | <li>SHOULD implement the TYPE_SIGNIFICANT_MOTION, TYPE_TILT_DETECTOR, |
| 3281 | TYPE_STEP_DETECTOR, TYPE_STEP_COUNTER composite sensors as described in the |
Bert McMeen | 816a242 | 2015-09-29 16:33:19 -0700 | [diff] [blame] | 3282 | Android SDK document. Existing and new Android devices are <strong>STRONGLY RECOMMENDED</strong> to implement the TYPE_SIGNIFICANT_MOTION composite sensor. If any of these |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 3283 | sensors are implemented, the sum of their power consumption MUST always be less |
| 3284 | than 4 mW and SHOULD each be below 2 mW and 0.5 mW for when the device is in a |
| 3285 | dynamic or static condition.</li> |
| 3286 | <li>If a gyroscope sensor is included, MUST implement the TYPE_GRAVITY and |
| 3287 | TYPE_LINEAR_ACCELERATION composite sensors and SHOULD implement the |
| 3288 | TYPE_GAME_ROTATION_VECTOR composite sensor. Existing and new Android devices |
Bert McMeen | 816a242 | 2015-09-29 16:33:19 -0700 | [diff] [blame] | 3289 | are STRONGLY RECOMMENDED to implement the TYPE_GAME_ROTATION_VECTOR sensor.</li> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 3290 | <li>SHOULD implement a TYPE_ROTATION_VECTOR composite sensor, if a gyroscope sensor |
| 3291 | and a magnetometer sensor is also included.</li> |
| 3292 | </ul> |
| 3293 | |
| 3294 | <h3 id="7_3_2_magnetometer">7.3.2. Magnetometer</h3> |
| 3295 | |
| 3296 | |
| 3297 | <p>Device implementations SHOULD include a 3-axis magnetometer (compass). If a |
| 3298 | device does include a 3-axis magnetometer, it:</p> |
| 3299 | |
| 3300 | <ul> |
| 3301 | <li>MUST implement the TYPE_MAGNETIC_FIELD sensor and SHOULD also implement |
| 3302 | TYPE_MAGNETIC_FIELD_UNCALIBRATED sensor. Existing and new Android devices are |
Bert McMeen | 816a242 | 2015-09-29 16:33:19 -0700 | [diff] [blame] | 3303 | STRONGLY RECOMMENDED to implement the TYPE_MAGNETIC_FIELD_UNCALIBRATED sensor.</li> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 3304 | <li>MUST be able to report events up to a frequency of at least 10 Hz and SHOULD |
| 3305 | report events up to at least 50 Hz.</li> |
| 3306 | <li>MUST comply with the Android sensor coordinate system as detailed in the |
| 3307 | Android APIs [<a href="http://developer.android.com/reference/android/hardware/SensorEvent.html">Resources, 74</a>].</li> |
| 3308 | <li>MUST be capable of measuring between -900 µT and +900 µT on each axis before |
| 3309 | saturating.</li> |
| 3310 | <li>MUST have a hard iron offset value less than 700 µT and SHOULD have a value |
| 3311 | below 200 µT, by placing the magnetometer far from dynamic (current-induced) |
| 3312 | and static (magnet-induced) magnetic fields.</li> |
| 3313 | <li>MUST have a resolution equal or denser than 0.6 µT and SHOULD have a resolution |
| 3314 | equal or denser than 0.2 µ.</li> |
| 3315 | <li>SHOULD be temperature compensated.</li> |
| 3316 | <li>MUST support online calibration and compensation of the hard iron bias, and |
| 3317 | preserve the compensation parameters between device reboots.</li> |
| 3318 | <li>MUST have the soft iron compensation applied—the calibration can be done either |
| 3319 | while in use or during the production of the device.</li> |
| 3320 | <li>SHOULD have a standard deviation, calculated on a per axis basis on samples |
| 3321 | collected over a period of at least 3 seconds at the fastest sampling rate, no |
| 3322 | greater than 0.5 µT.</li> |
| 3323 | <li>SHOULD implement a TYPE_ROTATION_VECTOR composite sensor, if an accelerometer |
| 3324 | sensor and a gyroscope sensor is also included.</li> |
| 3325 | <li>MAY implement the TYPE_GEOMAGNETIC_ROTATION_VECTOR sensor if an accelerometer |
| 3326 | sensor is also implemented. However if implemented, it MUST consume less than |
| 3327 | 10 mW and SHOULD consume less than 3 mW when the sensor is registered for batch |
| 3328 | mode at 10 Hz.</li> |
| 3329 | </ul> |
| 3330 | |
| 3331 | <h3 id="7_3_3_gps">7.3.3. GPS</h3> |
| 3332 | |
| 3333 | |
| 3334 | <p>Device implementations SHOULD include a GPS receiver. If a device |
| 3335 | implementation does include a GPS receiver, it SHOULD include some form of“assisted GPS” technique to minimize GPS lock-on time.</p> |
| 3336 | |
| 3337 | <h3 id="7_3_4_gyroscope">7.3.4. Gyroscope</h3> |
| 3338 | |
| 3339 | |
| 3340 | <p>Device implementations SHOULD include a gyroscope (angular change sensor). |
| 3341 | Devices SHOULD NOT include a gyroscope sensor unless a 3-axis accelerometer is |
| 3342 | also included. If a device implementation includes a gyroscope, it:</p> |
| 3343 | |
| 3344 | <ul> |
| 3345 | <li>MUST implement the TYPE_GYROSCOPE sensor and SHOULD also implement |
| 3346 | TYPE_GYROSCOPE_UNCALIBRATED sensor. Existing and new Android devices are |
Bert McMeen | 816a242 | 2015-09-29 16:33:19 -0700 | [diff] [blame] | 3347 | STRONGLY RECOMMENDED to implement the SENSOR_TYPE_GYROSCOPE_UNCALIBRATED sensor.</li> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 3348 | <li>MUST be capable of measuring orientation changes up to 1,000 degrees per second.</li> |
| 3349 | <li>MUST be able to report events up to a frequency of at least 50 Hz for |
| 3350 | Android Watch devices as such devices have a stricter power constraint and |
| 3351 | 100 Hz for all other device types.</li> |
| 3352 | <li>SHOULD report events up to at least 200 Hz.</li> |
| 3353 | <li>MUST have a resolution of 12-bits or more and SHOULD have a resolution of |
| 3354 | 16-bits or more.</li> |
| 3355 | <li>MUST be temperature compensated.</li> |
| 3356 | <li>MUST be calibrated and compensated while in use, and preserve the compensation |
| 3357 | parameters between device reboots.</li> |
| 3358 | <li>MUST have a variance no greater than 1e-7 rad^2 / s^2 per Hz (variance per Hz, |
| 3359 | or rad^2 / s). The variance is allowed to vary with the sampling rate, but must |
| 3360 | be constrained by this value. In other words, if you measure the variance of |
| 3361 | the gyro at 1 Hz sampling rate it should be no greater than 1e-7 rad^2/s^2.</li> |
| 3362 | <li>SHOULD implement a TYPE_ROTATION_VECTOR composite sensor, if an accelerometer |
| 3363 | sensor and a magnetometer sensor is also included.</li> |
| 3364 | <li>If an accelerometer sensor is included, MUST implement the TYPE_GRAVITY and |
| 3365 | TYPE_LINEAR_ACCELERATION composite sensors and SHOULD implement the |
| 3366 | TYPE_GAME_ROTATION_VECTOR composite sensor. Existing and new Android devices |
Bert McMeen | 816a242 | 2015-09-29 16:33:19 -0700 | [diff] [blame] | 3367 | are STRONGLY RECOMMENDED to implement the TYPE_GAME_ROTATION_VECTOR sensor.</li> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 3368 | </ul> |
| 3369 | |
| 3370 | <h3 id="7_3_5_barometer">7.3.5. Barometer</h3> |
| 3371 | |
| 3372 | |
| 3373 | <p>Device implementations SHOULD include a barometer (ambient air pressure |
| 3374 | sensor). If a device implementation includes a barometer, it:</p> |
| 3375 | |
| 3376 | <ul> |
| 3377 | <li>MUST implement and report TYPE_PRESSURE sensor.</li> |
| 3378 | <li>MUST be able to deliver events at 5 Hz or greater.</li> |
| 3379 | <li>MUST have adequate precision to enable estimating altitude.</li> |
| 3380 | <li>MUST be temperature compensated.</li> |
| 3381 | </ul> |
| 3382 | |
| 3383 | <h3 id="7_3_6_thermometer">7.3.6. Thermometer</h3> |
| 3384 | |
| 3385 | |
| 3386 | <p>Device implementations MAY include an ambient thermometer (temperature sensor). |
| 3387 | If present, it MUST be defined as SENSOR_TYPE_AMBIENT_TEMPERATURE and it MUST |
| 3388 | measure the ambient (room) temperature in degrees Celsius.</p> |
| 3389 | |
| 3390 | <p>Device implementations MAY but SHOULD NOT include a CPU temperature sensor. If |
| 3391 | present, it MUST be defined as SENSOR_TYPE_TEMPERATURE, it MUST measure the |
| 3392 | temperature of the device CPU, and it MUST NOT measure any other temperature. |
| 3393 | Note the SENSOR_TYPE_TEMPERATURE sensor type was deprecated in Android 4.0.</p> |
| 3394 | |
| 3395 | <h3 id="7_3_7_photometer">7.3.7. Photometer</h3> |
| 3396 | |
| 3397 | |
| 3398 | <p>Device implementations MAY include a photometer (ambient light sensor).</p> |
| 3399 | |
| 3400 | <h3 id="7_3_8_proximity_sensor">7.3.8. Proximity Sensor</h3> |
| 3401 | |
| 3402 | |
| 3403 | <p>Device implementations MAY include a proximity sensor. Devices that can make a |
| 3404 | voice call and indicate any value other than PHONE_TYPE_NONE in getPhoneType |
| 3405 | SHOULD include a proximity sensor. If a device implementation does include a |
| 3406 | proximity sensor, it:</p> |
| 3407 | |
| 3408 | <ul> |
| 3409 | <li>MUST measure the proximity of an object in the same direction as the screen. |
| 3410 | That is, the proximity sensor MUST be oriented to detect objects close to the |
| 3411 | screen, as the primary intent of this sensor type is to detect a phone in use |
| 3412 | by the user. If a device implementation includes a proximity sensor with any |
| 3413 | other orientation, it MUST NOT be accessible through this API.</li> |
| 3414 | <li>MUST have 1-bit of accuracy or more.</li> |
| 3415 | </ul> |
| 3416 | |
| 3417 | <h2 id="7_4_data_connectivity">7.4. Data Connectivity</h2> |
| 3418 | |
| 3419 | |
| 3420 | <h3 id="7_4_1_telephony">7.4.1. Telephony</h3> |
| 3421 | |
| 3422 | |
| 3423 | <p>“Telephony” as used by the Android APIs and this document refers specifically |
| 3424 | to hardware related to placing voice calls and sending SMS messages via a GSM |
| 3425 | or CDMA network. While these voice calls may or may not be packet-switched, |
| 3426 | they are for the purposes of Android considered independent of any data |
| 3427 | connectivity that may be implemented using the same network. In other words, |
| 3428 | the Android “telephony” functionality and APIs refer specifically to voice |
| 3429 | calls and SMS. For instance, device implementations that cannot place calls or |
| 3430 | send/receive SMS messages MUST NOT report the android.hardware.telephony |
| 3431 | feature or any subfeatures, regardless of whether they use a cellular network |
| 3432 | for data connectivity.</p> |
| 3433 | |
| 3434 | <p>Android MAY be used on devices that do not include telephony hardware. That is, |
| 3435 | Android is compatible with devices that are not phones. However, if a device |
| 3436 | implementation does include GSM or CDMA telephony, it MUST implement full |
| 3437 | support for the API for that technology. Device implementations that do not |
| 3438 | include telephony hardware MUST implement the full APIs as no-ops.</p> |
| 3439 | |
| 3440 | <h3 id="7_4_2_ieee_802_11_wi-fi">7.4.2. IEEE 802.11 (Wi-Fi)</h3> |
| 3441 | |
| 3442 | <div class="note"> |
| 3443 | <p>Android Television device implementations MUST include Wi-Fi support.</p> |
| 3444 | </div> |
| 3445 | |
| 3446 | |
| 3447 | <p>Android Television device implementations MUST include support for one or more |
| 3448 | forms of 802.11 (b/g/a/n, etc.) and other types of Android device |
| 3449 | implementation SHOULD include support for one or more forms of 802.11. If a |
| 3450 | device implementation does include support for 802.11 and exposes the |
| 3451 | functionality to a third-party application, it MUST implement the corresponding |
| 3452 | Android API and:</p> |
| 3453 | |
| 3454 | <ul> |
| 3455 | <li>MUST report the hardware feature flag android.hardware.wifi.</li> |
| 3456 | <li>MUST implement the multicast API as described in the SDK documentation [<a href="http://developer.android.com/reference/android/net/wifi/WifiManager.MulticastLock.html">Resources, 79</a>].</li> |
| 3457 | <li>MUST support multicast DNS (mDNS) and MUST NOT filter mDNS packets |
| 3458 | (224.0.0.251) at any time of operation including when the screen is not in an |
| 3459 | active state.</li> |
| 3460 | </ul> |
| 3461 | |
| 3462 | <h4 id="7_4_2_1_wi-fi_direct">7.4.2.1. Wi-Fi Direct</h4> |
| 3463 | |
| 3464 | |
| 3465 | <p>Device implementations SHOULD include support for Wi-Fi Direct (Wi-Fi |
| 3466 | peer-to-peer). If a device implementation does include support for Wi-Fi |
| 3467 | Direct, it MUST implement the corresponding Android API as described in the SDK |
| 3468 | documentation [<a href="http://developer.android.com/reference/android/net/wifi/p2p/WifiP2pManager.html">Resources, 80</a>]. If a device implementation includes support for Wi-Fi Direct, then it:</p> |
| 3469 | |
| 3470 | <ul> |
| 3471 | <li>MUST report the hardware feature android.hardware.wifi.direct.</li> |
| 3472 | <li>MUST support regular Wi-Fi operation.</li> |
| 3473 | <li>SHOULD support concurrent Wi-Fi and Wi-Fi Direct operation.</li> |
| 3474 | </ul> |
| 3475 | |
| 3476 | <h4 id="7_4_2_2_wi-fi_tunneled_direct_link_setup">7.4.2.2. Wi-Fi Tunneled Direct Link Setup</h4> |
| 3477 | |
| 3478 | <div class="note"> |
| 3479 | <p>Android Television device implementations MUST include support for Wi-Fi |
| 3480 | Tunneled Direct Link Setup (TDLS).</p> |
| 3481 | </div> |
| 3482 | |
| 3483 | |
| 3484 | <p>Android Television device implementations MUST include support for Wi-Fi |
| 3485 | Tunneled Direct Link Setup (TDLS) and other types of Android device |
| 3486 | implementations SHOULD include support for Wi-Fi TDLS as described in the |
| 3487 | Android SDK Documentation [<a href="http://developer.android.com/reference/android/net/wifi/WifiManager.html">Resources, 81</a>]. If a device implementation does include support for TDLS and TDLS is enabled |
| 3488 | by the WiFiManager API, the device:</p> |
| 3489 | |
| 3490 | <ul> |
| 3491 | <li>SHOULD use TDLS only when it is possible AND beneficial.</li> |
| 3492 | <li>SHOULD have some heuristic and NOT use TDLS when its performance might be worse |
| 3493 | than going through the Wi-Fi access point.</li> |
| 3494 | </ul> |
| 3495 | |
| 3496 | <h3 id="7_4_3_bluetooth">7.4.3. Bluetooth</h3> |
| 3497 | |
| 3498 | <div class="note"> |
| 3499 | <p>Android Watch and Automotive implementations MUST support Bluetooth. Android |
| 3500 | Television implementations MUST support Bluetooth and Bluetooth LE.</p> |
| 3501 | </div> |
| 3502 | |
| 3503 | |
| 3504 | <p>Android includes support for Bluetooth and Bluetooth Low Energy [<a href="http://developer.android.com/reference/android/bluetooth/package-summary.html">Resources, 82</a>]. Device implementations that include support for Bluetooth and Bluetooth Low |
| 3505 | Energy MUST declare the relevant platform features (android.hardware.bluetooth |
| 3506 | and android.hardware.bluetooth_le respectively) and implement the platform |
| 3507 | APIs. Device implementations SHOULD implement relevant Bluetooth profiles such |
| 3508 | as A2DP, AVCP, OBEX, etc. as appropriate for the device. Android Television |
| 3509 | device implementations MUST support Bluetooth and Bluetooth LE. </p> |
| 3510 | |
| 3511 | <p>Device implementations including support for Bluetooth Low Energy:</p> |
| 3512 | |
| 3513 | <ul> |
| 3514 | <li>MUST declare the hardware feature android.hardware.bluetooth_le.</li> |
| 3515 | <li>MUST enable the GATT (generic attribute profile) based Bluetooth APIs as |
| 3516 | described in the SDK documentation and [<a href="http://developer.android.com/reference/android/bluetooth/package-summary.html">Resources, 82</a>].</li> |
| 3517 | <li>SHOULD support offloading of the filtering logic to the bluetooth chipset when |
| 3518 | implementing the ScanFilter API [<a href="https://developer.android.com/reference/android/bluetooth/le/ScanFilter.html">Resources, 83</a>], and MUST report the correct value of where the filtering logic is implemented whenever queried via the |
| 3519 | android.bluetooth.BluetoothAdapter.isOffloadedFilteringSupported() method.</li> |
| 3520 | <li>SHOULD support offloading of the batched scanning to the bluetooth chipset, but |
| 3521 | if not supported, MUST report ‘false’ whenever queried via the |
| 3522 | android.bluetooth.BluetoothAdapater.isOffloadedScanBatchingSupported() method.</li> |
| 3523 | <li>SHOULD support multi advertisement with at least 4 slots, but if not supported, |
| 3524 | MUST report ‘false’ whenever queried via the |
| 3525 | android.bluetooth.BluetoothAdapter.isMultipleAdvertisementSupported() method.</li> |
| 3526 | </ul> |
| 3527 | |
| 3528 | <h3 id="7_4_4_near-field_communications">7.4.4. Near-Field Communications</h3> |
| 3529 | |
| 3530 | |
| 3531 | <p>Device implementations SHOULD include a transceiver and related hardware for |
| 3532 | Near-Field Communications (NFC). If a device implementation does include NFC |
| 3533 | hardware and plans to make it available to third-party apps, then it:</p> |
| 3534 | |
| 3535 | <ul> |
| 3536 | <li>MUST report the android.hardware.nfc feature from the |
| 3537 | android.content.pm.PackageManager.hasSystemFeature() method [<a href="http://developer.android.com/reference/android/content/pm/PackageManager.html">Resources, 53</a>].</li> |
| 3538 | <li>MUST be capable of reading and writing NDEF messages via the following NFC |
| 3539 | standards: |
| 3540 | <ul> |
| 3541 | <li>MUST be capable of acting as an NFC Forum reader/writer (as defined by the NFC |
| 3542 | Forum technical specification NFCForum-TS-DigitalProtocol-1.0) via the |
| 3543 | following NFC standards: |
| 3544 | <ul> |
| 3545 | <li>NfcA (ISO14443-3A)</li> |
| 3546 | <li>NfcB (ISO14443-3B)</li> |
Martijn Coenen | 048f4aa | 2015-09-17 14:24:55 +0200 | [diff] [blame] | 3547 | <li>NfcF (JIS X 6319-4)</li> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 3548 | <li>IsoDep (ISO 14443-4)</li> |
| 3549 | <li>NFC Forum Tag Types 1, 2, 3, 4 (defined by the NFC Forum)</li> |
| 3550 | </ul> |
Martijn Coenen | 048f4aa | 2015-09-17 14:24:55 +0200 | [diff] [blame] | 3551 | <li>MUST be capable of reading and writing NDEF messages as well as raw |
| 3552 | data via the following NFC standards:</li> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 3553 | <ul> |
| 3554 | <li>NfcV (ISO 15693)</li> |
| 3555 | </ul></li> |
Martijn Coenen | 048f4aa | 2015-09-17 14:24:55 +0200 | [diff] [blame] | 3556 | <li>SHOULD be capable of reading the barcode and URL (if encoded) of |
| 3557 | Thinfilm NFC Barcode |
| 3558 | [<a href="http://developer.android.com/reference/android/nfc/tech/NfcBarcode.html">Resources, XX</a>] products. |
| 3559 | </li> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 3560 | <li>MUST be capable of transmitting and receiving data via the following |
| 3561 | peer-to-peer standards and protocols: |
| 3562 | <ul> |
| 3563 | <li>ISO 18092</li> |
Martijn Coenen | 048f4aa | 2015-09-17 14:24:55 +0200 | [diff] [blame] | 3564 | <li>LLCP 1.2 (defined by the NFC Forum)</li> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 3565 | <li>SDP 1.0 (defined by the NFC Forum)</li> |
| 3566 | <li>NDEF Push Protocol [<a href="http://static.googleusercontent.com/media/source.android.com/en/us/compatibility/ndef-push-protocol.pdf">Resources, 84</a>]</li> |
| 3567 | <li>SNEP 1.0 (defined by the NFC Forum)</li> |
| 3568 | </ul></li> |
| 3569 | <li>MUST include support for Android Beam [<a href="http://developer.android.com/guide/topics/connectivity/nfc/nfc.html">Resources, 85</a>]: |
| 3570 | <ul> |
| 3571 | <li>MUST implement the SNEP default server. Valid NDEF messages received by the |
| 3572 | default SNEP server MUST be dispatched to applications using the |
| 3573 | android.nfc.ACTION_NDEF_DISCOVERED intent. Disabling Android Beam in settings |
| 3574 | MUST NOT disable dispatch of incoming NDEF message.</li> |
| 3575 | <li>MUST honor the android.settings.NFCSHARING_SETTINGS intent to show NFC sharing |
| 3576 | settings [<a href="http://developer.android.com/reference/android/provider/Settings.html#ACTION_NFCSHARING_SETTINGS">Resources, 86</a>].</li> |
| 3577 | <li>MUST implement the NPP server. Messages received by the NPP server MUST be |
| 3578 | processed the same way as the SNEP default server.</li> |
| 3579 | <li>MUST implement a SNEP client and attempt to send outbound P2P NDEF to the |
| 3580 | default SNEP server when Android Beam is enabled. If no default SNEP server is |
| 3581 | found then the client MUST attempt to send to an NPP server.</li> |
| 3582 | <li>MUST allow foreground activities to set the outbound P2P NDEF message using |
| 3583 | android.nfc.NfcAdapter.setNdefPushMessage, and |
| 3584 | android.nfc.NfcAdapter.setNdefPushMessageCallback, and |
| 3585 | android.nfc.NfcAdapter.enableForegroundNdefPush.</li> |
| 3586 | <li>SHOULD use a gesture or on-screen confirmation, such as 'Touch to Beam', before |
| 3587 | sending outbound P2P NDEF messages.</li> |
| 3588 | <li>SHOULD enable Android Beam by default and MUST be able to send and receive |
| 3589 | using Android Beam, even when another proprietary NFC P2p mode is turned on.</li> |
| 3590 | <li>MUST support NFC Connection handover to Bluetooth when the device supports |
| 3591 | Bluetooth Object Push Profile. Device implementations MUST support connection |
| 3592 | handover to Bluetooth when using android.nfc.NfcAdapter.setBeamPushUris, by |
| 3593 | implementing the “Connection Handover version 1.2” [<a href="http://members.nfc-forum.org/specs/spec_list/#conn_handover">Resources, 87</a>] and “Bluetooth Secure Simple Pairing Using NFC version 1.0” [<a href="http://members.nfc-forum.org/apps/group_public/download.php/18688/NFCForum-AD-BTSSP_1_1.pdf">Resources, 88</a>] specs from the NFC Forum. Such an implementation MUST implement the handover |
| 3594 | LLCP service with service name “urn:nfc:sn:handover” for exchanging the |
| 3595 | handover request/select records over NFC, and it MUST use the Bluetooth Object |
| 3596 | Push Profile for the actual Bluetooth data transfer. For legacy reasons (to |
| 3597 | remain compatible with Android 4.1 devices), the implementation SHOULD still |
| 3598 | accept SNEP GET requests for exchanging the handover request/select records |
| 3599 | over NFC. However an implementation itself SHOULD NOT send SNEP GET requests |
| 3600 | for performing connection handover.</li> |
| 3601 | </ul></li> |
| 3602 | <li>MUST poll for all supported technologies while in NFC discovery mode.</li> |
| 3603 | <li>SHOULD be in NFC discovery mode while the device is awake with the screen |
| 3604 | active and the lock-screen unlocked.</li> |
| 3605 | </ul> |
| 3606 | </ul> |
| 3607 | |
| 3608 | <p>(Note that publicly available links are not available for the JIS, ISO, and NFC |
| 3609 | Forum specifications cited above.)</p> |
| 3610 | |
| 3611 | <p>Android includes support for NFC Host Card Emulation (HCE) mode. If a |
| 3612 | device implementation does include an NFC controller chipset capable of HCE and |
| 3613 | Application ID (AID) routing, then it:</p> |
| 3614 | |
| 3615 | <ul> |
| 3616 | <li>MUST report the android.hardware.nfc.hce feature constant.</li> |
| 3617 | <li>MUST support NFC HCE APIs as defined in the Android SDK [<a href="http://developer.android.com/guide/topics/connectivity/nfc/hce.html">Resources, 10</a>].</li> |
| 3618 | </ul> |
| 3619 | |
| 3620 | <p>Additionally, device implementations MAY include reader/writer support for the |
| 3621 | following MIFARE technologies.</p> |
| 3622 | |
| 3623 | <ul> |
| 3624 | <li>MIFARE Classic</li> |
| 3625 | <li>MIFARE Ultralight</li> |
| 3626 | <li>NDEF on MIFARE Classic</li> |
| 3627 | </ul> |
| 3628 | |
| 3629 | <p>Note that Android includes APIs for these MIFARE types. If a device |
| 3630 | implementation supports MIFARE in the reader/writer role, it:</p> |
| 3631 | |
| 3632 | <ul> |
| 3633 | <li>MUST implement the corresponding Android APIs as documented by the Android SDK.</li> |
| 3634 | <li>MUST report the feature com.nxp.mifare from the |
Martijn Coenen | 048f4aa | 2015-09-17 14:24:55 +0200 | [diff] [blame] | 3635 | android.content.pm.PackageManager.hasSystemFeature() method <a href="http://developer.android.com/reference/android/content/pm/PackageManager.html">[Resources, 53]</a>. Note that this is not a standard Android feature and as such does not appear |
| 3636 | as a constant in the android.content.pm.PackageManager class.</li> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 3637 | <li>MUST NOT implement the corresponding Android APIs nor report the com.nxp.mifare |
| 3638 | feature unless it also implements general NFC support as described in this |
| 3639 | section.</li> |
| 3640 | </ul> |
| 3641 | |
| 3642 | <p>If a device implementation does not include NFC hardware, it MUST NOT declare |
| 3643 | the android.hardware.nfc feature from the |
| 3644 | android.content.pm.PackageManager.hasSystemFeature() method [<a href="http://developer.android.com/reference/android/content/pm/PackageManager.html">Resources, 53]</a>, and MUST implement the Android NFC API as a no-op.</p> |
| 3645 | |
| 3646 | <p>As the classes android.nfc.NdefMessage and android.nfc.NdefRecord represent a |
| 3647 | protocol-independent data representation format, device implementations MUST |
| 3648 | implement these APIs even if they do not include support for NFC or declare the |
| 3649 | android.hardware.nfc feature.</p> |
| 3650 | |
| 3651 | <h3 id="7_4_5_minimum_network_capability">7.4.5. Minimum Network Capability</h3> |
| 3652 | |
| 3653 | |
| 3654 | <p>Device implementations MUST include support for one or more forms of data |
| 3655 | networking. Specifically, device implementations MUST include support for at |
| 3656 | least one data standard capable of 200Kbit/sec or greater. Examples of |
| 3657 | technologies that satisfy this requirement include EDGE, HSPA, EV-DO, 802.11g, |
| 3658 | Ethernet, Bluetooth PAN, etc.</p> |
| 3659 | |
| 3660 | <p>Device implementations where a physical networking standard (such as Ethernet) |
| 3661 | is the primary data connection SHOULD also include support for at least one |
| 3662 | common wireless data standard, such as 802.11 (Wi-Fi).</p> |
| 3663 | |
| 3664 | <p>Devices MAY implement more than one form of data connectivity.</p> |
| 3665 | |
| 3666 | <h3 id="7_4_6_sync_settings">7.4.6. Sync Settings</h3> |
| 3667 | |
| 3668 | |
| 3669 | <p>Device implementations MUST have the master auto-sync setting on by default so |
| 3670 | that the method getMasterSyncAutomatically() returns “true” [<a href="http://developer.android.com/reference/android/content/ContentResolver.html">Resources, 89</a>].</p> |
| 3671 | |
| 3672 | <h2 id="7_5_cameras">7.5. Cameras</h2> |
| 3673 | |
| 3674 | |
| 3675 | <p>Device implementations SHOULD include a rear-facing camera and MAY include a |
| 3676 | front-facing camera. A rear-facing camera is a camera located on the side of |
| 3677 | the device opposite the display; that is, it images scenes on the far side of |
| 3678 | the device, like a traditional camera. A front-facing camera is a camera |
| 3679 | located on the same side of the device as the display; that is, a camera |
| 3680 | typically used to image the user, such as for video conferencing and similar |
| 3681 | applications.</p> |
| 3682 | |
| 3683 | <p>If a device implementation includes at least one camera, it SHOULD be possible |
| 3684 | for an application to simultaneously allocate 3 bitmaps equal to the size of |
| 3685 | the images produced by the largest-resolution camera sensor on the device.</p> |
| 3686 | |
| 3687 | <h3 id="7_5_1_rear-facing_camera">7.5.1. Rear-Facing Camera</h3> |
| 3688 | |
| 3689 | |
| 3690 | <p>Device implementations SHOULD include a rear-facing camera. If a device |
| 3691 | implementation includes at least one rear-facing camera, it:</p> |
| 3692 | |
| 3693 | <ul> |
| 3694 | <li>MUST report the feature flag android.hardware.camera and |
| 3695 | android.hardware.camera.any.</li> |
| 3696 | <li>MUST have a resolution of at least 2 megapixels.</li> |
| 3697 | <li>SHOULD have either hardware auto-focus or software auto-focus implemented in |
| 3698 | the camera driver (transparent to application software).</li> |
| 3699 | <li>MAY have fixed-focus or EDOF (extended depth of field) hardware.</li> |
| 3700 | <li>MAY include a flash. If the Camera includes a flash, the flash lamp MUST NOT be |
| 3701 | lit while an android.hardware.Camera.PreviewCallback instance has been |
| 3702 | registered on a Camera preview surface, unless the application has explicitly |
| 3703 | enabled the flash by enabling the FLASH_MODE_AUTO or FLASH_MODE_ON attributes |
| 3704 | of a Camera.Parameters object. Note that this constraint does not apply to the |
| 3705 | device’s built-in system camera application, but only to third-party |
| 3706 | applications using Camera.PreviewCallback.</li> |
| 3707 | </ul> |
| 3708 | |
| 3709 | <h3 id="7_5_2_front-facing_camera">7.5.2. Front-Facing Camera</h3> |
| 3710 | |
| 3711 | |
| 3712 | <p>Device implementations MAY include a front-facing camera. If a device |
| 3713 | implementation includes at least one front-facing camera, it:</p> |
| 3714 | |
| 3715 | <ul> |
| 3716 | <li>MUST report the feature flag android.hardware.camera.any and |
| 3717 | android.hardware.camera.front.</li> |
| 3718 | <li>MUST have a resolution of at least VGA (640x480 pixels).</li> |
| 3719 | <li>MUST NOT use a front-facing camera as the default for the Camera API. The |
| 3720 | camera API in Android has specific support for front-facing cameras and device |
| 3721 | implementations MUST NOT configure the API to to treat a front-facing camera as |
| 3722 | the default rear-facing camera, even if it is the only camera on the device.</li> |
| 3723 | <li>MAY include features (such as auto-focus, flash, etc.) available to rear-facing |
| 3724 | cameras as described in <a href="#7_5_1_rear-facing_camera">section 7.5.1</a>.</li> |
| 3725 | <li>MUST horizontally reflect (i.e. mirror) the stream displayed by an app in a |
| 3726 | CameraPreview, as follows: |
| 3727 | <ul> |
| 3728 | <li>If the device implementation is capable of being rotated by user (such as |
| 3729 | automatically via an accelerometer or manually via user input), the camera |
| 3730 | preview MUST be mirrored horizontally relative to the device’s current |
| 3731 | orientation.</li> |
| 3732 | <li>If the current application has explicitly requested that the Camera display be |
| 3733 | rotated via a call to the android.hardware.Camera.setDisplayOrientation()[<a href="http://developer.android.com/reference/android/hardware/Camera.html#setDisplayOrientation(int)">Resources, 90</a>] method, the camera preview MUST be mirrored horizontally relative to the |
| 3734 | orientation specified by the application.</li> |
| 3735 | <li>Otherwise, the preview MUST be mirrored along the device’s default horizontal |
| 3736 | axis.</li> |
| 3737 | </ul></li> |
| 3738 | <li>MUST mirror the image displayed by the postview in the same manner as the |
| 3739 | camera preview image stream. If the device implementation does not support |
| 3740 | postview, this requirement obviously does not apply.</li> |
| 3741 | <li>MUST NOT mirror the final captured still image or video streams returned to |
| 3742 | application callbacks or committed to media storage.</li> |
| 3743 | </ul> |
| 3744 | |
| 3745 | <h3 id="7_5_3_external_camera">7.5.3. External Camera</h3> |
| 3746 | |
| 3747 | |
| 3748 | <p>Device implementations with USB host mode MAY include support for an external |
| 3749 | camera that connects to the USB port. If a device includes support for an |
| 3750 | external camera, it:</p> |
| 3751 | |
| 3752 | <ul> |
| 3753 | <li>MUST declare the platform feature android.hardware.camera.external and |
| 3754 | android.hardware camera.any.</li> |
| 3755 | <li>MUST support USB Video Class (UVC 1.0 or higher).</li> |
| 3756 | <li>MAY support multiple cameras.</li> |
| 3757 | </ul> |
| 3758 | |
| 3759 | <p>Video compression (such as MJPEG) support is RECOMMENDED to enable transfer of |
| 3760 | high-quality unencoded streams (i.e. raw or independently compressed picture |
| 3761 | streams). Camera-based video encoding MAY be supported. If so, a simultaneous |
| 3762 | unencoded/ MJPEG stream (QVGA or greater resolution) MUST be accessible to the |
| 3763 | device implementation.</p> |
| 3764 | |
| 3765 | <h3 id="7_5_4_camera_api_behavior">7.5.4. Camera API Behavior</h3> |
| 3766 | |
| 3767 | |
| 3768 | <p>Android includes two API packages to access the camera, the newer |
| 3769 | android.hardware.camera2 API expose lower-level camera control to the app, |
| 3770 | including efficient zero-copy burst/streaming flows and per-frame controls of |
| 3771 | exposure, gain, white balance gains, color conversion, denoising, sharpening, |
| 3772 | and more.</p> |
| 3773 | |
| 3774 | <p>The older API package, android.hardware.Camera, is marked as deprecated in |
| 3775 | Android 5.0 but as it should still be available for apps to use Android device |
| 3776 | implementations MUST ensure the continued support of the API as described in |
| 3777 | this section and in the Android SDK.</p> |
| 3778 | |
| 3779 | <p>Device implementations MUST implement the following behaviors for the |
| 3780 | camera-related APIs, for all available cameras:</p> |
| 3781 | |
| 3782 | <ul> |
| 3783 | <li>If an application has never called |
| 3784 | android.hardware.Camera.Parameters.setPreviewFormat(int), then the device MUST |
| 3785 | use android.hardware.PixelFormat.YCbCr_420_SP for preview data provided to |
| 3786 | application callbacks.</li> |
| 3787 | <li>If an application registers an android.hardware.Camera.PreviewCallback instance |
| 3788 | and the system calls the onPreviewFrame() method when the preview format is |
| 3789 | YCbCr_420_SP, the data in the byte[] passed into onPreviewFrame() must further |
| 3790 | be in the NV21 encoding format. That is, NV21 MUST be the default.</li> |
| 3791 | <li>For android.hardware.Camera, device implementations MUST support the YV12 |
| 3792 | format (as denoted by the android.graphics.ImageFormat.YV12 constant) for |
| 3793 | camera previews for both front- and rear-facing cameras. (The hardware video |
| 3794 | encoder and camera may use any native pixel format, but the device |
| 3795 | implementation MUST support conversion to YV12.)</li> |
| 3796 | <li>For android.hardware.camera2, device implementations must support the |
| 3797 | android.hardware.ImageFormat.YUV_420_888 and android.hardware.ImageFormat.JPEG |
| 3798 | formats as outputs through the android.media.ImageReader API.</li> |
| 3799 | </ul> |
| 3800 | |
| 3801 | <p>Device implementations MUST still implement the full Camera API included in the |
| 3802 | Android SDK documentation [<a href="http://developer.android.com/reference/android/hardware/Camera.html">Resources, 91</a>], regardless of whether the device includes hardware autofocus or other |
| 3803 | capabilities. For instance, cameras that lack autofocus MUST still call any |
| 3804 | registered android.hardware.Camera.AutoFocusCallback instances (even though |
| 3805 | this has no relevance to a non-autofocus camera.) Note that this does apply to |
| 3806 | front-facing cameras; for instance, even though most front-facing cameras do |
| 3807 | not support autofocus, the API callbacks must still be “faked” as described.</p> |
| 3808 | |
| 3809 | <p>Device implementations MUST recognize and honor each parameter name defined as |
| 3810 | a constant on the android.hardware.Camera.Parameters class, if the underlying |
| 3811 | hardware supports the feature. If the device hardware does not support a |
| 3812 | feature, the API must behave as documented. Conversely, device implementations |
| 3813 | MUST NOT honor or recognize string constants passed to the |
| 3814 | android.hardware.Camera.setParameters() method other than those documented as |
| 3815 | constants on the android.hardware.Camera.Parameters. That is, device |
| 3816 | implementations MUST support all standard Camera parameters if the hardware |
| 3817 | allows, and MUST NOT support custom Camera parameter types. For instance, |
| 3818 | device implementations that support image capture using high dynamic range |
| 3819 | (HDR) imaging techniques MUST support camera parameter Camera.SCENE_MODE_HDR [<a href="http://developer.android.com/reference/android/hardware/Camera.Parameters.html">Resources, 92</a>].</p> |
| 3820 | |
| 3821 | <p>Because not all device implementations can fully support all the features of |
| 3822 | the android.hardware.camera2 API, device implementations MUST report the proper |
| 3823 | level of support with the android.info.supportedHardwareLevel property as |
| 3824 | described in the Android SDK [<a href="https://developer.android.com/reference/android/hardware/camera2/CameraCharacteristics.html#INFO_SUPPORTED_HARDWARE_LEVEL">Resources, 93]</a> and report the appropriate framework feature flags [<a href="http://source.android.com/devices/camera/versioning.html">Resources, 94]</a>. </p> |
| 3825 | |
| 3826 | <p>Device implementations MUST also declare its Individual camera capabilities of |
| 3827 | android.hardware.camera2 via the android.request.availableCapabilities property |
| 3828 | and declare the appropriate feature flags [<a href="http://source.android.com/devices/camera/versioning.html">Resources, 94]</a>; a device must define the feature flag if any of its attached camera devices supports the feature.</p> |
| 3829 | |
| 3830 | <p>Device implementations MUST broadcast the Camera.ACTION_NEW_PICTURE intent |
| 3831 | whenever a new picture is taken by the camera and the entry of the picture has |
| 3832 | been added to the media store.</p> |
| 3833 | |
| 3834 | <p>Device implementations MUST broadcast the Camera.ACTION_NEW_VIDEO intent |
| 3835 | whenever a new video is recorded by the camera and the entry of the picture has |
| 3836 | been added to the media store.</p> |
| 3837 | |
| 3838 | <h3 id="7_5_5_camera_orientation">7.5.5. Camera Orientation</h3> |
| 3839 | |
| 3840 | |
| 3841 | <p>Both front- and rear-facing cameras, if present, MUST be oriented so that the |
| 3842 | long dimension of the camera aligns with the screen’s long dimension. That is, |
| 3843 | when the device is held in the landscape orientation, cameras MUST capture |
| 3844 | images in the landscape orientation. This applies regardless of the device’s |
| 3845 | natural orientation; that is, it applies to landscape-primary devices as well |
| 3846 | as portrait-primary devices.</p> |
| 3847 | |
| 3848 | <h2 id="7_6_memory_and_storage">7.6. Memory and Storage</h2> |
| 3849 | |
| 3850 | |
| 3851 | <h3 id="7_6_1_minimum_memory_and_storage">7.6.1. Minimum Memory and Storage</h3> |
| 3852 | |
| 3853 | <div class="note"> |
| 3854 | <p>Android Television devices MUST have at least 5GB of non-volatile storage |
| 3855 | available for application private data.</p> |
| 3856 | </div> |
| 3857 | |
| 3858 | |
| 3859 | <p>The memory available to the kernel and userspace on device implementations MUST |
| 3860 | be at least equal or larger than the minimum values specified by the following |
| 3861 | table. (See <a href="#7_1_1_screen_configuration">section 7.1.1</a> for screen size and density definitions.)</p> |
| 3862 | <table> |
| 3863 | <tr> |
| 3864 | <th>Density and screen size</th> |
| 3865 | <th>32-bit device</th> |
| 3866 | <th>64-bit device</th> |
| 3867 | </tr> |
| 3868 | <tr> |
| 3869 | <td>Android Watch devices (due to smaller screens)</td> |
| 3870 | <td>416MB</td> |
| 3871 | <td>Not applicable</td> |
| 3872 | </tr> |
| 3873 | <tr> |
| 3874 | <td><ul> |
Unsuk Jung | 2e62f9a | 2015-07-16 23:01:44 -0700 | [diff] [blame] | 3875 | <li class="table_list">280dpi or lower on small/normal screens</li> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 3876 | <li class="table_list">mdpi or lower on large screens</li> |
| 3877 | <li class="table_list">ldpi or lower on extra large screens</li> |
| 3878 | </ul></td> |
| 3879 | <td>424MB</td> |
Unsuk Jung | 2e62f9a | 2015-07-16 23:01:44 -0700 | [diff] [blame] | 3880 | <td>704MB</td> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 3881 | </tr> |
| 3882 | <tr> |
| 3883 | <td><ul> |
| 3884 | <li class="table_list">xhdpi or higher on small/normal screens</li> |
| 3885 | <li class="table_list">hdpi or higher on large screens</li> |
| 3886 | <li class="table_list">mdpi or higher on extra large screens</li></ul></td> |
| 3887 | <td>512MB</td> |
| 3888 | <td>832MB</td> |
| 3889 | </tr> |
| 3890 | <tr> |
| 3891 | <td><ul> |
| 3892 | <li class="table_list">400dpi or higher on small/normal screens</li> |
| 3893 | <li class="table_list">xhdpi or higher on large screens</li> |
| 3894 | <li class="table_list">tvdpi or higher on extra large screens</li></ul></td> |
| 3895 | <td>896MB</td> |
| 3896 | <td>1280MB</td> |
| 3897 | </tr> |
| 3898 | <tr> |
| 3899 | <td><ul> |
| 3900 | <li class="table_list">560dpi or higher on small/normal screens</li> |
| 3901 | <li class="table_list">400dpi or higher on large screens</li> |
| 3902 | <li class="table_list">xhdpi or higher on extra large screens</li></ul></td> |
| 3903 | <td>1344MB</td> |
| 3904 | <td>1824MB</td> |
| 3905 | </tr> |
| 3906 | </table> |
| 3907 | |
| 3908 | |
| 3909 | <p>The minimum memory values MUST be in addition to any memory space already |
| 3910 | dedicated to hardware components such as radio, video, and so on that is not |
| 3911 | under the kernel’s control.</p> |
| 3912 | |
| 3913 | <p>Device implementations with less than 512MB of memory available to the kernel |
| 3914 | and userspace, unless an Android Watch, MUST return the value "true" for |
| 3915 | ActivityManager.isLowRamDevice().</p> |
| 3916 | |
| 3917 | <p>Android Television devices MUST have at least 5GB and other device |
| 3918 | implementations MUST have at least 1.5GB of non-volatile storage available for |
| 3919 | application private data. That is, the /data partition MUST be at least 5GB for |
| 3920 | Android Television devices and at least 1.5GB for other device implementations. |
Bert McMeen | 816a242 | 2015-09-29 16:33:19 -0700 | [diff] [blame] | 3921 | Device implementations that run Android are <strong>STRONGLY RECOMMENDED</strong> to have at least 3GB of non-volatile storage for application private data so |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 3922 | they will be able to upgrade to the future platform releases.</p> |
| 3923 | |
| 3924 | <p>The Android APIs include a Download Manager that applications MAY use to |
| 3925 | download data files [<a href="http://developer.android.com/reference/android/app/DownloadManager.html">Resources, 95</a>]. The device implementation of the Download Manager MUST be capable of |
| 3926 | downloading individual files of at least 100MB in size to the default “cache" |
| 3927 | location.</p> |
| 3928 | |
| 3929 | <h3 id="7_6_2_application_shared_storage">7.6.2. Application Shared Storage</h3> |
| 3930 | |
| 3931 | |
| 3932 | <p>Device implementations MUST offer shared storage for applications also often |
| 3933 | referred as “shared external storage”. </p> |
| 3934 | |
| 3935 | <p>Device implementations MUST be configured with shared storage mounted by |
| 3936 | default, “out of the box”. If the shared storage is not mounted on the Linux |
| 3937 | path /sdcard, then the device MUST include a Linux symbolic link from /sdcard |
| 3938 | to the actual mount point.</p> |
| 3939 | |
| 3940 | <p>Device implementations MAY have hardware for user-accessible removable storage, |
| 3941 | such as a Secure Digital (SD) card slot. If this slot is used to satisfy the |
| 3942 | shared storage requirement, the device implementation:</p> |
| 3943 | |
| 3944 | <ul> |
| 3945 | <li>MUST implement a toast or pop-up user interface warning the user when there is |
| 3946 | no SD card.</li> |
| 3947 | <li>MUST include a FAT-formatted SD card 1GB in size or larger OR show on the box |
| 3948 | and other material available at time of purchase that the SD card has to be |
| 3949 | separately purchased.</li> |
| 3950 | <li>MUST mount the SD card by default.</li> |
| 3951 | </ul> |
| 3952 | |
| 3953 | <p>Alternatively, device implementations MAY allocate internal (non-removable) |
| 3954 | storage as shared storage for apps as included in the upstream Android Open |
| 3955 | Source Project; device implementations SHOULD use this configuration and |
| 3956 | software implementation. If a device implementation uses internal |
| 3957 | (non-removable) storage to satisfy the shared storage requirement, that storage |
| 3958 | MUST be 1GB in size or larger and mounted on /sdcard (or /sdcard MUST be a |
| 3959 | symbolic link to the physical location if it is mounted elsewhere).</p> |
| 3960 | |
| 3961 | <p>Device implementations MUST enforce as documented the |
| 3962 | android.permission.WRITE_EXTERNAL_STORAGE permission on this shared storage. |
| 3963 | Shared storage MUST otherwise be writable by any application that obtains that |
| 3964 | permission.</p> |
| 3965 | |
| 3966 | <p>Device implementations that include multiple shared storage paths (such as both |
| 3967 | an SD card slot and shared internal storage) MUST NOT allow Android |
| 3968 | applications to write to the secondary external storage, except for their |
| 3969 | package-specific directories on the secondary external storage, but SHOULD |
| 3970 | expose content from both storage paths transparently through Android’s media |
| 3971 | scanner service and android.provider.MediaStore.</p> |
| 3972 | |
| 3973 | <p>Regardless of the form of shared storage used, if the device implementation |
| 3974 | has a USB port with USB peripheral mode support, it MUST provide some mechanism |
| 3975 | to access the contents of shared storage from a host computer. Device |
| 3976 | implementations MAY use USB mass storage, but SHOULD use Media Transfer Protocol |
| 3977 | to satisfy this requirement. If the device implementation supports Media |
| 3978 | Transfer Protocol, it:</p> |
| 3979 | |
| 3980 | <ul> |
| 3981 | <li>SHOULD be compatible with the reference Android MTP host, Android File Transfer |
| 3982 | [<a href="http://www.android.com/filetransfer">Resources, 96</a>].</li> |
| 3983 | <li>SHOULD report a USB device class of 0x00.</li> |
| 3984 | <li>SHOULD report a USB interface name of 'MTP'.</li> |
| 3985 | </ul> |
| 3986 | |
| 3987 | <h2 id="7_7_usb">7.7. USB</h2> |
| 3988 | |
| 3989 | |
| 3990 | <p>Device implementations SHOULD support USB peripheral mode and SHOULD support |
| 3991 | USB host mode.</p> |
| 3992 | |
| 3993 | <p>If a device implementation includes a USB port supporting peripheral mode:</p> |
| 3994 | |
| 3995 | <ul> |
| 3996 | <li>The port MUST be connectable to a USB host that has a standard type-A or type |
| 3997 | -C USB port.</li> |
| 3998 | <li>The port SHOULD use micro-A, micro-AB or type-C USB form factor. Existing and |
Bert McMeen | 816a242 | 2015-09-29 16:33:19 -0700 | [diff] [blame] | 3999 | new Android devices are <strong>STRONGLY RECOMMENDED to meet these requirements</strong> so they will be able to upgrade to the future platform releases.</li> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 4000 | <li>The port SHOULD be centered in the middle of an edge. Device implementations |
| 4001 | SHOULD either locate the port on the bottom of the device (according to natural |
| 4002 | orientation) or enable software screen rotation for all apps (including home |
| 4003 | screen), so that the display draws correctly when the device is oriented with |
Bert McMeen | 816a242 | 2015-09-29 16:33:19 -0700 | [diff] [blame] | 4004 | the port at bottom. Existing and new Android devices are <strong>STRONGLY RECOMMENDED to meet these requirements</strong> so they will be able to upgrade to future platform releases.</li> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 4005 | <li>It MUST allow a USB host connected with the Android device to access the |
| 4006 | contents of the shared storage volume using either USB mass storage or Media |
| 4007 | Transfer Protocol.</li> |
| 4008 | <li>It SHOULD implement the Android Open Accessory (AOA) API and specification as |
| 4009 | documented in the Android SDK documentation, and if it is an Android Handheld |
| 4010 | device it MUST implement the AOA API. Device implementations implementing the |
| 4011 | AOA specification: |
| 4012 | <ul> |
| 4013 | <li>MUST declare support for the hardware feature android.hardware.usb.accessory [<a href="http://developer.android.com/guide/topics/connectivity/usb/accessory.html">Resources, 97</a>].</li> |
| 4014 | <li>MUST implement the USB audio class as documented in the Android SDK |
| 4015 | documentation [<a href="http://developer.android.com/reference/android/hardware/usb/UsbConstants.html#USB_CLASS_AUDIO">Resources, 98</a>].</li> |
| 4016 | </ul></li> |
| 4017 | <li>It SHOULD implement support to draw 1.5 A current during HS chirp and traffic |
Bert McMeen | 816a242 | 2015-09-29 16:33:19 -0700 | [diff] [blame] | 4018 | as specified in the USB battery charging specification [<a href="http://www.usb.org/developers/docs/devclass_docs/USB_Battery_Charging_1.2.pdf">Resources, 99</a>]. Existing and new Android devices are <strong>STRONGLY RECOMMENDED to meet these requirements</strong> so they will be able to upgrade to the future platform releases.</li> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 4019 | <li>The value of iSerialNumber in USB standard device descriptor MUST be equal to |
| 4020 | the value of android.os.Build.SERIAL.</li> |
| 4021 | </ul> |
| 4022 | |
| 4023 | <p>If a device implementation includes a USB port supporting host mode, it:</p> |
| 4024 | |
| 4025 | <ul> |
| 4026 | <li>SHOULD use a type-C USB port, if the device implementation supports USB 3.1.</li> |
| 4027 | <li>MAY use a non-standard port form factor, but if so MUST ship with a cable or |
| 4028 | cables adapting the port to a standard type-A or type-C USB port.</li> |
| 4029 | <li>MAY use a micro-AB USB port, but if so SHOULD ship with a cable or cables |
| 4030 | adapting the port to a standard type-A or type-C USB port.</li> |
| 4031 | <li>is <strong>very strongly RECOMMENDED</strong> to implement the USB audio class as documented in the Android SDK |
| 4032 | documentation [<a href="http://developer.android.com/reference/android/hardware/usb/UsbConstants.html#USB_CLASS_AUDIO">Resources, 98</a>].</li> |
| 4033 | <li>MUST implement the Android USB host API as documented in the Android SDK, and |
| 4034 | MUST declare support for the hardware feature android.hardware.usb.host [<a href="http://developer.android.com/guide/topics/connectivity/usb/host.html">Resources, 100</a>].</li> |
| 4035 | <li>SHOULD support the Charging Downstream Port output current range of 1.5 A ~ 5 A |
| 4036 | as specified in the USB Battery Charging Specifications [<a href="http://www.usb.org/developers/docs/devclass_docs/USB_Battery_Charging_1.2.pdf">Resources, 99</a>].</li> |
| 4037 | </ul> |
| 4038 | |
| 4039 | <h2 id="7_8_audio">7.8. Audio</h2> |
| 4040 | |
| 4041 | |
| 4042 | <h3 id="7_8_1_microphone">7.8.1. Microphone</h3> |
| 4043 | |
| 4044 | <div class="note"> |
| 4045 | <p>Android Handheld, Watch, and Automotive implementations MUST include a |
| 4046 | microphone.</p> |
| 4047 | </div> |
| 4048 | |
| 4049 | |
| 4050 | <p>Device implementations MAY omit a microphone. However, if a device |
| 4051 | implementation omits a microphone, it MUST NOT report the |
| 4052 | android.hardware.microphone feature constant, and MUST implement the audio |
Glenn Kasten | 20cdbb7 | 2015-09-24 11:56:42 -0700 | [diff] [blame^] | 4053 | recording API at least as no-ops, per <a href="#7_hardware_compatibility">section 7</a>. |
| 4054 | Conversely, device implementations that do possess a microphone:</p> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 4055 | |
| 4056 | <ul> |
Glenn Kasten | 20cdbb7 | 2015-09-24 11:56:42 -0700 | [diff] [blame^] | 4057 | <li>MUST report the android.hardware.microphone feature constant</li> |
| 4058 | <li>MUST meet the audio recording requirements in <a href="#5_4_audio_recording">section 5.4</a></li> |
| 4059 | <li>MUST meet the audio latency requirements in <a href="#5_6_audio_latency">section 5.6</a></li> |
| 4060 | <li>STRONGLY RECOMMENDED to support near-ultrasound recording as described in |
| 4061 | <a href="#7_8_3_near_ultrasound">section 7.8.3</a></li> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 4062 | </ul> |
| 4063 | |
| 4064 | <h3 id="7_8_2_audio_output">7.8.2. Audio Output</h3> |
| 4065 | |
| 4066 | <div class="note"> |
| 4067 | <p>Android Watch devices MAY include an audio output.</p> |
| 4068 | </div> |
| 4069 | |
| 4070 | <p>Device implementations including a speaker or with an audio/multimedia output |
| 4071 | port for an audio output peripheral as a headset or an external speaker:</p> |
| 4072 | |
| 4073 | <ul> |
| 4074 | <li>MUST report the android.hardware.audio.output feature constant.</li> |
| 4075 | <li>MUST meet the audio playback requirements in <a href="#5_5_audio_playback">section 5.5</a>.</li> |
| 4076 | <li>MUST meet the audio latency requirements in <a href="#5_6_audio_latency">section 5.6</a>.</li> |
Glenn Kasten | 20cdbb7 | 2015-09-24 11:56:42 -0700 | [diff] [blame^] | 4077 | <li>STRONGLY RECOMMENDED to support near-ultrasound playback as described in |
| 4078 | <a href="#7_8_3_near_ultrasound">section 7.8.3</a></li> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 4079 | </ul> |
| 4080 | |
| 4081 | <p>Conversely, if a device implementation does not include a speaker or audio |
| 4082 | output port, it MUST NOT report the android.hardware.audio output feature, and |
| 4083 | MUST implement the Audio Output related APIs as no-ops at least. </p> |
| 4084 | |
| 4085 | <p>Android Watch device implementation MAY but SHOULD NOT have audio output, but |
| 4086 | other types of Android device implementations MUST have an audio output and |
| 4087 | declare android.hardware.audio.output.</p> |
| 4088 | |
| 4089 | <h4 id="7_8_2_1_analog_audio_ports">7.8.2.1. Analog Audio Ports</h4> |
| 4090 | |
| 4091 | |
| 4092 | <p>In order to be compatible with the headsets and other audio accessories using |
| 4093 | the 3.5mm audio plug across the Android ecosystem [<a href="http://source.android.com/accessories/headset-spec.html">Resources, 101</a>], if a device implementation includes one or more analog audio ports, at least |
| 4094 | one of the audio port(s) SHOULD be a 4 conductor 3.5mm audio jack. If a device |
| 4095 | implementation has a 4 conductor 3.5mm audio jack, it:</p> |
| 4096 | |
| 4097 | <ul> |
| 4098 | <li>MUST support audio playback to stereo headphones and stereo headsets with a |
| 4099 | microphone, and SHOULD support audio recording from stereo headsets with a |
| 4100 | microphone.</li> |
| 4101 | <li>MUST support TRRS audio plugs with the CTIA pin-out order, and SHOULD support |
| 4102 | audio plugs with the OMTP pin-out order.</li> |
| 4103 | <li>MUST support the detection of microphone on the plugged in audio accessory, if |
| 4104 | the device implementation supports a microphone, and broadcast the |
| 4105 | android.intent.action.HEADSET_PLUG with the extra value microphone set as 1.</li> |
| 4106 | <li>SHOULD support the detection and mapping to the keycodes for the following 3 |
| 4107 | ranges of equivalent impedance between the microphone and ground conductors on |
| 4108 | the audio plug: |
| 4109 | <ul> |
| 4110 | <li><strong>70 ohm or less</strong>: KEYCODE_HEADSETHOOK</li> |
Glenn Kasten | 54e6ac1 | 2015-08-12 09:07:12 -0700 | [diff] [blame] | 4111 | <li><strong>210-290 Ohm</strong>: KEYCODE_VOLUME_UP</li> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 4112 | <li><strong>360-680 Ohm</strong>: KEYCODE_VOLUME_DOWN</li> |
| 4113 | </ul></li> |
| 4114 | <li>SHOULD support the detection and mapping to the keycode for the following range |
| 4115 | of equivalent impedance between the microphone and ground conductors on the |
| 4116 | audio plug: |
| 4117 | <ul> |
| 4118 | <li><strong>110-180 Ohm: </strong>KEYCODE_VOICE_ASSIST</li> |
| 4119 | </ul></li> |
| 4120 | <li>MUST trigger ACTION_HEADSET_PLUG upon a plug insert, but only after all |
| 4121 | contacts on plug are touching their relevant segments on the jack.</li> |
| 4122 | <li>MUST be capable of driving at least 150mV +/- 10% of output voltage on a 32 Ohm |
| 4123 | speaker impedance.</li> |
| 4124 | <li>MUST have a microphone bias voltage between 1.8V ~ 2.9V.</li> |
| 4125 | </ul> |
| 4126 | |
Glenn Kasten | 20cdbb7 | 2015-09-24 11:56:42 -0700 | [diff] [blame^] | 4127 | <h3 id="7_8_3_near_ultrasound">7.8.3. Near-Ultrasound </h3> |
| 4128 | |
| 4129 | <p>Near-Ultrasound audio is the 18.5 kHz to 20 kHz band. |
| 4130 | Device implementations MUST correctly report the support |
| 4131 | of near-ultrasound audio capability via the |
| 4132 | <a href="http://developer.android.com/reference/android/media/AudioManager.html#getProperty(java.lang.String)">AudioManager.getProperty</a> |
| 4133 | API as follows: |
| 4134 | </p> |
| 4135 | |
| 4136 | <ul> |
| 4137 | <li>If |
| 4138 | <a href="http://developer.android.com/reference/android/media/AudioManager.html#PROPERTY_SUPPORT_MIC_NEAR_ULTRASOUND">PROPERTY_SUPPORT_MIC_NEAR_ULTRASOUND</a> |
| 4139 | is "true", then |
| 4140 | <ul> |
| 4141 | <li>The microphone's mean power response in the 18.5 kHz to 20 kHz band MUST be no more than |
| 4142 | 15 dB below the response at 2 kHz.</li> |
| 4143 | <li>The signal to noise ratio of the microphone MUST be no lower than 80 dB.</li> |
| 4144 | </ul> |
| 4145 | </li> |
| 4146 | <li>If |
| 4147 | <a href="http://developer.android.com/reference/android/media/AudioManager.html#PROPERTY_SUPPORT_SPEAKER_NEAR_ULTRASOUND">PROPERTY_SUPPORT_SPEAKER_NEAR_ULTRASOUND</a> |
| 4148 | is "true", then the speaker's mean response in 18.5 kHz - 20 kHz MUST be no lower than 40 dB |
| 4149 | below the response at 2 kHz. |
| 4150 | </li> |
| 4151 | </ul> |
| 4152 | |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 4153 | <h1 id="8_performance_compatibility">8. Performance Compatibility</h1> |
| 4154 | |
| 4155 | |
| 4156 | <p>Some minimum performance criterias are critical to the user experience and |
| 4157 | impacts the baseline assumptions developers would have when developing an app. |
| 4158 | Android Watch devices SHOULD and other type of device implementations MUST meet |
| 4159 | the following criteria:</p> |
| 4160 | |
| 4161 | <h2 id="8_1_user_experience_consistency">8.1. User Experience Consistency</h2> |
| 4162 | |
| 4163 | |
| 4164 | <p>Device implementations MUST provide a smooth user interface by ensuring a |
| 4165 | consistent frame rate and response times for applications and games. Device |
| 4166 | implementations MUST meet the following requirements: </p> |
| 4167 | |
| 4168 | <ul> |
| 4169 | <li><strong>Consistent frame latency</strong>. Inconsistent frame latency or a delay to render frames MUST NOT happen more |
| 4170 | often than 5 frames in a second, and SHOULD be below 1 frames in a second.</li> |
| 4171 | <li><strong>User interface latency</strong>. Device implementations MUST ensure low latency user experience by scrolling a |
| 4172 | list of 10K list entries as defined by the Android Compatibility Test Suite |
| 4173 | (CTS) in less than 36 secs.</li> |
| 4174 | <li><strong>Task switching</strong>. When multiple applications have been launched, re-launching an already-running |
| 4175 | application after it has been launched MUST take less than 1 second.</li> |
| 4176 | </ul> |
| 4177 | |
| 4178 | <h2 id="8_2_file_i_o_access_performance">8.2. File I/O Access Performance</h2> |
| 4179 | |
| 4180 | |
| 4181 | <p>Device implementations MUST ensure internal storage file access performance consistency for read |
| 4182 | and write operations. </p> |
| 4183 | |
| 4184 | <ul> |
| 4185 | <li><strong>Sequential write</strong>. Device implementations MUST ensure a sequential write performance of at least 5MB/s |
| 4186 | for a 256MB file using 10MB write buffer.</li> |
| 4187 | <li><strong>Random write</strong>. Device implementations MUST ensure a random write performance of at least 0.5MB/s for a |
| 4188 | 256MB file using 4KB write buffer.</li> |
| 4189 | <li><strong>Sequential read</strong>. Device implementations MUST ensure a sequential read performance of at least 15MB/s for |
| 4190 | a 256MB file using 10MB write buffer.</li> |
| 4191 | <li><strong>Random read</strong>. Device implementations MUST ensure a random read performance of at least 3.5MB/s for a |
| 4192 | 256MB file using 4KB write buffer.</li> |
| 4193 | </ul> |
| 4194 | |
| 4195 | <h1 id="9_security_model_compatibility">9. Security Model Compatibility</h1> |
| 4196 | |
| 4197 | |
| 4198 | <p>Device implementations MUST implement a security model consistent with the |
| 4199 | Android platform security model as defined in Security and Permissions |
| 4200 | reference document in the APIs [<a href="http://developer.android.com/guide/topics/security/permissions.html">Resources, 102</a>] in the Android developer documentation. Device implementations MUST support |
| 4201 | installation of self-signed applications without requiring any additional |
| 4202 | permissions/certificates from any third parties/authorities. Specifically, |
| 4203 | compatible devices MUST support the security mechanisms described in the follow |
| 4204 | subsections.</p> |
| 4205 | |
| 4206 | <h2 id="9_1_permissions">9.1. Permissions</h2> |
| 4207 | |
| 4208 | |
| 4209 | <p>Device implementations MUST support the Android permissions model as defined in |
| 4210 | the Android developer documentation [<a href="http://developer.android.com/guide/topics/security/permissions.html">Resources, 102</a>]. Specifically, implementations MUST enforce each permission defined as |
| 4211 | described in the SDK documentation; no permissions may be omitted, altered, or |
| 4212 | ignored. Implementations MAY add additional permissions, provided the new |
| 4213 | permission ID strings are not in the android.* namespace.</p> |
| 4214 | |
Svetoslav | 4bbf740 | 2015-09-11 14:45:48 -0700 | [diff] [blame] | 4215 | <p>Permissions with a protection level of dangerous are runtime permissions. Applications |
| 4216 | with targetSdkVersion > 22 request them at runtime. The system MUST show a dedicated UI for the |
| 4217 | user to decide whether to grant the requested runtime permissions and also provide a UI for the |
| 4218 | user to manage runtime permissions. On the system there MUST be one and only one |
| 4219 | implementation of both the UI for the user to accept runtime permissions and the UI for |
| 4220 | the user to manage runtime permissions.</p> |
| 4221 | |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 4222 | <h2 id="9_2_uid_and_process_isolation">9.2. UID and Process Isolation</h2> |
| 4223 | |
| 4224 | |
| 4225 | <p>Device implementations MUST support the Android application sandbox model, in |
| 4226 | which each application runs as a unique Unixstyle UID and in a separate |
| 4227 | process. Device implementations MUST support running multiple applications as |
| 4228 | the same Linux user ID, provided that the applications are properly signed and |
| 4229 | constructed, as defined in the Security and Permissions reference [<a href="http://developer.android.com/guide/topics/security/permissions.html">Resources, 102</a>].</p> |
| 4230 | |
| 4231 | <h2 id="9_3_filesystem_permissions">9.3. Filesystem Permissions</h2> |
| 4232 | |
| 4233 | |
| 4234 | <p>Device implementations MUST support the Android file access permissions model |
| 4235 | as defined in the Security and Permissions reference [<a href="http://developer.android.com/guide/topics/security/permissions.html">Resources, 102</a>].</p> |
| 4236 | |
| 4237 | <h2 id="9_4_alternate_execution_environments">9.4. Alternate Execution Environments</h2> |
| 4238 | |
| 4239 | |
| 4240 | <p>Device implementations MAY include runtime environments that execute |
| 4241 | applications using some other software or technology than the Dalvik Executable |
| 4242 | Format or native code. However, such alternate execution environments MUST NOT |
| 4243 | compromise the Android security model or the security of installed Android |
| 4244 | applications, as described in this section.</p> |
| 4245 | |
| 4246 | <p>Alternate runtimes MUST themselves be Android applications, and abide by the |
| 4247 | standard Android security model, as described elsewhere in <a href="#9_security_model_compatibility">section 9</a>.</p> |
| 4248 | |
| 4249 | <p>Alternate runtimes MUST NOT be granted access to resources protected by |
| 4250 | permissions not requested in the runtime’s AndroidManifest.xml file via the |
Unsuk Jung | 2e62f9a | 2015-07-16 23:01:44 -0700 | [diff] [blame] | 4251 | <uses-permission> mechanism.</p> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 4252 | |
| 4253 | <p>Alternate runtimes MUST NOT permit applications to make use of features |
| 4254 | protected by Android permissions restricted to system applications.</p> |
| 4255 | |
| 4256 | <p>Alternate runtimes MUST abide by the Android sandbox model. Specifically, |
| 4257 | alternate runtimes:</p> |
| 4258 | |
| 4259 | <ul> |
| 4260 | <li>SHOULD install apps via the PackageManager into separate Android sandboxes ( |
| 4261 | Linux user IDs, etc.).</li> |
| 4262 | <li>MAY provide a single Android sandbox shared by all applications using the |
| 4263 | alternate runtime.</li> |
| 4264 | <li>and installed applications using an alternate runtime, MUST NOT reuse the |
| 4265 | sandbox of any other app installed on the device, except through the standard |
| 4266 | Android mechanisms of shared user ID and signing certificate.</li> |
| 4267 | <li>MUST NOT launch with, grant, or be granted access to the sandboxes |
| 4268 | corresponding to other Android applications.</li> |
| 4269 | <li>MUST NOT be launched with, be granted, or grant to other applications any |
| 4270 | privileges of the superuser (root), or of any other user ID.</li> |
| 4271 | </ul> |
| 4272 | |
| 4273 | <p>The .apk files of alternate runtimes MAY be included in the system image of a |
| 4274 | device implementation, but MUST be signed with a key distinct from the key used |
| 4275 | to sign other applications included with the device implementation.</p> |
| 4276 | |
| 4277 | <p>When installing applications, alternate runtimes MUST obtain user consent for |
| 4278 | the Android permissions used by the application. If an application needs to |
| 4279 | make use of a device resource for which there is a corresponding Android |
| 4280 | permission (such as Camera, GPS, etc.), the alternate runtime MUST inform the |
| 4281 | user that the application will be able to access that resource. If the runtime |
| 4282 | environment does not record application capabilities in this manner, the |
| 4283 | runtime environment MUST list all permissions held by the runtime itself when |
| 4284 | installing any application using that runtime.</p> |
| 4285 | |
| 4286 | <h2 id="9_5_multi-user_support">9.5. Multi-User Support</h2> |
| 4287 | |
| 4288 | <div class="note"> |
| 4289 | <p>This feature is optional for all device types.</p> |
| 4290 | </div> |
| 4291 | |
| 4292 | |
| 4293 | <p>Android includes support for multiple users and provides support for full user |
| 4294 | isolation [<a href="http://developer.android.com/reference/android/os/UserManager.html">Resources, 103]</a>. Device implementations MAY enable multiple users, but when enabled MUST meet |
| 4295 | the following requirements related to multi-user support [<a href="http://source.android.com/devices/storage/">Resources, 104</a>]:</p> |
| 4296 | |
| 4297 | <ul> |
| 4298 | <li>Device implementations that do not declare the android.hardware.telephony |
| 4299 | feature flag MUST support restricted profiles, a feature that allows device |
| 4300 | owners to manage additional users and their capabilities on the device. With |
| 4301 | restricted profiles, device owners can quickly set up separate environments for |
| 4302 | additional users to work in, with the ability to manage finer-grained |
| 4303 | restrictions in the apps that are available in those environments.</li> |
| 4304 | <li>Conversely device implementations that declare the android.hardware.telephony |
| 4305 | feature flag MUST NOT support restricted profiles but MUST align with the AOSP |
| 4306 | implementation of controls to enable /disable other users from accessing the |
| 4307 | voice calls and SMS.</li> |
| 4308 | <li>Device implementations MUST, for each user, implement a security model |
| 4309 | consistent with the Android platform security model as defined in Security and |
| 4310 | Permissions reference document in the APIs [<a href="http://developer.android.com/guide/topics/security/permissions.html">Resources, 102</a>].</li> |
| 4311 | <li>Device implementations MAY support creating users and managed profiles via the |
| 4312 | android.app.admin.DevicePolicyManager APIs, and if supported, MUST declare the |
| 4313 | platform feature flag android.software.managed_users. |
| 4314 | <li>Device implementations that declare the feature flag |
| 4315 | android.software.managed_users MUST use the upstream AOSP icon badge to |
Glenn Kasten | 54e6ac1 | 2015-08-12 09:07:12 -0700 | [diff] [blame] | 4316 | represent the managed applications and other badge UI elements like Recents & |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 4317 | Notifications.</li> |
| 4318 | <li>Each user instance on an Android device MUST have separate and isolated |
| 4319 | external storage directories. Device implementations MAY store multiple users' |
| 4320 | data on the same volume or filesystem. However, the device implementation MUST |
| 4321 | ensure that applications owned by and running on behalf a given user cannot |
| 4322 | list, read, or write to data owned by any other user. Note that removable |
| 4323 | media, such as SD card slots, can allow one user to access another’s data by |
| 4324 | means of a host PC. For this reason, device implementations that use removable |
| 4325 | media for the external storage APIs MUST encrypt the contents of the SD card if |
| 4326 | multiuser is enabled using a key stored only on non-removable media accessible |
| 4327 | only to the system. As this will make the media unreadable by a host PC, device |
| 4328 | implementations will be required to switch to MTP or a similar system to |
| 4329 | provide host PCs with access to the current user’s data. Accordingly, device |
| 4330 | implementations MAY but SHOULD NOT enable multi-user if they use removable |
| 4331 | media [<a href="http://developer.android.com/reference/android/os/Environment.html">Resources, 105</a>] for primary external storage.</li> |
| 4332 | </ul> |
| 4333 | |
| 4334 | <h2 id="9_6_premium_sms_warning">9.6. Premium SMS Warning</h2> |
| 4335 | |
| 4336 | |
| 4337 | <p>Android includes support for warning users of any outgoing premium SMS message |
| 4338 | [<a href="http://en.wikipedia.org/wiki/Short_code">Resources, 106</a>] . Premium SMS messages are text messages sent to a service registered with a |
| 4339 | carrier that may incur a charge to the user. Device implementations that |
| 4340 | declare support for android.hardware.telephony MUST warn users before sending a |
| 4341 | SMS message to numbers identified by regular expressions defined in |
| 4342 | /data/misc/sms/codes.xml file in the device. The upstream Android Open Source |
| 4343 | Project provides an implementation that satisfies this requirement.</p> |
| 4344 | |
| 4345 | <h2 id="9_7_kernel_security_features">9.7. Kernel Security Features</h2> |
| 4346 | |
| 4347 | |
| 4348 | <p>The Android Sandbox includes features that can use the Security-Enhanced Linux |
| 4349 | (SELinux) mandatory access control (MAC) system and other security features in |
| 4350 | the Linux kernel. SELinux or any other security features, if implemented below |
| 4351 | the Android framework:</p> |
| 4352 | |
| 4353 | <ul> |
| 4354 | <li>MUST maintain compatibility with existing applications.</li> |
| 4355 | <li>MUST NOT have a visible user interface when a security violation is detected |
| 4356 | and successfully blocked, but MAY have a visible user interface when an |
| 4357 | unblocked security violation occurs resulting in a successful exploit.</li> |
| 4358 | <li>SHOULD NOT be user or developer configurable.</li> |
| 4359 | </ul> |
| 4360 | |
| 4361 | <p>If any API for configuration of policy is exposed to an application that can |
| 4362 | affect another application (such as a Device Administration API), the API MUST |
| 4363 | NOT allow configurations that break compatibility.</p> |
| 4364 | |
| 4365 | <p>Devices MUST implement SELinux or an equivalent mandatory access control system |
| 4366 | if using a kernel other than Linux and meet the following requirements, which |
| 4367 | are satisfied by the reference implementation in the upstream Android Open |
| 4368 | Source Project.</p> |
| 4369 | |
| 4370 | <p>Device implementations:</p> |
| 4371 | |
| 4372 | <ul> |
| 4373 | <li>MUST support a SELinux policy that allows the SELinux mode to be set on a |
| 4374 | per-domain basis, and MUST configure all domains in enforcing mode. No |
| 4375 | permissive mode domains are allowed, including domains specific to a |
| 4376 | device/vendor.</li> |
| 4377 | <li>SHOULD load policy from /sepolicy file on the device.</li> |
| 4378 | <li>MUST NOT modify, omit, or replace the neverallow rules present within the |
| 4379 | sepolicy file provided in the upstream Android Open Source Project (AOSP) and |
| 4380 | the policy MUST compile with all neverallow present, for both AOSP SELinux |
| 4381 | domains as well as device/vendor specific domains.</li> |
| 4382 | <li>MUST support dynamic updates of the SELinux policy file without requiring a |
| 4383 | system image update.</li> |
| 4384 | </ul> |
| 4385 | |
| 4386 | <p>Device implementations SHOULD retain the default SELinux policy provided in the |
| 4387 | upstream Android Open Source Project, until they have first audited their |
| 4388 | additions to the SELinux policy. Device implementations MUST be compatible with |
| 4389 | the upstream Android Open Source Project.</p> |
| 4390 | |
| 4391 | <h2 id="9_8_privacy">9.8. Privacy</h2> |
| 4392 | |
| 4393 | <p>If the device implements functionality in the system that captures the contents |
| 4394 | displayed on the screen and/or records the audio stream played on the device, |
| 4395 | it MUST continuously notify the user whenever this functionality is enabled and |
| 4396 | actively capturing/recording.</p> |
| 4397 | |
| 4398 | <p>If a device implementation has a mechanism that routes network data traffic |
| 4399 | through a proxy server or VPN gateway by default (for example, preloading a VPN |
| 4400 | service with android.permission.CONTROL_VPN granted), the device implementation |
| 4401 | MUST ask for the user's consent before enabling that mechanism.</p> |
| 4402 | |
| 4403 | <h2 id="9_9_full-disk_encryption">9.9. Full-Disk Encryption</h2> |
| 4404 | |
| 4405 | <div class="note"> |
| 4406 | <p>Optional for Android device implementations without a lock screen.</p> |
| 4407 | </div> |
| 4408 | |
| 4409 | |
| 4410 | <p>If the device implementation supports a lock screen with PIN (numeric) or |
| 4411 | PASSWORD (alphanumeric), the device MUST support full-disk encryption of the |
| 4412 | application private data (/data partition), as well |
| 4413 | as the SD card partition if it is a permanent, non-removable part of the device |
| 4414 | [<a href="http://source.android.com/devices/tech/security/encryption/index.html">Resources, 107</a>]. For devices supporting full-disk encryption, the full-disk encryption SHOULD |
| 4415 | be enabled all the time after the user has completed the out-of-box experience. |
| 4416 | While this requirement is stated as SHOULD for this version of the Android |
| 4417 | platform, it is <strong>very strongly RECOMMENDED</strong> as we expect this to change to MUST in the future versions of Android. |
| 4418 | Encryption MUST use AES with a key of 128-bits (or greater) and a mode designed |
| 4419 | for storage (for example, AES-XTS, AES-CBC-ESSIV). The encryption key MUST NOT |
| 4420 | be written to storage at any time without being encrypted. Other than when in |
| 4421 | active use, the encryption key SHOULD be AES encrypted with the lockscreen |
| 4422 | passcode stretched using a slow stretching algorithm (e.g. PBKDF2 or scrypt). |
| 4423 | If the user has not specified a lockscreen passcode or has disabled use of the |
| 4424 | passcode for encryption, the system SHOULD use a default passcode to wrap the |
| 4425 | encryption key. If the device provides a hardware-backed keystore, the password |
| 4426 | stretching algorithm MUST be cryptographically bound to that keystore. The |
| 4427 | encryption key MUST NOT be sent off the device (even when wrapped with the user |
| 4428 | passcode and/or hardware bound key). The upstream Android Open Source project |
Clay Murphy | f4fa6bc | 2015-08-28 17:20:31 -0700 | [diff] [blame] | 4429 | provides a preferred implementation of this feature based on the Linux kernel |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 4430 | feature dm-crypt.</p> |
| 4431 | |
| 4432 | <h2 id="9_10_verified_boot">9.10. Verified Boot</h2> |
| 4433 | |
| 4434 | <p> |
| 4435 | Verified boot is a feature that guarantees the integrity of the device software. |
| 4436 | If a device implementation supports the feature, it MUST: |
Glenn Kasten | 54e6ac1 | 2015-08-12 09:07:12 -0700 | [diff] [blame] | 4437 | </p> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 4438 | <ul> |
| 4439 | <li>Declare the platform feature flag android.software.verified_boot</li> |
| 4440 | <li>Perform verification on every boot sequence</li> |
Clay Murphy | f4fa6bc | 2015-08-28 17:20:31 -0700 | [diff] [blame] | 4441 | <li>Start verification from an immutable hardware key that is the root of trust, |
| 4442 | and go all the way up to the system partition</li> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 4443 | <li>Implement each stage of verification to check the integrity and authenticity |
| 4444 | of all the bytes in the next stage before executing the code in the next stage</li> |
| 4445 | <li>Use verification algorithms as strong as current recommendations |
| 4446 | from NIST for hashing algorithms (SHA-256) and public key sizes (RSA-2048)</li> |
| 4447 | </ul> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 4448 | |
Clay Murphy | f4fa6bc | 2015-08-28 17:20:31 -0700 | [diff] [blame] | 4449 | <p>The upstream Android Open Source Project provides a preferred implementation of this |
| 4450 | feature based on the Linux kernel feature dm-verity.</p> |
| 4451 | |
| 4452 | <p>Starting from Android 6.0, device implementations with Advanced Encryption Standard (AES) |
| 4453 | crypto perfomance above 50MiB/seconds MUST support verified boot for device integrity. |
| 4454 | If a device implementation is already launched without supporting verified boot on an earlier |
| 4455 | version of Android, such a device can not add support for this feature with a system software |
| 4456 | update and thus are exempted from the requirement.</p> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 4457 | |
| 4458 | <h1 id="10_software_compatibility_testing">10. Software Compatibility Testing</h1> |
| 4459 | |
| 4460 | |
| 4461 | <p>Device implementations MUST pass all tests described in this section.</p> |
| 4462 | |
| 4463 | <p>However, note that no software test package is fully comprehensive. For this |
Bert McMeen | 816a242 | 2015-09-29 16:33:19 -0700 | [diff] [blame] | 4464 | reason, device implementers are <strong>STRONGLY RECOMMENDED</strong> to make the minimum number of changes as possible to the reference and |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 4465 | preferred implementation of Android available from the Android Open Source |
| 4466 | Project. This will minimize the risk of introducing bugs that create |
| 4467 | incompatibilities requiring rework and potential device updates.</p> |
| 4468 | |
| 4469 | <h2 id="10_1_compatibility_test_suite">10.1. Compatibility Test Suite</h2> |
| 4470 | |
| 4471 | |
| 4472 | <p>Device implementations MUST pass the Android Compatibility Test Suite (CTS) [<a href="http://source.android.com/compatibility/index.html">Resources, 108</a>] available from the Android Open Source Project, using the final shipping |
| 4473 | software on the device. Additionally, device implementers SHOULD use the |
| 4474 | reference implementation in the Android Open Source tree as much as possible, |
| 4475 | and MUST ensure compatibility in cases of ambiguity in CTS and for any |
| 4476 | reimplementations of parts of the reference source code.</p> |
| 4477 | |
| 4478 | <p>The CTS is designed to be run on an actual device. Like any software, the CTS |
| 4479 | may itself contain bugs. The CTS will be versioned independently of this |
| 4480 | Compatibility Definition, and multiple revisions of the CTS may be released for |
| 4481 | Android ANDROID_VERSION. Device implementations MUST pass the latest CTS version available |
| 4482 | at the time the device software is completed.</p> |
| 4483 | |
| 4484 | <h2 id="10_2_cts_verifier">10.2. CTS Verifier</h2> |
| 4485 | |
| 4486 | |
| 4487 | <p>Device implementations MUST correctly execute all applicable cases in the CTS |
| 4488 | Verifier. The CTS Verifier is included with the Compatibility Test Suite, and |
| 4489 | is intended to be run by a human operator to test functionality that cannot be |
| 4490 | tested by an automated system, such as correct functioning of a camera and |
| 4491 | sensors.</p> |
| 4492 | |
| 4493 | <p>The CTS Verifier has tests for many kinds of hardware, including some hardware |
| 4494 | that is optional. Device implementations MUST pass all tests for hardware that |
| 4495 | they possess; for instance, if a device possesses an accelerometer, it MUST |
| 4496 | correctly execute the Accelerometer test case in the CTS Verifier. Test cases |
| 4497 | for features noted as optional by this Compatibility Definition Document MAY be |
| 4498 | skipped or omitted.</p> |
| 4499 | |
| 4500 | <p>Every device and every build MUST correctly run the CTS Verifier, as noted |
| 4501 | above. However, since many builds are very similar, device implementers are not |
| 4502 | expected to explicitly run the CTS Verifier on builds that differ only in |
| 4503 | trivial ways. Specifically, device implementations that differ from an |
| 4504 | implementation that has passed the CTS Verifier only by the set of included |
| 4505 | locales, branding, etc. MAY omit the CTS Verifier test.</p> |
| 4506 | |
| 4507 | <h1 id="11_updatable_software">11. Updatable Software</h1> |
| 4508 | |
| 4509 | |
| 4510 | <p>Device implementations MUST include a mechanism to replace the entirety of the |
| 4511 | system software. The mechanism need not perform “live” upgrades—that is, a |
| 4512 | device restart MAY be required.</p> |
| 4513 | |
| 4514 | <p>Any method can be used, provided that it can replace the entirety of the |
| 4515 | software preinstalled on the device. For instance, any of the following |
| 4516 | approaches will satisfy this requirement:</p> |
| 4517 | |
| 4518 | <ul> |
| 4519 | <li>“Over-the-air (OTA)” downloads with offline update via reboot</li> |
| 4520 | <li>“Tethered” updates over USB from a host PC</li> |
| 4521 | <li>“Offline” updates via a reboot and update from a file on removable storage</li> |
| 4522 | </ul> |
| 4523 | |
| 4524 | <p>However, if the device implementation includes support for an unmetered data |
| 4525 | connection such as 802.11 or Bluetooth PAN (Personal Area Network) profile:</p> |
| 4526 | |
| 4527 | <ul> |
| 4528 | <li>Android Automotive implementations SHOULD support OTA downloads with offline |
| 4529 | update via reboot.</li> |
| 4530 | <li>All other device implementations MUST support OTA downloads with offline |
| 4531 | update via reboot.</li> |
| 4532 | </ul> |
| 4533 | |
| 4534 | <p>The update mechanism used MUST support updates without wiping user data. That |
| 4535 | is, the update mechanism MUST preserve application private data and application |
| 4536 | shared data. Note that the upstream Android software includes an update |
| 4537 | mechanism that satisfies this requirement.</p> |
| 4538 | |
| 4539 | <p>For device implementations that are launching with Android ANDROID_VERSION and later, the |
| 4540 | update mechanism SHOULD support verifying that the system image is binary |
| 4541 | identical to expected result following an OTA. The block-based OTA |
| 4542 | implementation in the upstream Android Open Source Project, added since Android |
| 4543 | 5.1, satisfies this requirement.</p> |
| 4544 | |
| 4545 | <p>If an error is found in a device implementation after it has been released but |
| 4546 | within its reasonable product lifetime that is determined in consultation with |
| 4547 | the Android Compatibility Team to affect the compatibility of third-party |
| 4548 | applications, the device implementer MUST correct the error via a software |
| 4549 | update available that can be applied per the mechanism just described.</p> |
| 4550 | |
| 4551 | <h1 id="12_document_changelog">12. Document Changelog</h1> |
| 4552 | |
| 4553 | |
| 4554 | <p>The following table contains a summary of the changes to the Compatibility |
| 4555 | Definition in this release. </p> |
| 4556 | <table> |
| 4557 | <tr> |
| 4558 | <th>Section</th> |
| 4559 | <th>Summary of change</th> |
| 4560 | </tr> |
| 4561 | <tr> |
| 4562 | <td>2. Device Types</td> |
| 4563 | <td>Added definition for Android automotive implementation.</td> |
| 4564 | </tr> |
| 4565 | <tr> |
| 4566 | <td>2.1 Device Configurations</td> |
| 4567 | <td>Added column for Android automotive implementation.</td> |
| 4568 | </tr> |
| 4569 | <tr> |
| 4570 | <td>3.3.2. 32-bit ARM Native Code Compatibility</td> |
| 4571 | <td>New section added.</td> |
| 4572 | </tr> |
| 4573 | <tr> |
| 4574 | <td>3.4.1. WebView Compatibility</td> |
| 4575 | <td>Updated webview user agent string requirement to accomodate upstream |
| 4576 | implementation change.</td> |
| 4577 | </tr> |
| 4578 | <tr> |
| 4579 | <td>3.4.2. Browser compatibility</td> |
| 4580 | <td>Added Android automotive implementations as another case that MAY omit a |
| 4581 | browser application.</td> |
| 4582 | </tr> |
| 4583 | <tr> |
| 4584 | <td>3.7. Runtime Compatibility</td> |
| 4585 | <td>Updated required runtime heap size for smaller screens and added requirement |
| 4586 | for the new dpi bucket (280dpi).</td> |
| 4587 | </tr> |
| 4588 | <tr> |
| 4589 | <td>3.8.3. Notifications</td> |
| 4590 | <td>Clarified notification requirement for Android Watch, Television and |
| 4591 | Automotive implementations.</td> |
| 4592 | </tr> |
| 4593 | <tr> |
| 4594 | <td>3.8.10. Lock Screen Media Control<</td> |
| 4595 | <td>Clarified requirement for Android Watch and Automotive implementations.</td> |
| 4596 | </tr> |
| 4597 | <tr> |
| 4598 | <td>3.8.13. Unicode and font</td> |
| 4599 | <td>Relaxed Emoji character input method requirement.</td> |
| 4600 | </tr> |
| 4601 | <tr> |
| 4602 | <td>3.9. Device Administration</td> |
| 4603 | <td>Clarified condition when the full range of device administration policies |
| 4604 | has to be supported.</td> |
| 4605 | </tr> |
| 4606 | <tr> |
| 4607 | <td>3.10. Accessibility</td> |
| 4608 | <td>Added Android automotive requirements.</td> |
| 4609 | </tr> |
| 4610 | <tr> |
| 4611 | <td>3.11. Text-To-Speech</td> |
| 4612 | <td>Added Android automotive requirements.</td> |
| 4613 | </tr> |
| 4614 | <tr> |
| 4615 | <td>5.1. Media Codecs</td> |
| 4616 | <td>Mandated decoding support for codecs reported by CamcorderProfile.</td> |
| 4617 | </tr> |
| 4618 | <tr> |
| 4619 | <td>5.1.3 Video Codecs</td> |
| 4620 | <td>Added Android automotive requirements.</td> |
| 4621 | </tr> |
| 4622 | <tr> |
| 4623 | <td>7.1.1.3. Screen Density</td> |
| 4624 | <td>Added a new screen dpi (280dpi).</td> |
| 4625 | </tr> |
| 4626 | <tr> |
| 4627 | <td>7.1.5. Legacy Application Compatibility Mode</td> |
| 4628 | <td>Added Android automotive requirements.</td> |
| 4629 | </tr> |
| 4630 | <tr> |
| 4631 | <td>7.2 Input Devices</td> |
| 4632 | <td>Added general introduction statement.</td> |
| 4633 | </tr> |
| 4634 | <tr> |
| 4635 | <td>7.2.1. Keyboard</td> |
| 4636 | <td>Added Android Automotive requirements.</td> |
| 4637 | </tr> |
| 4638 | <tr> |
| 4639 | <td>7.2.3. Navigation Keys</td> |
| 4640 | <td>Added Android Automotive requirements.</td> |
| 4641 | </tr> |
| 4642 | <tr> |
| 4643 | <td>7.3.1. Accelerometer</td> |
| 4644 | <td>Relaxed requirement for reporting frequency on Android Watch.</td> |
| 4645 | </tr> |
| 4646 | <tr> |
| 4647 | <td>7.3.4. Gyroscope</td> |
| 4648 | <td>Relaxed requirement for reporting frequency on Android Watch.</td> |
| 4649 | </tr> |
| 4650 | <tr> |
| 4651 | <td>7.4.3 Bluetooth</td> |
| 4652 | <td>Added Android Automotive requirements.</td> |
| 4653 | </tr> |
| 4654 | <tr> |
| 4655 | <td>7.4.4. Near-Field Communications</td> |
| 4656 | <td>Clarified condition for when Host Card Emulation is a requirement.</td> |
| 4657 | </tr> |
| 4658 | <tr> |
| 4659 | <td>7.6.1. Minimum Memory and Storage</td> |
| 4660 | <td>Updated minimum memory requirements for lower resulution screen devices |
| 4661 | and added hard-limit requirement isLowRamDevice().</td> |
| 4662 | </tr> |
| 4663 | <tr> |
| 4664 | <td>7.6.2. Application Shared Storage</td> |
| 4665 | <td>Updated requirements when support for host machine access is mandatory.</td> |
| 4666 | </tr> |
| 4667 | <tr> |
| 4668 | <td>7.8.1. Microphone</td> |
| 4669 | <td>Added Android Automotive requirements.</td> |
| 4670 | </tr> |
| 4671 | <tr> |
| 4672 | <td>8.2. File I/O Access Performance</td> |
| 4673 | <td>Clarified requirements.</td> |
| 4674 | </tr> |
| 4675 | <tr> |
| 4676 | <td>9.8. Privacy</td> |
| 4677 | <td>Added privacy requirement for preloaded VPNs.</td> |
| 4678 | </tr> |
| 4679 | <tr> |
| 4680 | <td>9.9. Full-Disk Encryption</td> |
| 4681 | <td>Clarified condition when Full-Disk encryption support is mandatory.</td> |
| 4682 | </tr> |
| 4683 | <tr> |
| 4684 | <td>9.10. Verified Boot</td> |
| 4685 | <td>Clarified definition of verified boot.</td> |
| 4686 | </tr> |
| 4687 | <tr> |
| 4688 | <td>11. Updatable Software</td> |
| 4689 | <td>Clarified the OTA download requirement is allowed but not mandatory for |
| 4690 | Android Automotive implementations.</td> |
| 4691 | </tr> |
| 4692 | </table> |
| 4693 | |
| 4694 | |
| 4695 | <h1 id="13_contact_us">13. Contact Us</h1> |
| 4696 | |
| 4697 | |
| 4698 | <p>You can join the android-compatibility forum <a href="https://groups.google.com/forum/#!forum/android-compatibility">[Resources, 109</a>] and ask for clarifications or bring up any issues that you think the document |
| 4699 | does not cover.</p> |
| 4700 | |
| 4701 | <h1 id="14_resources">14. Resources</h1> |
| 4702 | |
| 4703 | |
| 4704 | <p>1. IETF RFC2119 Requirement Levels: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a></p> |
| 4705 | |
| 4706 | <p>2. Android Open Source Project: <a href="http://source.android.com/">http://source.android.com/</a></p> |
| 4707 | |
| 4708 | <p>3. Android Television features: <a href="http://developer.android.com/reference/android/content/pm/PackageManager.html#FEATURE_LEANBACK">http://developer.android.com/reference/android/content/pm/PackageManager.html#FEATURE_LEANBACK</a> </p> |
| 4709 | |
| 4710 | <p>4. Android Watch feature: <a href="http://developer.android.com/reference/android/content/res/Configuration.html#UI_MODE_TYPE_WATCH">http://developer.android.com/reference/android/content/res/Configuration.html#UI_MODE_TYPE_WATCH</a></p> |
| 4711 | |
| 4712 | <p>5. API definitions and documentation: <a href="http://developer.android.com/reference/packages.html">http://developer.android.com/reference/packages.html</a></p> |
| 4713 | |
| 4714 | <p>6. Android Permissions reference: <a href="http://developer.android.com/reference/android/Manifest.permission.html">http://developer.android.com/reference/android/Manifest.permission.html</a></p> |
| 4715 | |
| 4716 | <p>7. android.os.Build reference: <a href="http://developer.android.com/reference/android/os/Build.html">http://developer.android.com/reference/android/os/Build.html</a></p> |
| 4717 | |
| 4718 | <p>8. Android ANDROID_VERSION allowed version strings: <a href="http://source.android.com/compatibility/ANDROID_VERSION/versions.html">http://source.android.com/compatibility/ANDROID_VERSION/versions.html</a></p> |
| 4719 | |
| 4720 | <p>9. Telephony Provider: <a href="http://developer.android.com/reference/android/provider/Telephony.html">http://developer.android.com/reference/android/provider/Telephony.html</a></p> |
| 4721 | |
| 4722 | <p>10. Host-based Card Emulation: <a href="http://developer.android.com/guide/topics/connectivity/nfc/hce.html">http://developer.android.com/guide/topics/connectivity/nfc/hce.html</a></p> |
| 4723 | |
| 4724 | <p>11. Android Extension Pack: <a href="http://developer.android.com/guide/topics/graphics/opengl.html#aep">http://developer.android.com/guide/topics/graphics/opengl.html#aep</a> </p> |
| 4725 | |
| 4726 | <p>12. android.webkit.WebView class: <a href="http://developer.android.com/reference/android/webkit/WebView.html">http://developer.android.com/reference/android/webkit/WebView.html</a></p> |
| 4727 | |
| 4728 | <p>13. WebView compatibility: <a href="http://www.chromium.org/">http://www.chromium.org/</a></p> |
| 4729 | |
| 4730 | <p>14. HTML5: <a href="http://html.spec.whatwg.org/multipage/">http://html.spec.whatwg.org/multipage/</a></p> |
| 4731 | |
| 4732 | <p>15. HTML5 offline capabilities:<a href="http://dev.w3.org/html5/spec/Overview.html#offline"> http://dev.w3.org/html5/spec/Overview.html#offline</a></p> |
| 4733 | |
| 4734 | <p>16. HTML5 video tag: <a href="http://dev.w3.org/html5/spec/Overview.html#video">http://dev.w3.org/html5/spec/Overview.html#video</a></p> |
| 4735 | |
| 4736 | <p>17. HTML5/W3C geolocation API: <a href="http://www.w3.org/TR/geolocation-API/">http://www.w3.org/TR/geolocation-API/</a></p> |
| 4737 | |
| 4738 | <p>18. HTML5/W3C webstorage API: <a href="http://www.w3.org/TR/webstorage/">http://www.w3.org/TR/webstorage/</a></p> |
| 4739 | |
| 4740 | <p>19. HTML5/W3C IndexedDB API: <a href="http://www.w3.org/TR/IndexedDB/">http://www.w3.org/TR/IndexedDB/</a></p> |
| 4741 | |
| 4742 | <p>20. Dalvik Executable Format and bytecode specification: available in the |
| 4743 | Android source code, at dalvik/docs</p> |
| 4744 | |
| 4745 | <p>21. AppWidgets: <a href="http://developer.android.com/guide/practices/ui_guidelines/widget_design.html">http://developer.android.com/guide/practices/ui_guidelines/widget_design.html</a></p> |
| 4746 | |
| 4747 | <p>22. Notifications: <a href="http://developer.android.com/guide/topics/ui/notifiers/notifications.html">http://developer.android.com/guide/topics/ui/notifiers/notifications.html</a></p> |
| 4748 | |
| 4749 | <p>23. Application Resources: <a href="https://developer.android.com/guide/topics/resources/available-resources.html">https://developer.android.com/guide/topics/resources/available-resources.html</a></p> |
| 4750 | |
| 4751 | <p>24. Status Bar icon style guide: <a href="http://developer.android.com/design/style/iconography.html">http://developer.android.com/design/style/iconography.html</a></p> |
| 4752 | |
| 4753 | <p>25. Notifications Resources: <a href="https://developer.android.com/design/patterns/notifications.html">https://developer.android.com/design/patterns/notifications.html</a> </p> |
| 4754 | |
| 4755 | <p>26. Search Manager: <a href="http://developer.android.com/reference/android/app/SearchManager.html">http://developer.android.com/reference/android/app/SearchManager.html</a> </p> |
| 4756 | |
| 4757 | <p>27. Toasts: <a href="http://developer.android.com/reference/android/widget/Toast.html">http://developer.android.com/reference/android/widget/Toast.html</a></p> |
| 4758 | |
| 4759 | <p>28. Themes: <a href="http://developer.android.com/guide/topics/ui/themes.html">http://developer.android.com/guide/topics/ui/themes.html</a></p> |
| 4760 | |
| 4761 | <p>29. R.style class: <a href="http://developer.android.com/reference/android/R.style.html">http://developer.android.com/reference/android/R.style.html</a></p> |
| 4762 | |
| 4763 | <p>30. Material design: <a href="http://developer.android.com/reference/android/R.style.html#Theme_Material">http://developer.android.com/reference/android/R.style.html#Theme_Material</a> </p> |
| 4764 | |
| 4765 | <p>31. Live Wallpapers: <a href="http://developer.android.com/reference/android/service/wallpaper/WallpaperService.html">http://developer.android.com/reference/android/service/wallpaper/WallpaperService.html</a></p> |
| 4766 | |
| 4767 | <p>32. Overview screen resources: <a href="http://developer.android.com/guide/components/recents.html">http://developer.android.com/guide/components/recents.html</a> </p> |
| 4768 | |
| 4769 | <p>33. Screen pinning: <a href="https://developer.android.com/about/versions/android-5.0.html#ScreenPinning">https://developer.android.com/about/versions/android-5.0.html#ScreenPinning</a> </p> |
| 4770 | |
| 4771 | <p>34. Input methods: <a href="http://developer.android.com/guide/topics/text/creating-input-method.html">http://developer.android.com/guide/topics/text/creating-input-method.html</a> </p> |
| 4772 | |
| 4773 | <p>35. Media Notification: <a href="https://developer.android.com/reference/android/app/Notification.MediaStyle.html">https://developer.android.com/reference/android/app/Notification.MediaStyle.html</a></p> |
| 4774 | |
| 4775 | <p>36. Dreams: <a href="http://developer.android.com/reference/android/service/dreams/DreamService.html">http://developer.android.com/reference/android/service/dreams/DreamService.html</a></p> |
| 4776 | |
| 4777 | <p>37. Settings.Secure LOCATION_MODE:</p> |
| 4778 | |
| 4779 | <p><a href="http://developer.android.com/reference/android/provider/Settings.Secure.html#LOCATION_MODE">http://developer.android.com/reference/android/provider/Settings.Secure.html#LOCATION_MODE</a></p> |
| 4780 | |
| 4781 | <p>38. Unicode 6.1.0: <a href="http://www.unicode.org/versions/Unicode6.1.0/">http://www.unicode.org/versions/Unicode6.1.0/</a></p> |
| 4782 | |
| 4783 | <p>39. Android Device Administration: <a href="http://developer.android.com/guide/topics/admin/device-admin.html">http://developer.android.com/guide/topics/admin/device-admin.html</a></p> |
| 4784 | |
| 4785 | <p>40. DevicePolicyManager reference: <a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html">http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html</a></p> |
| 4786 | |
| 4787 | <p>41. Android Device Owner App:</p> |
| 4788 | |
| 4789 | <p><a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#isDeviceOwnerApp(java.lang.String)">http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#isDeviceOwnerApp(java.lang.String)</a></p> |
Andy Dyer-smith | 3d24bbe | 2015-09-11 15:35:23 +0100 | [diff] [blame] | 4790 | <p>XX. Android Device Owner Provisioning Flow:</p> |
| 4791 | |
| 4792 | <p><a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#ACTION_PROVISION_MANAGED_DEVICE">http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#ACTION_PROVISION_MANAGED_DEVICE</a></p> |
| 4793 | <p>XX. Device Owner Provisioning via NFC:</p> |
| 4794 | |
| 4795 | <p><a href="https://source.android.com/devices/tech/admin/provision.html#device_owner_provisioning_via_nfc">https://source.android.com/devices/tech/admin/provision.html#device_owner_provisioning_via_nfc</a></p> |
| 4796 | <p>XX. Android Managed Profile Provisioning flow:</p> |
| 4797 | |
| 4798 | <p><a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#ACTION_PROVISION_MANAGED_PROFILE">http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#ACTION_PROVISION_MANAGED_PROFILE</a></p> |
| 4799 | |
| 4800 | <p>XX. Android Profile Owner App:</p> |
| 4801 | |
| 4802 | <p><a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#isProfileOwnerApp(java.lang.String)">http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#isProfileOwnerApp(java.lang.String)</a></p> |
Unsuk Jung | 5bc8114 | 2015-07-16 22:27:20 -0700 | [diff] [blame] | 4803 | |
| 4804 | <p>42. Android Accessibility Service APIs: <a href="http://developer.android.com/reference/android/accessibilityservice/AccessibilityService.html">http://developer.android.com/reference/android/accessibilityservice/AccessibilityService.html</a></p> |
| 4805 | |
| 4806 | <p>43. Android Accessibility APIs: <a href="http://developer.android.com/reference/android/view/accessibility/package-summary.html">http://developer.android.com/reference/android/view/accessibility/package-summary.html</a></p> |
| 4807 | |
| 4808 | <p>44. Eyes Free project: <a href="http://code.google.com/p/eyes-free/">http://code.google.com/p/eyes-free</a></p> |
| 4809 | |
| 4810 | <p>45. Text-To-Speech APIs: <a href="http://developer.android.com/reference/android/speech/tts/package-summary.html">http://developer.android.com/reference/android/speech/tts/package-summary.html</a></p> |
| 4811 | |
| 4812 | <p>46. Television Input Framework: <a href="https://source.android.com/devices/tv/index.html">https://source.android.com/devices/tv/index.html</a></p> |
| 4813 | |
| 4814 | <p>47. Reference tool documentation (for adb, aapt, ddms, systrace): <a href="http://developer.android.com/tools/help/index.html">http://developer.android.com/tools/help/index.html</a></p> |
| 4815 | |
| 4816 | <p>48. Android apk file description: <a href="http://developer.android.com/guide/components/fundamentals.html">http://developer.android.com/guide/components/fundamentals.html </a></p> |
| 4817 | |
| 4818 | <p>49. Manifest files: <a href="http://developer.android.com/guide/topics/manifest/manifest-intro.html">http://developer.android.com/guide/topics/manifest/manifest-intro.html</a></p> |
| 4819 | |
| 4820 | <p>50. Android Media Formats: <a href="http://developer.android.com/guide/appendix/media-formats.html">http://developer.android.com/guide/appendix/media-formats.html</a></p> |
| 4821 | |
| 4822 | <p>51. RTC Hardware Coding Requirements: <a href="http://www.webmproject.org/hardware/rtc-coding-requirements/">http://www.webmproject.org/hardware/rtc-coding-requirements/</a></p> |
| 4823 | |
| 4824 | <p>52. AudioEffect API: <a href="http://developer.android.com/reference/android/media/audiofx/AudioEffect.html">http://developer.android.com/reference/android/media/audiofx/AudioEffect.html</a></p> |
| 4825 | |
| 4826 | <p>53. Android android.content.pm.PackageManager class and Hardware Features List:</p> |
| 4827 | |
| 4828 | <p><a href="http://developer.android.com/reference/android/content/pm/PackageManager.html">http://developer.android.com/reference/android/content/pm/PackageManager.html</a></p> |
| 4829 | |
| 4830 | <p>54. HTTP Live Streaming Draft Protocol: <a href="http://tools.ietf.org/html/draft-pantos-http-live-streaming-03">http://tools.ietf.org/html/draft-pantos-http-live-streaming-03</a></p> |
| 4831 | |
| 4832 | <p>55. ADB: <a href="http://developer.android.com/tools/help/adb.html">http://developer.android.com/tools/help/adb.html</a> </p> |
| 4833 | |
| 4834 | <p>56. Dumpsys: <a href="https://source.android.com/devices/input/diagnostics.html">https://source.android.com/devices/input/diagnostics.html</a> </p> |
| 4835 | |
| 4836 | <p>57. DDMS: <a href="http://developer.android.com/tools/debugging/ddms.html">http://developer.android.com/tools/debugging/ddms.html</a> </p> |
| 4837 | |
| 4838 | <p>58. Monkey testing tool: <a href="http://developer.android.com/tools/help/monkey.html">http://developer.android.com/tools/help/monkey.html</a> </p> |
| 4839 | |
| 4840 | <p>59. SysyTrace tool: <a href="http://developer.android.com/tools/help/systrace.html">http://developer.android.com/tools/help/systrace.html</a></p> |
| 4841 | |
| 4842 | <p>60. Android Application Development-Related Settings:</p> |
| 4843 | |
| 4844 | <p><a href="http://developer.android.com/reference/android/provider/Settings.html#ACTION_APPLICATION_DEVELOPMENT_SETTINGS">http://developer.android.com/reference/android/provider/Settings.html#ACTION_APPLICATION_DEVELOPMENT_SETTINGS</a></p> |
| 4845 | |
| 4846 | <p>61. Supporting Multiple Screens: <a href="http://developer.android.com/guide/practices/screens_support.html">http://developer.android.com/guide/practices/screens_support.html</a></p> |
| 4847 | |
| 4848 | <p>62. android.util.DisplayMetrics: <a href="http://developer.android.com/reference/android/util/DisplayMetrics.html">http://developer.android.com/reference/android/util/DisplayMetrics.html</a></p> |
| 4849 | |
| 4850 | <p>63. RenderScript: <a href="http://developer.android.com/guide/topics/renderscript/">http://developer.android.com/guide/topics/renderscript/</a></p> |
| 4851 | |
| 4852 | <p>64. Android extension pack for OpenGL ES: <a href="https://developer.android.com/reference/android/opengl/GLES31Ext.html">https://developer.android.com/reference/android/opengl/GLES31Ext.html</a> </p> |
| 4853 | |
| 4854 | <p>65. Hardware Acceleration: <a href="http://developer.android.com/guide/topics/graphics/hardware-accel.html">http://developer.android.com/guide/topics/graphics/hardware-accel.html</a></p> |
| 4855 | |
| 4856 | <p>66. EGL Extension-EGL_ANDROID_RECORDABLE:</p> |
| 4857 | |
| 4858 | <p><a href="http://www.khronos.org/registry/egl/extensions/ANDROID/EGL_ANDROID_recordable.txt">http://www.khronos.org/registry/egl/extensions/ANDROID/EGL_ANDROID_recordable.txt</a></p> |
| 4859 | |
| 4860 | <p>67. Display Manager: <a href="http://developer.android.com/reference/android/hardware/display/DisplayManager.html">http://developer.android.com/reference/android/hardware/display/DisplayManager.html</a></p> |
| 4861 | |
| 4862 | <p>68. android.content.res.Configuration: <a href="http://developer.android.com/reference/android/content/res/Configuration.html">http://developer.android.com/reference/android/content/res/Configuration.html</a></p> |
| 4863 | |
| 4864 | <p>69. Action Assist: <a href="http://developer.android.com/reference/android/content/Intent.html#ACTION_ASSIST">http://developer.android.com/reference/android/content/Intent.html#ACTION_ASSIST</a></p> |
| 4865 | |
| 4866 | <p>70. Touch Input Configuration: <a href="http://source.android.com/devices/tech/input/touch-devices.html">http://source.android.com/devices/tech/input/touch-devices.html</a></p> |
| 4867 | |
| 4868 | <p>71. Motion Event API: <a href="http://developer.android.com/reference/android/view/MotionEvent.html">http://developer.android.com/reference/android/view/MotionEvent.html</a></p> |
| 4869 | |
| 4870 | <p>72. Key Event API: <a href="http://developer.android.com/reference/android/view/KeyEvent.html">http://developer.android.com/reference/android/view/KeyEvent.html</a> </p> |
| 4871 | |
| 4872 | <p>73. Android Open Source sensors: <a href="http://source.android.com/devices/sensors/">http://source.android.com/devices/sensors</a></p> |
| 4873 | |
| 4874 | <p>74. android.hardware.SensorEvent: <a href="http://developer.android.com/reference/android/hardware/SensorEvent.html">http://developer.android.com/reference/android/hardware/SensorEvent.html</a></p> |
| 4875 | |
| 4876 | <p>75. Timestamp sensor event: <a href="http://developer.android.com/reference/android/hardware/SensorEvent.html#timestamp">http://developer.android.com/reference/android/hardware/SensorEvent.html#timestamp</a></p> |
| 4877 | |
| 4878 | <p>76. Android Open Source composite sensors: <a href="http://source.android.com/devices/sensors/sensor-types.html#composite_sensor_type_summary">https://source.android.com/devices/sensors/sensor-types.html#composite_sensor_type_summary</a></p> |
| 4879 | |
| 4880 | <p>77. Continuous trigger mode: <a href="http://source.android.com/devices/sensors/report-modes.html#continuous">https://source.android.com/devices/sensors/report-modes.html#continuous</a></p> |
| 4881 | |
| 4882 | <p>78. Accelerometer sensor: <a href="http://developer.android.com/reference/android/hardware/Sensor.html#TYPE_ACCELEROMETER">http://developer.android.com/reference/android/hardware/Sensor.html#TYPE_ACCELEROMETER</a></p> |
| 4883 | |
| 4884 | <p>79. Wi-Fi Multicast API: <a href="http://developer.android.com/reference/android/net/wifi/WifiManager.MulticastLock.html">http://developer.android.com/reference/android/net/wifi/WifiManager.MulticastLock.html</a></p> |
| 4885 | |
| 4886 | <p>80. Wi-Fi Direct (Wi-Fi P2P): <a href="http://developer.android.com/reference/android/net/wifi/p2p/WifiP2pManager.html">http://developer.android.com/reference/android/net/wifi/p2p/WifiP2pManager.html</a></p> |
| 4887 | |
| 4888 | <p>81. WifiManager API: <a href="http://developer.android.com/reference/android/net/wifi/WifiManager.html">http://developer.android.com/reference/android/net/wifi/WifiManager.html</a></p> |
| 4889 | |
| 4890 | <p>82. Bluetooth API: <a href="http://developer.android.com/reference/android/bluetooth/package-summary.html">http://developer.android.com/reference/android/bluetooth/package-summary.html</a></p> |
| 4891 | |
| 4892 | <p>83. Bluetooth ScanFilter API: <a href="https://developer.android.com/reference/android/bluetooth/le/ScanFilter.html">https://developer.android.com/reference/android/bluetooth/le/ScanFilter.html</a></p> |
| 4893 | |
| 4894 | <p>84. NDEF Push Protocol: <a href="http://source.android.com/compatibility/ndef-push-protocol.pdf">http://source.android.com/compatibility/ndef-push-protocol.pdf</a></p> |
| 4895 | |
| 4896 | <p>85. Android Beam: <a href="http://developer.android.com/guide/topics/connectivity/nfc/nfc.html">http://developer.android.com/guide/topics/connectivity/nfc/nfc.html</a> </p> |
| 4897 | |
| 4898 | <p>86. Android NFC Sharing Settings:</p> |
| 4899 | |
| 4900 | <p><a href="http://developer.android.com/reference/android/provider/Settings.html#ACTION_NFCSHARING_SETTINGS">http://developer.android.com/reference/android/provider/Settings.html#ACTION_NFCSHARING_SETTINGS</a></p> |
| 4901 | |
| 4902 | <p>87. NFC Connection Handover: <a href="http://members.nfc-forum.org/specs/spec_list/#conn_handover">http://members.nfc-forum.org/specs/spec_list/#conn_handover</a></p> |
| 4903 | |
| 4904 | <p>88. Bluetooth Secure Simple Pairing Using NFC: <a href="http://members.nfc-forum.org/apps/group_public/download.php/18688/NFCForum-AD-BTSSP_1_1.pdf">http://members.nfc-forum.org/apps/group_public/download.php/18688/NFCForum-AD-BTSSP_1_1.pdf</a> </p> |
| 4905 | |
| 4906 | <p>89. Content Resolver: <a href="http://developer.android.com/reference/android/content/ContentResolver.html">http://developer.android.com/reference/android/content/ContentResolver.html</a></p> |
| 4907 | |
| 4908 | <p>90. Camera orientation API: <a href="http://developer.android.com/reference/android/hardware/Camera.html#setDisplayOrientation(int)">http://developer.android.com/reference/android/hardware/Camera.html#setDisplayOrientation(int)</a></p> |
| 4909 | |
| 4910 | <p>91. Camera: <a href="http://developer.android.com/reference/android/hardware/Camera.html">http://developer.android.com/reference/android/hardware/Camera.html</a></p> |
| 4911 | |
| 4912 | <p>92. Camera: <a href="http://developer.android.com/reference/android/hardware/Camera.Parameters.html">http://developer.android.com/reference/android/hardware/Camera.Parameters.html</a></p> |
| 4913 | |
| 4914 | <p>93. Camera hardware level: <a href="https://developer.android.com/reference/android/hardware/camera2/CameraCharacteristics.html#INFO_SUPPORTED_HARDWARE_LEVEL">https://developer.android.com/reference/android/hardware/camera2/CameraCharacteristics.html#INFO_SUPPORTED_HARDWARE_LEVEL</a> </p> |
| 4915 | |
| 4916 | <p>94. Camera version support: <a href="http://source.android.com/devices/camera/versioning.html">http://source.android.com/devices/camera/versioning.html</a> </p> |
| 4917 | |
| 4918 | <p>95. Android DownloadManager: <a href="http://developer.android.com/reference/android/app/DownloadManager.html">http://developer.android.com/reference/android/app/DownloadManager.html</a></p> |
| 4919 | |
| 4920 | <p>96. Android File Transfer: <a href="http://www.android.com/filetransfer">http://www.android.com/filetransfer</a></p> |
| 4921 | |
| 4922 | <p>97. Android Open Accessories: <a href="http://developer.android.com/guide/topics/connectivity/usb/accessory.html">http://developer.android.com/guide/topics/connectivity/usb/accessory.html</a></p> |
| 4923 | |
| 4924 | <p>98. Android USB Audio: <a href="http://developer.android.com/reference/android/hardware/usb/UsbConstants.html#USB_CLASS_AUDIO">http://developer.android.com/reference/android/hardware/usb/UsbConstants.html#USB_CLASS_AUDIO</a></p> |
| 4925 | |
| 4926 | <p>99. USB Charging Specification: <a href="http://www.usb.org/developers/docs/devclass_docs/USB_Battery_Charging_1.2.pdf">http://www.usb.org/developers/docs/devclass_docs/USB_Battery_Charging_1.2.pdf</a></p> |
| 4927 | |
| 4928 | <p>100. USB Host API:<a href="http://developer.android.com/guide/topics/connectivity/usb/host.html"> http://developer.android.com/guide/topics/connectivity/usb/host.html</a></p> |
| 4929 | |
| 4930 | <p>101. Wired audio headset: <a href="http://source.android.com/accessories/headset-spec.html">http://source.android.com/accessories/headset-spec.html</a> </p> |
| 4931 | |
| 4932 | <p>102. Android Security and Permissions reference: <a href="http://developer.android.com/guide/topics/security/permissions.html">http://developer.android.com/guide/topics/security/permissions.html</a></p> |
| 4933 | |
| 4934 | <p>103. UserManager reference: <a href="http://developer.android.com/reference/android/os/UserManager.html">http://developer.android.com/reference/android/os/UserManager.html</a></p> |
| 4935 | |
| 4936 | <p>104. External Storage reference: <a href="http://source.android.com/devices/storage">http://source.android.com/devices/storage</a></p> |
| 4937 | |
| 4938 | <p>105. External Storage APIs: <a href="http://developer.android.com/reference/android/os/Environment.html">http://developer.android.com/reference/android/os/Environment.html</a></p> |
| 4939 | |
| 4940 | <p>106. SMS Short Code: <a href="http://en.wikipedia.org/wiki/Short_code">http://en.wikipedia.org/wiki/Short_code</a></p> |
| 4941 | |
| 4942 | <p>107. Android Open Source Encryption: <a href="http://source.android.com/devices/tech/security/encryption/index.html">http://source.android.com/devices/tech/security/encryption/index.html</a></p> |
| 4943 | |
| 4944 | <p>108. Android Compatibility Program Overview: <a href="http://source.android.com/compatibility/index.html">http://source.android.com/compatibility/index.html</a></p> |
| 4945 | |
| 4946 | <p>109. Android Compatibility forum: <a href="https://groups.google.com/forum/#!forum/android-compatibility">https://groups.google.com/forum/#!forum/android-compatibility</a></p> |
| 4947 | |
| 4948 | <p>110. WebM project: <a href="http://www.webmproject.org/">http://www.webmproject.org/</a> </p> |
| 4949 | |
| 4950 | <p>111. Android UI_MODE_TYPE_CAR API: <a href="http://developer.android.com/reference/android/content/res/Configuration.html#UI_MODE_TYPE_CAR">http://developer.android.com/reference/android/content/res/Configuration.html#UI_MODE_TYPE_CAR</a></p> |
| 4951 | |
| 4952 | <p>112. Android MediaCodecList API: <a href="http://developer.android.com/reference/android/media/MediaCodecList.html">http://developer.android.com/reference/android/media/MediaCodecList.html</a></p> |
| 4953 | |
| 4954 | <p>113. Android CamcorderProfile API: <a href="http://developer.android.com/reference/android/media/CamcorderProfile.html">http://developer.android.com/reference/android/media/CamcorderProfile.html</a></p> |
| 4955 | |
| 4956 | <p>Many of these resources are derived directly or indirectly from the Android |
| 4957 | SDK, and will be functionally identical to the information in that SDK’s |
| 4958 | documentation. In any cases where this Compatibility Definition or the |
| 4959 | Compatibility Test Suite disagrees with the SDK documentation, the SDK |
| 4960 | documentation is considered authoritative. Any technical details provided in |
| 4961 | the references included above are considered by inclusion to be part of this |
| 4962 | Compatibility Definition.</p> |
| 4963 | |
| 4964 | </div> |
| 4965 | </body> |
| 4966 | </html> |