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