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