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