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