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