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