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