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