+This list is for general discussion about the Android open-source project or +the platform technologies.
+Subscribe using Google Groups: android-platform
+Subscribe via email: android-platform+subscribe@googlegroups.com +
Subscribe to this list for discussion and help on building the Android source code, and on the build system. If you've just checked out the source code and @@ -58,14 +66,14 @@ href="http://groups.google.com/group/android-porting">android-porting
Subscribe via email: android-porting+subscribe@googlegroups.com
-This list is for developers who want to contribute code to the Android -user-space projects, such as the core system libraries, the Android -services, the public APIs, or the built-in applications. Note: contributors +
+This list is for developers who want to contribute code to Android. This is a +working list, and is not appropriate for general discussion. We ask that +general discussion go to android-platform. Note: contributors to the Android kernel should go to the android-kernel list, below.
Subscribe using Google Groups: android-platform
-Subscribe via email: android-platform+subscribe@googlegroups.com +href="http://groups.google.com/group/android-contrib">android-contrib
+Subscribe via email: android-contrib+subscribe@googlegroups.com
@@ -88,9 +96,8 @@ site, you can use your email client of choice to participate in the mailing list under "subscribe via email" in the lists above.
To set up how you receive mailing list postings by email:
-
-
- Sign into the group via the Google Groups site. For example, for the android-framework group you would -visit http://groups.google.com/group/android-framework. +
- Sign into the group via the Google Groups site. For example, for the android-platform group you would +visit http://groups.google.com/group/android-platform.
- Click "Edit my membership" on the right side.
- Under "How do you want to read this group?" select one of the email options.
- #android-offtopic - for, well, off-topic discussions
- #android-root - for discussion related to off-label uses of hardware -
- #androidfra - pour discuter d'Android en français +
- #android-fr - pour discuter d'Android en français
Getting Started
More Information
diff --git a/pdk/docs/compatibility/contact-us.jd b/pdk/docs/compatibility/contact-us.jd
index ba4e8871a..609c8ab4d 100644
--- a/pdk/docs/compatibility/contact-us.jd
+++ b/pdk/docs/compatibility/contact-us.jd
@@ -7,13 +7,13 @@ this site, you can reach us in one of a few different ways. To get the most
out of any of these options, please first read "Getting the Most from Our
Lists" on the Community page.
-- Obtain the Android software stack source code
This is the +
- Obtain the Android software source code
This is the source code for the Android platform, that you port to your hardware.
- - Comply with Android Compatibility Definition Document
- This document enumerates the software and the hardware features of +
- Comply with Android Compatibility Definition Document (CDD)
+ The CDD enumerates the software and hardware requirements of a compatible Android device.
- Pass the Compatibility Test Suite (CTS)
You can use the CTS (included in the Android source code) as an ongoing aid to compatibility during the development process.
- - Submit CTS report
[Optional] You can also submit your CTS report, - so that it can be validated and recorded.
Note: - the submission system is currently under construciton, and is not currently - available.
PDK
-
-
- PDK 1.6 -
-
- Compatibility
-
-
- Android 1.6 -
-- Follow the normal steps to setup repo and check out the sources. @@ -22,17 +22,6 @@ to setup repo and check out the sources.
- from this point, the fastboot tool (which is put automatically in your path) can be used to flash a device: boot the device into the bootloader by holding the back key while pressing the power key, and run "fastboot -w flashall".
- Follow the normal steps -to setup repo and check out the sources. - -
- At the root of your source tree, run ". build/envsetup.sh" like you normally would for an emulator build. - -
- Run "make adb" if you don't already have adb in your path.
- in vendor/htc/dream-open/ there is a script called "extract-files.sh" that must be run (from that directory) to extract some proprietary binaries from your device (*). You only need to do this once.
- run "lunch htc_dream-eng" to specifically configure the build system for dream (the default is the equivalent of "lunch generic-eng", which doesn't contain dream-specific files).
- run make from the top of the source tree. - -
- from this point, the fastboot tool (which is put automatically in your path) can be used to flash a device: boot the device into the bootloader by holding the back key while pressing the power key, and run "fastboot -w flashall".
- Assigned
- Like
Unassigned, but the bug has been + - Assigned
Like
Unassigned, but the bug has been actually assigned to a specific contributor to fix. - Spam
A kind soul sent us some delicious pork products, that we, regrettably, do not want.
- Question
Someone mistook the issue tracker for a help forum. -(This is not as uncommon as one might assume: many users whose native language -isn't English can make this mistake.)
+(This is not as uncommon as you might think: many users whose native language
+isn't English misunderstand the site and make this mistake.)
- Unreproducible
An AOSP contributor attempted to reproduce the behavior described, and was unable to do so. This sometimes means that the bug is legitimate but simply rare or difficult to reproduce, and sometimes means diff --git a/pdk/docs/source/roles.jd b/pdk/docs/source/roles.jd index 451c821d9..f4fb89151 100644 --- a/pdk/docs/source/roles.jd +++ b/pdk/docs/source/roles.jd @@ -15,22 +15,22 @@ href="{@docRoot}source/index.html">Get Involved.
Contributor
A "Contributor" is anyone making contributions to the AOSP source code, -including both employees of Google or other companies, as well as -external developers who are contributing to Android on their own behalf. -There is no distinction between Contributors who are employed by -Google, and those who are not: all engineers use the same git/gerrit tools, -follow the same code review process, and are subject to the same requirements -on code style and so on.
+including both employees of Google or other companies, as well as external +developers who are contributing to Android on their own behalf. There is no +distinction between Contributors who are employed by Google, and those who are +not: all engineers use the same tools (git,repo, +andgerrit), follow the same code review process, and are subject +to the same requirements on code style and so on.Developer
A "Developer" is an engineer writing applications that run on Android devices. There is, of course, no difference in skillset between a "Developer" -and a "Contributor"; AOSP simply uses "Developer" to help identify our audience. -Since the key purpose of Android is to cultivate an open development platform, -"Developers" are one of the key customers of the Android platform. As such, we -talk about them a lot, though this isn't technically a separate role in the -AOSP per se.
+and a "Contributor", but AOSP uses "Developer" to distinguish between +engineers using the platform and those contributing to it. Developers are +(along with end users) the "customers" of the platform that the Contributors +create. As such, we talk about Developers a lot, though this isn't technically +a separate role in the AOSP per se.Verifier
@@ -62,12 +62,12 @@ responsible for the following: releases. - Designate Verifiers and Approvers for submitted patches.
- Be fair and unbiased while reviewing changes. Accept or reject patches - based on technical merit and alignment with the Android platform. + based on technical merit and alignment with the Android strategy.
- Review changes in a timely manner and make best efforts to communicate when changes are not accepted.
- Optionally maintain a web site for the project for information and documents specific to the project.
- Act as a facilitator in resolving technical conflicts. -
- Be the public face for the project and the go-to person for questions +
- Be a public face for the project and the go-to person for questions related to the project.
Discussion Group
+For General Discussion
The preferred way to reach us is via the android-compatibility mailing list. Use this list for all your compatibility-related questions. Please be aware that this is a public forum.
-CTS Technical Questions
+For CTS Technical Questions
If you have specific issues with the Compatibility Test Suite that require
you to disclose information you'd prefer not to be public, you can contact an
email address we've set up specifically this purpose:
- Finally, business inquiries about the compatibility program, including
requests to use branding elements and so on, can be sent to the address compatibility@android.com. Like
+href="mailto:android-partnerships@google.com">android-partnerships@google.comPrivate Inquiries
+For Business Inquiries
Thanks for your interest in Android Compatibility! The links below allow +you to access the key documents and information.
+ +Android 2.1
+Android 2.1 is the release of the development milestone code-named +Eclair. Android 2.1 is the current version of Android. Source code for Android +2.1 is found in the 'eclair' branch in the open-source tree. Note that for +technical reasons, there is no compatibility program for Android 2.0 or 2.0.1, +and new devices must use Android 2.1. +
+ + +Android 1.6
+Android 1.6 was the release of the development milestone code-named Donut. +Android 1.6 was obsoleted by Android 2.1. Source code for Android 1.6 is found +in the 'donut' branch in the open-source tree. +
+ +Compatibility Test Suite
+The Compatibility Test Suite (CTS) is found in the open-source tree. Specific +snapshots of the CTS are found in the same branches as for the system. (For +instance, the Android 2.1 CTS can be found in the 'eclair' branch.) The CTS user +manual is not specific to given versions. +
+ +Older Android Versions
+There is no Compatibility Program for older versions of Android, such as Android +1.5 (known in development as Cupcake). New devices intended to be Android +compatible must ship with Android 1.6 or later.
diff --git a/pdk/docs/compatibility/index.jd b/pdk/docs/compatibility/index.jd index 0c39a9853..a1c37aeeb 100644 --- a/pdk/docs/compatibility/index.jd +++ b/pdk/docs/compatibility/index.jd @@ -3,15 +3,15 @@ doc.type=compatibility @jd:bodyAndroid is an open source product, and anyone can use the source code to build devices. The purpose of the Android compatibility program is to help Android -device implementations remain compatible with all apps.
+device implementations remain compatible with apps.A device is considered compatible if existing and new third-party applications run correctly on it. Poor device implementations that change APIs or alter behaviors will break these apps and so are not compatible. The -Android compatibility program's aim is to ensure that these APIs are -consistently implemented across devices.
+Android Compatibility Program provides information and tools that device +implementers use to ensure that their devices are Android-compatible.The latest version of the Android source code and compatibility program is -1.6, which roughly corresponded to the Donut branch. The compatibility -program for Android 2.x (corresponding to Eclair) is coming soon.
+2.1, which roughly corresponded to the Eclair branch. +Why build compatible Android devices?
Users want a customizable device.
A mobile phone is a highly personal, always-on, always-present gateway to @@ -20,7 +20,7 @@ extending its functionality. That's why Android was designed as a robust platform for running after-market applications.
Developers outnumber us all.
-No device manufacturer can hope to write all the software that anyone could +
No device manufacturer can hope to write all the software that a person could conceivably need. We need third-party developers to write the apps users want, so the Android Open Source Project aims to make it as easy and open as possible for developers to build apps.
@@ -40,28 +40,21 @@ Android compatibility program in general, see the program overview.Building a compatible device is a four-step process:
-
-
Benefits of compatibility
-By submitting a validated CTS report, you receive public recognition of -your device's compatibility. This also opens up additional options you can -pursue such as use of the Android branding, access to Android Market, and -more.
-As a consequence of some legal quirks, we aren't able to offer automatic -licensing of either the Android Market or branding. To actually obtain access -to these programs, you will need to contact us to obtain a -license.
+Joining the Ecosystem
+Once you've built a compatible device, you may wish to include Android +Market to provide your users access to the third-party app ecosystem. +Unfortunately, for a variety of legal and business reasons, we aren't able to +automatically license Android Market to any compatible device. To inquire +about access about Android Market, you can contact us
diff --git a/pdk/docs/downloads/downloads_toc.cs b/pdk/docs/downloads/downloads_toc.cs deleted file mode 100644 index 28f43af75..000000000 --- a/pdk/docs/downloads/downloads_toc.cs +++ /dev/null @@ -1,21 +0,0 @@ - - --
-
This page provides access to various downloads. Note that if you're looking -for the Android SDK (for application developers), you should visit developer.android.com.
- -Compatibility
-The Compatibility Definition Document can be downloaded below. The -Compatibility Test Suite is available in the open-source tree.
-| Item | -File | -Size | -
|---|---|---|
| Android CDD 2.1 | -android-cdd-2.1.pdf | -23070805 bytes | -
| Android CTS 2.1 Manual | -android-cts-manual-2.1.0.pdf | -23070805 bytes | -
| Android CDD 1.6 | -android-cdd-1.6.pdf | -23070805 bytes | -
| Android CTS 1.6 Manual | -android-cts-manual-1.6.4.pdf | -23070805 bytes | -
For more information on how to build an Android-compatible device, see the -Compatibility page. Note that -there is no compatibility program for Android 1.5 and earlier. Note also that -there is no compatibility program for Android 2.0, since it was superceded by -Android 2.1 after only a few weeks. -
diff --git a/pdk/docs/faqs.jd b/pdk/docs/faqs.jd index a55d380fe..2506f0855 100644 --- a/pdk/docs/faqs.jd +++ b/pdk/docs/faqs.jd @@ -74,8 +74,8 @@ benefit.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.
-You can find more information on this topic at our Branches Releases - page.
+You can find more information on this topic at our Branches and Releases page.
Why are parts of Android developed in private?
It typically takes over a year to bring a device to market, but of course @@ -143,8 +143,7 @@ benefit.
"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 - Compatibility Program -- may call themselves "Android" and participate in - the Android ecosystem. + Compatibility Program -- may participate in the Android ecosystem.How can I contribute to Android?
There are a number of ways you can contribute to Android. You can report @@ -170,8 +169,9 @@ benefit.
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.
-You can find more information on this topic at the Submitting Patches - page.
+You can find more information on this topic at the Submitting Patches + page.
Compatibility
What does "compatibility" mean?
@@ -185,7 +185,7 @@ benefit.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 - ecosystem, and irrelevant to developers.
+ ecosystem.What is the role of Android Market in compatibility?
Devices that are Android compatible may seek to license the Android Market @@ -200,11 +200,11 @@ benefit.
Compatibility Definition Document (CDD) spells out the specific device configurations that will be considered compatible.For example, though the Android source code could be ported to run on a - device that doesn't have a camera, the CDD requires that in order to be - compatible, all devices must have a camera. This allows developers to rely - on a consistent set of device capabilities when writing their apps.
+ 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.The CDD will evolve over time to reflect market realities. For instance, - the 1.6 CDD only allows cell phones, but the 2.x CDD allows devices to omit + 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 augment Android Market to allow developers to retain control over where @@ -271,12 +271,15 @@ benefit.
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 - system user interface for the few areas that do impact third-party apps. + system user interface for areas that do impact third-party apps.When are compatibility definitions released for new Android versions?
Our goal is to release new versions of Android Compatibility Definition Documents (CDDs) once the corresponding Android platform version has - converged enough to permit it. Since the CDDs
+ converged enough to permit it. While we can't release a final draft of a CDD + for an Android software version before the first flagship device ships with + that software, final CDDs will always be released after the first device. + However, wherever practical we will make draft versions of CDDs available.How are device manufacturers' compatibility claims validated?
There is no validation process for Android device compatibility. However, diff --git a/pdk/docs/index.jd b/pdk/docs/index.jd index 217877dfe..76f48da31 100644 --- a/pdk/docs/index.jd +++ b/pdk/docs/index.jd @@ -1,7 +1,19 @@ page.title=Welcome to Android home=true @jd:body -
News
+Introducing the Compatibility Program
+We're pleased to introduce the Android Compatibility Program. We've released
+two tools -- the Compatibility Definition Document and the Compatibility Test
+Suite -- to help device manufacturers build compatible devices.
Site redesign
+You're looking at the new and improved source.android.com! We've updated
+the layout and site design, and also added new information. We hope you find
+these improvements helpful.
+Here you can find the information and source code you need to build an Android-compatible device.
Android is an open-source software stack for mobile devices, and a @@ -12,51 +24,40 @@ home=true created Android, and made its source code open.
News
-Site redesign
-You're looking at the new and improved source.android.com! We've updated
-the layout and site design, and also added new information. We hope you find
-these improvements helpful.
Introducing the Compatibility Program
-We're pleased to introduce the Android Compatibility Program. We've released
-two tools -- the Compatibility Definition Document and the Compatibility Test
-Suite -- to help device manufacturers build compatible devices. Full details
-of the Compatibility Program will be available in the first quarter of 2010.
|
-
Get Involved+Source
-
-
Build a Device+Porting
-
Compatibility
-
|
+ The information on this page is a bit out of date. We'll update this page as soon as we can.
-To build donut or master for dream (your +a matching official image.
To build donut for dream (your device needs to be an ADP1 running an official 1.6 system):
Note: these instructions work for the sapphire (ADP2) build target, as +well. Simply replace "dream" with "sapphire" above.
As a result, Google frequently has possession of confidential -information of third parties, and we must refrain from revealing patentable +information of third parties, and we must refrain from revealing sensitive features until we've secured the appropriate protections. Meanwhile, there are real risks to the platform arising from having too many platform versions extant at once. For these reasons, we have structured the open-source project diff --git a/pdk/docs/source/index.jd b/pdk/docs/source/index.jd index 230a0b35f..9dbd971a0 100644 --- a/pdk/docs/source/index.jd +++ b/pdk/docs/source/index.jd @@ -3,7 +3,7 @@ doc.type=source @jd:body
Thanks for your interest in Android! Here are some ways you can get involved -and help Google improve Android. For background on the Android project and our +and help us improve Android. For background on the Android project and our goals, check out the Project Philosophy page.
@@ -11,7 +11,7 @@ Philosophy page.One of the easiest and most effective ways you can help improve Android is to file bugs. For more information, visit the Reporting Bugs page.
-Please note that we can't guarantee that any particular bug can be fixed in +
Please note that we can't guarantee that any particular bug will be fixed in any particular release. To see what happens to your bug once you report it, read Life of a Bug.
@@ -27,7 +27,7 @@ compatible Android devices, using the SDK.Contribute to the Code
Code is King. We'd love to review any changes you submit, so please check out the source, pick a bug or feature, and get coding.
-You can get started with by learning about the You can get started with Android by learning about the Life of a Patch, and by
learning about The Android Open Source Project uses a few open source initiative approved open
-source licenses to enable availability of source code and to accept
-contributions from individuals and corporations.git, repo, and other tools using the
links to the left. If you need help along the way, you can join our
Android Open Source Project license
-The preferred license for the Android Open Source Project is Apache 2.0. Apache 2.0 -is a commercial and open source friendly open source license. The majority of -the Android platform is licensed under the Apache 2.0 license. While the -project will strive to adhere to the preferred license, there may be -exceptions which will be handled on a case-by-case basis. For example, the -Linux kernel patches are under the GPLv2 license with system exceptions, which -can be found on The preferred license for the Android Open Source Project is the Apache Software License, +2.0 ("Apache 2.0"), and the majority of the Android software is licensed +with Apache 2.0. While the project will strive to adhere to the preferred +license, there may be exceptions which will be handled on a case-by-case +basis. For example, the Linux kernel patches are under the GPLv2 license with +system exceptions, which can be found on kernel.org.
Contributor License Grants
@@ -25,15 +22,15 @@ Source Project will be required to complete, sign, and submit an Individual Contributor License Grant. The grant can be executed online through the code review -tool. The agreement clearly defines the terms under which intellectual -property has been contributed to the Android Open Source Project.This license +tool. The grant clearly defines the terms under which intellectual +property has been contributed to the Android Open Source Project. This license is for your protection as a contributor as well as the protection of the project; it does not change your rights to use your own contributions for any other purpose.For a corporation (or other entity) that has assigned employees to work on the Android Open Source Project, a Corporate -Contributor License Grant is available. This version of the Grant allows a +Contributor License Grant is available. This version of the grant allows a corporation to authorize contributions submitted by its designated employees and to grant copyright and patent licenses. Note that a Corporate Contributor License Grant does not remove the need for any developer to sign their own diff --git a/pdk/docs/source/life-of-a-bug.jd b/pdk/docs/source/life-of-a-bug.jd index 1d58ae1d9..5d77f7a16 100644 --- a/pdk/docs/source/life-of-a-bug.jd +++ b/pdk/docs/source/life-of-a-bug.jd @@ -57,7 +57,7 @@ might have been reported via an internal bug-tracking system, which is considered the "master" copy. (For instance, Google maintains one such private issue tracker, intended primarily for bugs which contain sensitive information which can't be revealed publicly.)
-Typically, a given bug will start in Unassigned, where it
@@ -77,8 +77,8 @@ determined to not require any action.