diff options
Diffstat (limited to 'src/source/faqs.jd')
| -rw-r--r-- | src/source/faqs.jd | 223 |
1 files changed, 111 insertions, 112 deletions
diff --git a/src/source/faqs.jd b/src/source/faqs.jd index 625afcbd..60e02c2e 100644 --- a/src/source/faqs.jd +++ b/src/source/faqs.jd @@ -31,54 +31,52 @@ page.title=Frequently Asked Questions people, the processes, and the source code that make up Android.</p> <p>The people oversee the project and develop the actual source code. The processes refer to the tools and procedures we use to manage the development -of the software. The net result is the source code that you can use to build -cell phone and other devices.</p> +of the software. The net result is the source code you can use to build +mobile phones and other devices.</p> <h3 id="why-did-we-open-the-android-source-code">Why did we open the Android source code?</h3> <p>Google started the Android project in response to our own experiences -launching mobile apps. We wanted to make sure that there would always be an +launching mobile apps. We wanted to make sure there would always be an open platform available for carriers, OEMs, and developers to use to make -their innovative ideas a reality. We also wanted to make sure that there was no -central point of failure, so that no single industry player could restrict or control +their innovative ideas a reality. We also wanted to make sure there was no +central point of failure, so no single industry player could restrict or control the innovations of any other. The single most important goal of the Android -Open-Source Project (AOSP) is to make sure that the open-source Android +Open Source Project (AOSP) is to make sure that the open-source Android software is implemented as widely and compatibly as possible, to everyone's benefit.</p> -<p>You can find more information on this topic at our Project Philosophy page.</p> <h3 id="what-kind-of-open-source-project-is-android">What kind of open-source project is Android?</h3> -<p>Google oversees the development of the core Android open-source platform, -and works to create robust developer and user communities. For the most part +<p>Google oversees the development of the core Android open-source platform +and works to create robust developer and user communities. For the most part, the Android source code is licensed under the permissive Apache Software License 2.0, rather than a "copyleft" license. The main reason for this is because our most important goal is widespread adoption of the software, and we believe that the ASL2.0 license best achieves that goal.</p> -<p>You can find more information on this topic at our Project Philosophy and -Licensing pages. </p> +<p>You can find more information on this topic on our <a href="{@docRoot}source/licenses.html">Licenses</a> page.</p> <h3 id="why-is-google-in-charge-of-android">Why is Google in charge of Android?</h3> <p>Launching a software platform is complex. Openness is vital to the long-term success of a platform, since openness is required to attract investment from developers and ensure a level playing field. However, the -platform itself must also be a compelling product to end users.</p> +platform itself must also be a compelling product to users.</p> <p>That's why Google has committed the professional engineering resources necessary to ensure that Android is a fully competitive software platform. Google treats the Android project as a full-scale product development -operation, and strikes the business deals necessary to make sure that great +operation and strikes the business deals necessary to make sure great devices running Android actually make it to market.</p> -<p>By making sure that Android is a success with end users, we help ensure the -vitality of Android as a platform, and as an open-source project. After all, +<p>By making sure Android is a success with users, we help ensure the +vitality of Android as a platform and as an open-source project. After all, who wants the source code to an unsuccessful product?</p> -<p>Google's goal is to ensure a successful ecosystem around Android, but no -one is required to participate, of course. We opened the Android source code +<p>Google's goal is to ensure a successful ecosystem around Android. Of course, no +one is required to participate. We opened the Android source code so anyone can modify and distribute the software to meet their own needs.</p> <h3 id="what-is-googles-overall-strategy-for-android-product-development">What is Google's overall strategy for Android product development?</h3> -<p>We focus on releasing great devices into a competitive marketplace, and +<p>We aim to release great devices into a competitive marketplace. We then incorporate the innovations and enhancements we made into the core -platform, as the next version.</p> -<p>In practice, this means that the Android engineering team typically focuses -on a small number of "flagship" devices, and develops the next version of +platform as the next version.</p> +<p>In practice, this means the Android engineering team typically focuses +on a small number of "flagship" devices and develops the next version of the Android software to support those product launches. These flagship devices absorb much of the product risk and blaze a trail for the broad OEM community, who follow up with many more devices that take advantage of the -new features. In this way, we make sure that the Android platform evolves +new features. In this way, we make sure the Android platform evolves according to the actual needs of real-world devices.</p> <h3 id="how-is-the-android-software-developed">How is the Android software developed?</h3> <p>Each platform version of Android (such as 1.5, 1.6, and so on) has a @@ -93,60 +91,61 @@ stable branch from the experimental branch as appropriate.</p> <p>Finally, Google works on the next version of the Android platform in tandem with developing a flagship device. This branch pulls in changes from the experimental and stable branches as appropriate.</p> -<p>You can find more information on this topic at our <a href="{@docRoot}source/code-lines.html">Branches and Releases</a>.</p> +<p>You can find more information on this topic at our <a href="{@docRoot}source/code-lines.html">Codelines, +Branches and Releases</a> page.</p> <h3 id="why-are-parts-of-android-developed-in-private">Why are parts of Android developed in private?</h3> -<p>It typically takes over a year to bring a device to market, but of course +<p>It typically takes more than a year to bring a device to market. And, of course, device manufacturers want to ship the latest software they can. Developers, -meanwhile, don't want to have to constantly track new versions of the +meanwhile, don't want to constantly track new versions of the platform when writing apps. Both groups experience a tension between -shipping products, and not wanting to fall behind.</p> +shipping products and not wanting to fall behind.</p> <p>To address this, some parts of the next version of Android including the core platform APIs are developed in a private branch. These APIs constitute the next version of Android. Our aim is to focus attention on the current -stable version of the Android source code, while we create the next version -of the platform as driven by flagship Android devices. This allows developers -and OEMs to focus on a single version without having to track unfinished +stable version of the Android source code while we create the next version +of the platform. This allows developers +and OEMs to use a single version without tracking unfinished future work just to keep up. Other parts of the Android system that aren't related to application compatibility are developed in the open, however. It's our intention to move more of these parts to open development over time.</p> <h3 id="when-are-source-code-releases-made">When are source code releases made?</h3> -<p>When they are ready. Some parts of Android are developed in the open, +<p>When they are ready. Releasing the source code is a fairly complex process. +Some parts of Android are developed in the open, so that source code is always available. Other parts are developed first in a private tree, and that source code is released when the next platform version is ready.</p> <p>In some releases, core platform APIs will be ready far enough in advance -that we can push the source code out for an early look in advance of the -device's release; however in others, this isn't possible. In all cases, we +that we can push the source code out for an early look prior to the +device's release; however in other releases, this isn't possible. In all cases, we release the platform source when we feel the version has stabilized enough, -and when the development process permits. Releasing the source code is a -fairly complex process.</p> +and when the development process permits.</p> <h3 id="what-is-involved-in-releasing-the-source-code-for-a-new-android-version">What is involved in releasing the source code for a new Android version?</h3> <p>Releasing the source code for a new version of the Android platform is a significant process. First, the software gets built into a system image for -a device, and put through various forms of certification, including +a device and put through various forms of certification, including government regulatory certification for the regions the phones will be deployed. It also goes through operator testing. This is an important phase of the process, since it helps shake out a lot of software bugs.</p></p> <p>Once the release is approved by the regulators and operators, the manufacturer begins mass producing devices, and we turn to releasing the source code.</p> -<p>Simultaneous to mass production the Google team kicks off several efforts -to prepare the open source release. These efforts include final API changes -and documentation (to reflect any changes that were made during +<p>Simultaneous to mass production, the Google team kicks off several efforts +to prepare the open source release. These efforts include making final API changes, +updating documentation (to reflect any modifications that were made during qualification testing, for example), preparing an SDK for the new version, and launching the platform compatibility information.</p> <p>Also included is a final legal sign-off to release the code into open source. Just as open source contributors are required to sign a Contributors -License Agreement attesting to their IP ownership of their contribution, -Google too must verify that it is clear to make contributions.</p> -<p>Starting at the time mass production begins, the software release process -usually takes around a month, which often roughly places source code -releases around the same time that the devices reach users.</p> +License Agreement attesting to their intellectual property ownership of their +contribution, Google too must verify it is clear to make contributions.</p> +<p>From the time mass production begins, the software release process +usually takes around a month. This often places source code releases +around the same time the devices reach users.</p> <h3 id="how-does-the-aosp-relate-to-the-android-compatibility-program">How does the AOSP relate to the Android Compatibility Program?</h3> -<p>The Android Open-Source Project maintains the Android software, and +<p>The Android Open Source Project maintains the Android software, and develops new versions. Since it's open-source, this software can be used for -any purpose, including to ship devices that are not compatible with other +any purpose, including to develop devices that are not compatible with other devices based on the same source.</p> <p>The function of the Android Compatibility Program is to define a baseline implementation of Android that is compatible with third-party apps written @@ -154,23 +153,25 @@ by developers. Devices that are "Android compatible" may participate in the Android ecosystem, including Google Play; devices that don't meet the compatibility requirements exist outside that ecosystem.</p> <p>In other words, the Android Compatibility Program is how we separate -"Android compatible devices" from devices that merely run derivatives of the +"Android-compatible devices" from devices that merely run derivatives of the source code. We welcome all uses of the Android source code, but only -Android compatible devices -- as defined and tested by the Android +Android-compatible devices -- as defined and tested by the Android Compatibility Program -- may participate in the Android ecosystem.</p> <h3 id="how-can-i-contribute-to-android">How can I contribute to Android?</h3> <p>There are a number of ways you can contribute to Android. You can report bugs, write apps for Android, or contribute source code to the Android -Open-Source Project.</p> -<p>There are some limits on the kinds of code contributions we are willing or +Open Source Project.</p> +<p>There are some limits to the kinds of code contributions we are willing or able to accept. For instance, someone might want to contribute an alternative application API, such as a full C++-based environment. We would -decline that contribution, since Android is focused on applications that run -in the Dalvik VM. Alternatively, we won't accept contributions such as GPL +decline that contribution, since Android encourages applications to be run +in the Dalvik VM. Similarly, we won't accept contributions such as GPL or LGPL libraries that are incompatible with our licensing goals.</p> -<p>We encourage those interested in contributing source code to contact us via -the AOSP Community page prior to beginning any work. You can find more -information on this topic at the Getting Involved page.</p> +<p>We encourage those interested in contributing source code to contact us +via the channels listed on the <a href="{@docRoot}source/community/index.html"> +Android Community</a> page prior to beginning any work. You can find more +information on this topic from the <a href="{@docRoot}source/contributing.html"> +Contributing</a> page.</p> <h3 id="how-do-i-become-an-android-committer">How do I become an Android committer?</h3> <p>The Android Open Source Project doesn't really have a notion of a "committer". All contributions -- including those authored by Google @@ -181,40 +182,40 @@ contributions.</p> <p>Once submitted, changes need to be accepted by a designated Approver. Approvers are typically Google employees, but the same approvers are responsible for all submissions, regardless of origin.</p> -<p>You can find more information on this topic at the <a href="{@docRoot}source/submit-patches.html">Submitting Patches</a> page.</p> +<p>You can find more information on this topic at the <a href="submit-patches.html">Submitting Patches</a> page.</p> <a href="#top">Back to top</a> <h2 id="compatibility">Compatibility</h2> <h3 id="what-does-compatibility-mean">What does "compatibility" mean?</h3> -<p>We define an "Android compatible" device as one that can run any +<p>We define an "Android-compatible device" as one that can run any application written by third-party developers using the Android SDK and NDK. We use this as a filter to separate devices that can participate in the -Android app ecosystem, and those that cannot. Devices that are properly +Android app ecosystem and those that cannot. Devices that are properly compatible can seek approval to use the Android trademark. Devices that are not compatible are merely derived from the Android source code and may not use the Android trademark.</p> <p>In other words, compatibility is a prerequisite to participate in the -Android apps ecosystem. Anyone is welcome to use the Android source code, -but if the device isn't compatible, it's not considered part of the Android +Android apps ecosystem. Anyone is welcome to use the Android source code. +But if the device isn't compatible, it's not considered part of the Android ecosystem.</p> <h3 id="what-is-the-role-of-google-play-in-compatibility">What is the role of Google Play in compatibility?</h3> <p>Devices that are Android compatible may seek to license the Google Play client software. This allows them to become part of the Android app -ecosystem, by allowing users to download developers' apps from a catalog +ecosystem, enabling their users to download developers' apps from a catalog shared by all compatible devices. This option isn't available to devices that aren't compatible.</p> <h3 id="what-kinds-of-devices-can-be-android-compatible">What kinds of devices can be Android compatible?</h3> -<p>The Android software can be ported to a lot of different kinds of devices, -including some on which third-party apps won't run properly. The Android -Compatibility Definition Document (CDD) spells out the specific device -configurations that will be considered compatible.</p> +<p>The Android software can be ported to many different kinds of devices, +including some on which third-party apps won't run properly. The +<a href="{@docRoot}compatibility/index.html">Android Compatibility Definition +Document</a> (CDD) spells out the specific device configurations that will be +considered compatible.</p> <p>For example, though the Android source code could be ported to run on a -phone that doesn't have a camera, the CDD requires that in order to be -compatible, all phones must have a camera. This allows developers to rely -on a consistent set of capabilities when writing their apps.</p> +phone that doesn't have a camera, the CDD requires all phones to have a camera. +This allows developers to rely on a consistent set of capabilities when writing their apps.</p> <p>The CDD will evolve over time to reflect market realities. For instance, -the 1.6 CDD only allows cell phones, but the 2.1 CDD allows devices to omit -telephony hardware, allowing for non-phone devices such as tablet-style -music players to be compatible. As we make these changes, we will also +version 1.6 of the CDD supports only cell phones. But the 2.1 CDD allows devices +to omit telephony hardware, enabling non-phone devices such as tablet-style music +players to be compatible. As we make these changes, we will also augment Google Play to allow developers to retain control over where their apps are available. To continue the telephony example, an app that manages SMS text messages would not be useful on a media player, so Google @@ -223,26 +224,27 @@ devices.</p> <h3 id="if-my-device-is-compatible-does-it-automatically-have-access-to-google-play-and-branding">If my device is compatible, does it automatically have access to Google Play and branding?</h3> <p>Google Play is a service operated by Google. Achieving compatibility is a prerequisite for obtaining access to the Google Play software and branding. -Device manufacturers should contact Google to obtain access to Google -Play.</p> +Device manufacturers should contact <a +href="mailto:android-partnerships@google.com">android-partnerships@google.com</a> +to obtain access to Google Play.</p> <h3 id="if-i-am-not-a-manufacturer-how-can-i-get-google-play">If I am not a manufacturer, how can I get Google Play?</h3> <p>Google Play is only licensed to handset manufacturers shipping devices. -For questions about specific cases, contact android-partnerships@google.com.</p> +For questions about specific cases, contact <a +href="mailto:android-partnerships@google.com">android-partnerships@google.com</a>.</p> <h3 id="how-can-i-get-access-to-the-google-apps-for-android-such-as-maps">How can I get access to the Google apps for Android, such as Maps?</h3> -<p>The Google apps for Android, such as YouTube, Google Maps and Navigation, -Gmail, and so on are Google properties that are not part of Android, and -are licensed separately. Contact android-partnerships@google.com for -inquiries related to those apps.</p> +<p>The Google apps for Android, such as YouTube, Google Maps, +Gmail, and more, are Google properties that are not part of Android and +are licensed separately. Contact <a +href="mailto:android-partnerships@google.com">android-partnerships@google.com</a> +for inquiries related to those apps.</p> <h3 id="is-compatibility-mandatory">Is compatibility mandatory?</h3> <p>No. The Android Compatibility Program is optional. Since the Android source -code is open, anyone can use it to build any kind of device. However, if a -manufacturer wishes to use the Android name with their product, or wants -access to Google Play, they must first demonstrate that the device is -compatible.</p> +code is open, anyone can use it to build any kind of device. However, if manufacturers +wish to use the Android name with their products, or want access to Google Play, +they must first demonstrate their devices are compatible.</p> <h3 id="how-much-does-compatibility-certification-cost">How much does compatibility certification cost?</h3> <p>There is no cost to obtain Android compatibility for a device. The -Compatibility Test Suite is open-source and available to anyone to use to -test a device.</p> +Compatibility Test Suite is open-source and available to anyone for device testing.</p> <h3 id="how-long-does-compatibility-take">How long does compatibility take?</h3> <p>The process is automated. The Compatibility Test Suite generates a report that can be provided to Google to verify compatibility. Eventually we intend @@ -251,7 +253,7 @@ to provide self-service tools to upload these reports to a public database.</p> <p>Since Google is responsible for the overall direction of Android as a platform and product, Google maintains the Compatibility Definition Document for each release. We draft the CDD for a new Android version in consultation -with a number of OEMs, who provide input on its contents.</p> +with various OEMs who provide input on its contents.</p> <h3 id="how-long-will-each-android-version-be-supported-for-new-devices">How long will each Android version be supported for new devices?</h3> <p>Since Android's code is open-source, we can't prevent someone from using an old version to launch a device. Instead, Google chooses not to license the @@ -260,9 +262,9 @@ obsolete. This allows anyone to continue to ship old versions of Android, but those devices won't use the Android name and will exist outside the Android apps ecosystem, just as if they were non-compatible.</p> <h3 id="can-a-device-have-a-different-user-interface-and-still-be-compatible">Can a device have a different user interface and still be compatible?</h3> -<p>The Android Compatibility Program focuses on whether a device can run +<p>The Android Compatibility Program determines whether a device can run third-party applications. The user interface components shipped with a -device (such as home screen, dialer, color scheme, and so on) does not +device (such as home screen, dialer, color scheme, and so on) do not generally have much effect on third-party apps. As such, device builders are free to customize the user interface as much as they like. The Compatibility Definition Document does restrict the degree to which OEMs may alter the @@ -304,7 +306,7 @@ prefer.</p> <p>The CTS is licensed under the same Apache Software License 2.0 that the bulk of Android uses.</p> <h3 id="does-the-cts-accept-contributions">Does the CTS accept contributions?</h3> -<p>Yes please! The Android Open-Source Project accepts contributions to +<p>Yes please! The Android Open Source Project accepts contributions to improve the CTS in the same way as for any other component. In fact, improving the coverage and quality of the CTS test cases is one of the best ways to help out Android.</p> @@ -323,16 +325,14 @@ Android Open Source Project. We are dedicated to building and maintaining one of the most secure mobile platforms available while still fulfilling our goal of opening the mobile device space to innovation and competition.</p> -<p> A comprehensive overview of the <a -href="http://source.android.com/tech/security/index.html">Android -security model and Android security processes</a> is provided in the Android -Open Source Project Website.</p> +<p>See the <a href="{@docRoot}devices/tech/security/index.html">Android Security +Overview</a> for a comprehensive description of the Android security model and processes.</p> <p>Application developers play an important part in the security of Android. The Android Platform provides developers with a rich <a -href="http://code.google.com/android/devel/security.html">security model</a> -that to request the capabilities, or access, needed by their -application and to define new capabilities that other applications can request. +href="http://developer.android.com/training/articles/security-tips.html">security model</a> +that allows them to request capabilities, or access, from users +and define new capabilities other applications can request. The Android user can choose to grant or deny an application's request for certain capabilities on the handset.</p> @@ -343,17 +343,16 @@ quickly and professionally to vulnerability reports from external researchers. </p> -<h3 id="issue">I think I found a security flaw. How do I -report it?</h3> +<h3 id="issue">I think I found a security flaw. How do I report it?</h3> <p>You can reach the Android security team at <a href="mailto:security@android.com">security@android.com</a>. If you like, you can protect your message using our <a -href="http://code.google.com/android/security_at_android_dot_com.txt">PGP +href="http://developer.android.com/security_at_android_dot_com.txt">PGP key</a>.</p> <p>We appreciate researchers practicing responsible disclosure by emailing us -with a detailed summary of the issue and keeping the issue confidential while +a detailed summary of the issue and keeping the issue confidential while users are at risk. In return, we will make sure to keep the researcher informed of our progress in issuing a fix. </p> @@ -368,16 +367,16 @@ href="http://groups.google.com/group/android-security-discuss">android-security- <h3 id="use">How do I securely use my Android phone?</h3> -<p>Android was designed so that you can safely use your phone without making +<p>Android was designed so you can safely use your phone without making any changes to the device or installing any special software. Android applications run in an Application Sandbox that limits access to sensitive information or data with the users permission.</p> <p>To fully benefit from the security protections in Android, it is important that -users only download and install software from known sources.</p> +users download and install software only from known sources.</p> <p>As an open platform, Android allows users to visit any website and load -software from any developer onto a device. As with a home PC, the user must be +software from any developer onto a device. As with a home PC, users must be aware of who is providing the software they are downloading and must decide whether they want to grant the application the capabilities it requests. This decision can be informed by the user's judgment of the software @@ -396,22 +395,22 @@ much detail about the application as possible, with the location it is being distributed from and why you suspect it of being malicious software.</p> <p>The term <i>malicious software</i> is subjective, and we cannot make an -exhaustive definition. Some examples of what the Android Security Team believes +exhaustive definition. Some examples of what the Android security team believes to be malicious software is any application that: <ul> <li>uses a bug or security vulnerability to gain permissions that have not - been granted by the user</li> + been granted by the user.</li> <li>shows the user unsolicited messages (especially messages urging the - user to buy something);</li> - <li>resists (or attempts to resist) the user's effort to uninstall it;</li> - <li>attempts to automatically spread itself to other devices;</li> - <li>hides its files and/or processes;</li> + user to buy something).</li> + <li>resists (or attempts to resist) the user's effort to uninstall it.</li> + <li>attempts to automatically spread itself to other devices.</li> + <li>hides its files and/or processes.</li> <li>discloses the user's private information to a third party, without the - user's knowledge and consent;</li> + user's knowledge and consent.</li> <li>destroys the user's data (or the device itself) without the user's - knowledge and consent;</li> + knowledge and consent.</li> <li>impersonates the user (such as by sending email or buying things from a - web store) without the user's knowledge and consent; or</li> + web store) without the user's knowledge and consent.</li> <li>otherwise degrades the user's experience with the device.</li> </ul> </p> @@ -421,12 +420,12 @@ fixes?</h3> <p>The manufacturer of each device is responsible for distributing software upgrades for it, including security fixes. Many devices will update themselves -automatically with software downloaded "over the air", while some devices +automatically with software downloaded "over the air" (OTA), while some devices require the user to upgrade them manually.</p> <p>Google provides software updates for a number of Android devices, including the <a href="http://www.google.com/nexus">Nexus</a> -series of devices, using an "over the air" (OTA) update. These updates may include +series of devices, using an OTA update. These updates may include security fixes as well as new features.</p> <h3 id="directfix">Can I get a fix directly from the |