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