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