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