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