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