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