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