diff --git a/docs/html/sdk/1.5_r1/index.jd b/docs/html/sdk/1.5_r1/index.jd index 345489ad74806..412887a95257d 100644 --- a/docs/html/sdk/1.5_r1/index.jd +++ b/docs/html/sdk/1.5_r1/index.jd @@ -1,21 +1,20 @@ -page.title=Android 1.5 SDK, Release 1 - -sdk.version=1.5_r1 +sdk.version=1.5 +sdk.rel.id=1 sdk.date=April 2009 -sdk.win_download=android-sdk-windows-1.5_r1.zip +sdk.win_download= sdk.win_bytes= sdk.win_checksum= -sdk.mac_download=android-sdk-mac_x86-1.5_r1.zip +sdk.mac_download= sdk.mac_bytes= sdk.mac_checksum= -sdk.linux_download=android-sdk-linux_x86-1.5_r1.zip +sdk.linux_download= sdk.linux_bytes= sdk.linux_checksum= - +page.title=Download Android SDK @jd:body
The SDK includes a variety of tools for developing and debugging application code and designing an application UI. You can read about the tools in the
Dev Guide and access them in the <sdk>/tools/ directory.
-
The tools package included in this SDK is the same as that included in the Android 1.0, Release 2 SDK.
+The tools package included in this SDK includes many updates from that provided in the previous SDK and requires you to migrate your applications to the new development environment. For details, see the Upgrading the SDK document.
You can look at a variety of tutorials and samples in the Dev Guide and access the sample code itself
-in the <sdk>/samples/ directory of the SDK package.
<sdk>/platforms/android-1.5/samples/ directory of the SDK package. Note the new location — the SDK now includes multiple platform versions that you can develop against and each has its own sample code directory.
+
diff --git a/docs/html/sdk/1.5_r1/installing.jd b/docs/html/sdk/1.5_r1/installing.jd
index df9ec3aee89b5..a1f7cffb0576e 100644
--- a/docs/html/sdk/1.5_r1/installing.jd
+++ b/docs/html/sdk/1.5_r1/installing.jd
@@ -1,312 +1,10 @@
-page.title=Installing the Android SDK
-sdk.version=1.5_r1
+sdk.version=1.5
+sdk.rel.id=1
+sdk.date=April 2009
+page.title=Installing the Android SDK
@jd:body
-
-This page describes how to install the Android SDK and set up your -development environment. If you haven't downloaded the SDK, you can -do so from the -Download page.
- -If you encounter any problems during installation, see the -Installation Notes at the bottom of -this page.
- -If you have already developed applications using an earlier version -of the SDK, please skip this page and read the -Upgrading the -SDK document instead. -
- - -Before you get started with the Android SDK, take a moment to confirm -that your development machine meets the system requirements. -
- -If you will be developing on Eclipse with the Android Development -Tools (ADT) Plugin — the recommended path if you are new to -Android — make sure that you have a suitable version of Eclipse -installed on your computer. If you need to install Eclipse, you can -download it from this location:
- -http://www.eclipse.org/downloads/
- -A Java or RCP version of Eclipse is recommended.
- -After downloading the SDK, unpack the .zip archive to a suitable location on your machine. By default, the SDK files are unpacked into a directory named android_sdk_<platform>_<release>_<build>. The directory contains a link to a local copy of the documentation and the subdirectories tools/, samples/, and others.
Make a note of the name and location of the unpacked SDK directory on your system — you will need to refer to the SDK directory later, when setting up the Android plugin or using SDK tools.
- -Optionally, you can add the path to the SDK tools directory to your path. As mentioned above, the tools/ directory is located in the SDK directory.
tools/ directory to it. If you don't
- see a line setting the path, you can add one:export PATH=${PATH}:<your_sdk_dir>/toolstools/ directory to the path. Adding tools to your path lets you run Android Debug Bridge (adb) and the other command line tools without needing to supply the full path to the tools directory. Note that, if you update your SDK, you should remember to update your PATH settings to point to the new location, if different.
If you will be using the Eclipse IDE as your environment for developing Android applications, continue reading the next -section in order to install the Android Development Tools plugin and set up Eclipse. If you choose not to use Eclipse, you can -develop Android applications using other tools — read the guide to developing -in other IDEs.
- - -Android offers a custom plugin for the Eclipse IDE, called Android -Development Tools (ADT), that is designed to give you a powerful, -integrated environment in which to build Android applications. It -extends the capabilites of Eclipse to let you quickly set up new Android -projects, create an application UI, add components based on the Android -Framework API, and debug using the Android SDK tools.
- -If you are new to Android or want to develop using the Eclipse IDE, -the ADT plugin will be an essential part of your development -environment. In general, using Eclipse with ADT is a highly recommended -approach and is the fastest way to get started. This section describes -how to install ADT into your Eclipse environment. - -
If you prefer to work in a development environment other than Eclipse, -you do not need to install Eclipse or the ADT Plugin. Instead, you can -access the SDK tools directly to build and debug your application.
- -Once you have Eclipse installed, as described in -Preparing for Installation, follow the steps below to -download the ADT plugin and install it in your respective Eclipse -environment.
- -| Eclipse 3.3 (Europa) | Eclipse 3.4 (Ganymede) |
|---|---|
-
|
-
-
-
|
-
Now, you just need to modify your Eclipse preferences to point to the Android SDK directory:
-Done! If you haven't encountered any problems, then you're ready to -begin developing Android applications. See the After -Installation: Next Steps section for suggestions on how to start.
- - --If you are having trouble downloading the ADT plugin after following the steps above, here are some suggestions:
- -http://dl-ssl.google.com/android/eclipse/
-If you are still unable to use Eclipse to download the ADT plugin as a remote update site, you can download the ADT files to your local machine using a browser and the install the files in Eclipse from there: -
--Note that to update your plugin, you will have to follow these steps again instead of the default update instructions.
- -Note that the "Android Editors" feature of ADT requires several optional -Eclipse components (for example, WST). If you encounter an error when -installing ADT, your Eclipse installion might not include those components. -For information about how to quickly add the necessary components to your -Eclipse installation, see the troubleshooting topic -ADT Installation Error: "requires plug-in org.eclipse.wst.sse.ui".
- -If you encounter this error when installing the ADT Plugin for Eclipse: -
-An error occurred during provisioning. -Cannot connect to keystore. -JKS-
-...then your development machine lacks a suitable Java VM. Installing Sun -Java 6 will resolve this issue and you can then reinstall the ADT -Plugin.
- - -Once you have installed the SDK and the ADT Plugin, you are ready to -begin developing applications. Here are a few ways you can get started:
- -Learn about Android
-Explore the SDK
-Explore some code
-<sdk>/samples, then compile and run it in
-your development environmentVisit the Android developer groups
-ia32-libs package using
-apt-get::
- apt-get install ia32-libs
apt-get install sun-java6-bin
See the Download page for more information.
diff --git a/docs/html/sdk/1.5_r1/requirements.jd b/docs/html/sdk/1.5_r1/requirements.jd index 3f0deca92210e..c3ee8f7eac44f 100644 --- a/docs/html/sdk/1.5_r1/requirements.jd +++ b/docs/html/sdk/1.5_r1/requirements.jd @@ -1,11 +1,7 @@ page.title=System Requirements - -sdk.version=1.5_r1 -sdk.date=April 2009 - @jd:body -The sections below describe the system and software requirements for developing Android applications using the Android SDK tools included in Android 1.5 SDK, Release 1.
+The sections below describe the system and software requirements for developing Android applications using the Android SDK tools included in Android SDK, Release .
This document describes how to move your development environment and existing -Android applications from an Android 1.0 SDK to the Android 1.5, Release 1 SDK. + +
See the Download page for more information.
+ + +android-1.5.html#api-changes Android 1.5 Version Notes - + document.If you have additional trouble updating your code, visit the @@ -148,4 +173,4 @@ preinstalled in the emulator. For more information, or if you encounter an "rein error when running or installing ApiDemos, see the troubleshooting topic I can't install ApiDemos apps in my IDE because of a signing error for information about how to solve the problem.
- +--> \ No newline at end of file diff --git a/docs/html/sdk/android-1.5.jd b/docs/html/sdk/android-1.5.jd index 55fc4ba6d3b07..fff911e29096c 100644 --- a/docs/html/sdk/android-1.5.jd +++ b/docs/html/sdk/android-1.5.jd @@ -8,238 +8,7 @@ sys.date=April 2009 API Level: 3 -This document provides version notes for the Android 1.5 system image included in the SDK.
- -The Android 1.5 system image delivered in the SDK is the development -counterpart to the Android 1.5 production system image, deployable to -Android-powered handsets starting in February 2009.
- -The Android 1.5 system image delivers an updated version of the framework -API. As with previous versions, the Android 1.5 API -is assigned an integer identifier — 3 — that is -stored in the system itself. This identifier, called the "API Level", allows the -system to correctly determine whether an application is compatible with -the system, prior to installing the application.
- -Applications can reference a specific API Level value in their
-manifest files, to indicate the minimum version of the Android system
-required to run the application. To reference a minimum API Level, applications
-can add a minSdkVersion attribute in their manifest files.
-The value of the attribute is an integer corresponding to an API Level
-identifier. Prior to installing an application, the system then checks the value of
-minSdkVersion and allows the install only
-if the referenced integer is less than or equal to the API Level integer stored
-in the system itself.
If you use the Android 1.5 system image to build an application
-compatible with Android-powered devices running the Android 1.5
-platform, please note that you must set the the
-android:minSdkVersion attribute in the application's
-manifest to "3", which is the API strictly associated with Android 1.5.
-
Specifically, you define the android:minSdkVersion
-attribute in a <uses-sdk> element as a child of
-<manifest> in the manifest file. When set, the
-attribute looks like this:
<manifest> - ... - <uses-sdk minSdkVersion="3" /> - ... -</manifest>- -
By setting android:minSdkVersion in this way, you ensure
-that users will only be able to install your application if their
-devices are running the Android 1.5 platform. In turn, this ensures that
-your application will function properly on their devices, especially if
-it uses APIs introduced in Android 1.5.
If your application uses APIs introduced in Android 1.5 but does not
-declare <uses-sdk minSdkVersion="3" />, then it will
-run properly on Android 1.5 devices but not on Android 1.0
-devices. In the latter case, the application will crash at runtime when
-it tries to use the Android 1.5 APIs.
If your application does not use any new APIs introduced in Android
-1.5, you can indicate general Android 1.0 compatibility by removing
-minSdkVersion or setting the attribute to "1". However,
-before publishing your application, you must make sure to compile your
-application against the Android 1.0 system image (available in the
-Android SDK), to ensure that it builds and functions properly for
-Android 1.0 devices. You should test the application against system
-images corresponding to the API Levels that the application is designed
-to be compatible with.
If you are sure your application is not using Android 1.5 APIs and -has no need to use them, you might find it easier to keep working in the -Android 1.1 SDK, rather than migrating to the Android 1.5 SDK and having -to do additional testing.
- - -The system image includes these external libraries, which you can -access from your application by adding a -<uses-library>.
-The Android 1.5 system image was tested for compatability with the -Android-powered devices listed below:
-The system image includes these built-in applications:
-The system image provides localized UI strings for the languages -listed below.
-Localized UI strings match the locales that are displayable in -the emulator, accessible through the device Settings application.
- -| Module or Feature | Change Description | -
|---|---|
| Annotations for test systems | |
| Added {@link android.test.suitebuilder.annotation.LargeTest LargeTest} annotation. | |
| Added {@link android.test.suitebuilder.annotation.MediumTest MediumTest} annotation. | |
| Added {@link android.test.suitebuilder.annotation.SmallTest SmallTest} annotation. | |
| Allow a process to easily know its UID. | |
| Added public method {@link android.os.Process#myUid} to class {@link android.os.Process android.os.Process} | |
| Padding in views | |
| Added public method {@link android.view.View#getBottomPaddingOffset} to class {@link android.view.View android.view.View}. | |
| Added public method {@link android.view.View#getLeftPaddingOffset} to class {@link android.view.View android.view.View}. | |
| Added public method {@link android.view.View#getRightPaddingOffset} to class {@link android.view.View android.view.View}. | |
| Added public method {@link android.view.View#getTopPaddingOffset} to class {@link android.view.View android.view.View}. | |
| Added public method {@link android.view.View#isPaddingOffsetRequired} to class {@link android.view.View android.view.View}. | |
| Marquee support | |
| Added public method {@link android.widget.TextView#setMarqueeRepeatLimit} to class {@link android.widget.TextView} | |
| Added public field {@link android.R.attr#marqueeRepeatLimit android.R.attr.marqueeRepeatLimit} | |
| New permissions | |
| Added public field {@link android.Manifest.permission#BROADCAST_SMS android.Manifest.permission.BROADCAST_SMS} | |
| Added public field {@link android.Manifest.permission#BROADCAST_WAP_PUSH android.Manifest.permission.BROADCAST_WAP_PUSH} | |
| API cleanup | |
| Removed protected constructor java.net.ServerSocket.ServerSocket(java.net.SocketImpl). |
Please see Download the Android 1.5 Early Look SDK for more information.
diff --git a/docs/html/sdk/terms.jd b/docs/html/sdk/terms.jd index 4638850421a29..b3c5ea253cc46 100644 --- a/docs/html/sdk/terms.jd +++ b/docs/html/sdk/terms.jd @@ -8,7 +8,8 @@ hide_license_footer=true 1. Introduction- 1.1 The Android Software Development Kit (referred to in this License Agreement as the "SDK" and specifically including the Android system files and packaged APIs) is licensed to you subject to the terms of this License Agreement. This License Agreement forms a legally binding contract between you and Google in relation to your use of the SDK. + 1.1 The Android Software Development Kit (referred to in this License Agreement as the "SDK" and specifically including the Android system files, packaged APIs, and Google Services add-ons) is licensed to you subject to the terms of this License Agreement. This License Agreement forms a legally binding contract between you and Google in relation to your use of the SDK. +
1.2 "Google" means Google Inc., a Delaware corporation with principal place of business at 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States. @@ -41,10 +42,11 @@ hide_license_footer=true 3.1 Subject to the terms of this License Agreement, Google grants you a limited, worldwide, royalty-free, non- assignable and non-exclusive license to use the SDK solely to develop applications to run on the Android platform.
- 3.2 You agree that Google or third parties own all legal right, title and interest in and to the SDK, including any Intellectual Property Rights that subsist in the SDK. "Intellectual Property Rights" means any and all rights under patent law, copyright law, trade secret law, trademark law, and any and all other proprietary rights. The Android Open Source Project + 3.2 You agree that Google or third parties own all legal right, title and interest in and to the SDK, including any Intellectual Property Rights that subsist in the SDK. "Intellectual Property Rights" means any and all rights under patent law, copyright law, trade secret law, trademark law, and any and all other proprietary rights. Google reserves all rights not expressly granted to you. +
- 3.3 Except to the extent required by applicable third party licenses, you may not copy (except for backup purposes), modify, adapt, redistribute, decompile, reverse engineer, disassemble, or create derivative works of the SDK or any part of the SDK. Except to the extent required by applicable third party licenses, you may not load any part of the SDK onto a mobile handset or any other hardware device except a personal computer, combine any part of the SDK with other software, or distribute any software or device incorporating a part of the SDK. + 3.3. Except to the extent required by applicable third party licenses, you may not copy (except for backup purposes), modify, adapt, redistribute, decompile, reverse engineer, disassemble, or create derivative works of the SDK or any part of the SDK. Except to the extent required by applicable third party licenses, you may not load any part of the SDK onto a mobile handset or any other hardware device except a personal computer, combine any part of the SDK with other software, or distribute any software or device incorporating a part of the SDK.
3.4 Use, reproduction and distribution of components of the SDK licensed under an open source software license are governed solely by the terms of that open source software license and not this License Agreement. @@ -62,7 +64,7 @@ hide_license_footer=true 4. Use of the SDK by You
- 4.1 Google agrees that it obtains no right, title or interest from you (or your licensors) under this License Agreement in or to any software applications that you develop using the SDK, including any intellectual property rights which subsist in those applications. + 4.1 Google agrees that it obtains no right, title or interest from you (or your licensors) under this License Agreement in or to any software applications that you develop using the SDK, including any intellectual property rights that subsist in those applications.
4.2 You agree to use the SDK and write applications only for purposes that are permitted by (a) this License Agreement and (b) any applicable law, regulation or generally accepted practices or guidelines in the relevant jurisdictions (including any laws regarding the export of data or software to and from the United States or other relevant countries). @@ -110,25 +112,14 @@ hide_license_footer=true 8. Using Android APIs
- 8.1 Android Maps API + 8.1 Google Data APIs
- 8.1.1 If you use the Android Maps API (described in the SDK by the Package names "com.google.android.maps" and "com.android.location.Geocoder"), the terms of your binding legal agreement with Google include this License Agreement, the Google Maps API Terms of Service and the Google Maps Terms of Service. You must read and agree to those Terms of Service before you use the Android Maps API. + 8.1.1 If you use any API to retrieve data from Google, you acknowledge that the data may be protected by intellectual property rights which are owned by Google or those parties that provide the data (or by other persons or companies on their behalf). Your use of any such API may be subject to additional Terms of Service. You may not modify, rent, lease, loan, sell, distribute or create derivative works based on this data (either in whole or in part) unless allowed by the relevant Terms of Service.
- 8.1.2 If you use the Android Maps API to retrieve map or satellite image data from Google, you must include the following copyright notice in your application or service in a manner that is reasonably available to users: -
-- "Copyright Notice: Data: (c)2007 TeleAtlas, AND, Europa Technologies, Kingway, Map Data Sciences Pty Ltd, PSMA, ZENRIN, Geocentre, MapLink/TeleAtlas; Imagery: (c)2007 DigitalGlobe, EarthSat, Sanborn, NYGIS, Scankort, TerraMetrics, MassGIS Commonwealth of Massachusetts, Digital Earth Technology." -
-- 8.2 Google Data APIs -
-- 8.2.1 If you use any API to retrieve data from Google, you acknowledge that the data may be protected by intellectual property rights which are owned by those who provide that data (or by other persons or companies on their behalf). You may not modify, rent, lease, loan, sell, distribute or create derivative works based on this data (either in whole or in part) unless you have been specifically given permission to do so by the owners of that data. -
-- 8.2.2 If you use any API to retrieve a user's data from Google, you acknowledge and agree that you shall retrieve data only with the user's explicit consent and only when, and for the limited purposes for which, the user has given you permission to do so. + 8.1.2 If you use any API to retrieve a user's data from Google, you acknowledge and agree that you shall retrieve data only with the user's explicit consent and only when, and for the limited purposes for which, the user has given you permission to do so. +
- 13.1 Google may make changes to the License Agreement as it distributes new versions of the SDK. When these changes are made, Google will make a new version of the License Agreement available on the website where the SDK is made available and with the SDK downloadable. -
-- 13.2 You agree that your use of a specific version of the SDK is governed by the License Agreement included with that version of the SDK. + 13.1 Google may make changes to the License Agreement as it distributes new versions of the SDK. When these changes are made, Google will make a new version of the License Agreement available on the website where the SDK is made available.
- August 18, 2008 + April 10, 2009
diff --git a/docs/html/sdk/terms_body.html b/docs/html/sdk/terms_body.html index e8fdc3cff7619..a73801f06f86c 100644 --- a/docs/html/sdk/terms_body.html +++ b/docs/html/sdk/terms_body.html @@ -5,7 +5,8 @@ 1. Introduction- 1.1 The Android Software Development Kit (referred to in this License Agreement as the "SDK" and specifically including the Android system files and packaged APIs) is licensed to you subject to the terms of this License Agreement. This License Agreement forms a legally binding contract between you and Google in relation to your use of the SDK. + 1.1 The Android Software Development Kit (referred to in this License Agreement as the "SDK" and specifically including the Android system files, packaged APIs, and Google Services add-ons) is licensed to you subject to the terms of this License Agreement. This License Agreement forms a legally binding contract between you and Google in relation to your use of the SDK. +
1.2 "Google" means Google Inc., a Delaware corporation with principal place of business at 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States. @@ -38,10 +39,11 @@ 3.1 Subject to the terms of this License Agreement, Google grants you a limited, worldwide, royalty-free, non- assignable and non-exclusive license to use the SDK solely to develop applications to run on the Android platform.
- 3.2 You agree that Google or third parties own all legal right, title and interest in and to the SDK, including any Intellectual Property Rights that subsist in the SDK. "Intellectual Property Rights" means any and all rights under patent law, copyright law, trade secret law, trademark law, and any and all other proprietary rights. The Android Open Source Project + 3.2 You agree that Google or third parties own all legal right, title and interest in and to the SDK, including any Intellectual Property Rights that subsist in the SDK. "Intellectual Property Rights" means any and all rights under patent law, copyright law, trade secret law, trademark law, and any and all other proprietary rights. Google reserves all rights not expressly granted to you. +
- 3.3 Except to the extent required by applicable third party licenses, you may not copy (except for backup purposes), modify, adapt, redistribute, decompile, reverse engineer, disassemble, or create derivative works of the SDK or any part of the SDK. Except to the extent required by applicable third party licenses, you may not load any part of the SDK onto a mobile handset or any other hardware device except a personal computer, combine any part of the SDK with other software, or distribute any software or device incorporating a part of the SDK. + 3.3. Except to the extent required by applicable third party licenses, you may not copy (except for backup purposes), modify, adapt, redistribute, decompile, reverse engineer, disassemble, or create derivative works of the SDK or any part of the SDK. Except to the extent required by applicable third party licenses, you may not load any part of the SDK onto a mobile handset or any other hardware device except a personal computer, combine any part of the SDK with other software, or distribute any software or device incorporating a part of the SDK.
3.4 Use, reproduction and distribution of components of the SDK licensed under an open source software license are governed solely by the terms of that open source software license and not this License Agreement. @@ -59,7 +61,7 @@ 4. Use of the SDK by You
- 4.1 Google agrees that it obtains no right, title or interest from you (or your licensors) under this License Agreement in or to any software applications that you develop using the SDK, including any intellectual property rights which subsist in those applications. + 4.1 Google agrees that it obtains no right, title or interest from you (or your licensors) under this License Agreement in or to any software applications that you develop using the SDK, including any intellectual property rights that subsist in those applications.
4.2 You agree to use the SDK and write applications only for purposes that are permitted by (a) this License Agreement and (b) any applicable law, regulation or generally accepted practices or guidelines in the relevant jurisdictions (including any laws regarding the export of data or software to and from the United States or other relevant countries). @@ -107,25 +109,14 @@ 8. Using Android APIs
- 8.1 Android Maps API + 8.1 Google Data APIs
- 8.1.1 If you use the Android Maps API (described in the SDK by the Package names "com.google.android.maps" and "com.android.location.Geocoder"), the terms of your binding legal agreement with Google include this License Agreement, the Google Maps API Terms of Service and the Google Maps Terms of Service. You must read and agree to those Terms of Service before you use the Android Maps API. + 8.1.1 If you use any API to retrieve data from Google, you acknowledge that the data may be protected by intellectual property rights which are owned by Google or those parties that provide the data (or by other persons or companies on their behalf). Your use of any such API may be subject to additional Terms of Service. You may not modify, rent, lease, loan, sell, distribute or create derivative works based on this data (either in whole or in part) unless allowed by the relevant Terms of Service.
- 8.1.2 If you use the Android Maps API to retrieve map or satellite image data from Google, you must include the following copyright notice in your application or service in a manner that is reasonably available to users: -
-- "Copyright Notice: Data: (c)2007 TeleAtlas, AND, Europa Technologies, Kingway, Map Data Sciences Pty Ltd, PSMA, ZENRIN, Geocentre, MapLink/TeleAtlas; Imagery: (c)2007 DigitalGlobe, EarthSat, Sanborn, NYGIS, Scankort, TerraMetrics, MassGIS Commonwealth of Massachusetts, Digital Earth Technology." -
-- 8.2 Google Data APIs -
-- 8.2.1 If you use any API to retrieve data from Google, you acknowledge that the data may be protected by intellectual property rights which are owned by those who provide that data (or by other persons or companies on their behalf). You may not modify, rent, lease, loan, sell, distribute or create derivative works based on this data (either in whole or in part) unless you have been specifically given permission to do so by the owners of that data. -
-- 8.2.2 If you use any API to retrieve a user's data from Google, you acknowledge and agree that you shall retrieve data only with the user's explicit consent and only when, and for the limited purposes for which, the user has given you permission to do so. + 8.1.2 If you use any API to retrieve a user's data from Google, you acknowledge and agree that you shall retrieve data only with the user's explicit consent and only when, and for the limited purposes for which, the user has given you permission to do so. +
- 13.1 Google may make changes to the License Agreement as it distributes new versions of the SDK. When these changes are made, Google will make a new version of the License Agreement available on the website where the SDK is made available and with the SDK downloadable. -
-- 13.2 You agree that your use of a specific version of the SDK is governed by the License Agreement included with that version of the SDK. + 13.1 Google may make changes to the License Agreement as it distributes new versions of the SDK. When these changes are made, Google will make a new version of the License Agreement available on the website where the SDK is made available.
- August 18, 2008 -
+ April 10, 2009 + \ No newline at end of file