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