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