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