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