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