Blame - src/compatibility/android-cdd.html - platform/docs/source.android.com

blob: a4c368c957c603c27bd376c9d499bc3b815d9d82 [file] [log] [blame]

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