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