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