diff options
| author | Scott Main <smain@google.com> | 2011-01-26 16:23:37 -0800 |
|---|---|---|
| committer | Scott Main <smain@google.com> | 2011-01-26 17:42:49 -0800 |
| commit | 9e6c0686be3e36d70bf2f687bdf4d477e70e6ee3 (patch) | |
| tree | 8713cc2c26e8594475a675fe40cb0cf234a3558b /docs/html | |
| parent | 1d07b5bc9b0a9e3de4495834242548a600cae1d8 (diff) | |
| download | frameworks_base-9e6c0686be3e36d70bf2f687bdf4d477e70e6ee3.zip frameworks_base-9e6c0686be3e36d70bf2f687bdf4d477e70e6ee3.tar.gz frameworks_base-9e6c0686be3e36d70bf2f687bdf4d477e70e6ee3.tar.bz2 | |
catchup the gingerbread branch to gingerbread-docs for all sdk docs
This is just a manual copy of all files that changed, rather than a dozen cherry picks.
Change-Id: I672f74a2ec9242a1d96713d1d84bfc4d2d47dd85
Diffstat (limited to 'docs/html')
27 files changed, 910 insertions, 168 deletions
diff --git a/docs/html/sdk/android-3.0-highlights.jd b/docs/html/sdk/android-3.0-highlights.jd new file mode 100644 index 0000000..f48aed8 --- /dev/null +++ b/docs/html/sdk/android-3.0-highlights.jd @@ -0,0 +1,266 @@ +page.title=Android 3.0 Platform Highlights + +@jd:body + + +<style type="text/css"> +#jd-content { + max-width:1200px; +} +#jd-content div.screenshot { + float:left; + clear:left; + padding:15px 30px 15px 0; +} +#jd-content div.video { + float:right; + padding:0 60px 40px; + margin-top:-15px; +} +#jd-content table.columns { + margin:0 0 1em 0; +} +#jd-content table.columns td { + padding:0; +} +#jd-content table.columns td+td { + padding:0 2em; +} +#jd-content table.columns td img { + margin:0; +} +#jd-content table.columns td+td>*:first-child { + margin-top:-2em; +} +.green { + color:#8db529; + font-weight:bold; +} +</style> + + + + + + +<p>Welcome to Android 3.0!</p> + +<p>The Android 3.0 platform introduces many new and exciting features for users and developers. +This document provides a glimpse of some of the new features and technologies, as delivered in the Android 3.0 Preview SDK. For more information about the SDK or how to download it, please see the <a href="{@docRoot}sdk/preview/index.html">Preview SDK</a> document.</p> + +<ul> + <li><a href="#UserFeatures">New User Features</a></li> + <li><a href="#DeveloperApis">New Developer Features</a></li> +</ul> + +<h2 id="UserFeatures" style="clear:right">New User Features</h2> + +<div style="padding-top:0em;"> +<div style="margin-right:1em;margin-left:1em;float:right;padding-top:2em;"><a href="images/3.0/home_hero1_full.png" target="_android"><img src="images/3.0/home_hero1.png" alt="" height="280" /></a></div> + +<h3>New UI designed from the ground up for tablets</h3> + +<p>Android 3.0 is a new version of the Android platform that is specifically optimized for devices with larger screen sizes, particularly tablets. It introduces a brand new, truly virtual and “holographic” UI design, as well as an elegant, content-focused interaction model.</p> + +<p>Android 3.0 builds on the things people love most about Android — refined multitasking, rich notifications, Home screen customization, widgets, and more — and transforms them with a vibrant, 3D experience and deeper interactivity, making them familiar but even better than before.</p> + +<p>The new UI brings fresh paradigms for interaction, navigation, and customization and makes them available to all applications — even those built for earlier versions of the platform. Applications written for Android 3.0 are able to use an extended set of UI objects, powerful graphics, and media capabilities to engage users in new ways.</p> + +<p style="margin-top:1em;margin-bottom:.75em;"><strong>System Bar, for global status and notifications</strong></p> + +<p>Across the system and in all applications, users have quick access to notifications, system status, and soft navigation buttons in a System Bar, available at the bottom of the screen. The System Bar is always present and is a key touchpoint for users, but in a new "lights out mode" can also be dimmed for full-screen viewing, such as for videos.</p> + +<p style="margin-top:1em;margin-bottom:.75em;"><strong>Action Bar, for application control</strong></p> + +<p>In every application, users have access to contextual options, navigation, widgets, or other types of content in an Action Bar, displayed at the top of the screen. The Action Bar is always present when an application is in use, although its content, theme, and other properties are managed by the application rather than the system. The Action Bar is another key touchpoint for users, especially with action items and an overflow dropdown menu, which users frequently access in a similar manner in most applications. </p> + +</div> + +<div style="padding-top:0em;"> +<div style="margin-right:1em;float:right;margin-left:1em;"><a href="images/3.0/homescreen_cust_port_full.png" target="_android"><img src="images/3.0/homescreen_cust_port.png" alt="" height="280" /></a></div> + +<p style="margin-top:1em;margin-bottom:.75em;"><strong>Customizable Home screens</strong></p> + +<p>Five customizable Home screens give users instant access to all parts of the system from any context. Each screen offers a large grid that maintains spatial arrangement in all orientations. Users can select and manipulate Home screen widgets, app shortcuts, and wallpapers using a dedicated visual layout mode. Visual cues and drop shadows improve visibility when adjusting the layout of shortcuts and widgets. Each Home screen also offers a familiar launcher for access to all installed applications, as well as a Search box for universal search of apps, contacts, media files, web content, and more.</p> + +</div> + +<div style="padding-top:0em;"> +<div style="margin-right:1.5em;float:left;"><a href="images/3.0/tasks_full.png" target="_android"><img src="images/3.0/tasks.png" alt="" height="280" /></a> + +<!--<p style="font-size:90%">Figure</p> --></div> + +<p style="margin-top:1em;margin-bottom:.75em;"><strong>Recent Apps, for easy visual multitasking</strong></p> + +<p>Multitasking is a key strength of Android and it is central to the Android 3.0 experience. As users launch applications to handle various tasks, they can use the Recent Apps list in the System Bar to see the tasks underway and quickly jump from one application context to another. To help users rapidly identify the task associated with each app, the list shows a snapshot of its actual state when the user last viewed it.</p> + +</div> + + +<h3>Redesigned keyboard</h3> + +<p>The Android soft keyboard is redesigned to make entering text fast and accurate on larger screen sizes. The keys are reshaped and repositioned for improved targeting, and new keys have been added, such as a Tab key, to provide richer and more efficient text input. Users can touch-hold keys to access menus of special characters and switch text/voice input modes from a button in the System Bar.</p> + +<div style="padding-top:1em;"> +<div style="margin-right:1em;float:right;"><a href="images/3.0/copy_full.png" target="_android"><img src="images/3.0/copy.png" alt="" height="180" /></a></div> + + +<h3>Improved text selection, copy and paste</h3> + +<p>When entering or viewing text, a new UI lets users quickly select a word by press-hold and then adjust the selection area as needed by dragging a set of bounding arrows to new positions. Users can then select an action from the Action Bar, such as copy to the clipboard, share, paste, web search, or find. </p> + + +<h3>New connectivity options</h3> + +<p>Android 3.0 includes new connectivity features that add versatility and convenience for users. Built-in support for Media/Photo Transfer Protocol lets users instantly sync media files with a USB-connected camera or desktop computer, without needing to mount a USB mass-storage device. Users can also connect full keyboards over either USB or Bluetooth, for a familiar text-input environment. For improved wi-fi connectivity, a new combo scan reduces scan times across bands and filters. New support for Bluetooth tethering means that more types of devices can share the network connection of an Android-powered device.</p> + + +<h3>Updated set of standard apps</h3> + +<div style="padding-top:0em;"> +<div style="margin-right:1em;float:right;;padding-top:0em;margin-left:1em;"><a href="images/3.0/browser_full.png" target="_android"><img src="images/3.0/browser.png" alt="" height="200" /></a><br> +<a href="images/3.0/camera_full.png" target="_android"><img src="images/3.0/camera_full.png" alt="" height="200" /></a></div> + +<p>The Android 3.0 platform includes an updated set of standard applications that are designed for use on larger screen devices. The sections below highlight some of the new features. </p> + +<strong>Browser</strong></p> + +<p>The browser includes new features that let users navigate and organize more efficiently. Multiple tabs replace browser windows and a new “incognito” mode allows anonymous browsing. Bookmarks and history are presented and managed in a single unified view. Users can now choose to automatically sign into Google sites on the browser with a supplied account and sync bookmarks with Google Chrome. New multitouch support is now available to JavaScript and plugins. Users can enjoy a better browsing experience at non-mobile sites through an improved zoom and viewport model, overflow scrolling, support for fixed positioning, and more.</p> + +<p style="margin-top:1em;margin-bottom:.75em;"><strong>Camera and Gallery</strong></p> + +<p>The Camera application has been redesigned to take advantage of a larger screen for quick access to exposure, focus, flash, zoom, front-facing camera, and more. The Gallery application lets users view albums and other collections in full-screen mode, with easy access to thumbnails for other photos in the collection. </p> + +<p style="margin-top:1em;margin-bottom:.75em;"><strong>Contacts</strong></p> + +<p>The Contacts app uses a new two-pane UI and Fast Scroll to let users easily organize and locate contacts. The application offers improved formatting of international phone numbers as user types, based on home country and an international number parsing library. Contact information is presented in a card-like UI, making it easier for users to read and edit contacts.</p> + +<p style="margin-top:1em;margin-bottom:.75em;"><strong>Email</strong></p> + +<p>The Email application uses a new two-pane UI to make viewing and organizing messages more efficient. The app lets users select one or more messages, then select an action from the Action Bar, such as moving them to a folder. Users can sync attachments for later viewing and keep track of email using a home screen Widget.</p> + +</div> + + +<h2 id="DeveloperApis" style="clear:both">New Developer Features</h2> + +<p>The Android 3.0 platform is designed specially to meet the unique needs of applications on devices with larger screen sizes. It offers all of the tools developers need to create incredible visual and interaction experiences on these devices.</p> + + <ul> +<li><a href="#ui">New UI framework for creating great tablet apps</a></li> +<li><a href="#graphics">High-performance 2D and 3D graphics</a></li> +<li><a href="#multicore">Support for multicore processor architectures</a></li> +<li><a href="#multimedia">Rich multimedia and connectivity</a></li> +<li><a href="#enterprise">Enhancements for enterprise</a></li> +<li><a href="#compatibility">Compatibility with existing apps</a></li> +</ul> + +<h3 id="ui">New UI Framework for creating great tablet apps</h3> + +<div style="padding-top:0em;"> +<div style="margin-right:1em;float:right;margin-left:1em;"><a href="images/3.0/contacts_full.png" target="_android"><img src="images/3.0/contacts.png" alt="" height="200" /></a></div> + + +<p style="margin-top:.75em;margin-bottom:.75em;"><strong>Activity fragments, for greater control of content and design flexibility</strong></p> + +<p>Starting with Android 3.0, developers can break the Activities of their applications into subcomponents called Fragments, then combine them in a variety of ways to create a richer, more interactive experience. For example, an application can use a set of Fragments to create a true multipane UI, with the user being able to interact with each pane independently. Fragments can be added, removed, replaced, and animated inside an Activity dynamically, and they are modular and reusable across multiple Activities. Because they are modular, Fragments also offer an efficient way for developers to write applications that can run properly on both larger screen as well as smaller screen devices.</p> + +</div> + +<p style="margin-top:1.25em;margin-bottom:.75em;"><strong>Redesigned UI widgets</strong></p> + +<p>Android 3.0 offers an updated set of UI widgets that developers can use to quickly add new types of content to their applications. The new UI widgets are redesigned for use on larger screens such as tablets and incorporate the new holographic UI theme. Several new widget types are available, including a 3D stack, search box, a date/time picker, number picker, calendar, popup menu, and others. Most of the redesigned UI widgets can now be used as remote views in application widgets displayed on the home screen. Applications written for earlier versions can inherit the new Widget designs and themes.</p> + + +<div style="padding-top:0em;"> +<div style="margin-right:1.5em;float:left;margin-left:0em;"><a href="images/3.0/widgets.png" target="_android"><img src="images/3.0/widgets.png" alt="" height="200" target="_android" /></a></div> + +<p style="margin-top:1.25em;margin-bottom:.75em;"><strong>Expanded Home screen widgets</strong></p> + +<p>Home screen widgets are popular with users because they offer fast access to application-specific data directly from the home screen. Android 3.0 lets developers take home screen widgets to the next level, offering more types of content and new modes of interaction with users. Developers can now use more standard UI widget types home screen widgets, including widgets that let users flip through collections of content as 3D stacks, grids, or lists. Users can interact with the home screen widgets in new ways, such as by using touch gestures to scroll and flip the content displayed in a widget. </p> + +</div> + +<p style="margin-top:1.25em;margin-bottom:.75em;"><strong>Persistent Action Bar</strong></p> + +<p>The platform provides each application with its own instance of the Action Bar at the top of the screen, which the application can use to give the user quick access to contextual options, widgets, status, navigation, and more. The application can also customize the display theme of its Action Bar instance. The Action Bar lets developers expose more features of their applications to users in a familiar location, while also unifying the experience of using an application that spans multiple Activities or states.</p> + +<p style="margin-top:1.25em;margin-bottom:.75em;"><strong>Richer notifications</strong></p> + +<p>Notifications are a key part of the Android user experience because they let applications show key updates and status information to users in real time. Android 3.0 extends this capability, letting developers include richer content and control more properties. A new builder class lets developers quickly create notifications that include large and small icons, a title, a priority flag, and any properties already available in previous versions. Notifications can offer more types of content by building on the expanded set of UI Widgets that are now available as remote Views.</p> + +<div style="padding-top:0em;"> +<div style="margin-right:1em;float:right;margin-left:1em;"><a href="images/3.0/mail_drag_full.png" target="_android"><img src="images/3.0/mail_drag.png" alt="" height="200" style="padding-top:1em;"/></a></div> + +<p style="margin-top:1.25em;margin-bottom:.75em;"><strong>Multiselect, clipboard, and drag-and-drop</strong></p> + +<p>The platform offers convenient new interaction modes that developers can use. For managing collections of items in lists or grids, developers can offer a new multiselect mode that lets users choose multiple items for an action. Developers can also use a new system-wide Clipboard to let users easily copy any type of data into and out of their applications. To make it easier for users to manage and organize files, developers can now add drag-and-drop interaction through a DragEvent framework.</p> + +</div> + + +<h3 id="graphics">High-performance 2D and 3D graphics</h3> + +<p style="margin-top:.75em;margin-bottom:.75em;"><strong>New animation framework</strong></p> + +<p>The platform includes a flexible new animation framework that lets developers easily animate the properties of UI elements such as Views, Widgets, Fragments, Drawables, or any arbitrary object. Animations can create fades or movement between states, loop an animated image or an existing animation, change colors, and much more. Adding animation to UI elements can add visual interest to an application and refine the user experience, to keep users engaged.</p> + +<p style="margin-top:1.25em;margin-bottom:.75em;"><strong>Hardware-accelerated 2D graphics</strong></p> + +<p>Android 3.0 offers a new hardware-accelerated OpenGL renderer that gives a performance boost to many common graphics operations for applications running in the Android framework. When the renderer is enabled, most operations in Canvas, Paint, Xfermode, ColorFilter, Shader, and Camera are accelerated. Developers can control how hardware-acceleration is applied at every level, from enabling it globally in an application to enabling it in specific Activities and Views inside the application.</p> + +<p style="margin-top:1.25em;margin-bottom:.75em;"><strong>Renderscript 3D graphics engine</strong></p> + +<p>Renderscript is a runtime 3D framework that provides both an API for building 3D scenes as well as a special, platform-independent shader language for maximum performance. Using Renderscript, you can accelerate graphics operations and data processing. Renderscript is an ideal way to create high-performance 3D effects for applications, wallpapers, carousels, and more.</p> + + +<h3 id="multicore">Support for multicore processor architectures</h3> + +<p>Android 3.0 is the first version of the platform designed to run on either single or multicore processor architectures. A variety of changes in the Dalvik VM, Bionic library, and elsewhere add support for symmetric multiprocessing in multicore environments. These optimizations can benefit all applications, even those that are single-threaded. For example, with two active cores, a single-threaded application might still see a performance boost if the Dalvik garbage collector runs on the second core. The system will arrange for this automatically.</p> + + +<h3 id="multimedia">Rich multimedia and connectivity</h3> + +<p style="margin-top:.75em;margin-bottom:.75em;"><strong>HTTP Live streaming</strong></p> + +<p>Applications can now pass an M3U playlist URL to the media framework to begin an HTTP Live streaming session. The media framework supports most of the HTTP Live streaming specification, including adaptive bit rate.</p> + +<p style="margin-top:1.25em;margin-bottom:.75em;"><strong>Pluggable DRM framework</strong></p> + +<p>Android 3.0 includes an extensible DRM framework that lets applications manage protected content according to a variety of DRM mechanisms that may be available on the device. For application developers, the framework API offers an consistent, unified API that simplifies the management of protected content, regardless of the underlying DRM engines. </p> + +<p style="margin-top:1.25em;margin-bottom:.75em;"><strong>Digital media file transfer</strong></p> + +<p>The platform includes built-in support for Media/Picture Transfer Protocol (MTP/PTP) over USB, which lets users easily transfer any type of media files between devices and to a host computer. Developers can build on this support, creating applications that let users create or manage media files that they may want to transfer or share across devices. </p> + +<p style="margin-top:1.25em;margin-bottom:.75em;"><strong>More types of connectivity</strong></p> + +<p>The platform offers new connectivity that developers can build on. API support for Bluetooth A2DP and HSP profiles lets applications query Bluetooth profiles for connected devices, audio state, and more, then notify the user. For example, a music application can check connectivity and status and let the user know that music is playing through a stereo headset. Applications can also register to receive system broadcasts of pre-defined vendor-specific AT commands, such as Platronics Xevent. For example, an application could receive broadcasts that indicate a connected device's battery level and could notify the user or take other action as needed. Applications can also take advantage of the platform's new support for full keyboards connected by USB or Bluetooth. </p> + + +<h3 id="enterprise">Enhancements for enterprise</h3> + +<p>In Android 3.0, developers of device administration applications can support new types of policies, including policies for encrypted storage, password expiration, password history, and password complex characters required. </p> + +<h3 id="compatibility">Compatibility with existing apps</h3> + +<p>Android 3.0 brings a new UI designed for tablets and other larger screen devices, but it also is fully compatible with applications developed for earlier versions of the platform, or for smaller screen sizes. Existing applications can seamlessly participate in the new holographic UI theme without code changes, by adding a single attribute in their manifest files. The platform emulates the Menu key, which is replaced by the overflow menu in the Action Bar in the new UI. Developers wanting to take fuller advantage of larger screen sizes can also create dedicated layouts and assets for larger screens and add them to their existing applications.</p> + + +<h2>More information</h2> + +<div class="video"> +<object width="278" height="180"> +<param name="movie" value="http://www.youtube.com/v/hPUGNCIozp0?hl=en&fs=1"></param> +<param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" +value="always"></param> +<embed src="http://www.youtube.com/v/hPUGNCIozp0?hl=en&fs=1" type="application/x-shockwave-flash" +allowscriptaccess="always" allowfullscreen="true" width="278" height="180"></embed> +</object> +</div> + +<p>For more information about the new developer APIs, see the Android 3.0 Platform notes in the SDK Preview documentation, available by download through the Android SDK Manager.</p> + +<p>For a video overview of platform features, see the Android 3.0 Sneak Peek. </p> + + diff --git a/docs/html/sdk/eclipse-adt.jd b/docs/html/sdk/eclipse-adt.jd index 0d1ea0c..62e27d3 100644 --- a/docs/html/sdk/eclipse-adt.jd +++ b/docs/html/sdk/eclipse-adt.jd @@ -1,9 +1,8 @@ page.title=ADT Plugin for Eclipse -sdk.preview=0 -adt.zip.version=8.0.1 -adt.zip.download=ADT-8.0.1.zip -adt.zip.bytes=8724909 -adt.zip.checksum=0e62185279083ddc01f18098ce7ba2d1 +adt.zip.version=9.0.0 +adt.zip.download=ADT-9.0.0.zip +adt.zip.bytes=4433536 +adt.zip.checksum=bc2757f2a5a11d131390ce547bae154b @jd:body @@ -100,6 +99,115 @@ padding: .25em 1em; <a href="#" onclick="return toggleDiv(this)"> <img src="{@docRoot}assets/images/triangle-opened.png" class="toggle-img" height="9px" width="9px" /> +ADT 9.0.0</a> <em>(January 2011)</em> + <div class="toggleme"> + +<dl> + +<dt>Dependencies:</dt> + +<dd>ADT 9.0.0 is designed for use with SDK Tools r9. If you haven't +already installed SDK Tools r9 into your SDK, use the Android SDK and AVD Manager to do +so.</dd> + +<dt>General notes:</dt> +<dd> + <ul> + <li>"Go To Declaration" hyperlink support: You can jump directly from code references (such as + <code>R.id.main</code>) to the corresponding XML declaration, or from XML attributes (such as + <code>@string</code>) to the corresponding resource definition, or from manifest XML + registrations to activities and services.</li> + <li>Improvements were made to name refactoring.</li> + <li>AVDs now automatically save their state, so they can restart almost instantly. You can enable this feature when + creating an AVD or by editing an AVD with the AVD Manager.</li> + <li>Improvements to the Visual Layout Editor: + <ul> + <li>Support for rendering targets: You can now choose an arbitrary Android platform to + render the current page, regardless of the project's minimum platform. This makes it + easy to verify the layout and appearance of your activity on different versions of + the platform. + </li> + <li>Improved support for empty and nested layouts: Dragging items over nested and + invisible layouts automatically enlarges and highlights these layouts, so that they + can receive drops. + </li> + <li>XML formatting improvements: The editor generates cleaner XML and you can now enable + XML auto-formatting in the <strong>Preferences</strong> menu.</li> + <li>Improved Outline labels: The Outline tab now displays additional information about each + View. Textual Views display a snippet of the actual text. Views with a source + (such as ImageView) displays the resource name. Included Views display the name of the View. + </li> + <li>When you right click a View in the Layout Editor, + the context menu now contains <strong>Edit ID...</strong> and <strong>Edit Text...</strong> + items. The <strong>Properties...</strong> context menus now list all of the properties and + provide a way to edit them + (<a href="http://tools.android.com/recent/editidtextandotherpropertiesviamenu">Details</a>). + </li> + <li>The layout editor now properly handles + <a href="{@docRoot}guide/topics/resources/layout-resource.html#include-element"><code><include></code></a> + and <a href="{@docRoot}guide/topics/resources/layout-resource.html#merge-element"><code><merge></code></a> + tags (<a href="http://tools.android.com/recent/supportforincludeandmerge">Details</a>).</li> + <li>"Extract as Include" refactoring: The Layout Editor has a new refactoring that allows + you to select one or more views in a layout, and extract it into a separate layout + (<a href="http://tools.android.com/recent/extractasincluderefactoring">Details</a>).</li> + <li>Improved diagnostics for class loading and rendering errors: Class loading and rendering + error messages are more useful and provide better information about the root cause of the + error.</li> + <li>Improved error handling to prevent drag and reordering operations from adding children + into an {@link android.widget.AdapterView}.</li> + <li>Outline reordering: Reordering your views in the Outline tab is much easier + (<a href="http://tools.android.com/recent/outlineimprovements">Details</a>).</li> + <li>Fix for keybinding bug where keyboard shortcuts did not work (Issues + <a href="http://code.google.com/p/android/issues/detail?id=13231">13231</a> and + <a href="http://code.google.com/p/android/issues/detail?id=13134">13134</a>).</li> + <li>Fix for problems with Custom layout attribute menu (Issue + <a href="http://code.google.com/p/android/issues/detail?id=13134">13134</a>).</li> + <li>Automatic configuration for various view types: Certain views have properties configured + by default. For example, the width of an {@link android.widget.EditText} object is set to + <code>match_parent</code> when added to a vertical {@link android.widget.LinearLayout} + or a default image is added to an {@link android.widget.ImageButton}.</li> + <li>Previews during dragging: Dragging from the palette or dragging within the layout editor + now shows live previews of the dragged item.</li> + <li>Navigation improvements: In the Layout Editor, double-clicking Views jumps to the + corresponding XML element. In the Outline view, double-clicking opens the Properties view.</li> + <li>The editor has Honeycomb style animation preview support.</li> + <li>Improved rendering support for various Views (such as TabHosts and SlidingDrawers) in + Honeycomb (Issues <a href="http://code.google.com/p/android/issues/detail?id=3162">3162</a> + and <a href="http://code.google.com/p/android/issues/detail?id=13092">13092</a>).</li> + <li>Included layouts can be rendered and edited in the context of the layouts that include + them. From a layout using an <a href="{@docRoot}guide/topics/resources/layout-resource.html#include-element"> + <code><include></code></a> tag, double-clicking on the + <a href="{@docRoot}guide/topics/resources/layout-resource.html#include-element"> + <code><include></code></a> element edits the referenced layout in the context of the + current layout. Additionally, when editing a layout that is included by other layouts, + you can quickly change between context layouts, by right clicking in the editor and choosing + <strong>Show included in...</strong>. This feature is only available in Honeycomb.</li> + </ul> + </li> + <li>This release fixes many other bugs, but the most important ones are listed below: + <ul> + <li>Fixed issue that prevented launching debug builds on productions devices when + <code>debuggable=true</code> was not set in the Android manifest.</li> + <li>The LogCat view in DDMS properly handles UTF-8 characters.</li> + <li>The SDK Manager is more reliable on Windows + (<a href="http://tools.android.com/recent/sdkmanagerfixes">Details</a>).</li> + <li>A JUnit initialization bug that prevented you from working with JUnit tests was fixed + (Issue <a href="http://code.google.com/p/android/issues/detail?id=12411">12411</a>).</li> + </ul> +</li> + </ul> +</dd> +</dl> +</div> +</div> + + + + +<div class="toggleable closed"> + <a href="#" onclick="return toggleDiv(this)"> + <img src="{@docRoot}assets/images/triangle-closed.png" class="toggle-img" height="9px" +width="9px" /> ADT 8.0.1</a> <em>(December 2010)</em> <div class="toggleme"> @@ -121,7 +229,7 @@ so.</p></dd> <p>Also see the recent release notes for 8.0.0, below.</p> </dd> </dl> - </div> +</div> </div> diff --git a/docs/html/sdk/images/3.0/browser.png b/docs/html/sdk/images/3.0/browser.png Binary files differnew file mode 100644 index 0000000..5d3ba31 --- /dev/null +++ b/docs/html/sdk/images/3.0/browser.png diff --git a/docs/html/sdk/images/3.0/browser_full.png b/docs/html/sdk/images/3.0/browser_full.png Binary files differnew file mode 100644 index 0000000..495a23d --- /dev/null +++ b/docs/html/sdk/images/3.0/browser_full.png diff --git a/docs/html/sdk/images/3.0/camera.png b/docs/html/sdk/images/3.0/camera.png Binary files differnew file mode 100644 index 0000000..a549182 --- /dev/null +++ b/docs/html/sdk/images/3.0/camera.png diff --git a/docs/html/sdk/images/3.0/camera_full.png b/docs/html/sdk/images/3.0/camera_full.png Binary files differnew file mode 100644 index 0000000..a549182 --- /dev/null +++ b/docs/html/sdk/images/3.0/camera_full.png diff --git a/docs/html/sdk/images/3.0/contacts.png b/docs/html/sdk/images/3.0/contacts.png Binary files differnew file mode 100644 index 0000000..0dcd164 --- /dev/null +++ b/docs/html/sdk/images/3.0/contacts.png diff --git a/docs/html/sdk/images/3.0/contacts_full.png b/docs/html/sdk/images/3.0/contacts_full.png Binary files differnew file mode 100644 index 0000000..829ad11 --- /dev/null +++ b/docs/html/sdk/images/3.0/contacts_full.png diff --git a/docs/html/sdk/images/3.0/copy.png b/docs/html/sdk/images/3.0/copy.png Binary files differnew file mode 100644 index 0000000..363aa8e --- /dev/null +++ b/docs/html/sdk/images/3.0/copy.png diff --git a/docs/html/sdk/images/3.0/copy_full.png b/docs/html/sdk/images/3.0/copy_full.png Binary files differnew file mode 100644 index 0000000..a8db8a2 --- /dev/null +++ b/docs/html/sdk/images/3.0/copy_full.png diff --git a/docs/html/sdk/images/3.0/home_hero1.png b/docs/html/sdk/images/3.0/home_hero1.png Binary files differnew file mode 100644 index 0000000..c81e7ef --- /dev/null +++ b/docs/html/sdk/images/3.0/home_hero1.png diff --git a/docs/html/sdk/images/3.0/home_hero1_full.png b/docs/html/sdk/images/3.0/home_hero1_full.png Binary files differnew file mode 100644 index 0000000..e280b81 --- /dev/null +++ b/docs/html/sdk/images/3.0/home_hero1_full.png diff --git a/docs/html/sdk/images/3.0/homescreen_cust_port.png b/docs/html/sdk/images/3.0/homescreen_cust_port.png Binary files differnew file mode 100644 index 0000000..ef7f5ab --- /dev/null +++ b/docs/html/sdk/images/3.0/homescreen_cust_port.png diff --git a/docs/html/sdk/images/3.0/homescreen_cust_port_full.png b/docs/html/sdk/images/3.0/homescreen_cust_port_full.png Binary files differnew file mode 100644 index 0000000..22433a3e --- /dev/null +++ b/docs/html/sdk/images/3.0/homescreen_cust_port_full.png diff --git a/docs/html/sdk/images/3.0/mail_drag.png b/docs/html/sdk/images/3.0/mail_drag.png Binary files differnew file mode 100644 index 0000000..6084caa --- /dev/null +++ b/docs/html/sdk/images/3.0/mail_drag.png diff --git a/docs/html/sdk/images/3.0/mail_drag_full.png b/docs/html/sdk/images/3.0/mail_drag_full.png Binary files differnew file mode 100644 index 0000000..f99c612 --- /dev/null +++ b/docs/html/sdk/images/3.0/mail_drag_full.png diff --git a/docs/html/sdk/images/3.0/tasks.png b/docs/html/sdk/images/3.0/tasks.png Binary files differnew file mode 100644 index 0000000..9e82dcb --- /dev/null +++ b/docs/html/sdk/images/3.0/tasks.png diff --git a/docs/html/sdk/images/3.0/tasks_full.png b/docs/html/sdk/images/3.0/tasks_full.png Binary files differnew file mode 100644 index 0000000..d2a2241 --- /dev/null +++ b/docs/html/sdk/images/3.0/tasks_full.png diff --git a/docs/html/sdk/images/3.0/widgets.png b/docs/html/sdk/images/3.0/widgets.png Binary files differnew file mode 100644 index 0000000..d847666 --- /dev/null +++ b/docs/html/sdk/images/3.0/widgets.png diff --git a/docs/html/sdk/index.jd b/docs/html/sdk/index.jd index 40eab1c..bfcd14e 100644 --- a/docs/html/sdk/index.jd +++ b/docs/html/sdk/index.jd @@ -1,21 +1,21 @@ page.title=Android SDK sdk.redirect=0 -sdk.win_installer=installer_r08-windows.exe -sdk.win_installer_bytes=32746192 -sdk.win_installer_checksum=04ce87b10a8361a1f63cf2238bbc1ee3 +sdk.win_installer=installer_r09-windows.exe +sdk.win_installer_bytes=32828818 +sdk.win_installer_checksum=a0185701ac0d635a4fbf8169ac949a3c5b3d31e0 -sdk.win_download=android-sdk_r08-windows.zip -sdk.win_bytes=32696391 -sdk.win_checksum=3e0b08ade5bfa9624bce9ddc164a48cb +sdk.win_download=android-sdk_r09-windows.zip +sdk.win_bytes=32779808 +sdk.win_checksum=1a1bb8fad80bcc2dfbd00443b9a13e6b -sdk.mac_download=android-sdk_r08-mac_86.zip -sdk.mac_bytes=28797617 -sdk.mac_checksum=d2e392c4e4680cbf2dfd6dbf82b662c7 +sdk.mac_download=android-sdk_r09-mac_x86.zip +sdk.mac_bytes=28829553 +sdk.mac_checksum=ef3102fdbbbbd9bf4d9b572624aa9dc1 -sdk.linux_download=android-sdk_r08-linux_86.tgz -sdk.linux_bytes=26817291 -sdk.linux_checksum=3b626645b223d137d27beefbda0c94bc +sdk.linux_download=android-sdk_r09-linux_x86.tgz +sdk.linux_bytes=26917824 +sdk.linux_checksum=9fefac5ff85d329836439f6e77a78cae @jd:body diff --git a/docs/html/sdk/installing.jd b/docs/html/sdk/installing.jd index 9de247a..7344bef 100644 --- a/docs/html/sdk/installing.jd +++ b/docs/html/sdk/installing.jd @@ -1,5 +1,4 @@ page.title=Installing the SDK -sdk.preview=0 @jd:body diff --git a/docs/html/sdk/oem-usb.jd b/docs/html/sdk/oem-usb.jd new file mode 100644 index 0000000..14015f5 --- /dev/null +++ b/docs/html/sdk/oem-usb.jd @@ -0,0 +1,81 @@ +page.title=OEM USB Drivers +@jd:body + +<div id="qv-wrapper"> +<div id="qv"> + <h2>See also</h2> + <ol> + <li><a href="{@docRoot}guide/developing/device.html">Developing on a Device</a></li> + <li><a href="{@docRoot}sdk/win-usb.html">Google USB Driver</a></li> + </ol> +</div> +</div> + +<p>If you are developing on Windows and would like to connect an Android-powered device + to test your applications, then you need to install the appropriate USB driver. This document +provides links to the web sites for several device original equipment manufacturers (OEMs), +where you can download the appropriate USB driver for your device. However, this list is +not exhaustive for all available Android-powered devices.</p> + +<p>If your device is one of the Android Developer Phones (ADP), a Nexus One, or a Nexus S, +then you should instead use the <a href="{@docRoot}sdk/win-usb.html">Google USB Driver</a>.</p> + +<p class="note"><strong>Note:</strong> If you're developing on Mac OS X or Linux, then you probably + don't need to install a USB driver. Refer to <a + href="{@docRoot}guide/developing/device.html#setting-up">Setting up a Device</a> to start + development with a device.</p> + +<p>For instructions about how to install the driver on Windows, follow the guide for <a + href="{@docRoot}sdk/win-usb.html#InstallingDriver">Installing the USB Driver</a>.</p> + +<p class="table-caption"><strong>Table 1.</strong> Links to OEM USB drivers</p> +<table><tr> + <th>OEM</th> + <th>Driver URL</th></tr> +<tr><td>Acer</td> <td><a +href="http://www.acer.com/worldwide/support/mobile.html">http://www.acer.com/worldwide/support/ +mobile.html</a> + </td></tr> + +<tr><td>Dell</td> <td> + <a href="http://support.dell.com/support/downloads/index.aspx?c=us&cs=19&l=en&s=dhs&~ck=anavml">http://support.dell.com/support/downloads/index.aspx?c=us&cs=19&l=en&s=dhs&~ck=anavml</a> </td></tr> + +<tr><td>Foxconn</td> <td><a +href="http://drivers.cmcs.com.tw/">http://drivers.cmcs.com.tw/</a></td> +</tr><tr><td>Garmin-Asus</td> <td><a +href="https://www.garminasus.com/en_US/support/pcsync/">https://www.garminasus.com/en_US/support/ +pcsync/</a></td> +</tr><tr><td>HTC</td> <td><a href="http://www.htc.com ">http://www.htc.com </a> <br>Click on the +support tab to select your products/device. Different regions will have different links.</td> +</tr> +<tr><td>Huawei</td> <td><a +href="http://www.huaweidevice.com/worldwide/downloadCenter.do?method=list&flay=software&directoryId= +20&treeId=0">http://www.huaweidevice.com/worldwide/downloadCenter.do?method=list&flay=software& +directoryId=20&treeId=0</a></td> +</tr><tr><td>KT Tech</td> <td><a +href="http://www.kttech.co.kr/cscenter/download05.asp">http://www.kttech.co.kr/cscenter/download05. +asp</a> for EV-S100(Take)</td> +</tr><tr><td>LGE</td> <td><a +href="http://www.lg.com/us/mobile-phones/mobile-support/mobile-lg-mobile-phone-support.jsp">http:// +www.lg.com/us/mobile-phones/mobile-support/mobile-lg-mobile-phone-support.jsp</a></td> +</tr><tr><td>Motorola</td> <td><a +href="http://developer.motorola.com/docstools/USB_Drivers/">http://developer.motorola.com/docstools/ +USB_Drivers/</a></td> +</tr><tr><td>Pantech</td> <td><a +href="http://www.isky.co.kr/cs/software/software.sky?fromUrl=index">http://www.isky.co.kr/cs/ +software/software.sky?fromUrl=index</a></td> +</tr><tr><td>Samsung</td> <td><a +href="http://www.samsung.com/us/support/downloads">http://www.samsung.com/us/support/downloads</a></ +td> +</tr><tr><td>Sharp</td> <td><a +href="http://k-tai.sharp.co.jp/support/">http://k-tai.sharp.co.jp/support/</a></td> +</tr><tr><td>SK Telesys</td> <td><a +href="http://www.sk-w.com/service/wDownload/wDownload.jsp">http://www.sk-w.com/service/wDownload/ +wDownload.jsp</a></td></tr><tr> +<td>Sony Ericsson</td> <td><a +href="http://developer.sonyericsson.com/wportal/devworld/search-downloads/android">http://developer. +sonyericsson.com/wportal/devworld/search-downloads/android</a></td></tr><tr> +<td>ZTE</td> <td><a +href="http://www.zte.com.cn/cn/products/mobile/services_support/index.jsp">http://www.zte.com.cn/cn/ +products/mobile/services_support/index.jsp</a></td></tr> +</table> diff --git a/docs/html/sdk/preview/index.jd b/docs/html/sdk/preview/index.jd index 81b4ff6..edfa02b 100644 --- a/docs/html/sdk/preview/index.jd +++ b/docs/html/sdk/preview/index.jd @@ -1,4 +1,183 @@ -sdk.redirect=true - +page.title=Android 3.0 Preview SDK @jd:body +<p>Android 3.0 is the next major release of the Android platform and is optimized for tablet +devices. We're offering a Preview SDK so you can get a head-start developing +applications for it or simply optimize your existing application for upcoming +tablets.</p> + + +<h3>What is the Preview SDK?</h3> + +<p>The Android 3.0 Preview SDK is an early look at the upcoming version of Android 3.0, for +developers only. </p> + +<p>The Preview SDK includes:</p> +<ul> + <li>An early Android 3.0 system image for use in the Android emulator</li> + <li>An Android 3.0 library with non-final APIs</li> + <li>A new WXGA emulator skin for an extra large Android Virtual Device</li> + <li>New documentation for Android 3.0, including a complete API reference, new developer guides, +and an API differences report between Android 3.0 and 2.3.</li> +</ul> + +<div class="note"> +<p><strong>Be aware that:</strong></p> +<ul> + <li>The APIs in the Preview SDK are <strong>not final</strong>. Some APIs may change in behavior +or availability when the final SDK is made available.</li> + <li>You <strong>cannot</strong> publish an application that's built against the Preview +SDK—you can only run an application built against the Preview SDK on the Android +emulator.</li> + <li>The documentation on <a href="http://developer.android.com">developer.android.com</a> +does <strong>not</strong> include the Android 3.0 documentation—to read the API reference and +developer guides for Android 3.0, you must install the Android 3.0 Preview documentation from +the AVD and SDK Manager.</li> +</ul> +</div> + + +<p><b>About emulator performance</b></p> + +<p>Because the Android emulator must simulate the ARM instruction set architecture on your +computer and the WXGA screen is significantly larger than what the emulator +normally handles, emulator performance is much slower than usual. </p> + +<p>In particular, initializing the emulator can be slow and can take several +minutes, depending on your hardware. When the emulator is booting there is +limited user feedback, so please be patient and continue waiting until you see +the home screen appear. </p> + +<p>We're working hard to resolve the performance issues in the emulator and it will improve in +future releases. In the meantime, we wanted to give developers access to new APIs and an basic test +environment as early as possible. </p> + +<p>Keeping in mind that performance on the emulator does not reflect the speed or performance of +apps on actual devices running Android 3.0, developing and testing on the emulator is still an +important tool in evaluating your application's appearance and functionality on the new platform. +</p> + + + + + +<h3>What can I do with the preview?</h3> + +<p>The Preview SDK is intended for testing existing applications on the new platform and +developing new applications with new Android 3.0 APIs.</p> + +<p>If you have an existing Android application, you don't <em>have to</em> do anything. Android +applications are always forward-compatible. If your application is a good citizen of the Android +APIs, your app should work fine on devices running Android 3.0 without any additional work. However, +in order to ensure proper performance and provide users a better experience when running your +application on an Android 3.0 tablet, we recommend that you perform the following:</p> + +<ol> + <li><b>Test your application on Android 3.0</b> + <p>Simply install the Android 3.0 preview in your Android SDK, create an AVD using the +Android 3.0 system image, install your application, and run some tests.</p> + <p>As mentioned above, your application should perform as expected. You might, however, +discover that your activity layouts are less than ideal on a large screen or some other aspects +of your application don't behave the way you expect.</p> + </li> + <li><b>Inherit the new "Holographic" theme</b> + <p>Android 3.0 offers an updated set of UI widgets that are redesigned for use on larger screens +such as tablets and incorporate the new holographic theme. Your existing application can inherit +the new design simply by setting the <a +href="{@docRoot}guide/topics/manifest/uses-sdk-element.html">{@code <uses-sdk>}</a> +element's {@code android:targetSdkVersion} attribute to {@code "Honeycomb"}.</p> + <p>If you do not update the {@code android:targetSdkVersion} attribute and the {@code +android:minSdkVersion} is set to "9" or lower, then your application uses the widget designs +from Android 2.3 and does <em>not</em> inherit the holographic theme.</p> + <p>In order for your application to match the rest of the system UI, we highly recommend you +make this change to inherit the new widget styles and system theme. However, beware that doing so +might conflict with color or text designs you applied to your application based on the previous +system theme, so you should be sure to inspect your application UI when using the holographic +theme.</p> + </li> + <li><b>Provide alternative layouts for extra large screens</b> + <p>As discussed in the guide to <a +href="{@docRoot}guide/practices/screens_support.html">Supporting Multiple Screens</a>, Android +2.3 and above support the <code>xlarge</code> resource qualifier, which you should use to supply +alternative layouts for extra large screens.</p> + <p>By providing alternative layouts for some of your activities when running on extra large +screens, you can improve the user experience of your application on a tablet without using any +new APIs.</p> + <p>For example, here are some things to consider when creating a new layout for tables:</p> + <ul> + <li>Landscape layout: The "normal" orientation for tablets is usually landscape (wide), so +you should be sure that your activities offer an appropriate layout for such a wide viewing +area.</li> + <li>Button position: Consider whether the position of the most common buttons in your UI are +easily accessible while holding a tablet with two hands.</li> + </ul> + <p class="note"><strong>Note:</strong> You can add alternative resources for <em>xlarge</em> +screens without changing your {@code minSdkVersion}. For example, if you add alternative layouts in +<code>res/layout-xlarge/</code> and your application is compatible with older versions, such +as Android 1.5—which doesn't support <em>xlarge</em> screens—this layout directory is +simply ignored by those devices.</p> + </li> +</ol> + + +<p>Otherwise, if you want to develop a new application or upgrade your existing application to +use APIs added in Android 3.0, we encourage you to get started by developing against the Android +3.0 preview platform. You can get started the same way as you would for any other version of +Android.</p> + + +<p>To get started—whether testing an existing application or creating a new one—follow +the procedure in the following section to install the Preview SDK.</p> + + + +<h3 id="Setup">How do I get it?</h3> + +<p>To get the Preview SDK, you can download it using the Android SDK and AVD Manager.</p> + +<p>If you're new to Android development, start by <a href="{@docRoot}sdk/index.html">downloading the +Android SDK starter package</a>.</p> + +<p><a href="{@docRoot}sdk/adding-components.html#launching">Launch the Android SDK and AVD +Manager</a> and install the following:</p> +<ul> + <li>SDK Platform Android Honeycomb Preview</li> + <li>Android SDK Tools, revision 9</li> + <li>Android SDK Platform-tools, revision 2</li> + <li>Documentation for Android 'Honeycomb' Preview</li> + <li>Samples for SDK API Honeycomb Preview</li> +</ul> + +<p class="note"><strong>Note:</strong> Be sure to install the documentation component for the +Honeycomb Preview SDK. The API reference for the Android 3.0 API is <strong>not</strong> available +online.</p> + +<p>Once you have installed these components, open your SDK directory and navigate to {@code +docs/sdk/} and open {@code index.html} in your browser. </p> + + + +<h3 id="Issues">Known issues</h3> + +<p>The following known issues occur for Android 3.0 AVDs that are loaded in the emulator:</p> + +<ul> + <li>The emulator displays a rotated portrait screen while in landscape +orientation. To view the screen correctly in landscape orientation, turn off the auto-rotate setting +in <strong>Settings > Screen > Auto-rotate screen</strong>. Then use Ctrl-F11 to rotate the +emulator.</li> + <li>You cannot take screenshots of an emulator screen. The Device Screen Capture window displays +<strong>Screen not available</strong>.</li> + <li>GPS emulation is currently not supported.</li> + <li>When rotating the emulator screen by pressing Ctrl-F11, the screen turns green momentarily, +then displays the normal interface.</li> + <li>The Dev Tools application sometimes crashes when trying to use the Package Browser +feature.</li> +</ul> + + +<div class="special"> + <p>For an overview of new features in Android 3.0, read the <a +href="{@docRoot}sdk/android-3.0-highlights.html">Platform Highlights</a>.</p> +</div> + diff --git a/docs/html/sdk/requirements.jd b/docs/html/sdk/requirements.jd index 401dfe3..3d62dd9 100644 --- a/docs/html/sdk/requirements.jd +++ b/docs/html/sdk/requirements.jd @@ -10,8 +10,8 @@ Android applications using the Android SDK. </p> <li>Mac OS X 10.5.8 or later (x86 only)</li> <li>Linux (tested on Ubuntu Linux, Lucid Lynx) <ul> - <li>GNU C Library (glibc) 2.11 or later is required.</li> - <li>On Ubuntu Linux, Lucid Lynx or later release is required.</li> + <li>GNU C Library (glibc) 2.7 or later is required.</li> + <li>On Ubuntu Linux, version 8.04 or later is required.</li> <li>64-bit distributions must be capable of running 32-bit applications. For information about how to add support for 32-bit applications, see the <a href="installing.html#troubleshooting">Ubuntu Linux diff --git a/docs/html/sdk/sdk_toc.cs b/docs/html/sdk/sdk_toc.cs index 7e677e3..3358cf0 100644 --- a/docs/html/sdk/sdk_toc.cs +++ b/docs/html/sdk/sdk_toc.cs @@ -37,6 +37,16 @@ </ul> </li><?cs /if ?> + <?cs + if:sdk.preview ?> + <li><h2>Android 3.0 Preview</h2> + <ul> + <li><a href="<?cs var:toroot ?>sdk/android-3.0-highlights.html">Platform Highlights</a> <span +class="new">new!</span></li> + <li><a href="<?cs var:toroot ?>sdk/preview/index.html">SDK</a> <span class="new">new!</span></li> + </ul> + </li><?cs + /if ?> <li> <h2> <span class="en">Downloadable SDK Components</span> @@ -63,7 +73,7 @@ <ul> <li class="toggle-list"> <div><a href="<?cs var:toroot ?>sdk/android-2.3.html"> - <span class="en">Android 2.3 Platform</span></a> <span class="new">new!</span></div> + <span class="en">Android 2.3 Platform</span></a></div> <ul> <li><a href="<?cs var:toroot ?>sdk/android-2.3-highlights.html">Platform Highlights</a></li> <li><a href="<?cs var:toroot ?>sdk/api_diff/9/changes.html">API Differences Report »</a></li> @@ -83,10 +93,8 @@ </li> </ul> <ul> - <li><a href="<?cs var:toroot ?>sdk/tools-notes.html">SDK Tools, r8</a> <span class="new">new!</span></li> - <li><a href="<?cs var:toroot ?>sdk/win-usb.html">USB Driver for - Windows, r4</a> <span class="new">new!</span> - </li> + <li><a href="<?cs var:toroot ?>sdk/tools-notes.html">SDK Tools, r9</a> <span class="new">new!</span></li> + <li><a href="<?cs var:toroot ?>sdk/win-usb.html">Google USB Driver, r4</a></li> </ul> </li> <li> @@ -101,7 +109,7 @@ <span style="display:none" class="zh-TW"></span> </h2> <ul> - <li><a href="<?cs var:toroot ?>sdk/eclipse-adt.html">ADT 8.0.1 + <li><a href="<?cs var:toroot ?>sdk/eclipse-adt.html">ADT 9.0.0 <span style="display:none" class="de"></span> <span style="display:none" class="es"></span> <span style="display:none" class="fr"></span> @@ -123,7 +131,7 @@ <span style="display:none" class="zh-TW"></span> </h2> <ul> - <li><a href="<?cs var:toroot ?>sdk/ndk/index.html">Android NDK, r5</a> + <li><a href="<?cs var:toroot ?>sdk/ndk/index.html">Android NDK, r5b</a> <span class="new">new!</span></li> <li><a href="<?cs var:toroot ?>sdk/ndk/overview.html">What is the NDK?</a></li> </ul> @@ -141,11 +149,11 @@ <span style="display:none" class="zh-TW"></span> </h2> <ul> + <li><a href="<?cs var:toroot ?>sdk/oem-usb.html"> + <span class="en">OEM USB Drivers</span> + </a></li> <li><a href="<?cs var:toroot ?>sdk/requirements.html">SDK System Requirements</a></li> - <!-- <li><a href="<?cs var:toroot ?>sdk/RELEASENOTES.html">SDK Release - Notes</a></li> --> - <li><a href="<?cs var:toroot ?>sdk/older_releases.html">SDK - Archives</a></li> + <li><a href="<?cs var:toroot ?>sdk/older_releases.html">SDK Archives</a></li> </ul> </li> diff --git a/docs/html/sdk/tools-notes.jd b/docs/html/sdk/tools-notes.jd index f8d7071..7d39e67 100644 --- a/docs/html/sdk/tools-notes.jd +++ b/docs/html/sdk/tools-notes.jd @@ -15,6 +15,7 @@ about how to update, see <a href="{@docRoot}sdk/adding-components.html#UpdatingComponents">Updating SDK Components</a>. </p> + <h2 id="notes">Revisions</h2> <p>The sections below provide notes about successive releases of @@ -64,6 +65,61 @@ padding: .25em 1em; <div class="toggleable opened"> <a href="#" onclick="return toggleDiv(this)"> <img src="{@docRoot}assets/images/triangle-opened.png" class="toggle-img" height="9px" width="9px" /> +SDK Tools, Revision 9</a> <em>(January 2011)</em> + <div class="toggleme"> + <dl> +<dt>Dependencies:</dt> +<dd> +<p>If you are developing in Eclipse with ADT, note that the SDK Tools r9 is +designed for use with ADT 9.0.0 and later. After installing SDK Tools r9, we +highly recommend updating your ADT Plugin to 9.0.0.</p> + +<p>If you are developing outside Eclipse, you must have <a href="http://ant.apache.org/">Apache +Ant</a> 1.8 or later.</p> + +<dt>Upgrading to SDK Tools r9:</dt> +<dd> +<p>If you are upgrading to SDK Tools r9 from SDK Tools r7 or earlier, the default installed location +for the <code>adb</code> tool has changed from <code><<em>SDK</em>>/tools/adb</code> to +<code><<em>SDK</em>>/platform-tools/adb</code>. This means that you should +add the new location to your PATH and modify any custom build scripts to +reference the new location. Copying the <code>adb</code> executable from the new +location to the old is not recommended, since subsequent updates to the SDK +Tools will delete the file.</p> +</dd> + +<dt>General notes:</dt> +<dd> + <ul> + <li>The default ProGuard configuration, <code>proguard.cfg</code>, now ignores the following classes: + <ul> + <li>classes that extend {@link android.preference.Preference}</li> + <li>classes that extend {@link android.app.backup.BackupAgentHelper}</li> + </ul> + </li> + <li>Ant lib rules now allow you to override <code>java.encoding</code>, <code>java.source</code>, + and <code>java.target</code> properties.</li> + <li>The default encoding for the <code>javac</code> Ant task is now UTF-8.</li> + <li>The LogCat view in DDMS now properly displays UTF-8 characters.</li> + <li>The SDK Manager is more reliable on Windows. For details on the improvements, see the + <a href="http://tools.android.com/recent/sdkmanagerfixes">Android Tools Project Site</a>. </li> + <li>If you enabled snapshots for an AVD, they are automatically captured. The emulator also now restores to the state when + it last closed almost instantly.</li> + <li>Fixed the missing JAR file error that prevented <code>draw9patch</code> from running.</li> + <li>Fixed the Windows launch scripts <code>hierarchyviewer</code> and <code>ddms</code> to support + the new location of <code>adb</code>.</li> + <li>Known issues with emulator performance: Because the Android emulator must simulate the ARM +instruction set architecture on your computer, emulator performance is slow. We're working hard to +resolve the performance issues and it will improve in future releases.</li> + </ul> +</dd> +</dl> +</div> +</div> + +<div class="toggleable closed"> + <a href="#" onclick="return toggleDiv(this)"> + <img src="{@docRoot}assets/images/triangle-closed.png" class="toggle-img" height="9px" width="9px" /> SDK Tools, Revision 8</a> <em>(December 2010)</em> <div class="toggleme"> diff --git a/docs/html/sdk/win-usb.jd b/docs/html/sdk/win-usb.jd index 1f74ffe..ffaec4c 100644 --- a/docs/html/sdk/win-usb.jd +++ b/docs/html/sdk/win-usb.jd @@ -1,4 +1,4 @@ -page.title=USB Driver for Windows +page.title=Google USB Driver @jd:body <div id="qv-wrapper"> @@ -6,27 +6,48 @@ page.title=USB Driver for Windows <h2>In this document</h2> <ol> <li><a href="#notes">Revisions</a></li> - <li><a href="#WinUsbDriver">Installing the USB Driver for Windows</a></li> + <li><a href="#WinUsbDriver">Downloading the Google USB Driver</a></li> + <li><a href="#InstallingDriver">Installing the USB Driver</a> + <ol> + <li><a href="#Win7">Windows 7</a></li> + <li><a href="#WinXp">Windows XP</a></li> + <li><a href="#WinVista">Windows Vista</a></li> + </ol> + </li> </ol> <h2>See also</h2> <ol> - <li><a - href="{@docRoot}guide/developing/device.html">Developing on a - Device</a></li> - <li><a - href="adding-components.html">Adding SDK Components</a></li> + <li><a href="{@docRoot}guide/developing/device.html">Developing on a Device</a></li> + <li><a href="{@docRoot}sdk/adding-components.html">Adding SDK Components</a></li> + <li><a href="{@docRoot}sdk/oem-usb.html">OEM USB Drivers</a></li> </ol> </div> </div> -<p>The USB driver for Windows is a downloadable component for the -Android SDK. If you are developing on Windows and would like to -connect an Android-powered device to test your applications, then you will need -to install the USB driver.</p> +<p>The Google USB driver is a downloadable component for Windows developers, available +for download from the AVD and SDK Manager.</p> -<p>This document provides information about the latest version of the -USB driver and a guide to installing the driver on your development -computer.</p> +<p>The Google USB Driver is only for Android Developer Phones (ADP), Nexus One, and Nexus S. +If you're using a different Android-powered device, +then you need to get a USB driver from the device OEM. For help finding the appropriate +driver, see the list of <a href="{@docRoot}sdk/oem-usb.html">OEM USB Drivers</a>.</p> + +<div class="sidebox-wrapper"> +<div class="sidebox"> + <p>The Google USB driver for Windows provides support for the following +Android-powered devices:</p> + <ul> + <li>ADP1 / T-Mobile G1*</li> + <li>ADP2 / Google Ion / T-Mobile myTouch 3G*</li> + <li>Verizon Droid*</li> + <li>Nexus One</li> + <li>Nexus S</li> + </ul> + <p>* <em>Or similar hardware on other carriers</em></p> + <p>Any additional devices will require Windows drivers provided by +the hardware manufacturer. See <a href="{@docRoot}sdk/oem-usb.html">OEM USB Drivers</a>.</p> +</div> +</div> <p class="note"><strong>Note:</strong> If you're developing on Mac OS X or Linux, then you do not need to install a @@ -34,6 +55,12 @@ USB driver. Refer to <a href="{@docRoot}guide/developing/device.html#setting-up">Setting up a Device</a> to start development with a device.</p> +<p>The sections below provide instructions on how to download the USB Driver +for Windows and install it on your development computer. </p> + + + + <h2 id="notes">Revisions</h2> <p>The sections below provide notes about successive revisions of the USB Driver @@ -132,77 +159,49 @@ for the T-Mobile G1 and myTouch 3G (and similar devices).</p></dt> </div> </div> -<h2 id="WinUsbDriver">Installing the USB Driver for Windows</h2> -<div class="sidebox-wrapper"> -<div class="sidebox"> - <p>The USB driver for Windows provides support for the following -Android-powered -devices:</p> - <ul> - <li>ADP1 / T-Mobile G1*</li> - <li>ADP2 / Google Ion / T-Mobile myTouch 3G*</li> - <li>Verizon Droid*</li> - <li>Nexus One</li> - <li>Nexus S</li> - </ul> - <p>* <em>Or similar hardware on other carriers</em></p> - <p>Any additional devices will require Windows drivers provided by -the hardware manufacturer.</p> -</div> +<h2 id="WinUsbDriver">Downloading the Google USB Driver</h2> + +<div class="figure" style="width:498px;margin:0"> + <img src="{@docRoot}images/developing/sdk-usb-driver.png" alt="" /> + <p class="img-caption"><strong>Figure 1.</strong> The SDK and AVD Manager + with the Google USB Driver selected.</p> </div> +<p>The USB Driver for Windows is available for download as an optional SDK +component. You need the driver only if you are developing on Windows and +want to connect an Android-powered device (ADP, Nexus One, or Nexus S) to your +development environment over USB. </p> + +<p>To download the driver, use the Android SDK and AVD Manager tool that is +included with the <a href="{@docRoot}sdk/index.html">Android SDK</a>:</p> +<ol> + <li>Launch the SDK and AVD Manager by double-clicking <code>SDK Manager.exe</code>, + at the root of your SDK directory.</li> + <li>Expand the <em>Third party Add-ons</em> and <em>Google Inc. add-ons</em>.</li> + <li>Check <strong>Google Usb Driver package</strong> and click <strong>Install selected</strong>.</li> + <li>Proceed to install the package. When done, the driver files are +downloaded into the <code><sdk>\google-usb_driver\</code> directory.</li> +</ol> -<p>The sections below provide instructions on how to download the USB Driver -for Windows and install it on your development computer. </p> -<h3>Downloading the USB Driver for Windows</h3> -<p>The USB Driver for Windows is available for download as an optional SDK -component. You need the driver only if you are developing on Windows and -want to connect an Android-powered device to your development environment -over USB. </p> +<h2 id="InstallingDriver">Installing the USB Driver</h2> -<p>To install the driver or upgrade your existing driver to the latest -revision, you must first download the driver to your development computer. </p> +<p>Once you've downloaded your USB driver, follow the instructions below to install or upgrade the +driver, based on your version of Windows and whether you're installing for the first time +or upgrading an existing driver.</p> -<p>To download the driver, use the Android SDK and AVD Manager tool that is -included with the Android SDK. If you haven't yet installed the Android SDK, as -described in <a href="installing.html">Installing the Android SDK</a>, please do -so before continuing with the driver installation. </p> - -<p>When you are ready to download the driver, follow the instructions given in -<a href="adding-components.html">Adding SDK Components</a> to launch the Android -SDK and AVD Manager. From the <strong>Available Packages</strong> panel, select -"Usb Driver Package" and download it to your computer. The driver files are -downloaded into the <code><sdk>\google-usb_driver\</code> directory.</p> - -<p>After the download, follow the instructions below to install or upgrade the -driver, based on your needs and Windows operating system version. If you are -connecting an Android-powered device to your computer for the first time, follow -the below procedure to "Perform a fresh installation." If you have installed one -of the older USB drivers and would like to upgrade to the latest version, follow -the procedure to "Upgrade an existing driver."</p> - -<p>Once you've completed the USB driver installation, -please see <a +<p class="note"><strong>Tip:</strong> When you finish the USB driver installation, +see <a href="{@docRoot}guide/developing/device.html">Developing on a Device</a> for other important information about using an Android-powered device for development.</p> <ol class="nolist"> - <li><strong>Windows Vista:</strong> - <ol class="nolist"> - <li><a href="#VistaFreshInstall">Perform a fresh installation</a></li> - <li><a href="#VistaUpgrade">Upgrade an existing driver</a></li> - </ol> - </li> - <li><strong>Windows XP:</strong> - <ol class="nolist"> - <li><a href="#XPFreshInstall">Perform a fresh installation</a></li> - <li><a href="#XPUpgrade">Upgrade an existing driver</a></li> - </ol> - </li> + <li><a href="#Win7">Windows 7</a></li> + <li><a href="#WinXp">Windows XP</a></li> + <li><a href="#WinVista">Windows Vista</a></li> </ol> @@ -213,94 +212,140 @@ however, this will lead to security warnings when you install or upgrade the driver. Making any other changes to the driver files may break the installation process.</p> -<h3 id="VistaFreshInstall">Windows Vista: Perform a fresh installation</h3> -<p>To install the Android USB driver on Windows Vista for the first time:</p> +<h3 id="Win7">Windows 7</h3> + +<p>To install the Android USB driver on Windows 7 for the first time:</p> <ol> - <li>Connect your Android-powered device to your computer's USB port. Windows - will detect the device and launch the Found New Hardware wizard.</li> - <li>Select "Locate and install driver software."</li> - <li>Select "Don't search online."</li> - <li>Select "I don't have the disk. Show me other options."</li> - <li>Select "Browse my computer for driver software."</li> - <li>Click "Browse..." and locate the folder where you copied the - installation package. As long as you specified the exact location of the - installation package, you may leave "Include subfolders" checked or - unchecked—it doesn't matter.</li> - <li>Click "Next." Vista may prompt you to confirm the privilege elevation - required for driver installation. Confirm it.</li> - <li>When Vista asks if you'd like to install the Google ADB Interface device, - click "Install" to install the driver.</li> + <li>Connect your Android-powered device to your computer's USB port.</li> + <li>Right-click on <em>Computer</em> from your desktop or Windows Explorer, + and select <strong>Manage</strong>.</li> + <li>Select <strong>Devices</strong> in the left pane.</li> + <li>Locate and expand <em>Other device</em> in the right pane.</li> + <li>Right-click the device name (such as <em>Nexus S</em>) and select <strong>Update + Driver Software</strong>. + This will launch the Hardware Update Wizard.</li> + <li>Select <strong>Browse my computer for driver software</strong> and click + <strong>Next</strong>.</li> + <li>Click <strong>Browse</strong> and locate the USB driver folder. (The Google USB +Driver is located in {@code <sdk>\google-usb_driver\}.)</li> + <li>Click <strong>Next</strong> to install the driver.</li> </ol> - -<h3 id="VistaUpgrade">Windows Vista: Upgrade an existing driver</h3> - -<p>To upgrade an existing Android USB driver on Windows Vista with the new +<p>Or, to <em>upgrade</em> an existing Android USB driver on Windows 7 with the new driver:</p> <ol> <li>Connect your Android-powered device to your computer's USB port.</li> - <li>Right-click on "Computer" from your desktop or Windows Explorer, - and select "Manage."</li> - <li>Select "Device Manager" in the left pane of the Computer Management + <li>Right-click on <em>Computer</em> from your desktop or Windows Explorer, + and select <strong>Manage</strong>.</li> + <li>Select <strong>Device Manager</strong> in the left pane of the Computer Management window.</li> - <li>Locate and expand "ADB Interface" in the right pane.</li> - <li>Right-click on "HTC Dream Composite ADB Interface", and select "Update - Driver Software..."</li> - <li>When Vista starts updating the driver, a prompt will ask how you want to - search for the driver - software. Select "Browse my computer for driver software."</li> - <li>Click "Browse..." and locate the folder where you copied the - installation package. As long as you specified the exact location of the - installation package, you may leave "Include subfolders" checked or - unchecked—it doesn't matter.</li> - <li>Click "Next." Vista may prompt you to confirm the privilege elevation - required for driver installation. Confirm it.</li> - <li>When Vista asks if you'd like to install the Google ADB Interface device, - click "Install" to install the driver.</li> + <li>Locate and expand <em>Android Phone</em> in the right pane.</li> + <li>Right-click <em>Android Composite ADB Interface</em> and select <strong>Update + Driver</strong>. + This will launch the Hardware Update Wizard.</li> + <li>Select <strong>Install from a list or specific location</strong> and click + <strong>Next</strong>.</li> + <li>Select <strong>Search for the best driver in these locations</strong>; un-check +<strong>Search removable media</strong>; and check <strong>Include this location in the +search</strong>.</li> + <li>Click <strong>Browse</strong> and locate the USB driver folder. (The Google USB +Driver is located in {@code <sdk>\google-usb_driver\}.)</li> + <li>Click <strong>Next</strong> to upgrade the driver.</li> </ol> -<h3 id="XPFreshInstall">Windows XP: Perform a fresh installation</h3> + + + +<h3 id="WinXp">Windows XP</h3> <p>To install the Android USB driver on Windows XP for the first time:</p> <ol> <li>Connect your Android-powered device to your computer's USB port. Windows will detect the device and launch the Hardware Update Wizard.</li> - <li>Select "Install from a list or specific location" and click - "Next."</li> - <li>Select "Search for the best driver in these locations"; un-check "Search - removable media"; and check "Include this location in the search."</li> - <li>Click "Browse..." and locate the folder where you copied the installation - package.</li> - <li>Click "Next" to install the driver.</li> + <li>Select <strong>Install from a list or specific location</strong> and click + <strong>Next</strong>.</li> + <li>Select <strong>Search for the best driver in these locations</strong>; un-check +<strong>Search + removable media</strong>; and check <strong>Include +this location in the search</strong>.</li> + <li>Click <strong>Browse</strong> and locate the USB driver folder. (The Google USB +Driver is located in {@code <sdk>\google-usb_driver\}.)</li> + <li>Click <strong>Next</strong> to install the driver.</li> +</ol> + +<p>Or, to <em>upgrade</em> an existing Android USB driver on Windows XP with the new +driver:</p> + +<ol> + <li>Connect your Android-powered device to your computer's USB port.</li> + <li>Right-click on <em>My Computer</em> from your desktop or Windows Explorer, + and select <strong>Manage</strong>.</li> + <li>Select <strong>Device Manager</strong> in the left pane.</li> + <li>Locate and expand <em>Android Phone</em> in the right pane.</li> + <li>Right-click <em>Android Composite ADB Interface</em> and select <strong>Update + Driver</strong>. + This will launch the Hardware Update Wizard.</li> + <li>Select <strong>Install from a list or specific location</strong> and click + <strong>Next</strong>.</li> + <li>Select <strong>Search for the best driver in these locations</strong>; un-check <strong>Search + removable media</strong>; and check <strong>Include +this location in the search</strong>.</li> + <li>Click <strong>Browse</strong> and locate the USB driver folder. (The Google USB +Driver is located in {@code <sdk>\google-usb_driver\}.)</li> + <li>Click <strong>Next</strong> to upgrade the driver.</li> </ol> -<h3 id="XPUpgrade">Windows XP: Upgrade an existing driver</h3> -<p>To upgrade an existing Android USB driver on Windows XP with the new +<h3 id="WinVista">Windows Vista</h3> + +<p>To install the Android USB driver on Windows Vista for the first time:</p> + +<ol> + <li>Connect your Android-powered device to your computer's USB port. Windows + will detect the device and launch the Found New Hardware wizard.</li> + <li>Select <strong>Locate and install driver software</strong>.</li> + <li>Select <strong>Don't search online</strong>.</li> + <li>Select <strong>I don't have the disk. Show me other options</strong>.</li> + <li>Select <strong>Browse my computer for driver software</strong>.</li> + <li>Click <strong>Browse</strong> and locate the USB driver folder. (The Google USB +Driver is located in {@code <sdk>\google-usb_driver\}.) As long as you specified the exact +location of the + installation package, you may leave <strong>Include subfolders</strong> checked or + unchecked—it doesn't matter.</li> + <li>Click <strong>Next</strong>. Vista may prompt you to confirm the privilege elevation + required for driver installation. Confirm it.</li> + <li>When Vista asks if you'd like to install the Google ADB Interface device, + click <strong>Install</strong> to install the driver.</li> +</ol> + +<p>Or, to <em>upgrade</em> an existing Android USB driver on Windows Vista with the new driver:</p> <ol> <li>Connect your Android-powered device to your computer's USB port.</li> - <li>Right-click on "My Computer" from your desktop or Windows Explorer, - and select "Manage."</li> - <li>Select "Device Manager" in the left pane of the Computer Management - window.</li> - <li>Locate and expand "Android Phone" in the right pane.</li> - <li>Right-click "Android Composite ADB Interface" and select "Update - Driver..." - This will launch the Hardware Update Wizard.</li> - <li>Select "Install from a list or specific location" and click - "Next."</li> - <li>Select "Search for the best driver in these locations"; un-check "Search - removable media"; and check "Include this location in the search."</li> - <li>Click "Browse..." and locate the folder where you copied the installation - package.</li> - <li>Click "Next" to install the driver.</li> + <li>Right-click on <em>Computer</em> from your desktop or Windows Explorer, + and select <strong>Manage</strong>.</li> + <li>Select <strong>Device Manager</strong> in the left pane.</li> + <li>Locate and expand <em>ADB Interface</em> in the right pane.</li> + <li>Right-click on <em>HTC Dream Composite ADB Interface</em>, and select <strong>Update + Driver Software</strong>.</li> + <li>When Vista starts updating the driver, a prompt will ask how you want to + search for the driver + software. Select <strong>Browse my computer for driver software</strong>.</li> + <li>Click <strong>Browse</strong> and locate the USB driver folder. (The Google USB +Driver is located in {@code <sdk>\google-usb_driver\}.) As long as you specified the +exact location of the + installation package, you may leave <strong>Include subfolders</strong> checked or + unchecked—it doesn't matter.</li> + <li>Click <strong>Next</strong>. Vista might prompt you to confirm the privilege elevation + required for driver installation. Confirm it.</li> + <li>When Vista asks if you'd like to install the Google ADB Interface device, + click <strong>Install</strong> to upgrade the driver.</li> </ol> |
