Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

am 60026c3a: Merge "Doc change: adjust compatibility doc." into froyo

Browse Source 
Merge commit '60026c3ab0093e6d4cd464061ab9f36d4d041532' into froyo-plus-aosp

* commit '60026c3ab0093e6d4cd464061ab9f36d4d041532':
  Doc change: adjust compatibility doc.
This commit is contained in:
Dirk Dougherty
2010-05-14 14:00:12 -07:00
committed by Android Git Automerger
parent 55b7d1243f 60026c3ab0
commit 0d54b806c6
1 changed files with 2 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/html/guide/practices/compatibility.jd
View File

@@ -46,11 +46,8 @@ make sure they reach the right audience.</p>
<h3 id="defined">What does “Compatibility” mean?</h3>
<p>A device is “Android compatible” if it can run apps written for the
<em>Android execution environment</em>. The exact details of the Android
execution environment are defined by the Android Compatibility Definition
Document, but the single most to the ability to install and correctly run an
Android <code>.apk</code> file.</p>
<p>A device is “Android compatible” if it can correctly run apps written for the
<em>Android execution environment</em>.</p>
<p>There is exactly one Android API for each <a
href="{@docRoot}guide/appendix/api-levels.html">API level</a>, and it’s the same
@@ -222,10 +219,6 @@ microphones.</li>
ones, we will always take steps to protect existing applications so that they
don’t end up being available to devices where they won’t work.</p>
<p>This is implemented using the <code>aapt</code> tool in the SDK. To see which
features your app explicitly requires or is implicitly assumed to require, you
can use the command <code>aapt dump badging</code>.</p>
<h3 id="conclusion">Conclusion</h3>
<p>The goal of Android is to create a huge installed base for developers to take