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